Well, I just did a fresh install in VB it works and boots with wayland.
and the settings.
1 Like
I tried with your settings but nothing, it does not boot at all! Only a blank screen with cursor blinking… it’s like calamares do not install grub on /dev/sda.
Which option do you select when the installer offered to install a boot loader?
But when i’ll install on my REAL machine, there’ll be yet partition, because I’ve already another linux (Mint) on others partition! I cannot erase entire hd!
I just installed in a Virtualbox VM and it is OK: https://0x0.st/XNl_.txt
1 Like
i do not say this is the expected behavior… it should work in all options installer is offering.
Only see that i can replicate.
I do not think the same will happen on real hardware.
16:06:15 [6]: DEBUG (Qt): no bootloader
16:06:15 [6]: DEBUG (Qt): grub not used
16:06:16 [6]: DEBUG (Qt): grub
16:06:16 [6]: DEBUG (Qt): no btl not checked
from the log…
[PYTHON JOB]: "Bootloader: grub (bios)"
.. Running QList("grub-install", "--target=i386-pc", "--recheck", "--force", "/dev/sda")
.. Running QList("grub-mkconfig", "-o", "/boot/grub/grub.cfg")
here we see it does install grub
Comparing, @pimpoli calamares log and one from @manuel I see one difference.
16:06:15 [6]: DEBUG (Qt): no bootloader
16:06:15 [6]: DEBUG (Qt): grub not used
16:06:16 [6]: DEBUG (Qt): grub
16:06:16 [6]: DEBUG (Qt): no btl not checked
This part is not there in @manuel log.
This,
[PYTHON JOB]: "Bootloader: grub (bios)"
It is in @manuel 's log but not in @pimpoli 's log. I think no bootloader was installed in the first place. Either he selected the “no bootloader” option or messed up during the manual partitioning.
as i already said i can clearly replicate the error here… and i do not unselect bootloader leaving it selected as default.
I not select “no bootloader”, and I make manual partitioning as usual, a root partition ext4 and a swap partition, with grub on /dev/sda
Any solutions? Is it a bug of calamares?
Ok, then I’m reinstalling this in a VM my first one worked OOTB. Let’s see if this reproduces the same issue.
if i would know i would have suggested a workaround already… still try to figure out how it happens at all…
and flagged the / root partition as boot also?
Seems in case using manual partition it will set no bootloader.
In case using Bios / legacy mode on Virtualbox will check on other VMs now…
Automatic partition methods do work fine.
Installed with all defaults and used auto partitioning. It works.
Log: https://0x0.st/XNUw.txt
I did the installation with manual partitioning and without flagging the root partition as the boot. For me, it booted and worked.
Log: https://0x0.st/XNUf.txt
reason still unknown… could be language selection. you are using en_US i was using de_DE and user is running italian Language?
16:05:50 [6]: static LocaleConfiguration LocaleConfiguration::fromLanguageAndLocation(const QString&, const QStringList&, const QString&)
Mapping "it_IT" in "IT" to locale.
.. Got best match for "it_IT" as "it_IT.UTF-8"
16:05:52 [6]: void Config::guessLocaleKeyboardLayout()
Got locale language "it_IT.UTF-8"
.. looking for locale part "IT"
.. matched "it"
16:05:52 [6]: void guessLayout(const QStringList&, KeyboardLayoutModel*, KeyboardVariantsModel*)
Next level: "it"
16:05:52 [6]: void Config::xkbApply()
xkbmap selection changed to: "it" - ""
I will check…