Also does it matter that the firmware used here indicates it's for 6.9.1 -> 01firmware-6.9.1_1.sfs?
No not really.
I had to use the last Puppy Linux woof-CE kernel-kit produced firmware (fdrv) to assemble 01firmware-6.9.1_1.sfs
. I couldn't get the kernel-kit to produce any usable fdrv
after this version. The fdrv
always shows up at the end around 4000 K and totally useless. Turns out this one works well with the Void Linux 6.10.10_1 kernel.
See speed was the main factor.....I was going to produce this distro in about an hour and a half and use a newer Void Linux kernel extracted during the build process.
Since there is NO reliable program/script that filters down the size of the complete firmware collection I went with the much smaller fdrv
converted manually to 01firmware
, and not try to manually pick out what firmware where.
You can use the 01firmware.sfs
as an uncompressed (un-squashed) directory and boot the system that way. Makes it much easier to work with. Like adding firmware to it and immediately testing it without having to squash it again.
Show me what to add and I will assemble another 01firmware.sfs
if in doubt.
My main dev machine is a Dell PowerEdge rack server.......horrible graphics card....since it's an industrial grade rack server which is designed to run 99% of the time headless, it doesn't need anything but 1280x1024 and ASCII so it's outfitted with MATOX graphics card.....many Puppy Linux fdrv's do not contain any firmware for it. So When I am making stuff...graphics always has to be tested on some other machine.