Adapting F-96-CE Puppy Linux for a Very Recent Laptop (3/2024)

[vtpup]

The absolute best in-depth discussion of touchpads and synaptics I have found is here:

https://wiki.archlinux.org/title/Synaptics

It seems there are bunch of alternative ways that touchpads can be handled by any Lnux OS, and I'm wondering if there's some alternative method in there that will stop my cursor loss problems in my present F96-CE v4 installation.

[ozsouth]

@vtpup - need to to test thus:

Open terminal & maximise it (important).
Run: dmesg | grep irmware

This will tell you if any firmware in use or missing. From there, can decide what to look for.

[vtpup]

From the test install with new huge kernel and the new fdrv:

Code: Select all

# dmesg | grep firmware
[   36.554611] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-86.ucode failed with error -2
[   36.554639] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-85.ucode failed with error -2
[   36.554669] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-84.ucode failed with error -2
[   36.554703] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-83.ucode failed with error -2
[   36.554732] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-82.ucode failed with error -2
[   36.554758] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-81.ucode failed with error -2
[   36.554784] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-80.ucode failed with error -2
[   36.554820] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-79.ucode failed with error -2
[   36.554846] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-78.ucode failed with error -2
[   36.554872] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-77.ucode failed with error -2
[   36.554898] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-76.ucode failed with error -2
[   36.554923] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-75.ucode failed with error -2
[   36.554949] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-74.ucode failed with error -2
[   36.554975] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-73.ucode failed with error -2
[   36.598087] iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 so-a0-gf-a0-72.ucode op_mode iwlmvm
[   36.955015] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   36.989542] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[   37.062299] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.18)
[   37.076907] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin (70.12.1) is recommended, but only i915/adlp_guc_70.bin (70.5.1) was found
[   37.076911] i915 0000:00:02.0: [drm] GT0: Consider updating your linux-firmware pkg or downloading from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[   37.094780] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.5.1
[   37.094783] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[   38.593793] Bluetooth: hci0: Waiting for firmware download to complete
# 

[ozsouth]

@vtpup - wow! your wifi is looking for firmware ver 86 & makes more than 12 retries before it finds ver 72 - usually only get about 6 retries before it gives up. The newest I can find is ver 83 - seems to require kernel 6.5 or later. As in pic below, go to site & click download icon on right, under green arrow in pic. That would only mean 3 retries & should work better.
Link: https://github.com/LibreELEC/iwlwifi-fi ... 0-83.ucode

The output you posted did not provide any touchpad clues, so may need a driver (?) compiled.
.

[vtpup]

Thanks ozsouth, will do. Though wifi is working now, and began working once I'd added version 71, even though it reported in that printout stopping at 72. Anyway I'll try the 83 version just so we can learn more. This is a definite learning process for me about how all these things mesh together.

re. touchpad, i've done more reading. Also I see in that printout that i915 isn't quite right, which I understand is the graphics. I'd like to fix that. I had screen problems with wine/sketchup as posted earlier and I finally gave up, and went to a virtual machine windows7 to run sketchup. I'd prefer wine if possible. Anyway, that's a different topic.

I will be away from computers for the morning. Major snowstorm happening, and I have to plow us out now with the old '51 John Deere Model M. Might not be able to answer stuff til this evening. I do appreciate all the help and the learning experience for me here.

[rockedge]

the old '51 John Deere Model M

Going to be cold on that tractor..........snow missed us on the coast of CT so our old John Deere 826 snowblower is still in its parking spot, wheels up.

Can we summarize your new gained knowledge once the hardware drivers are sorted out? Seems like a valuable experience figuring out how to get F96-CE_4 working well on a very new and modern machine.

[vtpup]

Can we summarize your new gained knowledge once the hardware drivers are sorted out? Seems like a valuable experience figuring out how to get F96-CE_4 working well on a very new and modern machine.

Sure Rockedge, I'd be happy to.

SnowThurs.jpg (196.21 KiB) Viewed 426 times

[vtpup]

I wanted to compare the firmware messages on Bookworm, which loads wifi and touchpad, and almost works with sound as well. I didn't see anything here either relating to the touchpad.

Code: Select all

  dmesg | grep firmware
[   64.002652] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[   64.002759] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[   64.175301] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-so-a0-gf-a0-72.ucode
[   64.176088] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   64.176093] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[   64.176113] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   64.176116] iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 so-a0-gf-a0-72.ucode op_mode iwlmvm
[   64.357227] i915 0000:00:02.0: firmware: direct-loading firmware i915/adlp_dmc_ver2_16.bin
[   64.359032] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc_ver2_16.bin (v2.16)
[   64.398351] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   64.401890] bluetooth hci0: firmware: direct-loading firmware intel/ibt-0040-0041.sfi
[   64.401899] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[   64.407262] i915 0000:00:02.0: firmware: direct-loading firmware i915/adlp_guc_70.bin
[   64.409110] i915 0000:00:02.0: firmware: direct-loading firmware i915/tgl_huc.bin
[   64.529601] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin version 70.5.1
[   64.529606] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[   64.542697] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-so-a0-gf-a0.pnvm
[   65.773970] sof-audio-pci-intel-tgl 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-rpl.ri
[   65.899980] sof-audio-pci-intel-tgl 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-2ch.tplg
[   65.959333] Bluetooth: hci0: Waiting for firmware download to complete
[   65.977770] bluetooth hci0: firmware: direct-loading firmware intel/ibt-0040-0041.ddc

However I did find by reading dmesg without a filter:

Code: Select all

[   64.143892] input: SYNA32E6:00 06CB:CE7D Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA32E6:00/0018:06CB:CE7D.0002/input/input7
[   64.143965] input: SYNA32E6:00 06CB:CE7D Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA32E6:00/0018:06CB:CE7D.0002/input/input8
[   64.144035] hid-multitouch 0018:06CB:CE7D.0002: input,hidraw0: I2C HID v1.00 Mouse [SYNA32E6:00 06CB:CE7D] on i2c-SYNA32E6:00

[vtpup]

I tried some of the tests with the 6.8 kernel test version, as described here:

https://forum.manjaro.org/t/synaptics-t ... d/11970/36

Code: Select all

# ls -l /sys/bus/acpi/devices/SYNA32E6:00/physical_node/
total 0
lrwxrwxrwx 1 root root    0 Apr  4 19:33 firmware_node -> ../../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:36/SYNA32E6:00
-r--r--r-- 1 root root 4096 Apr  4 19:22 modalias
-r--r--r-- 1 root root 4096 Apr  4 19:33 name
drwxr-xr-x 2 root root    0 Apr  4 19:33 power
lrwxrwxrwx 1 root root    0 Apr  4 19:33 subsystem -> ../../../../../../bus/i2c
-rw-r--r-- 1 root root 4096 Apr  4 19:22 uevent
-r--r--r-- 1 root root 4096 Apr  4 19:33 waiting_for_supplier

Code: Select all

# cat /sys/bus/i2c/devices/i2c-*/name
SMBus I801 adapter at efa0
i915 gmbus tc5
i915 gmbus tc6
AUX A/DDI A/PHY A
AUX USBC1/DDI TC1/PHY TC1
AUX USBC2/DDI TC2/PHY TC2
AUX USBC3/DDI TC3/PHY TC3
AUX USBC4/DDI TC4/PHY TC4
Synopsys DesignWare I2C adapter
Synopsys DesignWare I2C adapter
i915 gmbus dpa
i915 gmbus dpb
i915 gmbus dpc
i915 gmbus tc1
i915 gmbus tc2
i915 gmbus tc3
i915 gmbus tc4
SYNA32E6:00

Code: Select all

# readlink /sys/bus/acpi/devices/SYNA32E6:00/physical_node
../../../../../pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA32E6:00

Code: Select all

# ls -l /sys/devices/pci0000:00/0000:00:15.0/
total 0
-r--r--r-- 1 root root 4096 Apr  4 19:42 ari_enabled
-rw-r--r-- 1 root root 4096 Apr  4 19:42 broken_parity_status
-r--r--r-- 1 root root 4096 Apr  4 19:22 class
-rw-r--r-- 1 root root  256 Apr  4 19:22 config
-r--r--r-- 1 root root 4096 Apr  4 19:42 consistent_dma_mask_bits
-rw-r--r-- 1 root root 4096 Apr  4 19:42 d3cold_allowed
-r--r--r-- 1 root root 4096 Apr  4 19:22 device
drwxr-xr-x 4 root root    0 Apr  4 19:22 dma
-r--r--r-- 1 root root 4096 Apr  4 19:42 dma_mask_bits
lrwxrwxrwx 1 root root    0 Apr  4 19:42 driver -> ../../../bus/pci/drivers/intel-lpss
-rw-r--r-- 1 root root 4096 Apr  4 19:42 driver_override
-rw-r--r-- 1 root root 4096 Apr  4 19:42 enable
lrwxrwxrwx 1 root root    0 Apr  4 19:42 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:36
drwxr-xr-x 4 root root    0 Apr  4 19:22 i2c_designware.0
drwxr-xr-x 3 root root    0 Apr  4 19:22 idma64.0
lrwxrwxrwx 1 root root    0 Apr  4 19:42 iommu -> ../../virtual/iommu/dmar1
lrwxrwxrwx 1 root root    0 Apr  4 19:42 iommu_group -> ../../../kernel/iommu_groups/12
-r--r--r-- 1 root root 4096 Apr  4 19:22 irq
drwxr-xr-x 2 root root    0 Apr  4 19:42 link
-r--r--r-- 1 root root 4096 Apr  4 19:42 local_cpulist
-r--r--r-- 1 root root 4096 Apr  4 19:42 local_cpus
-r--r--r-- 1 root root 4096 Apr  4 19:22 modalias
-rw-r--r-- 1 root root 4096 Apr  4 19:42 msi_bus
-rw-r--r-- 1 root root 4096 Apr  4 19:42 numa_node
drwxr-xr-x 2 root root    0 Apr  4 19:42 power
-r--r--r-- 1 root root 4096 Apr  4 19:42 power_state
--w--w---- 1 root root 4096 Apr  4 19:42 remove
--w------- 1 root root 4096 Apr  4 19:42 rescan
-r--r--r-- 1 root root 4096 Apr  4 19:22 resource
-rw------- 1 root root 4096 Apr  4 19:42 resource0
-r--r--r-- 1 root root 4096 Apr  4 19:22 revision
lrwxrwxrwx 1 root root    0 Apr  4 19:22 subsystem -> ../../../bus/pci
-r--r--r-- 1 root root 4096 Apr  4 19:22 subsystem_device
-r--r--r-- 1 root root 4096 Apr  4 19:22 subsystem_vendor
-rw-r--r-- 1 root root 4096 Apr  4 19:22 uevent
-r--r--r-- 1 root root 4096 Apr  4 19:22 vendor

[rockedge]

@vtpup the photo would make a great background.....add a 50%-60% transparent black layer on top so the desktop icons pop

[vtpup]

Thanks Rockedge! I do actually have a similar one as a desktop background, but of the front yard without the tractor.

I've taken a mental break from working with that experimental install and am back with the working 6.1.8 kernel F96. I needed to print something tonight, and of course CUPS wasn't set up yet. So I did that using the same exact settings and driver as I have on my old laptop (even compared them). But as often happens, it didn't print. I get a filter failed message.

The printer driver is old, so I'm guessing 32 bit. The other laptop is also running 64 bit (Bionic) but it has the 32 bit compatibility sfs in it.

Does F96-CE already have 32 bit compat? I notice the choice is grayed out in Quickpet.

[vtpup]

Out of curiosity, and while waiting for word about 32 bit compat for F96-CE, I decided to try to install Bionic64 in the new laptop. It went well but of course touchpad and wifi didn't work. BUT, I then installed the 6.1.8 Huge kernel using Quickpet, plus the linux_firmware_20240201.sfs and wifi and touchpad worked!

I then tested CUPS setup on that without, and then with 32 bit compat, and yes it is absolutely needed for my printer driver.

So,,, does F96-CE have a 32 bit compat sfs?

[rockedge]

So,,, does F96-CE have a 32 bit compat sfs?

I have been using the one from Fossapup64-9.5

Download here -> https://rockedge.org/kernels/data/Devx/ ... ossa64.sfs

[bigpup]

@rockedge

How about adding that link to the 32bit compatibility SFS in the first post of the F96-CE topic.
viewtopic.php?t=8392

[vtpup]

Thanks Rockedge, I added the Fossapup 32 compat sfs to the 6.1.8 Kernel F-96-CE v4 working installation and rebooted. Unfortunately printing a test page still throws the error message "Filter Failed". I tried turning off the firewall, just in case there was a problem there, but no change.

I double checked the CUPS printer setup specs and they are exactly the same as those that work on this same laptop under Bionicpup64 w/ Bionic 32 bit compatibility sfs.

I don't know for sure that the 32 bit fossa compat is the problem -- it could be something else. One difference is the version of CUPS, which is 2.3.1 in F96-CE v4 and 2.2.7 in Bionic64.

The printer specs in CUPS are as follows. Note they do work in Bionic64:

Description: Laser Printer
Location: Cheryl's Office
Driver: Xerox Phaser 6000B v1.0 (color)
Connection: socket://10.0.0.15:9100
Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=one-sided

One other unrelated question.... Is it okay if I change the title of this thread to "Adapting F-96-CE Puppy Linux for a Very Recent Laptop (3/2024)"

I've gone far afield of the original post topic, and this new topic description would cover all of what's been tackled so far, and hopefully be of interest in a more general way. I will summarize in a single post once we get most of the experiments, investigations and fixes accomplished.

[vtpup]

Testing the F96-CE v4 6.1.8 kernel CUPS issue:

1.) I created a fresh instance of the above, and created a new save folder.

2.) I loaded linux_firmware_20240201.sfs, and I added iwlwifi-so-a0-gf-a0-71.ucode to /lib/firmware (both were needed to get wifi working for the Intel ax211 wifi card).

3.) I loaded the 32bit-compatibilty-fossa64.sfs and installed the xerox-phaser-6000-6010_1.0-1_i386.deb to provide the printer driver for my specific printer.

4.) I entered the network socket connection details and chose the printer driver in CUPS to create a new printer.

5.) Printing a test page from Maintenance in CUPS failed with "Filter Failed" message.

As a comparative test, I created new instances of Bionicpup64 and Fossapup64 9.5, changed kernels to 6.1.8, and updated each OS through Quickpet.

I followed the steps 2 through 4 above with both of them.

Printing a test page was successful from both of those. So there seems to be something specifically different about F-96 CE.

Bionicpup64 uses CUPS v2.2.7,

Both Fossapup64 9.5 and F96-CE v4 use CUPS version 2.3.1.

[bigpup]

Is it okay if I change the title of this thread to "Adapting F-96-CE Puppy Linux for a Very Recent Laptop (3/2024)"

That would be a good thing to do!

In the first post give a few details about the computers specs.
CPU
RAM
Graphics hardware

[bigpup]

Before you start adding software to get what may be needed to operate specific hardware.

It is best to do initial boot making basic setup settings.

Do a shutdown and make a save file/folder.

Boot now using the save and then start adding software.

For what software you are adding.

After installing it.

Reboot making sure the save is getting updated.

Now when it boots, all the added software is there to be activated, when needed by the boot process, to support the hardware.

[vtpup]

Yes, that's what I do. All of the above had savefolders. They still do.