Bug 17711 - drakx's Xorg fails to start with Hyper-V ("Fatal server error: addScreen/ScreenInit failed for driver 0")
Summary: drakx's Xorg fails to start with Hyper-V ("Fatal server error: addScreen/Scre...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL: https://bugs.debian.org/cgi-bin/bugre...
Depends on:
Reported: 2016-02-08 21:19 CET by David Remy
Modified: 2018-12-30 12:17 CET (History)
4 users (show)

See Also:
Source RPM: drakx-installer-stage2, kernel, x11-driver-video-fbdev
Status comment:

boot error (70.88 KB, image/png)
2016-02-08 21:23 CET, David Remy
x log screenshot (74.56 KB, image/png)
2016-02-08 21:24 CET, David Remy
bug log (121.37 KB, text/plain)
2016-02-09 18:57 CET, David Remy
do not include hyperv_fb (mga#17711) (1.13 KB, patch)
2018-12-30 12:17 CET, Thierry Vignaud
Details | Diff

Description David Remy 2016-02-08 21:19:35 CET
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.

Screenshots attached.

Version-Release number of selected component (if applicable):
Feb 2 Mageia-6-dev1-i586-DVD.iso 1a2b7540062b5551d3766a479ef6ed92 

How reproducible:
Happens on every boot shortly after choosing to install Mageia from Grub.


Steps to Reproduce:
Comment 1 David Remy 2016-02-08 21:22:25 CET
Using the Safe boot options does allow for me to get past this particular error.
Comment 2 David Remy 2016-02-08 21:23:36 CET
Created attachment 7428 [details]
boot error
Comment 3 David Remy 2016-02-08 21:24:04 CET
Created attachment 7429 [details]
x log screenshot
Comment 4 David Remy 2016-02-09 18:57:27 CET
Created attachment 7439 [details]
bug log

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: 0 => 1
Attachment 7429 is obsolete: 0 => 1

Comment 5 Marja Van Waes 2016-02-13 22:37:53 CET
Assigning this one to Thierry, too, since it happens in stage2

Component: Release (media or process) => Installer
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakx-installer-stage2
CC: sysadmin-bugs => marja11

Comment 6 Thierry Vignaud 2016-06-15 12:06:53 CEST
@Thomas: any idea? hyperv_fb did was loaded.

@David: could you try a newer cauldron?

Assignee: thierry.vignaud => tmb
Source RPM: drakx-installer-stage2 => drakx-installer-stage2, kernel, x11-driver-video-fbdev
Summary: 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")

Comment 7 Thomas Backlund 2016-06-15 12:13:49 CEST
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
Comment 8 Thierry Vignaud 2016-07-08 04:22:18 CEST
Any progress Thomas?

CC: (none) => thierry.vignaud

Comment 9 Marja Van Waes 2016-08-26 11:42:46 CEST
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.

Assignee: tmb => kernel

Comment 10 Andriy Klyuchevskyy 2018-12-28 16:50:33 CET
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.

CC: (none) => akluch

Comment 11 Thierry Vignaud 2018-12-29 18:09:58 CET
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"

URL: (none) => https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861066

Comment 12 Thierry Vignaud 2018-12-29 18:18:17 CET
I wonder if we shouldn't try to remove hyperv_fb from drakx-installer-images...
WDYT Thomas?
Comment 13 Thomas Backlund 2018-12-29 22:50:38 CET

I'll try to test it under hyperv

CC: (none) => tmb

Comment 14 Thierry Vignaud 2018-12-30 12:17:39 CET
Created attachment 10627 [details]
do not include hyperv_fb (mga#17711)

To be applied with git am -3 < 0001*

Note You need to log in before you can comment on or make changes to this bug.