You are not logged in.
Just working an a new PC with Beowulf and Cinnamon as desktop.
Got gnome-system-log installed, and do not like it. It just shows syslog, auth and 2 other uninteresting logs. From my Mate desktops with mate-system-log I am used to see the complete contents of /var/log. Well, tried to install mate-system-log on the Cinnamon system, and failed. Error: package mate-system-log can't be found.
A closer look showed that on my Mate systems I have an application in /usr/bin/mate-system-log, but I have no idea to which package this application belongs to. Searching in dpkg.log did not help. Search in Synaptic with all available options also did not help. Looked at the files that belong to Mate-desktop-environment*..., no trace of the mate-system-log.
How can I find out in which package this application is hidden?
Thanks, rolfie
As lang as you stay with ASCII you will have 3.2.7. If you move to Beowulf, you will get 3.8.8.
rolfie
Once booted up efibootmgr -v reported an error. After fiddling around for a while I ran
grub-install /dev/sdato try and ensure that it would still boot. This was ok and does still boot via grub as expected.
Wonder why this worked. This is CSM style, not EFI. To my knowledge you have to use something like
# grub-install --bootloader-id=devuanas I use to generate a devuan entry (no secure boot).
efibootmgr (with or with "-v") now reports
efibootmgr No BootOrder is set; firmware will attempt recoveryHowever, as a side effect of all this, the grub entry for Xen now works and I am posting this with Chimaera as Dom0 under Xen.
Doesn't tell me anything, don't use Xen.
The directory /sys/firmware/efi/efivars/ exists, but is empty.
Is the directory mounted?
As everything seems to be working, it is tempting to leave it alone. But where is the fun in that!
It would be nice if efibootmgr agreed with the firmware screen (what is that called, it can't be the BIOS screen, can it?)In writing this an obvious point becomes clear. If I am running Devuan under Xen, then access to EFI stuff may be impaired. Having booted on the bare metal,
efibootmgr BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0004,0002 Boot0000* debian Boot0002* Hard Drive Boot0004* zenefibootmgr -v BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0004,0002 Boot0000* debianCould not parse device path: Invalid argumentIt is interesting that it couldn't parse option 0000 as that is the one that is actually booted.
Also the directory /sys/firmware/efi/efivars/ now contains the expected stuff.
Setting up stuff seems to be easier on the firmware screen than using efibootmgr as selecting the the parts of the path to the boot image is easier when there is a choice of options rather than entering a complex command line. The first part of the path was incomprehensible to me, but there was a choice of one (disk?) and from there the options were obvious.
What do you mean by "firmware screen"? The bios? On my 3 latest ASUS board with AMI bios I haven't got any chance to modify any settings but the boot order, if any.
Confused, rolfie
Many months later:
Learned that I have to format the disk as dvdrw and with UDF2.01. Then mounting RW works.
rolfie
Dependency hell.
We could reply: What the hell are you doing here?
Before you try to clean out your installation you better read some literature about sources.list and Franken-Debian. Here are some useful links.
You could start on the main page of Devuan.org: https://devuan.org/,
about installation: https://devuan.org/os/install,
about releases: https://devuan.org/os/releases
about sources.list recommendations: https://devuan.org/os/packages
about FrankenDebian: https://wiki.debian.org/DontBreakDebian
HTH, rolfie
Edith: added link to the Debian Wiki.
Got a RX580 installed on a Ryzen 2700X computer. Worked fine with ASCII and now with Beowulf with KMS driver (included in the kernel) and firmware. You need non-free added to the sources.list, you install amd64-microcode and firmware-amd-graphics. On ASCII you better pull firmware-amd-graphics from backports.
If you need some guidance, check out the Devuan.org website, there you will find some instructions how to set the sources.list.
No fiddling required with amdgpu-pro.
rolfie
When Synaptic is open you can't install anything with apt(-get).
# apt install cups
To encourage you, please read https://dev1galaxy.org/viewtopic.php?id=3358.
rolfie
The following trick may do what you want:
1.) apt remove grub-efi-amd64-signed
2.) grub-install --bootloader-id=devuan
Worked in my Chimaera VM.
I can confirm that also Chimaera (in a VM) has the same behaviour. What easily worked under Beowulf is no more working with the testing/unstable stuff.
Needs a closer look.
rolfie
That will work if you don't use Secure Boot. But you still will have a debian and a devuan EFI directory.
Use the efibootmgr to boot the devuan entry. If that works, you can delete the debian entry with the file manager.
rolfie
Got two PC here with Beowulf installed from scratch, both with Mate desktop. No ash, just bash and bash-completion are installed. Both work fine whenever calling Mate terminal as user or with pkexec as root. Same on the desktop opening the (Mate-)terminal.
Also got two Beowulf VMs running in Virtual Box. One is based on an ASCII upgrade with Mate. Same setup as above, works like a charm w/o ash. The other one is a native Beowulf with Cinnamon. The I only have xterm, but that also works fine.
rolfie
I m sitting on fresh installed Beowulf. No ash, just bash, dash and bash-completion. No problems.
Have you got bash-completion installed?
I am not using the alias.
rolfie
Checked with my ASCII installation on the same PC. Had to update Veracrypt to run the same version first. There I do not see the shutdown delay I have with Beowulf. Something is different here.
rolfie
There are several options I know how to mount a Veracrypt volume.
1.) Veracrypt GUI
2.) Veracrypt cli interface
3.) cryptsetup
I use 1 and 2. All in common is that you have to tell the sw which container to open and where to mount it. No idea what LibPAM-TMPDIR does or requires.
If you use 2 you will see the mounted container(s) in the GUI. I am not astonished that a container opened with cryptsetup isn't seen by the GUI.
rolfie
I do consequently use the backports kernels on all my machines. Did that from Squeeze onward for various generations of hardware. Never had any issues.
And every now and then I used bugfixes from backports. But thats rare.
rolfie
VirtualBox is a buggy pile of shite which is slower than QEMU/KVM and the developers have a tendency of covering up and ignoring security issues.
See also https://bugs.debian.org/cgi-bin/bugrepo … bug=794466
And it relies on blobs.
Maybe you're right. But for me VBox does what I expect it to do. I can pass through USB drives w/o any problem, UEFI mode is sort of crap but available. I can boot a VM from an iso, ....
Tried the same with qemu/kvm and gave up when bold promoters of qemu/kvm didn't have any advise how to solve my issues. I guess this highly promoted piece of SW still requires a lot of brains to really make it a competition for VBox.
rolfie
I am running 6.1.10 directly from Oracle, installed with dpkg -i. Extension pack installed, and guest extensions in each of my old and new virtual machines.
Had some fun to get it working on Beowulf, see https://dev1galaxy.org/viewtopic.php?id=3641.
Maybe it helps. Good luck, rolfie
No issues here with latest VB directly from Oracle on Beowulf and Chimaera as guest. No issues with systemd.
Have you installed the extension pack?
rolfie
If Caja is correct, 1.7TB. About half of a 4T drive.
rolfie
Beowulf amd64, openrc as init, shares from file server mounted with nfs4. Veracrypt is used to open a NTFS container as data drive for a Win7 VM. This is done via a script in the user startup folder.
Shutting down this container seems to cause a about 15s long delay past the line "Asking all remaining processes to terminate".
The complete output looks like this:
[ok] Asking all remaining processes to terminate ... done.
Currently running processes (pstree):
init-+-rc---openrc---openrc-run---sendsigs---pstree
|-rpc.statd
|-rpcbind
|-veracrypt---dmsetup
'-veracrypt---18*[{veracrypt}]
[FAIL] Killing all remaining processes ... failedOn another PC with a similar setup, just without Veracrypt, the shutdown has normal speed.
How can I speedup closing the Veracrypt volume?
rolfie
You move the themes folder to /boot/grub and specify that in /etc/default/grub. From my notes:
# mkdir /boot/grub/themes
# cp -r /usr/share/desktop-base/grub-themes/cinnabar-grub /boot/grub/themes/
# nano /etc/default/grub
Change entry to:
GRUB_THEME=/boot/grub/themes/cinnabar-grub/theme.txt
# update-grub That fixes the error and brings the new cinnabar theme to grub. If you do not want that you can copy the default theme.
rolfie
okay so if i understand this correctly it has something to do with desktop-base and grub, not sure if it is present with or without encryption though?
Only appears with encryption, because when grub starts there is no access to /usr/share/..... yet.
rolfie
Have a read of https://dev1galaxy.org/viewtopic.php?id=3471. Isn't that the same kind of issue you see? Error message is slightly different, but similar.
rolfie