Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
sudo systemctl enable proc-sys-fs-binfmt_misc.automount
[sudo] password for jb:
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB Personal: Lenovo X1 Carbon with MX-23 Fluxbox Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
show that the binfmt_misc filesystem is mounted?
On a standard MX-23 system using systemd boot It's this:
tim@bookworm:~$ mount | grep bin
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=5275)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
Jerry3904 wrote: Sun Oct 06, 2024 12:51 pm
BTW: if this is just my system then we'll just let this go.
I will reinstall since nothing on it is critical.
could be 5 graphics playing up in a way that doesn't show up on the 4. @CharlesV I don't really know what the changes were to the theme. only MXLiveLogo and MXImagine are different though. the other themes are all the same as always were, so you could try those.
I will download the deb's and test. There were two changes to the MXLiveLogo:
- I had a run condition past the bounds of the array ( <= instead of < )
- And I had used "MaxCallback" in the calculation of which image we were on, and should have been using "max number of Images"
MXImagine is a much modified code segment.
*QSI = Quick System Info from menu (Copy for Forum) *MXPI = MX Package Installer *Please check the solved checkbox on the post that solved it. *Linux -This is the way!
BTW: tested my OpenBox RPi respin, derived from the official MX RPi. Splash worked on first boot, then I upgraded and new splash also worked just fine. After testing your suggestion, I'm going to create a clean install from the 23.4 and see how that goes.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB Personal: Lenovo X1 Carbon with MX-23 Fluxbox Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
A weird event: after doing my OB test, I returned to my standard boot (from a USB) and--for once--the splash showed! Tried it a second time and it failed again, so I give up on this erratic stuff. Will download a clean image and test on that since that's what really matters.
Thanks for the suggestions, back later.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB Personal: Lenovo X1 Carbon with MX-23 Fluxbox Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
OK, I don't know what has been going on but it's apparently irrelevant in this context. I upgraded a clean 23.3 that I already had, did a bit of cleanup, then rebooted and the splash was fine.
I haven't done much at all with the MX RPi except keep it upgraded--aside from changing wallpaper, ,panel, etc.--so I'm hard pressed to identify a likely source for what I have been seeing.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB Personal: Lenovo X1 Carbon with MX-23 Fluxbox Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
