LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Problems booting with 2.6.15.2 kernel (https://www.linuxquestions.org/questions/slackware-14/problems-booting-with-2-6-15-2-kernel-410903/)

Changeling 02-02-2006 11:06 AM

Problems booting with 2.6.15.2 kernel
 
Hi guys,
Got a problem booting. I'm running slackware 10.2 current. I compiled the 2.6.15.2 kernel, but haven't been able to boot since. It freezes at this point:
Loading Linux-2.6.15.2
Bios data check successful
Uncompressing Linux.. Ok, booting the kernel
I've tried several times to recompile the old kernel, which was the 2.6.14.5, but I can't get that one to work either. After I finish the compile and do the /sbin/lilo, I get this message:
Warning '/proc/partions does not exist disk scan bypassed.
I'm trying not to reinstall. Has anybody run into this?
Thanks,
tom

MS3FGX 02-02-2006 11:13 AM

What does your lilo.conf look like (the part about the kernel images)?

And I am assuming that the stock 2.6 Slackware kernel did work properly? Or no?

mint567 02-02-2006 11:43 AM

have you updated udev, module-init-tools, etc. New kernel 2.6.15 requires udev > 071 i beleive.

Changeling 02-02-2006 12:29 PM

Quote:

Originally Posted by MS3FGX
What does your lilo.conf look like (the part about the kernel images)?

And I am assuming that the stock 2.6 Slackware kernel did work properly? Or no?

This is my lilo part regarding the kernel
image= /boot/vmlinux-2.6.14.5
root= /dev/sda2
Label= Linux-2.6.14.5
read-only
And yes, the stock kernel did work, so did the 2.6.14.5

Changeling 02-02-2006 12:30 PM

Quote:

Originally Posted by mint567
have you updated udev, module-init-tools, etc. New kernel 2.6.15 requires udev > 071 i beleive.

That I didn't do. That's probably the problem. I'll try that this afternoon before going to work

mdarby 02-02-2006 01:27 PM

hrm. I'm having a bit of trouble getting my new 2.6.15.2 to boot as well...

MS3FGX 02-02-2006 09:57 PM

The system would not check for udev, module-init-tools, or anything else for that matter, until later on in the boot process. That isn't causing your current problem.

Are you sure that you compiled in framebuffer support so that your kernel is able to output video to your monitor?

"Uncompressing Linux.. Ok, booting the kernel" is the last thing LILO says before actually loading the kernel image, so any output past that point would be the job of the kernel. If you didn't include FB support, you would see nothing until the machine loaded X (assuming you have it set to boot into X).

Changeling 02-02-2006 11:16 PM

I found out what I did;) I have two computers running Slackware and when I went to compile I used the Athlon processor instead of the Intel pentium 4. One of my computers is an Athlon XP 2800 and the one I'm running now is Pentium 4 2.8. I had an epiphany at work today and just now recompiled with the proper processor enabled and I'm good to go. Thanks everyone for there kind assistance.;)


All times are GMT -5. The time now is 03:41 AM.