Bookworm Build script

[wiak]

Yes, I'm also wanting to move default to pipewire from pulseaudio. However, it remains a bit of a moving target in terms of configuration and ease. Newer pipewire packages are gradually making configuration easier, but sometimes moving default system config dirs for pipewire. Eventually I expect most config work simply to be automated on install, including pulseaudio removal. I think I'll wait a bit yet therefore to avoid having to do it all over again later.
Should be soonish though, since already default in Ubuntu with Gnome desktop (as is Wayland; but problem there is that lighter DEnvs like XFCE are not yet Wayland ready)

[dimkr]

You can find a complete recipe for running PipeWire with PulseAudio and ALSA compatibility in https://github.com/puppylinux-woof-CE/w ... initrc#L46. pavucontrol and Blueman work just fine and the transition should be seamless if you do something similar. (And screen capture works under Wayland, for both spot and root.)

In Puppy, .xinitrc starts a separate D-Bus session bus for spot, runs PipeWire and WirePlumber as spot (so applications run as spot can talk to them) under this instance, then forces applications running as root to use spot's instances (so root doesn't need its own PipeWire and WirePlumber instances, reducing RAM consumption).

[dancytron]

You can find a complete recipe for running PipeWire with PulseAudio and ALSA compatibility in https://github.com/puppylinux-woof-CE/w ... initrc#L46. pavucontrol and Blueman work just fine and the transition should be seamless if you do something similar. (And screen capture works under Wayland, for both spot and root.)

In Puppy, .xinitrc starts a separate D-Bus session bus for spot, runs PipeWire and WirePlumber as spot (so applications run as spot can talk to them) under this instance, then forces applications running as root to use spot's instances (so root doesn't need its own PipeWire and WirePlumber instances, reducing RAM consumption).

That's basically what the "system" mode does when it runs as root in pulse audio, force it to run as a separate user.

It looks like "system" mode is going to be deprecated for pipewire. It's a compile option, which isn't in the default debian version, which makes it really impractical for Debian Dog.

[dimkr]

It looks like "system" mode is going to be deprecated for pipewire.

That's why Puppy runs it in "session" mode. In addition to the clear future-proofness and portability benefits of not running it in "system" mode, Puppy uses a single "session" instance for both root and spot, something nice to have in any lightweight distro that runs applications as root. PipeWire is 3 processes (pipewire, pipewire-pulse and wireplumber), each with many dependencies (some big), so the saving are not negligible.

[fredx181]

*** Updated Bookworm Build script *** (attached at first post)

Important change:
- Debian has now a separate repository for nonfree firmware: non-free-firmware
Added it in the script to be able to use it.
For an existing build, change in /etc/apt/sources.list:
deb http://deb.debian.org/debian bookworm main contrib non-free
To (add "non-free-firmware"):
deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
(also added this change to updated "repo-conf" (1.0.3) package in custom repository)

Other changes:
- No prompt anymore during build for yes/no overwriting (custom) /etc/rc.local
- The Desktop environment chosen (DE_CONFIG variable) now added to the "build_setup.conf" file.

Btw, now that the "soft freeze" has happened for Bookworm, I don't expect any unpleasant surprises anymore running the build script (and mid of this year Bookworm becomes the "stable" branch).

[dcung]

*** Updated Bookworm Build script *** (attached at first post)

I refreshed my ISOs with the new script.
All completed okay, except I noticed something I thought to report in case it's of significance.

I usually make one ISO with systemd (I made a DDOG with systemd).
And when systemd is checked, I saw this.
(Others without systemd, don't have this messages).


Creating isodata/live/01-filesystem.squashfs...
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on isodata/live/01-filesystem.squashfs, block size 524288.
[==========================================================| ] 29384/29454 99%
Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_default
[===========================================================/] 29454/29454 100%

Code: Select all

Now we will create compressed kernel: k-6.1.0-6-amd64.squashfs and filesystem: '01-filesystem.squashfs'
Please enter your choice, xz compression will give smaller size than gzip,
but xz takes much longer time to compress
Creating kernel .squashfs isodata/live/k-6.1.0-6-amd64.squashfs . . .
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on isodata/live/k-6.1.0-6-amd64.squashfs, block size 524288.
[=============================================================/] 4378/4378 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 524288
	compressed data, compressed metadata, compressed fragments,
	compressed xattrs, compressed ids
	duplicates are removed
Filesystem size 83238.20 Kbytes (81.29 Mbytes)
	16.94% of uncompressed filesystem size (491414.32 Kbytes)
Inode table size 38980 bytes (38.07 Kbytes)
	24.46% of uncompressed inode table size (159372 bytes)
Directory table size 47348 bytes (46.24 Kbytes)
	43.87% of uncompressed directory table size (107937 bytes)
Number of duplicate files found 0
Number of inodes 4917
Number of files 4035
Number of fragments 657
Number of symbolic links  0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 882
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)
Creating isodata/live/01-filesystem.squashfs...
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on isodata/live/01-filesystem.squashfs, block size 524288.
[==========================================================| ] 29384/29454  99%
Unrecognised xattr prefix system.posix_acl_access

Unrecognised xattr prefix system.posix_acl_default
[===========================================================/] 29454/29454 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 524288
	compressed data, compressed metadata, compressed fragments,
	compressed xattrs, compressed ids
	duplicates are removed
Filesystem size 469844.91 Kbytes (458.83 Mbytes)
	29.18% of uncompressed filesystem size (1610365.11 Kbytes)
Inode table size 306010 bytes (298.84 Kbytes)
	23.80% of uncompressed inode table size (1285517 bytes)
Directory table size 338474 bytes (330.54 Kbytes)
	38.71% of uncompressed directory table size (874423 bytes)
Xattr table size 40 bytes (0.04 Kbytes)
	100.00% of uncompressed xattr table size (40 bytes)
Number of duplicate files found 2400
Number of inodes 37479
Number of files 27392
Number of fragments 869
Number of symbolic links  5802
Number of device nodes 8
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 4277
Number of ids (unique uids + gids) 19
Number of uids 8
	root (0)
	unknown (42)
	unknown (997)
	puppy (1000)
	unknown (1002)
	_apt (100)
	unknown (998)
	man (6)
Number of gids 15
	root (0)
	dip (30)
	shadow (42)
	netdev (106)
	dialout (20)
	puppy (1002)
	unknown (998)
	tty (5)
	ssl-cert (105)
	utmp (43)
	staff (50)
	unknown (108)
	adm (4)
	unknown (999)
	mail (8)
OK

Finally creating ISO...
xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:../DebLive_bookworm-amd64.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 58.2g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/mnt/sda4/Bookworm/bookworm/isodata'
xorriso : UPDATE :      18 files added in 1 seconds
xorriso : UPDATE :      18 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file '/usr/lib/ISOLINUX/isohdpfx.bin'
libisofs: NOTE : Aligned image size to cylinder size by 389 blocks
xorriso : UPDATE :  6.43% done
xorriso : UPDATE :  57.21% done
ISO image produced: 288768 sectors
Written to medium : 288768 sectors at LBA 0
Writing to 'stdio:../DebLive_bookworm-amd64.iso' completed successfully.

OK

Finished! If all went well, DebLive_bookworm-amd64.iso has been created. 
Also the required files for a frugal install are in isodata 'live' folder 

Have a good day!

root@live:/mnt/sda4/Bookworm# 

[fredx181]

I usually make one ISO with systemd (I made a DDOG with systemd).
And when systemd is checked, I saw this.
(Others without systemd, don't have this messages).


Creating isodata/live/01-filesystem.squashfs...
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on isodata/live/01-filesystem.squashfs, block size 524288.
[==========================================================| ] 29384/29454 99%
Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_default
[===========================================================/] 29454/29454 100%

Thanks, yes it's systemd related, did some digging and found here how to find "acl" files: https://superuser.com/questions/398448/ ... h-acls-set
In the "bookworm" directory (where chroot is inside) (and found chroot/var/log/journal) :

Code: Select all

root@live:/mnt/live/mnt/nvme0n1p3/bookworm# getfacl -R -s -p chroot  | sed -n 's/^# file: //p'
chroot/var/log/journal

Or : ls -l chroot/var/log/

Code: Select all

.....
.....
 ls -l drwxr-sr-x+ 2 root  999   4096 mrt 16 10:48 journal
....

Note the '+' , mksquashsfs cannot handle these files

But long story short: Not a problem, as in the booted system the '+' is back for the /var/log/journal directory.

[soniabu]

Open a terminal and type: xrandr -o inverted

Then flip the laptop over. Does it work properly now?

To restore it, type: xrandr -o normal

rcrsn,
now I managed to invert the screen with the commands you suggested.
For some purposes it is useful to me. Unfortunately, however, a good percentage of the touchscreen functions
are lost and all this compromises the general use of the Lenovo PC.
I'll see later if it's me in the inverted context incapacitated or a degradation of the laptop's functions.
Thanks anyway for the help
sonia

[gumanzoy]

Hi Fred.

I try to build with my Xfce config. I see some unwanted packages.
That cause by conky
I remove it and get -23MB to 01-filesystem.squashfs
In Bookworm libimlib2 depends on libheif1 and libspectre1
Maybe it would be nice to rebuild libimlib2 without it.

Code: Select all

root@live:~# apt-get install conky
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
...
The following NEW packages will be installed:
  conky conky-std fonts-urw-base35 libaom3 libdav1d6 libde265-0 libgif7
  libgs-common libgs10 libgs10-common libheif1 libhwy1 libidn12 libijs-0.35
  libimlib2 libjbig2dec0 libjxl0.7 liblua5.3-0 libnuma1 libopenjp2-7 libpaper1
  libspectre1 libwebpdemux2 libx265-199 poppler-data xfonts-encodings
  xfonts-utils
0 upgraded, 27 newly installed, 0 to remove and 1 not upgraded.
Need to get 23.1 MB of archives.
After this operation, 90.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

root@live:~# apt-get install libimlib2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
...
The following NEW packages will be installed:
  fonts-urw-base35 libaom3 libdav1d6 libde265-0 libgif7 libgs-common libgs10
  libgs10-common libheif1 libhwy1 libidn12 libijs-0.35 libimlib2 libjbig2dec0
  libjxl0.7 libnuma1 libopenjp2-7 libpaper1 libspectre1 libwebpdemux2
  libx265-199 poppler-data xfonts-encodings xfonts-utils
0 upgraded, 24 newly installed, 0 to remove and 1 not upgraded.
Need to get 22.4 MB of archives.
After this operation, 88.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

root@live:~# apt-get install libheif1 libspectre1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
...
The following NEW packages will be installed:
  fonts-urw-base35 libaom3 libdav1d6 libde265-0 libgs-common libgs10
  libgs10-common libheif1 libidn12 libijs-0.35 libjbig2dec0 libnuma1
  libopenjp2-7 libpaper1 libspectre1 libx265-199 poppler-data xfonts-encodings
  xfonts-utils
0 upgraded, 19 newly installed, 0 to remove and 1 not upgraded.
Need to get 20.6 MB of archives.
After this operation, 82.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

[fredx181]

Hi Fred.

I try to build with my Xfce config. I see some unwanted packages.
That cause by conky
I remove it and get -23MB to 01-filesystem.squashfs
In Bookworm libimlib2 depends on libheif1 and libspectre1
Maybe it would be nice to rebuild libimlib2 without it.
...

Yes, I see, conky with all dependencies became very big now.
Always difficult and tricky to interfere with the very strict Debian package management, so I would recommend not to do, but anyway... tried some trickery.
The libimlib2 from Bullseye doesn't have that much dependencies, so here's modified libimlib2_1.7.1-2_amd64.deb (made it version 1:1.7.1-2, the '1:' at the front of the version is trick it to make that dpkg *thinks* it's newest)
https://doglinux.github.io/book-worm/libimlib2/
To try, first install the other debs (libtiff5 and libwebp6) and then libimlib2.
Just for testing, experimental, cannot predict the consequences in the long term.
Perhaps you have idea ?

[gumanzoy]

Yes, I see, conky with all dependencies became very big now.
Always difficult and tricky to interfere with the very strict Debian package management, so I would recommend not to do, but anyway... tried some trickery.
The libimlib2 from Bullseye doesn't have that much dependencies, so here's modified libimlib2_1.7.1-2_amd64.deb (made it version 1:1.7.1-2, the '1:' at the front of the version is trick it to make that dpkg *thinks* it's newest)
https://doglinux.github.io/book-worm/libimlib2/
To try, first install the other debs (libtiff5 and libwebp6) and then libimlib2.
Just for testing, experimental, cannot predict the consequences in the long term.
Perhaps you have idea ?

I don't use conky. And i remove it from my build for now.

Another question. thunar_4.16.1-1_amd64.deb
Maybe need to update package in repo to 4.18 ?

[fredx181]

....
Another question. thunar_4.16.1-1_amd64.deb
Maybe need to update package in repo to 4.18 ?

Thanks !, yes, forgot about that, added 4.18 to custom repo now, I compiled thunar with "no root warning" patched, it's version 1:4.18.4-1 and will override the official Debian version.
Still you can install the Debian version if preferred (has root warning) apt install thunar=4.18.4-1 (will be seen as downgrade though).

Lots of changes in Bookworm compared to Bullseye, e.g. gtk2 less supported, python2 in fact not supported anymore (all python3 now), but added minimal python2 support in custom repo.
Also it seemed that forcing "usr-merged" system can't be avoided.
Hard to keep up with all these changes. So there may be some things unexpected.

[gumanzoy]

Thanks !, yes, forgot about that, added 4.18 to custom repo now, I compiled thunar with "no root warning" patched, it's version 1:4.18.4-1 and will override the official Debian version.

Lots of changes in Bookworm compared to Bullseye, e.g. gtk2 less supported, python2 in fact not supported anymore (all python3 now), but added minimal python2 support in custom repo.
Also it seemed that forcing "usr-merged" system can't be avoided.
Hard to keep up with all these changes. So there may be some things unexpected.

Thanks.

I almost finish my Bookworm build. Need some more testing.
Not so much config changes need compare to Bullseye.
I expect problems with "usr-merged". But no see any trouble.

[fredx181]

...
I expect problems with "usr-merged". But no see any trouble.

As far as I know the only problem that may arise is if added an extra .squashfs module loaded (at boot) contains a regular directory e.g. /lb or /bin (rather than a symlink) , then boot will fail because of that.
Doesn't go for .deb packages, if it contains regular /lb or /bin dir it's fine, apt or dpkg can handle it.

[fredx181]

*** Updated Bookworm build system ***

Appimages maintained again (for to use on Puppy or other NOT Debian(dog) systems), I tested on FossaPup and KLV-Airedale, has dependencies included, download and info:
https://debiandog.github.io/MakeLive/Re ... rmdog.html
edit: ...............................
There were some reports in the past that running it on Puppy there was an error because of libgtk3-nocsd not found.
Should be fixed now, as libgtk3-nocsd0 will be installed initially by the debootstrap process.
.....................
(note: running from a "gvfs mounted" partition may fail, see here: viewtopic.php?p=88394#p88394)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Small change in the mklive-bookworm script:
- User 'puppy' gets now the uid 1000
(instead of previously being 1002 (1000 is better IMO for the main unprivileged user)
If always running the system logged in as root, this update is not of much value, btw.
Re-attached mklive-bookworm at first post.

Now that Bookworm will become the 'stable' branch soon, I don't expect major problems running the build script, but y'll never know .

[fredx181]

I noticed on Bookworm that the RAM amount 'used', as free or top or conky show, is very much higher than it was before (e.g. on Bullseye or Buster), double or even more!
This has to do with the newest "procps" package (2:4.0.2-3) (which includes free, top ).

Htop and task-manager show the *correct* amount, btw. (but I'm not really sure what is 'correct' these days ).

To change to 'correct' RAM usage display, install a slightly older procps:

Install both these packages (version 2:3.3.17-7.1) (edit: install first libprocps8):
libprocps8: https://github.com/doglinux/book-worm/r ... _amd64.deb
procps: https://github.com/doglinux/book-worm/r ... _amd64.deb

To prevent upgrading put it on hold:
apt-mark hold procps

[dancytron]

Just built a systemd Chromedog with everything the default but some extra drivers.

All went well, sound worked both with root and puppy running Chrome after picking the correct sound card for each user using Bill's sound-card-selector script to select the soundcard for each user (used "su puppy" in the terminal to set it for the puppy user).

[fredx181]

I noticed on Bookworm that the RAM amount 'used', as free or top or conky show, is very much higher than it was before (e.g. on Bullseye or Buster), double or even more!
This has to do with the newest "procps" package (2:4.0.2-3) (which includes free, top ).

Htop and task-manager show the *correct* amount, btw. (but I'm not really sure what is 'correct' these days ).

To change to 'correct' RAM usage display, install a slightly older procps:

Install both these packages (version 2:3.3.17-7.1) (edit: install first libprocps8):
libprocps8: https://github.com/doglinux/book-worm/r ... _amd64.deb
procps: https://github.com/doglinux/book-worm/r ... _amd64.deb

To prevent upgrading put it on hold:
apt-mark hold procps

As I see no problems with this older procps, I have now added these packages (v3.3.17-7.1) to the custom repo and will be seen as newest (so when doing e.g. apt upgrade this version will be in installed and htop, free, top, lxtask and conky will all show the same memory usage).
After installed:

Code: Select all

root@live:~# apt-cache policy procps
procps:
  Installed: 3:3.3.17-7.1
  Candidate: 3:3.3.17-7.1
  Version table:
 *** 3:3.3.17-7.1 500
        500 https://github.com/doglinux/book-worm/raw/master/amd64 ./ Packages
        100 /var/lib/dpkg/status
     2:4.0.2-3 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages

If preferred newest from deb.debian.org (2:4.0.2-3), do apt install procps=2:4.0.2-3

[gumanzoy]

As I see no problems with this older procps, I have now added these packages (v3.3.17-7.1)
If preferred newest from deb.debian.org (2:4.0.2-3), do apt install procps=2:4.0.2-3

I use
cpu-x (4.5.2-2) it depends on
libproc2-0 (>= 2:4.0.2)
I need to don't forget about it, when i next time rebuild 01-filesystem.squashfs of by build.

[fredx181]

As I see no problems with this older procps, I have now added these packages (v3.3.17-7.1)
If preferred newest from deb.debian.org (2:4.0.2-3), do apt install procps=2:4.0.2-3

I use
cpu-x (4.5.2-2) it depends on
libproc2-0 (>= 2:4.0.2)
I need to don't forget about it, when i next time rebuild 01-filesystem.squashfs of by build.

There should not be a problem with cpu-x (or other package depending on libproc2-0) as libproc2-0 (2:4.0.2) will still be installed (so then libprocps8 and libproc2-0 are both installed).

Code: Select all

root@live:~# apt install cpu-x
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libcpuid16 libglfw3 libproc2-0
Suggested packages:
  libgles1 libgles2 libosmesa6
The following NEW packages will be installed:
  cpu-x libcpuid16 libglfw3 libproc2-0
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 1,871 kB of archives.
After this operation, 3,862 kB of additional disk space will be used.
Do you want to continue? [Y/n] 

[fredx181]

I am having a problem with the newest kernel on Bookworm (6.1.0-8 and 6.1.0-9) when trying to set monitor resolution to something other than the default (for me 1920x1080, then changing to 1600x900) results in crashing X and unresponsive keyboard. Got this problem on Devuan Daedalus too, btw.
Anyone else experiencing this ? (edit: or not ?)
With kernel 6.1.0-7 (and earlier) it was OK for me.
EDIT: Used 'Monitor settings' from menu (lxrandr) but also tested "Display settings" on a XFCE build, same problem.

[dcung]

I refreshed my bookworm ISOs collection using latest mklive (from page 1).
I don't use bookworm.
Still using buster/bullseye on most of my laptops.

Anyone else experiencing this ? (edit: or not ?)

I tested bookworm-ddog on 2 laptops.
It does not look like I experienced it (kernel 6.1.0-9).

Samsung NP740U3 - default 1920x1080
Fujitsu S962 - default 1366x768

Note - I didn't do extensive tests. Just switching resolutions to see X crashes, and it didn't, all seems to work fine only lower/uglier resolution.

[fredx181]

I refreshed my bookworm ISOs collection using latest mklive (from page 1).
I don't use bookworm.
Still using buster/bullseye on most of my laptops.

Anyone else experiencing this ? (edit: or not ?)

I tested bookworm-ddog on 2 laptops.
It does not look like I experienced it (kernel 6.1.0-9).

Samsung NP740U3 - default 1920x1080
Fujitsu S962 - default 1366x768

Note - I didn't do extensive tests. Just switching resolutions to see X crashes, and it didn't, all seems to work fine only lower/uglier resolution.

Thanks, good to know. It seems my "newish" Asus laptop doesn't like kernel 6.1.0-8 (or higher) for some reason (that I don't know yet).

[gumanzoy]

Thanks, good to know. It seems my "newish" Asus laptop doesn't like kernel 6.1.0-8 (or higher) for some reason.

Model name ? GPU ?
I can look for similar hardware.
I try to reproduce on some machines but change resolution work ok with 6.1.0-8.

[fredx181]

Thanks, good to know. It seems my "newish" Asus laptop doesn't like kernel 6.1.0-8 (or higher) for some reason.

Model name ? GPU ?
I can look for similar hardware.
I try to reproduce on some machines but change resolution work ok with 6.1.0-8.

Thanks, it's this one:
https://www.amazon.com/ASUS-Blacklit-Ke ... B09NVXQXRZ

[fredx181]

Thanks, good to know. It seems my "newish" Asus laptop doesn't like kernel 6.1.0-8 (or higher) for some reason.

Model name ? GPU ?
I can look for similar hardware.
I try to reproduce on some machines but change resolution work ok with 6.1.0-8.

Thanks, it's this one:
https://www.amazon.com/ASUS-Blacklit-Ke ... B09NVXQXRZ

Did lots of searching on the web but couldn't find a real solution for the (total) freeze problem after setting resolution with xrandr.
But I could workaround it by creating a simple xorg.conf (and resolution 1600x900 is OK at boot):

Code: Select all

Section "Screen"
    Identifier  "Screen 1"
    DefaultDepth 24

    Subsection "Display"
        Depth       24
        Modes        "1600x900" "1360x768" "800x600"
        ViewPort    0 0
    EndSubsection
EndSection

[dancytron]

I am having a problem with the newest kernel on Bookworm (6.1.0-8 and 6.1.0-9) when trying to set monitor resolution to something other than the default (for me 1920x1080, then changing to 1600x900) results in crashing X and unresponsive keyboard. Got this problem on Devuan Daedalus too, btw.
Anyone else experiencing this ? (edit: or not ?)
With kernel 6.1.0-7 (and earlier) it was OK for me.
EDIT: Used 'Monitor settings' from menu (lxrandr) but also tested "Display settings" on a XFCE build, same problem.

I do get this in Radky's Bookworm Puppy. A longshot, but maybe related???

I'll have to look and see what the kernel is on the last bookworm I built, which worked fine.

viewtopic.php?p=89536#p89536

[dancytron]

I'm on kernel 6.1.0-7 right now and it works for me on my laptop (the new Debian bookworm puppy doesn't).

I'm going to build another one with the latest kernel and see if I get similar issues.

[dancytron]

I am having a problem with the newest kernel on Bookworm (6.1.0-8 and 6.1.0-9) when trying to set monitor resolution to something other than the default (for me 1920x1080, then changing to 1600x900) results in crashing X and unresponsive keyboard. Got this problem on Devuan Daedalus too, btw.
Anyone else experiencing this ? (edit: or not ?)
With kernel 6.1.0-7 (and earlier) it was OK for me.
EDIT: Used 'Monitor settings' from menu (lxrandr) but also tested "Display settings" on a XFCE build, same problem.

I just built a DD Bookworm with the latest -9 kernel. Posting from it now.

It boots, but to the 800x600 screen just like Puppy Bookworm, but doesn't freeze.

xrandr and the monitor settings program only sees 800x600.

Something is up with it.

[fredx181]

xrandr and the monitor settings program only sees 800x600.

That's bad ! Hopefully it will be fixed with later kernel versions.

EDIT: As I said in the BookwormPup64 thread, on my 15 years old HP laptop I'm having no problems at all with latest kernel, weird !

EDIT2: When you have time, can you try creating xorg.conf similar as I did viewtopic.php?p=89499#p89499 but with your preferred resolution as being first (at Modes line) ?