You are not logged in.
Next step will be installing virtualbox.
Yep, still no /dev/dsp in Daedalus.
But installing wireplumber seemed to be the easy way out of silence.
https://www.youtube.com/watch?v=lL6NUBk_j6M
https://manpages.ubuntu.com/manpages/tr … ign.1.html "Sign an EFI boot image for use with secure boot."
So initrd:s aren't usually signed? Or usually shim doesn't care about those?
... on the other hand, to be able to mount /home from encrypted lvm partition(that is not /) during boot means that initrd has to be modified ...
... but there is no need to modify initrd if there is only 1 big / -partition . No separate /home or swap or anything.
But right now i'm not going to start all over from scratch.
Internet connection works. Lvm works. Sudo works. And "su -" works too.
Soon it is time to install xorg and vbox and fix audio.
I'm between sixes and sevens about that EFI partition(and SB). Maybe i'll bypass that someday(if i can). Boot straight into /boot part instead. With a pre-EFI-era machine that's trivial operation. But maybe not with that Fujitsu.
But I've been also thinking that shim should contain public keys for some distros, right? So with a stock kernel and a one_size_fits_all_initrd there shouldn't be problems with shim when booting those?
... on the other hand, to be able to mount /home from encrypted lvm partition(that is not /) during boot means that initrd has to be modified ...
Edit. I'm under an impression from mokutil-related pages that i can make my own keys with openssl and sign whatever i want on /boot with them. The user_made keys are supposed to go to firmware, right?
Btw , can netinstall's partitioning tool make a working EFI partition or not?
Next time i'll try to remember check the "/"-situation after configuring LVM but before "done". Just in case.
Today i was able to boot the livedvd's, so last night i must have changed the firmware settings before trying to boot the Chimaera or Daedalus
Still planning to run that memtest though.
If it tells you that you have not assigned "/" to a partition then I suppose one way out is to assign "/" to a partition.
I thought that i did.
Starting to think that i should run memtest on that machine.
Last night i noticed that i couldn't boot Chimaera dektop live nor Daedalus desktop live. I think firmware settings should allow booting those. Combine with other difficult behaviour lately...
Topic 8 in https://www.devuan.org/os/documentation … encryption might give some insight how the result about should look alike.
The installation procedure wasn't like that.
sda1=EFI
sda2=/boot
sda3=reserved for encrypted /
sda4=reserved for encrypted VG
would be the idea as far as the partitioning goes.
Call the "Logical Volume Manager". You are asked to provide a name for the Logical Volume group at first. When that is setup you can define Logical volumes, e.g. 1_root, 2_swap as I do, and 3_home if you like. You will be asked for a size definition. You may use MB, % ... . Exit the "Logical Volume Manager" when you are done.
Now you should find /dev/mapper/1_root .... in the display. Select these devices one by one and assign file system and the mount point. Only when this point is done you can leave the partitioning menu and start the installation.
That "Logical Volume" part was the problem. As i said before, i was able to make /dev/sda3_crypt and /dev/sda4_crypt . Even make a PV inside /dev/sda4_crypt .
But the problems started when trying to make VG, and devices /dev/vg/swap and /dev/vg/home . And make those the swap device and /home - partition. I ran into complaints about /-partition. Couldn't get past that "partitioning the disk"-phase.
I guess i could provide some screenshots after i have successfully installed xorg and vbox, to clarify what i mean. But that will take some time.
Daedalus netinstall's UI looks very much like Debian netinstall's UI so i guess the former one is really not under Devuan's jurisdiction?
But maybe there is something that i don't completely understand about that partitioning phase.
I can make encrypted / - partition. And also another encrypted partition and make a "physical volume for lvm" inside that device.But if i try to make VG and LV's inside that second encrypted partitition, i get complaints about /-partition and can't get past the partitioning phase.
Used Daedalus netinstall.
I tried to make /home and swap as logical volumes inside a encrypted volume group with Daedalus netinstall's partitioning tool. Couldn't get out of that partitioning phase because of complaints about / -partition.
Bug or a feature? Or something else?
Found these links:
https://dev1galaxy.org/viewtopic.php?id=4039
https://dev1galaxy.org/viewtopic.php?id=2856
maybe those will be helpful some day. Before that i would like to make lvm, sudo and some other packages work. It seems that i have to install something called libsystemd so that i can install lvm2.https://pkginfo.devuan.org/cgi-bin/pack … =2.03.22-1
Although, if i remember correctly, i'll may have to update initrd in order to enable /home on a logical volume.
I wonder if there is going to be problems with that updated initrd when shim or SB is enabled?
Today i'm not in the mood for writing an initscript to enable lvm after initrd is done.
Edit. i think i saw some lvm-related scripts under /etc/init.d inside virtual machine i made. I installed Chimaera on that vm.
One thing i noticed with Daedalus: the manual partition tool was getting my way when trying to do things. How about giving an option to jump into a shell and giving the necessary commands by hand? In the partition menu i mean. To accompany those automatic and manual modes.
This week i found the "jump to a shell"-item in Daedalus's installation menu
But maybe there is something that i don't completely understand about that partitioning phase.
I can make encrypted / - partition. And also another encrypted partition and make a "physical volume for lvm" inside that device.
But if i try to make VG and LV's inside that second encrypted partitition, i get complaints about /-partition and can't get past the partitioning phase.
Used Daedalus netinstall.
Planning to figure out what mokutil can and cannot do.
It seems that i have to sign vmlinuz and initrd if i want to boot Devuan when SB is enabled. It would be nice if i could sign more than just those. Just in case.
I have also heard about something called EFI-Stub. Can i bypass loading anything from EFI partition with that?
But one step at a time...
After some experiments it became clear to me that when secureboot is on, it verifies the signatures on removable media too. For some reason i thought that when SB is on it just refuses to boot from that kind of media.
Either there were no /dev/dsp in my Chimaera install or "chmod o+rw /dev/dsp" as root didn't help. Not quite sure anymore which one was the case. Should document better.
So, chain-loading from UEFI with GRUB, is it possible or not?
Answering to myself: that would be a no, because https://www.gnu.org/software/grub/manua … t-and-shim .
Although i can load grub's configfile from another partition.
Also, should there be signed .efi-files inside that Daedalus install disk?
I'll run "ls -laR $daedalus_boot_dir | grep efi | less" soon. I know that latest Ubuntu server install disk boots, and Daedalus install disk won't, when secureboot is enabled.
This time it looks like "su -" works without problems. Haven't tried any sudo stuff yet.
Would like to find out if i can boot into Daedalus when SB is on.
It would be also nice if i can make SB protect the cntents of Daedalus's /boot somehow. If possible.
I heard rumours about somethings called mokmanager and mokutil...
Made a working /boot and /boot/EFI for Ubuntu. Also made additional partitions and installed Daedalus into one of them.
Tried to chain-boot from Ubuntu's /boot to Daedalus's /boot with:
menuentry chain {
insmod chain
set root=(hd0, part_x)
chainloader +1
}
as grub.cfg in /boot/EFI/ubuntu . Got some EFI-related complaints from GRUB. I hope i got the partition number right in "set root"-line. I mean that part_x should be the /boot of Daedalus.
Also i tried to boot straight into /boot partition of Daedalus with super grub disk. That worked.
So, chain-loading from UEFI with GRUB, is it possible or not?
Also, should there be signed .efi-files inside that Daedalus install disk? I'm starting to think that maybe using that Ubuntu-disk wasn't absolutely necessary step...
Looks like i can boot Ubuntu install disk when secureboot is turned on. Let's see if can make a working /boot - partition with it.
Tried to boot Fujitsu with devuan live. It worked. And after that, tried youtube. I got sounds out of my hardware. So the silence may be a problem with configuration after all.
https://www.youtube.com/watch?v=rRV8ln2VnHc Velikije Luki- Afganistan
Some day i have to re-install that Devuan. Getting tired with that "super grub disk 2 method". That disk is getting scratched and external dvd will outlive its usefulness some day.
May of last year, i had w10 install disk that was ancient enough to co-operate with D4. I may have misplaced it somewhere. So Ubuntu install disk may be needed.
There is some highly mysterious dark magic going on with that laptop and its firmware.
W10 install disk seemed to fix some of that weirdness.
https://en.wikipedia.org/wiki/Gutmann_method#Criticism not fully convinced that Guttman's method has additional value over DoD's 7-times-wipe.
And if you don't trust DoD's method, there's always a sledgehammer and gas-welding-equipment. Much quicker than Guttmann, at least.
I think that booting from usb stick or optical disc is not supposed to work when secureboot is active.