tmpuser: hello, yesterday i wrote about a problem i'm encountering with radeonhd driver. Shortly I compiled it from git and deployed with no errors. When I start compiz I get a white screen. Here I was told to reinstall mesa. I've been messing a bit around with mesa packages and i discover that removing libgli-mesa-glx compiz started correctly (I believe due to sw fallback, am i right?). So I tried downgrading mesa-glx to a previous version but now compiz fails
tmpuser: with the following error:
tmpuser: tmpuser@vinc-think:~$ compiz --replace
tmpuser: Checking for Xgl: not present.
tmpuser: xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
tmpuser: No whitelisted driver found
tmpuser: aborting and using fallback: /usr/bin/metacity
tmpuser: here is my Xorg.0.log: http://pastebin.com/d1fa76c47
tmpuser: someone can help me with this? Thank you
tmpuser: (debian stable, linux 2.6.30-1)
adamk_: The "no whitelisted driver" error simply means that compiz-manager doesn't know that compiz works with the radeonhd driver.
adamk_: More problematic, though, is that you still don't have direct rendering working.
tmpuser: adamk_, yestarday you told me that this can be due to some fglrx interaction
tmpuser: am i correct?
tmpuser: 'cos in this case i would try starting with a clean installation of the os
adamk_: chithead mentioned that, though I was around at the time.
adamk_: Don't do anything yet.
adamk_: What GPU is this?
tmpuser: it is a Ati mobility radeon X1300
adamk_: And what is the output of 'dmesg | grep drm' ?
chithead: if dmesg, Xorg.0.log or glxinfo mention nothing of fglrx then is should be ok
tmpuser: here dmesg output:
tmpuser: [ 29.259070] [drm] Initialized drm 1.1.0 20060810
tmpuser: [ 29.331915] [drm] Initialized radeon 1.30.0 20080528 for 0000:01:00.0 on minor 0
adamk_: Oh, and make sure you have the kernel-firmware package installed...
tmpuser: is dmesg output right?
tmpuser: by the way kernel firmware wasn't installed
adamk_: tmpuser: Alright, either unload the radeon and drm modules, and try starting X again, or simply reboot, and see if it works now.
adamk_: Cause it definitely won't work without that package.
tmpuser: still nothing. reading xorg's log it seems i miss this file: /usr/lib/dri/swrast_dri.so
tmpuser: can this be related to my problem?
beer: is it true that radeon hd does not support 3 screens that is connected to 3 different radeon 4350 grapics cards using Xinerama or semelar technology?
beer: if it is true I have 3 of such cards I could donate to the devs if they want those cards
yangman: beer: yeah, multi-card setup isn't supported in general
beer: so if there is a developer of radeonhd that would like 3 cards I would send it to him/her
beer: http://dk.asus.com/products.aspx?l1=2&l2=8&l3=817&l4=0&model=2870&modelmenu=1 <- this is the card
yangman: give the mailling list a ping. it's just not an easy problem to solve, and not so much a lack of hardware access
beer: hmm, seems I am still a bit noobish: I can find the arcive (http://lists.opensuse.org/radeonhd/) but not how to post on it
yangman: you need to sign up to the mailling list and send an email
yangman: it's not a forum ;)
beer: how do it sign op for it?
yangman: send a mail to firstname.lastname@example.org
beer: I did not know that there could be a + in a email adreesse
beer: when I want to send the the mailing list I just send to: email@example.com , right?
yangman: no, firstname.lastname@example.org
shadowmaster: allowing radeonhd to use EXA (drm.ko and radeon.ko loaded, kernel 2.6.31) seems to slow down some things like drawing large popup menus, or scrolling pages on Firefox
shadowmaster: RS780M/RS780MN chipset
adamk: shadowmaster, You're sure that DRI is enabled in the X server?
shadowmaster: well, I have the line "(II) RADEONHD(0): Direct rendering enabled" in the server log
adamk: OK. And, just to double check, does 'xvinfo' show any adapters present?
shadowmaster: "Adaptor #0: "RadeonHD Textured Video"", yes
adamk: OK, so 2D acceleration is working.
adamk: Not sure why it would be so slow.
sdsdsd: hello, i have a Radeon X1200 (r500). What is the best driver for me? (using kernel 2.6.30-1 and 2.6.31, Debian Squeeze)
yangman: radeon or radeonhd will both work
yangman: use whichever you feel has the right feature set for you
shadowmaster: um, I'll check if the slow down happens with the 18.104.22.168 kernel too.
sdsdsd: yangman, with one is better for my card? since i want direct rendering.
yangman: sdsdsd: 3D acceleration is handled by mesa. the xorg driver is irrelevant
sdsdsd: wait a sec
shadowmaster: same slowdown (and some minor flickering, actually) with 22.214.171.124. Doesn't happen if I change the acceleration method to ShadowFB
shadowmaster: using latest radeonhd from the git repository btw
shadowmaster: changing it to ShadowFB also managed to crash my machine while I was trying to reinstall an older build of radeonhd :/
yangman: EXA isn't as optimized as it can be. shadowfb will just feel smoother under certain setup
yangman: try radeon and see if it's better there
sdsdsd: hello, i tried to get direct rendering with radeonhd withlou success, how can you help me? (how can i pick the version of necessary things)
shadowmaster: the link in the topic seems not to be working for me
adamk: sdsdsd, It should really just work on any relatively new distribution without any work.
adamk: sdsdsd, What distribution are you using?
sdsdsd: Debian Squeeze
yangman: shadowmaster: works fine here
shadowmaster: a DNS cache issue then I guess.
sdsdsd: (Until yestarday it doesnt worked, today i have full-upgraded and get some new versions)
sdsdsd: btw i have a Radeon X1200 (r500)
yangman: sdsdsd: pastebin your Xorg.0.log
easy: i've been trying to find out about power management support. anyone know how this is progressing?
shadowmaster: notices that the kernel llog got filled with garbage characters after the X.org crash :/
yangman: easy: waiting on more documentation. it's something that's best suited for KMS in any case
easy: ok thx
adamk: Sounds like your kernel supports KMS but your DDX doesn't.
adamk: sdsdsd, What's the output of 'cat /proc/fb' ?
sdsdsd: 0 VESA VGA 1 radeondrmfb
adamk: Yeah, you probably need to update a few items from source.
adamk: Or you can disable KMS.
sdsdsd: i come back.. sorry
sdsdsd: adamk if i disable kms will i have the direct rendering working well?
adamk: sdsdsd, I *think* direct rendering will work, yes.
adamk: sdsdsd, You can disable it by adding radeon.modeset=0 on the kernel line in grub.
sdsdsd: (adamk, i can use the direct rendering mode, but it is worse than without. It uses 2ghz of processor jus by moving a window)
Commie_Cary: dose radeonhd have decent support for radeon hd 3600 yet?
sdsdsd: wait a minute, please
yangman: Commie_Cary: define "decent"
Commie_Cary: yangman, 3d support near the same levels as flgrx
adamk: No. Nor will it for a while.
yangman: Commie_Cary: that's mesa. DDX isn't relevant
yangman: but it's coming along
adamk: 3D support is available via mesa, but is very preliminary.
adamk: And is not nearly as fast as fglrx.
yangman: spread the word: Mesa handles 3D :3
yangman: spread it
Lenin_Cat: because im tending to want to switch to nvidia
shadowmaster: out of curiosity, if I replace the radeonhd module (radeonhd_drv.so), am I supposed to expect X.org to crash?
shadowmaster: that is, if X.org is running and using it at that time
shadowmaster: um, that's strange then. It had crashed immediately when I cp'd an older version over it.
Lenin_Cat: I always ned to reboot to play some of my fav games
Lenin_Cat: ATI sucks balls :<
adamk: Then switch to nvidia.
sdsdsd: adamk, thank, its a lot better.
sdsdsd: *thank you
adamk: sdsdsd, Cool.
sdsdsd: now cat /proc/fb just have 0 VESA VGA
sdsdsd: i think that is all right right now
adamk: Yep, that disabled KMS.
adamk: And hopefully allowed direct rendering.
adamk: sdsdsd, Let's just double check.
sdsdsd: now i can use xv and the 3D rendering is better. But i still cant play Neverball , xD
adamk: What is the output of 'glxinfo | grep -i render' ?
sdsdsd: direct rendering: Yes
sdsdsd: OpenGL renderer string: Mesa DRI R300 20060815 NO-TCL
sdsdsd: R300? but my card is R500
adamk: Alright, so you are using the correct 3D driver, though that would appear to be a little older than I would expect.
adamk: r300 through r500 cards use the same driver because the 3D core is basically the same.
sdsdsd: i understand
sdsdsd: what is a little older?
sdsdsd: the 3D driver?
adamk: Do you know what version of mesa is installed?
sdsdsd: how to het it?
adamk: Yeah, the 3D driver seems older
sdsdsd: OpenGL version string: 1.4 Mesa 7.5.1
sdsdsd: (how to get a newer driver>)
adamk: Alright, that is the most recent release.
adamk: Is this a laptop?
adamk: This could be an IGP card.
adamk: And Mesa had bug regarding IGP cards recently.
sdsdsd: how can i discover if it is a IGP card?
adamk: What is the output of 'lspci | grep -i vga' ?
sdsdsd: 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series]
adamk: Yeah, the RS cards are IGP.
adamk: sdsdsd, I'm going to refer you to #radeon to find out what version of Mesa does not have this bug, because I really don't know, and I have to get going :-)
sdsdsd: i on #radeon, what does i have to ask?
sdsdsd: What version of MESA doesnt have the IGP bug?
adamk: sdsdsd, Tell them that you are having a problem with slow 3D acceleration, and that you heard that there was a bug regarding IGP chipsets in recent versions of Mesa.
sdsdsd: ok, ty
adamk: I'll be back later.
sdsdsd: ok, thanks
yu_raider: hello, I'm using arch and I get a blank screen when I try launching X with radeonhd driver
yangman: yu_raider: xserver-1.6 defaults to a black screen by default
yu_raider: yangman: so I should try for example kdm instead?
yu_raider: oh ok.
yu_raider: another problem, when I try to switch consoles I get no signal
yangman: GPU and radeonhd version?
yu_raider: radeonhd 1.5, gpu 4850
yangman: is the system frozen then or can you go back to X?
yu_raider: I can
yangman: hm. not sure. don't remember if it's a known problem. certainly not a common one
yu_raider: it shouldn't be much of a problem if I get kdm up and running
yu_raider: thanks for the help, I'm gonna try it now
movidi: i'm under archlinux using radeonhd driver with ati mobility radeon 4330
movidi: i'm using git drivers from the arch aur repository
movidi: I start xserver
movidi: and in this moment(before start xorg-server) if I switch to a console (out of X server) the screen appear in green color
movidi: anyone cognise this error?
SiaCo: Hi, I have Radeon Mobility HD 3670 which I think I'm missing something to get 3D up and running. `glxinfo | grep -i render` gives me direct rendering: Yes; OpenGL renderer string: Software Rasterizer which I suspect isn't correct :p Can anyone point me in the right direction of what I might be missing?
yangman: SiaCo: r6xx support isn't in a released mesa version yet
SiaCo: ahh :| I see. Is it being worked on? :)
Sp0tter: Hello, I have a gigabtyte board with the 785G chipset (radeon hd 4200 integrated). Is it possible to use two monitors with one as an extension of the desktop ? I've been reading all over and trying for days with different xorg.conf options and with xrandr, and I can't get anything but clone mode to work.
Sp0tter: I'm using the latest of everything, with Arch Linux.
Sp0tter: sits down on the couch and props his feet up.
yangman: Sp0tter: http://wiki.debian.org/XStrikeForce/HowToRandR12
Sp0tter: yep, i've read that
Sp0tter: many many times
Sp0tter: i've been through the first 200 links on google for anything related to radeonhd, linux duah monitor ati, ect.,ect.. :(
Sp0tter: following that exactly, i am still stuck in clone mode
yangman: Sp0tter: try to put it into dualhead mode, then pastebin the output of xrandr --verbose
Sp0tter: it works now "kidn of", it has them side by side but it locks windows touching the edge of the screen
Sp0tter: i'm going to go haed and install gnome and try it then see if its better
zooko: Greetings, people of #radeonhd! I have just compiled the latest radeonhd driver from git and I still have the same problem that I have had for many months now -- it doesn't detect my monitor unless I set HPD.
zooko: Oh, in fact I seem, to now have a worse problem -- even if I set HPD then it won't start. Hm...
zooko: (EE) RADEONHD(0): RHDDRIVersionCheck: drmOpen("radeon", "pci:0000:02:00.0") fail
zooko: 02:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO]
zooko: ^-- thus say /var/log/Xorg.0.log and lspci respectively
zooko: For what it is worth I also tried disabling atombios when building.
yangman: don't do that. your GPU needs atombios modesetting
yangman: pastebin your Xorg.0.log please
zooko: Will do.
zooko: Just a minute...
zooko: I'm making sure this isn't a different change such as to my x util programs...
zooko: Okay so far I've figured out that I was wrong that the modern git version won't start at all (that was, indeed, a misconfiguration of my x utilities).
zooko: Instead, the radeonhd 1.2.4 from Ubuntu as well as the current git version have similar behavior.
zooko: The new one does give that EE error message and the 1.2.4 one doesn't, but that error message doesn't appear to prevent xserver from starting and doing tex.
yangman: probably just needs a quirk to be added
yangman: that EE is unrelated
yangman: file a bug or ping the maillinglist
yangman: there's a note in Xorg.0.log on what to send
zooko: I'll just turn on "HPD off" again so that I can start even though it doesn't detect my dvi connection
zooko: then I can run a graphical web browser (over the analog connection) to file the bug report. :-)
zooko: I don't see the note in Xorg.0.log saying what to send.
zooko: I'll just send my whole Xorg.0.log.
zooko: send mail to email@example.com
zooko: Thanks, yangman.
lazni: what should I learn in order to code radeonhd?
Diablo-D3: hey all
Diablo-D3: I have a rv770
Diablo-D3: does my card have any 3D support yet?
JohnDoe: Diablo-D3: work in progres
Diablo-D3: wants to get rid of fglrx so badly
Diablo-D3: apparently the BFS sched has ran into a particularly nasty fglrx bug
Diablo-D3: opengl apps stop running after anywhere from a few seconds to several minutes
Diablo-D3: the thread (or entire process if its single threaded) just stops
Diablo-D3: you cant kill it, it wont die, and its not a zombie
Diablo-D3: and its not a bug with BFS
Diablo-D3: the i915 driver hits it as well due to it's usage of threads