PuppEX Slack64 Build 241016 compatible with Slackware 15.0

[exton]

NEWS ABOUT PuppEX Slack64 15.0 241016
This Puppy derivative is built using Puppy Linux Woof-CE Builder. It is compatible with Slackware 15.0 and uses kernel 6.10.13-exton. This Puppy system works very well on UEFI and non-UEFI computers. You can build your own Puppy Linux Slackware 15 compatible system using PuppEX as "groundwork". Just start the remaster tool (Remaster Puppy) and follow the instructions given by the remaster script. I've included devx_puppex-slack64.sfs in the ISO file. Load it if you need it. Study all installed packages in this PuppEX build.

IMPORTANT NOTE
For some unknown reason this PuppEX build won't run on some newer computers. I could only run it on three of my six computers. X fails to start on my newest computers. And running Xorgwizard doesn't help. You can run the system very well in VirtualBox and VMware though. I can also mention that this PuppEX build works on my (very) old Acer Aspire 5102WLMi AMD with ATI Radeon Xpress 1100. Because of the X problems I have kept my previous PuppEX Slack64 15.0 Build from 220625 on the server. That build runs on all "normal" computers.

SCREENSHOTS
1. First screen after boot
2. A Frugal install running from a USB stick
3. Puppy Linux info
4. The Light Browser is outdated
5. Installing Firefox
6. Installing VirtualBox Guest Additions
7. Running in full screen in VirtualBox
8. Running the lspci command
9. Showing a Samba connection

ABOUT THE X PROBLEM
Maybe @Clarity, @fredx181, @bigpup, @peebee or someone else here knows or can figure out what's wrong with the auto-configuration of X. Please let me know. A solution would be much appreciated. The problem is not with the kernel. I've tested the system with other kernels.

[rockedge]

@exton I have also run into this problem with the X server crashing during/after booting when constructing KLV distro designs.

I found that in some cases it was the .xinitrc configuration and something not starting. Then there also were other similar occurrences with the X server attempting to start but has ownership/permissions problem reaching needed components.

Check for errors with ownership/permissions and double check the /root/.xinitrc and /home/spot/.xinitrc compared to the default .xinitrd

[exton]

@rockedge,

Ok, but how shall we explain that the new PuppEX version runs on some (older) computers and in VirtualBox/Vmware? I mean if something is wrong with the .xinitrc file that should/must make the system unusable on all computers.

[norgo]

@exton
X crashed during start on my laptop with intel graphics.

Code: Select all

[   25.501415] thinkpad_acpi: radio switch found; radios are enabled
[   25.501587] thinkpad_acpi: Tablet mode switch found (type: GMMS), currently in laptop mode
[   25.505675] i915 0000:00:02.0: vgaarb: deactivate vga console
[   25.505735] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   25.506433] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=mem
[   25.506952] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc.bin failed with error -2
[   25.506977] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc_ver2_16.bin failed with error -2
[   25.506979] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/adlp_dmc.bin (-ENOENT). Disabling runtime power management.
[   25.506981] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[   25.508633] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[   25.508635] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[   25.514823] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[   25.517312] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked
[   25.519645] AVX2 version of gcm_enc/dec engaged.
[   25.519678] AES CTR mode by8 optimization enabled
[   25.524164] usb 3-5: Found UVC 1.50 device Integrated RGB Camera (5986:2142)
[   25.567953] usb 3-5: Found UVC 1.50 device Integrated RGB Camera (5986:2142)
[   25.574055] thinkpad_acpi: battery 1 registered (start 0, stop 100, behaviours: 0x7)
[   25.574078] ACPI: battery: new extension: ThinkPad Battery Extension
[   25.583124] usbcore: registered new interface driver uvcvideo
[   25.587590] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input29
[   25.631059] i915 0000:00:02.0: [drm] *ERROR* GT0: GuC firmware i915/adlp_guc_70.bin: fetch failed -ENOENT
[   25.631065] i915 0000:00:02.0: [drm] GT0: GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[   25.633745] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 0.0.0
[   25.633823] i915 0000:00:02.0: [drm] *ERROR* GT0: GuC initialization failed -ENOENT
[   25.633826] i915 0000:00:02.0: [drm] *ERROR* GT0: Enabling uc failed (-5)
[   25.633828] i915 0000:00:02.0: [drm] *ERROR* GT0: Failed to initialize GPU, declaring it wedged!
[   25.634708] i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_set_wedged_on_init+0x34/0x50 [i915]

added following firmware

Code: Select all

/lib/firmware/i915/adlp_dmc.bin
/lib/firmware/i915/adlp_dmc_ver2_16.bin
/lib/firmware/i915/adlp_guc_70.bin

after that X start without crash.

[Clarity]

@peebee or @dimkr "may" know as this seems to be problem associated with WoofCE construction used in distro build

[exton]

@norgo,

Very good, but please tell me exactly how you added the firmware in question.

[norgo]

@exton
usualy we put the firmware into fdrv but this is not mandatory.
In your case into fdrv_slackex_24.10.sfs
If you want to add firmware afterward extract the fdrv_slackex_24.10.sfs and put the firmware files into fdrv_slackex_24.10 folder.
Use the same folder structure as the original firmware source.
/lib/firmware ....
To create the new sfs

Code: Select all

mksquashfs fdrv_slackex_24.10 fdrv_slackex_24.10.sfs -b 512k -Xbcj x86

[exton]

@norgo

Ok, thanks, but think I've found a better solution. The fdrv-file in PuppEX Slack64 lacks a lot of firmware. I will "borrow" a fdrv-file from another Puppy system. Hopefully PuppEX Slack64 will run on ALL computers then.

It seems to me that the Woof-CE Builder doesn't generate enough firmware (to the fdrv-file).