| 1 |
On Monday 19 November 2007 12:35:14 am Billy Holmes wrote: |
| 2 |
> Jeff Cranmer wrote: |
| 3 |
> > Cannot open root device "sda3" or unknown block (0,0) |
| 4 |
> > Please append a correct "root=" boot option. |
| 5 |
> > Here are the available partitions |
| 6 |
> |
| 7 |
> run "make menuconfig" in your new kernel dir. |
| 8 |
> |
| 9 |
> check to ensure ext3 is compiled in. (not sure why it wouldn't be) |
| 10 |
|
| 11 |
ext3 journalling file system support, ext3 extended attributes and ext3 posix |
| 12 |
access control lists are all compiled into the kernel. |
| 13 |
> |
| 14 |
> check to make sure you've got udev or devfs installed properly in both |
| 15 |
> kernels (maybe one isn't defined in the kernel, and the old kernel had |
| 16 |
> it). I'd really try to ensure you're running udev and not devfs, but |
| 17 |
> first things first. |
| 18 |
> |
| 19 |
> IF SATA: |
| 20 |
> Make sure the proper SATA options are the same for each kernel. There's |
| 21 |
> one SATA option that isn't compatible with another SATA option. (it |
| 22 |
> could be fixed in newer kernels by now) |
| 23 |
> |
| 24 |
|
| 25 |
From dmesg for the current working kernel, I worked out that the drive which |
| 26 |
it is having trouble finding is a serial ATA drive, running the sata_nv |
| 27 |
driver. |
| 28 |
|
| 29 |
Vendor: ATA Model: WDC WD2500JS-60N Rev: 10.0 |
| 30 |
Type: Direct-Access ANSI SCSI revision: 05 |
| 31 |
|
| 32 |
I disabled all the SATA drivers except for the nvidia one, and have made some |
| 33 |
progress. |
| 34 |
|
| 35 |
The kernel now finds the drive, but for some reason puts a little 8MB drive at |
| 36 |
sda, and populates the 'real' 250MB drive at sdb, so the kernel still panics |
| 37 |
(probably due to fstab wanting to see the main drive at sda, not sdb). |
| 38 |
|
| 39 |
I'd like to get a log of this, but dmesg only shows the log of the kernel that |
| 40 |
boots. Does anyone have any suggestions of how to get at the log for a |
| 41 |
panicking kernel, or have any suggestions on how to fix this. I suspect the |
| 42 |
I may be able to play with fstab and get the new kernel to boot, but I'm |
| 43 |
loath to do this, as that will most likely break the kernel that is working, |
| 44 |
so if it doesn't simultaneously fix the non-working kernel, I'm toast. |
| 45 |
|
| 46 |
Any suggestions gratefully received. |
| 47 |
|
| 48 |
------------------------------------------------------- |
| 49 |
-- |
| 50 |
gentoo-user@g.o mailing list |
Archives