FC2T2 Initial Things - Update

Dan Goodes fedora-list at planetmirror.com
Thu Apr 1 01:37:10 UTC 2004


Further to my previous email regarding issues with the radeon driver:

1) XF86Config has the "radeon" driver defined, so it's definitely that
driver that has the issue

2) It appears to only occur when something tries to run 3D stuff.

3) Here's an excerpt from my XFree86.0.log file, from the point in time
when the problem occurs:

(II) RADEON(0): Wrote: rd=13, fd=22, pd=4
(WW) Open APM failed (/dev/apm_bios) (No such device)
(==) RADEON(0): Write-combining range (0xe0000000,0x4000000)
(WW) RADEON(0): Direct rendering not yet supported on IGP320/330/340/350,
7000, 9000 integrated chips
(II) RADEON(0): Memory manager initialized to (0,0) (1408,8191)
(II) RADEON(0): Reserved area from (0,1050) to (1408,1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 7139
(II) RADEON(0): Acceleration enabled
(II) RADEON(0): Using hardware cursor (scanline 1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 7136
(**) RADEON(0): DPMS enabled
(II) RADEON(0): Direct rendering disabled
(==) RandR enabled
(II) Mouse0: ps2EnableDataReporting: succeeded
AUDIT: Thu Apr  1 11:23:35 2004: 1698 X: client 5 rejected from local host

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


When reporting a problem related to a server crash, please
send the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xorg at freedesktop.org.

(II) RADEON(0): Wrote: rd=13, fd=22, pd=4

--snip--

4) Also, from an SSH session, it seems impossible to use "telinit 3" to
get out of X windows (and thus restart X). Although the machine hasn't
locked up, it appears that it can't be brought back into X without a
restart.

-Dan





More information about the fedora-test-list mailing list