My 2.4.0 did that the first time when I had the entry vga=788 in lilo and
didn't compile in framebuffer and virtual terminal support (I think they were
called.). Check your lilo for that and remove it or change 788 to normal and
see if it'll boot. [It was as though if I could by esp feel my way to the
sign in, it would log in. (It went thru the boot process, I just couldn't
see it, but I could tell it was doing it by the sounds). Is that what you
mean?]
-s
---------- Forwarded Message ----------
Subject: Re: [expert] Problems with 2.4.1 kernel, will not boot.
Date: Mon, 5 Feb 2001 19:48:56 -0500
From: Neal Lippman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], "anmat" <[EMAIL PROTECTED]>
I am also having problems getting 2.4.1 to boot, and trying has been trashing
my system to boot (no pun intended). I've already posted how trying to boot
lost my supermount entries in /etc/fstab (which I've figured out; see
separate post) and also my ability to mount windows (vfat) file systems
(which I now realized is because enabling and disabling supermount has
trashed that entry in fstab, and I have now fixed...)
I have done make xconfig to configure up the 2.4.1 kernel and compiled, and
tried this several different ways. When I try to boot the 2.4.1 kernel, the
system "hangs". However, it seems to be accessing the hard drive, but the
monitor remains blank. There is a clicking sound from the monitor, suggesting
it has set a video mode, that perhaps the monitor or the video card is not
handling correctly. I have not yet been able to figure this out.
My grub's menu.lst is as follows:
**** START GRUB MENU.LST ****
timeout 5
color black/cyan yellow/cyan
i18n (hd0,0)/grub/messages
keytable (hd0,0)/us.klt
altconfigfile (hd0,0)/grub/menu.once
default 0
title linux
kernel (hd0,0)/vmlinuz root=/dev/hda5 hdd=ide-scsi vga=788
title linux-2.4.1
kernel (hd0,0)/vmlinuz-2.4.1 root=/dev/hda5 hdd=ide-scsi vga=788
title linux-backup
kernel (hd0,0)/vmlinuz-2.2.17-21mdk-backup root=/dev/hda5 hdd=ide-scsi
vga=788
title windows
root (hd0,1)
makeactive
chainloader +1
title floppy
root (fd0)
chainloader +1
*** END GRUB MENU.LST ****
Note that the "vga=788" was copied from the linux section that boots vmlinuz,
whch is a symlink to /boot/vmlinuz-2.2.17-21mdk, so I presume my system can
handle that video mode.
My system, if anyone has any ideas, is a PIII/800 with an ASUS CUSL-2
motherboard. The video card is a Guillemot Prophet II MX in the AGP slot and
the onboard video of the i815 chipset is disabled. (BTW: I don't think the
problem is 2.4.1 trying to use the onboard video, because then themonitor
would presumable give the "no signal" display rather than just remaining
dark).
In the kernel config, I have included MTRR, and have disabled DRI since I
don't think it is supported for nvidia based cards, and also because as far
as I can tell, none of the listed video drivers that enable when you select
DRI are applicable for this card.
I note that I have a /proc/mtrr directory which responds with appropriate
data to "cat /proc/mtrr" so I presume that mtrr works fine on my system.
My config does include v4l, firewire, xircom USB-based cam, ide-scsi, but
nothing else extraordinary.
Any ideas?
On Monday 05 February 2001 13:36, anmat wrote:
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, February 06, 2001 12:29 AM
> Subject: [expert] Problems with 2.4.1 kernel, will not boot.
>
> > I have just installed the 2.4.1-2 version of the kernel, but my
>
> system
>
> > will no longer reboot. It hangs at the point when it says "Loading
> > Linux".
>
> Make sure that when you do make menuconfig (or whichever you use) that you
> select the correct processor (In the first or second option set). It
> defaults to Pentium 3, and if you don't have one, the kernel will hang at
> boot just like you describe.
>
> > If i try to boot off a floppy created with the 2.4.0-12 kernel in
> > place, the system boots, but I get error messages saying reiserfs is
> > not supported, supermount is also not supported, along with an
> > abundance of "file not found" messages due to the reiserfs
> > filesystems. Then, when I get a prompt, I am unable to log on. I
> > enter the user, but am not asked for a password and am told "login
> > incorrect."
>
> It sounds like it can't find the root file system . This is actually coded
> into the kernel, although you can change it.
>
> For future reference:
>
> #rdev /boot/<name of kernel image>
>
> will tell you which partition is coded in as root. To change it:
>
> rdev /boot/<name of kernel image> /dev/<root partition>
>
> If the kernel your booting is on the root partition, it shouldn't matter
> whats coded into it, but, if its on a floppy, it critical.
>
> One way to recover is to get hold of http://www.toms.net/rb/ (tomsrtbt - a
> linux distribution on a floppy - great tool kit - can be transfered to
> floppy from either linux or Dos), and boot up with it. You can then mount
> your root partition (lucky its not reiserfs here, tomsrtbt doesn't support
> it), remove the floppy (tomsrtbt loads into a ramdisk), then rename your
> old kernel and system.map or copy a good kernel from floppy into /boot. You
> did back-up your old kernel before installing the new one, didn't you?
>
> > I have also tried booting from a floppy created under the 2.2.17-21
> > kernel but get the same message. All my filesystems are reiserfs
> > except for root.
> >
> > Is my system recoverable, and if so, how?
>
> This is Linux, almost anything is recoverable. Hope I've been of help.
>
> > Ben Greenfield
> >
> > System Administrator
> > Brake Bros Foodservice Ltd
> > Tel: 01233 206603
> > Fax: 01233 206172
> > e-mail: [EMAIL PROTECTED]
-------------------------------------------------------
