I have concerns about the new pdrv boot argument.
Also, I don't understand the root= argument. A Puppy frugal install has not needed it since Puppy 2.x.
I have concerns about the new pdrv boot argument.
Also, I don't understand the root= argument. A Puppy frugal install has not needed it since Puppy 2.x.
Code: Select all
linux /bw64/vmlinuz net.ifnames=0 root=UUID=3675127c-925a-40e7-8c93-be861e4e3501 pmedia=usbflash pdrv=3675127c-925a-40e7-8c93-be861e4e3501 psubdir=/bw64 ...
This style didn't work for me either. My line is just
Code: Select all
linux /BookwormPup64/vmlinuz pdev1=mmcblk0p2 psubdir=BookwormPup64 ...
I would assume that if Bookworm is running the same 6.1.0-9-amd64 kernel, it would work there too.
Linux-lite works with ISObooter3. See above.
The Realtek 8821ce WiFi driver (github version) is included in the k6.1.0-9 combo-wifi-driver-pack. It has been tested successfuly on a device with ID 10ec:c821.
Concerning PeasyApps: This project contains a version of PeasyPort that claims to be mine but has a number of anonymous, un-annotated changes.
I would not trust it.
I have reported this issue in other Puppies but was ignored.
What model is this converted Chromebook?
Does the UEFI firmware identify the emmc drive as a boot device?
I don't know why my setup boots and your does not. It feels like a timing problem in the Bookworm initrd.
Did you run a recent Puppy on the Lenovo?
Many old laptops have Broadcom wifi. In Puppy, it just needs some firmware.
BTW, if you try to run a modern Puppy on a machine with 1GB RAM or less, you will be disappointed.
It looks OK now. Thanks.
Change pdev1=mmcblk1p2 to pdev1=mmcblk0p2.
Do a cold start.
Or remove the pdev1 argument.
If the boot fails and ends with a prompt, type the command: blkid
Does it show any emmc parititions?
The Starter Kit avoids this situation by using UUIDs to identify locations.
Here is a problem I have seen with emmc hardware. If you do a soft reboot instead of a cold start, the system gets confused about the name of the emmc drive. It may change from mmcblk0 to mmcblk1.
Check you grub menu stanza. Which one is shown there?
Thanks.
MiniOS works with ISObooter3. LIke the PuppyOld ISOs, you need to extract some files and copy them to sdb2. See above.
I suspect that TC00's "ISO to USB" burning tool has left the flash drive in read-only state.
So the Savefile Creator tool failed, even though it reported success.
I would use Rufus instead to make the flash drive.
KLA-OT2baseCE-2.6 works with ISObooter3. Use 6-Other and add the key lines listed above.
My mistake. The --default-item option is already working with a combobox in 2.3.5, as does --editable.