BookwormPup64 10.0.8

[radky]

@radky, Thanks for the link to the 10.0.2 iso. I did run a quick test and whatever changes made the stock suspend/resume stop working occurred between 10.0 and 10.02. Both 10.0.2 and 10.0.3 require the connman stop/restart and the psmouse remove/reinstall and psynclient run in the suspend.sh script to work for me. 10.0 does not, suspend/resume works perfectly there OOTB. I used the same usrmerge kernel in all tests and checked both a pristine JWM install and my ydrv LXDE install. I'll ponder the changelogs but use 10.0 for now. The patches in suspend make resume pretty laggy as well as being puzzling. My WAG is that it is the Debian security updates.

Update: An interesting tidbit: In 10.0.3 (stock kernel) synclient "VertEdgeScroll"=1 or synclient "VertEdgeScroll"=0 will not run when called from a script (suspend.sh). In 10.0 (either 10.0 or 10.0.3 kernel) synclient will run and set properties correctly when called in exactly the same way.

@Marv

Lid-suspend functionality seems OK in my tests of BW64 10.0.3 on my ThinkPad Yoga 11e laptop.

1 - ConnMan WiFi connectivity - OK on resume
2 - Logitech M325 USB mouse connectivity - OK on resume
3 - Synaptics s3203_ver5 touchpad - OK on resume

Also tested by adding the following commands (one command per test) to the resume section of /etc/acpi/actions/suspend.sh

4 - psynclient -l (tested after changing touchpad settings) - OK on resume (psynclient runs and correctly applies the new touchpad settings)
5 - synclient VertEdgeScroll=1 - OK on resume (VerticalEdgeScroll correctly enabled)
6 - synclient VertEdgeScroll=0 - OK on resume (VerticalEdgeScroll correctly disabled)

---

With each point release of BW64 there are multiple binary/security updates from upstream Debian. I don't know which change after BW64 10.0.0 may have negatively impacted suspend and resume functionality of your Fujitsu S761 laptop.

Maybe @dimkr will provide additional insight.

[dimkr]

Here, this is the diff between 10.0.2 and 10.0.3, in terms of Debian updates:

Code: Select all

--
 Package: amd64-microcode
-Version: 3.20230719.1~deb12u1
+Version: 3.20230808.1.1~deb12u1
--
 Package: base-files
-Version: 12.4+deb12u1
+Version: 12.4+deb12u2
--
 Package: cups
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-bsd
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-client
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-common
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-core-drivers
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-daemon
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
--
 Package: cups-ipp-utils
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-ppdc
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: cups-server-common
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: curl
-Version: 7.88.1-10+deb12u1
+Version: 7.88.1-10+deb12u4
--
 Package: dbus
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
 Package: dbus-bin
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
 Package: dbus-daemon
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
 Package: dbus-session-bus-common
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
 Package: dbus-system-bus-common
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
 Package: dbus-x11
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
--
 Package: debian-archive-keyring
-Version: 2023.3
+Version: 2023.3+deb12u1
 Package: debianutils
-Version: 5.7-0.4
+Version: 5.7-0.5~deb12u1
--
 Package: ghostscript
-Version: 10.0.0~dfsg-11+deb12u1
+Version: 10.0.0~dfsg-11+deb12u2
--
 Package: gir1.2-gtk-3.0
-Version: 3.24.37-2
+Version: 3.24.38-2~deb12u1
--
 Package: gir1.2-vte-2.91
-Version: 0.70.6-1~deb12u1
+Version: 0.70.6-2~deb12u1
--
 Package: gtk-update-icon-cache
-Version: 3.24.37-2
+Version: 3.24.38-2~deb12u1
--
 Package: libc-bin
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
 Package: libc-dev-bin
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
 Package: libc-l10n
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
 Package: libc6
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
 Package: libc6-dev
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
--
 Package: libcups2
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
--
 Package: libcupsimage2
-Version: 2.4.2-3+deb12u1
+Version: 2.4.2-3+deb12u4
 Package: libcurl3-gnutls
-Version: 7.88.1-10+deb12u1
+Version: 7.88.1-10+deb12u4
 Package: libcurl4
-Version: 7.88.1-10+deb12u1
+Version: 7.88.1-10+deb12u4
--
 Package: libdbus-1-3
-Version: 1.14.8-2~deb12u1
+Version: 1.14.10-1~deb12u1
--
 Package: libgs-common
-Version: 10.0.0~dfsg-11+deb12u1
+Version: 10.0.0~dfsg-11+deb12u2
 Package: libgs10
-Version: 10.0.0~dfsg-11+deb12u1
+Version: 10.0.0~dfsg-11+deb12u2
 Package: libgs10-common
-Version: 10.0.0~dfsg-11+deb12u1
+Version: 10.0.0~dfsg-11+deb12u2
--
 Package: libgssapi-krb5-2
-Version: 1.20.1-2
+Version: 1.20.1-2+deb12u1
 Package: libgtk-3-0
-Version: 3.24.37-2
+Version: 3.24.38-2~deb12u1
 Package: libgtk-3-common
-Version: 3.24.37-2
+Version: 3.24.38-2~deb12u1
--
 Package: libhwy1
-Version: 1.0.3-3
+Version: 1.0.3-3+deb12u1
--
 Package: libimlib2
-Version: 1.10.0-4+b1
+Version: 1.10.0-4+deb12u1
--
 Package: libk5crypto3
-Version: 1.20.1-2
+Version: 1.20.1-2+deb12u1
--
 Package: libkrb5-3
-Version: 1.20.1-2
+Version: 1.20.1-2+deb12u1
 Package: libkrb5support0
-Version: 1.20.1-2
+Version: 1.20.1-2+deb12u1
--
 Package: libpam-modules
-Version: 1.5.2-6
+Version: 1.5.2-6+deb12u1
 Package: libpam-modules-bin
-Version: 1.5.2-6
+Version: 1.5.2-6+deb12u1
 Package: libpam-runtime
-Version: 1.5.2-6
+Version: 1.5.2-6+deb12u1
 Package: libpam0g
-Version: 1.5.2-6
+Version: 1.5.2-6+deb12u1
--
 Version: 0.21.2-1
+Package: libptytty0
+Version: 2.0-1+b1
--
 Package: libssl3
-Version: 3.0.9-1
+Version: 3.0.11-1~deb12u2
+Package: libstartup-notification0
+Version: 0.12-6+b1
--
 Package: libudev1
-Version: 252.12-1~deb12u1
+Version: 252.17-1~deb12u1
--
 Package: libunbound8
-Version: 1.17.1-2
+Version: 1.17.1-2+deb12u1
--
 Package: libvpx7
-Version: 1.12.0-1
+Version: 1.12.0-1+deb12u2
 Package: libvte-2.91-0
-Version: 0.70.6-1~deb12u1
+Version: 0.70.6-2~deb12u1
 Package: libvte-2.91-common
-Version: 0.70.6-1~deb12u1
+Version: 0.70.6-2~deb12u1
--
 Package: libwebp7
-Version: 1.2.4-0.2
+Version: 1.2.4-0.2+deb12u1
 Package: libwebpdemux2
-Version: 1.2.4-0.2
+Version: 1.2.4-0.2+deb12u1
 Package: libwebpmux3
-Version: 1.2.4-0.2
+Version: 1.2.4-0.2+deb12u1
--
 Package: libx11-6
-Version: 2:1.8.4-2+deb12u1
+Version: 2:1.8.4-2+deb12u2
 Package: libx11-data
-Version: 2:1.8.4-2+deb12u1
+Version: 2:1.8.4-2+deb12u2
 Package: libx11-xcb1
-Version: 2:1.8.4-2+deb12u1
+Version: 2:1.8.4-2+deb12u2
--
 Package: libxpm4
-Version: 1:3.5.12-1.1
+Version: 1:3.5.12-1.1+deb12u1
--
 Package: linux-libc-dev
-Version: 6.1.38-4
+Version: 6.1.55-1
 Package: locales
-Version: 2.36-9+deb12u1
+Version: 2.36-9+deb12u3
--
 Package: openssh-client
-Version: 1:9.2p1-2
+Version: 1:9.2p1-2+deb12u1
 Package: openssl
-Version: 3.0.9-1
+Version: 3.0.11-1~deb12u2
--
 Version: 3.2.7-1
+Package: rxvt-unicode
+Version: 9.30-2+b4
--
 Package: udev
-Version: 252.12-1~deb12u1
+Version: 252.17-1~deb12u1
--
 Package: xserver-common
-Version: 2:21.1.7-3
+Version: 2:21.1.7-3+deb12u2
--
 Package: xserver-xorg-core
-Version: 2:21.1.7-3
+Version: 2:21.1.7-3+deb12u2

(plus kernel bump, probably from 6.1.38+4 to 6.1.55+1)

Nothing here looks really relevant to the problem you're having (not sure I 100% understand the symptoms, though), and /etc/acpi is unchanged in 10.0.3.

[Marv]

@Marv

Lid-suspend functionality seems OK in my tests of BW64 10.0.3 on my ThinkPad Yoga 11e laptop.

1 - ConnMan WiFi connectivity - OK on resume
2 - Logitech M325 USB mouse connectivity - OK on resume
3 - Synaptics s3203_ver5 touchpad - OK on resume

Also tested by adding the following commands (one command per test) to the resume section of /etc/acpi/actions/suspend.sh

4 - psynclient -l (tested after changing touchpad settings) - OK on resume (psynclient runs and correctly applies the new touchpad settings)
5 - synclient VertEdgeScroll=1 - OK on resume (VerticalEdgeScroll correctly enabled)
6 - synclient VertEdgeScroll=0 - OK on resume (VerticalEdgeScroll correctly disabled)

Thanks, I don't have any other laptop hardware to test on, but that's exactly how it works on the S761 in pristine 10.0, but not in pristine 10.2 or 10.3. The failure of the synclient commands to apply changes is puzzling in particular to me. I'll probably put it on the back burner til 10.0.4 and revisit it then.

@dimkr Thanks, I'll look at the diff and play with my 'synclient failure from script' oddity on the Fujitsu S761 for now.

[OscarTalks]

Are we not able to get installwatch working in this Pup?
I think the new2dir script needs it, does it not?

A little later:-
I have tried a few things that didn't work, but now I tried apt update followed by apt install checkinstall so I have the official Debian package. Plucking out the installwatch files from that seems to give me a .pet that works, but need to test it more, or happy to hear advice or suggestions

[gyrog]

A request:
For the next version could you please consider defining DISTRO_FILE_PREFIX as something a little more descriptive than simply 'dpup'.
(Maybe something like 'dpupbw', or 'dpupbw64', or even 'dpupbookworm64'.)

It is possible for all Puppy savefolders to be stored in a single directory, so you end up with a directory containing something like:

Code: Select all

dpup32save dpupsave fossapup64save s15pup64save upupjj+dsave

Notice that the non-dpup filenames are more indicative of exactly which Puppy the savefolder belongs to.
It's also going to be a real pain if folk want to install more than a single dpup, i.e. one that is not based on Bookworm.

[OscarTalks]

I remain a big fan of PSIP although I am not sure how many others there are these days.
It is of course a GUI for the pjproject program which is still very much in active development. Jamesbond has done some updating of the PSIP source in 2023 so I was experimenting with it a bit in BookwormPup64

The very latest pjproject release is 2.14 and although I was able to compile latest PSIP with that, unfortunately it aborted when I tried to run it. The slightly earlier pjproject release however is 2.13.1 which is the one which jamesbond reports that he tested with and which I can confirm does indeed compile and run successfully in BookwormPup64 in my tests. This works with openSSL-3 so eliminates the problems of having no SSL support with earlier pjproject versions. I can see in the terminal output of PSIP that TLS transport is operational. It also does link against libopus, but I am not sure if the opus codec is actually functional. It would be nice if it were. Maybe the sample rate setting is a factor as I believe opus sometimes requires 48000?
EDIT: Opus codec is working, just seen it in the stats when I did a call to "Wideband G722 Demo"

Anyway I will upload a package in case there are any folks out there who wish to test it out:-
http://smokey01.com/OscarTalks/psip-1.4 ... 4-bkwm.pet

[Clarity]

An inadvertent click on the taskbar's LAN adapter icon causes it to disappear. This is the 2nd time this has happened to me. Each time I have hunted the system to try to recover the taskbar icon with NO success. Anyone know how to recover it without restarting?

Thanks in advance if this has happened to you and you can share how you recovered.

[OscarTalks]

Clarity,
If you mean the blue and green rectangles icon in the notification area that is connman-ui-gtk.bin but task manager shows it as running as spot.
I can not reproduce your problem here, clicking it (left or right) does not kill it for me.
If I choose to click the "Quit" option to kill it, I can restart it again from terminal with:-

Code: Select all

run-as-spot connman-ui-gtk.bin &

followed by

Code: Select all

exit

to close the terminal but leave the program running
But there probably is some other way of switching it back on which I have not spotted yet.

[Clarity]

Thanks...Worked!

[Sofiya]

Bookworm Pup64 10.0.3 Thanks..

[Marv]

@Marv

Lid-suspend functionality seems OK in my tests of BW64 10.0.3 on my ThinkPad Yoga 11e laptop.

1 - ConnMan WiFi connectivity - OK on resume
2 - Logitech M325 USB mouse connectivity - OK on resume
3 - Synaptics s3203_ver5 touchpad - OK on resume

Also tested by adding the following commands (one command per test) to the resume section of /etc/acpi/actions/suspend.sh

4 - psynclient -l (tested after changing touchpad settings) - OK on resume (psynclient runs and correctly applies the new touchpad settings)
5 - synclient VertEdgeScroll=1 - OK on resume (VerticalEdgeScroll correctly enabled)
6 - synclient VertEdgeScroll=0 - OK on resume (VerticalEdgeScroll correctly disabled)

Thanks, I don't have any other laptop hardware to test on, but that's exactly how it works on the S761 in pristine 10.0, but not in pristine 10.2 or 10.3. The failure of the synclient commands to apply changes is puzzling in particular to me. I'll probably put it on the back burner til 10.0.4 and revisit it then.

@dimkr Thanks, I'll look at the diff and play with my 'synclient failure from script' oddity on the Fujitsu S761 for now.

I haven't been using Bookworm64 10.0.3 much, mostly due to the lidsuspend quirks on my Fujitsu S761 -but not on a near identical but slightly newer S762- Both BIOS are updated to the newest available for the hardware.
I do have work-arounds in suspend.sh but there is a fair time penalty on awaking for modprobing psmouse.

Two positive changes to note on the Fujitsu S761 platform, observed when testing newer kernels in Bookworm64 10.0.3. Kernels all from @peebee and with their structure usrmerge adjusted. With the 6.6.1 kernel, connman reconnected on awaking with no intervention, and with the 6.6.8 kernel, on awaking the touchpad also works perfectly with no patches at all required in the suspend.sh script. This is all on the Fujitsu S761 hardware, either with a pristine (other than the kernel swap) boot, or in my full LXDE'd savefile-less install. The only other laptop hardware I have, the Fujitsu S762, suspends and wakes correctly with the stock kernel or any of these swaps.

A small thing but if you lidsuspend 5 or 10 times in a typical day it tips the balance back toward Bookworm64 for a daily. Posting from it now.

Just reporting my experience,

[radky]

@Marv

Upstream Debian Bookworm incorporates the 6.1.X kernel and Woof-CE generates a Puppy compatible kernel using the upstream sources. The resulting kernel build is used in both Vanilla Dpup and BW64.

The upstream release of Debian Bookworm 12.3 was planned for 9 Dec 2024. However, kernel 6.1.64 in that release inherited a serious bug with the potential for ext4 data corruption. Consequently, upstream Bookworm 12.3 was quickly withdrawn and subsequently replaced a few days later by Bookworm 12.4 with kernel 6.1.66.

Unfortunately, shortly thereafter a serious WiFi regression was reported in 6.1.66, and the Debian devs quickly updated the kernel sources to 6.1.67 which fixed the WiFi regression.

At some point, a Woof-CE generated kernel >= 6.1.67 should be available for Vanilla Dpup and BW64. That said, if I understand correctly, Woof-CE generated builds of BW64 will not move to the 6.6.X kernel, but will continue with updated releases of the 6.1.X kernel.

Thanks for report Marv. Its good to know your Fujitsu S761 laptops will suspend properly after switching to kernel 6.6.X.

[dimkr]

That said, if I understand correctly, Woof-CE generated builds of BW64 will not move to the 6.6.X kernel, but will continue with updated releases of the 6.1.X kernel.

Yes, sticking to "Debian Stable" packages is a double-edged sword: you don't get new features that introduce new bugs (package versions are frozen and they receive only bug and security fixes), but old bugs stay until a fix is available and gets backported to the old package version in Debian Stable. If you're affected by a bug fixed in 6.6.x, you'll have to wait until it's backported to 6.1.x and Debian Stable kernel is updated to new 6.1.x version.

woof-CE can build a Puppy from Debian Testing packages, but it's a moving target. Currently you get kernel 6.5.x, tomorrow it can be 6.6.x, you get new features but things that worked can break. It's impossible to release a "stable" 1.0.0 Puppy based on Debian Testing packages, then release a 1.0.1 "bugfix release" that doesn't introduce any new issues, because Debian Testing changes all the time.

[gyrog]

How to install 'screener-1.0.1' on "dpup Bookworm64".

See this post:
viewtopic.php?p=106649#p106649

[radky]

BookwormPup64 10.0.4

• New Woof-CE build of BW64
• See first post for downloads and second post for changelog

[Sofiya]

BookwormPup64 10.0.4

[bigpup]

BookwormPup64 10.0.4 Changelog

• New kernel build (6.1.67) including upstream Debian fixes/updates (thanks dimkr and peebee)

Changing the kernel, if it is really fixing something in BookwormPup64, and this is the only way to fix it.
OK.
But are these fixes/updates for Debian or will it also fix some issue in BookwormPup64 that needed fixing?

But now, anyone that had to compile something that is kernel specific, is going to have to do it again, for v10.0.4.
If they have a topic posted, for what they compiled, and offer it to download.
It will not work in this v10.0.4.

Example:
My compiled Nvidia manufactures graphics hardware driver is not going to work in v10.0.4.
It was compiled for the kernel that is in v10.0.3. (6.1.55)

This is one reason, that it is not a good idea to change the kernel, after official stable release of a Puppy version.

[ozsouth]

Withdrawn - new version 10.0.5m uploaded 27Feb24.

[radky]

BookwormPup64 10.0.4 Changelog

• New kernel build (6.1.67) including upstream Debian fixes/updates (thanks dimkr and peebee)

Changing the kernel, if it is really fixing something in BookwormPup64, and this is the only way to fix it.
OK.
But are these fixes/updates for Debian or will it also fix some issue in BookwormPup64 that needed fixing?

But now, anyone that had to compile something that is kernel specific, is going to have to do it again, for v10.0.4.
If they have a topic posted, for what they compiled, and offer it to download.
It will not work in this v10.0.4.

Example:
My compiled Nvidia manufactures graphics hardware driver is not going to work in v10.0.4.
It was compiled for the kernel that is in v10.0.3. (6.1.55)

This is one reason, that it is not a good idea to change the kernel, after official stable release of a Puppy version.

@bigpup

Believe it or not, I devote long hours to improving BW64 for the larger complement of Puppy users -- not just for you. Older kernel releases may work OK for some users but not for others. For example, the Fujitsu S761 laptops of Puppy user @Marv (reported above) do not currently suspend properly with prior releases of kernel 6.1.x in BW64. With each kernel release, the upstream kernel developers will backport fixes to 6.1.x to address various issues. Hopefully, at some point the backported fixes will address important issues reported by Marv and other users of BW64.

Granted, compiling a new video driver for the updated kernel is inconvenient and DKMS can be hit or miss. Perhaps a better option for you is switching back to the 6.1.55 kernel that matches your compiled video driver.

[dancytron]

viewtopic.php?p=89536#p89536

I have an HP 15 Laptop https://support.hp.com/us-en/product/hp ... ku=N5Y09UA

It has a Radeon Display chip/card/whatever.

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] (rev 45)

When booting, it boots with the 800x600 vesa display and freezes hard on the 1st setup screen.

When booting to the console with pfix=nox, that works. When I run the xorg wizard and try anything but the default, X fails and goes back to the command prompt. The default freezes the same way as before. edit: also tried manually entering "radeon" and "radeon_b10" in the xorgwizard. /edit

My guess is a missing display driver or some kind of mesa.dri related file...

@dancytron

If I understand correctly, the Woof-CE generated firmware and 6.1.X kernel of BW64 (and Vanilla Dpup) are based on the content and configuration parameters currently employed by mainstream Debian 12 (Bookworm).

Debian Bookworm will be at 'Full Freeze' status on 24 May 2023, at which time software/firmware updates are essentially complete for the official release of Debian-12 on 10 Jun 2023.

A quick check of the fdrv of BW64-Beta1 suggests it already contains the Mullins iteration of Radeon firmware for the R4/R5 Graphics chipsets, but I don't know about specific support for revision 45. Even so, the next release of BW64 (Beta2) will contain any potential firmware updates concurrent with the official release of mainstream Debian Bookworm.

Maybe @dimkr will also reply.

I just installed it with the kernel_5.4.53_usrmerged.tar.gz in https://www.smokey01.com/radky/puppy-bookworm64/ instead of the default kernel. It loaded the display correctly and there was no lockup.

Just tested with the new version/kernel. Same error as before. It's something BW Puppy specific, it runs fine on BW debian dog and MX Linux. Don't waste your time on it.

Regarding kernels, I think one of the big advantages of overlay is that we can change kernels for little incompatibilities like mine and also for things like real time kernels or other specialty stuff. Fred has a "change kernel" utility in DD that might be close to just working.

[mikeslr]

bigpup, as you know two advantages of Puppys over Major Distros is that (1) they are designed as portables: you don't have to replace a functional OS with a newer version hoping it is better and (2) they employ a modular design: components --such as kernels-- can swapped. A third is that grub2config, frugalpup or manual editing of grub.cfg will quickly allow you to boot into a new Puppy.

Other than the time it takes to download an ISO, it takes very little time to setup a new Puppy without erasing you old. That's what I do. The old remains until I'm satisfied that the new is 'something better'.

In fact, only hardware specific applications require drivers specific to a kernel. If a new Puppy's kernel lacks the drivers needed by one's hardware, once the new Puppy has been deployed --tested and found lacking-- manual swapping in of a usable kernel, again, only takes a couple of minutes. Thereafter, you can wait to compile/have complied drivers or the availability of an even more recent kernel which has the ones you need.

At no time are you left with a non-functional operating system; or a new OS worse than your old.

[bigpup]

BookwormPup64 10.0.4
Frugal install on SSD drive
Using save folder.

Tried to compile the Nvidia driver using this driver package.
NVIDIA-Linux-x86_64-525.105.17.run

Downloaded and loaded the devx and kernel sources SFS's for v 10.0.4

The driver compiling process ends with no modules compiled and this error.

ERROR: You do not appear to have libc header files installed on your system. Please install your distribution's libc development package.

Any ideas on how to fix this error?

Note:
This is the Nvidia driver package, that did compile, under BookwormPup64 v10.0.3

I have a topic for a Nvidia driver for v10.0.3
I would like to make one for v10.0.4

[dimkr]

Any ideas on how to fix this error?

Code: Select all

apt install libc6-dev

[bigpup]

# apt install libc6-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libc6-dev is already the newest version (2.36-9+deb12u3).
libc6-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Isn't this saying it is already installed?

I am still learning apt and information it gives.

[dimkr]

Yes, this means it's installed. Try to install gcc.

[bigpup]

You know it is never just easy!

# apt install gcc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
gcc is already the newest version (4:12.2.0-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[dimkr]

What does gcc --version say?

[bigpup]

# gcc --version
gcc (Debian 12.2.0-14) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[bigpup]

I have seen some Nvidia driver packages not willing to compile, because what they are looking for to use is not located where they think it should be.

I will download and try a different Nvidia driver run package and see what that does.

Maybe try a newer one.

No help.

Get the same errors with a different Nvidia driver run package.

[Clarity]

Thought I remembered something recent in the kernel for nvidia cards (contributed by nvidia). Would a newer kernel address this? @dimkr and others may know.

I have 2 test PCs that are nvidia only to HDMI

Hope this is helpful info.