On 13/12/2020 22.19, mauro wrote:
On 13/12/20 20:07, Carlos E. R. wrote:
It is so small that I can not read the text at the top.
I'm working on that...with 72 × 72 ppi I've got a size of toomuch 2.4MB. Gimp, when I take it down to 25x25, gives me 2.4MB again...I don't get it!
mail the original directly to me, and then I will try to find out what can be done to reduce the size :-)
The file is bad, the:
GRUB_DISTRIBUTOR="shortstring"
must be indeed a short string, not two lines.
Ya, I got that. With a short string and no spaces in it my Yast opens the grub module allright, but after all I don't care if I can not open it from Yast, I prefer to be able to arrange the text in the boot screen as I wish
The problem is, the string is not intended as a message or description (I would like that!) but as identifier of the current operating system, different from others for multiple boot systems. For example: Windows opensuse fedora It is used by grub to display it, but it is also used as directory name on UEFI systems: cer@Telcontar:~> ls /boot/efi/EFI/ auxiliary boot main-os cer@Telcontar:~> Telcontar:~ # efibootmgr BootCurrent: 0003 Timeout: 3 seconds BootOrder: 0002,0001,0003,0004,0000 Boot0000* main-os-secureboot Boot0001* main-os-secureboot Boot0002* auxiliary-secureboot Boot0003* UEFI OS Boot0004* auxiliary-secureboot Telcontar:~ # For instance, my BIOS (actually, my UEFI) barfs on a name like "main_os" and accepts "main-os". It also has a length limitation (I don't know how much). So this naming is critical.
I'm afraid the picture is not that great, I've taken it with a camera, not knowing if it's possible to do a screenshot at the grub bootscreen, and furthermore I have scaled it more than necessary (it seems that susepaste takes images max 1024K)
Maybe, I don't know for sure. Depends on the time to survive. The other day I posted a 382K photo for two months.
Yes, I've read something about a "ttl". But K for a photo is indeed a poor thing. Don't we have a better option than susepaste?
Not ours.
I'm surprised that Grub works. Maybe it seems to work, but things fail later, like the UEFI boot menu.
Andrei will know better what the limitations are, if he is still reading this :-)
no no no, I can assure you, my Grub has been flawlessly working for...months? Maybe a year now, in this non-standard-but-perfectly-functioning conditions :) I'm on olde BIOS though, and I've got no menu, as you've seen, I used to dualboot with the self-acclaimed-philanthropist's evil creature once, but I soon ditched it and that keeps me smiling.
Ah, no menu.
A confirmation/extension/explanation from Andrei would be most welcomed. What puzzles me is that the make config of grub doesn't complain at all...try it! In the worst case you know what to change back.
No, I know for sure my BIOS will break.
I'm gonna see now if i can fix that picture for you
Just email it directly to me, I have some experience :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)