MX Linux Forum

Posted: **Thu Jan 06, 2022 8:32 am**

I've made up several respins of the official isos.

***edit***

**edit** all MX-21 respins have been removed from dolphin oracle's personal sourceforge, due to sourceforge asking me to. I don't have the isos anymore, so don't ask for them please.

MX 23.3 respins are still available, and will likely get updated at somepoint to latest.

**end edit***

MX 23.4 systemd-only respin is up. Its a full version of MX-23.3 64 bit, with sysVinit removed.

MX 23.3 sysVinit-only resipin is up, Full version of MX-23.3 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

MX-23 respins

Posted: **Thu Jan 06, 2022 8:53 am**

nice!

Posted: **Thu Jan 06, 2022 9:31 am**

Way cool!

Posted: **Thu Jan 06, 2022 9:37 am**

Very cool.

Gonna try the bare_x64 in a VM.

OK, that took only 5-6 minutes to install into a VM. Boot time is the same as my MX-21 Fluxbox on hardware. Great job.

Posted: **Fri Jan 07, 2022 3:13 pm**

dolphin_oracle wrote: Thu Jan 06, 2022 8:32 am the second is a 32 bit iso with the antiX 4.9 kernel, for folks that need that kernel for one reason or another. otherwise its identical to the standard 32bit Xfce iso.

On the 32bit iso boot it gives a "SQUASHFS error: Filesystem uses "unknown" compression.
Hmm, not sure I had the impression mx-snapshot would capture this and would not allow creating zstd-compressed squashfs for antix 4.9 kernel, which does not support squashfs_zstd compression.
+++EDIT+++
for the record...
Check:

Code: Select all

unsquashfs -stat /mnt/iso/iso1/antiX/linuxfs| grep -i compression
Compression zstd

and

Code: Select all

grep ^CONFIG_SQUASHFS_ /mnt/iso/sq1/boot/config-4.9.0-294-antix.1-686-smp-pae 
CONFIG_SQUASHFS_FILE_CACHE=y
CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZ4=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
CONFIG_SQUASHFS_4K_DEVBLK_SIZE=y
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3

Posted: **Fri Jan 07, 2022 3:14 pm**

fehlix wrote: Fri Jan 07, 2022 3:13 pm
dolphin_oracle wrote: Thu Jan 06, 2022 8:32 am the second is a 32 bit iso with the antiX 4.9 kernel, for folks that need that kernel for one reason or another. otherwise its identical to the standard 32bit Xfce iso.
On the 32bit iso boot it gives a "SQUASHFS error: Filesystem uses "unknown" compression.
Hmm, not sure I had the impression mx-snapshot would capture this and would not allow creating zstd-compressed squashfs for antix 4.9 kernel, which does not support squashfs_zstd compression.

hmph...apparently not. I'll redo that one.

Posted: **Fri Jan 07, 2022 3:58 pm**

I messed up the check? https://github.com/MX-Linux/mx-snapshot ... pp#L53-L58
Do you have headers installed? I set it up so the check doesn't fail if there is no /boot/config-kernelversion

Posted: **Fri Jan 07, 2022 4:17 pm**

Adrian wrote: Fri Jan 07, 2022 3:58 pm I messed up the check? https://github.com/MX-Linux/mx-snapshot ... cpp#L53-58
Do you have headers installed? I set it up so the check doesn't fail if there is no /boot/config-kernelversion

I'm pretty sure the headers are installed. I'll give it a check when I get home.

Posted: **Fri Jan 07, 2022 7:25 pm**

@fehlix i uploaded new 4.9 iso, this time used gzip.

@Adrian there is a config file uner /boot called config-4.9.0-294-antix.1-686-smp-pae and a matching vmlinuz-4.9.0-294-antix.1-686-smp-pae.

uname -r reports as 4.9.0-294-antix.1-686-smp-pae

Posted: **Sat Jan 08, 2022 8:10 pm**

@dolphin_oracle , thank you. Especially for the 32-bit version. I think the 64-bit "bare" version would be good to try experimenting with LXDE/LXQT? That was brought up in another thread and I'd like to start playing with that idea.

Seaken64

Posted: **Sat Jan 08, 2022 10:08 pm**

One can always install alternate desktop on any of the versions. LXDE especially is quite small and it's well configured out of the box. Having it doesn't require a respin.

Posted: **Sun Jan 09, 2022 5:05 am**

seaken64 wrote: Sat Jan 08, 2022 8:10 pm I think the 64-bit "bare" version would be good to try experimenting with LXDE/LXQT? That was brought up in another thread and I'd like to start playing with that idea.

I heard that LXDE isn't undergoing further development and Lxqt has taken over. But I often see it around and last time I looked it was in MX's repo ???

Posted: **Sun Jan 09, 2022 1:34 pm**

Yes, development has moved on to LXQt. But the LXDE is still being maintained by volunteers. And yes, it is in MXPI.

I am using LXDE now. I started with MX-21 XFCE. Then I used the MXPI to install LXDE. Then I restarted and chose the LXDE session from the drop down list on the top of the desktop manager/login manager.

It is familiar to me, having used Lubuntu and Peppermint and LXLE in the past. But now I remember why I ended up using Xubuntu and then MX. One thing that was always annoying to me was there was no setting widget to turn off the damn tap to click feature or turn off the touchpad while typing. I have retyped this paragraph several times due to errant characters being inserted where I did not intend.

I'm sure there are ways around this and some LXDE fans will be able to point me in the right direction. But I do remember that LXDE was harder to configure to my liking than XFCE. And I prefer antiX's approach to setting up the desktop environment and antiX is better in low memory.

But I am intrigued and I will try to manage LXDE for awhile to see if I can learn to handle it.

Seaken64

Posted: **Sun Jan 09, 2022 2:26 pm**

seaken64 wrote: Sun Jan 09, 2022 1:34 pm Yes, development has moved on to LXQt. But the LXDE is still being maintained by volunteers. And yes, it is in MXPI.

I am using LXDE now. I started with MX-21 XFCE. Then I used the MXPI to install LXDE. Then I restarted and chose the LXDE session from the drop down list on the top of the desktop manager/login manager.

It is familiar to me, having used Lubuntu and Peppermint and LXLE in the past. But now I remember why I ended up using Xubuntu and then MX. One thing that was always annoying to me was there was no setting widget to turn off the damn tap to click feature or turn off the touchpad while typing. I have retyped this paragraph several times due to errant characters being inserted where I did not intend.

I'm sure there are ways around this and some LXDE fans will be able to point me in the right direction. But I do remember that LXDE was harder to configure to my liking than XFCE. And I prefer antiX's approach to setting up the desktop environment and antiX is better in low memory.

But I am intrigued and I will try to manage LXDE for awhile to see if I can learn to handle it.

Seaken64

It's familiar to me also as I switched to it when using Fedora some years ago as I didn't like Gnome. It does live up to its name as it's very fast and easy on resources plus I liked the PCMan file manager.

Why don't you disable the touchpad while typing? On an Acer it's usually fn + F7. I'm typing this on an Asus and on this model it can't be done after booting. It can only be done by changing the setting in the BIOS. Somewhat inconvenient but I avoid that by always having it disabled and using a usb mouse, except on the rare occasion when I have to use both usb ports. And then I dread the thought of using the touchpad.

Edit: Before I get asked, why don't I use a usb hub, well I tried that, and on this laptop it works well with a mouse, keyboard, flash drive or anything else with low power requirements but as soon as I plug in an external hd, no go. Anyway it's not a big deal; like I said I only have to use both on rare occasions when my other laptop which has three ports is not with me.

Posted: **Sun Jan 09, 2022 2:43 pm**

LU344928 wrote: Sun Jan 09, 2022 2:26 pm
It's familiar to me also as I switched to it when using Fedora some years ago as I didn't like Gnome. It does live up to its name as it's very fast and easy on resources plus I liked the PCMan file manager.

Why don't you disable the touchpad while typing? On an Acer it's usually fn + F7. I'm typing this on an Asus and on this model it can't be done after booting. It can only be done by changing the setting in the BIOS. Somewhat inconvenient but I avoid that by always having it disabled and using a usb mouse, except on the rare occasion when I have to use both usb ports. And then I dread the thought of using the touchpad.

Just a thought but why not get something like this, 4-Port USB 3.0 Hub with Individual LED Power Switches.

https://www.amazon.com/Sabrent-4-Port-I ... B00JX1ZS5O

Posted: **Sun Jan 09, 2022 2:49 pm**

I learned to use a synaptics config command to turn off tapping back when I was learning antiX. I will go back and re-learn that technique, or look for a widget that works in LXDE.

Seaken64

Posted: **Sun Jan 09, 2022 3:19 pm**

towwire wrote: Sun Jan 09, 2022 2:43 pm
LU344928 wrote: Sun Jan 09, 2022 2:26 pm
It's familiar to me also as I switched to it when using Fedora some years ago as I didn't like Gnome. It does live up to its name as it's very fast and easy on resources plus I liked the PCMan file manager.

Why don't you disable the touchpad while typing? On an Acer it's usually fn + F7. I'm typing this on an Asus and on this model it can't be done after booting. It can only be done by changing the setting in the BIOS. Somewhat inconvenient but I avoid that by always having it disabled and using a usb mouse, except on the rare occasion when I have to use both usb ports. And then I dread the thought of using the touchpad.
Just a thought but why not get something like this, 4-Port USB 3.0 Hub with Individual LED Power Switches.

https://www.amazon.com/Sabrent-4-Port-I ... B00JX1ZS5O

You beat me to it - I wasn't quick enough with that edit above. :)

Posted: **Sun Jan 09, 2022 3:33 pm**

It's not convenient for me to use a USB mouse while I have the laptop on my lap, so I use the touchpad in that case. I do sometimes set the laptop on a stand and plug in a USB keyboard/trackpad compo. And that combo gives me the option to turn off the trackpad.

I'll figure it out. It's just that LXDE does not make this type of thing as easy as XFCE does. Even antiX has a tool for the touchpad on the Control Centre.

Seaken64

Arghhh! I can't take it anymore! I'm switching back to XFCE on this laptop. I'll try LXDE on one of my desktops. The cursor is all over the place with this touchpad.

Posted: **Sun Jan 09, 2022 6:48 pm**

This thread really got diverted.

Posted: **Sun Jan 09, 2022 6:53 pm**

Yeah, sorry. That was probably my fault. Future comments on LXDE will go in another thread.

Seaken64

Posted: **Tue Jan 18, 2022 4:16 pm**

Whats the root password for the bare edition ISO ? I'm trying to access other drives on the pc before installing and i need root access.

Posted: **Tue Jan 18, 2022 4:20 pm**

never mind figured out it is demo

Posted: **Sat Feb 12, 2022 8:36 am**

just added a "bare" version that is systemd-only. notes in the first post.

Posted: **Sun Apr 10, 2022 5:57 pm**

I wonder if there's any negative if choosing systemd in boot options with the regular/official ISO?

Posted: **Sun Apr 10, 2022 6:16 pm**

Lots of users use systemd without complaint.

Posted: **Sun Apr 10, 2022 7:55 pm**

What does "bare bones" actually mean? I have a new bare-bone pc (waiting on a hd) that I want systemd on only as I found that trying to get vpn's working in sysvinit is more hassle than it's worth. What desktop and what kernel? Or is there a choice when installing? The thought of removing everything you don't actually use is not a bad idea. If your graphics are radeon on an amd, are the intel drivers removable then? I realize each device really needs it's own personal install regardless if it's the same OS.
My laptop uses intel but I see nvidia installed on my system. I assume I could just remove them?
Still downloading the bare-bones systemd only 64bit iso...

Posted: **Sun Apr 10, 2022 7:59 pm**

davidy wrote: Sun Apr 10, 2022 7:55 pm What does "bare bones" actually mean? I have a new bare-bone pc (waiting on a hd) that I want systemd on only as I found that trying to get vpn's working in sysvinit is more hassle than it's worth. What desktop and what kernel? Or is there a choice when installing? The thought of removing everything you don't actually use is not a bad idea. If your graphics are radeon on an amd, are the intel drivers removable then? I realize each device really needs it's own personal install regardless if it's the same OS.
My laptop uses intel but I see nvidia installed on my system. I assume I could just remove them?

its the basic Xfce installation and MX tools, 5.10 kernel, but without many other applications. Firefox is still installed though.

I need to update the systemd-only one. there are some changes in MX packages that aren't present on it and won't be because of the way its built.

Posted: **Sun Apr 10, 2022 8:29 pm**

Cool. Sounds like it is something one would use if you had a specific application for the appliance itself. I'm gonna try av-linux first then. I planned on running a vm of windows10 on top of mx so my 'appliance' will be kind of a jack of all trades affair. We'll see. Thanks Dolphin.

Posted: **Sun Apr 10, 2022 8:32 pm**

Jerry3904 wrote: Sun Apr 10, 2022 6:16 pm Lots of users use systemd without complaint.

'Cause they don't know better

Seriously, you generally need to reboot systemd more often because of it's architecture. Systemd is also more of a pita from a system admin's standpoint as all the log files are binary (normal desktop users, who don't seem to ever read logs anyway, probably won't see any difference). It also sucketh on low memory servers as services will crash and reload (a freaking lot!). From experience expect to see notices about lmtp and dnsadmin (cPanel) failing and recovering daily on a server with 1G RAM or less.*

ymwv,
Michael

* Bumping swap up to 2G will solve the fail/recovery cycle at the cost of your box is slower.

Posted: **Mon Apr 11, 2022 8:04 am**

updated my bare and bare-systemd-only spins.

Posted: **Mon Apr 11, 2022 9:11 am**

Jerry3904 wrote: Sun Apr 10, 2022 6:16 pm Lots of users use systemd without complaint.

Michael-IDA wrote: Sun Apr 10, 2022 8:32 pm you generally need to reboot systemd more often because of it's architecture. Systemd is also more of a pita from a system admin's standpoint

I don't know if my doubt was understood.
I don't want to compare sysvinit with systemd. I want to know if in a system with both pre-installed is there chance of conflicts if choosing one or the other?

Posted: **Mon Apr 11, 2022 9:20 am**

Bamber wrote: Mon Apr 11, 2022 9:11 am
Jerry3904 wrote: Sun Apr 10, 2022 6:16 pm Lots of users use systemd without complaint.

Michael-IDA wrote: Sun Apr 10, 2022 8:32 pm you generally need to reboot systemd more often because of it's architecture. Systemd is also more of a pita from a system admin's standpoint
I don't know if my doubt was understood.
I don't want to compare sysvinit with systemd. I want to know if in a system with both pre-installed is there chance of conflicts if choosing one or the other?

Not usually. I run systemd most of the time.

Posted: **Mon Apr 11, 2022 9:30 am**

I have been uisng systemd for several months and is my normal boot method. I ocassionally boot sysvinit but not often. I have seen no conflicts. The only diference I see is a faster boot with systemd of two to five seconds.
And I do not need to boot more often with systemd

Posted: **Mon Apr 11, 2022 4:33 pm**

Thanks Dolphin. I gonna update my image with the just bare one. One of these days I'll look into the script for making my vpn 'just work' with sysvinit. So far using systemd has saved me a ton of downtime. I should probably make a thread.

Posted: **Mon Apr 11, 2022 10:46 pm**

Added a KDE respin with a 5.16 kernel.

Posted: **Mon May 30, 2022 6:31 pm**

added a Xfce AHS respin with nvidia 5.10 drivers installed. also uses 5.17 kernel and all latest updates. since nouveau is blacklisted, machines that can't run the latest nvidia drivers should avoid this one. there really isn't any other purpose for this spin other than for later nvidia users that can't use nouvaeu. Otherwise identical to the 21.1 AHS (xfce) release.

tested on an optimus laptop. I don't have a desktop nvidia machine or a dedicated nvidia machine to test with.

Posted: **Sun Jul 24, 2022 4:23 am**

Thank you for the excellent respin(s). I installled the latest(nvidia one) and it runs really nice here. Although it still booted with nouveau, but I entered blacklist=nouveau at bootmenu line and the newer nvidia driver loaded perfectly.

Posted: **Thu Sep 15, 2022 9:02 am**

RE: the second is a 32 bit iso with the antiX 4.9 kernel, for folks that need that kernel for one reason or another. otherwise its identical to the standard 32bit Xfce iso.

dolphin_oracle,
May i ask a question sir, regarding your fantastic MX 21 respin with the 4.9 kernel, will we be able to update the kernel at some point? If so, will the kernel update be included with regular system updates/upgrades, or manually?
Thanks in advance,
eforest99

Posted: **Thu Sep 15, 2022 9:09 am**

eforest99 wrote: Thu Sep 15, 2022 9:02 am RE: the second is a 32 bit iso with the antiX 4.9 kernel, for folks that need that kernel for one reason or another. otherwise its identical to the standard 32bit Xfce iso.

dolphin_oracle,
May i ask a question sir, regarding your fantastic MX 21 respin with the 4.9 kernel, will we be able to update the kernel at some point? If so, will the kernel update be included with regular system updates/upgrades, or manually?
Thanks in advance,
eforest99

when the update, it would be manual from mx-packageinstaller->Popular Apps->kernels.

Posted: **Sat Sep 24, 2022 7:32 pm**

updated all spins with latest packages and kernels.

see first post in this thread for info.

Posted: **Wed Oct 26, 2022 9:58 am**

Which of your 64-bit respins, without systemd, would you recommend as a server base OS, please?

Thanks for creating and sharing these!

Posted: **Wed Oct 26, 2022 10:02 am**

kd4e wrote: Wed Oct 26, 2022 9:58 am Which of your 64-bit respins, without systemd, would you recommend as a server base OS, please?

Thanks for creating and sharing these!

they are all desktop centric and have relatively minor changes from the original isos. The "bare" one has the least desktop apps installed though. MX isn't really targeted as a server system OOTB. Adrian has a cli version that may be closer to what you want though.

Posted: **Wed Oct 26, 2022 10:19 am**

I'm also looking at Devuan and VOID but would prefer to use MX, my 'daily driver', if I can.

Thanks!

Posted: **Thu Dec 29, 2022 9:16 pm**

I've been using the systemd only respin for about a year now. I see the ISOs were updated in Sept and I'm about to install it on a new Geekom IT8, but I'm noticing MX Linux has difficulty initializing the sound drivers. It's not only with this respin; the same is true for the AHS and standard MX desktop ISOs.

I have the earlier ISO (original bare systemd only respin, prior to the Sept update) installed on a SSD USB drive which I can boot from. It doesn't do sound on my Acer Swift 5 either. Both the Acer Swift 5 and the Geekom IT8 use the same Intel Cannon Point-LP High Definition Audio chipset. Here is the audio info from quick sys info on the Geekom IT8:

Code: Select all

Audio:  Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel v: kernel
           alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0403
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes
           Sound Server-2: PulseAudio v: 14.2 running: yes

Is there a solution to this problem? 6 months ago or so I dug deep to try & find one, and did manage to get full sound out of the headphones but not much at all out of the speakers. I spent a lot of trial & error time fiddling with blacklisting drivers, options etc but never found a complete solution.

Posted: **Fri Dec 30, 2022 2:07 am**

Please open your own topic with your issue on this respin in the respins forum, and share the full QSI there, thank you.

Posted: **Sun Apr 09, 2023 4:52 am**

I have installed all the current updates to the systemd varient. I also installed and configured fluxbox so you can choose either fluxbox or xfce if you use this. Firefox ESR is installed rather than the mainstream release, but it's easy enough to switch back with synaptic. I also added a few keybindings for the MacBook Pro backlights (they might work for you too) and I set alt-p to capture a screenshot.

https://easyupload.io/rgbl8n
MXsystemd20230408.iso
md5:
1ffd93abc7d3a1cf5689c48fd2f5e1f9

Posted: **Sun Apr 09, 2023 5:10 am**

je55eah wrote: Sun Apr 09, 2023 4:52 am I have installed all the current updates to the systemd varient. I also installed and configured fluxbox so you can choose either fluxbox or xfce if you use this. Firefox ESR is installed rather than the mainstream release, but it's easy enough to switch back with synaptic. I also added a few keybindings for the MacBook Pro backlights (they might work for you too) and I set alt-p to capture a screenshot.

https://easyupload.io/rgbl8n
MXsystemd20230408.iso
md5:
1ffd93abc7d3a1cf5689c48fd2f5e1f9

It would be prudent to start your own thread to announce your own respin, so it is not confused with dolphin's.

Posted: **Sun Apr 09, 2023 5:14 am**

@asqwerth
it is dolphin's respin, brought up to date.

Posted: **Sun Apr 09, 2023 5:49 am**

Putting it delicately, the download origin/source is different.
@je55eah

Posted: **Sun Apr 09, 2023 6:00 am**

@asqwerth
Any suggestions? I just searched for a site that was free to use then used it. I didn't see anything bad like porn or excessive ads.

Posted: **Sun Apr 09, 2023 6:24 am**

je55eah wrote: Sun Apr 09, 2023 6:00 am @asqwerth
Any suggestions? I just searched for a site that was free to use then used it. I didn't see anything bad like porn or excessive ads.

I'm not stating that you have to upload on a different download site.

I'm suggesting that it is best to open a new thread and post your download links there. You can explain that your iso respin was based on dolphin's, but that you modded certain things which you should list.

That way, forum users know what your iso was based on, but are also aware it was done by another member, not dolphin. That's what I mean by "source" - it's your iso, not dolphin's.

Posted: **Sun Apr 09, 2023 6:33 am**

My name is on it, so I don't think anyone thought dolphin posted it. Next time, perhaps.

Posted: **Mon Apr 17, 2023 2:33 pm**

Here is another update of dolphin_oracle's systemd respin. This time I have enabled the ahs repositories and installed the 6.1 kernel. The normal firefox version is installed, as opposed to the lts version. Fluxbox has also been installed and configure to resemble XFCE, which is still installed. A few of the buttons from the sidebar have been moved to the taskbar and the sidebar has been disabled. A show desktop button has been added to the lower right corner of the taskbar. The desktop icon link to the tutorial videos was moved to the start menu. Compton has been enabled to to fix conky transparency issues. alt-p has been set as a shortcut to create screenshots. The special keys for led backlights have been enabled. Tap to click has been disabled for the left button on the touchpad. I created a desktop file that opens the fluxbox menu and ctrl-esc can also be used to open that menu.

https://easyupload.io/hyihix
md5:
de09d9564cefe5f563c53d91753bff1e MXsystemd20230416.iso

This not being published by dolphin_oracle, I am publishing it here because it is not a significant departure from the systemd respin he shared. I moved a few buttons and ran some updates.

Posted: **Tue May 23, 2023 7:54 am**

I wil try the dolphin systemd respin as a live usb,why only because vpn,s this case proton all want systemd :(
So far no succes, boots to standard MX, make a fresh live usb to much tries feeling

if i keep failing wil make a new topic.

Posted: **Sun Jun 11, 2023 11:12 am**

I would like to use the pystemd python library to restart a systemd service within my application but pip can't install it due to a missing dependency or PKG "mis"configuration (it can't find libsystemd.pc). PyCharm IDE can't install it nor can I as root.

Code: Select all

Collecting pystemd
  Using cached pystemd-0.13.2.tar.gz (308 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error
  
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
      Package libsystemd was not found in the pkg-config search path.
      Perhaps you should add the directory containing `libsystemd.pc'
      to the PKG_CONFIG_PATH environment variable
      No package 'libsystemd' found
      `pkg-config --modversion libsystemd` failed. Please ensure all prerequisite packages from README.md are installed.
      [end of output]

I found some version and added them to the PKG_CONFIG_PATH env var but it didn't help.
root-# find . -type f | grep libsystemd
./systemd/libsystemd-shared-247.so
./x86_64-linux-gnu/libsystemd.so.0.30.0

I'm booted with systemd with this respin.

Posted: **Sun Jun 11, 2023 3:27 pm**

MX21/bullseye has both libsystemd-dev and python3-systemd

Posted: **Sun Jun 11, 2023 9:33 pm**

baldyeti wrote: Sun Jun 11, 2023 3:27 pm MX21/bullseye has both libsystemd-dev and python3-systemd

Thanks for the reply. I installed both of those packages and yet still cannot install the pystemd package with pip3.

I'm not locked into using pystemd if I could find any python3 library / package that allows me to start / stop / status existing systemd units natively without spawning a subprocess. Most of the packages I can find info for provide access to logs & status, but no control over running units.

Nothing in this description of python3-systemd tells me it can replace the functionality I need from systemctl for example. It may provide the status of units I need, but not control of them.

How can I do what this guy describes natively without using a command line subprocess? That's what brought me to pystemd.

I resolved the problem. Not sure if I needed the other 2 packages you mentioned, but after installing those I still needed python3-dev. After installing that pip was able to build the wheels to success.

Posted: **Mon Jun 12, 2023 4:13 am**

Glad you solved it - you probably do not need the 2 packages i suggested, i thought systemd-dev might be a requirement for compiling your C extension, but as you've mentioned python3-dev was likely the missing bit.

Posted: **Wed Aug 23, 2023 1:46 pm**

Be OK wrote: Tue May 23, 2023 7:54 am I wil try the dolphin systemd respin as a live usb,why only because vpn,s this case proton all want systemd

If I understand you correctly, you seem to be under the impression that Proton VPN needs systemd. I use Proton VPN and do not use systemd. I haven't noticed any issues with MX 21 but on MX 23 we don't have the library they use to put the icon in the systray. The VPN works fine though.

Posted: **Fri Sep 08, 2023 2:37 pm**

@dolphin_oracle - Will you be making a new systemd only respin for MX Linux 23? I sure hope so, as I require systemd AND persistence for USB booted live systems.

Posted: **Mon Sep 11, 2023 12:03 am**

a_freed_man wrote: Fri Sep 08, 2023 2:37 pm @dolphin_oracle - Will you be making a new systemd only respin for MX Linux 23? I sure hope so, as I require systemd AND persistence for USB booted live systems.

just put it up.

https://sourceforge.net/projects/do-tes ... snapshots/

added info to first post

Posted: **Tue Sep 12, 2023 9:47 pm**

Awesome! U-da-Man dolphin!

With great graditude, thank you

Posted: **Tue Sep 19, 2023 2:08 pm**

I've noticed on this respin that I don't get USB automounting. Is that a side effect of this respin? How can USB automounting by users be restored restored / enabled?

Posted: **Tue Sep 19, 2023 2:41 pm**

a_freed_man wrote: Tue Sep 19, 2023 2:08 pm I've noticed on this respin that I don't get USB automounting. Is that a side effect of this respin? How can USB automounting by users be restored restored / enabled?

shouldn't be. probably have to turn it back on in thunar's volume management options.

Posted: **Sat Sep 23, 2023 10:31 am**

Sure enough, the Thunar option to automount removable media was not enabled. However, turning it on didn't resolve the issue, nor did logging out & back in or rebooting either. I tried several different USB devices, not automounted.

All of the devices did show up with blkid though. Any ideas on what I might check to troubleshoot this?

Posted: **Sat Sep 23, 2023 11:03 am**

likely need all three of the attached options. well, maybe not the third one.

Posted: **Sun Sep 24, 2023 9:19 am**

Hi all,
Hello @dolphin oracle, (a noob question) ... Can you explain more precisely the advantages & inconvenients, and the goal, of a "bare respin" version. And if a MX23-bare-respin is planed? (And why the need of a only systemd version, for a better compatibility ?)

Posted: **Sun Sep 24, 2023 9:58 am**

Yes, that took care of it, thx!

I don't see a way to mark this as solved. Must be due to the context I'm guessing.

Posted: **Sun Sep 24, 2023 10:06 am**

Click on the check next to your username on the post that solved the poroblem.

Posted: **Sun Sep 24, 2023 10:07 am**

a_freed_man wrote: Sun Sep 24, 2023 9:58 am Yes, that took care of it, thx!

I don't see a way to mark this as solved. Must be due to the context I'm guessing.

You aren’t the original poster so you can’t mark. But yeah no applicable anyway.

Posted: **Sun Sep 24, 2023 10:16 am**

dolphin_oracle wrote: Sun Sep 24, 2023 10:07 am
a_freed_man wrote: Sun Sep 24, 2023 9:58 am Yes, that took care of it, thx!

I don't see a way to mark this as solved. Must be due to the context I'm guessing.
You aren’t the original poster so you can’t mark. But yeah no applicable anyway.

Thanks DO. I did not notice that.

Posted: **Sun Sep 24, 2023 10:20 am**

oops wrote: Sun Sep 24, 2023 9:19 am Hi all,
Hello @dolphin oracle, (a noob question) ... Can you explain more precisely the advantages & inconvenients, and the goal, of a "bare respin" version. And if a MX23-bare-respin is planed? (And why the need of a only systemd version, for a better compatibility ?)

the bare respin had few preinstalled applications. some people like that. I do not have a mx23 version planned at this time. there is already a "minimal" respin. https://sourceforge.net/projects/mx-lin ... X-Minimal/

and there is no real need for a systemd-only respin. it was mostly a platform for me to see if I could make the live persistence system at least operation under systemd without making gigantic changes to the live system. its not error free but is probably "good enough" for enthusiasts. a few folks don't want to mess with sysVinit for whatever reason (usual some service that doesn't have an init script) and the respin removes that for them.

Posted: **Sun Sep 24, 2023 10:32 am**

... OK, thank you for your accurate explanation dolphin_oracle.

Posted: **Sun Sep 24, 2023 11:22 pm**

Next issue is that it doesn't detect the WiFi adaptor in the system. It is "WiFi 6" according to beeLink.
Seems like these Intel based systems in the last few years have chipsets that prove to be difficult to program. I have an Acer Swift laptop that sound doesn't work properly (doesn't auto detect when headphones are plugged in for one thing, I have to manually select the output device. Sometimes it comes out of both headphones & speakers!).

I posted the quick info here. Here is the Network section from it:

Code: Select all

Network:
  Device-1: Intel driver: iwlwifi v: kernel modules: wl port: N/A bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>

The above isn't what I'm seeing right now. Could be I turned on WiFi in my router when I took the quick info before. I will restart with phone hotspot on to see if it's detected now... It wasn't. The quick info for the network has also changed slightly, showing:

Code: Select all

Device 1: Intel driver: N/A modules: iwlwifi, wl port N/A bus-ID: 00:14.3 chip-ID: 8086:54f0
class-ID: 0280

The difference is the "N/A modules vs "kernel modules", so probably not significant.

Is there an rfkill or equiv on MX23? The info for one of the other guys in that thread had the same chipset on his beeLink and his interface was UP, so I'll send him a DM to ask what he did to get WiFi working.

The MX Network Assistant shows wl, iwlwifi drivers (and others), and 2 items under status tab. The 1st is Network Controller which has no interface and cannot be disabled. The 2nd is for the wired eth0. Net diagnostics tab is useless for this type of issue. Rescanning shows same info.

Posted: **Mon Sep 25, 2023 8:26 am**

@dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.

Posted: **Mon Sep 25, 2023 8:28 am**

manyroads wrote: Mon Sep 25, 2023 8:26 am @dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.

if you mean the sid/unstable debian repo, I wouldn't recommend it. but its linux, you can do what you want.

Posted: **Mon Sep 25, 2023 8:45 am**

dolphin_oracle wrote: Mon Sep 25, 2023 8:28 am
manyroads wrote: Mon Sep 25, 2023 8:26 am @dolphin_oracle Am I right to assume that the bare systemd version can/might be run as unstable? For me a "thin MX" that is capable of running unstable would be wonderful.
if you mean the sid/unstable debian repo, I wouldn't recommend it. but its linux, you can do what you want.

I often do... generally everything I break I'm lucky enough to patch back together; I'll test the systemd only version first. Then I'll trim things down to see where it breaks.

If I come up with something useful/ workable, I'll share it with "both people" who might be interested.

Posted: **Mon Sep 25, 2023 12:32 pm**

@a_freed_man

1.) blacklist the broadcom 'wl' modules stuff ...
2.) Intel AX101 chipset needs at least a kernel v6.4.xx ++, see my experiences w#my BeeLink EQ12 in this post/thread:
viewtopic.php?p=731457#p731457

greetz

l0dr3

Posted: **Tue Sep 26, 2023 8:48 am**

messing around with a spin that only includes sysVinit. oddly, plymouth (the boot splash daemon) is proving to be a challenge.

Posted: **Tue Sep 26, 2023 7:44 pm**

l0dr3 wrote: Mon Sep 25, 2023 12:32 pm @a_freed_man

1.) blacklist the broadcom 'wl' modules stuff ...
2.) Intel AX101 chipset needs at least a kernel v6.4.xx ++, see my experiences w#my BeeLink EQ12 in this post/thread:
viewtopic.php?p=731457#p731457

greetz

l0dr3

I did manage to get WiFi working by installing a 6.4 kernel from mx-package manager, but still no bluetooth. I tried renaming the ibt*4150 files to ibt*1050 but no change to behavior, it still won't load firmware.

Posted: **Wed Sep 27, 2023 6:45 am**

a_freed_man wrote: Tue Sep 26, 2023 7:44 pm I did manage to get WiFi working by installing a 6.4 kernel from mx-package manager, but still no bluetooth. I tried renaming the ibt*4150 files to ibt*1050 but no change to behavior, it still won't load firmware.

@a_freed_man , plz open a new thread in the 'Help' subforum, where i can assist you, in finding the right firmware combination for your specific AX101 chipset.

THIS problem is not related to D_O's respin, its a problem that occurs on almost all distros and derivates ...

greetz

l0dr3

Posted: **Wed Sep 27, 2023 7:38 am**

dolphin_oracle wrote: Tue Sep 26, 2023 8:48 am messing around with a spin that only includes sysVinit. oddly, plymouth (the boot splash daemon) is proving to be a challenge.

@dolphin_oracle hope you won't hold back on releasing such sysvinit-only respin, only because of a plymouth issue;
I for one (as others probably do too) enjoy scrolling boot text....

Posted: **Wed Sep 27, 2023 8:45 am**

ceeslans wrote: Wed Sep 27, 2023 7:38 am
dolphin_oracle wrote: Tue Sep 26, 2023 8:48 am messing around with a spin that only includes sysVinit. oddly, plymouth (the boot splash daemon) is proving to be a challenge.
@dolphin_oracle hope you won't hold back on releasing such sysvinit-only respin, only because of a plymouth issue;
I for one (as others probably do too) enjoy scrolling boot text....

I have a working prototype. will probably get something done this weekend if I have the time.

Posted: **Fri Sep 29, 2023 9:39 pm**

MX 23 sysVinit-only resipin is up, Full version of MX-23 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

Link to my mx-23 based respins is in the first post.

Posted: **Sat Sep 30, 2023 6:37 am**

Many thanks DO. Recommend you adjust the title to reflect the new date.

Posted: **Sat Sep 30, 2023 6:51 am**

Forgot to mention a headsup for anyone trying this before I get a chance to:

On the login screen, are the power options (hibernate, suspend, restart, shutdown) available or greyed out?
I think it's an issue with lightdm but I think Stevo backported version 1.32.0-3 (test repos) which is supposed to solve it.

Update:
@dolphin_oracle Just installed it and can confirm that power options are greyed out on login screen. Default installed version of lightdm is 1.26.

I removed 1.26 and installed lightdm_1.32.0-3~mx23+1_amd64.deb from the test repo:
mxrepo.com/mx/testrepo/pool/test/l/lightdm/lightdm_1.32.0-3~mx23+1_amd64.deb

and now buttons are available.

A couple of other 'issues'. I'm still seeing a lot of output at boot even though 'quiet splash' is there. Second I thought there was in issue with volume but it seems to have resolved itself. Muted icon and no option to turn it on when right clicking. A reboot seems to have sorted it though. Don't know what that was about.

Posted: **Sat Sep 30, 2023 7:39 pm**

pipewire has issues. working on it.

thanks for hte info on the test lightdm. I fixed it on revised isos a different way, but that is probably better than what I did. will check it out, but revised isos that "fix" the pipewire issue are up.

**actually uploading a new one with the test repo lightdm. I like its solution better than mine.

Posted: **Sun Oct 01, 2023 3:13 am**

No problem. Thanks to you for working on it on your weekend. Do you guys ever take a break? lol.

Yes it's part of a bug/patch which they fixed in 1.32. Something to do with a dependancy on logind:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=932047

We told Stevo about it and he kindly backported 1.32 to testing.
The sound issue was only a glitch it seems, since it's worked well after that. I'll be interested to see what the pipewire fix brings.
The 'quiet splash' is working now as well but something's overriding the /e/d/grub file and subsequent update-grub. Disabling os-prober in grub using:
GRUB_DISABLE_OS_PROBER=true
GRUB_DISABLE_OS_PROBER="true"

has no effect. Still runs and detects other OSes. Update-grub doesn't display the traditional warnings about it being on/off either. I will play around with it a bit more before I download the newer iso. Many thanks again.

Posted: **Sun Oct 01, 2023 6:44 pm**

Do you do anything specific with power management in your systemd only respin? I've installed the offical KDE iso and systemd won't suspend my laptop properly. I have a forum post about it.

Once I installed your systemd only version it seemed to work exactly as expected, so I'm not sure what the difference is between the two but something is configured differently.

Posted: **Sun Oct 01, 2023 7:08 pm**

rgif wrote: Sun Oct 01, 2023 6:44 pm Do you do anything specific with power management in your systemd only respin? I've installed the offical KDE iso and systemd won't suspend my laptop properly. I have a forum post about it.

Once I installed your systemd only version it seemed to work exactly as expected, so I'm not sure what the difference is between the two but something is configured differently.

nothing but an updated kernel.

Posted: **Mon Oct 02, 2023 7:50 am**

BitterTruth wrote: Sun Oct 01, 2023 3:13 am
We told Stevo about it and he kindly backported 1.32 to testing.
The sound issue was only a glitch it seems, since it's worked well after that. I'll be interested to see what the pipewire fix brings.
The 'quiet splash' is working now as well but something's overriding the /e/d/grub file and subsequent update-grub. Disabling os-prober in grub using:
GRUB_DISABLE_OS_PROBER=true
GRUB_DISABLE_OS_PROBER="true"

has no effect. Still runs and detects other OSes. Update-grub doesn't display the traditional warnings about it being on/off either. I will play around with it a bit more before I download the newer iso. Many thanks again.

that is not a spin issue. we went out of our way to keep os-prober enabled because debian goes out of their way to disable os-prober.

towards teh bottom of the /etc/default/grub file you should see this:

Code: Select all

#comment out the below line to allow the above GRUB_DISABLE_OS_PROBER to be toggled off manually
if [ -e /etc/default/grub.mx-defaults ]; then
     .  /etc/default/grub.mx-defaults
fi
#comment out the above lines to allow the above GRUB_DISABLE_OS_PROBER to be toggled off manually

so comment out those lines, and the GRUB_DISABLE_OS_PROBER=true will be followed.

Posted: **Mon Oct 02, 2023 7:57 am**

Thanks for that. I managed to edit the /etc/grub.d/30_os-prober file instead and removed the overrides. Also added in the warnings. Everything's back the way I like.

I just mentioned it in case somebody else had an issue with it.

I've got to say though, feels really smooth, looks gorgeous.

Posted: **Mon Oct 02, 2023 8:40 am**

dolphin_oracle wrote: Fri Sep 29, 2023 9:39 pm MX 23 sysVinit-only resipin is up, Full version of MX-23 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

Link to my mx-23 based respins is in the first post.

I noticed libsystemd-shared is installed. What does it do?

Posted: **Mon Oct 02, 2023 9:15 am**

anticapitalista wrote: Mon Oct 02, 2023 8:40 am
dolphin_oracle wrote: Fri Sep 29, 2023 9:39 pm MX 23 sysVinit-only resipin is up, Full version of MX-23 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

Link to my mx-23 based respins is in the first post.
I noticed libsystemd-shared is installed. What does it do?

I don't know, maybe just some cleanup.

Posted: **Mon Oct 02, 2023 9:40 am**

dolphin_oracle wrote: Mon Oct 02, 2023 9:15 am
anticapitalista wrote: Mon Oct 02, 2023 8:40 am
dolphin_oracle wrote: Fri Sep 29, 2023 9:39 pm MX 23 sysVinit-only resipin is up, Full version of MX-23 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

Link to my mx-23 based respins is in the first post.
I noticed libsystemd-shared is installed. What does it do?
I don't know, maybe just some cleanup.

I purged it and everything seems to be working ok.

Posted: **Tue Oct 03, 2023 2:31 pm**

anticapitalista wrote: Mon Oct 02, 2023 8:40 am... noticed libsystemd-shared is installed. What does it do?

https://packages.debian.org/bookworm/libsystemd-shared wrote:
Package: libsystemd-shared

systemd shared private library

This internal shared library provides common code used by various systemd components. It is supposed to decrease memory and disk footprint. The shared library is not meant for public use and is not API or ABI stable.

:)

Posted: **Tue Oct 03, 2023 8:55 pm**

I updated the sysVinit only spin to remove the library, although its just a library and doesn't do anything on its own.

Posted: **Wed Oct 04, 2023 4:38 am**

dolphin_oracle wrote: Tue Oct 03, 2023 8:55 pm I updated the sysVinit only spin to remove the library, although its just a library and doesn't do anything on its own.

Many thanks DO. Lean & mean!

Posted: **Tue Jan 23, 2024 1:08 pm**

updated my systemd_only and sysVinit_only spins to conform with mx23.2. link in first post.

Posted: **Tue Jan 23, 2024 1:17 pm**

The title stayed as: "updated 10-21-2023" :)

Posted: **Thu Feb 01, 2024 5:52 pm**

dolphin_oracle wrote: Tue Jan 23, 2024 1:08 pm updated my systemd_only and sysVinit_only spins to conform with mx23.2. link in first post.

Hi @dolphin_oracle:
I built a ParrotOS based respin with some MX tools, "https://sourceforge.net/projects/senpai ... rrotOS_MX/".
I would like to try to make it with MX base but ParrotOS only supports "Systemd".
My MX-23.2 respin only with Mate, I would like to convert it to one with only systemd, to do some testing of a Mate respin with this "https://gitlab.com/parrotsec/project/installer-script" to install ParrotOS and its privacy/security tools over MX base.

But my MX-Mate respins have sysvinit and systemd, how could I totally remove sysvinit, I don't have much idea about the "init".....

Best regards

Posted: **Thu Feb 01, 2024 6:20 pm**

Code: Select all

sudo apt install systemd-sysv

Posted: **Fri Feb 02, 2024 3:33 am**

Just that!

I will try it, thank you!

Posted: **Sat Feb 03, 2024 6:43 am**

dolphin_oracle wrote: Thu Feb 01, 2024 6:20 pm
Code: Select all
sudo apt install systemd-sysv

Thank you, dolphin_oracle
it worked, let's see how it looks

Best regards

Posted: **Wed Feb 28, 2024 7:46 am**

So it's kinda easy on MX to end up with a systemd system.. does that mean that the SysV option is 'for show' and that the Debian base simply makes it too difficult? Or at least creates problems? I installed MX on an old Lenovo R500 and something happened, can't remember exactly, that required me to switch to systemd default boot. (It was not my machine so i could not keep maintaining it daily)

Posted: **Wed Feb 28, 2024 7:53 am**

coyotito wrote: Wed Feb 28, 2024 7:46 am So it's kinda easy on MX to end up with a systemd system.. does that mean that the SysV option is 'for show' and that the Debian base simply makes it too difficult? Or at least creates problems? I installed MX on an old Lenovo R500 and something happened, can't remember exactly, that required me to switch to systemd default boot. (It was not my machine so i could not keep maintaining it daily)

debian doesn't make it particularly easy. but in my experience with the MX setup the one that tends to trip people up is the libvirt packages. the default depends tend to remove sysVinit, but there are alternate depends that our popular apps entry uses to get libvirt and virt-manager installed. apt will tell you when things are going to be removed, but many people don't pay attention to what apt is saying and go ahead. So nothing will be removed unless you say "yes".

technically sysVinit works better with the antiX live system. so its not "for show". I wouldn't waste my time for "show".

Posted: **Wed Feb 28, 2024 9:06 am**

Hi:
I have Virt-manager installed from "Popular applications" and working perfectly with Sysvinit, it never gave me problems and I use it a lot..., and I never use MX, over Systemd, for me Sysvinit is faster.
When I uninstalled it for my respin with ParrotOS, I already saw all the work behind, impressive....

Best regards

Posted: **Thu Feb 29, 2024 9:32 am**

Senpai wrote: Wed Feb 28, 2024 9:06 am Hi:
I have Virt-manager installed from "Popular applications" and working perfectly with Sysvinit, it never gave me problems and I use it a lot..., and I never use MX, over Systemd, for me Sysvinit is faster.
When I uninstalled it for my respin with ParrotOS, I already saw all the work behind, impressive....

Best regards

I'm not following this clearly ...

Are you saying that you've created a ParrotOS respin inside MX Linux without systemd, or that you installed systemd and have sysvinint working in virtual mode, or ?

Thanks.

Posted: **Thu Feb 29, 2024 9:54 am**

kd4e wrote: Thu Feb 29, 2024 9:32 am
Senpai wrote: Wed Feb 28, 2024 9:06 am Hi:
I have Virt-manager installed from "Popular applications" and working perfectly with Sysvinit, it never gave me problems and I use it a lot..., and I never use MX, over Systemd, for me Sysvinit is faster.
When I uninstalled it for my respin with ParrotOS, I already saw all the work behind, impressive....

Best regards
I'm not following this clearly ...

Are you saying that you've created a ParrotOS respin inside MX Linux without systemd, or that you installed systemd and have sysvinint working in virtual mode, or ?

Thanks.

Sorry for my english translator....
Create a respin of MX-Mate by removing sysvinit as indicated in the previous messages, because ParrotOS only supports systemd, the ParrotOS installation is created from a scritp maintained by them in Gitlab. https://gitlab.com/parrotsec/project/installer-script
In my blog you have more detailed instructions. https://sourceforge.net/p/senpai-respin ... rrotos-60/
But basically it could be done with any other Debian-derived distro, better with a desktop compatible with ParrotOS, which at the moment in version 6.0 I think it is only Mate.

Best regards

Posted: **Thu Feb 29, 2024 5:38 pm**

OK, I sure appreciate the clarification.

I was hoping to hear that you found a way to make ParrotOS work without systemd.

Oh, well.

Thanks!

Posted: **Sun Jun 23, 2024 12:09 am**

updated my systemd_only and sysVinit_only spins to conform with mx23.3. link in first post.

Mostly conform anyway. there are some testing items in there. there is a slightly different mechanism starting and restarting pipewire on the sysvinit only spin. (technically its present on the systemd-only spin, but not used).

there is also a development live initrd on both spins. this is something we've worked on for a while, but I thought it might be worth including for development purposes. that would only affect live users, as installed systems do not use it, and the goal is that the end user doesn't notice a change.

Posted: **Sun Jun 23, 2024 11:32 am**

I have installed the "bare systemd only" respin in a VM and am trying to get it to boot only to a text console and not having any luck.

Started by using the boot options GUI tool to disable the graphical theme, and that worked.

I have changed the kernel parameters from the default "quiet slash slasht" to only "quiet", used "systemctl disable lightdm".

Also tried changing kernel param from "quiet" to "quiet 3" and to "text".

Nothing I've tried works so far. I want the default to be just a text console, but have the option to start a normal X GUI session with startx or equiv cmd line.

Posted: **Sun Jun 23, 2024 12:03 pm**

Those old run level boot codes don’t work on systemd. You need to disable lightdm service.

Posted: **Sun Jun 23, 2024 12:27 pm**

dolphin_oracle wrote: Sun Jun 23, 2024 12:03 pm Those old run level boot codes don’t work on systemd. You need to disable lightdm service.

I have changed the kernel parameters from the default "quiet slash slasht" to only "quiet", used "systemctl disable lightdm".

I did, as I posted above. Apparently you missed that.

All I get is a black screen, not even a flashing cursor.

Posted: **Sun Jun 23, 2024 12:38 pm**

a_freed_man wrote: Sun Jun 23, 2024 12:27 pm
dolphin_oracle wrote: Sun Jun 23, 2024 12:03 pm Those old run level boot codes don’t work on systemd. You need to disable lightdm service.

I have changed the kernel parameters from the default "quiet slash slasht" to only "quiet", used "systemctl disable lightdm".
I did, as I posted above. Apparently you missed that.

All I get is a black screen, not even a flashing cursor.

I did.

possibly this then.

https://unix.stackexchange.com/question ... th-systemd

Posted: **Sun Jun 23, 2024 12:51 pm**

I did try the systemctl set-default to multi-user.target, but not with the -f.
There were a few other suggestions in that link, I'll give them a try.
Thanks!

Posted: **Sun Jun 23, 2024 1:17 pm**

I doubt the -f flag on the disable makes a difference in this case.
I verified the systemd symlinks are valid units for graphical.target & multi-user.target.
I get a warning about runlevel defaults when I use systemctl [status|enable|disable] lightdm.
setting the default.target has no obvious affect on lightdm's unit status. I know thereis an interplay between init.d scripts & systemd, so this issue isn't as pure as it would be under only systemd or sysV.

With X I have the network configured and can reach the Internet. When I disable lightdm (+ chg default, + diff kernel opts: text systemd.unit=multi-user.target) I get a login console prompt after several minutes delay.

Apparently the network doesn't start. See image

Posted: **Sun Jun 23, 2024 2:13 pm**

being targeted at the desktop, the spins are set up to be used with network-manager. there is a cli interface for it. systemd-network likely isn't needed, but if you want to use manually networking, you'll need to set it up.

Posted: **Sun Jun 23, 2024 6:22 pm**

The NM created the /etc/network/interfaces and added nameservers to /etc/resolv.conf.

I did several things, not sure what was essential. I disabled the network-manager with systemd, but interfaces still wouldn't come up. I may have forgotten to stop it tho.

I created /etc/init/network-manager.override file containing "manual". Restart was fast and I had networking afterwards.

I can even switch back to the desktop with startx.

Posted: **Tue Jun 25, 2024 10:46 am**

I just discovered the MX Workbench respin and it might be just what I need to resolve a bootup issue I have on an old Lenovo i5 system I'm trying to install TrueNAS on.

I added a dual SATA M.2 PCIe adaptor to use as a RAID system drive to install it on, and 2 SATA 2TB HDDs for the main storage. I booted the TueNAS installer from a USB flash drive and installed it onto the M.2 SATA drive array without a problem, TrueNAS detected the drives just fine. However the machine's BIOS did not, and TrueNAS wouldn't boot.

I upgraded the BIOS from 2014 version to the latest one released in 2022, still didn't detect the M.2 SATA drives.

I ran into the exact same problem on an old Dell system a coupla years ago running MX21, which I solved by booting it off a USB drive and essentially chrooting to MX installed on the SSD the BIOS refused to boot from. Fro what I see online this is a fairly common problem with older hardware.

Now TrueNAS is based on Debian but uses the ZFS filesystem. I see MX. Workbench provides tools to support ZFS but I'm not sure how to use them. I see the ZFS daemon for FUSE access is started at boot, but I don't see how to mount the TrueNAS drives, mount fails. I'm hoping perhaps I might be able to boot MX Workbench from USB and resolve the TrueNAS boot problem in a similar manor as I did for the Dell system.

I can imagine 2 possibilities:
1) change the MX EFI on the USB to point to the M.2 SATA drives to boot TrueNAS (I believe EFI has support for PCIe devices)
2) MX mounts the M.2 drive (possibly using chroot) and starts its' systemd / init start process.

I'm open to other suggestions for this boot problem.

Posted: **Tue Jun 25, 2024 11:06 am**

a_freed_man wrote: Tue Jun 25, 2024 10:46 am I just discovered the MX Workbench respin and it might be just what I need to resolve a bootup issue I have on an old Lenovo i5 system I'm trying to install TrueNAS on.

I added a dual SATA M.2 PCIe adaptor to use as a RAID system drive to install it on, and 2 SATA 2TB HDDs for the main storage. I booted the TueNAS installer from a USB flash drive and installed it onto the M.2 SATA drive array without a problem, TrueNAS detected the drives just fine. However the machine's BIOS did not, and TrueNAS wouldn't boot.

I upgraded the BIOS from 2014 version to the latest one released in 2022, still didn't detect the M.2 SATA drives.

I ran into the exact same problem on an old Dell system a coupla years ago running MX21, which I solved by booting it off a USB drive and essentially chrooting to MX installed on the SSD the BIOS refused to boot from. Fro what I see online this is a fairly common problem with older hardware.

Now TrueNAS is based on Debian but uses the ZFS filesystem. I see MX. Workbench provides tools to support ZFS but I'm not sure how to use them. I see the ZFS daemon for FUSE access is started at boot, but I don't see how to mount the TrueNAS drives, mount fails. I'm hoping perhaps I might be able to boot MX Workbench from USB and resolve the TrueNAS boot problem in a similar manor as I did for the Dell system.

I can imagine 2 possibilities:
1) change the MX EFI on the USB to point to the M.2 SATA drives to boot TrueNAS (I believe EFI has support for PCIe devices)
2) MX mounts the M.2 drive (possibly using chroot) and starts its' systemd / init start process.

I'm open to other suggestions for this boot problem.

I don't know much about that kind of thing. I suggest opening another thread on it. workbench is one of adrian's spins, not mine.

Posted: **Tue Jun 25, 2024 12:11 pm**

I don't know much about ZFS tools, I just added them to Workbench because somebody requested them, hope they are useful for your case.

Posted: **Sun Jun 30, 2024 10:11 am**

FYI - also noticed the efibootmgr version is very old (17-2). It may be the most recent available, but it doesn't work the way its' man page says it should. It always shows the same info regardless of the -d argument provided for the device.

Posted: **Mon Jul 01, 2024 10:07 am**

I recommend you open a separate thread for what you are trying to achieve and your exact issue that you are having. If you have multiple issues with different respins, apps then separate threads for each would be better to get the help you need. QSI of your setup would also be good. You mention 'an old lenovo i5'. What model/motherboard exactly? How did you install the bootloader if any onto the m2 drive when you installed truenas?

I don't understand how truenas could detect the pcie m2 drive if your bios doesn't detect it? Did you do the installation on another machine?

EDIT: when you start your new thread, please confirm
1) what mode you are booting the machine in (bios, efi,csm etc)
2) how you formatted the usb (mbr or gpt)
3) how and where you installed bootloader/grub(?) during the truenas installation

Posted: **Thu Jul 04, 2024 8:54 am**

BitterTruth wrote: Mon Jul 01, 2024 10:07 am I recommend you open a separate thread for what you are trying to achieve and your exact issue that you are having. If you have multiple issues with different respins, apps then separate threads for each would be better to get the help you need. QSI of your setup would also be good. You mention 'an old lenovo i5'. What model/motherboard exactly? How did you install the bootloader if any onto the m2 drive when you installed truenas?

I don't understand how truenas could detect the pcie m2 drive if your bios doesn't detect it? Did you do the installation on another machine?

EDIT: when you start your new thread, please confirm
1) what mode you are booting the machine in (bios, efi,csm etc)
2) how you formatted the usb (mbr or gpt)
3) how and where you installed bootloader/grub(?) during the truenas installation

I hear you about separate threads, will do. I'll kick it off by quoting this reply and with Lenovo QSI.

I'll answer your question about m2 drive detection here: it's via kernel modules. Every recent Live boot installer detects it, but they load a kernel, MX included. I'm not sure which module is responsible for that PCIe card tho, and it does no good at boot time (need EFI driver binary that detects that PCIe card. UEFI / GPT is how I install everything now). There's a zfsBootMenu.EFI binary I thought was perfect as it actually boots a very small Linux kernel and is capable of finding bootable partitions in zfs, however TrueNAS has altered zfs in a way zfsBootMenu doesn't understand so that doesn't resolve problem either.

Posted: **Thu Aug 15, 2024 11:34 am**

I'm not sure this is the right place for this but I wanted to share my experience using MX Linux minimal 21, I was very Happy then finding a minimal respin as I prefer appimages or blender style standalone apps over installed ones, also installing apps on mx linux is very easy and preinstalled packages will be outdated at some point and has to be upgraded, so I encourage you to make the minimal official as this is the biggest draw back is that you don't get official support, other issues that bothered me were resolved by digging and installing packages that resolved my issues that might not be a problem for super user but normal users might suffer. so I'm sharing my note of things to do after installing Minimal:
minimal version(as downloaded) needs tweeking after install
- install gvfs so that thunar can see external drives or usb flash, and gvfs-fuse & gvfs-backends for ftp server to open within thunar.
- install menulibre for edit applications on the whisker menu to work.
- enable AHS repository for latest Nvidia drivers, from MX Repo Manager goto indivdual sources, find mx.list, check the box that containes ahs at the end of the line.
- after enabling AHS repo, install Nvidia driver normally, from the app menu find "Nvidia Driver installer"
- install Xarchiver for the extract here in the right click menu inside thunar file manager to work.
- to install Qiuck system info which is required by MX forums to give support, you have to know the right package name "qiuck-system-info-gui" (that was a tricky one)

Posted: **Thu Aug 15, 2024 11:39 am**

Is there a difference between "Base" "Bare" "Minimal" ?

Posted: **Thu Aug 15, 2024 12:04 pm**

Check the first post in this thread...

Posted: **Thu Aug 15, 2024 12:08 pm**

It's unclear, to me, what is the difference between this

MX 23.3 sysVinit-only resipin is up, Full version of MX-23.3 64 bit, with systemd removed. elogind, libelogind, and libpam-elogind are utilized to fill those session management requirements.

and the generic non-systemD MX 23.3 ...

Posted: **Thu Aug 15, 2024 1:01 pm**

Systemd is present though not enabled on the official release. The respin does not even have it present.

Posted: **Thu Aug 15, 2024 1:20 pm**

Jerry3904 wrote: Thu Aug 15, 2024 1:01 pm Systemd is present though not enabled on the official release. The respin does not even have it present.

So, otherwise, it's the same.

That's cool.

Thanks!

Posted: **Thu Aug 15, 2024 1:30 pm**

Shaddy wrote: Thu Aug 15, 2024 11:34 am I'm not sure this is the right place for this but I wanted to share my experience using MX Linux minimal 21, I was very Happy then finding a minimal respin as I prefer appimages or blender style standalone apps over installed ones, also installing apps on mx linux is very easy and preinstalled packages will be outdated at some point and has to be upgraded, so I encourage you to make the minimal official as this is the biggest draw back is that you don't get official support, other issues that bothered me were resolved by digging and installing packages that resolved my issues that might not be a problem for super user but normal users might suffer. so I'm sharing a note
minimal version(as downloaded) needs tweeking after install
- install gvfs so that thunar can see external drives or usb flash, and gvfs-fuse & gvfs-backends for ftp server to open within thunar.
- install menulibre for edit applications on the whisker menu to work.
- enable AHS repository for latest Nvidia drivers, from MX Repo Manager goto indivdual sources, find mx.list, check the box that containes ahs at the end of the line.
- after enabling AHS repo, install Nvidia driver normally, from the app menu find "Nvidia Driver installer"
- install Xarchiver for the extract here in the right click menu inside thunar file manager to work.
- to install Qiuck system info which is required by MX forums to give support, you have to know the right package name "qiuck-system-info-gui" (that was a tricky one)

that's not one of my respins, so not the place. but thanks.

Posted: **Fri Dec 06, 2024 11:10 am**

Has anything changed wrt the antix persistence in this mx-23 respin? It may just be my faulty memory, but I thought the only option I needed to select to boot with persistence was p_static_root. Also, when a console screen resolution is selected it doesn't boot with that setting. The "Console" terminology is a bit confusing if that boot option is referring to the X11 display resolution and not the text virtual terminals (Ctrl-Alt-Fn keys).

The first boot used the following options and persistence worked as expected:
- separate static root and home persistence (NOT p_static_root)
- root size: 20GB (option 23)
- home size: 80GB (option 35)
- swap size: 4GB (option 12)

Second boot I didn't let timer expire but rather used up arrow to select top option (MX 23) to boot.
The default option selected is not the top, but rather is Language, something in middle of list.

I'm booting a 120GB SSD in a USB3 enclosure via UEFI on a fairly new bee Link system.

If p_static_root was selected the only difference is that no "home" persistence size is prompted, but the rest is the same. However I didn't get any home persistence with p_static_root. I believe I did get root persistence, not sure, need to retest that.

Is there a way I can reset all those boot options so I could start a new test fresh, without using the USB maker to wipe the whole drive?
Or how can the top "MX-23 64..." option be selected by default so the system will boot with persistence without user intervention?

Posted: **Fri Dec 06, 2024 11:37 am**

a_freed_man wrote: Fri Dec 06, 2024 11:10 am Has anything changed wrt the antix persistence in this mx-23 respin? It may just be my faulty memory, but I thought the only option I needed to select to boot with persistence was p_static_root. Also, when a console screen resolution is selected it doesn't boot with that setting. The "Console" terminology is a bit confusing if that boot option is referring to the X11 display resolution and not the text virtual terminals (Ctrl-Alt-Fn keys).

The first boot used the following options and persistence worked as expected:
- separate static root and home persistence (NOT p_static_root)
- root size: 20GB (option 23)
- home size: 80GB (option 35)
- swap size: 4GB (option 12)

Second boot I didn't let timer expire but rather used up arrow to select top option (MX 23) to boot.
The default option selected is not the top, but rather is Language, something in middle of list.

I'm booting a 120GB SSD in a USB3 enclosure via UEFI on a fairly new bee Link system.

If p_static_root was selected the only difference is that no "home" persistence size is prompted, but the rest is the same. However I didn't get any home persistence with p_static_root. I believe I did get root persistence, not sure, need to retest that.

Is there a way I can reset all those boot options so I could start a new test fresh, without using the USB maker to wipe the whole drive?
Or how can the top "MX-23 64..." option be selected by default so the system will boot with persistence without user intervention?

Presuming systemd iso with UEFI boot. (see this is where quick-system-info i nice, just saying).

No options have been changed, but the console text options I don't think work under systemd boots, if that is the spin you are using. They are basically ignored.

you can change the boot options at any time.

if you want to get rid of the persistence files, boot without any persistence enabled and delete the persistence files you don't want. the default names and locations are /live/boot-dev/antiX/rootfs and /live/boot-dev/antiX/homefs.

if you set the language and timezone, then the top option will be the default.

summary of persistence boot options and what they do:

Code: Select all



persist_all - use separate persistence files for root and home. root is loaded into ram

persist_root - use persistence file for root (home folder included). loaded into ram

persist_static - like persist_all, but not loaded into ram, accessed from live-usb if its writeable.

p_static_root - like persist_root, but not loaded into ram

persist_home - no root persistence file, only home. home is never loaded into ram

frugal_persist - like persist_all, but performs a "frugal" install onto a folder on an internal hard drive. subsequent boots with this option will try to find the existing frugal install and boot it.

frugal_root - like persist_root, but for frugal installs

frugal_static - like persist_static, but for frugal installs

f_static_root - like p_static_root, but for frugal installs

frugal_home - like persist_home, but for a frugal install

frugal_only - do a frugal install, but no persistence used (read only system).

Posted: **Fri Dec 06, 2024 12:44 pm**

Thanks Dolphin. Yes, UEFI booting with systemd only. Quick info below.

When I look at the freshly created USB Maker filesystem is see:

Code: Select all

antiX
boot
cdrom.ico
snapshot_USB-20241125
EFI
lost+found
made-by-live-usb-maker

Do I need to boot, delete peristence files then reboot to start over? Won't the persistence files be locked?
I don't recall seeing a /live/boot-dev folder. What I recall is a /Live-xxx??? folder under root and user accounts.
I'll reboot now and play around, looking more carefully for the rootfs and homefs files.

Code: Select all

Snapshot created on: 20231002_0747
System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto-systemd-only-respin October 02  2023 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: AZW model: SEi serial: <superuser required> UEFI: American Megatrends LLC.
    v: ALDER109 date: 12/01/2022
CPU:
  Info: model: 12th Gen Intel Core i5-1235U bits: 64 type: MST AMCP arch: Alder Lake level: v3
    note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
    microcode: 0x430
  Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled cache: L1: 928 KiB
    desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB
    desc: 1x12 MiB
  Speed (MHz): avg: 790 high: 1449 min/max: 400/4400:3300 scaling: driver: intel_pstate
    governor: powersave cores: 1: 1052 2: 574 3: 400 4: 936 5: 400 6: 1179 7: 400 8: 1200 9: 1048
    10: 1449 11: 451 12: 400 bogomips: 59904
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] driver: i915 v: kernel arch: Gen-12.2
    process: Intel 10nm built: 2021-22+ ports: active: HDMI-A-1 empty: HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:46a8 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) 32 FHD serial: <filter> built: 2017
    res: 1600x900 hz: 60 dpi: 58 gamma: 1.2 size: 698x392mm (27.48x15.43") diag: 801mm (31.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: Mesa Intel Graphics (ADL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0403
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-7:3 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2184 hci-v: 5.2 rev: 2184
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 585 GiB used: 62.52 GiB (10.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT500P3PSSD8 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P9CR40A temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 type: USB model: SSK SSK Storage size: 119.24 GiB block-size:
    physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 1507 scheme: GPT
Partition:
  ID-1: / raw-size: 50 GiB size: 48.91 GiB (97.83%) used: 15.6 GiB (31.9%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot raw-size: 1000 MiB size: 965.9 MiB (96.59%) used: 194.3 MiB (20.1%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 274 KiB (0.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 398.69 GiB size: 391.36 GiB (98.16%) used: 36.97 GiB (9.4%) fs: ext4
    dev: /dev/dm-0 maj-min: 254:0 mapped: home_space-home
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16 GiB used: 512 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    maj-min: 259:3
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2504 pm: dpkg pkgs: 2489 libs: 1317 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 15
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/tailscale.list
    1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
Info:
  Processes: 318 Uptime: 13m wakeups: 5 Memory: 15.39 GiB used: 2.13 GiB (13.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Fri Dec 06, 2024 1:14 pm**

a_freed_man wrote: Fri Dec 06, 2024 12:44 pm Thanks Dolphin. Yes, UEFI booting with systemd only. Quick info below.

When I look at the freshly created USB Maker filesystem is see:
Code: Select all
antiX
boot
cdrom.ico
snapshot_USB-20241125
EFI
lost+found
made-by-live-usb-maker
Do I need to boot, delete peristence files then reboot to start over? Won't the persistence files be locked?
I don't recall seeing a /live/boot-dev folder. What I recall is a /Live-xxx??? folder under root and user accounts.
I'll reboot now and play around, looking more carefully for the rootfs and homefs files.

you can either do as I describe, or while running something else, like you are doing when you list out the file system above, open up the antiX folder and delete the rootfs and homefs files to reset to whatever the current default linuxfs file contains on the next boot of the live system.

I gave you the path for the files. they should be present if you are running persistence. I believe on the systemd respin, while running, /live is symlink to /run/initramfs.

Posted: **Fri Dec 06, 2024 1:28 pm**

I'm booted under the live usb system I just created with USB Maker. /live lists the root of the USB drive, exactly as I posted from the installed MX linux OS. I also see the /live/boot-dev/ folder, and the rootfs file (I booted using p_static_root persistence so home is included, no separare homefs file).

Verified setting Language sets default to top option as you described.

Next I'll check that removing the rootfs file under antiX causes prompting for persistence and swap creation when p_static_root is selected.

Thanks again!

Posted: **Fri Dec 06, 2024 1:52 pm**

Verified removing the rootfs file does cause reset of persistence and if rebooted using that option does prompt for recreating iit and swap.

However, I still don't have persistence on home as I expect using p_static_root. I DO if I use the option that saves root and home separately. I believe you called it persist_static, but IIRC the menu name is slightly different as it specifically uses the word "separate". That works as expected, saving anything I create in user accounts. I am now booted on the live USB with p_static_root. I see I now have OS updates, so will see if they persist. I created the maximum size for rootfs this time. I use menu to shut down, same as with persist_static.

If nothing is saved I don't understand p_static_root. Doesn't seem to work as I have used it before. Also, shouldn't the Language be saved once set, so on subsequent boots it's not the default option? IIRC that's how it worked for persist_static.

Posted: **Fri Dec 06, 2024 2:33 pm**

a_freed_man wrote: Fri Dec 06, 2024 1:52 pm Verified removing the rootfs file does cause reset of persistence and if rebooted using that option does prompt for recreating iit and swap.

However, I still don't have persistence on home as I expect using p_static_root. I DO if I use the option that saves root and home separately. I believe you called it persist_static, but IIRC the menu name is slightly different as it specifically uses the word "separate". That works as expected, saving anything I create in user accounts. I am now booted on the live USB with p_static_root. I see I now have OS updates, so will see if they persist. I created the maximum size for rootfs this time. I use menu to shut down, same as with persist_static.

If nothing is saved I don't understand p_static_root. Doesn't seem to work as I have used it before. Also, shouldn't the Language be saved once set, so on subsequent boots it's not the default option? IIRC that's how it worked for persist_static.

have you used the boot option to save the boot options?

p_static_root doesn't use a separate homefs persistence file, even if its present. changes will be saved in the rootfs file.

Posted: **Mon Dec 09, 2024 10:17 am**

I am aware the p_static_root should save the home as part of root, but that didn't seem to be happening.

I don't recall it being necessary to use the "save boot options" option in the past. I will retest and make sure I do that. I will use the 2nd option to save "both", gfx and whatever the other one is.

Posted: **Tue Dec 24, 2024 9:42 pm**

Updated 23.4 systemd-only respin is up. Link in first post.

the sysvinit-only spin might get updated, I haven't decided yet.

Posted: **Tue Apr 01, 2025 11:32 am**

I hate to admit it, but I'm trying to setup a dual boot system with MX and Windows 10 and MX doesn't detect Windows.

I'm using Dolphin's systemd only respin, which I know from previous posts has a few things omitted. However, it does have the os-prober script. There are comments in grub.cfg for it but nothing in between. I ran os-prober from the command line and it prints a single line with Windows 10 ESP:

Code: Select all

/dev/nvme0n1p2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi

It was a real PITA getting both op systems installed to dual boot. I used to do it all the time but frankly it's been many years since I have (Windows 7 days) and it was much easier then. gparted's resize corrupted the Windows partition so had to start over after many attempts to fix the install failed.

Now I can boot either OS if I use the BIOS hot key to select what to boot, but grub is not the default boot loader and if it is selected from the BIOS menu it doesn't include Windows as I expected.

So how can this be resolved? I want grup to be the default boot loader with an entry for the Windows boot manager.
ANSWER: edit /etc/default/grub and uncomment this line: GRUB_DISABLE_OS_PROBER=false and run sudo update-grub. That gets the Wndows menu entry added to the grub menu. To get grub the default boot loader probably requires BCDEdit or interacting with Windows to set Windows Boot Manager options.

Another issue I have is when I run MX updater it can't rebuild modules for the 2 kernel versions installed, one of which doesn't even show up in the mx package installer:

Code: Select all

Error! Your kernel headers for kernel 6.1.0-28-amd64 cannot be found at /lib/modules/6.1.0-28-amd64/build
 or /lib/modules/6.1.0-28-amd64/source.
Please install the linux-headers-6.1.0-28-amd64 package or use the --kernelsourcedir option to tell DKMS 
where it's located.

I don't see a way to only install kernel hearders so compiles can succeed, aside from installing specific kernel versions. When I install kernel 6.5.0.1 from the package manager it complains when it tries to [also] rebuild 6.1 modules.

So what should I do to resolve that issue? I would be OK with removing the 6.1 kernel, but the package manager doesn't show it as installed (nor did it show the running 6.5 kernel as installed either, until I ran the mx updater).

Code: Select all

Snapshot created on: 20231002_0747
System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto-systemd-only-respin October 02  2023 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: MSI model: B250M BAZOOKA (MS-7A70) v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: 1.70 date: 07/03/2018
CPU:
  Info: model: Intel Core i5-7400 bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
    microcode: 0xF8
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 3300 min/max: 800/3500 scaling: driver: intel_pstate governor: powersave
    cores: 1: 3300 2: 3300 3: 3300 4: 3300 bogomips: 24000
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Micro-Star MSI driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2,HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) 32 FHD serial: <filter> built: 2017
    res: 1600x900 hz: 60 dpi: 58 gamma: 1.2 size: 698x392mm (27.48x15.43") diag: 801mm (31.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics 630 (KBL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
  Local Storage: total: 465.76 GiB used: 57.08 GiB (12.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B7QCXE7 temp: 36.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 78.12 GiB size: 76.35 GiB (97.73%) used: 17.06 GiB (22.3%) fs: ext4
    dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.6 MiB (26.7%) fs: vfat
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /home raw-size: 223.3 GiB size: 218.74 GiB (97.96%) used: 5.77 GiB (2.6%) fs: ext4
    dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16.6 GiB used: 256 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p5 maj-min: 259:5
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2507 pm: dpkg pkgs: 2492 libs: 1317 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 15
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/tailscale.list
    1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
Info:
  Processes: 296 Uptime: 29m wakeups: 1 Memory: 7.65 GiB used: 2.31 GiB (30.2%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Tue Apr 01, 2025 2:45 pm**

the headers for the 6.1.0-28 kernel are still in repo.

Code: Select all

sudo apt install linux-headers-6.1.0-28-amd64

should do it.

it may be that the 6.1 kenrel is partially installed. removing the 6.1 kernel would do it if you aren't using it.

Code: Select all

sudo apt purge linux-image-6.1.0-28-amd64

Posted: **Thu Apr 03, 2025 10:33 pm**

Thanx, that cleaned things up nicely.

Posted: **Tue Apr 08, 2025 12:12 pm**

However, when I ran the update today it still wants the 6.1 kernel headers, despite purging 6.1 from my system. I ran the update-initram -U (iirc the name of the cmd to do that) so it wasn't in the initram or in /boot. What else might be bring in a dependency of an old kernel version? 6.1 isn't even listed in the mx-package installer, and the only 1 I have selected there and configured to boot is 6.5.10.

I believe the solution is that there were references in /lib/modules/6.1.0-* causing packages to remain.
An apt-get autoremove AND an rm -rf /lib/modules/6.1.0-* appears to have resolved the problem, but until the next update is required I am not sure. Odd thing is the fill color of the open box update icon in the task bar disappeared when I ran the autoremove and rm -rf, but clicking that icon now runs the Synaptic package manager which I don't recall it doing before. May be b/c I only clicked it when updates were available?

No builds or references to 6.1.0* kernel headers were needed in the updates I just did, so the autoremove AND an rm -rf /lib/modules/6.1.0-* has indeed resolved the problem.

Posted: **Fri Apr 18, 2025 4:21 pm**

I'm using a brand new i9 system today, and having difficulties getting the nvidia drivers loaded. Here's my current QSI:

Code: Select all

Snapshot created on: 20231002_0747
System:
  Kernel: 6.1.0-33-amd64 [6.1.133-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-33-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto-systemd-only-respin October 02  2023 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: CyberPowerPC product: GamingPC v: -CF serial: <superuser required>
  Mobo: Gigabyte model: B760M C V2 v: x.x serial: <superuser required> UEFI: American Megatrends
    LLC. v: F4 date: 09/27/2024
CPU:
  Info: model: Intel Core i9-14900F bits: 64 type: MST AMCP arch: Raptor Lake gen: core 14
    level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183)
    stepping: 1 microcode: 0x12C
  Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled cache: L1: 2.1 MiB
    desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB
    desc: 1x36 MiB
  Speed (MHz): avg: 808 high: 1062 min/max: 800/5500:5800:4300 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 1062 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800
    22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800
    bogomips: 127795
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GB203 [GeForce RTX 5070 Ti] vendor: Micro-Star MSI driver: N/A alternate: nvidia
    non-free: N/A status: unknown device ID pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 5
    speed: 32 GT/s bus-ID: 01:00.0 chip-ID: 10de:2c05 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: nouveau,vesa unloaded: fbdev,modesetting alternate: nv dri: swrast gpu: N/A
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: default res: 1920x1080 hz: 77 size: N/A modes: N/A
  API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes
Audio:
  Device-1: Intel Raptor Lake High Definition Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 5 speed: 32 GT/s bus-ID: 01:00.1 chip-ID: 10de:22e9 class-ID: 0403
  API: ALSA v: k6.1.0-33-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 04:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek driver: N/A pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
    chip-ID: 10ec:b851 class-ID: 0280
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-14:7
    chip-ID: 0bda:b850 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
  Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: peripheral accept
Drives:
  Local Storage: total: 1.82 TiB used: 22.81 GiB (1.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: LEGEND 800 GOLD size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1.2.P.45 temp: 49.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 102.54 GiB size: 100.37 GiB (97.88%) used: 16.26 GiB (16.2%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot raw-size: 1.07 GiB size: 1.02 GiB (95.27%) used: 104.7 MiB (10.0%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 274 KiB (0.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 1.7 TiB size: 1.67 TiB (98.37%) used: 6.44 GiB (0.4%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16.11 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2565 pm: dpkg pkgs: 2550 libs: 1343 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 15
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/librewolf.list
    1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/tailscale.list
    1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
Info:
  Processes: 493 Uptime: 11m wakeups: 0 Memory: 31.18 GiB used: 2.28 GiB (7.3%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

I first tried to use the latest 6.5 kernel and the 5.3.5 nvidia drivers from Debian backports. That failed after several attempts, now I've purged the 6.5 from the system b/c every time I tried to do an update it continued to attempt to build dkms modules for 6.5 kernel but complained there were no headers installed, yet there were.

Seems I'm now seeing same thing for 6.1 headers.
The MX Package Installer says:

Code: Select all

Module build for kernel 6.1.0-33-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

# lsmod | grep -i nouveau
# lsmod | grep -i nvidia
Both return nothing. Hhowever if you look at the QSI you will see the nouveau driver in the Graphics section, depite there being at least 2 files in /etc/modules.d/ to blacklist it, possibly b/c of an issue with Debian 535 nvidia driver?

I may try to install the packages I downloaded directly from nvidia for v550 and 570, but I need to uninstall the Debian 535 drivers first as .run scripts from nvidia fail unless I do. It also highly suggests I use the Debian drivers, so am exhausting my options with that approach first.

Why the dkms fails to build or find the headers for whatever kernel version I am using seems odd to me, especially with the default kernel which I installed from MX Pkg Mgr.

UPDATE:
/etc/modules-load.d/nvidia.conf--> /etc/alternatives/glx--nvidia-load.conf

Code: Select all

# ls -ls /etc/alternatives/glx
glx/                                        glx--libglxserver_nvidia.so
glx--libEGL.so.1-x86_64-linux-gnu           glx--libnvidia-cfg.so.1-x86_64-linux-gnu
glx--libEGL.so-x86_64-linux-gnu             glx--nvidia-blacklists-nouveau.conf
glx--libGLESv1_CM.so.1-x86_64-linux-gnu     glx--nvidia-bug-report.sh
glx--libGLESv2.so.2-x86_64-linux-gnu        glx--nvidia-drm-outputclass.conf
glx--libGL.so.1-x86_64-linux-gnu            glx--nvidia_drv.so
glx--libGL.so-x86_64-linux-gnu              glx--nvidia-load.conf
glx--libGLX_indirect.so.0-x86_64-linux-gnu  glx--nvidia-modprobe.conf

Posted: **Fri Apr 18, 2025 5:31 pm**

You might try purging and reinstalling dkms

Posted: **Fri Apr 18, 2025 6:10 pm**

EeyoreTheDonkey wrote: Fri Apr 18, 2025 5:31 pm You might try purging and reinstalling dkms

That failed miserably with tons of errors. I am winning to try such drastic suggestions b/c I can restore from a backup, which is probably necessary after this.

Code: Select all

The following packages were automatically installed and are no longer required:
  libcudadebugger1 libegl-nvidia0 libgles-nvidia1 libgles-nvidia2 libgles1 libnvidia-allocator1
  libnvidia-api1 libnvidia-egl-wayland1 libnvidia-fbc1 libnvidia-ngx1 libnvidia-opticalflow1
  libnvoptix1 nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd nvidia-powerd
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  broadcom-sta-dkms* dkms* nvidia-driver* nvidia-driver-full* nvidia-kernel-dkms* rtl8812au-dkms*
  rtl8821ce-dkms* rtl8821cu-dkms*
0 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
After this operation, 189 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 391751 files and directories currently installed.)
Removing broadcom-sta-dkms (6.30.223.271-26~mx23ahs) ...
/usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 --all
Module broadcom-sta-6.30.223.271 for kernel 6.1.0-33-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

wl.ko:
 - Uninstallation
   - Module was not found within /lib/modules/6.1.0-33-amd64/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module broadcom-sta-6.30.223.271 completely from the DKMS tree.
Removing rtl8821ce-dkms (5.5.2.1+git20240526-0~mx23) ...
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
/usr/sbin/dkms.mx remove -m rtl8821ce -v 5.5.2.1+git20240526 --all
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
Module rtl8821ce-5.5.2.1+git20240526 for kernel 6.1.0-33-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

rtl8821ce.ko:
 - Uninstallation
   - Module was not found within /lib/modules/6.1.0-33-amd64/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821ce-5.5.2.1+git20240526 completely from the DKMS tree.
Removing rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
/usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 --all
Error! The module/version combo: rtl8821cu-5.12.0 is not located in the DKMS tree.
dpkg: error processing package rtl8821cu-dkms (--remove):
 installed rtl8821cu-dkms package pre-removal script subprocess returned error exit status 3
dpkg: too many errors, stopping
Errors were encountered while processing:
 rtl8821cu-dkms
Processing was halted because there were too many errors.

Posted: **Fri Apr 18, 2025 8:04 pm**

lets check a few things just to cover the bases

Code: Select all

apt policy linux-image-6.1.0-33-amd64
apt policy linux-headers-6.1.0-33-amd64
apt policy mx-system

Posted: **Sat Apr 19, 2025 5:12 pm**

I managed to get Nvidia driver version 5.7.0 installed and working after a 12 hr session of troubleshooting / investigation with the help of chatGPT. The build / install of that driver (which I obtained directly from Nvidia; I'll have to review but IIRC I chose the open, not proprietary version) succeeded EXCEPT the dkms portions. That took place under kernel version 6.1.0.28. Today without thinking I updated, which required ~213 packages. It updated the kernel to 6.1.0.33. I have not yet rebooted.

I spent most of yesterday trying to build/install Nvidia driver version 5.5.0 after giving up trying to make the 5.3.5 version from Debian backports work. One of the major frustrations that took much time to resolve, was how to fully blacklist nouveau from the initramfs image. chatGPT took 2 tries to get a hook script right that finally accomplished that. Even with the -Z and other options for the Nvidia .run script, that script always failed and inspecting the initramfs showed nouveau still present, even after several attempts to blacklist it.

Once the hooks script was working and nouveau.ko was removed from initramfs, the Nvidia 5.5.0 script should have worked, but it didn't!

I decided since my GPU was the latest generation driver v5.5.0 might not be adequate, so I ran the 5.7.0 Nvidia script which succeeded, except for DKMS. At least the driver was installed and nvidia-smi was happy.

Now it's a matter of figuring out why the DKMS build fails.
-- END OF BACKSTORY --

Dolphin, here is the answer to your policy questions for the current -33 and previous -28 kernels:

Code: Select all

# apt policy linux-image-6.1.0-33-amd64
linux-image-6.1.0-33-amd64:
  Installed: 6.1.133-1
  Candidate: 6.1.133-1
  Version table:
 *** 6.1.133-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status

# apt policy linux-headers-6.1.0-33-amd64
linux-headers-6.1.0-33-amd64:
  Installed: 6.1.133-1
  Candidate: 6.1.133-1
  Version table:
 *** 6.1.133-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status

# apt policy mx-system
mx-system:
  Installed: 23.10.02mx23
  Candidate: 23.10.02mx23
  Version table:
 *** 23.10.02mx23 100
        100 /var/lib/dpkg/status

# apt policy linux-image-6.1.0-28-amd64
linux-image-6.1.0-28-amd64:
  Installed: 6.1.119-1
  Candidate: 6.1.119-1
  Version table:
 *** 6.1.119-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status

# apt policy linux-headers-6.1.0-28-amd64
linux-headers-6.1.0-28-amd64:
  Installed: 6.1.119-1
  Candidate: 6.1.119-1
  Version table:
 *** 6.1.119-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        100 /var/lib/dpkg/status

Posted: **Sat Apr 19, 2025 6:01 pm**

Here is the log for the dkms. Same failure cause for 28 and 33 kernels: can't find vmlinux:

Code: Select all

Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia-peermem.ko due to unavailability of vmlinux
  BTF [M] /var/lib/dkms/nvidia/570.133.07/build/nvidia-drm.ko
Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia-drm.ko due to unavailability of vmlinux
  BTF [M] /var/lib/dkms/nvidia/570.133.07/build/nvidia-modeset.ko
Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia-modeset.ko due to unavailability of vmlinux
  BTF [M] /var/lib/dkms/nvidia/570.133.07/build/nvidia.ko
Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia.ko due to unavailability of vmlinux
  BTF [M] /var/lib/dkms/nvidia/570.133.07/build/nvidia-uvm.ko
Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia-uvm.ko due to unavailability of vmlinux
make[2]: Leaving directory '/usr/src/linux-headers-6.1.0-33-amd64'
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-33-common'

MX Linux Forum

dolphin_oracle's respins (updated June 23, 2024)

dolphin_oracle's respins (updated June 23, 2024)

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 2-12-2022)

Re: dolphin_oracle's respins (updated 5-30-2022)

Re: dolphin_oracle's respins (updated 5-30-2022)

Re: dolphin_oracle's respins (updated 5-30-2022)

Re: dolphin_oracle's respins (updated 5-30-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-24-2022)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)

Re: dolphin_oracle's respins (updated 9-10-2023)