Moderator: fredx181
*** Updated mklive-sid build system ***
Change: Added Mate Desktop to the Desktop Environment choices. (see more info and screenshots here (Bullseye): viewtopic.php?p=31907#p31907 )
Attached at first post "mklive-sid' script for to use on DebianDog (or any other true DEB based OS)
Appimages, recommended to use on Puppy (and other OS's), see here: https://debiandog.github.io/MakeLive/Re ... d-sid.html
Fred
*** Sid Build Script updated ***
New attached mklive-sid at first post
Fixed problem that the build couldn't finish because of conflicting packages.
Was caused by the fact that some python2 related packages aren't updated anymore and replaced by python3.
I expect in the future that some packages depending on python2 (and somehow won't run with python3) will stop working.
Other changes:
- Changes for when running with -gui and -cli Same as described here: viewtopic.php?p=37892#p37892 (for Bullseye).
- Added choice to run with systemd or without
EDIT: Here's a kernel "package", 64-bit kernel from Sid v5.14 : https://github.com/doglinux/sid/release ... d64.tar.gz
Perhaps can be useful for someone to run v5.14 on Bullseye, extract in the "live" folder.
EDIT2: 15 oct, Appimages updated as well now.
Fred
Long time no comments here. So I want want to leave one.
I use DebianDog Sid every day without problems. Update it from time to time. No problems at all.Simply works day in day out.
Thanks again to Fred and all other contributors.
Payoon
Hi all,
Just wonder how can I change/disable blank screen timeout in Debiandog bullseye/sid. My pc is pretty old, after it goes into sleep, it takes quite a long time to be woken up (>10 sec after hit kb or click/move mouse).
Thanks in advance and Happy Easter!
chester
This should work: xset s off && xset -dpms # Turn off screen blanking
To run at start put it in ~/.xsession (before exec openbox-session) or add script in ~/Startup containing it.
it works perfectly.
Thanks a lot, Fred!
chester
Hi Fred,
I was curious and wanted to know if Sid installs legacy nvidia driver 340.
I used mklive-sid from first page of this thread (removed fake .gz).
I built Xfce4 Whisker minimal build. But when I ran it showed "Bullseye" (?).
So, I chose another build, DebianDog Full_openbox_Xfce-Jwm. This one showed "Sid".
Anyway - I got the answer. It installed legacy nvidia driver 340 okay.
I just thought I report it. I built the minimal build twice, and it shows "Bullseye" both times.
dcung wrote:I just thought I report it. I built the minimal build twice, and it shows "Bullseye" both times.
Thanks, yes, it's a mistake I made.
Sort of fixed now, bit of a workaround though, but should be OK now when doing new build.
Added to ~/Startup this script 'sid-conky-fix' that will change the conky display:
Code: Select all
#!/bin/bash
if cat /etc/debian_version | grep -q sid ; then
if grep -q 'Bullseye $nodename on $machine' $HOME/.conkyrc-port; then sed -i 's/Bullseye/Sid/' $HOME/.conkyrc-port; fi
if grep -q 'Bullseye $nodename on $machine' $HOME/.conkyrc-live; then sed -i 's/Bullseye/Sid/' $HOME/.conkyrc-live; fi
fi
Just run it on an existing Sid build for change to Sid at conky view (or edit the .conkyrc files manually).
If there are more bugs found, I'll make a "real" fix for this (needs to modify the mklive-sid script, appimages and content on Github, I'm lazy atm 
)
Hi Fred,
After I found out that Sid installed legacy nvidia 340 driver, I have been tinkering with Sid a little more.
I tried to install Broadcom Sta driver, and got the following error (and log file attached).
Does that Deprecated feature: REMAKE_INITRD mean no longer possible to install this driver?
apt-get update
apt-get install linux-headers-$(uname -r)
apt install broadcom-sta-dkms
Code: Select all
root@live:~# apt install broadcom-sta-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
broadcom-sta-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,208 kB of archives.
After this operation, 14.5 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/non-free amd64 broadcom-sta-dkms all 6.30.223.271-17 [2,208 kB]
Fetched 2,208 kB in 1s (1,656 kB/s)
Selecting previously unselected package broadcom-sta-dkms.
(Reading database ... 52166 files and directories currently installed.)
Preparing to unpack .../broadcom-sta-dkms_6.30.223.271-17_all.deb ...
Unpacking broadcom-sta-dkms (6.30.223.271-17) ...
Setting up broadcom-sta-dkms (6.30.223.271-17) ...
Loading new broadcom-sta-6.30.223.271 DKMS files...
Deprecated feature: REMAKE_INITRD
Building for 5.17.0-1-amd64
Building initial module for 5.17.0-1-amd64
Deprecated feature: REMAKE_INITRD
Error! Bad return status for module build on kernel: 5.17.0-1-amd64 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@live:~#
dcung wrote: Sun Apr 24, 2022 11:22 pmHi Fred,
After I found out that Sid installed legacy nvidia 340 driver, I have been tinkering with Sid a little more.
I tried to install Broadcom Sta driver, and got the following error (and log file attached).
Does that Deprecated feature: REMAKE_INITRD mean no longer possible to install this driver?apt-get update
apt-get install linux-headers-$(uname -r)
apt install broadcom-sta-dkms
....
....
I don't know, never seen that message before, perhaps it's kernel related, similar bug report here: https://www.mail-archive.com/debian-bug ... 52008.html
fredx181 wrote: Mon Apr 25, 2022 8:10 amI don't know, never seen that message before, perhaps it's kernel related, similar bug report here: https://www.mail-archive.com/debian-bug ... 52008.html
That bug report gave me impression that the driver was working with kernel 5.16.0-6-amd64.
I made fresh build yesterday, and it came with k-5.17.0-1-amd64.
I still have ISO that I made few days ago, and it came with k-5.16.0-6-amd64, so I thought to give it a try. But I found that headers for k-5.16.0-6-amd64 no longer there (in current repo).
Pity, I already deleted the frugal install I used for testing nvidia driver that had the k-5.16.0-6-amd64 headers installed.
This is my Broadcom, could be same issue maybe?
Code: Select all
[ 8.498511] wlan0: Broadcom BCM4328 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
dcung wrote:I still have ISO that I made few days ago, and it came with k-5.16.0-6-amd64, so I thought to give it a try. But I found that headers for k-5.16.0-6-amd64 no longer there (in current repo).
It's a bit of a hassle, but you can always search at snapshot.debian https://snapshot.debian.org/package/linux/5.16.18-1/, note the date (2022-03-30) and add to sources.list, in this case:
deb http://snapshot.debian.org/archive/debian/20220330/ sid main contrib non-free
And you should be able to install the older linux-headers 5.16.0-6
fredx181 wrote: Mon Apr 25, 2022 9:58 amIt's a bit of a hassle, but you can always search at snapshot.debian https://snapshot.debian.org/package/linux/5.16.18-1/, note the date (2022-03-30) and add to sources.list, in this case:
deb http://snapshot.debian.org/archive/debian/20220330/ sid main contrib non-free
And you should be able to install the older linux-headers 5.16.0-6
I added to source.list, but it's still not happy...
Code: Select all
root@live:~# apt update
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Get:2 http://deb.debian.org/debian sid InRelease [165 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 Packages.diff/Index [63.6 kB]
Get:3 https://github.com/doglinux/sidog/raw/master/amd64 ./ InRelease [2,301 B]
Get:5 http://snapshot.debian.org/archive/debian/20220330 sid InRelease [165 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 Packages T-2022-04-25-1402.12-F-2022-04-25-1402.12.pdiff [9,383 B]
Get:6 http://deb.debian.org/debian sid/main amd64 Packages T-2022-04-25-1402.12-F-2022-04-25-1402.12.pdiff [9,383 B]
Get:7 http://snapshot.debian.org/archive/debian/20220330 sid/main amd64 Packages [9,127 kB]
Get:8 http://snapshot.debian.org/archive/debian/20220330 sid/main Translation-en [6,770 kB]
Get:9 http://snapshot.debian.org/archive/debian/20220330 sid/contrib amd64 Packages [65.4 kB]
Get:10 http://snapshot.debian.org/archive/debian/20220330 sid/contrib Translation-en [55.9 kB]
Get:11 http://snapshot.debian.org/archive/debian/20220330 sid/non-free amd64 Packages [112 kB]
Get:12 http://snapshot.debian.org/archive/debian/20220330 sid/non-free Translation-en [103 kB]
Fetched 16.6 MB in 24s (704 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
68 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://dl.google.com/linux/chrome/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
root@live:~# apt-get install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-5.16.0-6-amd64
E: Couldn't find any package by glob 'linux-headers-5.16.0-6-amd64'
E: Couldn't find any package by regex 'linux-headers-5.16.0-6-amd64'
root@live:~#
I searched and downloaded this (linux-headers-5.16.0-6), but don't know what to do with it. They appear to be same .deb file (?)
https://snapshot.debian.org/package/lin ... _5.16.18-1
https://packages.debian.org/bookworm/am ... 4/download
@dcung Mmm... tested and it appears that the date (20220330) was too early, try:
deb http://snapshot.debian.org/archive/debian/20220410/ sid main contrib non-free
That's what I meant that it could be a hassle, you need to experiment a little as it's not always accurate what's showing at snapshot.debian.
And in such a situation I always check in Synaptic what's available (or apt-cache search linux-headers-5.16.0-6)
fredx181 wrote: Tue Apr 26, 2022 8:02 am
deb http://snapshot.debian.org/archive/debian/20220410/ sid main contrib non-free
This works. I installed the header. Thanks Fred.
Then installed the STA driver. It gave warning, but no error. And it looks like it installed successfully. WiFi still works.
Code: Select all
root@live:~# apt install broadcom-sta-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
dctrl-tools distro-info-data dkms dpkg-dev libdpkg-perl lsb-release make
Suggested packages:
debtags debian-keyring git bzr make-doc
Recommended packages:
linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic
| linux-headers build-essential libalgorithm-merge-perl
libfile-fcntllock-perl
The following NEW packages will be installed:
broadcom-sta-dkms dctrl-tools distro-info-data dkms dpkg-dev libdpkg-perl
lsb-release make
0 upgraded, 8 newly installed, 0 to remove and 75 not upgraded.
Need to get 6,766 kB of archives.
After this operation, 22.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 distro-info-data all 0.53 [7,656 B]
Get:2 http://deb.debian.org/debian sid/main amd64 lsb-release all 11.1.0 [27.9 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libdpkg-perl all 1.21.7 [1,611 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 make amd64 4.3-4.1 [396 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 dpkg-dev all 1.21.7 [2,354 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 dctrl-tools amd64 2.24-3+b1 [104 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 dkms all 3.0.3-1 [57.1 kB]
Get:8 http://deb.debian.org/debian sid/non-free amd64 broadcom-sta-dkms all 6.30.223.271-17 [2,208 kB]
Fetched 6,766 kB in 1s (4,869 kB/s)
Selecting previously unselected package distro-info-data.
(Reading database ... 51169 files and directories currently installed.)
Preparing to unpack .../0-distro-info-data_0.53_all.deb ...
Unpacking distro-info-data (0.53) ...
Selecting previously unselected package lsb-release.
Preparing to unpack .../1-lsb-release_11.1.0_all.deb ...
Unpacking lsb-release (11.1.0) ...
Selecting previously unselected package libdpkg-perl.
Preparing to unpack .../2-libdpkg-perl_1.21.7_all.deb ...
Unpacking libdpkg-perl (1.21.7) ...
Selecting previously unselected package make.
Preparing to unpack .../3-make_4.3-4.1_amd64.deb ...
Unpacking make (4.3-4.1) ...
Selecting previously unselected package dpkg-dev.
Preparing to unpack .../4-dpkg-dev_1.21.7_all.deb ...
Unpacking dpkg-dev (1.21.7) ...
Selecting previously unselected package dctrl-tools.
Preparing to unpack .../5-dctrl-tools_2.24-3+b1_amd64.deb ...
Unpacking dctrl-tools (2.24-3+b1) ...
Setting up distro-info-data (0.53) ...
Setting up lsb-release (11.1.0) ...
Selecting previously unselected package dkms.
(Reading database ... 51724 files and directories currently installed.)
Preparing to unpack .../archives/dkms_3.0.3-1_all.deb ...
Unpacking dkms (3.0.3-1) ...
Selecting previously unselected package broadcom-sta-dkms.
Preparing to unpack .../broadcom-sta-dkms_6.30.223.271-17_all.deb ...
Unpacking broadcom-sta-dkms (6.30.223.271-17) ...
Setting up make (4.3-4.1) ...
Setting up libdpkg-perl (1.21.7) ...
Setting up dctrl-tools (2.24-3+b1) ...
Setting up dpkg-dev (1.21.7) ...
Setting up dkms (3.0.3-1) ...
Setting up broadcom-sta-dkms (6.30.223.271-17) ...
Loading new broadcom-sta-6.30.223.271 DKMS files...
Deprecated feature: REMAKE_INITRD
Building for 5.16.0-6-amd64
Building initial module for 5.16.0-6-amd64
Deprecated feature: REMAKE_INITRD
Done.
Deprecated feature: REMAKE_INITRD
Deprecated feature: REMAKE_INITRD
Deprecated feature: REMAKE_INITRD
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.16.0-6-amd64/updates/dkms/
depmod....
root@live:~#
Code: Select all
Kernel driver in use: wl
Kernel modules: ssb, wl
root@live:~# Hi folks,
my last upgrade on DD-SID 64 on July 14th went down without problems. Yesterday I wanted to upgrade again and it crashed during that upgrade.
When using the console I got following message (translated from German):
elogin: collides with systemd but 251.3-1 is to be installed
eudev: damaged system (>220) but 251.3-1 is to be installed
libelogind0 : collides with: libsystemd0
When I look what synaptic wants to do : remove dbus synaptic and even xfce and many many more
but it wants to install libsystemd-shared and libip4tc2
When I let all happen ystem crashes totally and needs reboot.
It all seems very odd, because I have no systemd installed.
Who can explain and say how to prevent?
Payoon
Hi Payoon, thanks for the report.
I could reproduce exactly the problem, but at the moment I'm not sure yet how to solve it.
The thing is that the default for Debian is to boot with systemd and I made a workaround (based on the way Antix does) to prevent including systemd by using elogind.
But the setup for that, elogind as replacement for systemd, is rather fragile, specially with Sid as it's constantly changing (many packages to be upgraded frequently).
I'll investigate further and get back within a few days about a solution if possible.
FWIW, I just made a Bookworm Starter Kit and it still works OK with elogind. But the default shell has changed from bash to dash.
Also, the package libcrystalhd3 needed by gmplayer is not yet in your Bookworm repo.
@Payoon , I saw earlier that you posted: (but obviously removed later)
thanks for Your reply. I think I have found a solution, which maybe not very elegant, but all the upgrade went through. I put that libsystemd0 file on hold:
apt-mark hold libsystemd0
That should be fine, and here's what I just found :
It seems that systemd-standalone-tmpfiles package is required :
Description: standalone tmpfiles binary for use in non-systemd systems
Standalone tmpfiles binary with minimal dependencies.
This package conflicts with the main systemd package and is meant for use in
non-systemd systems.
So, another temporary solution is to install that first before upgrading :
apt install systemd-standalone-tmpfiles && apt upgrade
I'll look for a permanent solution, so that only apt upgrade will do.
Strange thing is BTW, that when doing a new build, all is OK (systemd-standalone-tmpfiles automatically installed).
Also, recommended to fix is creating the symlink sh to bash (instead of sh > dash) (see below).
FWIW, I just made a Bookworm Starter Kit and it still works OK with elogind. But the default shell has changed from bash to dash.
Also, the package libcrystalhd3 needed by gmplayer is not yet in your Bookworm repo.
Ugh, that's bad, thanks, I didn't notice.
This in the build script doesn't work anymore:
Code: Select all
echo "dash dash/sh boolean false" | debconf-set-selections
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dashReplace by this should work:
cd /bin; ln -sf bash sh; cd --
(or do it in the system, once booted)
The "dash" package from Bookworm and Sid are changed (sigh...), just dpkg-reconfigure dash even doesn't work anymore (should present a yes/no dialog to choose default shell)
I will add libcrystalhd3 later, thanks again.
fredx181 wrote: Fri Jul 22, 2022 9:38 amReplace by this should work:
cd /bin; ln -sf bash sh; cd --
(or do it in the system, once booted)
Thanks. I have already done that and it works. It was somewhat disconcerting to see all my gtkdialog apps fail because they need "export -f".
@fredx181
Hi. I have made the same experience. The upgrade crashes but when I make a new build with the same files and settings,everything sets up without error.
I will try what you have suggested and experiment with "systemd-standalone-tmpfiles" installed first. Let you know.
Payoon
Payoon wrote: Sat Jul 23, 2022 4:47 pm@fredx181
Hi. I have made the same experience. The upgrade crashes but when I make a new build with the same files and settings,everything sets up without error.I will try what you have suggested and experiment with "systemd-standalone-tmpfiles" installed first. Let you know.
Payoon
Hi Payoon, thanks, just made some changes in the custom repository for Sid (new elogind packages) that should make "apt upgrade" work without problems (no need then to install first "systemd-standalone-tmpfiles") .
Other fix needed is the symlink in /bin , sh > bash, from existing build in the booted system do (as previously mentioned): cd /bin; ln -sf bash sh; cd --
Probably I will update mklive-sid (and mklive-bookworm too) later to fix that for any new build.
Hi Fred,
you were faster than me. But as info : When putting "libsystemd0" on hold and installing "systemd-standalone-tmpfiles" before doing the upgrade all works fine. No systemd in sight. The changes you have made are better though. Thanks for the help.
Payoon
Two major problems should be fixed now.
(not only for Sid, also for Bookworm)
See here: https://forum.puppylinux.com/viewtopic. ... 352#p62352 and here: https://forum.puppylinux.com/viewtopic. ... 389#p62389 and thank you both again for reporting these.
Did NOT change the mklive script, but made some changes in the repositories :
- New elogind (and related) packages (replacement for systemd) in the custom packages repo, taken from Devuan, but changed the version number to higher, to be sure that these are "upgradable".
- Added symlink sh > bash in the tar.gz archives e.g. dog-boot-sid......tar.gz (contents to be copied during the build at early stage to the chroot)
For an exiting build: fix for when sh is symlink to dash, make it sh > bash : cd /bin; ln -sf bash sh from a running system.
It needs to be sh > bash in /bin for many gtkdialog based scripts to work properly.
EDIT: Forgot to mention that the custom repository contains the latest "dash" package, but modified, same as in Bullseye and earlier, has the old mechanism, i.e. being able to choose default shell by running dpkg-reconfigure dash
Updated mklive-sid script, see attachment at first post and see info here: viewtopic.php?p=68558#p68558.
Change is: Download and install newest debootstrap that really supports the (legacy) --no-merged-usr option.
See about usrmerge (which we are trying to avoid because of several reasons, e.g. sfs-load won't work properly then): https://packages.debian.org/unstable/main/usrmerge
Updated mklive-sid script, see attachment at first post
Again a problem appeared that has to do with "merged-usr", added a workaround to the script to avoid the usr-merge (with debootstrap, base build), I'm not sure if it's possible to retain in the future.
It's not that I particularly dislike this usr-merged system, just afraid (with reasons) that compatibility with sfs-load and some custom packages and configurations will be messed up with a usr-merged system.
Perhaps one day we should "go with the flow" with a (today's standard) usr-merged system , perhaps a non usr-merged system may give some unexpected problems in the future 
. Time will tell.
Here's a good read about some ins-and-outs about usrmerge for Debian: https://lwn.net/Articles/890219/
*** mklive-sid updated ***
Attached new version at first post
Now will build a "usr-merged" system e.g. /bin, /lib, /sbin are symlinks, see also info (about bookworm):
https://forum.puppylinux.com/viewtopic. ... 577#p70577
And made some other fixes (it's hard to keep up with the constant changes from Debian Sid, but should work OK for now)
2022-11-06: ISO updated (after almost 2 years, many changes since then), download and info: https://github.com/DebianDog/Sid
Built with new mklive-sid build script, contains now "usr-merged" system.
Firmware .squashfs is included.
fredx181, Thanks for all your hard work on this project.
Question: I ran the full install on an EFI system with Win/10 and other distros. I installed it to one of the partitions.
When it got to the grub install part, it didn't seem like it was going to setup a multiboot EFI setup, so I didn't install grub.
Would it have setup the EFI Multiboot correctly for me?