Bug 13312 - Kernel module prevents X server to start on Matrox g200er2 video card (IBM System X) -- Mageia 4
Summary: Kernel module prevents X server to start on Matrox g200er2 video card (IBM Sy...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-05-03 08:17 CEST by Anil Vohra
Modified: 2015-10-27 06:58 CET (History)
3 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description Anil Vohra 2014-05-03 08:17:26 CEST
Description of problem:

I rcently installed Mageia 4 x64 bit on IBM Sytem X machine with builtin Matrox Card of g200R2 type. Installation is fine and through the normal GUI. But on reboot, the display freezes and remains at 45 degrees slant even on the text console. Connection via network didnot work as firewall was on and, above all, sshd was not installed in the default install (which should be done, in my opinion, may be kept as a stopped service). 

After some reinstalls, I finally connected to the system via ssh and tried to resolve the issue. The matrox card uses mgag200 kernel module. And perhaps X-server does not like it and complains -- unable to load driver as the device has already been taken by a kernel module ( in this case mgag200).

Blacklisting the module in modprobe.d didnot help.

Any solution to this? Please help. 



Further, I downgraded to Mageia 3. The console was OK but X-windows did not start and same error appeared. However, in this case blaklisting the mgag200 module in modprobe.d solved the problem and X-srver started but at a much lower resolution, so a price had to be paid for this!


How reproducible: Always



Reproducible: 

Steps to Reproduce:
Anil Vohra 2014-05-03 08:21:08 CEST

CC: (none) => vohra64

Anil Vohra 2014-05-05 18:11:09 CEST

CC: vohra64 => (none)

Anil Vohra 2014-05-05 18:11:23 CEST

CC: (none) => vohra64

Manuel Hiebel 2014-05-08 20:10:43 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => tmb

Comment 1 Ethan Merritt 2014-05-14 01:51:35 CEST
Possibly a duplicate of Bug 12792

If so, the solution may be to install the package
x11-driver-video-modesetting

CC: (none) => eamerritt

Comment 2 Felix Miata 2014-05-20 01:06:22 CEST
Any guidance to be had from https://bugzilla.novell.com/show_bug.cgi?id=823658 possibly the inverse problem?

CC: (none) => mrmazda

Comment 3 Samuel Verschelde 2015-09-21 13:21:25 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Marja Van Waes 2015-10-27 06:58:25 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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


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