You are not logged in.
Beowulf? Then you need to patch a file. Gone with Chimaera.
For the patch read this please: https://dev1galaxy.org/viewtopic.php?id=1753
rolfie
.. and then you can remove the "supervisor password" with the machine still having disabled SecureBoot ?
Haven't tried that because the Supervisor PW disables any change of the BIOS settings. Since its a mobile unit I think PW protection makes sense.
And Chimaera is encrypted anyhow.
Maybe I give it a try while I am at home ....
rolfie
I did not choose the display manager, I simply got whatever the default is. Is there some reasonably simply config file that can be changed to use a different display manager?
Yes, I'm getting seriously interested in upgrading. This string of disabling screwups is really getting frustrating.
Well, meanwhile I know what I want and how to install a system with SW I want from CLI level onward. I have read the release notes and the recommendations of the suitable combinations. I am happy with lightdm.
What I do is:
apt install xorg
apt install lightdm
apt install mate-desktop-environment-extras --no-install-recommends on older PCs/for my wife
apt install cinnamon --no-install-recommends on my workstation and laptop.
followed by installation of all the goodies I use and need (got a nice piece of paper documenting my procedures and experiences).
About switching the display manager: I have no experience with that.
rolfie
I gave Slim a try on ASCII and abandoned it for LightDM. Get rid of Slim. I consider it to be a pain .....
And consider upgrading to Beowulf, works fine. Meanwhile I am on Chimaera on all the every day used computers. Its rock stable.
rolfie
Bought an Acer Aspire 5 laptop in April this year. No more CSM present, thanks to the agreement of the major HW/SW suppliers.
To be able to disable SecureBoot you have to set a supervisor password.
Installed Chimaera on it, since then working fine.
rolfie
Probably no Debian package?
I get the same error on my wife's PC (Chimaera, openrc, MATE). When I klick ok, I get the dialogue.
No issue on my PC with Chimaera, openrc, Cinnamon.
rolfie
When reading the initial post and the thread: Maybe another victim of the path issue? Have you read the (Beowulf) release notes and are you aware of the difference between su and su -?
Some days later: today I was called to my wife's PC because it was un-usable. My wife missed the popup, it closed by itself and left the desktop (Mate) sort of locked. Could not open the menu, start no desktop item, the context menu of the desktop came up, but no action was possible. Could trigger a shutdown with CTRL-ALT-DEL.
After the reboot I looked at the group settings of my wife, and corrected one or the other thing. E.g. I added her to the bluetooth group, removable, CDROM..... Looks like this fixed the issue.
rolfie
Maybe another victim of the path issue? Have you read the release notes and are you aware of the difference between su and su -?
My wife's PC, upgraded from Beowulf to Chimaera. She gets a popup on every login requesting "Setting RfKill State requires privileges". When I log on on the same PC under my account, no popup. On my PC, same hardware, native Chimaera, I also do not get this popup. There is no bluetooth hardware built into both the PC's.
The only thing that might be different on my wifes PC is that there is a ReinerSCT tanJack deluxe for homebanking installed, but that is connected via USB and should not have bluetooth communication (no hint in the manual).
Looks like the policy org.blueman.policy is causing this. My wife usually cancels the popup.
Well, checked if rfkill is installed. Wasn't, installed it and no change. Also entering the root PW once did not change the behaviour.
Where do I start with troubleshooting? De-install blueman?
Thanks, rolfie
Haven't got any further ideas. Your install is behaving un-normal. That no EFI partition is possible may be due to that the installer possibly is started in legacy mode. But why ext3 and ext4 as options are missing?
Maybe some of the issue are due to the fact that you need to start the installer with an additional stick being present.
rolfie
I am sorry I don't get what you are doing, and why you have problems like not being able to set the boot flag and why ext4 isn't available. Are you using Manual Partitioning? This is recommended for an individual setup as you like it.
Steps:
1.) Highlight the disk where you want to install (sda, nvme....) and press Return (RET). You should be asked if you want to create a new partition table. Say yes and choose gpt (I just did that in a VM). May you have created partitions already, does not matter, they are getting deleted.
2.) When thats done, in the next screen you should see the disk and below that a line that says free space xxx GB. Move the cursor to the free space and press RET.
3.) On the next screen select "Create a new partition", press RET. Specify 256M as size, Beginning. Press RET.
4.) On the next screen first scroll down to Use As (ext4 should be presented as default). Press RET. You should get a list with 15 choices starting with ext4, ext3, ..... , Do not use.
5.) Select EFI System Partition and press RET. You should get a screen where the name is empty, the bootable flag is already set. You can't specify any mount point here, this is done automagically by the install process.
6.) Move the cursor up to the Name field, press return and call it e.g. EFISystem.
7.) Move the cursor down to "Done setting up the Partition" and press RET.
8.) On the next screen move the cursor to the large free space below the EFI partition. Press RET. Specify 64G, beginning, RET. Note: the installer leaves 1M empty before the EFI partition.
9.) Again you should see a screen that starts with Name, then Use as (you should see ext4 as default). You should leave everything at default, and just modify Name and Label. When you are happy move down the cursor to "Done setting up the Partition" and press RET.
10.) Same game for the swap partition. Specify 16G and beginning. USE as Swap partition. Done RET.
11.) Same game for /home. Slect the rest of the disk, Use as ext4, mount point /home. Done RET.
12.) Move cursor to "Finish partitioning..." and RET.
Now you should have the disk split up in 256M EFI System, 64G for /, 16G for Swap and the rest for /home.
rolfie
Well, the result from the search is misleading.
I would suggest you remove slim (isn't really maintained any more) and install lighdm. Then you will have the full set of features for multiusers.
rolfie
I just tried the latest netinstall dated Sept 13th in VBox. The installer main menu misses the "Setup users and passwords" initially. I usually load the LVM and the static address bits during "Load installer components ...", and after that the "Setup users and passwords" suddenly is present.
rolfie
If you go for an unencrypted install which is much easier for a beginner, no separate /boot is required.
On Install Devuan it says:
It's important to choose the correct [GRUB] bootloader location. It should not be installed to a partition but to the MBR area which is located on the hard disk.
What does that mean in my set-up?
Thats only valid for the legacy install, you can ignore that. There is no nice efi install howto (yet).
efi installs have a fixed setup. In the efi partition a bootloader is installed, the kernels and the residual parts and configs for grub are installed in /boot (which does not need to be in its own partition).
You will get asked as one of the last things if you want a (I don't know how this is in English, I only do German installs normally) USB something path, you may ignore that and say no.
rolfie
Stop, that not right. You need to go for an efi partitioning scheme. If you are getting asked, use GPT not msdos.
1.) 256M as "efi system partition", will be formatted as FAT32, bootable flag set, name is your choice (not required), will be mounted to /boot/efi later on. Will hold the efi starter.
2.) 1024M to 2048M for /boot (but only if you want to encrypt your root). ext4, name is your choice (not required)
3.) Unencrypted root: since you have a 500G disk/ssd I would spend 64G for /root. Gives you plenty of headroom for additional SW. ext4. name is your choice (not required).
4.) I would spend 16G for swap
5.) Rest for /home, ext4, name to your choice again.
If you want everything encrypted, thats a different beast.
rolfie
No need for excuses. To fix that: you are allowed to edit your posts. In the bottom of the post your find 4 options, one is edit. This means you can delete the extra line.
To the installer: just did such an install of Chimaera into a VBox VM about a week ago, there it was no such issue. Looks like a bug in the latest installer?
rolfie
What is Beowulf Gold? The step "Setup users and passwords" normally comes past setting up the network. In expert mode you just have to klick through that step. Maybe https://www.devuan.org/os/documentation … all-devuan helps to show what to expect. Chimaera isn't that much different.
Make sure you got the official downloads from Devuan.
rolfie
Just found something in a German laptop forum about rufus and Secure Boot: rufus does not write a valid Secure Boot signature. That means in your case rufus isn't the right tool.
rolfie
Edith: well, I have successfully used rufus for a lot of bootable USB sticks in the past. Legacy mode or UEFI, it always worked fine, but without Secure Boot. I always did disable this "feature".
Have a look at https://www.devuan.org/os/install and drill down the links. Especially https://www.devuan.org/os/documentation … all-devuan may be useful. Unfortunately it only shows the legacy grub installation, not the efi version.
rolfie
When I boot one of the latest Devuan isos in VBox, I get:
UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDKII, 0x00010000)
Mapping table
FS0: Alias(s):F0c:;BLK0:
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)
BLK2: Alias(s):
PciRoot(0x0)/Pci(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)
BLK1: Alias(s):
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)/HD(2,MBR,0x6B8B4567,0xFC8,0x5C0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>I am used to switch to FS0: based on the experience that some of the VMs won't autostart. Then I typically drill down the EFI folder and find some *.efi file which can be booted. Here I get on ls:
Shell> FS0:
FS0:\> ls10 Files: boot.cat, debian, devuan, g2ldr, g2ldr.mbr, md5sum.txt, README.html, README.txt, Release_notes_chimaera_4.0.0.txt, setup.exe
5 Dirs: boot, dists, docs, firmware, pool
I have drilled down every single directory and searched for a *.efi file, no success. Using BLK1: is the same.
When I try exit on the shell, I get a menu, but no useful option I could start with the Boot Manager.
Nevertheless, found something new: when I exit the menu with the Continue option, I get presented a different mapping table:
Mapping table
FS0: Alias(s):F0c:;BLK0:
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)
FS1: Alias(s):CD0c1:;BLK2:
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)/CDROM(0x1)
BLK4: Alias(s):
PciRoot(0x0)/Pci(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)
BLK3: Alias(s):
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)/HD(2,MBR,0x6B8B4567,0xFC8,0x5C0)
BLK1: Alias(s):
PciRoot(0x0)/Pci(0xF1,0x1)/Ata(0x0)/CDROM(0x0)Drilling down FS1: brings an efi directory and a bootable bootx64.efi file. BLK1: is the above mentioned file system (10 files 5 dirs).
Strange behaviour.
rolfie
@Ralph: thanks for taking up this side issue. Maybe we should ask Golinux to split out this as a separate thread.
Ok, lunchbreak is over now. I have looked at the original iso and my creation, here is the output:
# fdisk -l devuan_chimaera_4.0.beta-20210906_amd64_netinstall.iso
Disk devuan_chimaera_4.0.beta-20210906_amd64_netinstall.iso: 371 MiB, 389021696 bytes, 759808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6b8b4567
Device Boot Start End Sectors Size Id Type
devuan_chimaera_4.0.beta-20210906_amd64_netinstall.iso1 * 0 759807 759808 371M 0 Empty
devuan_chimaera_4.0.beta-20210906_amd64_netinstall.iso2 4040 5511 1472 736K ef EFI (FAT-12/16/32)
# fdisk -l daedalus.iso
Disk daedalus.iso: 373,22 MiB, 391350272 bytes, 764356 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytesThe VM based on the daedalus.iso is running Mate desktop on encrypted LVM with openrc with daedalus in the sources.list.
I can't answer what VBox does not see. Does it make sense to show the printouts I am getting?
rolfie
No. Me neither. What is the EFI partition in the Devuan isos?
In the meantime I have found out that the BIOS Superuser password of the PC is set, which prevents me from disabling Secure Boot. (I bought the PC secondhand.)
Asking the seller isn't an option? At least give it a try.
rolfie
1) Why doesn't it boot? What does happen on the attempt?
I end up in the VBox efi shell and can't find any command that allows to boot the iso image. In the EFI directory copied from the Debian iso's there is a grubx64.efi re. a bootx64.efi. When that is added the iso starts automagically the installer.
rolfie