You are not logged in.
Pages: 1
Hello Arch community,
I have Probook 4530s with Intel and discrete ATI on board, and I'm not satisfied with gnome shell performance.
When I dragging some window all around, it feels like it's not smooth enough - unconsistent lags here and there. Gnome-shell process raises to 15-20 CPU percentage.
Especially when I moving window to another monitor or "touching" dock, which also animated.
Other than that - smooth scrolling in Firefox, not bad overall performance.
I tried to enable gnome-shell with ATI card, but failed.
What should I look at?
Thanks.
Offline
You should look at why running gnome on the ATI card fails.
Offline
I use open source drivers for videocards. Dunno how to switch graphics with this ones.
Catalyst control center could help, but my xserver is 1.17 (unsupported by current AUR's "catalyst" package. Installing "catalyst-test" makes gdm unbootable).
Found many instructions how to disable discrete video, while I need exactly opposite.
Offline
Para todos todo, para nosotros nada
Offline
Bumblebee requires proprietary drivers, didn't try PRIME though. I'll check it
Offline
Maybe I did not understand PRIME well, but it's like outsourcing OpenGL rendering to discrete card?
Ok, but I need the whole gnome being processed by ATI.
Offline
Compiled linux-ck with BFS scheduler, dont's see any changes.
Offline
Made gnome-shell and X "good" with verynice.
Lowered resolution to 800x600 - still lags.
Just want to know - is it how Intel works with Mutter? Is it considered "normal" with embedded graphics?
I have a virtualbox with Windows, and moving/dragging there is perfect though it's provided by this Intel graphics.
Offline
Installed KDE, it's fast and smooth. Probably problem was Mutter indeed.
Offline
Just want to know - is it how Intel works with Mutter? Is it considered "normal" with embedded graphics?
I have a virtualbox with Windows, and moving/dragging there is perfect though it's provided by this Intel graphics.
Works well on my rig: i7 Haswell Mobile. No lag, standard 60 fps in glxgears, no screen tearing in VLC @ 1920 x 1080 w/1080p videos. Word of caution: Do not use the current Intel GPU sna/uxa 'fix' that is populating various Arch-based distro forums. It does not apply to GNOME 3.16 which uses Wayland by default. You can default to Xorg if you want, but Wayland works better with this chipset IMO.
Regards.
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
Works well on my rig: i7 Haswell Mobile. No lag, standard 60 fps in glxgears, no screen tearing in VLC @ 1920 x 1080 w/1080p videos. Word of caution: Do not use the current Intel GPU sna/uxa 'fix' that is populating various Arch-based distro forums. It does not apply to GNOME 3.16 which uses Wayland by default. You can default to Xorg if you want, but Wayland works better with this chipset IMO.
Regards.
Videos are fine, 60 fps in gears too.
I noticed that lags are most noticeable when I drag some window and "touch" something like Gnome Dash (I use Dash-to-Dock extension with intellectual hiding) with it.
Dash is starting to animate hiding down, or when I touch upper panel which has autohide too. Or when I move window to second monitor. CPU raises to 30% at that time.
Funny thing: on my second monitor vsync is not working while main screen is fine.
What do you mean by using this fix? Using TearFree and sna/uxa in 20-intel.conf? I tried it, removed it eventually.
I don't use Wayland, it's too buggy. No Desktop icons working, mouse cursor lagging, right-click in terminal misplaced, remmina doesn't work at all, etc.
By default? Xwayland is half the solution. Pure wayland by default in GDM only.
At some point I think that Gnome is pretty smooth, but then I come home to my main PC, which has Arch w Gnome too, and I see REAL smoothness and 60 fps by feel.
Thanks for the reply.
Offline
Another thing: Uninstalling xf86-video-intel package has no impact on performance.
How can I be sure that this driver is ever used?
Offline
Word of caution: Do not use the current Intel GPU sna/uxa 'fix' that is populating various Arch-based distro forums.
I don't know what that's got to do with the issue at hand. Using UXA is a decent enough workaround for various graphical glitches that occur when using SNA with some versions of Intel Graphics. I don't think anybody claimed that switching to UXA would boost performance. In fact, the opposite would be true in that case.
Offline
I don't see any glitches, it's just overall sloppy performance. Stutters here and there.
Switching between UXA and SNA doesn't make any changes either.
Offline
bfg9800gt wrote:Just want to know - is it how Intel works with Mutter? Is it considered "normal" with embedded graphics?
I have a virtualbox with Windows, and moving/dragging there is perfect though it's provided by this Intel graphics.Works well on my rig: i7 Haswell Mobile. No lag, standard 60 fps in glxgears, no screen tearing in VLC @ 1920 x 1080 w/1080p videos. Word of caution: Do not use the current Intel GPU sna/uxa 'fix' that is populating various Arch-based distro forums. It does not apply to GNOME 3.16 which uses Wayland by default. You can default to Xorg if you want, but Wayland works better with this chipset IMO.
Regards.
You asked a direct question and I answered it directly. In referencing the sna/uxa 'fix' I meant that GNOME 3 & GDM defaults to Wayland on a vanilla Arch install. No further Xorg configuration is necessary with Intell HD 4400 chipsets such as mine. "Fixes' such as you will see pertaining to KF 5 & Plasma, screen-tearing 'fixes' etc. in other forum areas here and thereabouts. If that does not apply to your situation--and I don't run it in a virtual box so I'm no help to you there--then glean what you will from my post. Or not.
Regards.
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
You asked a direct question and I answered it directly.
Are you replying to yourself? Can't understand your quotation.
I don't run it in a virtual box
Virtualbox is Arch host with windows guest.
GNOME 3 & GDM defaults to Wayland on a vanilla Arch install
I got it. Probably you can't help here.
No further Xorg configuration is necessary with Intell HD 4400 chipsets such as mine
You just said Wayland is "default". Why do we need xorg then?
then glean what you will from my post. Or not.
Thanks granddaddy. I will.
I'm no help to you
Finally you're totally right.
Offline
Contain your saussages, gentlemen! It's bbq season and there are Germans around!
A short search for your problem told me, that other people are also having problems with Gnome 3.16, Intel chips and X.org. If you use GDM, then it probably runs on Wayland, not X. I'm currently not on Gnome, so I cannot tell you how to tell Gnome what to use. However, the following tests come to me as obvious:
1. Start Gnome without GDM (xinitrc + startx) and see if the lag persists. I had this problem recently with SDDM+KDE and while those are two totally unrelated systems, a DM transitioning to a new graphic stack should be ruled out as the culprit.
2. Whatever backend you use, test the other backend. Gnome is currently in a transition to fully support Wayland ASAP, so regressions are to be expected.
Offline
Contain your saussages, gentlemen! It's bbq season and there are Germans around!
A short search for your problem told me, that other people are also having problems with Gnome 3.16, Intel chips and X.org. If you use GDM, then it probably runs on Wayland, not X. I'm currently not on Gnome, so I cannot tell you how to tell Gnome what to use. However, the following tests come to me as obvious:
1. Start Gnome without GDM (xinitrc + startx) and see if the lag persists. I had this problem recently with SDDM+KDE and while those are two totally unrelated systems, a DM transitioning to a new graphic stack should be ruled out as the culprit.
2. Whatever backend you use, test the other backend. Gnome is currently in a transition to fully support Wayland ASAP, so regressions are to be expected.
Oh, greetins fine gentleman!
You choose your session right in the GDM, and then it opens in another tty. GDM is always running, not just transforming into user session.
I use GDM, but just "GNOME" session, no Wayland around. For me it's currently unusable. Looking forward 3.18 though.
1) You mean totally without display manager? Ok I'll test it. Also tried sddm and lightdm. Oh and when Arch in a windows guest, GDM brakes hardware acceleration: https://bbs.archlinux.org/viewtopic.php?id=197372
2) I understand it. But I use Arch at work, and having stable system is crucial for me. With all that bugs, lags and broken RDP client it's totally unusable.
Thanks for the reply.
Offline
Contain your saussages, gentlemen! It's bbq season and there are Germans around!
Had to chuckle at that one!
Regarding GDM, it does indeed default to Wayland but you can force the use of X instead if that helps, see GDM#Use Xorg backend.
Offline
If I may ask a dumb question...
I'm running Gnome 3.16 and do not even know weather I'm using Wayland or Xorg.
I see that I'm able to choose between Wayland or a default Gnome session during login, but pacman -Qs xorg-server is giving me the same output on both logins.
Last edited by Rickrock (2015-07-31 13:19:56)
Offline
If I may ask a dumb question...
I'm running Gnome 3.16 and do not even know weather I'm using Wayland or Xorg.I see that I'm able to choose between Wayland or a default Gnome session during login, but pacman -Qs xorg-server is giving me the same output on both logins.
You should start new thread.
GDM always has Wayland, unless configured specifically. Gnome-session with "GNOME" option in GDM starts with Xorg. "Gnome on Wayland" start gnome-session on Wayland.
Installed packages are just installed packages.
Last edited by bfg9800gt (2015-07-31 12:16:49)
Offline
Awebb wrote:Contain your saussages, gentlemen! It's bbq season and there are Germans around!
Had to chuckle at that one!
Regarding GDM, it does indeed default to Wayland but you can force the use of X instead if that helps, see GDM#Use Xorg backend.
Give a break to GDM, gnome shell is the issue.
It's just the guy who said "Wayland in Gnome is by default" probably came from future.
Offline
Guys, I would like to know how to disable window-to window snapping in Gnome. This thing is also annoying as puck and feels like lagging.
Is there a way to disable this?
This dude also has the same problem, unanswered: http://superuser.com/questions/948202/h … -3-desktop
Last edited by bfg9800gt (2015-08-03 09:00:52)
Offline
Pages: 1