Get them from here:
Comments:Posted on 28 Jul 2008, 2:58 by ANOSage
I see the kernel files - thank you. Please recall many confessions that I don't do software! Frankly, I would need a very long recipe list of detailed instructions. I have Symbios, Initio, Adaptec, Advansys and CMD cards lurking around here somewhere. It is going to be a non-trivial exercise just setting up the HW, but I'm game for it, with a lot of help with the SW, please. Results are not going to be reported overnight, though, as I live a very full to overflowing lifestyle of which this aspect is only a very tiny portion. Blogging takes minutes, setting up takes days/weeks.
Posted on 28 Jul 2008, 3:01 by linuxcbon
scsi and analog modems
My opinion is that scsi and analog modems should not be in the main puppy version. But they can be made as add-ons.
Posted on 28 Jul 2008, 8:45 by BarryK
I'll be getting onto testing booting from SCSI sometime, as Aitch and an Aussie-person-who-prefers-to-remain-anonymous have given me lots of hardware. I need to decide what PC can be the guinea pig, and I have to find some spare table space...
Posted on 28 Jul 2008, 8:10 by Sit Heel Speak
Needs different initrd?
I must've missed something. I presume the idea is, at this point, we can try the scsi(n)-k126.96.36.199 kernel as a drop-in replacement for the k188.8.131.52 kernel in Puppy 4.1-alpha-4.
But...attempting to do so, on a USB stick, WakePup boot floppy, Adaptec 39160 PCI scsi adapter with 3 disks on it, plus 2 ATA100 disks...with scsi-1 renamed to vmlinuz, all other parts of 4.1-alpha-4 left alone...I see a message
Unlzmaing Linux... done.
Booting the kernel.
but then after "Searching for Puppy files (etc.)" it freezes at "can't find pup_404.sfs"
The original k184.108.40.206 in 4.1-alpha-4, renamed back to vmlinuz and rebooted via WakePup, gives the usual
Booting the kernel
messages and proceeds to boot normally.
Is there an initrd.gz image I need, as well as the new kernel?
Posted on 28 Jul 2008, 17:22 by BarryK
Re: Booting SCSI
No, you have to wait until 4.1alpha5 is released, based on the 220.127.116.11 kernel.
I don't yet know if there are any 'gotchas' in the initrd. I will be uploading 4.1alpha5, then hopefully not too long after that I'll put together a SCSI PC -- or attempt to -- and find out if it'll boot.
The main problem in your test, maybe the only problem, is that the initrd has usb, squashfs, etc kernel drivers in it which are for the 18.104.22.168 kernel, so they would have failed to load.
So, it may be that when 4.1alpha5 is released, you can try without waiting for me and it might just work.
Posted on 28 Jul 2008, 18:13 by ANOSage
Booting with scsi...
...really is the only remaining issue. The big question remains how cards with and without their own intercept BIOSes will behave. Adaptec cards have a plethora of options, but the rest are somewhat sparse in this respect.
Posted on 31 Jul 2008, 10:55 by Aitch
I was just answering a query about this & by chance did a quick search, and was surprised to see this
Is there any documentation about this/what you have done/what you have tested/got working?
Which one should I use for my tekram dc 395uw or my aha 2940uw, both scsi3 [68p]
Is there a different kernel for 50p scsi1/2 cards?
How to replace a kernel anyhow?
@SHS keep me posted on this please
Posted on 31 Jul 2008, 17:36 by BarryK
Replace with SCSI kernel
If you have Puppy installed to a writable media, such as USB drive, Zip drive or hard drive, then you can replace the kernel vmlinuz with a SCSI one.
Or, it is possible to edit the puppy-xxx.iso file using ISOmaster and replace the vmlinuz, then burn to CD.
You also need to see my earlier post about what is in the SCSI1, SCSI2 and SCSI3 kernels.
I have not yet put any SCSI hrdware together.