Page 2 of 4

Re: MX is slow after last update [Solved]

Posted: Wed Oct 01, 2014 2:55 am
by jerry525
lucky9 wrote:boot into init 3 and run sgfxi as root
you might have to do this twice
Sorry I am not very technical, can someone explain how to do this please.

Re: MX is slow after lqast update

Posted: Wed Oct 01, 2014 11:34 am
by Stevo
Don't bother with sgfxi, it's good for detecting and making sure the system is using the driver for Intel graphics, but you're already using the Intel driver. We can check what driver is installed with

Code: Select all

apt-cache policy xserver-xorg-video-intel
If it's the backports version, we can try going back to the standard Wheezy version and see if that fixes it.

Re: MX is slow after lqast update

Posted: Wed Oct 01, 2014 2:45 pm
by jerry525
Ok thanks for that.

Code: Select all

$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.21.15-2~bpo70+1
  Candidate: 2:2.21.15-2~bpo70+1
  Version table:
 *** 2:2.21.15-2~bpo70+1 0
        500 http://ftp.uk.debian.org/debian/ wheezy-backports/main i386 Packages
        100 /var/lib/dpkg/status
     2:2.19.0-6 0
        500 http://ftp.uk.debian.org/debian/ wheezy/main i386 Packages
Do I just unselect the backports repo ijn synaptic then update?

Re: MX is slow after lqast update

Posted: Wed Oct 01, 2014 3:03 pm
by kmathern
The following should downgrade it. It's a simulation. If the simulation looks okay remove the "-s" and run it again for real. {post the output of the simulation if you're unsure}

Code: Select all

su -c 'apt-get install xserver-xorg-video-intel/wheezy -s'
After downgrading it you'll need to pin it so it doesn't upgraded again. You can do that in Synaptic, or you can use the apt-mark hold cli command :

Code: Select all

su -c 'apt-mark hold xserver-xorg-video-intel'

edit: after doing the downgrade you'll also need to restart X or do a shutdown/restart to see if the downgrade fixed the slowdown problem.

Re: MX is slow after lqast update

Posted: Wed Oct 01, 2014 3:14 pm
by jerry525
Yes pls check the simulation output for me:

Code: Select all

$ su -c 'apt-get install xserver-xorg-video-intel/wheezy -s'
Password: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '2:2.19.0-6' (Debian:7.6/stable [i386]) for 'xserver-xorg-video-intel'
The following packages will be DOWNGRADED:
  xserver-xorg-video-intel
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Inst xserver-xorg-video-intel [2:2.21.15-2~bpo70+1] (2:2.19.0-6 Debian:7.6/stable [i386])
Conf xserver-xorg-video-intel (2:2.19.0-6 Debian:7.6/stable [i386])

Re: MX is slow after lqast update

Posted: Wed Oct 01, 2014 3:17 pm
by kmathern
It's correct. (it will downgrade the xserver-xorg-video-intel package to the 2:2.19.0-6 version)

Re: MX is slow after last update [Solved]

Posted: Wed Oct 01, 2014 3:52 pm
by jerry525
Worked an absolute treat!

I'm so pleased & relieved. :happy:

Many thanks for your and everyone else's help.

Re: MX is slow after lqast update

Posted: Fri Oct 03, 2014 9:10 am
by Richard
Thank you all for this fix for a problem I didn't realize I had.

Hadn't been on the desktop much over the last few weeks.
Just thought it was slower than it used to be; however,
it was still faster than the netbooks so I just adapted.

Re: MX is slow after lqast update

Posted: Fri Oct 03, 2014 12:53 pm
by Stevo
That's too bad about the new driver messing things up. What Intel chipsets has it affected badly so far? And is there anyone using it successfully?

Also, what exactly do you mean when you say the system has slowed down? Are screen redraws slow, and does "top" in the terminal show xorg eating all your CPU cycles?

Re: MX is slow after lqast update

Posted: Fri Oct 03, 2014 1:23 pm
by lucky9
My Acer One D-250 (Atom single-core with HT, 2 GB RAM) hasn't had a problem that I'm aware of. However I'd have to check to see if this upgrade was made on it as I don't upgrade it very often. Last time was on 9/13.
Is it possible that something connected to the Intel driver wasn't configured correctly (or even upgraded)?