Tigerchen: nen I anwesend?
Tigerchen: sry fc
pkern: Hi. radeonhd 1.0.0 crashes for me after some 15-20s of usage with the following: ../../src/rhd_cursor.c:110: setCursorImage: Assertion '(Cursor->Height > 0) && (Cursor->Height <= MAX_CURSOR_HEIGHT)' failed.
khorben_: if you don't get an answer here, you can try to subscribe and submit it to the mailing-list, or even better submit the bug
pkern: Last time I subscribed I was overwhelmed by mails, and I needed to subscribe to send mails to the list.
pkern: Now granted it's also mirrored on gmane IIRC.
khorben_: you can subscribe and setup the list so that you don't receive the messages
pkern: That's https://bugs.freedesktop.org/show_bug.cgi?id=12907 probably.
pkern: khorben_: Thanks for the hint.
khorben_: you're welcome
pkern: And with SWCursor it works.
soc: hi, just wanted to say thank you for this great driver!
soc: what are you doing at the moment? afaik the released docs only included 2d and that runs great on the majority of the systems ...
pkern: Hm, the picture is somehow noisy. Tooltips feel weird because they are not coloured with a single colour but rather bringled. I didn't notice that on fglrx...
ndim: pkern: Ah, you too...
pkern: Don't know how I should report that, though.
PinkFreud: heya folks. I'm having an issue with radeonhd (Debian experimental, 0.0.4~git20071124-1) under version 1.4.0 of the X server.
PinkFreud: I have an older 17" lcd (Dell 1700FP, 4:3 aspect ratio) connected to a Raritan kvm which apparently doesn't support dde.
PinkFreud: no matter what I use in my xorg.conf (HorizSync + VertRefresh lines in the Monitor section, PreferredMode, and even explicitly defined modelines), I keep getting handed a 1280x768 resolution.
PinkFreud: suffice it to say, this doesn't look very good on a non-widescreen display.
PinkFreud: is it at all possible to convince X, or the radeonhd driver, to use another resolution?
PinkFreud: I have X.org 1.3.0 working with this setup, though it's on a different machine which does *not* use a Radeon.
ndim: PinkFreud: I guess the TFT does DDC...
PinkFreud: yes, it does. the kvm does not, though.
ndim: Uhm.
ndim: Oh.
ndim: Well... do you use << Monitor "foo" >>?
PinkFreud: yes, I have a Monitor section.
PinkFreud: In the past, I was able to work around the lack of DDC by merely specifying HorizSync and VertRefresh.
ndim: With randr, you should use << Option "monitor-VGA_1" "foO" >>, I gather.
PinkFreud: This apparently does not work now, though I'm unsure if the problem lies with X.org or the radeonhd driver.
PinkFreud: hmmm.
PinkFreud: I haven't gotten to the point of setting up multiple monitors yet.
PinkFreud: I'd be happy with just one working display at the moment. :P
PinkFreud: alas, 1280x768 is horribly squashed. while I *can* see an image, I don't quite consider it working as it's not a native resolution for my display. :)
PinkFreud: apparently, DDC doesn't quite work, either
PinkFreud: it detects my monitor's max resolution as 1280x1024, but then the radeonhd driver goes on to happily ignore this, and gives me:
PinkFreud: (II) RADEONHD(0): Output DVI-I_2/TMDS_B using initial mode 1600x1024
PinkFreud: (II) RADEONHD(0): Output DVI-I_2/DAC_A using initial mode 1400x1050
ndim: PinkFreud: If you do not have Option "NoRandR" set, you are running radeonhd in randr mode.
PinkFreud: hmmm.
PinkFreud: I can use RandR, as I do eventually want to set up the second head
ndim: Unfortunately, my NEC MultiSync 5FG 17" CRT predating the invention of DDC is broken.
ndim: PinkFreud: But then you must configure your monitor accordingly.
ndim: I.e. << Monitor "foo" >> will probably no cut it.
ndim: (Not that I have any actual experience. :)
PinkFreud: (II) RADEONHD(0): Setting up "1280x1024" (1280x1024@75.0Hz)
PinkFreud: ok, with NoRandR set, it does look like it works
PinkFreud: so the question is - what does an RandR configured monitor look like? :)
ndim: PinkFreud: Or without NoRandR, and replacing the << Monitor "foo" >> with << Option "monitor-DVI-I_2" "foo" >> ?
PinkFreud: where did you get DVI-I_2 from?
PinkFreud: is that the dvi connector it's detecting?
ndim: xrandr -q
ndim: Whatever that prints... and where your display is connected to
PinkFreud: Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
PinkFreud: default connected 1280x1024+0+0 0mm x 0mm 1280x1024 75.0*
ndim: Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 1400 x 1400
ndim: VGA_1 disconnected
ndim: PANEL connected 1400x1050+0+0 286mm x 214mm 1400x1050 60.0*+
ndim: DVI-D_1 disconnected
PinkFreud: whoops
PinkFreud: still had NoRandR
PinkFreud: DVI-I_2/TMDS_B unknown connection 1280x768+0+0 0mm x 0mm
PinkFreud: DVI-I_2/DAC_A connected 1280x768+0+0 0mm x 0mm
PinkFreud: which one do I use?
ndim: Analog or digital?
PinkFreud: also, I use a dual cable DVI connector (the ends on this one are VGA, though that doesn't matter).
PinkFreud: heh, analog.
ndim: TMDS is digital, DAC is a digital-analog converter.
PinkFreud: each end is labeled with a number - 1 or 2, depending on the head.
ndim: So I'd use DVI-I_2/DAC_A
ndim: Or DVI-I_2
PinkFreud: I have the monitor connected to '1' right now, but radeonhd is detecting '2'
PinkFreud: DVI-I_1/DAC_B disconnected
PinkFreud: hmmm.
PinkFreud: interesting. DVI-I_1, but DAC_B
PinkFreud: ok, sort of.
PinkFreud: it detects more available frequencies for the display on DVI-I_2/DAC_A
PinkFreud: however, it's still insisting that it wants to use 1280x768
PinkFreud: DISPLAY=:0 xrandr --output DVI-I_2/DAC_A --mode 1280x1024
PinkFreud: that works to reconfigure the display mode.
PinkFreud: now, how do I tell X that that should be the default, instead of the wonky 1280x768?
ndim: PinkFreud: Eh, great.
PinkFreud: setting PreferredMode in the Monitor section doesn't quite work
PinkFreud: it causes X to hang, alas.
ndim: IIRC there was a bug in the X server (not in the rhd driver) regarding PreferredMode. Something about an endless loop...
PinkFreud: oops.
PinkFreud: is there another way to inform RandR to use a sane video mode by default?
glisse: agd5f: hey monday is your first official day as AMD boy ? ;)
PinkFreud: hmm
PinkFreud: hmmm. is it possible to still use the old static dual-head config if I disable RandR?
PinkFreud: given the apparent brain-deadedness of RandR coupled with the PreferredMode bug, I'd be just as happy disabling RandR until it improves.
agd5f: glisse: yup :)
glisse: :)
glisse: agd5f: will be nice to see commit with an amd address
agd5f: glisse: I can't wait :)
agd5f: orientation next week
glisse: agd5f: you got their ?
glisse: s/got/go
glisse: fly to canada for orientation ?
agd5f: no, at AMD in Sunnyvale
glisse: oh
agd5f: although I'll be heading up to canada at some point as well
agd5f: just in time for winter :)
glisse: :)
glisse: you lucky
agd5f: heh
pkern: The picture is somehow noisy with radeonhd. Tooltips feel weird because they are not coloured with a single colour but rather bringled. fglrx doesn't show this problem...
marcheu: wth does bringled means ?
glisse: marcheu: this is how you see world after could of drink i think :d
glisse: s/could/couple
glisse: should go to sleep or stop drinking or do both
marcheu: ah, I didn't know because I'm never drunk
glisse: marcheu: that must be painfull...
glisse: i can't imagine how people can live without being drunk
marcheu: well, I am beautiful, sexy, and in good shape, and never drink. I'm probably the perfect guy. that's simple.
glisse: wonder why not every people is like marcheu world :)
pkern: marcheu: Well, that's what my translator bought up.
pkern: Sorry... brindled