SCSI kernels
July 22, 2008 —
BarryK
I went to a Slackware download site to obtain kernel .config files for Slackware's "SCSI kernels". Surprise, Slackware stopped providing these at version 11.0. Up to and including 11.0, Slackware provided four kernels, named "adaptec", "scsi", "scsi1" and "scsi2", with different groups of SCSI drivers built in. There are various reasons for this:
1. Having SCSI drivers builtin rather than modules makes it easier to boot from a SCSI drive.
2. All SCSI drives are not builtin to one kernel as the kernel can become confused at bootup and there will be a "kernel panic".
3. All SCSI drives are not builtin to one kernel as the kernel would become very big.
Anyway, I have created three SCSI kernels for Puppy 4.1, with the 2.6.25.11 kernel. I have named them "scsi1", "scsi2" and "scsi3". The first is almost the same as the Slackware "adaptec" kernel, the second close to the Slackware "scsi" kernel, and all left-over SCSI drivers are in my "scsi3" kernel.
The idea is that when I or someone else wants to boot Puppy off a SCSI drive, you just pop in the right kernel.
So, I had better document how each is configured:
SCSI1
CONFIG_SCSI_AHA152X=y
CONFIG_SCSI_AHA1542=y
CONFIG_SCSI_AHA1740=y
CONFIG_SCSI_AACRAID=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_SCSI_AIC79XX=y
CONFIG_SCSI_AIC94XX=y
CONFIG_SCSI_DPT_I2O=y
CONFIG_SCSI_GENERIC_NCR5380=y
CONFIG_SCSI_GENERIC_NCR5380_MMIO=y
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_NCR53C406A=y
SCSI2
CONFIG_SCSI_EATA=y
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_GENERIC_NCR5380=y
CONFIG_SCSI_GENERIC_NCR5380_MMIO=y
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_INITIO=y
CONFIG_SCSI_INIA100=y
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_QLOGIC_FAS=y
CONFIG_SCSI_QLOGIC_1280=y
CONFIG_SCSI_QLA_FC=y
CONFIG_SCSI_QLA_ISCSI=y
CONFIG_SCSI_SIM710=y
SCSI3
CONFIG_SCSI_3W_9XXX=y
CONFIG_SCSI_7000FASST=y
CONFIG_SCSI_ACARD=y
CONFIG_SCSI_ADVANSYS=y
CONFIG_SCSI_IN2000=y
CONFIG_SCSI_ARCMSR=y
CONFIG_SCSI_HPTIOP=y
CONFIG_SCSI_BUSLOGIC=y
CONFIG_SCSI_DMX3191D=y
CONFIG_SCSI_DTC3280=y
CONFIG_SCSI_FUTURE_DOMAIN=y
CONFIG_SCSI_GDTH=y
CONFIG_SCSI_GENERIC_NCR5380=y
CONFIG_SCSI_GENERIC_NCR5380_MMIO=y
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_IPS=y
CONFIG_SCSI_INITIO=y
CONFIG_SCSI_INIA100=y
CONFIG_SCSI_NCR53C406A=y
CONFIG_SCSI_STEX=y
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_PAS16=y
CONFIG_SCSI_SIM710=y
CONFIG_SCSI_SYM53C416=y
CONFIG_SCSI_DC395x=y
CONFIG_SCSI_DC390T=y
CONFIG_SCSI_T128=y
CONFIG_SCSI_U14_34F=y
CONFIG_SCSI_ULTRASTOR=y
Comments
Here we goUsername: cthisbear
This will be like too many candles on the cake for Sage. Surely it is not April Fools Day again? I'll have to check my calender. Chris
SCSI support
Username: dogone
"I'm no doubt in the minority, but I still have two serviceable SCSI scanners, a Microtek E6 and an HP Photo scanner (film, slides and prints). These devices are still usable under most large Linux distros. I don't look forward to the day they or Puppy drop SCSI support. Would it be too self-centered to suggest that legacy Adaptech (2940 family) support never be abandoned? Surely such limited support could always be justified.
Alleluhia!
Username: ANOSage
"C'est magnifique, merci beaucoup. Instructions already committed to hard copy as well as FDD! Excuse me while I blow dust off boxloads of HW and recover my professional scanner from the loft.
SCSI hard drives waiting
Username: ChiJoan
"I've got SCSI controllers, hard drives, and CD-RW to learn about. Maybe I won't have to buy that SATA PCI-X controller for the $20.00 Intel Xeon server board I found and need CPUs for yet. Amazing what they recycle these days, and thanks to Linux I can reuse it in another old Gateway 2000 full tower case. Wonder if Puppy will pick-up the USB sound card when I get it...there are no PCI slots on this board. Thanks guys and gals for all your hard work. ChiJoan
Tags: puppy