[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: r128 driver problem with FC5



On Thu, 15 Jun 2006, Nigel Henry wrote:

FC5 installs ok, but to start X, I have to change the r128 driver to vesa
in /etc/X11/xorg.conf.

I had similar problems with FC4 and the Cyberblade i1 card's Trident driver,
but after doing all the updates, post install, I was able to change back to
the Trident driver, and X started ok.

I don't know whether this is a problem due to system packages needing to be
updated or what.

I can't say that I like messing with xorg.conf. More often than not I find
myself in text mode, and have to have a quick nano session to put things back
as they were to get X to start.

This is the output from /var/log/Xorg.setup.log when trying to start X with
the Rage128's r128 driver.

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.9-22.18.bz155725.ELsmp i686Red Hat, Inc.
Current Operating System: Linux localhost 2.6.16-1.2080.13.rrt.rhfc5.ccrma #1
PREEMPT Sat Apr 22 19:05:27 EDT 2006 i686
Build Date: 02 May 2006
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/dev/null", Time: Sat May 27 00:12:42 2006
(++) Using config file: "/tmp/tmp5Ed8TDxorg.config"
(WW) ****INVALID IO ALLOCATION**** b: 0x9000 e: 0x90ff correcting
Requesting insufficient memory window!: start: 0x9000 end: 0x90ff size
0xf0120100
Requesting insufficient memory window!: start: 0x9400 end: 0x94ff size
0xf0120100
Requesting insufficient memory window!: start: 0x9800 end: 0x98ff size
0xf0120100
Requesting insufficient memory window!: start: 0x9c00 end: 0x9cff size
0xf0120100
(EE) Cannot find a replacement memory range

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

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x87) [0x80b86c7]
1: [0x472420]
2: /usr/lib/xorg/modules/drivers/r128_drv.so(R128FreeScreen+0x2b) [0x13ea9b]
3: /usr/bin/Xorg(xf86DeleteScreen+0x5e) [0x80c50ee]
4: /usr/bin/Xorg(InitOutput+0x9e4) [0x80a2364]
5: /usr/bin/Xorg(main+0x276) [0x806ffc6]
6: /lib/libc.so.6(__libc_start_main+0xdc) [0x4a5724]
7: /usr/bin/Xorg(FontFileCompleteXLFD+0xb1) [0x806f511]

Fatal server error:
Caught signal 11.  Server aborting

Any specific help would be really appreciated.

You need to report this problem to X.Org, not here, an XFree86 forum.

Marc.

+----------------------------------+-----------------------------------+
|  Marc Aurele La France           |  work:   1-780-492-9310           |
|  Academic Information and        |  fax:    1-780-492-1729           |
|    Communications Technologies   |  email:  tsi@xxxxxxxxxxx          |
|  352 General Services Building   +-----------------------------------+
|  University of Alberta           |                                   |
|  Edmonton, Alberta               |     Standard disclaimers apply    |
|  T6G 2H1                         |                                   |
|  CANADA                          |                                   |
+----------------------------------+-----------------------------------+
XFree86 developer and VP.  ATI driver and X server internals.
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86

[X Forum]     [Xorg]     [XFree86]     [XFree86 Newbie]     [IETF Announce]     [Security]     [Fontconfig]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Video for Linux]     [Linux RAID]     [Linux Kernel]

Powered by Linux