Same for me!
I have an AMD65 bit system with a 200M graphics. It gives me an XServer crash :(
From the log file:
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x6d) [0x48b99d]
1: /lib64/libc.so.6 [0x30bd430630]
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxSave64BitBAR+0x2d)
[0x2aaaabcc6b4d]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x37f)
[0x2aaaabcd1a3f]
4: /usr/bin/Xorg(InitOutput+0x6e7) [0x463707]
5: /usr/bin/Xorg(main+0x275) [0x434625]
6: /lib64/libc.so.6(__libc_start_main+0xf4) [0x30bd41dab4]
7: /usr/bin/Xorg(FontFileCompleteXLFD+0x229) [0x433ad9]
Fatal server error:
Caught signal 11. Server aborting
On 24/07/07, Jack Howarth <howarth@xxxxxxxxxxxxxxxxx> wrote:
I am not having any luck with the latest 8.39.4 fglrx rpms
released on livna yesterday. On my x86_64 fc7 machine with
a Radeon X1650 graphics card, I still see an error...
(II) Primary Device is: PCI 08:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.39.4
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.393.1
(II) ATI Proprietary Linux Driver Build Date: Jul 20 2007 13:50:49
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:8:0:1) found
(--) Chipset Supported AMD Graphics Processor (0x71C2) found
(II) AMD Video driver is running on a device belonging to a group targeted for this release
which ends with a backtrace...
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x6d) [0x48b99d]
1: /lib64/libc.so.6 [0x3ee7a30630]
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxSave64BitBAR+0x2d) [0x2aaaac0edb4d]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x37f) [0x2aaaac0f8a3f]
4: /usr/bin/Xorg(InitOutput+0x6e7) [0x463707]
5: /usr/bin/Xorg(main+0x275) [0x434625]
6: /lib64/libc.so.6(__libc_start_main+0xf4) [0x3ee7a1dab4]
7: /usr/bin/Xorg(FontFileCompleteXLFD+0x229) [0x433ad9]
Fatal server error:
Caught signal 11. Server aborting
If I am not mistaken this is the same old error we had before when fglrx couldn't cope with the change in the BusID format reported by the 1.3.0 xserver.
Is this working for anyone?
Jack
ps I don't have this issue with xorg-x11-server-Xorg-1.1.1-47.8.fc6 and
fglrx-kmod-8.36.5-3.x under fc7 so the X1650 card has been recognized in
the past by the fglrx driver.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
