You are not logged in.
I have:
# apt list lsb*
Auflistung... Fertig
lsb-base/stable,stable,now 10.2019051400 all [installiert]
lsb-release/stable,stable,now 10.2019051400 all [Installiert,automatisch]
rolfie
The button is called "Edit".
rolfie
Got the 3.1.0 with openrc to work, Cinnamon as desktop, efi mode, /boot unencrypted, encrypted LVM for root and swap, separate home.
Despite having a mirror set up, the CDROM still was present in the sources.list. Easy to fix.
The installation booted grub with shimx64.efi. I removed it afterwards.
Locale was fine with this setup.
Would say that runit is experimental in the current status.
rolfie
Update to todays status
Got the Beowulf 3.0.0 based Chimaera installation on P(artition)4/P5 on the new NMVe working fine with openrc as init and Cinnamon as desktop. I created a devuan4 entry in the efi flash which is used to start this installation.
Went on trying to revive the Beowulf 3.1.0 based installation on P2/P3 of the NVMe. There I am stuck.
I did a new install overwriting the last one. Used runit as init system, the rest being as before, i.e. efi expert install to cli, encrypted LVM with unencrypted boot. First thing that stuck my eye: the installation did not get stuck on the grub prompt but booted fine, the grub splash was shown immediately, I could enter the encryption key and log in as root.
The CD was still enabled in the sources.list, locale at C.UTF-8. Fixed the sources.list as first action. In the efi I found a debian entry holding a grub.cfg, and a devuan entry holding all the usual files including the shimx64.efi. Removed grub-efi-amd64-signed and did a new grub-install --bootloader-id=devuan3 --no-uefi-secure-boot. A new entry devuan3 was generated and points to grubx64.efi as expected. Removed the debian and devuan entries on the file system and cleaned the efi flash with the efibootmgr -b 000x -B.
The modifed setup boots up to the command prompt. Against my expectation, I still have the locale issue, and the efivarfs is not mounted. efibootmgr tells me that this system does not support efi variables. Well, mounted the efivarfs to the usual directory and can read the variables now. efibootmgr points to the correct entry, devuan3 still is present.
Is it possible that runit does forget to mount efivarfs?
rolfie
Update on the Beowulf 3.0.0 install on P4/P5:Same issues basically, the boot also ends in the grub-console, no grub menu shown.
Started the rescue mode and fixed issue #1. Looked at the locale, also is at C.UTF-8. Then fidelled a bit with boot, grub-install and update-grub, grub.cfg, efivars and the efibootmgr. Finally used efibootmgr -v and saw that all Devuan entries in the efi memeory were referring to shimx64.efi, despite my disabling Secure Boot.
Well, searched the man pages for grub-install and found the option --no-uefi-secure-boot.
A grub-install --no-uefi-secure-boot --bootloader-id=devuan4 brought a grubx64.efi into play. A reboot showed the usual blue grub splash screen, I am now working on P4/P5 and the Chimaera upgrade. The locale issue is gone too.
Next step is trying the same on the 3.1.0 install.
What I am wondering about: how did I get into this situation in the first place?
rolfie
Have installed a fresh nvme on my older workstation with X470 chipset, Ryzen7 2700X, AMD 570 graphics card. Now I try to bring up the PC with Beowulf and Chimaera in parallel installations, but I face several issues I did not see with 3.0.0 installs. HW set to Fast Boot disabled, CSM on, UEFI driver first, Secure Boot off. The old ASCII/Beowulf installs did work with that setup.
Downloaded the Desktop DVD image, copied this to a new USB stick with rufus (same procedure as used with 3.0.0). Stick booted in EFI mode, Expert install, German language and Keyboard, manual paritioning (P1=EFI, P2=/boot, P3=encrypted LVM), enable contrib/nonfree and backports, disable sources, use a mirror from Germany, ..... just go for a CLI install, no graphical desktop yet.
1.) Minor issue: The sources.list still contains one uncommented line referring to the CD-ROM.
2.) locale is set to LANG=C.UTF-8, LANGUAGE=de. dpkg-reconfigure locales in rescue mode does not change anything. I just have de-DE.UTF-8 selected, no errors produced, locale does not change??
3.) Managed to break the locale on the first install when trying to fix this. Couldn't enter my special characters composed with ALTGR any more. Did a second installation with same parameters, overwriting the first install. Now I end up in the grub console. Even after a rescue session and re-installing grub. Häääh?
Next thing I will try is doing an install from my old 3.0.0 medium generated last summer on P4=/boot for Chimaera and P5 for encrypted LVM for Chimaera.
Any feedback is welcome.
rolfie
It may not be that simple. All depends on if the meta package linux-image-amd64 is installed, and if this is linked to the main repository or to backports.
If you choose linux-image-amd64 during installation and not one of the presented dedicated kernel images, apt update && apt upgrade will check for updates and install them when available. For Beowulf this is the 4.19 kernels.
When you only install one dedicated kernel from backports, that will stay forever and not be affected by apt update && apt upgrade. Unless you install the meta-package from backports. Then the stock kernel is left alone and backports is updated.
You can't have both.
rolfie
You may give the latest BIOS a try, good luck with that, I hope it helps. In my case it did not do anything.
When I look at what you posted, the dump-type stuff does not belong there. That may be some data written by the linux kernel into EFI flash.
Good luck, rolfie
Read this thread: https://dev1galaxy.org/viewtopic.php?id=3616
My suspicion: on a crash the kernel overwrites contents of the efi flash. Got an older socket AMD3+ board that had a similar issue (https://dev1galaxy.org/viewtopic.php?id=2820).
Now all my installations have /sys/firmware/efi/efivars/ set to ro in fstab.
I had the ASUS Prime X470-Pro sent back to service. They flashed a new bios and fixed the efi memory, something I could not achieve with the means available to a normal user. Now the board works normal again.
rolfie
CD1 is called devuan_beowulf_3.1.0_amd64-server.iso
Beginning of February I downloaded a current Bullseye netinstall image and installed it in VBox. Can't remember that I got an init choice like in Devuan.
rolfie
Started off with sysvinit under ASCII some years ago, then experimented with openrc in VBox and finally installed an AMD470/Ryzen 2700X with openrc / ASCII. Motivation: refer to HOAS comment in the previous post.
Meanwhile all my active PCs at home have moved to openrc/Beowulf. With my kind of operation (office and internet, a nfs fileserver in the background) I have no issues found.
Currently I am investigating runit/Chimaera in VBox.
I can only encourage you to try openrc.
rolfie
Mate 1.20.4 from the Devuan repository.
Rolfie
sudo apt -t beowulf-backports install linux-image-amd64
Should also work and provide automatic kernel updates.
Kernel:
apt list linux-image-5*
apt install linux-image-5.10.0-0.bpo.3-amd64
Firmware:
apt list firmware-linux-nonfree* -a
apt -t beowulf-backports install firmware-linux-nonfree
What happens on
apt full-upgrade
?
rolfie wrote:The main repo is missing.
http://deb.devuan.org/merged beowulf main contrib non-free
Consider if you need to complie packages. If not, disable the deb-src lines.
What does non-free mean in this context? Licenses other than GPL, MIT, and their kin?
Have a read: https://www.debian.org/intro/free.en.html
non-free means code that is propriatry. Unfortunately you will need non-free stuff to get your tg3 working.
Same with me and my AMD GPUs.
rolfie
Actually your post is off topic, you would have better written a new post.
Read https://www.devuan.org/os/packages
rolfie
The problem is also present in a fresh install based on Beowulf 3.0.0 netinstall in VBox. Same procedure used as for the 3.1.0 install, only difference is runit on 3.1.0 and openrc on 3.0.0.
I guess there must be a bug somewhere in Mate. Strangely enough my workstation is fine.
rolfie
You are missing a quote before the print command. Use copy/paste.
rolfie
Just done a Mate install from 3.1 in VBox, can confirm that that installation forgets the picture from the home folder.
rolfie
There should be no difference in the Mate desktop if I update an older 3.0 install or do a fresh install from 3.1 when using the same init.
Beowulf 3.0 install with Mate dated June 2020, amd64 with backports kernel 5.9, up to date:
Just added a picture from my home folder as background: survives changing the background and a reboot.
rolfie
Here is an example regarding ASCII with Mate desktop: https://dev1galaxy.org/viewtopic.php?id=1952
Maybe this helps.
rolfie
cat /etc/apt/sources.list # # deb cdrom:[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200526]/ beowulf contrib main non-free # deb cdrom:[Devuan GNU/Linux 3.0 (beowulf) amd64 - desktop 20200526]/ beowulf contrib main non-free # A network mirror was not selected during install. The following entries # are provided as examples, but you should amend them as appropriate # for your mirror of choice. # deb http://deb.devuan.org/merged beowulf-security main deb-src http://deb.devuan.org/merged beowulf-security main # beowulf-updates, previously known as 'volatile' # A network mirror was not selected during install. The following entries # are provided as examples, but you should amend them as appropriate # for your mirror of choice. # deb http://deb.devuan.org/merged beowulf-updates main deb-src http://deb.devuan.org/merged beowulf-updates main
1. Got any other sources I should use (mirrors, for instance), and if so can you tell me why (or point me towards something that will tell me what and why)?
The main repo is missing.
http://deb.devuan.org/merged beowulf main contrib non-free
Consider if you need to complie packages. If not, disable the deb-src lines.
2. Got anything to read RE mirrors and how that helps me or Devuan in general?
Scan through https://www.devuan.org/. There is a lot of useful information.
During the upgrade (which was blessedly fast and simple compared to Windows 10), I noticed this:
/etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64 W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3
A search indicates it could prevent network cards from working after reboot. If that's an issue, the same says that I need to add non-free to my sources.
https://thespecter.net/blog/technology/ … odule-tg3/Going back to the link rolfie posted:
Note that all software shipped with Devuan in the main component is free software. But if needed, non-free software is also available. Just add the non-free and contrib components to the appropriate line(s) in /etc/apt/sources.list like this:
deb http://deb.devuan.org/merged beowulf main non-free contrib
Is there any way to specify that I only want certain software from a specific source? I do a lot of emulation and rom-hacking stuff, and the authors of programs for such love to require the latest stable versions for compilation.
Enabling contrib non-free does not mean everything in there is installed automatically. You have to install packages from non-free explicitely to have them available. Once they are installed they are maintained automatically. Example:
apt install firmware-linux-nonfree
You may also install non-free packages, and then disable the non-free section in the sources.list again. Your choice. But then the stuff is no more updated.
How would I add package sources from debian while restricting it to the subsets that don't require things that are forbidden in devuan?
This is not recommended at all.
Where can I see the list of packages that are forbidden?
Look for "Banned packages" on the Devuan web page.
rolfie