You are not logged in.
- Topics: Active | Unanswered
#1101 Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-23 19:31:23
- rolfie
- Replies: 14
I am trying to add Beowulf as second OS past an Arch installation on the SSD of a brand new PC. I would like to share my experience and need some advice how to deal with the remaining problems.
Basics: HW is a Ryzen 3700x on ASUS X570-Pro mainboard, latest bios. UEFI system, Arch installed as first OS on the SSD (also encrypted with LWM), enough space on the EFI partition, labelled as ESP. CSM off, secure boot off, all keys deleted, Uefi driver first.
The Beowulf beta desktop iso was written to a USB stick with rufus/Windows 7. Got a small 2G boot partition and a large 256G partition for an encrypted LVM setup by gparted past the Arch stuff. The stick boots fine in EFI mode, I used the expert installer and manual partitioning. First installation attempt failed with grub not installing. On the second attempt I paid attention to have a network connection to a mirror. This time the grub installation worked. This is an important topic.
Beowulf is now booting, I have got Lightdm/Mate desktop running. With the patch applied to /lib/cryptdisk.functions the shutdown is fast.
First effect: in the efibootmgr is no more indication of the Arch boot entries. It looks now like this:
# efibootmgr -v
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0008,0009,000A,000C,000D
Boot0000* GRUB HD(1,GPT,44444444-5555-4444-8888-999999999999,0x800,0x400000)/File(\EFI\GRUB\GRUBX64.EFI)
Boot0001* debian HD(1,GPT,44444444-5555-4444-8888-999999999999,0x800,0x400000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0004* Hard Drive BBS(HD,,0x0)..GO..NO........o.G.I.G.A.B.Y.T.E. .G.P.-.A.S.M.2.N.E.6.1.0.0.T.T.T.D....................A..........................dy.%.w .....2..Gd-.;.A..MQ..L.S.N.1.9.3.5.0.8.9.0.0.3.8.5........BO
Boot0005* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO..........A.S.U.S. . . . .B.W.-.1.6.D.1.H.T....................A.............................................>..Gd-.;.A..MQ..L.L.K.J.P.E.C.3.B.1.4. .3. . . . . . . . ........BO
Boot0008* debian HD(1,GPT,44444444-5555-4444-8888-999999999999,0x800,0x400000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot0009* Hard Drive BBS(HD,,0x0)..GO..NO........o.G.I.G.A.B.Y.T.E. .G.P.-.A.S.M.2.N.E.6.1.0.0.T.T.T.D....................A..........................dy.%.w .....2..Gd-.;.A..MQ..L.S.N.1.9.3.5.0.8.9.0.0.3.8.5........BO..NO..........C.T.5.0.0.M.X.5.0.0.S.S.D.1....................A.............................................>..Gd-.;.A..MQ..L.9.1.5.0.1.E.6.E.8.8.7.A. . . . . . . . ........BO
Boot000A* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO..........A.S.U.S. . . . .B.W.-.1.6.D.1.H.T....................A.............................................>..Gd-.;.A..MQ..L.L.K.J.P.E.C.3.B.1.4. .3. . . . . . . . ........BO
Boot000C* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(1,0)/HD(1,MBR,0x97df71f4,0x800,0x1ca3800)..BO
Boot000D* USB BBS(HD,,0x0)..GO..NO........q.S.a.n.D.i.s.k....................A.............................>..Gd-.;.A..MQ..L.4.C.5.3.0.0.0.0.0.4.0.3.2.8.1.1.3.2.3.4........BOI did manually modify the boot number from 1 to 8. No change. Also removed grub-efi-amd64-signed, did not help. Why is Arch overwritten? I though that two Linux OS could reside on the same drive with one efi partition without conflict.
Second side effect: When booting before loading the grub screen I get this error. I am requested to press a key, or if I wait long enough the grub screen pops up. The output actually is in German, I translated it.
Error: no such device: 76c68ea3-5785-49b4-b93e-66f4de5b3a2b
Error: no server specified This uuid is the one of the encrypted LVM partition for Beowulf /dev/nvme0n1p4. What is going on here?
[Edit: Thats wrong, its the uuid of the root partition inside the LVM! Edit]
Third side effect: after upgrading to kernel 5.4-bpo.4 kernel panic, due to EFI_MEMMAP is not enabled.
Thanks, rolfie
Edit: some clarification, more info added.
#1102 Re: Hardware & System Configuration » Old Brother Scanners broken in Beowulf (problem descr. and workaround) » 2020-04-18 11:33:55
As a workaround try the following: install ASCII in a virtual machine and forward the scanner to this machine. I assume these are USB devices, that should work ok with Virtual Box (had such a setup for a long time with a scanner that only had Windows drivers around).
Its not comfortable, but ok for a lower volume.
rolfie
#1103 Re: Other Issues » What would cause wget to work and apt to get "Connection failed"? » 2020-04-17 19:49:34
According to this page https://devuan.org/os/ you should use:
deb http://auto.mirror.devuan.org/merged jessie mainGive it a try.
rolfie
#1104 Re: News & Announcements » Beowulf Beta is here! » 2020-04-08 08:09:31
Still getting error
E: The value 'beowulf-backports' is invalid for APT::Default-Release as such a release is not available in the sourcesMaybe the error is related to the !Italian! sources.list?
Take a close read of https://devuan.org/get-devuan, paragraph Package repositories and https://dev1galaxy.org/viewtopic.php?id=3276. Country codes are deprecated.
A simple deb http://deb.devuan.org/merged beowulf-backports main (contrib non-free) should do the job.
rolfie
#1105 Re: News & Announcements » Beowulf Beta is here! » 2020-04-07 16:56:15
Look at this old thread: https://dev1galaxy.org/viewtopic.php?id=2023
rolfie
#1106 Re: News & Announcements » Beowulf Beta is here! » 2020-04-06 18:51:32
Something is a bit strange about beowulf backports or maybe more like the package search? I looked on my fileserver running Beowulf for about a year now. beowulf-backports are present, apt lists packages like linux-image-5.4.
When I use the https://pkginfo.devuan.org/cgi-bin/d1pk … se=beowulf to search for linux-image-5* that are present in backports, I get:
26 results for "linux-image-5*" in beowulf (in 7.427974ms)
[beowulf] linux-image-4.19.0-8-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-amd64-unsigned-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-unsigned-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-unsigned-4.19.98-1
[beowulf] linux-image-amd64-4.19+105+deb10u3
[beowulf] linux-image-amd64-dbg-4.19+105+deb10u3
[beowulf] linux-image-amd64-signed-template-4.19.98-1
[beowulf] linux-image-cloud-amd64-4.19+105+deb10u3
[beowulf] linux-image-cloud-amd64-dbg-4.19+105+deb10u3
[beowulf] linux-image-rt-amd64-4.19+105+deb10u3
[beowulf] linux-image-rt-amd64-dbg-4.19+105+deb10u3
[beowulf-security] linux-image-4.19.0-6-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-amd64-signed-template-4.19.67-2+deb10u2Whats wrong there?
rolfie
#1107 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-04 11:43:04
apt remove libreoffice_6.4 will do. The beauty of this approach is that dpkg is part of the Debian/Devuan package administration. The installation will be listed as local in the package database. You may use all tools/commands you usually use, like synaptic, apt/apt-get, ....
As root enter apt list libreoffice in a terminal and see what you get.
rolfie
#1108 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-04 07:58:37
/tmp is cleaned out on every reboot, so if you have extracted the tarball to there as suggested, you don't need to worry about the debs.
Anyhow, when extracting a LO tarball, the files will always end up in a subdirectory with the version in the name (when you specify to create directories as int he comrpessed image).
rolfie
#1109 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-03 08:28:28
You can use a tarball from the Libreoffice website to install. Make sure you have a deb and the right architecture. Optionally also load the offline help and the language pack. Then do:
- Extract the contents of the tarball(s) to /tmp. With Mate desktop I use Engrampa.
- As root go into /tmp, cd into LibreOffice_6.4.2_Linux_x86-64/DEBs.
- Install with dpkg -i *.deb
- Optionally repeat with offline help and the language pack.
- Reboot and use LO
rolfie
#1110 Re: Installation » How do I make a triple-boot system, starting with Devuan? » 2020-04-01 19:07:15
Thought I'd seen a reply, must have been deleted.
Consider how to partition the SSD for your 3 distros. Less is more. And if you want to have control you may use the manual partitioning. But you need to know or learn what you are doing.
rolfie
#1111 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-01 17:56:52
Sorry, you are running ASCII and want to install a big package from Beowulf backports, that is bound to cause trouble. Anyhow, in backports you won't find the libreoffice meta package.
Use https://pkginfo.devuan.org/ to search which package is where to find.
rolfie
PS: And it really looks like Beowulf-backports have vanished again. I have used it before, no more present.
#1112 Re: Installation » Issue with deb.devuan.org? » 2020-04-01 17:15:16
No issues, neither apt update, synaptics nor access to the websites via firefox-esr using http.
rolfie
#1113 Re: Installation » How do I make a triple-boot system, starting with Devuan? » 2020-03-31 18:30:22
There are several threads in this forum about encryption. And several approaches. Search and give it a read.
The 120G SSD isn't very big. We are talking about a non UEFI computer, don't we? Instead of MBR partitioning, read about GPT and the advantages. Maybe not required on that SSD, but I would call it an option, nowadays I prefer GPT whenever possible.
My approach for an encrypted setup: separate /boot unencrypted, separate /home drive encrypted, with the installer generate a volume for encryption, inside that a physical volume for LVM, split that into swap and root. Works great since I think Etch/Lenny, when I started to learn about Linux.
rolfie
#1114 Re: News & Announcements » Beowulf Beta is here! » 2020-03-29 18:43:15
Is Devuan 3 ready to update prod servers from 2.1? I have no heavy load servers, but I need a native php7.3 and a stable system without X, DE and other... actually, only LAMP (in ESXi).
Depends on what you expect. My private little fileserver (samba and nfs) runs on Beowulf since last summer, can't complain, rockstable.
rolfie
#1115 Re: Hardware & System Configuration » Devuan Ascii - Opensource Drivers Amd / AMD RX560 » 2020-03-27 19:03:34
Install 4.19 backports kernel and the non-free firmware from backports.
rolfie
#1116 Re: Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-23 10:11:47
A new installation with network mirror works fine.
That means grub-efi-amd64 is missing on the DVD.
rolfie
#1117 Re: Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-22 19:12:36
Did you install with or without a network mirror?
Without. I am used to set the sources.list to the mirrors after the first boot.
rolfie
#1118 Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-22 18:51:33
- rolfie
- Replies: 6
Installation into a Virtual Box VM with UEFI, encrypted with LVM, separate /boot-Partition. Expert install with openrc, let the installer partition the available space (32M). Goal was a minimal system with CLI for setting up my preffered desktop MATE without the garbage you get with the normal selection.
Host is a ASCII installation with VBox 6.0.14 directly installed with dpkg -i. Its not the latest version but it works for me.
The installation ended with no error message on installing grub, but the VM did not boot. Same scenario as https://dev1galaxy.org/viewtopic.php?id=2676. Used the DVD as rescue system and tried all options as posted in the mentioned thread. Finally suceeded with grub-install --bootloader-id=debian followed by an update-grub.
Found the log in /var/log/installer on the VM, here is the important part attached.
Scanning through there 2 topics struck my eyes:
1.) Mar 19 19:16:10 05efi: debug: /target/boot/efi does not have /EFI directory: exiting. I saw this when first running the rescue system, and fixed it manually. A normal grub-install did not help, still ended in the grub shell.
2.) Mar 19 19:15:29 in-target: Paket grub-efi-amd64 ist nicht verfügbar: the installer did not find grub-efi-amd64.
What went wrong there? My mistake or deficits in the installer?
Observation: the installer did not have a clear indication if started in EFI or MBR mode.
rolfie
Mar 19 19:15:27 main-menu[361]: INFO: Menu item 'grub-installer' selected
Mar 19 19:15:27 grub-installer: info: architecture: amd64/efi
Mar 19 19:15:27 in-target: Paketlisten werden gelesen...
Mar 19 19:15:27 in-target:
Mar 19 19:15:27 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:27 in-target:
Mar 19 19:15:27 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:27 in-target:
Mar 19 19:15:27 in-target: Die folgenden zusätzlichen Pakete werden installiert:
Mar 19 19:15:27 in-target: libefiboot1 libefivar1 libfuse2 os-prober
Mar 19 19:15:27 in-target: Vorgeschlagene Pakete:
Mar 19 19:15:27 in-target: multiboot-doc grub-emu xorriso desktop-base fuse
Mar 19 19:15:27 in-target: Die folgenden NEUEN Pakete werden installiert:
Mar 19 19:15:27 in-target: grub-common libefiboot1 libefivar1 libfuse2 os-prober
Mar 19 19:15:27 in-target: 0 aktualisiert, 5 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Mar 19 19:15:27 in-target: Es müssen noch 0 B von 2.722 kB an Archiven heruntergeladen werden.
Mar 19 19:15:27 in-target: Nach dieser Operation werden 17,3 MB Plattenplatz zusätzlich benutzt.
Mar 19 19:15:27 in-target: Holen:1 cdrom://[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200313] beowulf/main amd64 libefivar1 amd64 37-2 [46,3 kB]
Mar 19 19:15:27 in-target: Holen:2 cdrom://[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200313] beowulf/main amd64 libefiboot1 amd64 37-2 [41,9 kB]
Mar 19 19:15:27 in-target: Holen:3 cdrom://[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200313] beowulf/main amd64 libfuse2 amd64 2.9.9-1 [128 kB]
Mar 19 19:15:27 in-target: Holen:4 cdrom://[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200313] beowulf/main amd64 grub-common amd64 2.02+dfsg1-20 [2.476 kB]
Mar 19 19:15:27 in-target: Holen:5 cdrom://[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200313] beowulf/main amd64 os-prober amd64 1.77 [30,2 kB]
Mar 19 19:15:28 in-target: Vormals nicht ausgewähltes Paket libefivar1:amd64 wird gewählt.^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... ^M(Lese Datenbank ... 5%^M(Lese Datenbank ... 10%^M(Lese Datenbank ... 15%^M(Lese Datenbank ... 20%^M(Lese Datenbank ... 25%^M(Lese Datenbank ... 30%^M(Lese Datenbank ... 35%^M(Lese Datenbank ... 40%^M(Lese Datenbank ... 45%^M(Lese Datenbank ... 50%^M(Lese Datenbank ... 55%^M(Lese Datenbank ... 60%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 65%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 70%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 75%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 80%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 85%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 90%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 95%^M
Mar 19 19:15:28 in-target: (Lese Datenbank ... 100%^M(Lese Datenbank ... 50907 Dateien und Verzeichnisse sind derzeit installiert.)^M
Mar 19 19:15:28 in-target: Vorbereitung zum Entpacken von .../libefivar1_37-2_amd64.deb ...^M
Mar 19 19:15:28 in-target: Entpacken von libefivar1:amd64 (37-2) ...^M
Mar 19 19:15:28 in-target: Vormals nicht ausgewähltes Paket libefiboot1:amd64 wird gewählt.^M
Mar 19 19:15:28 in-target: Vorbereitung zum Entpacken von .../libefiboot1_37-2_amd64.deb ...^M
Mar 19 19:15:28 in-target: Entpacken von libefiboot1:amd64 (37-2) ...^M
Mar 19 19:15:28 in-target: Vormals nicht ausgewähltes Paket libfuse2:amd64 wird gewählt.^M
Mar 19 19:15:28 in-target: Vorbereitung zum Entpacken von .../libfuse2_2.9.9-1_amd64.deb ...^M
Mar 19 19:15:28 in-target: Entpacken von libfuse2:amd64 (2.9.9-1) ...^M
Mar 19 19:15:28 in-target: Vormals nicht ausgewähltes Paket grub-common wird gewählt.^M
Mar 19 19:15:28 in-target: Vorbereitung zum Entpacken von .../grub-common_2.02+dfsg1-20_amd64.deb ...^M
Mar 19 19:15:28 in-target: Entpacken von grub-common (2.02+dfsg1-20) ...^M
Mar 19 19:15:28 in-target: Vormals nicht ausgewähltes Paket os-prober wird gewählt.^M
Mar 19 19:15:28 in-target: Vorbereitung zum Entpacken von .../os-prober_1.77_amd64.deb ...^M
Mar 19 19:15:28 in-target: Entpacken von os-prober (1.77) ...^M
Mar 19 19:15:28 in-target: libfuse2:amd64 (2.9.9-1) wird eingerichtet ...^M
Mar 19 19:15:28 in-target: libefivar1:amd64 (37-2) wird eingerichtet ...^M
Mar 19 19:15:28 in-target: libefiboot1:amd64 (37-2) wird eingerichtet ...^M
Mar 19 19:15:28 in-target: grub-common (2.02+dfsg1-20) wird eingerichtet ...^M
Mar 19 19:15:28 in-target: os-prober (1.77) wird eingerichtet ...^M
Mar 19 19:15:28 in-target: Trigger für man-db (2.8.5-2) werden verarbeitet ...^M
Mar 19 19:15:28 in-target: Trigger für libc-bin (2.28-10) werden verarbeitet ...^M
Mar 19 19:15:29 in-target: Paketlisten werden gelesen...
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: grub-common ist schon die neueste Version (2.02+dfsg1-20).
Mar 19 19:15:29 in-target: 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Mar 19 19:15:29 grub-installer: info: Identified partition label for /dev/sda2: gpt
Mar 19 19:15:29 grub-installer: dpkg: warning: ignoring request to remove grub which isn't installed
Mar 19 19:15:29 grub-installer: dpkg: warning: ignoring request to remove grub-legacy which isn't installed
Mar 19 19:15:29 grub-installer: dpkg: warning: ignoring request to remove grub-pc-bin which isn't installed
Mar 19 19:15:29 grub-installer: dpkg: warning: ignoring request to remove grub-pc which isn't installed
Mar 19 19:15:29 in-target: Paketlisten werden gelesen...
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: Paket grub-efi-amd64 ist nicht verfügbar, wird aber von einem anderen Paket
Mar 19 19:15:29 in-target: referenziert. Das kann heißen, dass das Paket fehlt, dass es abgelöst
Mar 19 19:15:29 in-target: wurde oder nur aus einer anderen Quelle verfügbar ist.
Mar 19 19:15:29 in-target: Doch die folgenden Pakete ersetzen es:
Mar 19 19:15:29 in-target: grub2-common grub-common grub-pc grub-efi-ia32
Mar 19 19:15:29 in-target:
Mar 19 19:15:29 in-target: E: Für Paket »grub-efi-amd64« existiert kein Installationskandidat.
Mar 19 19:15:29 grub-installer: info: Additionally installing shim-signed to go with grub-efi-amd64
Mar 19 19:15:30 in-target: Paketlisten werden gelesen...
Mar 19 19:15:30 in-target:
Mar 19 19:15:30 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:30 in-target:
Mar 19 19:15:30 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:30 in-target:
Mar 19 19:15:30 in-target: E: Paket shim-signed kann nicht gefunden werden.
Mar 19 19:15:30 grub-installer: info: Calling 'apt-install grub-efi-amd64' failed
Mar 19 19:15:36 main-menu[361]: (process:2805): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:36 main-menu[361]: (process:2805): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:36 main-menu[361]: (process:2805): File descriptor 3 (pipe:[13960]) leaked on lvdisplay invocation.
Mar 19 19:15:36 main-menu[361]: (process:2805): Parent PID 3335: /bin/sh
Mar 19 19:15:36 main-menu[361]: (process:2805): File descriptor 4 (/dev/pts/0) leaked on lvdisplay invocation.
Mar 19 19:15:36 main-menu[361]: (process:2805): Parent PID 3335: /bin/sh
Mar 19 19:15:36 main-menu[361]: (process:2805): File descriptor 5 (/dev/pts/0) leaked on lvdisplay invocation.
Mar 19 19:15:36 main-menu[361]: (process:2805): Parent PID 3335: /bin/sh
Mar 19 19:15:36 main-menu[361]: (process:2805): File descriptor 6 (/dev/pts/0) leaked on lvdisplay invocation.
Mar 19 19:15:36 main-menu[361]: (process:2805): Parent PID 3335: /bin/sh
Mar 19 19:15:36 main-menu[361]: (process:2805):
Mar 19 19:15:36 main-menu[361]: (process:2805): Volume group "sda" not found
Mar 19 19:15:36 main-menu[361]: (process:2805):
Mar 19 19:15:36 main-menu[361]: (process:2805):
Mar 19 19:15:36 main-menu[361]: (process:2805): Cannot process volume group sda
Mar 19 19:15:36 main-menu[361]: (process:2805):
Mar 19 19:15:36 main-menu[361]: (process:2805): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:36 main-menu[361]: (process:2805): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:36 main-menu[361]: WARNING **: Configuring 'grub-installer' failed with error code 1
Mar 19 19:15:36 main-menu[361]: WARNING **: Menu item 'grub-installer' failed.
Mar 19 19:15:38 main-menu[361]: DEBUG: resolver (gpgv-udeb): package doesn't exist (ignored)
Mar 19 19:15:38 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:15:38 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:15:38 lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
Mar 19 19:15:42 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:15:42 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:15:42 main-menu[361]: INFO: Menu item 'grub-installer' selected
Mar 19 19:15:42 grub-installer: info: architecture: amd64/efi
Mar 19 19:15:43 in-target: Paketlisten werden gelesen...
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: grub-common ist schon die neueste Version (2.02+dfsg1-20).
Mar 19 19:15:43 in-target: 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Mar 19 19:15:43 in-target: Paketlisten werden gelesen...
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: grub-common ist schon die neueste Version (2.02+dfsg1-20).
Mar 19 19:15:43 in-target: 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Mar 19 19:15:43 grub-installer: info: Identified partition label for /dev/sda2: gpt
Mar 19 19:15:43 grub-installer: dpkg: warning: ignoring request to remove grub which isn't installed
Mar 19 19:15:43 grub-installer: dpkg: warning: ignoring request to remove grub-legacy which isn't installed
Mar 19 19:15:43 grub-installer: dpkg: warning: ignoring request to remove grub-pc-bin which isn't installed
Mar 19 19:15:43 grub-installer: dpkg: warning: ignoring request to remove grub-pc which isn't installed
Mar 19 19:15:43 in-target: Paketlisten werden gelesen...
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:43 in-target:
Mar 19 19:15:43 in-target: Paket grub-efi-amd64 ist nicht verfügbar, wird aber von einem anderen Paket
Mar 19 19:15:43 in-target: referenziert. Das kann heißen, dass das Paket fehlt, dass es abgelöst
Mar 19 19:15:43 in-target: wurde oder nur aus einer anderen Quelle verfügbar ist.
Mar 19 19:15:43 in-target: Doch die folgenden Pakete ersetzen es:
Mar 19 19:15:43 in-target: grub2-common grub-common grub-pc grub-efi-ia32
Mar 19 19:15:43 in-target:
Mar 19 19:15:44 in-target: E: Für Paket »grub-efi-amd64« existiert kein Installationskandidat.
Mar 19 19:15:44 grub-installer: info: Additionally installing shim-signed to go with grub-efi-amd64
Mar 19 19:15:44 in-target: Paketlisten werden gelesen...
Mar 19 19:15:44 in-target:
Mar 19 19:15:44 in-target: Abhängigkeitsbaum wird aufgebaut....
Mar 19 19:15:44 in-target:
Mar 19 19:15:44 in-target: Statusinformationen werden eingelesen....
Mar 19 19:15:44 in-target:
Mar 19 19:15:44 in-target: E: Paket shim-signed kann nicht gefunden werden.
Mar 19 19:15:44 grub-installer: info: Calling 'apt-install grub-efi-amd64' failed
Mar 19 19:15:51 main-menu[361]: (process:3571): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:51 main-menu[361]: (process:3571): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:51 main-menu[361]: (process:3571): File descriptor 3 (pipe:[13960]) leaked on lvdisplay invocation.
Mar 19 19:15:51 main-menu[361]: (process:3571): Parent PID 3795: /bin/sh
Mar 19 19:15:51 main-menu[361]: (process:3571): File descriptor 4 (/dev/pts/0) leaked on lvdisplay invocation. Parent PID 3795: /bin/sh
Mar 19 19:15:51 main-menu[361]: (process:3571): File descriptor 5 (/dev/pts/0) leaked on lvdisplay invocation. Parent PID 3795: /bin/sh
Mar 19 19:15:51 main-menu[361]: (process:3571): File descriptor 6 (/dev/pts/0) leaked on lvdisplay invocation. Parent PID 3795: /bin/sh
Mar 19 19:15:51 main-menu[361]: (process:3571):
Mar 19 19:15:51 main-menu[361]: (process:3571): Volume group "sda" not found
Mar 19 19:15:51 main-menu[361]: (process:3571):
Mar 19 19:15:51 main-menu[361]: (process:3571):
Mar 19 19:15:51 main-menu[361]: (process:3571): Cannot process volume group sda
Mar 19 19:15:51 main-menu[361]: (process:3571):
Mar 19 19:15:51 main-menu[361]: (process:3571): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:51 main-menu[361]: (process:3571): dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Mar 19 19:15:51 main-menu[361]: WARNING **: Configuring 'grub-installer' failed with error code 1
Mar 19 19:15:51 main-menu[361]: WARNING **: Menu item 'grub-installer' failed.
Mar 19 19:15:53 main-menu[361]: DEBUG: resolver (gpgv-udeb): package doesn't exist (ignored)
Mar 19 19:15:53 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:15:53 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:15:53 lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
Mar 19 19:15:55 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:15:55 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:15:55 main-menu[361]: INFO: Menu item 'nobootloader' selected
Mar 19 19:16:07 main-menu[361]: DEBUG: resolver (gpgv-udeb): package doesn't exist (ignored)
Mar 19 19:16:07 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:16:07 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:16:07 lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
Mar 19 19:16:07 lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi
Mar 19 19:16:09 main-menu[361]: INFO: Falling back to the package description for brltty-udeb
Mar 19 19:16:09 main-menu[361]: INFO: Falling back to the package description for choose-init
Mar 19 19:16:09 main-menu[361]: INFO: Menu item 'finish-install' selected
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/01kickseed
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/05localechooser
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/06espeakup
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/06rootskel
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/06user-setup
Mar 19 19:16:09 user-setup: Shadow passwords are now on.
Mar 19 20:16:09 chpasswd[4143]: pam_unix(chpasswd:chauthtok): password changed for root
Mar 19 19:16:09 user-setup: Adding user `rolf' ...
Mar 19 19:16:09 user-setup: Adding new group `rolf' (1000) ...
Mar 19 20:16:09 groupadd[4150]: group added to /etc/group: name=rolf, GID=1000
Mar 19 20:16:09 groupadd[4150]: group added to /etc/gshadow: name=rolf
Mar 19 20:16:09 groupadd[4150]: new group: name=rolf, GID=1000
Mar 19 19:16:09 user-setup: Adding new user `rolf' (1000) with group `rolf' ...
Mar 19 20:16:09 useradd[4154]: new user: name=rolf, UID=1000, GID=1000, home=/home/rolf, shell=/bin/bash
Mar 19 19:16:09 user-setup: Creating home directory `/home/rolf' ...
Mar 19 19:16:09 user-setup: Copying files from `/etc/skel' ...
Mar 19 20:16:09 usermod[4162]: change user 'rolf' password
Mar 19 20:16:09 chfn[4167]: changed user 'rolf' information
Mar 19 20:16:09 chpasswd[4174]: pam_unix(chpasswd:chauthtok): password changed for rolf
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `audio' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group audio
Mar 19 20:16:09 gpasswd[4178]: user rolf added by root to group audio
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `cdrom' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group cdrom
Mar 19 20:16:09 gpasswd[4184]: user rolf added by root to group cdrom
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `dip' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group dip
Mar 19 20:16:09 gpasswd[4190]: user rolf added by root to group dip
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `floppy' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group floppy
Mar 19 20:16:09 gpasswd[4196]: user rolf added by root to group floppy
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `video' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group video
Mar 19 20:16:09 gpasswd[4202]: user rolf added by root to group video
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `plugdev' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group plugdev
Mar 19 20:16:09 gpasswd[4208]: user rolf added by root to group plugdev
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: Adding user `rolf' to group `netdev' ...
Mar 19 19:16:09 user-setup: Adding user rolf to group netdev
Mar 19 20:16:09 gpasswd[4214]: user rolf added by root to group netdev
Mar 19 19:16:09 user-setup: Done.
Mar 19 19:16:09 user-setup: adduser: The group `scanner' does not exist.
Mar 19 19:16:09 user-setup: adduser: The group `bluetooth' does not exist.
Mar 19 19:16:09 user-setup: adduser: The group `debian-tor' does not exist.
Mar 19 19:16:09 user-setup: adduser: The group `lpadmin' does not exist.
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/07brltty
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/07preseed
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/07speakup
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/10apt-cdrom-setup
Mar 19 19:16:09 finish-install: info: Running /usr/lib/finish-install.d/10clock-setup
Mar 19 19:16:09 anna-install: Installing os-prober-udeb
Mar 19 19:16:09 anna-install: Installing ext2-modules
Mar 19 19:16:10 anna-install: Installing ext3-modules
Mar 19 19:16:10 anna-install: Installing ext4-modules
Mar 19 19:16:10 anna-install: Installing xfs-modules
Mar 19 19:16:10 anna-install: Installing jfs-modules
Mar 19 19:16:10 anna-install: Installing msdos-modules
Mar 19 19:16:10 os-prober: unknown udeb msdos-modules
Mar 19 19:16:10 anna-install: Installing vfat-modules
Mar 19 19:16:10 os-prober: unknown udeb vfat-modules
Mar 19 19:16:10 anna-install: Installing ntfs-modules
Mar 19 19:16:10 os-prober: unknown udeb ntfs-modules
Mar 19 19:16:10 anna-install: Installing minix-modules
Mar 19 19:16:10 os-prober: unknown udeb minix-modules
Mar 19 19:16:10 anna-install: Installing hfs-modules
Mar 19 19:16:10 os-prober: unknown udeb hfs-modules
Mar 19 19:16:10 anna-install: Installing hfsplus-modules
Mar 19 19:16:10 os-prober: unknown udeb hfsplus-modules
Mar 19 19:16:10 anna-install: Installing qnx4-modules
Mar 19 19:16:10 os-prober: unknown udeb qnx4-modules
Mar 19 19:16:10 anna-install: Installing ufs-modules
Mar 19 19:16:10 os-prober: unknown udeb ufs-modules
Mar 19 19:16:10 anna-install: Installing btrfs-modules
Mar 19 19:16:10 anna-install: Installing fuse-modules
Mar 19 19:16:10 anna-install: Installing fs-core-modules
Mar 19 19:16:10 os-prober: unknown udeb fs-core-modules
Mar 19 19:16:10 anna-install: Installing fs-secondary-modules
Mar 19 19:16:10 os-prober: unknown udeb fs-secondary-modules
Mar 19 19:16:10 os-prober: File descriptor 3 (pipe:[13960]) leaked on lvs invocation. Parent PID 4453: log-output
Mar 19 19:16:10 os-prober: File descriptor 4 (/dev/pts/0) leaked on lvs invocation. Parent PID 4453: log-output
Mar 19 19:16:10 os-prober: File descriptor 5 (/dev/pts/0) leaked on lvs invocation. Parent PID 4453: log-output
Mar 19 19:16:10 os-prober: File descriptor 6 (/dev/pts/0) leaked on lvs invocation. Parent PID 4453: log-output
Mar 19 19:16:10 os-prober: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sda1
Mar 19 19:16:10 05efi: debug: /dev/sda1 is a FAT32 partition
Mar 19 19:16:10 05efi: debug: /dev/sda1 partition scheme is gpt
Mar 19 19:16:10 05efi: debug: /dev/sda1 partition type is c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Mar 19 19:16:10 05efi: debug: /target/boot/efi does not have /EFI directory: exiting#1119 Re: Documentation » Append date and time to .bash_history at start of session » 2020-03-22 16:33:10
I am always willing to learn, you got a point there. update-alternatives allows to switch to the mate-terminal-wrapper, I will change my default mode to that proposal. This also fixes the problems with the text in the bash_history.
Thanks, rolfie
#1120 Re: Documentation » Append date and time to .bash_history at start of session » 2020-03-22 15:29:05
Putting it in ~/.bash_profile didn't work for me. I suppose I have to log out of my desktop session and restart it. Putting it in ~/.bashrc works every time I open a new terminal on the desktop. If I put it in /root/.bashrc, it works every time I do 'su' or 'su -' in a terminal.
Entering:
. ~/.profile
echo "##
##Session begin $(date)
##" >> ~/.bash_historyinto /root/.bashrc causes a memory access error (Speicherzugriffsfehler in German), no matter if I use Mate with pkexec, su - or xterm. Whats wrong here? Guess I have to use the rescue mode again.
It does not matter if the separator is inserted every time I use the root terminal, I like the idea to have a better feeling for when I did something administering my installations.
BTW: the machine in question is Beowulf Beta from DVD in a VBox with UEFI encrypted with LVM. Rebooting the VM didn't make a difference.
rolfie
Edit: could fix it via opening the root folder under the Mate file manager with administrative privileges and using geany to remove the modifications from the .bashrc file.
#1121 Re: Documentation » Append date and time to .bash_history at start of session » 2020-03-22 15:21:34
Don't use pkexec to start a root terminal, that's a silly idea. Why do the MATE devs do that?
Please can you explain why this is a silly idea?
And its not a MATE devs idea. I put something together about a year ago, related to dropping gksu: https://dev1galaxy.org/viewtopic.php?id=2717
Use this to start a root terminal:
x-terminal-emulator -e su -
That line works fine as additional entry in the menu.
But: I don't like xterm. The font is ugly and much too small for my eyes, and the window is too small. Mate terminal gives me exactly what I want and need, and offers to increase the window to a width of 132 characters.
There should be a way to achieve this.
rolfie
#1122 Re: Documentation » Append date and time to .bash_history at start of session » 2020-03-22 12:46:45
Tried that and created the .bash_profile in the /root folder of a Beowulf installation in a VM based on the Beta DVD, does not work. I use Mate, the root terminal is started by pkexec mate-terminal.
What can be wrong? Rights?
rolfie
PS: seems to work when I start the Mate terminal as user and switch to root with su -. How can I make this work via pkexec?
#1123 Re: Installation » VMware install Devuan ascii » 2020-03-19 14:59:18
Kernel 4.9.0-11 isn#t the latest kernel, that is -12. The following headers are in the repos:
[ascii-backports] linux-headers-4.9.0-4-common-grsec-4.9.65-2+grsecunoff1~bpo9+1
[ascii-backports] linux-headers-4.9.0-4-grsec-amd64-4.9.65-2+grsecunoff1~bpo9+1
[ascii] linux-headers-4.9.0-12-all-4.9.210-1
[ascii] linux-headers-4.9.0-12-all-amd64-4.9.210-1
[ascii] linux-headers-4.9.0-12-amd64-4.9.210-1
[ascii] linux-headers-4.9.0-12-common-4.9.210-1
[ascii] linux-headers-4.9.0-12-common-rt-4.9.210-1
[ascii] linux-headers-4.9.0-12-rt-amd64-4.9.210-1
[ascii-security] linux-headers-4.9.0-11-all-4.9.189-3+deb9u2
[ascii-security] linux-headers-4.9.0-11-all-amd64-4.9.189-3+deb9u2
[ascii-security] linux-headers-4.9.0-11-amd64-4.9.189-3+deb9u2
[ascii-security] linux-headers-4.9.0-11-common-4.9.189-3+deb9u2
[ascii-security] linux-headers-4.9.0-11-common-rt-4.9.189-3+deb9u2
[ascii-security] linux-headers-4.9.0-11-rt-amd64-4.9.189-3+deb9u2rolfie
#1124 Re: Hardware & System Configuration » New kernel not stable (4.9.0-12) » 2020-03-19 07:05:08
Have you got the intel-microcode installed? Take the one from backports, thats newer. If that does not help try kernel 4.19 from backports.
rolfie
#1125 Re: Other Issues » Problems upgrading elogind libelogind0 libpam-elogind » 2020-03-18 18:15:47
As the title say, i'm having problems with this update, im installing devuan from the usb version of ascii, it is only the graphical installer, then i perform the upgrade to beowulf by changing the sources.list, everything goes fine except that i have to manually install the firmware-amd-graphics, but that's it.
That is normal, that firmware is non-free.
i'm a regular everyday user, not a power one, i only use this machine to play in steam, watch videos and movies and some graphics edition, so i've done the usual sudo apt update/upgrade and the only packages showed to need are those mentioned in the title, but after the upgrade when i boot my machine i have no GUI i boot directly into the tty i can startx but have no full performance, tried reinstall elogind and company the xorg server the amd firmware but nothing works i have to avoid completely the upgrade of those programs in order to use my pc which have the amd ryzen 3 2200g apu.
I can't stay with ascii 'cause of my apu need the more recent possible software drivers, and beowulf works pretty nice except for this weird problem.
Please can you tell as a bit more about your boundary conditions like UEFI yes/no, mbr/gpt, DE etc. including the exact error message? Maybe you need some additional settings.... I myself got an ASCII running fine on a Ryzen 7 2700X, while my fileserver is on Beowulf already. Had no issue with elogind. Maybe its worth when you search the forum for threads about elogind, there is something available to read.
I also tried to install minimal to avoid all bloatware in cinnamon but i get stuck at making alsa work
Regarding alsa, refer to https://dev1galaxy.org/viewtopic.php?pid=20555#p20555
Good luck, rolfie
Board footer
