2.6.10 reboots

salted · 02-10-2005, 12:34 PM

Hi all. I've searched over these forums for the past few days, and I haven't found anything matching the problem I'm having.

A couple of days ago, I compiled the 2.6.10 kernel into my Slack 10 box here at home. I followed Shilo's instructions on his site (although I did it from command line since I can't get into X from root). Everything went smoothly with no error messages, and I updated and ran Lilo. After restarting I selected 2.6.10 from lilo and it said "Loading 2.6.10" "BIOS Data Check successful" and then restarted. This has happened to me about 5 times. I'm booting from my old 2.4.x kernel right now. I checked most of what I could think of, making sure the symlinks were right and that I copied System.map and .config over correctly.

Anyone have any ideas? I'm wondering if its a framebuffer issue maybe? I'm not real sure where to go with this, but framebuffer seems to be a common problem.

Thanks in advance,
salted

mdarby · 02-10-2005, 12:53 PM

If it was just a framebuffer issue, the kernel would still boot. I would suspect hardware drivers not being compiled in.

Matir · 02-10-2005, 12:58 PM

Are you using initrd? That can cause headaches.

salted · 02-10-2005, 01:39 PM

Ouch, I guess I screwed up, this being my first compile and all. Yes, I'm running initrd. Should I just recompile everything from scratch again? I have the day off, so its no biggie if I have to.

Thanks,
salted

shilo · 02-10-2005, 02:13 PM

Quote:

I would suspect hardware drivers not being compiled in.

Me, too.

Quote:

I'm running initrd.

Why? Try not using it before you try re-compiling. Remember to run /sbin/lilo.

Quote:

Should I just recompile everything from scratch again?

You don't have to start from scratch, really. If you have the /usr/src/linux symlinked to /usr/src/linux-2.6.10, just login as root and:

Code:

cd /usr/src/linux
make menuconfig #Easiest from CLI IMHO.  Make any changes.
make bzImage
cp arch/i386/boot/bzImage vmlinuz-2.6.10
make modules
make modules_install
cp .config /boot/config-2.6.10
cp System.map /boot/System.map-2.6.10
ln -s /boot/config-2.6.10 /boot/config
ln -s /boot/System.map-2.6.10 /boot/System.map
vi /etc/lilo.conf #or whatever editor you like.  No initrd.
/sbin/lilo

***EDIT***
I also:

Code:

ln -s /boot/vmlinuz-2.6.10 /boot/vmlinuz

If you do that, make sure all the entries in /etc/lilo.conf are pointing where you want them to point, i.e. the entry for the stock 2.4 kernel should not point to the symlink. My example /etc/lilo.conf reflects this change.

***/EDIT***

For me, this works. It is way faster than the initial compile, too. Here's a copy of my /etc/lilo.conf for reference.

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
prompt
timeout = 600
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
bitmap = /boot/logo64a.bmp
bmp-colors = 15,,0;5,,15
bmp-table = 59,5,1,18,
bmp-timer= 66,28,6,8,0
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.10-ck
  root = /dev/hda1
  label = Linux-2.6.10ck
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.10
  root = /dev/hda1
  label = Linux-2.6.10
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.28
  root = /dev/hda1
  label = Linux-2.4.28
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

salted · 02-12-2005, 07:57 PM

Sorry this has taken so long to respond; I've been busy. Shilo, I did what you said to a T, and then rebooted and nothing worked. Then, I tried to boot into my 2.4 kernel, and it did the same thing, so I'm speaking to you from my Windows partition. I've decided that I really screwed up, and I don't think I know what hardware support I'm missing. Maybe someone could help me out?

Thanks,
salted

mdarby · 02-12-2005, 09:30 PM

can you boot into your slack install at all? If so, can you post the output from 'dmesg' and 'ls -l /boot'

If not, unless you can nuke your current install and reinstall, you need to find a good linux boot disk (I recommend http://www.sysresccd.org/); boot into it, chroot into your existing install and run those commands listed above.