[Peeweelinux] Kernel Panic

[Correy Edmed]

Hi Troy and Adi and Ricardo and Leif and PWL archive

**********************************************************************
Target System = PCM-3350 GX1 300MHz
Developement PC = Redhat 6.2 with all the rpm's installed as specified 
in Reference
**********************************************************************

Troy has helped me so far with this problem but I noticed in the 
peewelinux archives that you all seem to know a bit in this area so any 
help you can give me would be much appreciated.

Thankyou for your answer Troy (attached at bottom) I have another CF 
that is branded Sandisk Ultra 256M compact flash. That I tried instead 
of the Kodac 128M CF

I have recompiled the kernel and made sure that all of the filesystems 
including ext2 fat16 and all the other ones are compiled in and not only 
as modules.

The things that I notice as fishy are

when PWL configures it it creates 3 partitions

Partition        Contents
hdc1               boot.b    bzImage    initrd    map
hdc2                bin    boot     dev    etc    lib    mnt    proc    
rc.init    root    sbin    tmp    usr    var
hdc3                **Is there but I can't mount it and no documentation 
about formating it during target install**

I then have a look at /etc/lilo.conf and find the following which seems 
really wacky so I have included the lines that I changed in bold
*********************************
disk=/dev/sda    *disk=/dev/hdc*
    bios=0x80
    heads=4
    sectors=32
    cylinders=490

boot=/dev/sda        *disk=/dev/hdc*
map=/boot/map
install=/boot/boot.b
compact
prompt
timeout=20
default=linux

image=/boot/bzImage-ipx    *image=/boot/bzImage*
    label=linux
    read-only
    root=/dev/hda1                *root=/dev/hdc2*
    vga=0x317
***************************************
However i don't even think it is accessing this file yet.

After these changes (new kernel, updated lilo.conf file) I get the same 
errors as before (ioctl) plus more errors I am thinking because of all 
the extra file systems I built into the kernel that try and recognise it 
but fail.
I have tried using the kernels supplied with pwl such as bzImage-full 
and selecting modules but no go there either.

Incase some more of the errors being produced would be helpful here they 
are:

*********************************************
Partition check:
hdc: hdc1 hdc2 hdc3
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Copying filesystem /dev/hda2 to /dev/ram2.....
/dev/hda2Flushing buffers to disk....
tcsetpgrp: Inappropriate ioctl for device
Invalid session number or type of track
Kernel panic: VFS: Unable to mount root fs on 01:02
*********************************************

I am able to get it to work when I use a Compressed ramdisk on ext2 
partition however that is not practical because it installs it all on 
hdc1 with no other partitions. I need it Uncompressed on ext2 partition 
so that I can write data to the hdc2 partition.

Do you know what hdc3 is used for is it meant to be a swap or something? 
I tried partitioning it,(mke2fs) so that I could mount it and everything 
however to no avail at bootup.

I have been reading the Bootdisk HOWTO and they have this error under 
their troubleshooting and say there is only a few problems here and to 
check the rdev -R on /dev/hdc1/bzImage. I followed through this 
possibility but it did nothing.

Apparently you can look up what device 01:02 is in the format XX:YY in 
/usr/src/linux/Documentation/devices.txt however I didn't understand this.

Thankyou for any help you can give me,  I will document any successful 
help I am given in my writeup.

Correy


Troy Engel wrote:

>Hiya,
>
>Correy Edmed said:
>  
>
>>tcsetpgrp: Inappropriate ioctl for device
>>kernel panic: VFS: Unable to mount root fs on 01:02
>>    
>>
>
>I saw this thread, but I'm not part of it I think? In any case, I'll try
>to help...
>
>  
>
>>/dev/hda2Flushing buffers to disk....
>>tcsetpgrp: Inappropriate ioctl for device
>>Kernel panic: VFS: Unable to mount root fs on 01:02
>>    
>>
>
>This smells like a CF error, or something in the subsystem like that. Do
>you have any other flash chips to try and use, besides this one? Likewise,
>do you have a different CF reader/writer to try?
>
>Under normal circumstances, this is the kind of error I would expect when
>trying to mount a bad disk (or possibly a disk with a filesystem the
>kernel doesn't have compiled in? like Sun or SGI disk, etc)
>
>Hope that helps some....
>-te
>
>  
>