r128 driver problem with FC5

Tue Jun 20 17:25:11 PDT 2006

Am Mittwoch, den 21.06.2006, 01:38 +0200 schrieb Nigel Henry:
> On Wednesday 21 June 2006 00:48, Felix Kühling wrote:
> > Hi Nigel,
> >
> > I'd be interested in seeing the full server log and the output of lspci
> > -v. This looks like it might be bug #6377, which is fixed in Xorg 7.1.
> > But without seeing the full log that's just a wild guess.
> >
> > See Adam's comments about how to get the complete log.
> >
> > Regards,
> >   Felix
> 
> Hi Felix. Had a few problems getting ssh to work as I´ve never used it before, 
> only Gftp, and fish, and still can get the backtrace. Anyway here is the log.
> 
> 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: "/var/log/Xorg.0.log", Time: Wed Jun 21 00:53:46 2006
> (==) Using config file: "/etc/X11/xorg.conf"
[snip]
> (II) Active PCI resource ranges:
> 	[0] -1	0	0xf0000400 - 0xf00004ff (0x100) MX[B]
> 	[1] -1	0	0xf0000000 - 0xf000007f (0x80) MX[B]
> 	[2] -1	0	0xf4000000 - 0xf3ffffff (0x0) MX[B]O
> 	[3] -1	0	0xf0100000 - 0xf0103fff (0x4000) MX[B](B)
> 	[4] -1	0	0xf8000000 - 0xfbffffff (0x4000000) MX[B](B)
> 	[5] -1	0	0x000010f0 - 0x000010ff (0x10) IX[B]
> 	[6] -1	0	0x00001400 - 0x00001403 (0x4) IX[B]
> 	[7] -1	0	0x00001408 - 0x2000140f (0x20000008) IX[B]
> 	[8] -1	0	0x00001404 - 0x00001407 (0x4) IX[B]

Yep, this looks just like bug #6377. IO address ranges with less than
16-bytes alignment. And X getting confused about them. The second last
range above is obviously illegal and the result of this bug. Note that
this problem is not necessarily triggered by the graphics card but can
be triggered by any other PCI device in your system that has IO address
ranges with small alignment.

[snip]

> And lspci
> 
> 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RL/VR AGP 
> (prog-if 00 [VGA])
>         Subsystem: ATI Technologies Inc Xpert 99/Xpert 2000
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping+ SERR- FastB2B+
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 66 (2000ns min), Cache Line Size 08
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
>         Region 1: I/O ports at 9000 [size=256]
>         Region 2: Memory at f0100000 (32-bit, non-prefetchable) [size=16K]
>         [virtual] Expansion ROM at f0120000 [disabled] [size=128K]
>         Capabilities: [50] AGP version 2.0
>                 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 
> 64bit- FW- AGP3- Rate=x1,x2
>                 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- 
> Rate=<none>
>         Capabilities: [5c] Power Management version 1
>                 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA 
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 
> Thanks for any help. Nigel.

As I said, the problem is probably triggered by a different PCI device.
lspci can help you find out which PCI device that is. It could be for
example an IDE or SATA controller. If you don't need it you may be able
to disable it in your BIOS setup to work around the problem.

Someone on this list mentioned experimental Xorg 7.1 packages for
Fedora. (or was that just a rumour?) They would most likely include a
fix.

Regards,
  Felix

> 
> 
> 
> 
> >
> > Am Freitag, den 16.06.2006, 18:50 +0200 schrieb Nigel Henry:
> > > Hi. I've been through all the FAQ's, and can't find anything relating to
> > > my problem. The graphics are ok using the vesa driver, but it's a real no
> > > go with DVD's. FC1,2,and 3 on the same machine, have no problem with the
> > > r128 driver.
> > >
> > > The query below is the one I accidentally posted to the Xfree86 mailing
> > > list, which didn't go down too well.
> > >
> > > 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.
> > >
> > > Nigel.
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > xorg mailing list
> > > xorg at lists.freedesktop.org
> > > http://lists.freedesktop.org/mailman/listinfo/xorg
> 
-- 
| Felix Kühling <fxkuehl at gmx.de>                     http://fxk.de.vu |
| PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3  B152 151C 5CC1 D888 E595 |