Page 2 of 37
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:19 am
by dolphin_oracle
I guess the nvidia drivers won't update till we migrate the new stuff to main.
Im more concerned with why you couldn't make an usb with mx-LUM
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:22 am
by Eadwine Rose
I have no idea.. it didn't work with either usb stick.. is there a log file somewhere.. should be on the system I am in now.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 10:24 am
by sdibaja
first run, tried to install Mate from the MX Package Installer
unmet dependencies:
mate-core: Depends: mate-desktop-environment-core ........
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 11:59 am
by Richard
@Gerson,
just leave boot set to root
that is where it has always been.
Some people and servers like to use a separate boot partition,
but I think you'd need to create a /boot if you wanted to use one.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:10 pm
by Gaer Boy
Live usb booted OK and went straight to install on SSD. Halfway through install notifier showed 1 update - mx-welcome. Ignored it. Did not install grub - booted MX-17 to update grub, then booted 18 Beta. Boot failed early. screen messages far more voluble that previously, but the final ones were:
Code: Select all
Running /script/init-bottom failed. No such file or directory.
mounting /run on /root/run failed.
Target filesystem doesn't have requested /sbin/init.
No init found.
ISO md5 is OK. No other oddities seen.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:18 pm
by dolphin_oracle
Gaer Boy wrote: Mon Dec 03, 2018 12:10 pm
Live usb booted OK and went straight to install on SSD. Halfway through install notifier showed 1 update - mx-welcome. Ignored it. Did not install grub - booted MX-17 to update grub, then booted 18 Beta. Boot failed early. screen messages far more voluble that previously, but the final ones were:
Code: Select all
Running /script/init-bottom failed. No such file or directory.
mounting /run on /root/run failed.
Target filesystem doesn't have requested /sbin/init.
No init found.
ISO md5 is OK. No other oddities seen.
did you enable any encryption options?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:25 pm
by Gaer Boy
No - accepted most defaults.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:27 pm
by dolphin_oracle
Gaer Boy wrote: Mon Dec 03, 2018 12:25 pm
No - accepted most defaults.
can you post the grub entry that you used to launch the installed system?
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:43 pm
by Gaer Boy
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.
Re: MX-18 beta 1 feedback
Posted: Mon Dec 03, 2018 12:51 pm
by 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. Is it because it is encrypted? 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.