On Wed, Feb 12, 2003 at 06:14:23PM +0100, Michel Dänzer mentioned:
> The dates don't matter, only the DRM version does. If the 3D clients
> still say it's smaller than 1.3, then I have no idea why, except if
> there's an older DRM built into the kernel - but then it should also
> show up in the dme
On Wed, Feb 12, 2003 at 04:33:03PM +0100, Michel Dänzer mentioned:
> > OK, I've a rebuild kernel. radeon.o and agpgart.o are modprobed. However,
> > I get the same error.
> What does
> dmesg | grep '\[drm\]'
> say?
ratbert[11]:~% dmesg | grep '\[drm\]'
[drm] AGP 0.99 on Intel i845 @ 0xf800 64
On Mit, 2003-02-12 at 17:32, John P. Looney wrote:
> On Wed, Feb 12, 2003 at 04:33:03PM +0100, Michel Dänzer mentioned:
> > > OK, I've a rebuild kernel. radeon.o and agpgart.o are modprobed. However,
> > > I get the same error.
> > What does
> > dmesg | grep '\[drm\]'
> > say?
>
> ratbert[11]:~%
On Mit, 2003-02-12 at 14:50, John P. Looney wrote:
> On Tue, Feb 11, 2003 at 03:07:57PM +0100, Michel Dänzer mentioned:
> > The point is that this is either the wrong (too old) radeon module, or
> > the radeon DRM is already built into the kernel (in which case you can
> > load another one as a mod
On Tue, Feb 11, 2003 at 03:07:57PM +0100, Michel Dänzer mentioned:
> The point is that this is either the wrong (too old) radeon module, or
> the radeon DRM is already built into the kernel (in which case you can
> load another one as a module unfortunately, but clients see the one
> built into the
On Die, 2003-02-11 at 14:55, John P. Looney wrote:
> On Tue, Feb 11, 2003 at 02:28:58PM +0100, Michel Dänzer mentioned:
>
> > > wolf.x86: radeon_ioctl.h:165: radeonAllocCmdBuf: Assertion `rmesa->dri.drmMinor
>>= 3' failed.
> > > Received signal 6, exiting...
> > Now you need to make sure the new
On Tue, Feb 11, 2003 at 02:28:58PM +0100, Michel Dänzer mentioned:
> Well, that's the source of my confusion - I don't provide a
> drm-trunk-module-2.4.18 package, and neither does Debian woody. I'll
> just assume you built it yourself from drm-trunk-module-src.
Ah yes, I did build it from your d
On Die, 2003-02-11 at 10:56, John P. Looney wrote:
> On Tue, Feb 11, 2003 at 12:36:54AM +0100, Michel Dänzer mentioned:
> > On Mon, 2003-02-10 at 19:31, John P. Looney wrote:
> > > Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
> > > Woody, though they were mostly fine in
On Mon, Feb 10, 2003 at 11:24:58PM +0100, Jacek Pop³awski mentioned:
> On Mon, Feb 10, 2003 at 06:31:37PM +, John P. Looney wrote:
> > Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
> > Woody, though they were mostly fine in Quake3, in Wolfenstien, there were
> > seve
On Tue, Feb 11, 2003 at 12:36:54AM +0100, Michel Dänzer mentioned:
> On Mon, 2003-02-10 at 19:31, John P. Looney wrote:
> > Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
> > Woody, though they were mostly fine in Quake3, in Wolfenstien, there were
> > severe problems wit
On Mon, 2003-02-10 at 19:31, John P. Looney wrote:
> Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
> Woody, though they were mostly fine in Quake3, in Wolfenstien, there were
> severe problems with corrupted textures.
>
> After noting a few people were recommended to u
On Mon, Feb 10, 2003 at 06:31:37PM +, John P. Looney wrote:
> Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
> Woody, though they were mostly fine in Quake3, in Wolfenstien, there were
> severe problems with corrupted textures.
Could you try driver 20021022 (from dri
Hi, I was using the old Radeon drivers that shipped with a dist-upgraded
Woody, though they were mostly fine in Quake3, in Wolfenstien, there were
severe problems with corrupted textures.
After noting a few people were recommended to upgrade to get rid of these
problems, I did. To upgrade, I use
13 matches
Mail list logo
