View previous topic :: View next topic |
Author |
Message |
plainsane1982 n00b
Joined: 22 Nov 2004 Posts: 9 Location: cologne, germany
|
Posted: Mon Nov 22, 2004 2:46 am Post subject: |
|
|
well thanks alot billybob, because after re-checking the menuconfig i noticed the Silicon Image S-ata driver was only compiled as module, not built-in (must have made a mistake their before)
It now boots! no more panic
Satisfies me after 14 hours of sitting behind this damn machine, now i can get some well deserved sleep. _________________ don't drink and drive, you might spill your beer |
|
Back to top |
|
|
epohs n00b
Joined: 27 Aug 2004 Posts: 51
|
Posted: Mon Nov 22, 2004 10:53 pm Post subject: |
|
|
Billybob wrote: | Try /dev/hda*
It looks like (since you're using (hd0,0)) that you only have 1 harddrive and may have misread /dev/hda in the guide as /dev/hde
but I dunno. Also e seems pretty high up there, how many harddrives do you have? |
I have two hard drives, hde and hdf. i'm fairly certain it is hde, although it really through me for a loop at first. |
|
Back to top |
|
|
epohs n00b
Joined: 27 Aug 2004 Posts: 51
|
Posted: Tue Nov 23, 2004 3:40 am Post subject: |
|
|
ok, so i rebuilt & reinstalled my kernel following the handbook. then when i typed reboot i got the following error: Code: | WARNING: could not determine runlevel - doing soft reboot
(It's better to use shutdown instead of reboot from the command line)
init: /dev/initctl: no such file or directory |
could this point to some other problem? |
|
Back to top |
|
|
ferdi_h n00b
Joined: 29 Feb 2004 Posts: 8
|
Posted: Tue Nov 23, 2004 11:18 am Post subject: |
|
|
I've had the same problems when trying to manually configure the gentoo-dev 2.6.9 kernel.
First I tried to do it from scratch (following the handbook instructions) and got the "unknown filesytem" error (both with reiserfs and (after reformatting the partition and installing Gentoo again) ext3 as filesystems). Next, I used the MEPIS generated .config file from my working kernel 2.6.7 Debian install to generate a gentoo-dev kernel, but got the same errors.
In the end I emerged the 2.4.26 kernel and used the genkernel script. Now everything works fine. So maybe it's a kernel 2.6 problem? I've read other posts on the internet regarding this problem and in some cases, moving back to kernel 2.4 solved the problem, as it did for me. But I don't think it's an ideal situation. I'll keep trying to get a working 2.6 kernel, but at least I've got something to fall back on now. |
|
Back to top |
|
|
Joschi n00b
Joined: 24 Nov 2004 Posts: 1
|
Posted: Wed Nov 24, 2004 3:06 am Post subject: |
|
|
I had this problem for a long time and after quite some time of "try & error" , i recompiled my kernel (2.6.8 ) In: file systems -> Partition Types:
i activated the options for PC BIOS (MSDOS partition tables) support with all the sub-options that appeared and the Windows Logical Disk Manager to be compiled into the kernel. Suddenly my Kernel was able to boot from ext3.
I hope this will help some of you.
P.S.: Don't forget to compile Generic IDE support into the kernel, i had this problem once and it took me quite some time to solve it... |
|
Back to top |
|
|
epohs n00b
Joined: 27 Aug 2004 Posts: 51
|
Posted: Wed Nov 24, 2004 3:30 am Post subject: |
|
|
thanks for the suggestions, i'll give it a go. |
|
Back to top |
|
|
slycordinator Advocate
Joined: 31 Jan 2004 Posts: 3065 Location: Korea
|
Posted: Wed Nov 24, 2004 4:15 am Post subject: |
|
|
plainsane1982 wrote: | I have a very simmilar problem
Code: | VFS: Cannot open root deice "hde9" or unknown-block (0,0) please append a correct "root=" boot option
Kernel panic - not syncing: VFS: unable to mount root fs on unknown block (0,0) |
is what i get
My machine:
athlon-xp 2500+
abit AN7 mobo (nforce2 chipset)
S-ATA drive 160GB (samsung sp1614c)
Silicon Immage S-ATA controller
/dev/hde7 is /boot with ext3 formatted
/dev/hde9 is / with XFS formatted
I am sure that the entry regarding XFS support in the makeconfig was correct
i'll be glad to provide any other info to help solve this problem |
In your grub.conf file try changing /dev/hde to /dev/sda. If you're using a 2.6 kernel and SATA drive will almost always be /dev/sda and if you're using a 2.4 kernel then the drive will be registered differently depending on which SATA-related driver you use. |
|
Back to top |
|
|
|