Re: new kernel >>> can't boot into debian (Solved)
The problem is solved, thanks. It was just the vga in lilo, it needed to be
normal.
----Original Message Follows----
From: Jerome Acks Jr <jracksjr@bellatlantic.net>
To: debian-user@lists.debian.org
Subject: Re: new kernel >>> can't boot into debian (not solved yet)
Date: Sun, 11 May 2003 22:01:27 -0400
MIME-Version: 1.0
Received: from murphy.debian.org ([146.82.138.6]) by
mc2-f11.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Sun, 11 May
2003 19:21:21 -0700
Received: from localhost (localhost [127.0.0.1])by murphy.debian.org
(Postfix) with QMQPid BC2321F85F; Sun, 11 May 2003 21:20:17 -0500 (CDT)
Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106])by
murphy.debian.org (Postfix) with ESMTP id E68C91F5F3for
<debian-user@lists.debian.org>; Sun, 11 May 2003 21:01:30 -0500 (CDT)
Received: from xanadu.home.l ([141.157.82.198]) by out006.verizon.net
(InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
id <20030512020130.WSFP25800.out006.verizon.net@xanadu.home.l>
for <debian-user@lists.debian.org>; Sun, 11 May 2003 21:01:30 -0500
Received: from dad by xanadu.home.l with local (Exim 3.36 #1 (Debian))id
19F2d5-0003yt-00for <debian-user@lists.debian.org>; Sun, 11 May 2003
22:01:27 -0400
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
Old-Return-Path: <jracksjr@bellatlantic.net>
Message-ID: <[🔎] 20030512020127.GA14961@xanadu.home.l>
Mail-Followup-To: debian-user@lists.debian.org
References: <[🔎] BAY8-F126hMB0iiOrkk0000c1a9@hotmail.com>
In-Reply-To: <[🔎] BAY8-F126hMB0iiOrkk0000c1a9@hotmail.com>
User-Agent: Mutt/1.5.3i
X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from
[141.157.82.198] at Sun, 11 May 2003 21:01:30 -0500
X-Spam-Status: No, hits=-40.5
required=4.0tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2,
QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,
USER_AGENT_MUTTautolearn=ham version=2.53-lists.debian.org_2003_04_28
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-lists.debian.org_2003_04_28
(1.174.2.15-2003-03-30-exp)
Resent-Message-ID: <_dNr1C.A.JDB.hTwv-@murphy>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/279094
X-Loop: debian-user@lists.debian.org
List-Post: <mailto:debian-user@lists.debian.org>
List-Help: <mailto:debian-user-request@lists.debian.org?subject=help>
List-Subscribe:
<mailto:debian-user-request@lists.debian.org?subject=subscribe>
List-Unsubscribe:
<mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
Resent-Date: Sun, 11 May 2003 21:20:17 -0500 (CDT)
Return-Path: bounce-debian-user=gezimh=hotmail.com@lists.debian.org
X-OriginalArrivalTime: 12 May 2003 02:21:21.0225 (UTC)
FILETIME=[2D7CBB90:01C3182D]
On Sun, May 11, 2003 at 03:18:36AM -0600, Gezim H wrote:
> Yes, I changed lilo.conf to include /boot/kernel-2.4.20 instead of
> kernel-2.2.20-idepci, then I ran it.
> Lilo works fine, because lilo shows up but then the monitor light blinks
> twice or so, and just the black screen apears, no errors, no anything.
The
> funny thing is that it seems as the monitor is off, because if I wait for
a
> little while, and press <CTRL>+<ALT>+<DEL> it reboots fine.
> I'm not sure what initrd is!
see man initrd
> I compiled a whole new kernel with new options, so I don't know the
options
> of 2.2.20 kernel.
>
Not enough usefull information to figure out your problem.
I suggest you download one of the stock 2.4.20 debian kernel-images
and install that. If you can get that to boot, you can copy its config
file from /boot to your kernel source tree and use that config file as
starting point for your custom kernel.
Assuming you still have kernel-image-2.2.20-idepci installed, add
following lines to lilo.conf to ensure you can always boot that image
by typing "2.2.20" at lilo prompt:
image=/vmlinuz-2.2.20-idepci
label=2.2.20
read-only
Since stock debian 2.4.x kernels use initrd, your lilo.conf should
also have lines like:
image=/vmlinuz
label=linux
read-only
# comment the next line for a non-initrd kernel
initrd=/boot/initrd.img
--
Jerome
<< attach3 >>
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
Reply to: