Bug 22512

Please describe the hardware whit that issue.

Keywords: (none) => NEEDINFO
CC: (none) => j.alberto.vc

Which installer did you use, classical installer (using a non-Live iso) or Live installer?

If classical, please provide 

   /root/drakx/report.bug.xz

from that install

If Live, please provide 

     log.txt

that is the result of running, as root:

    journal -b 1 > log.txt

compress log.txt with xz if it's too large

CC: (none) => marja11, zen25000

Hi Marja,

Sorry, my /root/drakx directory is perfectly EMPTY !! There is nothing in it :-(

I observe this behaviour with BOTH of the supports (64 bits) . For me the responsible is GRUB2 : as soon as a boot option ("Mageia", "MS Window" ..) has been selected, the BIOS boot options order is changed.

Then, the next time you want to stop/restart the system, in place of restarting from the CD or the USB key as expected, it reboots from the hard disk and you have to stop it once again and to go in the BIOS configuration to restablish the correct boot order .. Five minutes lost ..

I know, it is not a big deal when the system is working fine but it becomes painful when you have to reboot and reboot again because you are debugging .. your Mageia installer ;-)

Hardware config :
Dell Inspiron  (09/2016)
CPU : Intel Core™ i5-6400 2.70GHz ×4 
RAM : 8 GB
Vidéo : NVIDIA GeForce GT 730

I think you confuse grub options with bios boot order for devices
https://bugs.mageia.org/show_bug.cgi?id=18785
Check if this fix works for you https://bugs.mageia.org/show_bug.cgi?id=21457#c3

CC: (none) => j.alberto.vc

by the way, check the battery of your bios

Please re-read carefully my last post and you will see I confuse absolutely nothing : when I choose an option (Mageia / Windows) IN GRUB, the BIOS options order is changed : the hard disk is re-selected by default as the boot media in place of any amovible media .

My computer is still very recent and nothing moves in the BIOS configuration as long as I don't touch GRUB2. So I won't spend an hour in testing the BIOS battery ..

(In reply to Michel AUTEM from comment #6)
> My computer is still very recent and nothing moves in the BIOS configuration
> as long as I don't touch GRUB2. So I won't spend an hour in testing the BIOS
> battery ..

Well i see strange things related with that, i have a PC that when the bios battery is empty starts the boot process when connect the cable of the power supply.

Some bios have the option of press a key and give the choice of select boot device on the fly, i know this don't solve your issue but it will save time to you

Unfortunately on my PC this option (F12 at start up) is de-activated with UEFI boot, it works only with Legacy boot .

As I told it, this bug (for me it is a kind of bug) is not a big problem, just annoying when you are debbuging something, or the next time you want to reboot from the DVD reader and you have forgotten -three weeks later- to re-enter the BIOS before, in view to re-establish the correct boot options order .. Each time you say "shit" ..

(In reply to Michel AUTEM from comment #3)
> Hi Marja,
> 
> Sorry, my /root/drakx directory is perfectly EMPTY !! There is nothing in it
> :-(

Are you sure you did a non-Live installation?

We really need logs to see what happened!

I can imagine, if you installed in UEFI mode, that efibootmgr changed the boot order.

In legacy BIOS mode, I can't think of any way in which the BIOS boot order could be changed during installation.

If you don't have /root/drakx/report.bug.xz then I suppose you used a Live medium to install from.

In that case: please attach log.txt as requested in comment #2:

> Which installer did you use, classical installer (using a non-Live iso) or
> Live installer?
> 
<snip>
> 
> If Live, please provide 
> 
>      log.txt
> 
> that is the result of running, as root:
> 
>     journal -b 1 > log.txt
> 
> compress log.txt with xz if it's too large

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0
CC: (none) => mageiatools
Source RPM: ? => efibootmgr ???

(In reply to Marja van Waes from comment #9)
> (In reply to Michel AUTEM from comment #3)
> > Hi Marja,
> > 
> > Sorry, my /root/drakx directory is perfectly EMPTY !! There is nothing in it
> > :-(
> 
> Are you sure you did a non-Live installation?
> 
> We really need logs to see what happened!
> 
> I can imagine, if you installed in UEFI mode, that efibootmgr changed the
> boot order.
> 
> In legacy BIOS mode, I can't think of any way in which the BIOS boot order
> could be changed during installation.
> 
> If you don't have /root/drakx/report.bug.xz then I suppose you used a Live
> medium to install from.
> 
> In that case: please attach log.txt as requested in comment #2:
> 
> > Which installer did you use, classical installer (using a non-Live iso) or
> > Live installer?
> > 
> <snip>
> > 
> > If Live, please provide 
> > 
> >      log.txt
> > 
> > that is the result of running, as root:
> > 
> >     journal -b 1 > log.txt
> > 
> > compress log.txt with xz if it's too large

[michel@linux ~]$ su root
Mot de passe : 
[root@linux michel]# journal -b 1 > log.txt
bash: journal : commande introuvable
[root@linux michel]# cd /
[root@linux /]# ls
bin@         etc/     lib64@       opt/                root/  sys/
boot/        home/    lost+found/  proc/               run/   tmp/
dead.letter  initrd/  media/       release-notes.html  sbin@  usr/
dev/         lib@     mnt/         release-notes.txt   srv/   var/
[root@linux /]# cd root
[root@linux ~]# ls
aif-mount/  Documents/  Images/   Musique/          tmp/
Bureau/     drakx/      Modèles/  Téléchargements/  Vidéos/
[root@linux ~]# cd drakx
[root@linux drakx]# ls
[root@linux drakx]# (==> empty !)

I have nothing to say about BIOS legacy mode, I use only the UEFI mode .

I installed MAGIEA from the two ISO supports because the "Classical" ISO is bugged and forced me to reboot a lot of times, and each time I had to re-enter the BIOS to restablish the correct boot order (or the system restarted each time from the hard disk) .

I'm pretty sure that's not the MAGEIA installation process itself which modifies the BIOS boot options but GRUB2 .

(In reply to Michel AUTEM from comment #10)

> 
> [michel@linux ~]$ su root
> Mot de passe : 
> [root@linux michel]# journal -b 1 > log.txt

Sorry, my bad!!

It should be:

    journalctl -b 1 > log.txt

(In reply to Michel AUTEM from comment #10)

> 
> I have nothing to say about BIOS legacy mode, I use only the UEFI mode .

Thanks for confirming you only use UEFI mode. 
> 
> I installed MAGIEA from the two ISO supports because the "Classical" ISO is
> bugged and forced me to reboot a lot of times, and each time I had to
> re-enter the BIOS to restablish the correct boot order (or the system
> restarted each time from the hard disk) .
> 
> I'm pretty sure that's not the MAGEIA installation process itself which
> modifies the BIOS boot options but GRUB2 .


Only efibootmgr can do that. I think setting the fresh Mageia install first in the boot order list is exactly how it's expected to work, even if you had a DVD or so set first in the boot order list before.

Status: UNCONFIRMED => NEW
Assignee: bugsquad => zen25000
Ever confirmed: 0 => 1
Component: Installer => RPM Packages
Source RPM: efibootmgr ??? => efibootmgr

(In reply to Marja van Waes from comment #12)
> (In reply to Michel AUTEM from comment #10)
> 
> > 
> > I have nothing to say about BIOS legacy mode, I use only the UEFI mode .
> 
> Thanks for confirming you only use UEFI mode. 
> > 
> > I installed MAGIEA from the two ISO supports because the "Classical" ISO is
> > bugged and forced me to reboot a lot of times, and each time I had to
> > re-enter the BIOS to restablish the correct boot order (or the system
> > restarted each time from the hard disk) .
> > 
> > I'm pretty sure that's not the MAGEIA installation process itself which
> > modifies the BIOS boot options but GRUB2 .
> 
> 
> Only efibootmgr can do that. I think setting the fresh Mageia install first
> in the boot order list is exactly how it's expected to work, even if you had
> a DVD or so set first in the boot order list before.

Thanks for you info . This option sounds me a bit strange because I have always considered that the DVD and then USB readers had to be priorized over the hardisk ..
Please find attached my log.txt file .

Created attachment 9993 [details]
log.txt file

I have experience in UEFI Dell
The preferred boot sequence is

UEFI (Windows Boot Manager)
Hard Disk

Because the WIndows Boot Manager (please confirm if the name was changed too) is always restored to the first option every time you think is MGA installer issue, but not

If efibootmgr is modifing this, is because the UEFI firmware 
I know friend's laptop computers that boots USBsticks with EFI if the bootmgr.efi Windows files exists in the root of the stick even you configure to boot in legacy and configured the cbs compayibility

Your laptop computer is dell brand, can you confirm the UEFI firmware in dell support is the ame as your laptop actually has?

Can confirm with dell support if this UEFI firmware is supossed to do that even you reinstall Windows from DVD???

CC: (none) => neoser10

Nothing did change with Mageia 7 . It seems that some stupid guy somewhere at DELL decided that this stupid behaviour of their firmware should be the "nominal" way . It occurs only when I (re)install the GRUB, so I can survive with it and I close this thread ..

Nothing did change with Mageia 7 . It seems that some stupid guy somewhere at DELL decided that this stupid behaviour of their firmware should be the "nominal" way . It occurs only when I (re)install the GRUB, so I can survive with it and I close this thread ..

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