MX-18 beta 1 feedback

[dolphin_oracle]

Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.

The encrypted drive can be accessed with thunar, and shows in disk manager.

looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.

[richb]

Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.

The encrypted drive can be accessed with thunar, and shows in disk manager.

looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.

I thought that was sdc1. the first entry that has a boot flag

[dolphin_oracle]

Beta 1 installed and runs fine. However it did not create a grub entry for a previously installed encrypted alpha on another internal drive. It did create an entry for MX 17.1 on a third internal drive. Same happened in an alpha install but thought it was an anomaly and did not report it.
PS It is an updated MX 17 beta 3 to final.

The encrypted drive can be accessed with thunar, and shows in disk manager.

looks like you wiped out the boot partition at some point. that's what the os-prober will pick up.

I thought that was sdc1. the first entry that has a boot flag

that's the ESP for uefi boots. different thing the /boot.

also, without an uncrypted /boot (like the installer requires), os-prober has no way to know what's in an encrypted partition, so they won't be picked up. not being able to tell what's in an encrypted partition is kind of the point.

[dolphin_oracle]

From grub.cfg

Code: Select all

menuentry 'MX 18 Continuum (18) (on /dev/sdb5)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534' {
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt5 --hint-efi=hd1,gpt5 --hint-baremetal=ahci1,gpt5  8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
	else
	  search --no-floppy --fs-uuid --set=root 8a1b6bd1-cadd-4fce-8bb3-37f3d76fc534
	fi
	linux /boot/vmlinuz-4.19.0-1-amd64 root=/dev/sdb5
	initrd /boot/initrd.img-4.19.0-1-amd64
}

I forgot to mention it's a UEFI boot.

can you try setting your

Code: Select all

root=/dev/sdb5

to

Code: Select all

root=UUID=Actual_UUID_Of_The_Device_here

[richb]

shoot wrong image posted. That drive does have an entry, this one does not.

[dolphin_oracle]

in that case...don't know.

[Gaer Boy]

The boot edit worked fine - posting from MX-18 Beta now. I have 10 minutes to look around.

[richb]

in that case...don't know.

I do not need that install. I just posted in case it was an issue "seeing" an encrypted drive if grub was re-wriiten by another OS.

[Stevo]

Those trying to install the Nvidia drivers might try enabling the test repository in Synaptic, then running ddm-mx to install. We have the 390.87 drivers there also that you need to be able to build on the 4.19 kernel.

[chrispop99]

(Trivial)

Using the Package Installer to add 'HP Printing' adds an entry to Settings, but it has no icon. This was the same in MX-17.

Chris