I've been working at upgrading my obsolete installation of Slack 8.0 to 8.1 via the download & installation of individual packages, and as the last step I'm compiling kernel v2.4.18.

Attempting to boot to the new kernel however results in a variety of errors shortly after the message SCSI Subsystem Driver Revision: 1.00 is displayed. They are as follows...

request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
<<a variety of normal net, TCP, and IP-related messages removed>>
request_module[block_major_8]: Root fs not mounted
VFS: Cannot open root device "801" or 08:01
Please append a correct "root=" option
Kernel Panic: unable to mount root fs on 08:01

The system in question is a 486DX-2/66, using an Adaptec AHA-1542C.

Kernel configuration for the build includes generic SCSI hard disk, tape, and CD-ROM support, with drivers for specific hardware enabled as modules.

I can boot to the "canned" build of kernel 2.4.5 from 8.0's distro using only generic SCSI support, and do not appear to need to load the module for the 1542C.

I'm re-compiling 2.4.18 with support for the 1542C enabled in the kernel as I type this, but it's going to be a few hours before I will see the results. I thought I'd throw this out to the wolves for feedback in the mean time.


Any insight appreciated!

if the primary storage device's driver is compiled as module then it needs to be in initrd. Please refer to your distro's manual for how to do this (as I've not used Slackware before I cannot provide u exact steps)

well...did you build in all scsi support + support for the file-sys. you're using ?
if not then either recompile or use and initrd.

i believe there's a README.initrd in the /boot dir of your install.

egag

Yes, base SCSI support & appropriate filesystem support is included.

...and I'm definitely not set up to use /dev/initrd. Prior to reading the last two comments I wasn't even aware that it existed.

If she'll behave after the current build-in-progress (with support for the 1542 included in the kernel) completes I'll leave it with that for the time being, but may spend some time reading upon initrd for future builds.

Thanks!

oh....should i need an initrd, i have todo some reading too.
you normally don't need it.

if you've build-in all basic support to mount and read the root partition
you'll be ok.

egag

Works like a charm after re-compiling with support for the 1542 included in the kernel. Thanks for the help!