Posts by rolfie

rolfie · Hardware & System Configuration

Install Beowulf and use kernel 5.4 from Beowulf backports.

rolfie

rolfie · Installation

I guess I looked at the wrong file in the efi directory which belongs to Arch.

Arch is booting fine when I change the boot order to 0.

Also created a new Devuan entry based on doing the opposite to https://dev1galaxy.org/viewtopic.php?id=3280.

Looks like the entries in the efi are duplicated, when using efibootmgr V17 on Arch, suddenly empty entries 2,3,4,5,6 were displayed. Tried to de-activate them under Arch, no help, under efibootmgr V15 (Beowulf) they are back again. Now I am getting more complaints before the blue grub screen comes up. Maybe update-grub under Beowulf ins't doing what its supposed to do?

rolfie

rolfie · Installation

Strange, I did several experiments trying to affect the problems, still the same. Looked into a VM with Beowulf upgraded from ASCII, encrypted with LVM to compare.

Removed the shim entry from the efi, deleted all shim files by uninstalling via Synaptic, ... always used update-grub next and rebooted, still the same. Then I looked at /boot/grub/grub.cfg. That file still is dated April 18th. Shouldn't that file be changed by update-grub?

The VM installation runs 5.4-bpo2 kernel, grub.cfg had a date of end of Feb this year. Did a update-grub, the file now has today timestamp. ?????

Arch was installed with --bootloader-id=GRUB according to the German Arch Beginners Tutorial. Do I have some interference between these two installations?

rolfie

rolfie · Installation

golinux wrote:

Is desktop-base installed? That should pull in all parts of the cinnabar theme. Sorry, can't help with grub issues. Hope you get it straightened out.

It is. There is a Cinnabar theme present, but not used by grub. Lightdm/Mate use Cinnabar.

rolfie

rolfie · Installation

xinomilo wrote:

after modifying disk with gparted to prepare 2nd install, the disk uuid probably got modified. check from working system here : /dev/disk/by-uuid, if it's not the same, chroot to troubling installation, modify grub and run update-grub.. then try booting again.
note, i dont use UEFI. and grub loads luks partition from eg. 'root=/dev/mapper/system--vg-root'

Tried update-grub, made no difference. When I compare the output from blkid and what is listed in /dev/disk/by-uuid I see no difference. What else can I check?

I also had a look at grub.cfg. In this file this uuid is listed twice in the header part:

set root='lvmid/xS2VOe-2irS-1ZJQ-fWAz-FBAn-BYSx-sAs2sG/hfqu6W-qJ0f-iYDd-2Su6-ZgOg-0PXN-deZDHi'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='lvmid/xS2VOe-2irS-1ZJQ-fWAz-FBAn-BYSx-sAs2sG/hfqu6W-qJ0f-iYDd-2Su6-ZgOg-0PXN-$
else
  search --no-floppy --fs-uuid --set=root 76c68ea3-5785-49b4-b93e-66f4de5b3a2b
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
insmod lvm
insmod ext2
set root='lvmid/xS2VOe-2irS-1ZJQ-fWAz-FBAn-BYSx-sAs2sG/hfqu6W-qJ0f-iYDd-2Su6-ZgOg-0PXN-deZDHi'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='lvmid/xS2VOe-2irS-1ZJQ-fWAz-FBAn-BYSx-sAs2sG/hfqu6W-qJ0f-iYDd-2Su6-ZgOg-0PXN-$
else
  search --no-floppy --fs-uuid --set=root 76c68ea3-5785-49b4-b93e-66f4de5b3a2b
fi

and here is the main entry that also references this uuid (cut off here due to nano):

menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-76c6$
        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_gpt
        insmod ext2
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root  97e1104c-2123-44da-9e09-97a02728d093
        else
          search --no-floppy --fs-uuid --set=root 97e1104c-2123-44da-9e09-97a02728d093
        fi
        echo    'Linux 5.4.0-0.bpo.4-amd64 wird geladen …'
        linux   /vmlinuz-5.4.0-0.bpo.4-amd64 root=/dev/mapper/vgBsys-1_root ro  quiet
        echo    'Initiale Ramdisk wird geladen …'
        initrd  /initrd.img-5.4.0-0.bpo.4-amd64
}

Another observation is that the grub color is the Debian blue, cinnebar does not seem to be used. Further ideas?

Thanks, rolfie

rolfie · Installation

Head_on_a_Stick wrote:

rolfie wrote:
Ryzen 3700x
You will need the backported kernel for that, 3rd generation Ryzen is poorly supported by kernel 4.19.

Mainboard and Ryzen 7 3700X CPU work fine with 4.19 kernel (except the other glitches). I have not seen any crashes, kernel panic whatsoever. Lightdm/Mate is coming up fine, LO/Firefox ... work flawlessly. The 5.4 kernel is preparation for installing my new Radeon RX 5500XT grahics card which isn't yet installed.

Head_on_a_Stick wrote:

What is your graphics hardware? The Devuan firmware-amd-graphics packages don't have the Navi firmware yet.

For the time being I installed an older passive Radeon card that was available in my cellar.

# lspci | grep VGA
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

The mainboard wanted CSM enabled with this card, it complained that this card wasn't efi compatible which it is afaik. It was used in an older PC with an efi installation.

Head_on_a_Stick wrote:

rolfie wrote:
First installation attempt failed with grub not installing.
Did you check TTY4 or the installer log for the actual error message? It would be nice to know why it failed.

Can't recall the exact text, just saw on the 2nd console that there was no efi partition present in /target/boot. I tried to mount it and to repeat the grub-install, failed. Well, I searched all my threads in this forum and stumbled somewhere across the bit with the network connection. On the second install I paid explicit attention to if the manual partitioning shows any way to mount the efi partition to /boot, there was none. And against my usual habit I made sure the network was setup for using an external mirror. I checked /target/boot just before the grub-install (again on second console), this time the efi partition was mounted.

Head_on_a_Stick wrote:

rolfie wrote:
I did manually modify the boot number from 1 to 8. No change.
The only difference between those two entries is Secure Boot support, which is provided by shimx64.efi.

Secure boot is disabled (Other OS), and I did delete all key from the database. I always do this.

Head_on_a_Stick wrote:

rolfie wrote:
Why is Arch overwritten?
Because your UEFI firmware is a useless, buggy pile of crap. Most are. I can show you how to generate a new NVRAM entry for Arch but your motherboard would probably just forget it again.
rolfie wrote:
I though that two Linux OS could reside on the same drive with one efi partition without conflict.
There is no conflict, as such, the Arch entry has just been lost.
EDIT: actually I think the Arch entry might be Boot0000. What was the exact grub-install command you ran when installing Arch? /EDIT

I used

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB --removable

so Boot0000 should be the Arch entry, but with F8 I do not get this as a choice. I haven't yet tried to use efibootmgr to change the boot order. Will be a separate experiment.

rolfie

rolfie · Installation

Head_on_a_Stick wrote:

rolfie wrote:
after upgrading to kernel 5.4-bpo.4 kernel panic, due to EFI_MEMMAP is not enabled.
As I mentioned earlier you will need that kernel version.
Have you tried the add_efi_memmap kernel parameter?

Oh man, found the issue. Its not the parameter, adding that to grub did not work. When I tried to downgrade to the bpo.3 kernel and recalled the command from the bash_history to simply replace 4 by 3, I saw this:

# apt install linux-image-5.4.0-0.bpo.4-686 linux-headers-5.4.0-0.bpo.4-686

Don't know how that happened, copy/paste error from apt list output or if it was too late yesterday... It works fine with -amd64.

Other stuff later...

rolfie

rolfie · Installation

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........BO

I 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.

rolfie · Hardware & System Configuration

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

rolfie · Other Issues

According to this page https://devuan.org/os/ you should use:

deb http://auto.mirror.devuan.org/merged jessie          main

Give it a try.

rolfie

rolfie · News & Announcements

kapqa wrote:

Still getting error
E: The value 'beowulf-backports' is invalid for APT::Default-Release as such a release is not available in the sources
Maybe 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

rolfie · News & Announcements

Look at this old thread: https://dev1galaxy.org/viewtopic.php?id=2023

rolfie

rolfie · News & Announcements

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+deb10u2

Whats wrong there?

rolfie

rolfie · Other Issues

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

rolfie · Other Issues

/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

rolfie · Other Issues

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

rolfie · Installation

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

rolfie · Other Issues

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.

rolfie · Installation

No issues, neither apt update, synaptics nor access to the websites via firefox-esr using http.

rolfie

rolfie · Installation

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

rolfie · News & Announcements

IdeaFix wrote:

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

rolfie · Hardware & System Configuration

Install 4.19 backports kernel and the non-free firmware from backports.

rolfie

rolfie · Installation

A new installation with network mirror works fine.

That means grub-efi-amd64 is missing on the DVD.

rolfie

rolfie · Installation

fsmithred wrote:

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

rolfie · Installation

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

The officially official Devuan Forum!

#1026 Re: Hardware & System Configuration » tuxedo notebook intel wi-fi 6 AX200 (kernel 5.1 requiered?) » 2020-04-26 12:16:22

#1027 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-25 20:37:42

#1028 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-25 19:39:02

#1029 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-25 19:29:23

#1030 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-24 18:55:32

#1031 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-24 17:41:05

#1032 Re: Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-24 16:49:06

#1033 Installation » [Closed] Problems with Beowulf as second OS on a SSD » 2020-04-23 19:31:23

#1034 Re: Hardware & System Configuration » Old Brother Scanners broken in Beowulf (problem descr. and workaround) » 2020-04-18 11:33:55

#1035 Re: Other Issues » What would cause wget to work and apt to get "Connection failed"? » 2020-04-17 19:49:34

#1036 Re: News & Announcements » Beowulf Beta is here! » 2020-04-08 08:09:31

#1037 Re: News & Announcements » Beowulf Beta is here! » 2020-04-07 16:56:15

#1038 Re: News & Announcements » Beowulf Beta is here! » 2020-04-06 18:51:32

#1039 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-04 11:43:04

#1040 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-04 07:58:37

#1041 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-03 08:28:28

#1042 Re: Installation » How do I make a triple-boot system, starting with Devuan? » 2020-04-01 19:07:15

#1043 Re: Other Issues » LibreOffice 6.1.5 or 6.4.2 to ASCII from Beowulf or Ceres repos? » 2020-04-01 17:56:52

#1044 Re: Installation » Issue with deb.devuan.org? » 2020-04-01 17:15:16

#1045 Re: Installation » How do I make a triple-boot system, starting with Devuan? » 2020-03-31 18:30:22

#1046 Re: News & Announcements » Beowulf Beta is here! » 2020-03-29 18:43:15

#1047 Re: Hardware & System Configuration » Devuan Ascii - Opensource Drivers Amd / AMD RX560 » 2020-03-27 19:03:34

#1048 Re: Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-23 10:11:47

#1049 Re: Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-22 19:12:36

#1050 Installation » Experiences with Beowulf Beta Desktop Iso » 2020-03-22 18:51:33

Board footer