You are not logged in.
Any idea as to what may have caused it?
I would presume that an ISO image was burned to the device at some point. The magic string laid down by that process can be very persistent.
It is an *.iso file I have used at one time or another.
Yes, probably.
Clear the magic string with
# wipefs -o 0x8001 /dev/sdbMerely disabling wicd with this handy utility -- glad I chose sysv for my init system!
-- does not work. I get error messages about the GUI not working until the daemon is restarted.
Hmm. Disable the tray application then:
mkdir -p ~/.config/autostart
cp /etc/xdg/autostart/wicd-tray.desktop ~/.config/autostart/
echo 'Hidden=true' >> ~/.config/autostart/wicd-tray.desktopjust what is recreating these links the instant they are deleted?
They are created dynamically by udev.
I then boot into my alternate (in construction) Beowulf 3.1.0 install to see if I can reach into the other installation's system files but I cannot see past /media/groucho/devuan/dev, even as root.
That's because udev isn't running in that system so /dev hasn't been populated.
Can we see
wipefs /dev/sdb{,1}Modify the command if the problematic drive has been assigned a different letter.
fsmithred had chimaera-based live isos but: no xorg...
You can always install X afterwards.
For example:
# apt install tasksel
# tasksel^ That will let you select any of the full desktop environments, just as you would from a netinstall ISO image.
It's not just the kernel. That generation of Intel integrated graphics chips require a newer Mesa version.
The OP could try chimaera now or even add the MX Linux repositories — they've backported Mesa to a buster base, I have a guide to adding & pinning their repositories over at forums.debian.net — but neither option is ideal. I would usually recommend Arch for new hardware but most people here won't like that because of the init system that shall not be named (or spelled correctly).
When I do a 'nano' of X11.conf it states I am creating a new file. Having looked in /etc I can see quite a lot of different things so not sure where to go from here.
See man xorg.conf for a list of the files that can be used to configure X. The modern way of doing it is to add snippets in individual files under /etc/X11/xorg.conf.d/ (the files can be called whatever you want as long as they end in .conf).
I don't know much about multi-monitor setups or VGA passthrough but see https://wiki.archlinux.org/index.php/Multihead & https://wiki.archlinux.org/index.php/PC … h_via_OVMF ← that's what I would follow.
Does this mean that lsb-modules are no longer necessary? And if so, does this also apply to devuan?
Yes and yes.
* Network manager and WICD and Bluetooth?
If you don't want them running then disable them:
# apt install sysv-rc-conf
# sysv-rc-confI got the answer that I should install lsb-core, but lsb-core is already installed on my system
There is no lsb-core package in Devuan beowulf, it is obsolete.
Note that shimx64.efi will work and allow Secure Boot to be enabled in Devuan but it is hard-coded to use /EFI/debian on the EFI system partition.
rolling debian packages into the repos without checking them for debianisms.
That's not how it works: https://dev1galaxy.org/viewtopic.php?id=3192
So you do understand how to make unattended-upgrades work then? I think the community would appreciate a quick HowTo thread in the Freedom Hacks section more than this pointless rant.
then did as Head_on_a_Stick said and
gpasswd -a $USER inputbecause I'm running headless over SSH. Not sure if this is strictly necessary?
No, it isn't. Don't add users to the input group unless you have to.
model name : Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
That won't work with Devuan beowulf.
https://lwn.net/Articles/658809/
Ask a search engine for more details about this (which you should already have done before posting here btw).
^ Good point rolfie, thanks for the clarification. I just presumed the OP had installed the metapackage, which was silly of me.
What is your CPU? If it starts with 10 or 11 then you're shit out of luck with beowulf.
Stormzy — Gang Signs & Prayer.
No link. Buy the album, it's great. If you like Grime ofc.
Is the gvfs-backends package installed?
Intel chips work well
10th generation Intel chips onwards need a newer Mesa version than is available for Devuan beowulf. The same is true for the most recent AMD cards.
The OP should also note that all current graphics cards require non-free firmware even with the open source drivers supplied by the kernel.
See also http://forums.debian.net/viewtopic.php?f=16&t=142974
EDIT: and please change the thread title — your machine doesn't "hang", it just fails to load the graphical desktop.
Are you sure you're not just trying to get out of combat duty?
But seriously, have you checked ~/.xsession-errors?
Does apt-get pick up updated kernel packages from backports automagically?
Yes, it does. Just run the usual apt update && apt upgrade. Don't target backports for updates & upgrades, that can break your box.
Like this?
Well that would work but I would use either/or. If you really want to use both methods then call the full path for date as well.
And for the log you should probably record both stdout and stderr:
/sbin/fstrim -a -v >> "$LOG" 2>&1It's not a permissions issue, it's a PATH issue.
Either set PATH in the script or call the full path to fstrim in the script.
EDIT: gah, too slow...
For the kernel, I downloaded the 5.11.2 source from kernel.org
How are you planning to keep that updated? That version is already old.
The beowulf-backports repository will be tracking the 5.10 LTS branch, which might be sufficient for your processor. That version is slightly delayed but your current strategy will leave your system with known kernel vulnerabilities unless you track upstream development assiduously and manually compile newer versions as they are released.