JarenJP: Anyone know what I need to do to get hdmi audio working with the radeonhd driver?
JarenJP: I've added
JarenJP: Option "Audio" "true"
JarenJP: Option "HDMI" "DVI-I_1"
JarenJP: to the device section of my xorg.conf file as it mentions I need to do in the man page.
elena09: That's their answer which I can't understand, will work or not?
yangman: it pretty clearly says catalyst 9.5 is what you should use
yangman: just install it using whatever your distro provides
yangman: if you have issues with it, you can try asking in #ati
udovdh: elena09, what is the problem?
elena09: I apologize, was working... I tried to be prepared to install Ubuntu on my ordered laptop and I asked AND about their catalyst 9.5 to see if it's good for ATI Mobility Radeon HD 3450
JarenJP: Is there a way to slow down the speed of my gpu fan while using the radeonhd driver?
yangman: JarenJP: no. we don't have documentation on power management and fan control yet
JarenJP: yangman: thanks, Maybe I'll hook it to the mother board and adjust the speed there.
JarenJP: yangman: is reading the temperature settings also not possible?
JarenJP: yangman: I mean, can we read the temp. sensors?
yangman: someone's been working on it, but he hasn't up the code up anywhere yet
bridgman: FYI we don't plan to provide documentation on the third party fan/temp chips; that's not our IP so would need to come from the HW vendors. The atombios tables do contain info on how the chips are connected (ie which GPIO pins) AFAIK
bridgman: I think the atombios tables identify the chip but not 100% sure, will check in a bit
bridgman: anyways, atombios.h should have most of this
MostAwesomeDude: Hm. How unique are those chips? Maybe some of them are already in lm_sensors?
bridgman: starting with rv670 (I think) we included a temp/fan control on chip, but it didn't start getting used immediately AFAIK
bridgman: that info will have to come from us
bridgman: I think they're bog-standard chips, the only catch is that access to the chips should go through the graphics driver since some of the relevent registers are also used by the driver
bridgman: and that should really be in the kernel, yada yada...
MostAwesomeDude: Well, the sensor stuff is mostly kernelside already.
MostAwesomeDude: We'd wire up DRM to access the sensors. Same as HDMI and TV-in.
yangman: sensor chips are usually well documented anyways
yangman: there's very good chances lm_sensors already support the ones in common use
yangman: but there's the issue of whether or not it's feasible to expose the GPU's internal wiring as a generic i2c interface that lm_sensors can poke at
yangman: but, maybe it's a non-issue. I don't *really* know what I'm talking about ;)
MostAwesomeDude: yangman: It's doable, just not currently done. :3
bridgman: agd5f seemed to think that having drm expose a generic i2c would work; his main concern was that it needed to be kms only or the ddx modesetting code could collide with sensor accesses
bridgman: hope I got that right ;)
MostAwesomeDude: Yeah, I think KMS-only is the right way.
MostAwesomeDude: That lets us consolidate all the various thingies on the card.
agd5f: lm_sensors is in the kernel so to take advantage of the infrastructure it would need to be done in the kernel
agd5f: atombios tables list the thermal chip, i2c addresses, gpio lines, etc.
agd5f: most of the thermal chips have specs available from the manufacturer's websites
T`: hi, i have one of my monitors rotated 90degrees.. and i see vertical black lines
T`: happens when i move a window around
T`: if i move my mouse around those lines they usually go away
T`: a screenshot of the screen doesn't show these black lines.. its only visible on the monitor.. i am using the latest git copy of radeonhd on HD3450 w/ubuntu 9.04
T`: can someone help me fix this issue?