LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Simple boot problem...but I can't fix it (https://www.linuxquestions.org/questions/linux-newbie-8/simple-boot-problem-but-i-cant-fix-it-174323/)

jamaas 04-25-2004 04:45 AM

Simple boot problem...but I can't fix it
 
I can not get a new kernel to boot. I started with Mandrake 10 and have dowloaded and compiled the new kernel 2.6.5 and then patched it to 2.6.6. I can not get either 2.6.5 or 2.6.6 to boot, using either lilo or grub! Neither new kernel seems to be able to find my / directory to boot and I get the standard
"vfs: can not open root device "303" or hda3
please append a correct "root"= boot option"

grub just says
"error 15: file not found"

Its pretty obvious what this means but I can not figure out why it is doing this. Same setup works fine to boot the original 2.6.3mdk kernel. I've compiled both ext2 and ext3 filesystems directly into th new kernels (not as modules), created a new initrd and all but can not get past this step. Can anyone give me some ideas about steps to diagnose what might be causing this? I know that distro kernels can be heavily hacked but surely the new vanilla kernels can find a simple ide, /dev/hda3 root file system when compiled properly.

I've googled and read and downloaded etc and still nothing works.

This is a HP pavilion ze5200 notebook and HP has set up some unusual disk partitions for some of their own stuff, which might be part of the problem but I can't find out how to fix it.

Grub menu.list is at bottom. "Linux" boots fine but Linux-2.6.6" just gives error 15!!

Any suggestions welcome.

Thanks

Jim


=================================
#
# Sample boot menu configuration file
#

# Boot automatically after a minute.
timeout 15

# By default, boot the second entry.
default 1

# Fallback to the first entry.
fallback 0

title XP
unhide (hd0,0)
#hide (hd0,1)
#hide (hd0,2)
rootnoverify (hd0,0)
chainloader +1
#makeactive

# For booting Linux
title Linux
root (hd0,2)
kernel /boot/vmlinuz root=/dev/hda3
makeactive

# For booting Linux 2.6.6
title Linux-2.6.6
root (hd0,2)
kernel /boot/bzImage-2.2.6
boot

zmieff 04-25-2004 04:52 AM

Quote:

title Linux-2.6.6 root (hd0,2) kernel /boot/bzImage-2.2.6 boot
i think "bzImage-2.2.6" is not the right file name

Qucho 04-25-2004 05:07 AM

LOL... you have ways ahead of you... (i am in the attempt #27 of my new kernel :P )

ok.. you compiled to the kernel your filesystes... that is the way to do it...
now.. did you compiled your PCI support in the kernel or as modules ???
what about the partition systems ?? as modules ?
and ... IDE support ??

By the way... if you got the wrong PCI/IDE/etc... devices you might get that problem too.

one last thing !!! dont bother with initrm !!!

debian_dummy 04-25-2004 05:08 AM

and I don't think it would hurt to append root=/dev/hda3 AFTER you correct the wrong image name

jamaas 04-25-2004 05:46 AM

Thanks mate, comments/questions within text!

Quote:

Originally posted by Qucho

LOL... you have ways ahead of you... (i am in the attempt #27 of my new kernel :P )

very comforting!!! :-)

ok.. you compiled to the kernel your filesystes... that is the way to do it...
now.. did you compiled your PCI support in the kernel or as modules ???

I think so but not sure, how do I check? Do you care to wade through my .config file?

what about the partition systems ?? as modules ?
and ... IDE support ??

again I think so, but not sure. I left in a initrd because some the choices in the configure would only compile as modules. Perhaps the kernel will find these modules once it boots? I'm thinking out louc here, is initrd only necessary for moudeles required during boot? Corolory, initrd is not necessary for modules if kernel boots?
By the way... if you got the wrong PCI/IDE/etc... devices you might get that problem too.

one last thing !!! dont bother with initrm !!!


jamaas 04-25-2004 05:53 AM

Have tried this and it didn't seem to matter but will try it again!

Thanks

Jim

Quote:

Originally posted by debian_dummy
and I don't think it would hurt to append root=/dev/hda3 AFTER you correct the wrong image name

jamaas 04-25-2004 05:55 AM

Quote:

Originally posted by zmieff
i think "bzImage-2.2.6" is not the right file name

It should be, have included a list of files in /boot. This is what I changed the name of bzImage file to. Is it critical to form links and have it linked to another filename? Is it imperitive that these files be set to executable?

Thanks

Jim

jamaas 04-25-2004 05:58 AM

oops, forgot to put in list of filenames
 
Quote:

Originally posted by zmieff
i think "bzImage-2.2.6" is not the right file name

./
../
boot.0300
bootfiles
bzImage-2.6.5*
bzImage-2.6.6*
config@
config-2.6.3-4mdk
config-2.6.5
diag1.img
diag2.img
grub/
initrd-2.6.3-4mdk.img*
initrd-2.6.5.img*
initrd-2.6.6.img*
initrd.img@
kernel.h@
kernel.h-2.6.3-4mdk
map
message@
message-graphic
message-text
output
output~
System.map@
System.map-2.6.3-4mdk
us.klt
vmlinuz@
vmlinuz2@
vmlinuz-2.6.3-4mdk
vmlinuz-2.6.5*
vmlinuz.old@

debian_dummy 04-25-2004 06:07 AM

Your menu. lst says 2.2.6 but the image is 2.6.6
Correct, reboot and post results.

jamaas 04-25-2004 06:10 AM

change your name
 
dummy does not suit you.... and I need it!!

Thanks, got it in one! Now I get the kernel panic error thing!

Jim

Qucho 04-25-2004 06:12 AM

ok.. I know that 27 kernels is a little too much... but must people dont need to go so far.. I just dont want any little thing that my kernel does not need on it. ;) now take that and add up that I ma a noob too.. well...

Anyways...
To configure my kernel I use;~$ make xconfig
Is the Qt interface, I can tell you how I do it there, only. :/

a) You can not compile 'in' the kernel if sumting above in the tree is a module. (most of the time)

b) in that interface, a dot means module, a 'check' means IN the kernel.

What you need 'IN' the kernel is;
Your PCI devices. The PCI hub, and anything that leads to 'reading your HD'
Your basic 'filesystem' (ext2, ext3), other fs as NTFS, or vfat can be modules.
Your vid cards (VGA, SVGA, and a specific one 'if' it is listed)
The partition systems (depending what was used to partition your HD's)
Input devices (Keyboard, mice)
Console graphic support.

The rest can be modules.
Compiling this way you dont need a ram disk, so no initrm should be selected. initrd is only necesary for installation disks and stuff like that.

Ram disk is found in the tree:
Device drivers> Block Devices> RAM Disk Support (yes) > Initial RAM Disk (initrd) Support (NO)

Note: make sure that :
Graphics support > Virtual Frame buffer (is a BIG NO) (otherwise you wont see any text at kernel boot)

Qucho 04-25-2004 06:14 AM

Dont edit GRUB menu.lst by hand.
It is easier to type: ~$ update-grub ;) after each new kernel

jamaas 04-25-2004 06:49 AM

will gconfig work ?
 
Thanks for this. So far I've used gconfig, only because I"ve downloaded and installed QT but never got it to work. If my understanding is correct these things should all end up with the same .config file? Perhaps they don't I'll follow your instructions with gconfig... unless you want to help me wrestle with QT. It too is likely somethign simple.

Thanks a bunch BTW. It must be ealy in CO.

JIM


Quote:

Originally posted by Qucho
ok.. I know that 27 kernels is a little too much... but must people dont need to go so far.. I just dont want any little thing that my kernel does not need on it. ;) now take that and add up that I ma a noob too.. well...

Anyways...
To configure my kernel I use;~$ make xconfig
Is the Qt interface, I can tell you how I do it there, only. :/



debian_dummy 04-25-2004 07:21 AM

For fsck sakes, 27 kernels and a newb .. me thinks not ...

jamaas 04-25-2004 07:47 AM

Tried this as best I could and still no luck, kernel panic!

Ideas?

Thanks

Jim



Quote:

Originally posted by Qucho
ok.. I know that 27 kernels is a little too much... but must people dont need to go so far.. I just dont want any little thing that my kernel does not need on it. ;) now take that and add up that I ma a noob too.. well...

Anyways...
To configure my kernel I use;~$ make xconfig
Is the Qt interface, I can tell you how I do it there, only. :/

a) You can not compile 'in' the kernel if sumting above in the tree is a module. (most of the time)

b) in that interface, a dot means module, a 'check' means IN the kernel.

What you need 'IN' the kernel is;
Your PCI devices. The PCI hub, and anything that leads to 'reading your HD'
Your basic 'filesystem' (ext2, ext3), other fs as NTFS, or vfat can be modules.
Your vid cards (VGA, SVGA, and a specific one 'if' it is listed)
The partition systems (depending what was used to partition your HD's)
Input devices (Keyboard, mice)
Console graphic support.

The rest can be modules.
Compiling this way you dont need a ram disk, so no initrm should be selected. initrd is only necesary for installation disks and stuff like that.

Ram disk is found in the tree:
Device drivers> Block Devices> RAM Disk Support (yes) > Initial RAM Disk (initrd) Support (NO)

Note: make sure that :
Graphics support > Virtual Frame buffer (is a BIG NO) (otherwise you wont see any text at kernel boot)



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