> Just upgraded to the latest radeon dri-cvs (using the binary packages > on SF) and now the X server won't start. This used to work fine with > the 20 May TCL snapshot. > > The kernel module seems to load OK: > > Jun 19 16:30:36 localhost kernel: [drm] AGP 0.99 on Unknown @ 0xec000000 64MB > Jun 19 16:30:36 localhost kernel: [drm] Initialized radeon 1.3.1 20020611 on minor 0 > > but the X server crashes. A full XFree86.0.log is below. For > comparison, the 20 May TCL produces an identical log (up to the moment > it crashes) apart from: > > Is there any significance in the different return value from > drmOpenDevice?
I was using XF4.1 told that wasnt good enough and had to upgrade to XF4.2. So I did, although I'm not sure I'm getting it 100% right. Tried XFree86.org's tarballs with install script but that didnt work too well. Currently installing: XFree86-4.20-16mdk.i586.rpm XFree86-server-4.20-16mdk.i586.rpm XFree86-libs-4.20-16mdk.i586.rpm (ie rpms from cooker) over a plain install of MDK8.1 with 3D acceleration. I then get a working XF4.2 but without direct rendering. Install a new binary TCL .bz2 package off SF and I get an identical XFree86.0.log. I must still try an old TCL binary from TG instead of SF and see what happens. So you are not alone, the error has been reproduced. Although in my case I suspect the root of the problems is me. On a side note: radeon_dri.so is 5.2MB in the SF d/l and radeon_dri.so is 1.8MB in the TG d/l. Any explanation? Liam ---- it depends ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
