Bug 28073

Martin, this is something along the lines we briefly mailed about...

We could reuse mga-bg-res code for initial image matching

CC: (none) => mageia, tmb

mga-bg-res appears to be broken on my M8 systems when run as root:

# /usr/libexec/mga-bg-res
mmap /dev/zero: Operation not permitted

# bash -x /usr/libexec/mga-bg-res
+ bgpath=/usr/share/mga/backgrounds
+ theme=Mageia-Default
++ readlink /usr/share/mga/backgrounds/default.png
+ curlink=/usr/share/mga/backgrounds/Mageia-Default-1600x1200.png
+ '[' -e /usr/sbin/monitor-edid -a -z '' ']'
++ exec /usr/sbin/monitor-edid
++ grep -m 1 ModeLine
mmap /dev/zero: Operation not permitted
+ res=
++ expr '' : '.*"\(.*\)".*'
+ res=
+ '[' -z ']'
+ res=1600x1200
+ '[' /usr/share/mga/backgrounds/Mageia-Default-1600x1200.png = /usr/share/mga/backgrounds/Mageia-Default-1600x1200.png ']'
+ exit 0

(which as it is automatically run by mga-bg-res.service, is a bad thing)

ah, of course...
the mmap issue comes from kernel security hardening with STRICT_DEVMEM

if one boots with iommu=relaxed it would probably still work...

that would be iomem=relaxed ...

one quick fix first step could be to simply default the background color to something that matches the Mageia theme and then as a second step later on figure out how to do the resolution mapping later.

or we set the full hd image as default and use theme scaling/stretching, but that could get ugly on ultrawide screens...

I am more comfortable with changing the default colour scheme than with using the Mageia background. rEFInd, by its nature, is not tied to any one OS installation, which is why I've avoided any branding and take care not to reinstall or upgrade what's in the ESP unless the user explicitly enables that.

There's also the issue that some people (me!) set their monitors up to use 1:1 pixel mapping, so the resolution/aspect ratio they need is the resolution/aspect ratio of the EFI frame buffer, not of the monitor.

For Mageia 9 I could look at adding an option in drakboot for the user to select a different background image, with the Mageia background available as a default option.

Thanks all for your advices.
Assigned this correctly to Martin, package maintainer.

CC: (none) => ouaurelien
Source RPM: (none) => refind-0.12.0-1.mga8.src.rpm
Assignee: bugsquad => mageia

(In reply to Martin Whitaker from comment #6)
> I am more comfortable with changing the default colour scheme than with
> using the Mageia background. rEFInd, by its nature, is not tied to any one
> OS installation, which is why I've avoided any branding and take care not to
> reinstall or upgrade what's in the ESP unless the user explicitly enables
> that.
> 

Yeah, lets start there for now.
We can figure out the rest for Mageia 9.

Try refind-0.12.0-2.mga8. If you already have refind installed, you'll need to run refind-install to update the files in the ESP, then copy the banner line from refind.conf-sample to your existing refind.conf.

The background colour is the official Mageia dark blue. I had to change the Mageia icon to be a white cauldron to stop it vanishing.

Nice,

that color scheme is better and is way nicer to the eyes... :)

I wonder if one could/should replace the refind logo with the Mageia one (or atleast add it in configs so users simply can un-comment it) for easy "branding"

@ Martin
I will try it.
@ TMB
This is the banner itself, and void around it is filled with the color of the top left pixel. It merits a try.

(In reply to Martin Whitaker from comment #9)
> Try refind-0.12.0-2.mga8. If you already have refind installed, you'll need
> to run refind-install to update the files in the ESP, then copy the banner
> line from refind.conf-sample to your existing refind.conf.
> 
> The background colour is the official Mageia dark blue. I had to change the
> Mageia icon to be a white cauldron to stop it vanishing.

Hi Martin,
I don't see any configuration for banner in /boot/EFI/EFI/Boot/refind.conf-sample.
What do you mean with the banner line?

it's in boot:

 l -1 /boot/EFI/EFI/refind/refind.conf*
/boot/EFI/EFI/refind/refind.conf*
/boot/EFI/EFI/refind/refind.conf-sample*

if you diff conf and conf-sample you see the difference

Replied to the bug report by mistake, to the dev ml with ...
On my system, line 95 of /boot/EFI/EFI/Boot/refind.conf is now
banner icons/dark-blue-banner.png
 
And it's working. Much easier on the eyes when turning on the system in a dark
room.

CC: (none) => davidwhodgins

(In reply to Dave Hodgins from comment #14)

> On my system, line 95 of /boot/EFI/EFI/Boot/refind.conf is now
> banner icons/dark-blue-banner.png

Isn't there a danger that a subsequent update of rEFInd will 'lose' your personal .png file?

Unless rEFInd's policy has changed since I set it up here, one needs to hide such a .png file in a personal subdirectory as defined in refind.conf by e.g.:

    icons_dir myicons

CC: (none) => maurice

No. The refind rpm package does not contain any /boot files. They are
copied to /boot only when the command refind-install is run.

According to the man page, the .conf file is only created if one does not
already exist.

Closing as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

question in comment 10 is not decided on yet:

I wonder if one could/should replace the refind logo with the Mageia one (or atleast add it in configs so users simply can un-comment it) for easy "branding"

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

The logo which can be added could be:
https://wiki.mageia.org/en/File:Logo_mageia_official_dark.png
I tried the 320px, it's a little small.
I don't know if this logo is already packaged.

Status: REOPENED => NEW

I am against branding. We don't make any significant changes to rEFInd, so why should we claim it as our own?

As I've mentioned before, rEFInd is specifically designed to be an independent boot manager, not tied to any one OS. The Mageia refind package is just a convenient way to install it; it works just the same if you install it from a different OS.

You anyway get a Mageia cauldron in the boot menu, and get full Mageia branding when you choose to boot Mageia.

(In reply to Maurice Batey from comment #15)
> (In reply to Dave Hodgins from comment #14)
> 
> > On my system, line 95 of /boot/EFI/EFI/Boot/refind.conf is now
> > banner icons/dark-blue-banner.png
> 
> Isn't there a danger that a subsequent update of rEFInd will 'lose' your
> personal .png file?

This is the .png file now provided as part of the Mageia refind package, so if you update using the Mageia package, then no. But yes, if you update from another source (although it won't be permanently lost, just moved to the icons-backup directory).

I admit I took a shortcut here to avoid changing the refind_install script this close to Mageia 8 release - I intend to improve it for Mageia 9.

(In reply to Martin Whitaker from comment #20)
> I am against branding. We don't make any significant changes to rEFInd, so
> why should we claim it as our own?
> 


It's not about "claim it as our own"...


It's about making it easier for endusers to switch to a theming that matches from start to end...

And many users wants to show of their favorite distro logo everywhere :)

But I dont care that much as the switched background color mkes it way better than before anyhow....

so close this if you want...

(In reply to Martin Whitaker from comment #6)
> 
> For Mageia 9 I could look at adding an option in drakboot for the user to
> select a different background image, with the Mageia background available as
> a default option.

We can leeave the report opened for that.

Indeed, I am happy to make it easy for users to theme it the way they want, but can't do that yet because we are in strings freeze.

(In reply to Maurice Batey from comment #15)

> Unless rEFInd's policy has changed since I set it up here, one needs to hide
> such a .png file in a personal subdirectory as defined in refind.conf by
> e.g.:
> 
>     icons_dir myicons

Actually, I have 3 .png files in that subdirectory, which will all  appear on my 
rEFInd boot menu:

      os_mageia61.png  os_mageia7.png  os_mageia8.png

   [The images are of Gimp-modified Mageia-like icons - see example in Dropbox below.]

 - but of course some extra linkage is needed to get them to correspond to the related installs and boot the right one when selected.

  The extra linkage is provided via the above sub-strings "mageia61", 
"mageia7", and "mageia8" by an automatic look-up in the /boot directory of Linux 
installs discovered by rEFInd for a *partition label* beginning with one of 
those sub strings, and if found that install is then booted.

Example: My Mageia-7 install has a partition label "Mageia7-root", so if the 
Mageia7 icon on the boot menu is clicked the system boots Mageia7.

   N.B. I don't use any Linux .efi boot files, or GRUB at all.

Here is a pic of my current rEFInd boot menu:

    https://www.dropbox.com/s/g71qzxt6h89vhes/mab-refind-menu.JPG?dl=0

and this is my refind.conf file:

    timeout 20
    dont_scan_dirs EFI/tmp EFI/mageia
    showtools memtest reboot shutdown gdisk about
    default_selection 1
    icons_dir myicons

Been happily using this system for years...

drakboot and the installer now allow the user to choose between

  - the default rEFInd banner dark blue background
  - the default Mageia background
  - a custom image file (manually installed somewhere in the ESP)

So closing as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED