You are not logged in.
Isn't the error message explicit enough? You need to use the command like this:
# dpkg-reconfigure localesThis is useless:
# dpkg-reconfigureSure you can. You need network to be able to load sw from the web. That will also work in a chroot environment.
Or you load packages with a different computer to a flash drive and copy it to the system causing problems. Installation via dpkg -i.
On Beowulf and Chimaera the efivarfs seems not to be loaded automatically on my systems. To avoid issues with the kernel writing crash dumps into the efi flash bricking the MB, I am used to add this line to the fstab:
# To stop linux accessing the EFI variables
efivarfs /sys/firmware/efi/efivars efivarfs ro 0 0I have installed Daedalus on my laptop now, and I am getting errors during boot saying (from bootlog):
Mounting local filesystems...mount: /sys/firmware/efi/efivars: efivarfs already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call.Well I tried with adding a remount before the ro:
# To stop linux accessing the EFI variables
efivarfs /sys/firmware/efi/efivars efivarfs remount,ro 0 0and now I am getting a different error:
Mounting local filesystems...mount: /sys/firmware/efi/efivars: mount point not mounted or bad option.
dmesg(1) may have more information after failed mount system call.In both cases dmesg does not show additional info.
Now I am stuck, whats wrong? The behaviour definitely is different
Did you use a root terminal? Did you become root with su -?
Normally drivers are included in the kernel image. The network chip itself isn't brand new, but when you check on the net there was an update of the e1000e driver in 2020. Chances are that the backports kernel improves the stability of the network.
What you need to do:
1.) Add backports to your sources.list. Instructions: https://www.devuan.org/os/packages
2.) Install the backports kernel: # apt -t chimaera-backports install linux-image-5.19.0-0.deb11.2-amd64
Reboot and test. If it works, also install the meta-kernel-package from backports: # apt -t chimaera-backports install linux-image-amd64 to receive updates.
Good luck
Which release do you use? Chimaera? Have you tried the backports kernel?
Try again later. Maybe one of the mirrors just had a hickup.
When you directly copy new firmware to /lib/firmware you need to build a new initrd to make that work.
But it's not good enough.
Devuan is supposed to be 'vanilla.'
It's not good enough.
... and what this aspect is concerned Devuan = Debian, both behave the same.
Checked my installations: except for on my laptop the dosfstools is present.
On my laptop I just saw in the boot messages that the efi system partition wasn't ok (volume not properly unmounted ...). This is a vfat partition mounted at /boot/EFI, and according to the fstab entry a fsck should be done during each boot. I am wondering why this did not work.
Well, unmounted the partition and tried to run fsck.vfat against this partition. To my astonishment the command wasn't found. After some research with the duck I installed the dosfstools package, then the check worked. I had to clear the dirty bit.
Comprehension question: is the installation of the dosfstools package mandatory to make the fsck during boot work?
Thanks, rolfie
HDD feels slow nowadays compared to SSDs. NVidea support on Linux partially is poor.
If you want to avoid kernel upgrades, remove linux-image-amd64. This is a meta-package w/o content, just refering to the latest kernel.
rolfie wrote:The default efi entry is called debian. As long as you work without Secure Boot, you may boot your install media in rescue mode and write individual efi entries for your installations, e.g.:
# grub-install --bootloader-id=devuan4 --no-uefi-secure-bootI have used devuan4 for Chimaera and devuan5 for Daedalus.
Where should I do it? in chimaera (the only which boots)?
Well, thats an approach that works with grub. I have no idea about rEFIne, never used it. And yes, the first and easiest to do would be to start with Chimaera and define an individual name for this version.
In a second step, I would try to boot the Daedalus install media, select rescue mode, select the partitions for Daedalus for a chroot environment, and use the above approach to define a new name for the Daedalus installation. Then it is easily possible to boot either Chimaera or Daedalus with grub, whatever you like.
The default efi entry is called debian. As long as you work without Secure Boot, you may boot your install media in rescue mode and write individual efi entries for your installations, e.g.:
# grub-install --bootloader-id=devuan4 --no-uefi-secure-bootI have used devuan4 for Chimaera and devuan5 for Daedalus.
When booting the installer make sure you are booting either in legacy mode for a CSM installation or in UEFI mode for a modern efi installation.
Got my laptop fixed again. Booted the installer stick into rescue mode, chrooted into the encrypted system. To get that working I needed to load some Realtek firmware for wired network access. Took me a while to figure out that the stick I first used wasn't FAT formatted. The installer didn't like that.
# grub-install --bootloader-id=devuan4 --no-uefi-secure-boot
# update-grubThat fixed it for me.
Edith
Note to the public: in general probably a simple
# grub-install
# update-grubwill do the job.
Chimaera: Just tried the update on my laptop: Yes, the grub update will cause headaches. Acer Aspire 5 A515-44, efi only, encrypted LVM with unencrypted root. The installation worked on second try (had to enable rw for the efivarfs), creates a new debian entry in the efi, on reboot the grub rescue shell comes up with "symbol grub_disk_native_sectors not found".
When I use F12 to select my original entry devuan4 the laptop boots. Then I removed the debian, and now I am getting the error also on my devuan4.
At least for encrypted system, you need to rebuild the initramfs to include the new firmware:
# update-initramfs -c -t -k allHow does the kernel know where to find the system-uuid? It is inside the LUKS partition. To see the UUID of the encrypted partition it would have to decrypt the LUKS partition first. How does it work?
Have a look at /etc/crypttab. The contents of this file is one of the inputs for grub and the initramfs.
Which partitioning software is it in this documentation?
These are pictures taken from the standard installer in normal mode.
No, wget as listed above does not work, because there is no http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb, there only is a http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring-udeb_2022.09.04_all.udeb.
Did the upgrade twice on two of my Daedalus VMs using the wget method, worked out fine with the devuan-keyring_2022.09.04_all.deb package, no udeb required.
The wget-method works on Daedalus. Attention: expand the path completely.
Well, you might as well load https://devuan.org/ in the TOR browser. Works perfect.
There are some hints on https://www.devuan.org/os/packages