See viewtopic.php?t=9113, it sacrifices everything possible including hardware support and performance for smaller size.
For AppImages to work, you probably need to install libfuse2.
See viewtopic.php?t=9113, it sacrifices everything possible including hardware support and performance for smaller size.
For AppImages to work, you probably need to install libfuse2.
No, it really depends on the application.
I think it's time to put F96-CE there instead of Fossapup64.
@wizard I'm not sure if there's any missing driver: as far as I see, all required drivers are built-in to the kernel (and nvme0 is detected before init is started, at a very early stage). Can you share the GRUB configuration file?
If you boot BookwormPup64 from a flash drive, does it recognize the drive? Or, is there any distro that boots fine from this drive?
Please share the output of these commands from any distro, where the drive is recognized (not necessarily at boot time):
Code: Select all
lsmod
lspci
dmesg
fdisk -l
Vanilla Dpup 9.3.40 and 10.0.52 include https://github.com/puppylinux-woof-CE/woof-CE/pull/4278, to gather feedback. It works fine for me.
It's a writable image, it's not read-only. Maybe you moved the files out of it, so now it appears empty.
Maybe try to redownload?
@Jasper In your case it's /dev/loop5, hence /dev/loop5p1 and /dev/loop5p2.
For those worried about the longevity and sustainability of BookwormPup64 or Puppy as a whole, I opened this PR, which upstreams many changes and hacks I extracted from the 10.0.6 ISO. There could be more, it's hard to go file by file and find them.
@MochiMoppel The current code should address your concerns