Please, someone please can explain me why my leap16 grub starts with a veri low resoultion ?
It starts very low and then once it’s starting one of the available leaps, the right resolution kicks in.
Can you specify your bootloader ?
I guess you’re using Grub2-bls, in which case this is a known limitation.
1 Like
i don’ t know which groub is, it is the one created by leap 16.
The previous ones created by the lep 15.* series, also recognized Windows installed on the second HDD. Something this one wouldn’t even dream of. Has it gotten worse?
@harlequin can you show the output from update-bootloader --show and os-prober
@malcolmlewis here the output :
ight@leap16:~> update-bootloader --show
Il percorso assoluto per ‘update-bootloader’ è ‘/sbin/update-bootloader’, quindi per avviarlo potrebbero essere necessari i permessi di super utente (es. root).
light@leap16:~> os-prober
unshare failed: Operation not permitted
/usr/bin/os-prober: riga 106: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
/usr/bin/os-prober: riga 184: blkid: comando non trovato
light@leap16:~
opensuse leap 15.6 started mate desktop in high resolution, i.e., icons were normal sized. All icons loaded at normal high resolution.
leap 16.0 loads the desktop at lower resolution, i.e., larger icons. Then after icons are loaded it then switches to the high resolution. Makes for a very cluttered desktop during loading.
It’s good you showed (included) the command you executed in the output and including the final prompt.
Unfortunately, you should execute the commands as the root user (not as regular user).
Second: the output is not in English, which this thread is tagged as, so is not readable for many folks reading.
So, please execute the commands as you did before, but please type “LANG=C” BEFORE the command:
# LANG=C update-bootloader --show
and then the second command as
# LANG=C os-prober
Typing “LANG=C” before the command will output the command in English.
here the output
sudo LANG=C update-bootloader --show
grub2
sudo LANG=C os-prober
602.422783 | DM multipath kernel driver not loaded
/dev/sdb5:openSUSE Leap 15.6:openSUSE:linux:btrfs:UUID=b5d1eb55-4259-4037-9a17-322de400a9e2:subvol=@/.snapshots/1248/snapshot
/dev/mapper/system-root:openSUSE Leap 15.6:openSUSE:linux:btrfs:UUID=2e998396-675d-41ea-adaa-f55e36423e80:subvol=@/.snapshots/1/snapshot
You write, “it starts low”
and then write, “… then once it starts …”
I’m confused. (or maybe I misunderstand post).
GRUB only “starts” once. It shows boot choices. Then you click a choice (I have two).
The next system menu shown is the DE (KDE, etc) login screen, not GRUB.
See the screenshots …
After I select a boot choice, the KDE Login screen is shown (cropped it).
GRUB boot menu (really 640x480)
KDE Login (really 1600x900)
@harlequin so your using Legacy (MBR) boot on this system, are the others installed with Legacy grub as well?
Am I seeing correctly that this is Leap 16.1?
Yes, I found it here (or did I goof up?):
It is the Alpha, Leap 16.1 will only be released in October.
@malcolmlewis , all the systems are installed with legacy grub.
@tckosvic said the same thing as @harlequin above. After grub, when loading desktop, leap 16 loads desktop at low resolution and afterwards changes to the high resolution. leap 15.6 loaded the desktop at high resolution and did not write things over top of others.
@harlequin likely changes with the kernel and using legacy boot…
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/index.html#jsc-PED-12206
@malcolmlewis , I seem to remember that I disabled UEFI in the BIOS some time ago due to problems it had caused me with the NVIDIA drivers. Now, with Leap16 installed and with two Leap 15.6 partitions on which the next Leap16 installation is planned on both (a clean install and not an upgrade), what should I do? Is it possible to install the next ones by enabling UEFI in the BIOS without compromising the Leap 16 already installed?
@harlequin older Nvidia cards perhaps? No, they are mutually exclusive…
I wonder why there is NO indication that this is a “16.1 Alpha” release (??). If you go to the URL I show, there is nothing marked (the sub-dirs or filenames) “alpha”. And that URL is an official openSUSE website.
The Agama installer does not indicate it’s Alpha when showing the options to install (I took screenshots).
And when I log in to the installed system, and go to KDE “Info Center”, it shows “Leap 16.1” but no “alpha” label.
I’m not saying this is a GA release, but I’m surprised there’s no indication this is an Alpha.
Because the URLyou show is the basic redirector (Mirror) link.
The official download site, shows that 16.1 is in alpha state:
