Thanks for everybody that confirmed the problem. I've reverted all my changes in the trunk, so starting from today the snapshots should no longer have this problem. This, of course, if the anonymous CVS repository doesn't get delayed again...
I moved by changes into a new branch (newdrm-0-0-1-branch), where I'll address this problem and proceed with what I was doing all in my on good time. When I have something worth to test I'll make some snapshots from this branch too. José Fonseca On Fri, Jun 20, 2003 at 03:41:03AM +0200, Paul Heldens wrote: > I'm experiencing the same. > > > On Wed, 2003-06-18 at 16:16, Alex Deucher wrote: > > For what it's worth I'm seeing the same behavior on my m6 using Xfree86 > > CVS from a couple weeks ago. I have to rmmod radeon to and restart X > > to get 3D to work. same messages in my log file. > > > > Alex > > > > ----------------------- > > > > Jos Fonseca wrote: > > >>(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:0:0" > > >>(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0c70000 > > >>(II) RADEON(0): [drm] mapped SAREA 0xe0c70000 to 0x40023000 > > >>(II) RADEON(0): [drm] framebuffer handle = 0xd8000000 > > >>(II) RADEON(0): [drm] added 1 reserved context for kernel > > >>(WW) RADEON(0): [agp] AGP not available > > >>(II) RADEON(0): [drm] removed 1 reserved context for kernel > > >>(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0c70000 at > > 0x40023000 > > >>(II) RADEON(0): Memory manager initialized to (0,0) (1152,8191) > > >>(II) RADEON(0): Reserved area from (0,864) to (1152,866) > > >>(II) RADEON(0): Largest offscreen area available: 1152 x 7325 > > >>(II) RADEON(0): Acceleration enabled > > >>(II) RADEON(0): Using hardware cursor (scanline 866) > > >>(II) RADEON(0): Largest offscreen area available: 1152 x 7321 > > >>(II) RADEON(0): Direct rendering disabled > > > > > > > > > This can't be. This log can't possible match the other one you gave > > me. > > > In the /var/log/messages it showed the agp buffer being added and so > > on. > > > > > > The only explanantion I can think of is that you're running _two_ X > > > servers. The first one acquires the AGP device but the second fails > > to > > > acquire, since the AGP device is already acquired by the first. > > > > FWIW, I get that now always when I start the X server, then shut down > > the X server and start it again. DRI will never work again, unless I > > rmmod the radeon module manually before I restart the X server. Sounds > > like some initialization thing. > > lsmod will show (before starting X, but after manually inserting > > agpgart > > & radeon): > > Module Size Used by Not tainted > > radeon 102152 0 (unused) > > agpgart 13904 1 > > > > after X is started: > > radeon 102152 12 > > agpgart 13904 3 > > > > and after X shutdown (and restart with dri not working): > > radeon 102152 0 > > agpgart 13904 3 > > > > after rmmod radeon the agpgart used count will be back to 0. > > > > Roland ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
