Description of problem:
I have a direkt-tek DTLAPY116-2.
I installed win 10 from usb media with no issues.
I can boot ubuntu 16-04 from usb media with no issues.
I installed kubuntu 18-04 from usb media with no issues.
Using Mageia-6-x86_64-DVD.iso, I am unable to start the installation process.
I tried 3 different methods to make usb media (all of which work on other x86-64 computers), but none would boot. I tried a usb dvd player with mageia-6, but it would not boot either.
Version-Release number of selected component (if applicable):
mageia 6 x86-64 bit
Steps to Reproduce:
1. make usb or dvd media of mageia-6
2. try to boot
We would need more details.
At which step did the install stops?
Any error message?
It never displays any message. No text, no graphics.
There is sometimes a single white pixel near the upper left of the screen.
I am pretty sure it is some kind of UEFI booting issue.
The ubuntu 16.04 and 18.04 usb boots and installs with no issues.
The windows 10 usb boots and installs with no issues.
I have installed mageia 6 on at least 2 other laptops with UEFI with no issues.
mageia 6 can't start installation using usb or dvd on direkt-tek DTLAPY116-2 =>
mageia 6 can't boot installation medium (neither usb nor dvd) on direkt-tek DTLAPY116-2
mageia 6 can't boot installation medium (neither usb nor dvd) on direkt-tek DTLAPY116-2 =>
mageia 6: can't boot installation medium (neither usb nor dvd) on direkt-tek DTLAPY116-2
Have you disabled secure boot?
Can you enable the CSM in the BIOS and boot in legacy mode?
Ah, from https://email@example.com/msg288926.html it looks like this machine has a 32-bit EFI BIOS. That's not supported in Mageia yet.
If you still have Ubuntu installed, you can check if this is the case by opening a terminal window and typing
It has a 64 bit fw_platform_size.
I just tested the usb media on a 15" dell laptop, and it boots fine.
99% sure this is a UEFI issue.
mageia 6: can't boot installation medium (neither usb nor dvd) on direkt-tek DTLAPY116-2 =>
mageia 6: can't boot installation medium (neither usb or dvd) on direkt-tek DTLAPY116-2
mageia 6: can't boot installation medium (neither usb or dvd) on direkt-tek DTLAPY116-2 =>
mageia 6: can't boot installation medium (neither usb nor dvd) on direkt-tek DTLAPY116-2
Just to be absolutely sure, could you also check the file names in the ESP (which will probably be mounted under /boot/efi in Ubuntu. What file(s) do you see in /boot/efi/EFI/BOOT?
Also, just to be absolutely clear, am I right in understanding that it stops before it gets to the initial boot menu?
Finally, please answer the questions in comment 3.
Also, please try a live DVD.
I have a lenovo here that would not start up on classical install at all.
But booting a live DVD works, so I installed from that and forgot all about it...
TPM is disabled.
There is no CSM or legacy mode.
The boot process stops before it gets to the initial boot menu.
I have not tried a live dvd, just the normal install dvd.
(In reply to jeff deifik from comment #9)
> I have not tried a live dvd, just the normal install dvd.
Can you _please_ try to boot a Live DVD?
I made a dvd of Mageia-6-LiveDVD-Plasma-x86_64-DVD.iso
I booted it, and I got a single pixel to light up.
No text, no graphics :-(
(In reply to Martin Whitaker from comment #7)
> Just to be absolutely sure, could you also check the file names in the ESP
> (which will probably be mounted under /boot/efi in Ubuntu. What file(s) do
> you see in /boot/efi/EFI/BOOT?
in /boot/efi/EFI/Boot there are 2 files,
bootx64.efi and fbx64.efi
there is no directory /boot/efi/EFI/BOOT,
in /boot/efi/EFI there is
Boot, Recovery, Microsoft, and Ubuntu
Created attachment 10272 [details]
Fedora EFI boot image
Thanks. That confirms it is a 64-bit EFI BIOS, and eliminates one possibility (there are reports that some BIOSs only work if the filenames are in uppercase).
Could you do the following test:
1. Dump the Live DVD ISO onto a USB stick and check it boots on another machine (we only really care that it gets as far as the boot menu).
2. Plug the USB stick into a running Linux system.
3. Open a terminal window and switch to being the root user by entering the command
(and entering your root user password when prompted for a password).
4. Check whether the USB stick has been automounted by entering the command
mount | grep LiveDVD
I expect you to see something like
/dev/sdb1 on /run/media/martin/Mageia-6-Plasma-LiveDVD type iso9660 ...
The base device name (excluding the final digit), dev/sdb, may be different, depending on what other drives you have in the system. In the following instructions, replace /dev/sdb with what you actually see.
5. Unmount the ISO image by entering the command
6. Mount the ESP on the USB stick by entering the command
mount /dev/sdb2 /mnt
7. Check the contents of the EFI/BOOT directory by entering the command
ls -l /mnt/EFI/BOOT
You should see
-rwxr-xr-x 1 root root 802816 Jul 11 2017 bootx64.efi*
drwxr-xr-x 2 root root 2048 Jul 11 2017 fonts/
-rwxr-xr-x 1 root root 1572 Jul 11 2017 grub.cfg*
drwxr-xr-x 3 root root 2048 Jul 11 2017 themes/
8. Download the attached file into the current working directory and uncompress it by entering the command
9. Copy it onto the USB stick by entering the command
cp bootx64.efi /mnt/EFI/BOOT
10. Unmount the ESP by entering the command
11. Check that you can still boot from the USB stick. You should only be able to get as far as the main boot menu - attempting to boot the Live system should result in an error message (because this is a Fedora boot image, and doesn't include all the necessary components for booting the Mageia system).
12. Now test if the USB stick boots on the DTLAPY116-2.
I did all of that.
I verified that the flash drive booted on a dell computer.
Using a linux system, the flash drive mounted on /dev/sdb1; there was no separate sdb2 partition. I created the flash drive using rufus 3.1
I copied the fedora bootx64.efi file to the correct directory.
Using a dell computer and the edited flash drive, I was able to see the boot menu , but the boot process did not finish as expected.
Using the DTLAPY116-2 computer and the edited flash drive, I did see a boot screen, just as I did with the dell computer. This is different than before, as I have never seen a mageia boot screen on the DTLAPY116-2 before. Of course, the boot process did not finish.
Does this mean there is some issue with the mageia bootx64.efi as supplied on the mageia 6 dvd and mageia 6 live dvd?
(In reply to jeff deifik from comment #15)
> Does this mean there is some issue with the mageia bootx64.efi as supplied
> on the mageia 6 dvd and mageia 6 live dvd?
Yes, this is likely the same problem as bug 23180. As described there, it's not just Mageia that has this problem. One of the many changes Fedora make to the grub2 bootloader fixes the problem. I'm working through the 144 patches that Fedora apply, trying to identify potential candidates. When I have something to test, I'll let you know.
Leaving this bug open for now, in case it turns out not to be the same as bug 23180.
I was able to boot ubuntu 16.04 as well as 18.04 usb sticks, so there was a way to boot successfully 2 years ago.
(In reply to jeff deifik from comment #17)
> I was able to boot ubuntu 16.04 as well as 18.04 usb sticks, so there was a
> way to boot successfully 2 years ago.
Well, in case this is a different bug, and Ubuntu have sent the fix upstream, try testing the boot image attached to bug 23180 (attachment 10245 [details]). That one's not compressed, but you will need to rename it to bootx64.efi when you copy it.
I copied the bug 23180 file to the flash drive.
Using the modified usb stick, I was able to boot the DTLAPY116-2 and see the installation options. I was able to use the up and down arrows to move around.
When I selected install, I got a black window where the install text would usually go, and no further graphics updates.
Created attachment 10275 [details]
Mageia EFI boot image with backported fixes
Please could you test this boot image for me. I'm trying to backport likely fixes to the Mageia 6 grub2 package, rather than use an unstable upstream version.
I tried the new efi boot image. I can see the 4 menu options, and move up and down to select them. I tried the live mageia and the install mageia, and the screen went blank and after a few seconds I saw the logo with the 5 circles, but booting did not progress any further.
Good, we are making progress :-)
At the boot menu, press 'e' to edit the boot command line and delete the words "splash quiet" before continuing to boot. You should then get some scrolling text in place of the logo. What are the last few lines printed out?
Note that when using the Live ISO, boot may seemingly stop when it reaches the hardware detection phase - you do need to wait a few minutes to be sure it really has got stuck.
there are a bunch of
[numbers] dracut: Scanning for all btrfs devices
[numbers] dracut: warning could not boot
dracut warning: could not boot
dracut warning: could not boot
[number] dracut warning: /dev/disk/by-label/mageia-6-plasma-livecd does not exist
dracut warning: /dev/disk/by-label/mageia-6-plasma-livecd does not exist
[number] dracut warning: /live/union does not exist
3 or 4 lines about device-mapper
to get more debug information...
dropping to debug shell
dracut: # [number] neo: [hardware error] machine check events logged
(the text is quite small as it is a 11.6 display at 1080p)
That makes me suspect you've not used the correct method for dumping the ISO onto the USB stick (and looking back, not having a /dev/sdb2 supports that). Did you select DD mode in Rufus?
I rewrote the flash drive using dd on a fedora-28 system.
It has /dev/sdb1 and /dev/sdb2.
I wrote the modified efi file to the efi/boot directory.
I verified I could boot using the flash drive on a dell laptop.
On the DTLAPY116-2 laptop, I can now boot to live mageia, using the flash drive.
Does that mean it is safe to install mageia-6 on the laptop using the flash drive?
(In reply to jeff deifik from comment #25)
> Does that mean it is safe to install mageia-6 on the laptop using the flash
The installer will run grub2-mkimage to create a new boot image for booting the installed system, and that boot image won't include the fix. I think you'll need to wait until there's an updated grub2-efi package that includes the fix.
Assigning to our grub2 maintainer. Barry, this bug can be fixed by backporting this upstream commit:
446794de8 tsc: Change default tsc calibration method to pmtimer on EFI systems
It would be good to get this included on the 6.1 ISOs.
Created attachment 10276 [details]
Patch containing upstream fix
The patch applies and builds OK to both the grub2 version in Mga6 and to Cauldron, and the patched Cauldron version currently builds OK for Mga6.
Do you suggest:
1. Update the existing grub2 in Mga6 with only this patch.
2. Update grub2 in Mga6 to the same as Cauldron (with the patch).
Using the Cauldron version would also add your translation changes.
I'd be inclined to include all the fixes from Cauldron - it looks like mga6 is going to be with us for some time yet. The only one you might need to drop is the dependency on console-setup, as I don't think that package is available in mga6.
I have pushed this to Cauldron and will also to Mga6 updates_testing.
Would you be able to write the advisory for the Mga6 update? You can explain it far better than I and also maybe have a test procedure to help validate it.
I will attach the Mga6 spec diff as a reminder for you :)
The affected packages are:
Created attachment 10277 [details]
spec diff for Mga6 update
On review, bug 22182 only occurs in Cauldron, but the fix should be harmless in mga6.
This update includes fixes for the following bugs:
- grub2 hangs during initial boot on some Intel SoC based systems (mga#23268)
- grub2-mkrescue puts files in /boot/grub instead of /boot/grub2 (mga#22918)
plus the following enhancement:
- enable translation of labels in the theme configuration file (mga#22257)
RPMs in core/updates_testing:
SRPMs in core/updates_testing:
The fix for this bug (23268) can only be tested if you have the affected hardware (in which case you wouldn't currently be able to boot Mageia on it), and is hard to test until we release the 6.1 ISOs. So for QA, we just want to check for regressions on existing systems. Note this will update your grub2 boot image, so best tested on a non-vital system. It should be very low risk though.
Bug 23268 is cosmetic. To test, run
grub2-mkrescue -o grub-rescue.iso
sudo mount grub-rescue.iso /mnt
sudo umount /mnt
(use su if you don't have sudo installed)
Before the update you should see
% ls /mnt/boot
After the update you should see
% ls /mnt/boot
The enhancement from bug 22257 is only used by my new tool for mastering Live ISOs. So again, just check for regressions - are the instructions at the bottom of the boot menu still present and correct.
Finally, to check the fix for bug 22182 has not caused any regressions, check that
both exist and are identical.
MGA6-32 MATE on IBM Thinkpad R50e
No installation issues.
All OK after reboot.
The real problem to solve with this update is on x86-64, but this demonstrates the update has no obvious ill effects on a 32-bit platform.
Works on x86_64 UEFI server, workstation and laptop
Works on x86_64 MBR system, Athlon X2, 8GB, nvidia 9800GT, Atheros wifi, Plasma.
Also works on x86_64 MBR system, HP 6550b, i3, 8GB, Intel graphics, Intel wifi, Plasma, desktop kernel.
In addition, it properly updated after the installation of kernel 4.14.56 for testing.
Also works on a Dell Inspiron 5100, P4, Radeon 7500 graphics, 1GB RAM, Atheros wifi, 32-bit Plasma install, using the vesa video driver.
As this is working on a variety of hardware with no regressions, I am giving it OKs and validating. Possible advisory in Comment 33.
An update for this issue has been pushed to the Mageia Updates repository.
(In reply to Martin Whitaker from comment #26)
> (In reply to jeff deifik from comment #25)
> > Does that mean it is safe to install mageia-6 on the laptop using the flash
> > drive?
> The installer will run grub2-mkimage to create a new boot image for booting
> the installed system, and that boot image won't include the fix. I think
> you'll need to wait until there's an updated grub2-efi package that includes
> the fix.
As grub2 is validated (and the new kernel) I have netinstall isos for test here:
if you want to try