From savignien@caramail.com Sat Dec  1 10:57:45 2007
From: savignien hercule <savignien@caramail.com>
To: radeonhd@lists.opensuse.org
Subject: Re: Re: [radeonhd] RS690 nearly working
Date: Sat, 01 Dec 2007 10:59:31 +0000
Message-ID: <109493435522362@lycos-europe.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3888865145929353088=="

--===============3888865145929353088==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> De: Luc Verhaegen <libv(a)skynet.be>
> A: Coleman Kane <cokane(a)cokane.org>
> Objet: Re: [radeonhd] RS690 nearly working
> Date: Fri, 30 Nov 2007 16:42:53 +0100

> On Fri, Nov 30, 2007 at 10:14:04AM -0500, Coleman Kane wrote:
> > Luc Verhaegen wrote:
> > > On Fri, Nov 30, 2007 at 12:58:31PM +0000, savignien hercule wrote:
> > >  =20
> > >> Hello,
> > >>
> > >> I'm not sure that the attachments works well with the list so here is =

> > >> the log.
> > >>    =20
> > >
> > > You wanted 1600x1200? According to this log, this was the actual mode=20
> > > that was set up :)
> > >
> > > It seems we got our lines crossed here, as i am not sure anymore what=20
> > > problem you were seeing in the first place then :)
> > >
> > > Thanks,
> > >
> > > Luc Verhaegen.
> > > SUSE/Novell X Driver Developer.
> > >  =20
> > He's getting the mode set up, but the display exhibits the "fuzzy
> > vertical stripes" problem that I originally had at 1600x1200. The only
> > resolution he can use and actually see what's going on is 1152x864. So
> > the card does set the framebuffer to 1600x1200, but all of the rendering
> > is scrambled on the screen.
> >=20
> > savignien, can you take a screenshot with a digital camera or with a
> > cell phone of the problem? I think you're having the same problem I had,
> > but it is really hard to actually describe it. Also, try running the
> > rhd_conntest program, unless you've already done that.
> >=20
> > --
> > Coleman Kane
>=20
> Did he run fglrx before and didn't powercycle in between? Because that's=20
> been culprit there so far.
>=20
> We don't know yet what we need to do to fix this, but we can reproduce=20
> it with fglrx so we will dig it out.
>=20
> Luc Verhaegen.
> SSUE/Novell X Driver Developer.
> --=20
> To unsubscribe, e-mail: <a href=3Dmailto:"radeonhd+unsubscribe(a)opensuse.o=
rg">radeonhd+unsubscribe(a)opensuse.org</a>
> For additional commands, e-mail: <a href=3Dmailto:"radeonhd+help(a)opensuse=
.org">radeonhd+help(a)opensuse.org</a>

Hello,

I never used fglrx. The "default" settings after installation was vesa and I =
only tried radeonhd after that. I'm also pretty sure that I powercycled at on=
e moment between my attempts.
Yes the log I sent was a try to get 1600x1200 working but it exhibited the "f=
uzzy" stripes symptom. I thought it would more significant than a successful =
log of 1152x864, maybe I was wrong...

I'll try to take a screenshot with a digital camera (I'll have to borrow one.=
..)
Meanwhile here is the output of rhd_conntest :
rhd_conntest: v0.0.4, git branch master, commit e86e764b
Checking connectors on 0x791E, 0x1462, 0x7327  (@01:05:00):
  Load Detection: RHD_OUTPUT_DACA
  HotPlug: RHD_HPD_0
  DDC: RHD_DDC_0
  DDC Line[0]: Slaves: 6e a0


Sincerely,
savi.


--===============3888865145929353088==--