From: Albert B. <al...@ob...> - 2000-12-27 03:30:58
|
I'm having a problem with DRI and XFree86 4.0.2. XFree86 reports the error: "(EE) R128(0): R128DRIScreenInit failed (DRM version = 1.0.0, expected 2.1.x). Disabling DRI." It worked fine with XFree86 4.0.1 and the r128 DRM from kernel 2.2.18. I have also tried using the r128 module from 2.4.0 test 13 with the same results. Any help would be greatly appreciated. I have an ATI Rage Xpert 99 AGP. Albert Baldassarre |
From: Michel <mic...@ii...> - 2000-12-27 10:54:54
|
Albert Baldassarre wrote: >=20 > I'm having a problem with DRI and XFree86 4.0.2. XFree86 reports the > error: "(EE) R128(0): R128DRIScreenInit failed (DRM version =3D 1.0.0, > expected 2.1.x). Disabling DRI." It worked fine with XFree86 4.0.1 and > the r128 DRM from kernel 2.2.18. I have also tried using the r128 modul= e > from 2.4.0 test 13 with the same results. Any help would be greatly > appreciated. I have an ATI Rage Xpert 99 AGP. You need the DRM from XFree86 4.0.2. You most probably have to build it yourself, you can get the source from the XFree86 or DRI CVS. Michel --=20 Earthling Michel D=E4nzer (MrCooper) \ CS student and free software ent= husiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Pr= oject |
From: Jeff E. <je...@us...> - 2000-12-27 13:54:57
|
On Wed, Dec 27, 2000 at 11:53:19AM +0100, Michel D=E4nzer wrote: > Albert Baldassarre wrote: > >=20 > > I'm having a problem with DRI and XFree86 4.0.2. XFree86 reports the > > error: "(EE) R128(0): R128DRIScreenInit failed (DRM version =3D 1.0.0= , > > expected 2.1.x). Disabling DRI." It worked fine with XFree86 4.0.1 a= nd > > the r128 DRM from kernel 2.2.18. I have also tried using the r128 mod= ule > > from 2.4.0 test 13 with the same results. Any help would be greatly > > appreciated. I have an ATI Rage Xpert 99 AGP. >=20 > You need the DRM from XFree86 4.0.2. You most probably have to build it > yourself, you can get the source from the XFree86 or DRI CVS. You mean that the DRM code in 2.2.18 is already outdated? Sigh. I hate ROTD software. Jeff |
From: Gareth H. <ga...@va...> - 2000-12-27 15:00:19
|
Jeff Epler wrote: > > You mean that the DRM code in 2.2.18 is already outdated? The r128 kernel module that matches the 4.0.2 release will be merged back into the main 2.4 kernel series soon. I'm rather busy with other things right now, so I haven't had time to do the sync yet. I don't know (and don't really care) what happens with 2.2 -- we try and keep 2.4 up to date, and the r128 has just gone through some major changes that haven't had time to filter through yet. -- Gareth |
From: Michel <mic...@ii...> - 2000-12-27 15:03:18
|
Jeff Epler wrote: >=20 > On Wed, Dec 27, 2000 at 11:53:19AM +0100, Michel D=E4nzer wrote: > > Albert Baldassarre wrote: > > > > > > I'm having a problem with DRI and XFree86 4.0.2. XFree86 reports th= e > > > error: "(EE) R128(0): R128DRIScreenInit failed (DRM version =3D 1.0= .0, > > > expected 2.1.x). Disabling DRI." It worked fine with XFree86 4.0.1= and > > > the r128 DRM from kernel 2.2.18. I have also tried using the r128 m= odule > > > from 2.4.0 test 13 with the same results. Any help would be greatly > > > appreciated. I have an ATI Rage Xpert 99 AGP. > > > > You need the DRM from XFree86 4.0.2. You most probably have to build = it > > yourself, you can get the source from the XFree86 or DRI CVS. >=20 > You mean that the DRM code in 2.2.18 is already outdated? For the current Rage128 DRI, yes. > Sigh. I hate ROTD software. This is an unusual situation. There have been dramatic changes in the r12= 8 DRM which don't allow for compatibility. And the timing has been somewhat unl= ucky as well with 2.2.18 coming out just before the DRM changes appeared. Michel --=20 Earthling Michel D=E4nzer (MrCooper) \ CS student and free software ent= husiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Pr= oject |
From: Jeff E. <je...@us...> - 2000-12-27 15:10:23
|
On Wed, Dec 27, 2000 at 04:02:36PM +0100, Michel D=E4nzer wrote: > Jeff Epler wrote: > > You mean that the DRM code in 2.2.18 is already outdated? >=20 > For the current Rage128 DRI, yes. >=20 > > Sigh. I hate ROTD software. >=20 > This is an unusual situation. There have been dramatic changes in the r= 128 DRM > which don't allow for compatibility. And the timing has been somewhat u= nlucky > as well with 2.2.18 coming out just before the DRM changes appeared. My card is a V4, not an R128, so that's in some sense a relief. For those who would wish to use an r128 with 2.2.18, is this possible? C= an you just drop the file into your 2.2 source tree and "make modules"? Jeff |
From: Iain T. <Iai...@di...> - 2000-12-27 18:26:12
|
On Wed, 27 Dec 2000, Jeff Epler wrote: > On Wed, Dec 27, 2000 at 04:02:36PM +0100, Michel D=E4nzer wrote: > > This is an unusual situation. There have been dramatic changes in the= r128 DRM > > which don't allow for compatibility. And the timing has been somewhat= unlucky > > as well with 2.2.18 coming out just before the DRM changes appeared. > My card is a V4, not an R128, so that's in some sense a relief. > For those who would wish to use an r128 with 2.2.18, is this possible? = Can > you just drop the file into your 2.2 source tree and "make modules"? Can't you just use the DRM that XFree86 builds, rather than the one the kernel builds? I am also under the impression that the XFree86 DRM modules can be built stand-alone anyway (something like cd xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel and make -f Makefile.linux), and copy the new module into /lib/modules/2.2.18/misc. This looks like it should work, as I managed to build the Radeon support module, and it insmodded OK, however, it promptly locked hard when the Enlightenment starting screen tried to put those nice half-screen images up. (and yes, I know Radeon support is somewhat experimental, but I was curious). -- = Regards, Iai...@di.... My website: http://www.warwick.ac.uk/~csuli/ XMMS now playing: Westwood Studios - Fortification |