According to Brad Bonkoski: While burning my CPU.
> 
> you might want to rey making a boot disk and a root disk and botting the
> machine with the flopies and then running a manual fsck to check the file
> structure of the partition you are trying to mount root on.  When that
> file system is messed up you will usually not be able to mount root on
> there and the kernel will 'panic'
> so try that
> -Brad

Bootdisk No, simply because ZipSlack is a UMSDOS system.

The kernel panic is because loadlin cant find the partition where the
filesystem is located on, "root" does not get mounted on the filesystem, 
root = "/" "rootfilesystem".

Ray Olszewski <[EMAIL PROTECTED]> explaned what the problem was and HOWTO
solve it.

> 
> On Mon, 15 Feb 1999, gene hitz wrote:
> 
> > I wrote to the list a few weeks ago. I'm the newbie who wanted to know
> > how to get started with Linux. I received many helpful responses from
> > the group and finally decided to try the Slackware version. I
> > downloaded the 35,663 Kb zipfile and unzipped it into a new clean
> > partition and wound up with 15 directories containing 10,989 files. I
> > tried following the readme.1st file unsuccessfully. In DOS, I tried
> > "loadlin vmlinuz root=/dev/sda4 rw" and after several pages of
> > installation I got the message, "vfs: cannot open root device 0804"
> > and "kernel panic: vfs: unable to mount root fs on 0804", and the
> > machine locked-up. When I next tried "loadlin vmlinuz root=/dev/hda1
> > rw" it answered "unable to open initial console" What am I doing wrong
> > and how do I proceed?
> > Gene Hitz  --  [EMAIL PROTECTED]
> > 
> > _________________________________________________________
> > DO YOU YAHOO!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Reply via email to