From: Crossbones <fx...@ho...> - 2001-01-30 05:17:55
|
----- Original Message ----- From: "Gareth Hughes" <ga...@va...> To: <dr...@bi...> Cc: "Robert Dale" <rd...@di...>; <dri...@li...> Sent: Wednesday, January 24, 2001 10:27 PM Subject: Re: [Dri-devel] Radeon Bug (I think) (fwd) > dr...@bi... wrote: > > > > > I submitted a similar bug awhile ago. See if it's the same. > > > Although, I haven't tried any more recent code since it's a different > > > machine working properly. > > > > > > http://sourceforge.net/bugs/?func=detailbug&bug_id=121904&group_id=387 > > > > Well assuming my mother board is the same (wish i could find tha manual, > > is there another way to check easily ?) then yes. > > > > A radeon 32MB DDR with an athlon 750 chip and an AMD Irongate AGP. > > Try running with: > > Option "AGPMode" "1" > > -- Gareth I've got the same setup, so I thought I'd comment on my end of this. :) Before using the option above, just getting in to X was tricky at best. It would sometimes work, but in lower resolutions with lower refresh rates. Using that option, X will always come up. I can't, however, exit from X. With about a half-dozen tries, only once did X actually exit without crashing. When it exited, the console was corrupted (scroll produced lines that had already gone off screen long ago, the cursor was never on the line text was being typed on.) Usually when exiting, the monitor goes in to something similar to standby. If I can be of further assistance, just holler! (heh) Steve |