unable to start graphic interface matrox mga200

[bofh_tog]

I have tried loading Mageia3, Mageia4, and installing from Mageia4 live, and am still unable to get a graphic login screen, or to start a graphic desktop from command line. The common theme of all of these is that I get the error "no screens found". I have searched to the best of my ability in the Mageia support forums for some deffinitave answer, and have not found anything that seems to match the issue, or to provide anything that has solved this issue. I have tried several machines each with similar results. I have tried Dell, HP, and SuperMicro servers and the common value I can see is the Matrox video card.

I was able to get video on Mageia4-Live, so I am sure that it can be done.

I have several files that I will link in a directory that may help others to help me. The following files and contents are from my most recent attempt.

This is a SuperMicro server.
dual E31235 Xeon processor
8G ram

http://doubleshot.pciwest.net/~mark/mageia-install-help/dmsg.txt dmesg output
http://doubleshot.pciwest.net/~mark/mageia-install-help/lsmod.txt lsmod output
http://doubleshot.pciwest.net/~mark/mageia-install-help/lspci.txt lspci ouput
http://doubleshot.pciwest.net/~mark/mageia-install-help/lsmod-grep-mga.txt lsmod piped through grep for mga

Code: Select all

lsmod | grep mga

Any help would be appreciated and I will do my best to provide any feedback that is requested.

[doktor5000]

Most part of the output provided is useless for this issue and als redundant. Hint: instead of lspci, please use lspcidrake -v as it also shows which driver is used for which device.

Please have a look at https://wiki.mageia.org/en/Mageia_4_Err ... e_CD.2FDVD and please provide the following information after booting to a text console:

Code: Select all

grep -i driver /var/log/Xorg.0.log
lspcidrake -v | grep VGA

[doktor5000]

Here are the outputs of the two commands.

Thank you for any assistance you may be able to provide.

Code: Select all

[mark@localhost ~]$ lspcidrake -v
Card:Matrox Millennium G series (single head): Matrox Electronics Systems Ltd.|MGA G200eW WPCM450 [DISPLAY_VGA] (vendor:102b device:0532 subv:15d9 subd:0624) (rev: 0a)
e1000e          : Intel Corporation|82574L Gigabit Network Connection [NETWORK_ETHERNET] (vendor:8086 device:10d3 subv:15d9 subd:0000)
i2c_i801        : Intel Corporation|6 Series/C200 Series Chipset Family SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:1c22) (rev: 05)
unknown         : Intel Corporation|6 Series/C200 Series Chipset Family SATA AHCI Controller [STORAGE_SATA] (vendor:8086 device:1c02) (rev: 05)
lpc_ich         : Intel Corporation|C202 Chipset Family LPC Controller [BRIDGE_ISA] (vendor:8086 device:1c52) (rev: 05)
unknown         : Intel Corporation|82801 PCI Bridge [BRIDGE_PCI] (vendor:8086 device:244e) (rev: a5)
ehci_pci        : Intel Corporation|6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [SERIAL_USB] (vendor:8086 device:1c26) (rev: 05)
shpchp          : Intel Corporation|6 Series/C200 Series Chipset Family PCI Express Root Port 5 [BRIDGE_PCI] (vendor:8086 device:1c18) (rev: b5)
shpchp          : Intel Corporation|6 Series/C200 Series Chipset Family PCI Express Root Port 1 [BRIDGE_PCI] (vendor:8086 device:1c10) (rev: b5)
ehci_pci        : Intel Corporation|6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [SERIAL_USB] (vendor:8086 device:1c2d) (rev: 05)
e1000e          : Intel Corporation|82579LM Gigabit Network Connection [NETWORK_ETHERNET] (vendor:8086 device:1502 subv:15d9 subd:1502) (rev: 05)
unknown         : Intel Corporation|Xeon E3-1200 Processor Family DRAM Controller [BRIDGE_HOST] (vendor:8086 device:0108) (rev: 09)
hub             : Linux 3.12.25-desktop-3.mga4 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
usbhid          : Microsoft|Microsoft Trackball Optical® [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:045e device:0023)
usbhid          : Logitech|Logitech USB Keyboard [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:046d device:c309)
hub             : Linux 3.12.25-desktop-3.mga4 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
usbhid          : Winbond Electronics Corp|Hermon USB hidmouse Device [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:0557 device:2221)
hid_generic     : Logitech Logitech USB Keyboard
hid_generic     : Logitech Logitech USB Keyboard
hid_generic     : Microsoft Microsoft Trackball Optical®
hid_generic     : Winbond Electronics Corp Hermon USB hidmouse Device
hid_generic     : Winbond Electronics Corp Hermon USB hidmouse Device

Code: Select all

[mark@localhost ~]$ grep -i driver /var/log/Xorg.0.log
[   126.507]    X.Org Video Driver: 14.1
[   126.507]    X.Org XInput driver : 19.1
[   127.523] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[   127.523]    ABI class: X.Org Video Driver, version 14.1
[   127.556] (II) Loading /usr/lib64/xorg/modules/drivers/mga_drv.so
[   127.556]    Module class: X.Org Video Driver
[   127.556]    ABI class: X.Org Video Driver, version 14.1
[   127.556] (II) v4l driver for Video4Linux
[   127.556] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
[   127.556] (EE) mga: This driver cannot operate until it has been unloaded.

[doktor5000]

Please next time use code tags as explained in ftp://ftp5.gwdg.de/pub/linux/mandriva/m ... e_tags.ogv

Also, did you check the instructions on the wiki page I've linked to above? That should at least allow you to boot, using one of the alternate drivers (e.g. vesa). Would be good to know if this works.

[bofh_tog]

I have tried using the vesa module to boot with similar results indicating no screens available. I have also tried the failsafe mode and still experience the same result. the display stops to allow either continue or enter recovery mode. I enter the CTRL-D to continue and the system display checking for new hardware with no continuation. I can switch to tty2 and log in as a user or as root, and get a command prompt.

I may have not explained myself completely above, but when booting directly from the live dvd media I do get a graphic desktop.

[doktor5000]

I may have not explained myself completely above, but when booting directly from the live dvd media I do get a graphic desktop.

In that case, in live mode please show the output of

Code: Select all

grep -i driver /var/log/Xorg.0.log
lspcidrake -v | grep VGA

or maybe better attach the complete /var/log/Xorg.0.log

[bofh_tog]

I apologize for the delay. I had a son in the hospital..

Here are the results of the commands from the live environment.

Code: Select all

# grep -i driver /var/log/Xorg.0.log
[   164.993]    X.Org Video Driver: 14.1
[   164.993]    X.Org XInput driver : 19.1
[   164.996] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[   166.186]    ABI class: X.Org Video Driver, version 14.1
[   167.372] (II) Loading /usr/lib64/xorg/modules/drivers/mga_drv.so
[   169.224]    Module class: X.Org Video Driver
[   169.224]    ABI class: X.Org Video Driver, version 14.1
[   169.224] (II) v4l driver for Video4Linux
[   169.224] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
[   169.240]    ABI class: X.Org Video Driver, version 14.1
[   169.623] (II) MGA(0): Not using driver mode "1920x1080" (width too large for virtual size)
[   169.623] (II) MGA(0): Not using driver mode "1280x1024" (mode requires too much memory bandwidth)
[   169.623] (II) MGA(0): Not using driver mode "1920x1080" (width too large for virtual size)
[   169.623] (II) MGA(0): Not using driver mode "1680x1050" (width too large for virtual size)
[   169.623] (II) MGA(0): Not using driver mode "1600x1200" (width too large for virtual size)
[   169.623] (II) MGA(0): Not using driver mode "1440x900" (width too large for virtual size)
[   169.623] (II) MGA(0): Not using driver mode "1400x1050" (width too large for virtual size)
[   169.623] (**) MGA(0):  Driver mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
[   169.623] (**) MGA(0):  Driver mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
[   169.623] (**) MGA(0):  Driver mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
[   169.623] (**) MGA(0):  Driver mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
[   169.623] (**) MGA(0):  Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
[   169.623] (**) MGA(0):  Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[   169.623] (**) MGA(0):  Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[   169.623] (**) MGA(0):  Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[   169.623] (**) MGA(0):  Driver mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
[   169.623] (**) MGA(0):  Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[   169.623] (**) MGA(0):  Driver mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
[   169.623] (**) MGA(0):  Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[   169.623] (**) MGA(0):  Driver mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
[   169.623] (**) MGA(0):  Driver mode "640x480": 30.2 MHz, 35.0 kHz, 66.7 Hz
[   169.623] (**) MGA(0):  Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[   169.623] (**) MGA(0):  Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
[   184.446]    Module class: X.Org XInput Driver
[   184.446]    ABI class: X.Org XInput driver, version 19.1
[   184.446] (II) Using input driver 'evdev' for 'Power Button'
[   184.460] (II) Using input driver 'evdev' for 'Power Button'
[   184.460] (II) Using input driver 'evdev' for 'Winbond Electronics Corp Hermon USB hidmouse Device'
[   184.460] (II) No input driver specified, ignoring this device.
[   184.460] (II) No input driver specified, ignoring this device.
[   184.461] (II) Using input driver 'evdev' for 'Winbond Electronics Corp Hermon USB hidmouse Device'
[   184.461] (II) Using input driver 'evdev' for 'Microsoft Microsoft Trackball Optical®'
[   184.461] (II) No input driver specified, ignoring this device.
[   184.461] (II) Using input driver 'evdev' for 'Logitech Logitech USB Keyboard'
[   184.462] (II) Using input driver 'evdev' for 'Logitech Logitech USB Keyboard'
[   184.462] (II) No input driver specified, ignoring this device.
[   184.462] (II) No input driver specified, ignoring this device.
[  1110.684] (II) Using input driver 'evdev' for 'Microsoft Microsoft Trackball Optical®'
[  1110.684] (II) No input driver specified, ignoring this device.
[  1110.685] (II) No input driver specified, ignoring this device.
[  1110.702] (II) Using input driver 'evdev' for 'Winbond Electronics Corp Hermon USB hidmouse Device'
[  1110.702] (II) No input driver specified, ignoring this device.
[  1110.707] (II) Using input driver 'evdev' for 'Power Button'
[  1110.707] (II) No input driver specified, ignoring this device.
[  1110.707] (II) No input driver specified, ignoring this device.
[  1110.712] (II) Using input driver 'evdev' for 'Logitech Logitech USB Keyboard'
[  1110.717] (II) Using input driver 'evdev' for 'Power Button'
[  1110.722] (II) Using input driver 'evdev' for 'Winbond Electronics Corp Hermon USB hidmouse Device'
[  1110.727] (II) Using input driver 'evdev' for 'Logitech Logitech USB Keyboard'


Code: Select all

# lspcidrake -v | grep VGA
Card:Matrox Millennium G series (single head): Matrox Electronics Systems Ltd.|MGA G200eW WPCM450 [DISPLAY_VGA] (vendor:102b device:0532 subv:15d9 subd:0624) (rev: 0a)


[doktor5000]

Seems to be the same driver, working in live mode, but not in installed system. Then please report that as a bug, after searching if it hasn't been reported yet already: https://wiki.mageia.org/en/How_to_report_a_bug_properly

Or before that, have a look at https://bugs.mageia.org/show_bug.cgi?id=13312 - maybe you just need to install x11-driver-video-modesetting package ?

[bofh_tog]

I tried installing the x11-driver-video-modesetting package, and still have the same issue.

I did find a bug listed https://bugs.mageia.org/show_bug.cgi?id=13098 that also addresses a similar issue. I have had the issue with both the last 2 major releases of mageia, so I am unsure if it is the same at this time.

I will continue to research and file a bug if this is in fact different.

Thank you for your help.

[doktor5000]

Also check the linked SuSe bug: https://bugzilla.novell.com/show_bug.cgi?id=823658
Maybe you can paste here the output as root of lsmod in live mode and from installed system