airlied: wonders why radeonhd would work different..
airlied: probably something in probe functions different..
rx__: it uses atombios to init
rx__: that should be same right?
airlied: rx__: this isn't anything to do with atombios..
airlied: rx__: its to do with X.
kdekorte: I have a weird issue but I'm not sure where it is (radeon driver, atom bios branch, EXA acceleration mode). I open Nautilus and switch to icon view and the background is a random pastel color. Does not happen in XAA mode
kdekorte: Any idea what could be causing that on F8?
jra: has anyone experience with "(EE) RADEON(0): Idle timed out, resetting engine..."?
jra: It's a Radeon32. X starts, screen goes off, ctrl-alt-bksp doesn't work... ctrl-alt-del does a normal shutdown and reboot
jra: I'm really beginning to suspect the hardware. A Rage128 and a Radeon9250 work fine with the same xorg.conf.
osiris_: jra: are you using atombios support branch?
libv: radeon32 seems like one of the very early ones
jra: The first, to be precise ;)
osiris_: jra: have you always been expiriencing this problem?
jra: no, only since xorg-server 1.4. but it's always after starting the computer, and after so many restarts it'll eventually vanish
Magnade: jra: does number of restarts help or just waiting a while and letting it warm up help?
Magnade: jra: might help to narrow it down if it is the hardware
jra: Yes. I put the card in a different pc and will try it there. Same distribution, same xorg/driver-versions. So far I'm on the "warmup" side.
airlied: kdekorte: bug in server.. I've been meaing to fix.
airlied: jra: using AGP? if so try option "bustype" "PCI"
kdekorte: airlied, which one is that the coloring issue?
airlied: kdekorte: yes.. exa issue
kdekorte: airlied, it only seems to appear in nautilus for me, I'm sure it pops up somewhere else, but it doesn't bother me much
dli_: airlied, success report, lcd panel brightness keyboard control works in radeon. this feature is still not on ToDo list for radeonhd
kdekorte: dli_ that is primarily why I am using radeon over radeonhd, brightness support and dpms working properly on my T60p
dli_: kdekorte, and lid close&open?
kdekorte: yes, that seems to work as well
kdekorte: I believe the lid close is a hardware switch so no matter the driver, the backlight will go off
dli_: kdekorte, lucky you
kdekorte: ha... I just tried it
kdekorte: and it does crash my display
kdekorte: using the radeon driver
dli_: kdekorte, right, the same here
kdekorte: I thought I had tried it the other day
kdekorte: switching to console and back fixes it
dli_: kdekorte, radeonhd fixed this on 10/08 for me
kdekorte: does dpms work on radeonhd for you?
kdekorte: dpms is important for me since I never shutdown my laptop during the week, so I want to make sure the display at least goes quiet
dli_: kdekorte, according to the log, dpms is enabled
dli_: kdekorte, radeonhd also enables it by default
kdekorte: right, but on radeonhd, the screen never goes dark on radeon it does
kdekorte: even though dpms is enabled on both
dli_: kdekorte, I got the screensaver + mplayer problem, so I disabled screensaver
kdekorte: what is that problem?
kdekorte: where the screen saver runs even though mplayer is running
dli_: kdekorte, mplayer couldn't turns screensaver auto
dli_: kdekorte, right, very nasty problem.
dli_: kdekorte, it could be a problem for xfce
Magnade: problem is gnome and kde use diff screensaver interfaces and mplayer doesn't want to bother implementing them
Magnade: that is both of them
dli_: Magnade, which one works for mplayer?
kdekorte: mplayer from my experience disables dpms while running. My own gnome-mplayer tells gnome-screensaver to go into inhibit mode
Magnade: dli_: dont recall i dont like screensavers so its diabled and not an issue for me...
dli_: kdekorte, I will try gnome, got to nuke ~/.gconf* ~/.gnome*, because gnome starts only as failsafe now
kdekorte: All my screen saver does is blank screen and then I have gnome-power-manager turn off the screen at the same time
Magnade: blank screens make for hard irc reading when your idling and working on something else
kdekorte: if I have not touched the keyboard for 30 mins, I'm probably not looking at it anyway
kdekorte: I have two machines and I'm constantly moving between them
Magnade: ive tried long timeout it always seems to be wrong so its off
kdekorte: Since I work at home, if I see the screen dark it is a reminder to me that I should not be working...
LuGaLbAnGa: hi all
LuGaLbAnGa: I can't activate 3d support with my x600 mobility radeon
LuGaLbAnGa: I'm using opensuse 10.3
LuGaLbAnGa: and I already installed and uninstalled fglrx, and before I did that 3d support was working
mcgreg: please paste yopir xorg.0.log to some paste vservice
LuGaLbAnGa: any clues on how can I put it to work?
mcgreg: please paste yopir xorg.0.log to some paste service <-- might make guessing easier
LuGaLbAnGa: mcgreg, sure.. just a sec
LuGaLbAnGa: perhaps you want the result of glxinfo as well?
mcgreg: not yet
mcgreg: what the heck is that?
LuGaLbAnGa: it's my /var/log/Xgl.0.log
mcgreg: /var/log/Xorg.0.log <-- this one please
sheek__: mcgreg, I was LuGaLbAnGa
mcgreg: /var/log/Xorg.0.log <-- this one please
sheek__: here is the correct log http://pastebin.ca/index.php
sheek__: sorry http://pastebin.ca/805016
LuGaLbAnGa: any clue?
mcgreg: so, it looks it should work as (II) RADEON(0): Direct rendering enabled
mcgreg: as you use Xgl , this might be the problem
mcgreg: dont use Xgl
dli_: use radeon + aiglx
LuGaLbAnGa: where can I change that?
dli_: fglrx sucks, xgl sucks, not sure which one does more
LuGaLbAnGa: I didn't know I were using xgl
mcgreg: well, I guess, he used xgl for fglrx driver to get compiz working ;)
LuGaLbAnGa: mcgreg, if I uninstall the xgl package it should be working then?
LuGaLbAnGa: so radeon and xlg are not compatible?
mcgreg: not really
mcgreg: dli_ said it, xgl sucks :)
LuGaLbAnGa: well, the reason I uninstalled ati proprietary graphics was because as soon as I installed them desktop effects stoped working and I never got them to work with that graphics
LuGaLbAnGa: got any clue why was that?
LuGaLbAnGa: (since 3d support is not complete to my card)
mcgreg: well, again as dli said, fglrx sucks (too) ... it is not yet very stable and has't good 3d support. it is very buggy
mcgreg: recently it got aiglx support, but noit complete. the 3d performance is quite good though
LuGaLbAnGa: but now that fglrx has aiglx support... isn't that a solution?
mcgreg: but the worst problem of all is, it leaks A LOOT of memory when using opengl/3d stuff
dli_: LuGaLbAnGa, if you don't want to become a driver/kernel/X debugging expert, don't use fglrx
zePh7r: mcgreg, seems like I still don't have 3d support
zePh7r: I restarted the computer
mcgreg: restarting X would be enoigh
mcgreg: you actually (almost never) need to restrart the whole damn thing
zePh7r: yeah, just for kernel updates
mcgreg: what does glxinfo says?
zePh7r: but they say restarting x with ctrl+alt+backspace is dangerous (don't know in each way but...)
mcgreg: hmm? but you still can simply log out, and then restart X
zePh7r: loging out itself wouldn't restart x?
mcgreg: no, but log out, then ctrl+alt+backspace
zePh7r: by the way, I am LuGaLbAnGa
zePh7r: mcgreg, please take a look at my glxinfo
mcgreg: ok, I guess you need to configre the rights
zePh7r: what rights?
mcgreg: Section "DRI"
mcgreg: Mode 0666
mcgreg: to your xo0rg.conf if you havent
zePh7r: to my xorg.conf?
zePh7r: take a look at my xorg.conf http://pastebin.com/m2dffc34f
zePh7r: as you can see, it is already in there
zePh7r: ah forget it, its 0660
mcgreg: well, I gacve you 0666, there is 0660 dunno if that is a difference though
mcgreg: try it with 0666 please
mcgreg: then we'll see
zePh7r: done, going to restart x
LuGaLbAnGa: mcgreg, it now works
LuGaLbAnGa: man, I would have never guessed
LuGaLbAnGa: what did it change exactly?
mcgreg: the rights.. probably it was set so only root had the right to access the drm .. but honestly I dont know :) I am not an expert to this :) I dont know much more than you do about this stuff :)
LuGaLbAnGa: oh well... I would never solve this by myself
mcgreg: if this hadn't worked, I'd be soon out of idea though ;D
mcgreg: and I only knew this, because I had this problem some time ago too ... (a few years I guess)
LuGaLbAnGa: it was here though... http://dri.freedesktop.org/wiki/DriTroubleshooting#head-e217f9d56159347d24d9b33b0aaf2e631482482d
LuGaLbAnGa: I had a clue it was dri related, but couldn't know for sure
LuGaLbAnGa: mcgreg, but how did this got into my xorg.conf?
LuGaLbAnGa: did sax2 generate a bad file?
LuGaLbAnGa: why would it not give permissions to run dri from userspace?
mcgreg: no idea.. never used anything else than debian and gentoo. maxbe you did it manuallya and typo'ed?
LuGaLbAnGa: no, i never entered that section manually...
LuGaLbAnGa: what about the group "video"... should that be a problem too?
mcgreg: dont think so .. but if you feel better, you can remove it from there :)
LuGaLbAnGa: lol ok
LuGaLbAnGa: well, I'm glad it could be solved
LuGaLbAnGa: thanks a lot for the help mcgreg
mcgreg: you're welcome