Actually, peterw, your previous post provides a clue as to what the CURRENT problem may be, that is the absence of required firmware (and perhaps drivers). One of its links leads to this quote:
'It's over my head, but see if this works:
"Code: Select all
sudo cp '/lib/firmware/brcm/brcmfmac43455-sdio.MINIX-NEO Z83-4.txt' '/lib/firmware/brcm/brcmfmac43455-sdio.MINIX TECH NOLOGY LIMITED-Z83-4A.txt'
Reboot"'
But let me make sure wmmiller understands what's going on.
For a technical explanation read, How Puppys Work, https://www.forum.puppylinux.com/viewtopic.php?t=5818 and How Puppys Save Works, https://www.forum.puppylinux.com/viewtopic.php?t=6526. The following is a layman understanding of those:
Puppys are modularly built. On boot-up they copy into RAM READ-ONLy file-systems that were included in the ISO. On shutdown you're offered the opportunity to create a SaveFolder (must be on a Linux Formatted Partition)* or a SaveFile (can be on any writable partition)*, and unless and until you create a Save will always be offered that option on reboot Shutdown. A Save is used to preserve settings, customizations and user-installed applications. Once created it will be mounted on boot-up so that its contents are part of your 'operating-system-in-RAM'.
Among the file-systems contained in the ISO are the kernel (vmlinuz) and a zdrv.sfs. The latter contains drivers compiled against that kernel. The zdrv.sfs for Bionicpup64 is named zdrv_bionicpup64_8.0.sfs. Sometimes a Puppy's creator also includes firmware in the zdrv.sfs. To make use of a wifi-adapter, both drivers and firmware must be present. Firmware, however, does not have to be compiled against a kernel. Once you have the needed firmware it can be used with any kernel by installing it (and Saving) or by placing a properly (re)named fdrv.sfs adjacent to the vmlinuz so that it will be copied into RAM on boot-up.
[Once you have A right vmlinuz, zdrv.sfs and fdrv.sfs, they can be swapped into a different Puppy (replacing the 'old') by merely renaming them: i.e., a zdrv.sfs for fossapup64_9.5 must have the name zdrv_fossapup64_9.5.sfs. Caution: the internal structure of some newer Puppys has changed complicating this. But the aforementioned files-systems for Bionicpup64 and fossapup64 are interchangeable].
In the post on the Linux Mint forum, the OP was using the 5.4.0-121-generic Kernel. To obtain wifi he only had to install the needed firmware. That is, the 5.4.0-121 kernel included the necessary drivers. If I recall correctly, Bionicpup64's ISO included a 4.9-something kernel (vmlinuz) and drivers compiled against it (zdrv). Hopefully, still all that may be missing is the necessary firmware (fdrv).
Links to separately packaged firmware can be found here, https://www.forum.puppylinux.com/postin ... it&p=51777. As gyrog’s package is the largest –so most likely to include the necessary firmware-- I’d try this one first, linux_firmware_2023_0712.sfs, https://www.mediafire.com/folder/k2j223jzddy9x/firmware. Download it, Right-Click>Select Rename, name it fdrv_bionicpup64_8.0.sfs and place it next to the vmlinuz. Reboot. [You can later try smaller packages. Or if the it includes the needed firmware, someone can explain how to copy it from the SFS into your Save so that you can remove the fdrv.sfs. But despite its size it will have little impact on your system. It will be copied into RAM-cache and Puppys are very efficient in their use of RAM cache. A 347 Mb SFS is likely to only reduce available RAM-for-Use by about 70 Mbs].
If that doesn’t solve the problem, you’ll find several 5.4 kernel packages here, https://archive.org/download/Puppy_Linux_Huge-Kernels The ones bearing the ‘ubun’ designation are most likely to work with either of the Ubuntu based Puppys, Bionic and Fossa. These are packaged as ‘Hugh Kernels’ containing both a vmlinuz and drivers compiled against it. Download, Right-Click>Extract. Rename the vmlinuz-something to just vmlinuz; rename the kernel_modules-something.sfs to zdrv_bionicpup64_8.0.sfs and substitute these for the current ones. Leave gryrog’s fdrv.sfs in place.
Which of those to try first is a guess.
Of course, if anyone knows the Asus X205T well enough to identify the kernel, drivers and firmware it needs, please chime in so that a lot of trial and error can be avoided.
In the meantime, wmmiller, you can boot up Bionicpup64 and open Menu>System>PupSysInfo. It’s Devices submenu should identify the wifi adapter builtin.
=======
* See this post about using Rufus. https://www.forum.puppylinux.com/viewto ... 522#p40522 Did you have Rufus create a ‘persistent’ partition so that Puppy would have some place to create SaveFiles/Folders?
to the forum!