'lo all...
I'm trying to get Puppy to work on a new PC... and I'm getting some very strange problems.
Firstly, I'm trying to boot from a USB flash drive that just has the fossapup64_9.5.iso 'unpacked' onto it, as well as a couple of .sfs files.
The PC has an ASUS PRIME Z790-P D4 motherboard with an Intel i5 12th gen CPU installed and a TPM installed... and has Windows 11 Home 64-bit installed. The UEFI has been set-up to use 'Other OS' rather than Windows, so I guess that means 'Secure Boot' is disabled. ASUS provides NO linux drivers for this motherboard.
I've tried most of the 'official' Puppy 64-bit variants over the last few days and none of them recognize the on-board network adapter. Note that I had the same problem with Puppy not recognizing the on-board video adapter and so had to organize a separate video card to be installed.
The motherboard manual describes the adapter as a 'Realtek 2.5Gb Ethernet port' and Puppy 'Sys-Info' reports the same.
Checking the Realtek web site, I find they have a linux driver (sources as a .bz2 file) for this adapter 'family':
Realtek PCIe FE / GbE / 2.5GbE / Gaming Family Controller Software Quick Download Link
Now, I've never built anything that relies on the kernel sources... but after some explorations in these forums, I found that we have an sfs file available: kernel_sources-5.4.53-fossapup64.sfs.
So, as I'm doing my 'primary' explorations with Fossapup64 9.5, I'm guessing (hoping) using this this file will help me get things sorted.
So, I have a 'vanilla' .4fs savefile created (just the 'Quicksetup' options)... and I use the 'Boot Manager' (in the Puppy menus) to load the devx_fossapup64_9.5.sfs and the kernel_sources-5.4.53-fossapup64.sfs files. After extracting the files from the driver .bz2 file, I run the 'autorun.sh' file and it all works Ok, building the driver (somewhere), removing the only loaded network driver (r8169) and it does something with 'devmod' to load the newly created r8125 driver.
After this, I run the 'Network Wizard' and I can connect quite happily to my local network, the local IP address is allocated and I can browse web sites and connect to SAMBA shares and all the rest of it.
However, when I try to run the 'Puppy Package Manager' - PPM (/usr/local/petget/pkg_chooser.sh) either by itself OR via the 'Install' (/usr/sbin/dotpup) script, the message "Loading Puppy Package Manager..." stays on the screen and nothing else visibly happens.
I've gone through looking at the processes and so on... and neither of the scripts are still running... but the message is still there. I then find that the message is created by gtkdialog... so killing that process gets rid of the message.
If I run the pkg_chooser.sh script in a terminal window to see what's going on, the following is displayed:
Code: Select all
root# /usr/local/petget/pkg_chooser.sh
[xcb] Unknown sequence number while processing reply
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
gtkdialog: ../../src/xcb_io.c:641: _XReply: Assertion `!xcb_xlib_threads_sequence_lost' failed.
/usr/local/petget/pkg_chooser.sh: line 743: 4385 Aborted gtkdialog -p PPM_GUI
root#
...which I don't understand at all.
Thinking the problem was something to do with the network adapter driver I built from scratch, I went back to booting without any savefile (and obviously, no available network) and the same problem with PPM occurred.
Going around in circles again, I tried inserting a USB 'flash drive' -like wireless adapter and can configure it and all the networking works... BUT! the problem with PPM not running persists.
So, it seems like there's something awry with Puppy and this hardware. I tried the same USB flash drive I was booting from on other PCs and they work Ok, in terms of PPM and the network connections (wireless USB and the on-board ethernet).
After ~20 years of using Puppy, it'd be pretty disappointing to have to stop using it because I can't install any software on this PC using any of the 'production' variants... so maybe someone has some clues on what is going silly here... or maybe it's as simple as it's the wrong motherboard... and maybe there's something better to use? The Windows side of things is all working Ok.. so far - I'm only a few days into probably a month of setting it all up if I have to get a new motherboard (Ugh!)
Thanks for any thoughts...