You are not logged in.
what are your experiences with the RC released to testing?
my take: ive got a laptop with a 1280x800 lcd, an external @ 1680x1050 and a tv (vga input) @ 1280x733 or something like that. i dont use both outputs at the same time.
when i use the bigger screen, everything works ok. but when i use the laptop's LCD or the TV, xorg redraws every 5 seconds making things unbearable. this is without KMS.
has anyone experienced this? any other bugs you found? how did you hack around them?
for now, i just reverted to 2.7 which still has EXA support.
Offline
It now performs better than the legacy driver for me, although I have not tested running on my TV screen yet.
Offline
It now performs better than the legacy driver for me, although I have not tested running on my TV screen yet.
yes, when it works ok, it performs better
my first workaround.
xorg redraws every 5 seconds, when compiz is running without --indirect-rendering, using that option makes the display work. on the laptop's lcd and big screen. still need to test the tv
please allan, test with and without that option.
EDIT: tested LCD tv and it works ok with indirect rendering.
one extra update, since kernel 30 and 2.8rc we get vga hotplugging support. tested this with the tv and the 20' monitor and it detected both correctly when plugged and xorg already started. this never worked before..
Last edited by eldragon (2009-06-17 18:40:08)
Offline
Why don't you enable KMS? Do you have problems with it?
I ask because for me UXA without KMS used to give me troubles (suspend to ram was broken, for example). Besides, KMS will be the only option soon, if I'm not mistaken, so better star testing it now and get everything fixed.
Offline
Why don't you enable KMS? Do you have problems with it?
I ask because for me UXA without KMS used to give me troubles (suspend to ram was broken, for example). Besides, KMS will be the only option soon, if I'm not mistaken, so better star testing it now and get everything fixed.
KMS + suspend = crash and burn
if you can suspend, please drop relevant information so that i can do some testing (how do you enable kms?) , since there are numerous bugs concerning suspend, i decided not to pursue the issue further until new versions of sowftware came along... still cannot suspend.
Offline
Strange that suspend works for you with UXA+UMS but not with UXA+KMS. In fact, KMS is supposed to make suspend more reliable.
I enable it in the usual way. By adding i915.modeset=1 to the kernel line in grub (I have MODULES="intel_agp drm i915" in /etc/mkinitcpio.conf - make sure you rebuild your kernel image if you didn't have them added before).
Apart fro that I do nothing special. Suspend just works.
Offline
Are you using an xorg.conf? I'm running without one and it is very good. Indeed the TV out worked automatically without and it didn't when I had xorg.conf.
Satisfied users don't rant, so you'll never know how many of us there are.
Offline
im using a xorg.conf but nothing related to display in there..
about kms, it fails miserably to suspend. and its not related to xorg since it fails even when done through init 3 (aka no xorg running)
there are several bugs reported against kms and suspend, so i guess i must be struck by one of those...
EDIT: ive tried kms without compiz, and suspend works so far. maybe its compiz that needs to catch up
Last edited by eldragon (2009-06-19 00:57:59)
Offline
I have a GM945. The package in testing works perfectly with the new kernel. Suspend to disk and suspend to ram work perfectly. Compositing works well (tested only with the KDE from [kde-unstable]), all crashes are gone. I haven't used KMS yet as I didn't have much time to play around with it. I also don't use a xorg.conf.
Offline
im trying to figure out why suspend is such a *** here with KMS, and everything points out to compiz.
ive been running different tests, and i found out, that if executed using /usr/share/applications/compiz.desktop , suspend fails to resume.
but if i use the fusion-icon method, it works without problems (extra testing needed).
ive tried to emulate fusion-icon's behaviour using its exact command to execute compiz. still it does not work.
for the curious, its being executed with:
compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering
why i bother: using fusion-icon makes the WM exeute twice.
Offline
Man, you guys are making want to enable the testing repo again...
EDIT: well, it WORKS, but I've still got the cracked-out transparency issues that happened when I tried KMS before (things go white instead of just slightly transparent, for example).
Arch64, GM945, no xorg.
Last edited by SomeGuyDude (2009-06-19 13:18:22)
And in the midst of such perfection,
I can't help but feel diseased.
Offline
Suspend works fine for me, except that the mouse cursor seems to be messed up after resuming. But that usually fixes itself after a couple of mouse clicks.
Offline
Man, you guys are making want to enable the testing repo again...
EDIT: well, it WORKS, but I've still got the cracked-out transparency issues that happened when I tried KMS before (things go white instead of just slightly transparent, for example).
Arch64, GM945, no xorg.
check this thread i started here... wanna help me build mesa with the patch?
Offline
Suspend works fine for me, except that the mouse cursor seems to be messed up after resuming. But that usually fixes itself after a couple of mouse clicks.
Got the same problem:
The cursor design looks like rubbish after resuming from suspend to ram. Unfortunately on my notebook a couple of mouse clicks do not fix it...
Offline
Running Debian Sid here with custom 2.6.30kernel+2.7.99intel and everything works fine now. With older kernels the system is unstable when running KMS.
Performance is.... well, regular. Looks great and smooth on the LVDS (1280x800) but a bit choppy on external VGA (1920x1080).
My blog: blog.marcdeop.com
Jabber ID: damnshock@jabber.org
Offline
GogglesGuy wrote:Suspend works fine for me, except that the mouse cursor seems to be messed up after resuming. But that usually fixes itself after a couple of mouse clicks.
Got the same problem:
The cursor design looks like rubbish after resuming from suspend to ram. Unfortunately on my notebook a couple of mouse clicks do not fix it...
What desktop environment do you use and how do you suspend?
I was having the problem too in my testing partition where I have KDE 4.3-beta1, so I thought it was its fault. If instead of using the suspend to RAM button I suspend from the command line it doesn't happen ("pm-suspend" as root if you have pm-utils installed, otherwise just "echo -n mem > /sys/power/state").
Last edited by Bogart (2009-06-19 16:49:23)
Offline
Bogart:
I'm on KDE 4.3-svn and the only suspend-mode that works for me is Suspend-2-RAM. And yeah, I pressed the Suspend-2-RAM-button from KDE's menu :-D
I also only use a minimal xorg.conf, which only contains the dontzap option.
Offline
all methods ive tried suspending with KMS + compiz are unreliable....
gonna testdrive metacity to death tomorrow.
ive already got rid of xorg.conf and still nothing.
Offline
Most of my issues have gone now which is probably has a lot to do 2.6.30 i915 changes, as well as the intel driver (running kms on x86_64). I'm still getting a few keyboard/system freezes which the screen suspends but this seems to make most of that go away:
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection
I guess there are stll some memory leaks in xorg, so I expect issues if a haven't rebooted for a while.
$ sudo pmap `pidof X` | wc -l
1508
Offline
i'm also seeing freezes with and without KMS enabled. They can be easily triggered by running xscreensaver-demo and browsing through the available screensavers. it's not a particular screensaver that makes X crash. it just happens after some time ...
ccc1
Offline
Man, you guys are making want to enable the testing repo again...
EDIT: well, it WORKS, but I've still got the cracked-out transparency issues that happened when I tried KMS before (things go white instead of just slightly transparent, for example).
Arch64, GM945, no xorg.
managed to finally patch mesa. running compiz with direct rendering and the patch applied fixes the transparency bug. /me is happy
Offline
i'm also seeing freezes with and without KMS enabled. They can be easily triggered by running xscreensaver-demo and browsing through the available screensavers. it's not a particular screensaver that makes X crash. it just happens after some time ...
ccc1
You should open a bug report on bugs.freedesktop.org as the intel developers have closed a number of bugs related to freezes which are probably fixed and which noone has commented on recently. They actually sent a message to the mailing list demanding that users who still see freezes report them.
Offline
for everyone having freezes during resume, the patch to the kernel in this this bug report fixed it for me...
and that means:
- KMS enabled
- compiz enabled
- direct rendering
everything works ok. ive got no transparency bug, can suspend and resume succesfully.
ive started a thread on how to patch mesa and fix the transparency bug. its here
Last edited by eldragon (2009-06-23 12:42:39)
Offline
I am impressed with the new Intel driver in conjunction with the new kernel.
I have KMS activated. For the first time, I can run KWin effects in KDE4 at a reasonable speed; X and KDE4 start at an impressive speed.
However, I cannot switch back to X from; when I switch to TTY and then go back to X, nothing happens, the screen stays black.
Also, I have the feeling as if my resolution in TTY is not detected correctly. It does not look like 1024x768.
EDIT: I have just try suspend (to RAM), and both suspending and waking up from suspend are fast. If during the next 5 minutes my system does not freeze, I am happy.
My system: Intel 945GM
EDIT2: My system didn't freeze; makes me even more happy. Switching back and fro between X and TTY still not working tho'. Ah, if I go from X to TTY and then actually restart X, X will work fine again.
Last edited by Stalafin (2009-06-23 14:06:15)
Offline
Also, I have the feeling as if my resolution in TTY is not detected correctly. It does not look like 1024x768.
do you have a 1024x768 screen? otherwise it should be your native display's resolution.
i get a 1280x800 tty screen
Offline