2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1

2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1

[Henrik Storner]

I installed 2.6.0-test1 this afternoon, and was quite pleased that it
could burn some cd's without the trouble I'd had with ide-scsi.

So I know 2.6.0-test1 works for me. But 2.6.0-test2 with the same
configuration (just a "make oldconfig" in between) stops during boot
with:

VFS: Cannot open root device "NULL" or sda1
Please append a correct "root=" boot option
Kernel panic: Unable to mount root fs on sda1

I have LILO on /dev/hda, and the root fs on /dev/sda1.  Adding a
"root=/dev/sda1" at the LILO: prompt doesn't change anything.


Henrik
-- 
Henrik Storner <henrik@hswn.dk> 

Re: 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1

[Yifang Dai]

On Sun, Jul 27, 2003 at 08:42:13PM +0000, Henrik Storner wrote:
> So I know 2.6.0-test1 works for me. But 2.6.0-test2 with the same
> configuration (just a "make oldconfig" in between) stops during boot
> with:
> 
> VFS: Cannot open root device "NULL" or sda1
> Please append a correct "root=" boot option
> Kernel panic: Unable to mount root fs on sda1
> 

I've got the same error, except my root device is /dev/hda3. It also
worked in 2.6.0-test1 :)

-- 
Yifang Dai		 |
eFax: (847)628-0255      |    Debian GNU/Linux
yifang_dai@yahoo.com     |    

Re: 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1

[gaxt]

Yifang Dai wrote:
> On Sun, Jul 27, 2003 at 08:42:13PM +0000, Henrik Storner wrote:
> 
>>So I know 2.6.0-test1 works for me. But 2.6.0-test2 with the same
>>configuration (just a "make oldconfig" in between) stops during boot
>>with:
>>
>>VFS: Cannot open root device "NULL" or sda1
>>Please append a correct "root=" boot option
>>Kernel panic: Unable to mount root fs on sda1
>>
> 
> 
> I've got the same error, except my root device is /dev/hda3. It also
> worked in 2.6.0-test1 :)
> 

I believe you need to change in your grub.conf file the root=/dev/hda3 
to a root=### ie root=0307

The number is composed of 3 pieces

(a) major device number ie. 3 above (leading zero is ignored)
(b) minor device number ie. 0 above
(c) partition on device ie. 7 above

I use hdb. hda and hdb are both major device number 3

hda is minor device number 0
hdb is minor device number 64
BUT minor device number is in base 16
so in base 16, hda is 0 (0x16=0) and hdb is 4 (4x16=64)

THUS

my root=/dev/hdb4 becomes root=344 (ie. maj device 3, minor device 64 
(4x16) and partition #4.

Examples:

hda1 = 301
hda3 = 303
hdb1 = 341
hdb4 = 344 etc.

Pardon if this is obvious. To determine linux device numbers, google. 
there's a list out there. I found a list below:

http://www.lanana.org/docs/device-list/devices.txt

Re: 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1

[Henrik Storner]

In <3F24A548.2040202@rogers.com> gaxt <gaxt@rogers.com> writes:

>Yifang Dai wrote:
>> On Sun, Jul 27, 2003 at 08:42:13PM +0000, Henrik Storner wrote:
>> 
>>>So I know 2.6.0-test1 works for me. But 2.6.0-test2 with the same
>>>configuration (just a "make oldconfig" in between) stops during boot
>>>with:
>>>
>>>VFS: Cannot open root device "NULL" or sda1
>>
>> I've got the same error, except my root device is /dev/hda3. It also
>> worked in 2.6.0-test1 :)

>I believe you need to change in your grub.conf file the root=/dev/hda3 
>to a root=### ie root=0307

Doesn't seem to do much good here. I've tried:

root=/dev/sda1
root=0801
root=801
root=2049         (0801 hex = 2049 decimal)
root=08:01
root=/dev/sda/1

but none of them gets the kernel to mount the root fs (yes, I do
have the SCSI driver and my reiserfs filesystem compiled in).

Anyone who added patches to -test2 who have a clue about what
is going on ?


Henrik
-- 
Henrik Storner <henrik@hswn.dk> 

Re: 2.6.0-test2 - Strange Terminal Problems- Gramofile

[gaxt]

in 260-test1-mm2-O8+O9 gramofile worked fine

in 260-test2 gramofile loads but when you press on "start recording" 
where you are supposed to get an ASCII equalizer changing with the music 
input, you get a blank screen. Same in an xterm as in a virtual terminal.

Re: 2.6.0-test2 - Strange Terminal Problems- Gramofile UPDATE - Scheduler?

[gaxt]

gaxt wrote:
> in 260-test1-mm2-O8+O9 gramofile worked fine
> 
> in 260-test2 gramofile loads but when you press on "start recording" 
> where you are supposed to get an ASCII equalizer changing with the music 
> input, you get a blank screen. Same in an xterm as in a virtual terminal.
> 

Hm. Well, closing down Wine (running Galciv) seems to have resolved the 
problem for some reason. Scheduler problems???