Description of problem:
When booting the Mageia-6-dev1-i586-DVD.iso with MD5 1a2b7540062b5551d3766a479ef6ed92 from Feb 2 X is unable to start when running in a Gen 1 (bios) HyperV Virtual Machine from Windows 10 15111.
Version-Release number of selected component (if applicable):
Feb 2 Mageia-6-dev1-i586-DVD.iso 1a2b7540062b5551d3766a479ef6ed92
Happens on every boot shortly after choosing to install Mageia from Grub.
Steps to Reproduce:
Using the Safe boot options does allow for me to get past this particular error.
Created attachment 7428 [details]
Created attachment 7429 [details]
x log screenshot
Created attachment 7439 [details]
Took a little to run bug for this report, sorry about that. As this is a VM, I can't do pass-through USB, and there was no HDD being detected this had me stumped as to how to get the log file off the system. Not had to use a floppy disk in many years, glad we still have virtual floppy disks though...
Attachment 7428 is obsolete:
Attachment 7429 is obsolete:
Assigning this one to Thierry, too, since it happens in stage2
Release (media or process) =>
@Thomas: any idea? hyperv_fb did was loaded.
@David: could you try a newer cauldron?
drakx-installer-stage2, kernel, x11-driver-video-fbdevSummary:
Fatal server error in X with Hyper-V =>
drakx's Xorg fails to start with Hyper-V ("Fatal server error: addScreen/ScreenInit failed for driver 0")
Hm, I seem to remember some hyperv issues reported on lkml or xorg list a while back, I'll check if I can find it...
and I could try to start up hyperv on my Win10 work computer to reproduce
Any progress Thomas?
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
I have the same issue when installing from Mageia-6-i586-DVD.iso into Hyper-V.
Parameters of the VM:
- 32 bit
- 4 GB of Ram
- 130 GB fresh VHD
- DVD-ROM (using the above mentioned ISO)
- Host OS: Windows 10 Enterprise October 2018 with Hyper-V feature enabled.
Note to myself: we should log both Xorg.log when first driver (vesa) failed
So vesa failed to load, attachment #7429 [details] showing:
"Vesa: Ignoring device with a bound kernel driver"
Then we try to fallback to fbdev which fails with:
"(EE) Unable to find a valid framebuffer device"
I wonder if we shouldn't try to remove hyperv_fb from drakx-installer-images...
I'll try to test it under hyperv
Created attachment 10627 [details]
do not include hyperv_fb (mga#17711)
To be applied with git am -3 < 0001*