BookwormPup64 10.0.8

[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.

[sonny]

BW64 provides legacy FrugalPup installers but also supports external installers such as Unebootin and Rufus when creating bootable USB media in UEFI and MBR modes. However, BW64 does not support Ventoy.

What did you mean by "BW64 does not support Ventoy?"

Ventoy does boot BW64 but it does not fully function in Ventoy?

[galen]

BW64 provides legacy FrugalPup installers but also supports external installers such as Unebootin and Rufus when creating bootable USB media in UEFI and MBR modes. However, BW64 does not support Ventoy.

What did you mean by "BW64 does not support Ventoy?"

Ventoy does boot BW64 but it does not fully function in Ventoy?

problems I've had with Ventoy [on fat32 USB]
is that it will not allow saving of savefile due to read-only mounted Ventoy boot partition
even though you can mount all sorts of partitions with live puppy and try them at savefile process
or it simply fails or crashes to console at savefile prompt with error -1024kb space needed.
Does anyone have a working Ventoy + puppy + save combo?

[Clarity]

Hello @radky and @rockedge for this upgraded v1004 offering.

I default booted. via SG2D, pristine. Did some initial cosmetics, saved the session at Shutdown. Upon reboot, v1004 found its sessions and went to desktop (So SAVESPEC processing during INIT works perfectly).

Sweet

I have a comment, and a couple request for help

Comment: This is NOT a request for action
When the Menu>Setup>Package Manager (Legacy) program is run, it has a nice area on its left where a notification is presented alerting the user to use the other PM...for good reason. But the verical layout of the screen could benefit from heightened 'real estate' so that the message, all of it, is readily displayed. As it is partial displayed, currently, it could be overlooked by PUP users.

Requests The steps to do so in all FossaPUP64 are different here in BWPup64 v1004

• Sound - we need an app or a right click on taskbar speaker that allow an alternate selection of output as well as a button to test for sound when a selection is made. Is this present?

• System Video - is there a recommended way in v1004 to change from modesetting driver to an nvidia driver, OOTB?

Performance is smooth, and rapid in testing thus far.

My next steps are to add the excellent PET packages that @ETP has made for use as well as to add his GetChrome PET to the system.

Thanks muchly for this great feat.

PPM.jpg (41.47 KiB) Viewed 5028 times

[keniv]

I've recently updated to v10.0.4. I have usually updated before by using the save file (yes I still use them) from the previous version then building a new clean save file for the new update i.e. I tried to use the save file from v10.0.3 in v10.0.4. However, I found that the 10.0.3 save file was named as dpupsave- ????.4sf and was not recognised. The new 10.0.4 save file was named dpupbw64save-????.4fs. When I renamed the 10.0.3 save file to the form of the new 10.0.4 it did work. Can I ask if this renaming was to prevent the use of save files from previous versions?
I've also noticed that in a "clean" version of 10.0.4 on using the terminal on the desktop that previous commands used are not retained. I've normally been used to using the pointer up and down keys to scroll through previously used commands. I find this useful. Is this a property of this particular terminal and if so can it be changed to allow scrolling through previously use commands. In Menu>Utility you can select LXTerminal which does have this facility. I know I could select it as the default terminal but it seems odd to me that the terminal on the desktop does not work in this way.
I have to say that overall I really do like BookwormPup64. It's fast becoming my daily driver. I particularly like being able to use some older .pets as well as synaptic. I have an interest in software defined radio. I use GQRX for this. Previously I've had problems installing this from .pets particularly with sound (it expects pulse). I installed it using synaptic and everything worked smoothly out of the box.

Regards,

Ken.

[MochiMoppel]

urxvt bug

There appears to be a bug in the urxvt setup.
From a terminal I try to open an urxvt window with dimension 20 chars wide and 1 char high, using command urxvt -g 20x1
Though the window is created, it creates a stream of error messages.
Less errors when using a 2 char height urxvt -g 20x2 and no error with 3 chars or more.

This behavior can be fixed by disabeling the perl extension. In /root/.Xdefaults comment out the respective line by preceding an exclamation mark:

Code: Select all

! urxvt.perl-ext-common: default,selection-to-clipboard,tabbed,matcher

This is fine with me because I don't like this extension anyway, but many users like it and there should be a better way.

urxvt_bug.png (129.16 KiB) Viewed 4880 times

[Clarity]

Hi @keniv... DoNOT take any of my responses as official. I am NOT the developer. But I can offer couple thoughts.

... Can I ask if this renaming was to prevent the use of save files from previous versions?

I 'think' this change is a good one as it seems to intend to distinguish this distro to be different from other developers doing similar distros for 32bit versions and other debian versions of this WoofCE PUP.

... I've normally been used to using the pointer up and down keys to scroll through previously used commands. ...

I ask, no matter which terminal you use, to also observe the "history' cli command in each. This response doesn't address the problem you're drawing attention to, but is useful to see if the terminal being used is recording its command history.

Hope this is helpful

[wizard]

@keniv

I've also noticed that in a "clean" version of 10.0.4 on using the terminal on the desktop that previous commands used are not retained. I've normally been used to using the pointer up and down keys to scroll through previously used commands

In my clean install of 10.0.04, the default terminal on the desktop is LXTerminal in which the up/down arrows show the history.

Also, if I use URxvt terminal from the menu, up/down arrows show the history.

Checked 10.0.02 and 10.0.03 and could not duplicate your issue.

For reference, you should also be able to show the history by pressing:
Ctrl p for previous
Ctrl n for next

Up/down arrows not working might be corrected by adding these two line to ~/root/.bashrc:
bind '"\e[A":history-search-backward'
bind '"\e[B":history-search-forward'

I have not tried this since mine is working correctly.

wizard

[keniv]

@wizard

In my clean install of 10.0.04, the default terminal on the desktop is LXTerminal in which the up/down arrows show the history.

Thanks for that piece of information because it pointed me towards a mistake that I must have made. I checked my clean install of 10.0.4. The desktop terminal icon does point to the default terminal. When I opened /usr/local/bin/defaultterminal I see exec lxterminal "$@" so LXTerminal is the default. I opened LXTerminal from the desktop, typed in a couple of commands then checked that these commands were retained by using the up and down arrows. To my surprised this now worked. Ctrl p and Ctrl n also worked. I closed the terminal then re-opened it again, repeated the above and everything worked. I then tried 10.0.4 with the save file from 10.0.3. When I opened the terminal from the desktop it seemed to open the LXTerminal. Doing the same tests as before I could use the up and down arrows to go between commands, however, if I closed the terminal then re-opened it the previous commands were gone. The arrow keys no longer worked and neither did
Ctrl p and Ctrl n. I think my problem with the terminal was due to me mistakenly selecting the the older save file when I though I'd selected the new clean save file. I'm sorry that I appear to have wasted peoples time with this. Thanks again for the help.

Ken.

[wizard]

@keniv

I'm sorry that I appear to have wasted peoples time with this. Thanks again for the help.

No waste of time, I've found reusing save file/folders between versions can sometimes produce small unwanted issues such as yours. We all learn from it.

wizard

[retiredt00]

Dear Radky
My old Apple laptop fails to suspend on lid-closure with Bookworm 10.0.4
The "suspend.sh" script works fine when called directly.
When closing the lid the "udevadm monitor" reports nothing indicating that the signal is not detected by the kernel.
Also "lsmod" indicates that "hwmon" module does not depend/uses on "applesmc" module even when the module is loaded.
Interestingly the "applesmc" module is NOT loaded when booting a clean bookworm64 build.
Adding the modules in dpupbw64initmodules.txt does not change the lid behavior or hwmon association.
I should also mention that this is a HD installation without any peripherals added to the machine.

I should point out that the same laptop suspends fine with FatDog901, loads "applesmc" automatically and "hwmon" utilizes it fine.
Looking at modules.dep in FatDog "applesmc" depends on "hwmon" but not in Bookworm.
Also in Bookworm "hwmon" is builtin but in FatDog a module
So it might be a kernel configuration
I should point out that dpup10.0.44 has the same suspend issue
I hope that a future kernel will be build with a configuration that will solve this issue (assuming is a kernel issue)
Thanks for you efforts and happy new year.

[bigpup]

Anyone having Nvidia graphics hardware.

ETP has been able to make a pet package of a Nvidia driver for use with BookwormPup64 10.0.4

It should support Nvidia hardware most people are going to have.

You can get it from this topic:
viewtopic.php?t=9884

[OscarTalks]

Is anyone able to play DVD's in BookwormPup64 10.0.4 ?
Just did a frugal in an oldish desktop computer and DVD's would not play at all by clicking on the drive or by opening from within SMPlayer.
Messages in the error log mentioned "no css available" and normally I would expect to see libdvdcss in system, but it wasn't there. I downloaded the latest source of libdvdcss (from Videolan) and compiled it. DVD's do then play, but not sure if everything is as it should be. I hardly ever play DVD's myself. Perhaps there is an "official" way of installing this library via apt or something? Anyway, maybe needs investigating?
Attaching .pet of the library in case it is of any help.
EDIT:- Library with split-off DEV package now posted a little bit further down the thread.

[wizard]

@OscarTalks

Just did a clean boot on 10.0.4 and clicking dvd icon plays in mpv, also smplayer opens and plays dvd correctly.

EDIT: above test was with a DVD that did not have CSS, testing a protected DVD gave the same results as yours, would not play.

Thanks for the pet file

wizard

[OscarTalks]

Hello wizard,
Thanks for the response. I wonder if you are doing something different or maybe your DVD is different from the ones I tried. Earlier I was installing BookwormPup64 in a machine for somebody else. Now back home and if I put a (film) DVD in the drive I get sr0 as the icon for it. Clicking that gives the dialog box "This seems to be a DVD, do you want to play it?" and if I try to play it nothing happens. If I open SMPlayer and do Open>Disc>DVD_from_drive it gives me an "Ooops..." error box.

Debian do not seem to offer libdvdcss as one of their own packages for bookworm. Instead there is a package which is supposed to download and compile some third party stuff including that library. As I said, I don't usually play DVD's at all, but when somebody asked me and I tried to play one it didn't work, so I think something needs to be added if it is possible to work out exactly what and how best to do it.