[SOLVED] just compiled kernel will not boot

markush · 10-14-2009, 02:05 PM

Hello,

boot with a live-CD and do a chroot into the partition. Then you can reconfigure your lilo.conf and execute lilo.

Markus

doc.nice · 10-14-2009, 03:43 PM

Thats what I meant with ATTENTION...

You now have to boot with the installation cd into recovery mode or such
or you have to use a live cd to reach a console:

download the iso image e.g. from www.grml.org
insert, reboot, boot from cd
you will end with a linux terminal.
type mount /media/hda1 (or mount /mnt/hda1, depending on the live cd)
type vi /media/hda1/boot/lilo.conf to revert the changes you made
(or use any other editor you are familiar in)
save the file, exit the editor and type reboot
eject cd, your old kernel should boot again.

When both kernels dislike sd1, it seems you are good with hda1, but missing the support for your root filesystem.
check if ext2 (or ext3 or whatever you use, see "mount" when running with the old kernel) and the partition support is compiled in.

For the FS support:

File systems --> <*> second extended fs support,
File systems --> <*> Ext3 journalling file system support

you can safely enable both.

For the partition table support:

either disable the advanced selection if you don't need it:
File systems --> Partition Types --> [ ] Advanced partition selection

or ensure that your type, usually DOS partition tables, is enabled:
File systems --> Partition Types -->[*] Advanced partition selection -->[*] PC BIOS (MSDOS partition tables) support

again, compiling as modules [M] does NOT work here.

smeezekitty · 10-14-2009, 04:49 PM

bash-2.05b#mount -t vfat /dev/hda1 -o wr /mnt/hda1
bash-2.05b#chroot /mnt/hda1
bash-2.05b#vi /etc/lilo.conf
bash-2.05b#lilo
Fatal: open /dev/hda1: Permission denied
Process returned on error.
bash-2.05b#

doc.nice · 10-14-2009, 04:54 PM

mount -o remount,suid,dev,rw /dev/hda1

the default in your live cd seems to mount (noexec,)nosuid...
then try again calling lilo

smeezekitty · 10-14-2009, 04:57 PM

ok its booting again YAY

doc.nice · 10-14-2009, 05:06 PM

good to hear

smeezekitty · 10-14-2009, 06:05 PM

i mean the old kernel the new one is still busted

smeezekitty · 10-14-2009, 08:30 PM

smeezekitty · 10-15-2009, 02:30 AM

bump again?

markush · 10-15-2009, 04:30 AM

Hello smeezekitty,

if you want to do an upgrade from a 2.4 to a 2.6 kernel, I'd recommend to do a complete new installation. That is what I would do in this case. Don't forget to make a backup of your home-directory.

Markus

doc.nice · 10-15-2009, 07:52 AM

sorry, in germany, your bumps where in the middle of the night...
Give an old man (TM) a little sleep

I think it's not necessary to do a reinstall, especially in this case:
the new kernel doesn't boot because some modules are missing, I suppose, a clean hd install would fix this.

Is there any reason you have to create your own kernel and cannot use a pre-packed one from your distribution?
this may work rather straightforward...

could you send your kernel .config file, the output of lspci and the exact kernel version you are trying to build?
I can then double check your settings in a virutal machine.

smeezekitty · 10-15-2009, 12:05 PM

kernel version 2.6.31 (i think its current, unpatched)
my .config is attached below

doc.nice · 10-15-2009, 12:43 PM

OK, possibly found the bug:
You seem not to have selected any IDE controller driver.

Check the output of lspci to find out what ide controller you use.
then enable the driver under Device Drivers, ATA/ATAPI/MFM/RLL support.
You can also try the Generic/default IDE chipset support and/or Generic PCI IDE chipset support.
The Intel PIIX/ICH, AMD/NVidia and ATI drivers are also a good candidate to try.
Simple enable all possible candidates for you...

Alternative: Device Drivers, Serial ATA (prod) and parallel ATA (experimental) drivers:
ATA SSF support, and again: whatever seems appropriate (Generic, Intel PATA MPIIX, Ati, Via, AMD/NVidia, ...)

You should decide if you use the first OR the second alternative, not both. And again the second alternative may need to use /dev/sda1 instead of /dev/hda1, but you are more "future-safe".

HTH,
Florian

smeezekitty · 10-15-2009, 12:51 PM

ok:

Code:

root@box:~# lspci
00:01.0 ISA bridge: Generic ISA bridge
00:01.1 IDE interface: Generic IDE Controller
00:02.0 EGA compatible controller
00:03.0 ???
00:04.0 ???
00:05.0 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller
00:06.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB

doc.nice · 10-15-2009, 01:50 PM

well, try the generic one, with that excat lspci info