You are not logged in.
Pages: 1
I figured it was some form of operator error, but also figured it would be handy to know how to get a working multiboot grub menu including windows etc for new folks just kicking the tires. Did not test with bios setups.
Installed grub version is 2.06-8
Having no boot options generates panic for many folks, even though fixing it is usually relatively easy.
As a follow up, re-enabling os-prober per Miyolinux in Daedalus live system prior to running the installer enables a fully populated grub config.
(and possibly a Debian entry in the UEFI menu, not sure what grub setup did that)
The "missing grub binaries" were just a path issue, had to do "su -" to get proper roots path, sudo and su aren't getting full path as usually seen, possibly intentional?
In the 2/2023 Daedalus /etc/default/grub "GRUB_DISABLE_OS_PROBER=false" line is simply commented out .
MiyoLinux wrote:
... open and edit the following file...
/etc/default/grub
...and add the following line...
GRUB_DISABLE_OS_PROBER=false
Save and close the file, then open a terminal and run an...
update-grub
I'm running on a Lenovo Thinkpad X260, dual core i7 32gb ram, 2TB nvme ssd, native UEFI from ~2018. Std Intel cpu w/integrated gfx.
New-ish to Devuan, but my Year of Linux on the Desktop was 1993...on my Amiga.
Ran into same issue, installed Daedalus from the live iso from Feb 2023...Grub entries for windows, Mint LMDE5 and Mageia disappeared upon Daedalus Kernel updates (obviously works somehow), although I initially booted Daedalus by running install-grub in Mageia, which has no issues with os-prober and dutifully created new entries for me.
The initial "grub install" in the Devuan live installer didn't actually install grub, which was more or less expected from the installers text.
LMDE also had no issues finding and creating entries for Daedalus. (in fact, both LDME5 and Mageia create UEFI boot menu entries as well as grub entries, including for Devuan)
poking around, the grub installation "appears" broken, as the usual grub binaries and scripts are mia-- i.e no "grub-install" "grub-mkconfig" etc.
I supposes its also possible they decided to rename everything without telling anyone, will have to figure out whats actually installed.
(I had the same gripe with grub2 that everyone had with systemd--- way too much code for a simple task. IIRC grub2 is larger that msdos 5)
Also tried grub2-install and other name variants, and needless to say grub-configurator didnt work due to no grub-install or grub-mkconfig.
Perhaps we should point out to the grub devs that grub also has "attack vector" issues, esp as it can boot non-signed images.
Anything that operates on bare metal has ~same potential issues.
Perhaps Poettering can contribute a bootloader extension to systemd that Microsoft will approve of? Wouldn't that be great ;-/
Have uncommented the disable comment for osprober in /etc/default/grub will try that edit prior to install this time to see if it works.
Pages: 1