I have tried many times, to get into the Fujitsu's UEFI configuration menu, to no avail. So i cannot reset to factory defaults.
It was a Big Mistake to disable the primary ssd. And also forgetting to do domething about those remains of previous install in that boot menu, that was a BIg Mistake too.

Found out the Hard Way that is not a proper way to enforce booting from optical disk.
It doesn't matter if that ssd is connected or not.

Now Lord Anubis is in need for a new host.

Set a main passwd for the firmware.
Set passwd for ssd, disabled asking it later.
Enabled tpm, disabled secureboot.
Enabled booting for removable drives.
Enabled boot menu also.
Enabled that boot menu for all users, not just for admin.

And noticed that cannot boot from usb-dvd-drive if that ssd is disconnected.
It may have been a mistake to set that disk passwd. I suspect it to be the cause that firmware needs ssd before booting from optical.

In boot order optical is before ssd, but not the absolutely first, i think. Have to confirm if i get a chance.

E. Firmware version is 1.28 . The date of it is from december of 2022, i think. Suspect that date is when the firmware was updated, not the date when fujitsu published it.

If you have rules you're happy with, there's also netfilter-persistent and iptables-persistent.

I don't think sudo in itself is a disease. But that "ALL=ALL NOPASSWD"-thing definitely is.

Tried heads once, 4 years ago. For some reason the dvd i burned didn't boot. Would like to try again some day with more recent .iso .

I haven't been troubled with rubber-feets of laptops.

But hardware support is always a problem with linux. Even with desktops.
Ok, usually you can get your graphics card working, kind of. But then you'll be stuck with the distro's kernel. No compiling the latest from kernel.org if you want those blobs working.

And then there's the new firmware that replaced BIOS. Recently noticed that  i cannot boot from dvd if ssd is removed. What will i do if that ssd breaks?
With old hardware i could boot from dvd even after removing the hdd. But not necessarily with new machines.
I find that annoying.

This mis-adventure continues.

Today i noticed: https://wiki.archlinux.org/title/intel_ … stallation .
These sounded familiar: "There have been couple reports where the whole graphics stack hard freezes" , "not even switching to a different virtual console work" .
And I think there's intel graphic chip in that machine.

But it will take a while to get a chance to try SysRq.
Last night i started the reinstall process. Erased the ssd with dd as a first step, to start with a "clean slate".

Now i have a "kind of a theory" why "freezing" happens. When trying to log out, lightdm tries to communicate with polkit but it can't and freezes. But on the other hand, then i would expect that package to go away when removing polkit-packages.
Not yet sure how that explains problems with startx. Should find out if there is xterm installed outside of vm.

And btw, couldn't reproduce the "freezing situation" inside a vm just yet. Did many things differently from 2-3 months ago, thats for sure. Should have documented better how the install went during march-april.

Edit. https://pkginfo.devuan.org/cgi-bin/pack … d=246.10-5 the "Recommends:"-part.
So changing displaymanager won't necessarily help if it is elogind that tries to access policykit-related stuff that is not available.

And elogind need dbus also.

Now there seem to be a new problem:if i want to keep polkit- and libpolkit - packages out of my system, i can't have wireplumber.
So i may have to learn how to make Fujitsu's audio work for real, without helper packages.

Btw. any ideas about a desktop environment without need for polkit or policykit?

So, xorg of Daedalus, it needs something that is not available when there is no proper display manager installed, am i right?
What it is that i need to make startx working?

Btw.

ps -aux | grep seat

returned

root SOME_THINGS /usr/sbin/seatd -g video

. So now there's seatd running, as root.
But if it is running as root, it shouldn't have had problems with access rights of /dev/input/* .

Edit.

And when started xinit as normal_user "ps -aux | grep X" returned

$normal_user $some_things tty1 /usr/lib/xorg/Xorg:0

.
So X is running as normal_user when i start it from text_mode . Running as $normal_user would explain the problems with /dev/input/* - files .

It has been a while since i had to write .xinitrc . So, after "#!/bin/sh" , i start window_manager with & at the end of the command, and after that some other commands, right?

Not happy about adding normal_user to group input...

Another experiment.
Installed Daedalus netinstall into vm.
After that told apt to install twm and xinit.
Tried startx with root and normal_user. In both cases startx exited immediately, no freezing.

As normal_user command

 grep EE ~/.local/share/xorg/Xorg.0.log 

returned rows like:

(EE) seatd_libseat device not open (/dev/input/eventX) 

and that normal_user doesn't belong to group input.
And same "EE rows" can be found in /var/log/Xorg.0.log after running startx as root.

EDit. after "apt-get install lxde" , running startx as normal_user started lxde session which i could exit without problems.
Let's find out again what happens after removing unnecessary packages.

Edit.2.
purging packages from libcupsfilters* to gstreamer* + autoremove and lightdm still works as expected
and same for going te previous list to vim and others.
Next try to remove pol-packages... "login box" works. Also i can use twm's menu because i installed that.

Removing "libcupsfilters* ilbgphoto* avahi* blu* coinor* colord* cups* exim* ftp* gcr*"+"apt autoremove" after that and logging in and out still works.
Let's remove some more.

Next "apt-get remove --purge brltty* openssh* network-manager-* mobile* modem* && apt autoremove ".  Make "netstat - tulpan"'s list empty.
Still login&lgout works.

apt-get remove --purge ghostscript* gimp-data gir* gstreamer* gnome* gnupg* gvfs* && apt autoremove
and still log{in,out} are ok

"gnome* gnupg* gvfs* inetutils-telnet iw libreoffice*" purged+autoremove
still login/out ok

mailcap,mutt,ppp can be purged
purging pol* seems to want to remove lxde-related packages, should be more precise with pol-stuff, policykit-1* is tied to lxde-packages
maybe poppler have to be there too

vim* , wireless* wpa* can be removed
and lgin/out still ok

at least lxpolkit seems to need policykit-packages, lets see how Daedalus works withoyt that. I guess that was ok, but removing anything more lxde-related seems to be too much.

... And outside of vm there are no policykit/polkit/pkexec-packages installed. Maybe i found the source of problem- maybe not. Are there any desktop software in Devuan which doesn't need policykit or polkit?

Now i know that i should have done incremental backups instead of full.
Trying to remove xfce-  and elogind- related packages had some side effects.
If i have to reinstall, i think i will use Chimaera dvd instead.

Last year i tried Chimaera minimal livedvd. Managed to install lxde without problems. At least i like to think that display manager and startx worked as expected.

But it was the "new" desktop then. With Fujitsu, all bets are off.