it.
Oh well, doesn't apply to me. I'm using radeon-20021006 and get a
blank screen - the monitor loses signal - and I can't switch back to
the console. C-M-del helps, though.
Anyways, here is my XFree86.0.log:
XFree86.0.log
Description: XFree86.0.log
This happens with both libxaa.a from my
Michel Dänzer:
On Son, 2002-10-06 at 14:50, Adam Duck wrote:
Oh well, doesn't apply to me. I'm using radeon-20021006
BTW, you actually need a r200 snapshot for a 8500, but that shouldn't
cause such a crash...
and get a blank screen - the monitor loses signal - and I can't switch back
On Son, 2002-10-06 at 17:21, Svein Harang wrote:
Michel Dänzer:
On Son, 2002-10-06 at 14:50, Adam Duck wrote:
Oh well, doesn't apply to me. I'm using radeon-20021006
BTW, you actually need a r200 snapshot for a 8500, but that shouldn't
cause such a crash...
and get a blank
All my xv problems disappeared with the 20001006 build of the R128
driver.
Thanks for all the hard work everybody!
signature.asc
Description: This is a digitally signed message part
On Sun, Oct 06, 2002 at 04:39:23PM +0200, Michel Dänzer wrote:
and get a blank screen - the monitor loses signal - and I can't switch back
to the console. C-M-del helps, though.
That means you _are_ on console, it's just not visible. ;)
(==) RADEON(0): Silken mouse enabled
Hmm, it
On Son, 2002-10-06 at 19:49, Malte Cornils wrote:
On Sun, Oct 06, 2002 at 04:39:23PM +0200, Michel Dänzer wrote:
and get a blank screen - the monitor loses signal - and I can't switch back
to the console. C-M-del helps, though.
That means you _are_ on console, it's just not visible.
gone away
with
j today's snapshot. Please test it.
Oh well, doesn't apply to me. I'm using radeon-20021006 and get a
blank screen - the monitor loses signal - and I can't switch back to
the console. C-M-del helps, though.
Anyways, here is my XFree86.0.log:
FYI--I always build my
John,
First, I'm sorry I didn't reply sooner. But I was holding out a little
to see if anything came up relevant to your case before giving you the
standard get-a-stack-backtrace-with-gdb.
It appears that there have been similar problems with the r200 chip
reported on th dri-devel mailing list
On Sun, Oct 06, 2002 at 08:07:41PM +0200, Michel Dänzer wrote:
BTW, how do I get a backtrace of this? get a statically-linked xserver
binary, run that under gdb?
Assuming that this is some sort of binary incompatibility, a static
build won't exhibit the problem (neither will a full build
and against glibc-2.3) but all these problems should have gone away
with
j today's snapshot. Please test it.
Oh well, doesn't apply to me. I'm using radeon-20021006 and get a
blank screen - the monitor loses signal - and I can't switch back to
the console. C-M-del helps, though
10 matches
Mail list logo
