OK... I just upgraded to 2.4.3, recompiled the DRM modules from DRI cvs,
and it's working. Was something done to the CVS code to make it work with
2.4.3, and, if so, could it have had a negative impact on 2.4.2?
Adam
On Sun, 1 Apr 2001, Adam K Kirchhoff wrote:
>
> This isn't just limited to my Radeon, now, either. It's happening with my
> G400. I've attached the full log file from when I tried with my Radeon
> with a CVS pull from this afternoon.
>
> Anyone want to take a look and tell me what they think? After X locks, I
> can still move around with a serial console for a brief period (30 seconds
> to a minute) before my entire machine locks up. If I go to reboot in that
> time, my entire machine locks up. I have my BIOS settings to allow 4x AGP
> (though this log file will show that I tried with AGPMode 1).... As far
> as I can tell, nothing has changed on my system since this last worked
> (with a CVS pull from earlier in the week... Monday, I think).
>
> Adam
>
> On Sat, 31 Mar 2001, Adam K Kirchhoff wrote:
>
> >
> > I pulled the DRI cvs this afternoon (main trunk) and gave it a whirl.
> > X never fully starts up. After about five-ten seconds, the monitor puts
> > itself to sleep and /var/log/XFree86.0.log ends with:
> >
> > 32 128x128 slots
> > 21 256x256 slots
> > 7 512x512 slots
> > (II) RADEON(0): Acceleration enabled
> > (II) RADEON(0): Using hardware cursor (scanline 4104)
> > (II) RADEON(0): Largest offscreen area available: 1280 x 3067
> > (II) RADEON(0): X context handle = 0x00000001
> > (II) RADEON(0): [drm] installed DRM signal handler
> > (II) RADEON(0): [DRI] installation complete
> > (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
> >
> >
> > If I disable the DRI, the server starts up and runs fine (minus 3D, of
> > course).
> >
> > Adam
> >
> >
> >
>
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
