Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500Mobility)

2003-01-27 Thread Nathaniel Gray

I guess this doesn't happen with DRI disabled? Looks like pure luck to
me that RADEONWaitForVerticalSync() ever returns when the DRM handles
vertical blank interrupts. I'll look into fixing that if noone beats me
to it.


True, the problem doesn't occur unless DRI is enabled.


 2.  I was using KDM and after exiting X my machine would lock up as it 
 tried to restart the login screen.  I think that even without KDM I 
 couldn't restart X after I started it once.  I'm not positive about 
 this though.

Can you verify that? Would be interesting to know.


Nope, I can't verify it.  I guess my system just got into a bad state 
somehow.  I'm using 4.2.99.4 right now and have successfully restarted 
X many times.  I haven't tried using KDM again though.

I'm almost ready to switch to this release for everyday use, but I still 
have to see how it handles a suspend/resume cycle.  I saw that Charl's 
dri_resume patch isn't in yet, which is a shame.  I guess no DRI for me 
for the near future.  I suppose that's already true if I want to use 
dual-head though.

For some reason anti-aliasing has ceased too.  Oh well, a problem for 
another day.

-- 
-- Nathaniel Gray -- Caltech Computer Science --
-- Mojave Project -- http://mojave.cs.caltech.edu --

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon 7500Mobility)

2003-01-26 Thread Michel Dänzer
On Sun, 2003-01-26 at 03:36, Charl P. Botha wrote: 
 I just built 4.2.99.4 from CVS on my Radeon 7500 Mobility laptop.
 Starting X yields a blank display and a locked keyboard.  Attempting to kill
 X or shutdown the laptop via ssh results in a complete system lockup.
 
 4.2.99.3 works perfectly on the *exact* same configuration.  I've attached
 my XFree86.0.log although it seems to be normal.

[...]

 (WW) RADEON(0): Restoring MEM_CNTL (), setting to 2d002d01
 (WW) RADEON(0): Restoring CONFIG_MEMSIZE (0400), setting to
 0400

Have you been following the discussion about this code? Do any of the
workarounds suggested in that thread (about '7200 support') help?


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86