Slacko 5.3.3-4g SCSI full , fresh install (no pets) on....
Processor AMD Athlon(tm) 64 Processor 3200+ Memory 967MB (94MB used).
....is not auto loading module for AIC-7850 according to pupscan:
DESCRIPTION: SCSI storage controller: Adaptec AIC-7850
VENDOR: 9004 DEVICE: 5078
sg not loaded either per pupscan and "modprobe sg"
Xsane .997 wants both. (sane-find-scanner comes up empty).
same hardware system running 4.3.1 scsi intel modems (with Xsane) works fine for Scanjet 4c SCSI scanner. ditto for win XP Sp3 and built-in scanner wizard.
could use 4.3.1 with XVESA video but would rather have slacko
with radeon driver and other niceties. wondering if AIC-7850 was trimmed out for this release. can you point me to relevant log files .rc files, firmware or whatever to check further ?
thanks in advance
5.3.3 Slacko SCSI modules not loading
For some reason those modules were not copied in to the build at the woof stage, I don't know why but I am investigating a possible woof bug.
try the attached pet, let me know if it works. Probably best to run "depmod" then reboot. Hopefully they will then load automatically if your scanner is connected.
try the attached pet, let me know if it works. Probably best to run "depmod" then reboot. Hopefully they will then load automatically if your scanner is connected.
Puppy Linux Blog - contact me for access
Pet fixed it! Tks to 01micko
Tks to you 01 micko. Followed your advice above, with these hints for noob like me:
1. clicked the download, accepted the offer to use petget to handle.
2. ran "depmod" with no args
3. rebooted and checked pupscan interfaces and voila, two relevant AIC-7xxx drivers loaded. I checked /root/.packages and found the modules_scsi_*******.files file with contents below
/lib/
/lib/modules/
/lib/modules/3.1.10-slacko_4gA/
/lib/modules/3.1.10-slacko_4gA/kernel/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/sg.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic94xx/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic94xx/aic94xx.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx_old.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/aic7xxx.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/aic79xx.ko
Can i assume i saw two entries for the aic7xxx b/c both the bolded above got auto-loaded?
any rate, works with Xsane on both machines. Then I applied the PPM bugfix and things are happy for a friday afternoon.
Tks to you and all who work so hard. linux is still a second language but, I have a dream...!
1. clicked the download, accepted the offer to use petget to handle.
2. ran "depmod" with no args
3. rebooted and checked pupscan interfaces and voila, two relevant AIC-7xxx drivers loaded. I checked /root/.packages and found the modules_scsi_*******.files file with contents below
/lib/
/lib/modules/
/lib/modules/3.1.10-slacko_4gA/
/lib/modules/3.1.10-slacko_4gA/kernel/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/sg.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic94xx/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic94xx/aic94xx.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx_old.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/aic7xxx.ko
/lib/modules/3.1.10-slacko_4gA/kernel/drivers/scsi/aic7xxx/aic79xx.ko
Can i assume i saw two entries for the aic7xxx b/c both the bolded above got auto-loaded?
any rate, works with Xsane on both machines. Then I applied the PPM bugfix and things are happy for a friday afternoon.
Tks to you and all who work so hard. linux is still a second language but, I have a dream...!
Ok, cool, glad it works and incidentally I found the woof bug which causes this.
I have selected the choice in woof where you can boot from scsi devices. This reportedly works (IIRC forum member Aitch on an old server box). What happens is that ALL scsi drivers get moved to the initrd.gz, which is a mistake, I believe, for devices that have nothing to do with booting, eg scanners.
I'll report this to Barry.
Thanks.
I have selected the choice in woof where you can boot from scsi devices. This reportedly works (IIRC forum member Aitch on an old server box). What happens is that ALL scsi drivers get moved to the initrd.gz, which is a mistake, I believe, for devices that have nothing to do with booting, eg scanners.
I'll report this to Barry.
Thanks.
Puppy Linux Blog - contact me for access
Normally the drivers get copied into the partition or save file.01micko wrote:Ok, cool, glad it works and incidentally I found the woof bug which causes this.
I have selected the choice in woof where you can boot from scsi devices. This reportedly works (IIRC forum member Aitch on an old server box). What happens is that ALL scsi drivers get moved to the initrd.gz, which is a mistake, I believe, for devices that have nothing to do with booting, eg scanners.
I'll report this to Barry.
Thanks.
But if you make a PUPMODE=2-full install manually bypassing the installer you might forget to open initrd.gz to fetch the drivers from there .
That part seems broken in the init script for frugals. Only /lib/modules/3.2.22-4g/kernel/drivers/scsi/imm.ko and ppa.ko get copied, sg.ko is supposed to get copied too, but doesn't.Karl Godt wrote: Normally the drivers get copied into the partition or save file.
Puppy Linux Blog - contact me for access
Happy Birthday, then!
This is older code from Puppy 430 (last three lines of the intro comments for the version):
Here they get moved :
Could think of PUPMODE mismatch or aufs whipeouts.
This is older code from Puppy 430 (last three lines of the intro comments for the version):
Code: Select all
#v424 whiteout processing for aufs2 fixed.
#v426 pkeys=de caused failure to boot from vfat partition.
#v426 record of layers needs to include zdrv.
Code: Select all
#the initrd does have some modules, move them to the main layered f.s...
#v4.02 moved this up. had it down after the the unionfs setup (just want it same place as the above code).
[ ! -d /pup_rw/lib/modules/$KERNELVER/initrd ] && [ ! -d /pup_ro1/lib/modules/$KERNELVER/initrd ] && REASON="new"
if [ "$REASON" != "" ];then
mkdir -p /pup_rw/lib/modules/$KERNELVER #PUPMODE=5, this dir not exist.
mv /lib/modules/$KERNELVER /pup_rw/lib/modules/$KERNELVER/initrd
rm -f /pup_rw/lib/modules/$KERNELVER/initrd/modules.*
sync
#note: /etc/rc.d/rc.sysinit will detect them and run depmod.
fi
#v3.91 a humongous initrd may have zdrv file...
[ -f /${ZDRVSFS} ] && [ ! -f /pup_rw/${ZDRVSFS} ] && [ ! -f /pup_ro1/${ZDRVSFS} ] && cp -a /${ZDRVSFS} /pup_rw/
fi