ATi X300SE - zaphod stopped working

Dave Airlie airlied at gmail.com
Mon May 12 02:16:54 PDT 2008


On Mon, May 12, 2008 at 7:14 PM, Jan Kasprzak <kas at fi.muni.cz> wrote:
> Dave Airlie wrote:
>  : On Mon, May 12, 2008 at 6:34 PM, Jan Kasprzak <kas at fi.muni.cz> wrote:
>  : >  I have upgraded my system from Fedora 8 to Fedora 9 (pre release), and
>
> : >  my dual-screen (Zaphod) X does not work anymore: when the dual-screen
>  : >  layout is in use, the X server fails to start with
>  : >
>  : >  (EE) RADEON(1): Unable to map MMIO aperture. Invalid argument (22)
>  :
>  : You need to grab the F9 ati driver from updates-testing if its available yet.
>  :
>  : or there is a build in koji
>  :
>  : http://koji.fedoraproject.org/packages/xorg-x11-drv-ati/6.8.0/15.fc9/
>
>         I have tried this one (thanks!) - it is better, but still not
>  fully working: the X server starts with two screens, but the second
>  one has its refresh times out of range of my monitor (it displays
>  "74.5kHz/60Hz out of range"). Moreover, when I try to move the cursor
>  to the secondary head, it locks up (the cursor disappears from the primary
>  head and cannot be moved back). When the last X client disconnects,
>  the server crashes with the following backtrace:
>
>  Backtrace:
>  0: X(xf86SigHandler+0x65) [0x479fe5]
>  1: /lib64/libc.so.6 [0x2b16c3f1b2a0]
>  2: X [0x4a6485]
>  3: X [0x4a7066]
>  4: X(xf86_reload_cursors+0x10c) [0x4a6aec]
>  5: X(xf86CrtcSetMode+0x3fd) [0x4a420d]
>  6: X(xf86SetDesiredModes+0x1bd) [0x4a469d]
>  7: /usr/lib64/xorg/modules/drivers//radeon_drv.so(RADEONScreenInit+0x18f7) [0x2b16c65fd1d7]
>  8: X(AddScreen+0x1c9) [0x42bf09]
>  9: X(InitOutput+0x216) [0x4623c6]
>  10: X(main+0x286) [0x42c6a6]
>  11: /lib64/libc.so.6(__libc_start_main+0xfa) [0x2b16c3f0732a]
>  12: X(FontFileCompleteXLFD+0x279) [0x42bc59]
>
>  Fatal server error:
>  Caught signal 11.  Server aborting
>
>         I can provide more debugging info if requested.

Wierd, I did actually test it for once on one of my cards.

can you open a bug on bugs.freedesktop.org or bugzilla.redhat.com so I
can track it?

attach xorg.conf and /var/log/Xorg.0.log.

Dave.



More information about the xorg mailing list