Puppy Linux Discussion Forum

Fedora Workstation 38 works with ISObooter3. See above.

The Realtek 8852be 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:b852.

The hplip-print-scan-klv-3.19.8_2.x86_64.xbps package I made last year for the KLV project still works with this version.

Those are not the changes I was talking about. But that's the last I will have to say about the issue.

curious wrote: ↑Wed Aug 02, 2023 5:08 pm

S15Pup32-22.12-230618.iso on the Notino, no wi-fi
and on Dell Inspiron 8600, Pentium M banias, 512 MB DDR1, no wi-fi

How did you conclude that those setups did not have wifi?

Please run lspci again. Are you now loading the i915 kernel driver?

Supposedly, Xorg is now using the modesetting driver instead of falling back to VESA like before.

You can try the kernel upgrade pack here.

You are conflating UEFI with Secure Boot.

The Starter Kit has discussions about UEFI and Secure Boot.

What we now need is someone else with a Baytrail Chromebook to report whether they can boot BookwormPup.

People need to identify their Chromebook model, CPU and/or Chrome ID name,

With an AMD Ryzon machine, the most likely culprit is the Radeon video. You could try booting with the "radeon.modeset=0" boot argument.

[Edit] On the flash drive, locate the file /boot/grub/grub.cfg

Change line 48 to: linux /vmlinuz pfix=fsck pmedia=cd radeon.modeset=0

@wizard: Which exact Thinkpad 11E model do you have? The Baytrail? Do you know its Chromebook ID name?

I read someplace that if you disconnect the laptop screen from the motherboard, the machine will automatically boot to the VGA port.

The pdev1 boot argument has been in Puppy forever and still works.

Debian 12 Live works with ISObooter3. See above.

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.

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

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.

wizard wrote: ↑Fri Aug 04, 2023 6:12 pm

then adding a menu entry for BW64 in the MX-liux grub.cfg.

Could you post the GRUB entry for that?

It's a mystery why my BookwormPup boots and yours does not. I can't see why its initrd would behave differently.

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.