You are not logged in.
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
I am getting exactly 96c4a206e8dfdc21138ec619687ef9acf36e1524dd39190c040164f37cc3468d on my download checked with gtkhash.
Would suggest you download again and recheck.
Edith: saw that the address given was a link and used right click - copy link adress in FF.
There is nothing special with LVM on Devuan. It works fine on my machines. Mostly created while installing the system.
Here are three links to HowTo's:
https://tldp.org/HOWTO/LVM-HOWTO/
https://linuxhandbook.com/lvm-guide/
https://www.howtoforge.com/linux_lvm
The first I have used a lot.
Any installer will do, there is nothing special to be done to make grub boot an encrypted root. I am using FDE with unencrypted /boot and an LVM in an encrypted partition for / and /swap for many years now, no issues. Legacy Bios or efi, mbr or gpt do not matter, all combinations work.
Cook book:
* I only use manual partitioning: p1 with 2048 MB for /boot, ext4; for p2 the encrypted partition I use 32G for / plus at least 32G for swap, i.e. 65535MB. Change these values to your demands.
* Select volume for encryption for p2. You have to enter a PW for the encryption.
* Select that volume and change it from ext4 to a physical volume for LVM.
* Define vg and logical volumes. Make one LV to /, ext4, the other one to swap.
* Write all to disk and continue with the installation. At the end the system should boot automagically and ask for the PW for decryption.
Manually setting everything up is a bit fidelly. There is a guide for guided setup at: https://www.devuan.org/os/documentation … encryption which is much easier.
Good luck, rolfie
Well, the error you got saying "EFI variables are not supported on this system." tells me you run into the same problem I have seen several times with Chimaera. Have a read through this thread: https://dev1galaxy.org/viewtopic.php?id=4496
I guess you need to mount the efivars before running the grub-install.
Good luck, rolfie
Use the normal net-installer, not the live media for installation. Then you have the option of creating an LVM. I do this all the time for my encrypted installations.
The expert installation is meant for people who know what they are doing. If you skip the menu option "Load installer components from installation media" you will get the minimum options for file systems. You do not need to tick one of the additional options, but when you abort that topic the required support for advanced file systems are not getting loaded.
VBox 6.1.36 has been released. Builds kernel modules against 5.18 kernel now.
VBox 6.1.36 has been released. Builds kernel modules against 5.18 kernel now.
When you search the forum a bit, you will find threads that describe that there were issues generating new installer isos for Daedalus. The note in the Daedalus directory suggest to use Chimaera media and then to upgrade to Daedalus for the time being.
Use the Download link on top of the Forum page, or look here for Chimaera: https://files.devuan.org/devuan_chimaera/installer-iso/
Rebooted. UEFI cannot find grub.
Guess: the install media was booted in legacy mode. I have installed Chimaera so often in efi mode meanwhile I can't imagine what else might have gone wrong.