Nightwulf|work: hi all
Nille02: good morning
Nightwulf|work: somebody else has got problems with drm-git r6xx-r7xx-support branch on kernel 2.6.29?
yangman: Nightwulf|work: if you're on 2.6.29, use drm-next instead
Nightwulf|work: yangman: ah..k...that's just another different branch or a seperate repository?
yangman: Nightwulf|work: git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git branch drm-next
Nightwulf|work: yangman: thx!
yangman: Nightwulf|work: lemme know if you have issues compiling against your installed kernel. I'll be around for a little while longer
Nightwulf|work: yangman: i will
yangman: Nightwulf|work: that's actually alirlied's repo for kernel work
Nightwulf|work: yangman: btw...any news about that artifact problem on hd3870x2/kde4?
yangman: I haven't heard anything
yangman: is it radeonhd specific?
Nightwulf|work: never tried with other drivers since fglrx won't run on that card either
yangman: well, I mean does it happen in radeon also
Nightwulf|work: yangman: i would have to use git branches there too i guess?
yangman: yes. to drm-next
Nightwulf|work: k, I'll try tomorrow and report the results...sorry but can't do it earlier :-/
yangman: you'll need to compile only the modules against your running kernel, not the entire source tree
Nightwulf|work: yangman: yeah...I'll try drm-next in a few minutes...what i ment was, that I won't have time to test radeon against this artifact bug until tomorrow ;-)
yangman: ah. ok
Nightwulf|work: wow...takes long to clone that repo
Zajec: that's whole kernel
Nightwulf|work: ah...ok...that explains it :P
yangman: oh, I forgot to mention that. I swear I was thinking it ;)
Nightwulf|work: hmmm....I'm a noob when it comes to compile only parts of the kernel...how do i compile just the drm-module stuff?
yangman: go into drivers/gpu/drm
yangman: then make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` CONFIG_RADEON=m CONFIG_DRM=m
yangman: you'll need whatever packages installed that lets you compile external kernel modules
Zajec: yangman: would be nice to put this in x.org howto
Zajec: http://www.x.org/wiki/radeonhd:r6xx_r7xx_branch i mean
Nightwulf|work: build errors...I'll pastebin them
yangman: huh. I figured it would compile cleanly against 2.6.29
yangman: to be honest, I haven't tried it myself yet. waiting for gentoo-sources to bump to 2.6.29
Nightwulf|work: yangman: you'll have to wait for long then :P
yangman: well, I should be working on my final project instead of poking at xorg stuff ;)
Nightwulf|work: so no chance to get exa-accel on 2.6.29 atm?
yangman: ask airlied about compiling drm-next against 2.6.29 when he's around
yangman: I assumed it would compile cleanly since it's what's going upstream
loki_666: Nightwulf|work: about your issue building drm-next modules: do you have 2.6.29 linux headers installed
loki_666: the errors error: 'struct drm_device' has no member named 'vbl_sigs' etc is typically that the compiler doesnt find the rights headers
Nightwulf|work: loki_666: no, since my distribution sticks to 2.6.28.x until now ;-)
Nightwulf|work: loki_666: i would have to build them on my own
loki_666: well if you allready are on 2.6.29 thats means you compiled yourself the kerenel?
loki_666: so you should have thoses headers anyway
loki_666: but i dont know how to specify the directory
Nightwulf|work: loki_666: yes and no....the kernel_headers installed in the system are located in /usr/include/* and those of the self compiled kernel are in /usr/src/linux-2.6.29/include
loki_666: they are also (on ubuntu) in /lib/modules/`uname -r`/build, is that the case for you? i bet no
loki_666: what's in /usr/include is for application interfaces
loki_666: it doest change very often
Nightwulf|work: they are
loki_666: try with make -j8 -C /usr/src/linux-2.6.29 SUBDIRS=`pwd` CONFIG_RADEON=m CONFIG_DRM=m
Nightwulf|work: doesn't work...same errors as above
loki_666: no idea then
Nightwulf|work: yep....that's exactly what I thought ;-)
girrr: I'm trying to get a onboard HD3200 running but the x server shuts down with the message "waiting for X server to shut down error setting MTRR (base = 0xd80000000), size = 0x080000000, type = 1) Invalid argument (22)"
girrr: there seems to be no errors reported in the Xorg.0.log
girrr: I've tried to disable almost everything including mtrr but the result seems the same
udovdh: Eythan, yes it works on my RV635
codemac: EXA for my 4850 hd! Thank you radeonhd team.
codemac: Is there any documentation for how I can effectively contribute to radeonhd? A bug tracker or anything?
yangman: codemac: bug tracking's part of freedesktop.org
codemac: aha, I just found the link to bugzilla on the wiki
MarcOChapeau: Good evening
MarcOChapeau: I'm having a weird issue. I'm trying to get DRI enabled on my system. I'm using a radeon HD2900. I'm guessing most of my setup is right, I usually don't have any kind of issues with other systems. but...
MostAwesomeDude: MarcOChapeau: No DRI for your card yet.
MarcOChapeau: that might be the issue :)
MarcOChapeau: still, is this kernel log alright ? : http://rafb.net/p/3OMSkn65.html
MostAwesomeDude: Yeah, something's up with your MTRRs.
MostAwesomeDude: Not sure, though.
MarcOChapeau: MostAwesomeDude: ok, but not necessarily related to the DRM module ?
agd5f: MarcOChapeau: you can enable the dri, but only for EXA and Xv, no 3D yet
MarcOChapeau: agd5f: actually, only 2D would be just what I nee
MostAwesomeDude: Oh, misunderstood. Thought you were asking about 3D, sorry.
MarcOChapeau: ok, so basically, I *should* see something in /dev/dri
MarcOChapeau: kernel is 2.6.28 btw
agd5f: MarcOChapeau: you need Dave's drm-next tree or drm from mesa/drm r6xx-r7xx-support branch
MarcOChapeau: agd5f: k, I guessed there was something like that :). thanks for the pointer ! I feel less stupid...
yangman: good to see some code activity happening on the ML again :)
Zajec: yangman: do you mean sth else than ev56 CPU support?
yangman: just in general
Zajec: didn't notice anything else :)
Zajec: yangman: did you still play with suspending?
yangman: not much since last time
yangman: focusing on graduating first ;)
Zajec: sure, obvious :)
yangman: but the suspend issue was really bugging me because it's a show stopper for my use pattern. I'm temporarily on radeon
Zajec: good luck at graduating then :) and about suspenging same for me :/
Zajec: really need that but also really need radeonhd (hdmi audio support)
yangman: I tried comparing the modesetting paths coming out of EnterVT with radeon, but a good chunk of it wasn't trivial, and the trivial difference didn't improve the situation any
yangman: I'm really hoping someone that knows the modesetting code would go in and take a look
har_ac: anyone have natit for hd2600xt