Hello -

Hardware: Pentium 1 @ 166 MHz, 512M on a Tyan 1562 motherboard.

Slackware Linux 10.2 is based on the 2.4.31 kernel.

Windows 98SE sees the SCSI interface as: io=0x130, irq=11, DMA=6 and it works well in that environment (it runs a SCSI ZIP drive). These resources are dedicated to the 1542CF. The BIOS has these resources set as "Legacy ISA".

Installed Slackware 10.2 using the precompiled scsi.i kernel which advertises module-style support for the AHA1542CF interface. The installation was done to a second EIDE 8 GB drive. Smooth installation.. just dropped in.

The AHA1542 is not seen at boot.

After some reading, a ..manual.. module install as root was attempted using modprobe:

bash-3.00# modprobe aha1542
/lib/modules/2.4.31/kernel/drivers/scsi/aha1542.o.gz: init_module: No such device
/lib/modules/2.4.31/kernel/drivers/scsi/aha1542.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.31/kernel/drivers/scsi/aha1542.o.gz: insmod /lib/modules/2.4.31/kernel/drivers/scsi/aha1542.o.gz failed

No success with "modprobe aha1542 0x130". "modprobe aha1542 io=0x130" produces a message that the parameter is not recognized.

I didn't see any particular revealing comments in syslog or dmesg.

This interface *did* work 100% no problems with Slackware 8.1 (Kernel 2.2?) . That it does not with 10.2 (Kernel 2.4.31) was a surprise.

On a whim, the modprobe line in /etc/rc.d/rc.modules was uncommented.. andthe same error message appears.

Your time *is* appreciated.

Mark

I believe that you need to run make menuconfig, select the Adaptec 154x devices specifically, and then recompile the kernel. You may has well compile the support into the kernel rather than have it as a module.

Hello Stress_Junkie -

And I was just about to post a follow-up to my first note and saw yours.

Here's the solution I found:

remove /etc/modules.conf

I didn't believe it. But reading through the various man pages, info-pages, and Linux How To's, it seems that modules.conf must be properly populated before modprobe will Do The Right Thing.

It is also documented that if /etc/modules.conf isn't there then modprobe assumes a default behavior that ..just.. happens to work.

Next up: I'll recompile the kernel to get rid of the unnecessary drivers and such and see how well that goes.

Now.. why doesn't eject -s /dev/sda really eject a ZIP platter? The drive ..sounds.. like it's going to eject.. but doesn't seem to make it all the way.

Regards,

Mark

I'll have to remember that about removing modules.conf. There's always something new to learn.