Description of problem: After upgrading to the F18 version of xorg-x11-drv-mga, the X server fails with this error message: [ 20.734] (II) LoadModule: "mga" [ 20.734] (II) Loading /usr/lib64/xorg/modules/drivers/mga_drv.so [ 20.735] (EE) Failed to load /usr/lib64/xorg/modules/drivers/mga_drv.so: /usr/lib64/xorg/modules/drivers/mga_drv.so: undefined symbol: MGAStormSync Version-Release number of selected component (if applicable): xorg-x11-drv-mga-1.6.1-2.fc18.x86_64 Additional info: This was first reported in bug 861401. That bug was closed "errata" pointing to version 1.6.2-1.fc18 of the package. But that build has apparently never been released to the Fedora 18 repositories. I'm not clear if this was an oversight, or there is some problem with the build. I found the package in koji, downloaded, and tried it. At first sight, it seems to work, but I haven't used it much yet, so it is to early to say for sure. In any case, the version of xorg-x11-drv-mga in the F18 beta isn't working.
I can confirm this bug kills X when upgrading from Fedora 17 to 18.
Created attachment 683785 [details] Correctly functioning package, built on pristine Fedora 18
Created attachment 683786 [details] Correctly functioning package, built on pristine Fedora 18
Ignore attachment #1 [details]. Attachment #2 [details] contains the correct RPM, built from the Fedora testing source RPM package. rpm2cpio < <SOURCE RPM> > <CPIO> cpio --extract < <CPIO> cp <SOURCE FILES> ~/rpmbuild/SOURCES rpmbuild -bb <SPEC> Then install the binary RPM. The same procedure has worked for over a decade.
I have run into the same issue upgrading from Fedora 17 to 18. Will try John's attachment...
Apropos comment 4, if you want to rebuild an SRPM, all you have to do is rpmbuild --rebuild <SOURCE RPM> (Attachment 683786 [details] isn't a source RPM though, but a binary 32 bit RPM.)
If you have the strange configuration of a Matrox card in a 64-bit system, you can build it for yourself. The source RPM I used is at: ftp://mirrors.kernel.org/fedora-enchilada/linux/development/rawhide/source/SRPMS/x/xorg-x11-drv-mga-1.6.2-1.fc19.src.rpm This needs to go straight into Fedora 18 errata. This change is highly uncontroversial.
Created attachment 730443 [details] Xorg log in fc18 Xorg log on pure fc18: xorg-x11-drv-mga-1.6.1-2.fc18.x86_64
Created attachment 730444 [details] lspci output of video card This is the Matrox video card
Created attachment 730466 [details] Xorg log when tried version build from fc19 SRC (version: 1.6.2-5) Log when build from fc19 SRC package version 1.6.2-5
I can confirm this bug with my 64-bit system and Matrox G550 video card. Only VESA driver works. Unfortunately version build from latest fc19 source package (xorg-x11-drv-mga-1.6.2-5.fc19.src.rpm) did not help. lspic output & Xorg Log information attached.
The driver is probably totally broken on 64-bit systems then. Why would you use such an ancient piece of hardware on a new 64-bit system? Invest $50 and get something modern that is much faster. I only got this configuration working because that entire system (video card included) is 10 years old.
Off topic, but this is not a new system, probably one of the earliest 64-bit system. I needed simply cheap linux-PC for one project. I bought old machine for only 10 euros without video card & hard disk. I had both hard disk & this G550 in my storage (so they was free :) ). So I really do not invest extra $50 for this project.... Unfortunately this G550 works now only by VESA driver because of this bug :(
I think your bug is distinct. The bug I addressed fixed a problem with a missing symbol: [ 48.312] (EE) Failed to load /usr/lib64/xorg/modules/drivers/mga_drv.so: /usr/lib64/xorg/modules/drivers/mga_drv.so: undefined symbol: MGAStormSync This appears to be your issue: [ 31.830] (EE) MGA(0): Unable to map BAR 0. No such file or directory (2) Seems like a more fundamental problem with the server. I have no idea what BAR 0 means, but it doesn't sound fun. The cause could be that the driver is not 64 bit clean. I don't think many people use this hardware anymore. It was very common in the Netherlands when I was working there around 2000-2002, over ten years ago. I'm sure it was also common in Finland at the time.
Here's the patch. Since you're building the package yourself, drop it in: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/292214
Actually I have never build package from source package before this. I could try it by modifying source and building new binary version from it. It would be very educational if I had more time right now, and also I'm not sure what is the correct patch for this "Unable to map BAR" problem.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'm not currently using that hardware. (I still have it around in case it would be of use, but that isn't very likely.) So while I suspect this is still a problem, I can't check for sure. And thus, I won't change the version. If anyone else can check it with F20, and finds it to still be broken, feel free to update the version field.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.