Bug 3958

Created attachment 3222 [details] [review]
use ASM_API

*** This bug has been marked as a duplicate of 2976 ***

Created attachment 3223 [details] [review]
updated patch for ASM_API

If that doesn't resolve things for you, please re-open.

(In reply to comment #2)
> 
> *** This bug has been marked as a duplicate of 2976 ***

I doubt. The symptom is different. I don't see a white screen. I see a garbled
screen and I can recognise the icons and images and some of the text. I have
tried to swap libvgahw.a as suggested by Mike Harris with the same module from
FC3 to no avail.

(In reply to comment #4)
> If that doesn't resolve things for you, please re-open.

I've chosen to reopen, see my comment #6. I am not convinced it is a duplicate.

Yeah, i've been pretty hasty with a conclusion there. I'm blaming cafeine :p

What did digging for mga problems turn up? Have you tried X.org CVS or a recent
snapshot?

(In reply to comment #7)
> Yeah, i've been pretty hasty with a conclusion there. I'm blaming cafeine :p
> 
> What did digging for mga problems turn up? Have you tried X.org CVS or a recent
> snapshot?

I didn't find anything similar to my problem when searching for mga.
I haven't tried X.org CVS or recent snapshots. I am relatively new to this and
since I cannot run FC4 I don't know how to add changes to it. Please advice.

I have made another try with the monitor connected to the DVI port and here the
symptom is different. Here it hangs with a black screen.

There is a chance that this still is a gcc4 issue, a problem similar to what is
occuring in vgahw.

If replacing vgahw with a gcc 3 compiled version is possible, then maybe a gcc3
compiled mga driver might be a good way forward for testing. Grab the FC3 X (is
this 6.8.2 too?) and take out the mga driver, move the fc4 driver out of the
way, and run the fc3 one.

(In reply to comment #10)
> There is a chance that this still is a gcc4 issue, a problem similar to what is
> occuring in vgahw.
> 
> If replacing vgahw with a gcc 3 compiled version is possible, then maybe a gcc3
> compiled mga driver might be a good way forward for testing. Grab the FC3 X (is
> this 6.8.2 too?) and take out the mga driver, move the fc4 driver out of the
> way, and run the fc3 one.

OK. I'll test it, but since I am leaving early today it may not be before
Monday. xorg for FC3 is 6.8.1

OK. Ran the FC3 mga driver. Suppose it was mga_drv.o. It didn't help a bit, in
fact X wouldn't load so it switched to text mode.

Second thing I tried was taken out of bug #161242. Some have there reported
problems similar to mine and a new set of modules were compiled for xorg with a
fixed gcc. From that I picked libvgahw.a and mga_drv.o and copied them to my FC4
system. But that didn't help either. Would you like to see a photo of it?

This is the pci config space access problem.
https://bugs.freedesktop.org/show_bug.cgi?id=2880
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163331

Fixed in fedora rawhide: 6.8.2-45

(In reply to comment #13)
> This is the pci config space access problem.
> https://bugs.freedesktop.org/show_bug.cgi?id=2880
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163331
> 
> Fixed in fedora rawhide: 6.8.2-45

Thanks, I hope this is true. I suppose 6.8.2-45 refers to Xorg, but where do I
find this "rawhide"?

Sorry, it use to be called "rawhide" but it is now called "development".

http://download.fedora.redhat.com/pub/fedora/linux/core/development/
(You can also ftp to the same adress)

You will also need to update glibc.

(In reply to comment #15)
> Sorry, it use to be called "rawhide" but it is now called "development".
> 
> http://download.fedora.redhat.com/pub/fedora/linux/core/development/
> (You can also ftp to the same adress)
> 
> You will also need to update glibc.

Thanks. How many of the xorg-x11 and glibc rpms should I install?

(In reply to comment #16)
> (In reply to comment #15)
> > Sorry, it use to be called "rawhide" but it is now called "development".
> > 
> > http://download.fedora.redhat.com/pub/fedora/linux/core/development/
> > (You can also ftp to the same adress)
> > 
> > You will also need to update glibc.
> 
> Thanks. How many of the xorg-x11 and glibc rpms should I install?


If you're using FC4 you should be able to use yum to upgrade the required RPMs:

  yum --enablerepo=development update xorg-x11

We also do plan to release an FC4 update with this fix shortly, though.

(closing bug)