Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 05/31/2017 04:41 PM, Anil Duggirala wrote: [snip] ... Is it possible that installing Mate caused trouble of some sort. ... I appreciate any help. For now, my plan, when I have time, is to reinstall Debian Stretch, dont touch anything and configure to load intel driver, and hope that any

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On Wed, 2017-05-31 at 19:50 +, Curt wrote: > On 2017-05-31, Anil Duggirala wrote: > > > > Hello, > > I was just wondering if you could confirm that I am now using the > > intel > > driver, I dont know how to check this in my Xorg log. I am still > > having > >

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 01/06/17 02:25, Greg Wooledge wrote: I have pasted my Xorg.log here https://paste.debian.net/955691thanks a lot, Please make sure you put whitespace after the URL. From https://paste.debian.net/955691 : Or surround the URL with angle brackets likethis to

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On Wed, May 31, 2017 at 07:50:09PM +, Curt wrote: > This used to grep accurately for the pertinent info (if things haven't > changed--I'm still on Wheezy (asthmatic cough)): > > grep -B4 'Module class: X.Org Video Driver' /var/log/Xorg.0.log > > (adjust path to log to wherever your log is

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 2017-05-31, Anil Duggirala wrote: > > Hello, > I was just wondering if you could confirm that I am now using the intel > driver, I dont know how to check this in my Xorg log. I am still having This used to grep accurately for the pertinent info (if things haven't

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Le 31/05/2017 à 16:25, Greg Wooledge a écrit : On Wed, May 31, 2017 at 09:15:20AM -0500, Anil Duggirala wrote: I was just wondering if you could confirm that I am now using the intel driver, I dont know how to check this in my Xorg log. You simply read it until you find the driver lines.

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On Wed, May 31, 2017 at 09:15:20AM -0500, Anil Duggirala wrote: > I was just wondering if you could confirm that I am now using the intel > driver, I dont know how to check this in my Xorg log. You simply read it until you find the driver lines. > I have pasted my Xorg.log here >

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Hello, I was just wondering if you could confirm that I am now using the intel driver, I dont know how to check this in my Xorg log. I am still having an issue I do believe pertains to Gnome. The Applications menu in Gnome Classic is sluggish at best, as I described before, moving the mouse around

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Hello, I am looking at 2 new threads in my Inbox, which one are we going to follow ??I pasted my new Xorg.log here https://paste.debian.net/945756 The situation has definitely improved, In my previous post (in the other thread) I used the word completely, because I was missing the cp command. I

Re: Poor X performance with Intel 8086:22b1 (Braswell) (was: Oh no something has gone wrong! after...)

> However, in https://lists.debian.org/debian-user/2017/05/msg00767.html he > provided a pastebin (now expired) of Xorg.0.log that reported the > modeset(0) > driver in use. > > https://lists.debian.org/debian-user/2017/05/msg00781.html explained how > he > could try configuring use of the Intel

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Looks like this will probably top-post, or perhaps not have any quoted material...I'm using mobile device at the moment, my apologies. The last time I had to mess with anything Xorg was with the xorg.conf filr, but that may well have been 10+ years ago. I've probably forgotten more than I ever

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Michael Milliman composed on 2017-05-26 20:23 (UTC-0500): > ...Does this cp command overwrite an existing > xorg.conf. AIR, the xorg.conf is no longer required (of course I've > slept several times since I think I saw that :) ). xorg.conf is an optional file that is unnecessary and not present

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 05/26/2017 08:03 PM, Felix Miata wrote: > Michael Milliman composed on 2017-05-26 19:40 (UTC-0500): > >> OK, so the question is, since he is using the default modeset(0) driver, >> what can he do,if anything, to install and try the Intel driver instead >> and see if it works better? > > In

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Michael Milliman composed on 2017-05-26 19:40 (UTC-0500): > OK, so the question is, since he is using the default modeset(0) driver, > what can he do,if anything, to install and try the Intel driver instead > and see if it works better? In

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 05/26/2017 07:35 PM, Felix Miata wrote: > Michael Milliman composed on 2017-05-26 19:06 (UTC-0500): > >> I hadn't checked the posts in the pastebin. As I >> stated, the problem is a little over my head at this point, so I'm not >> sure what the modeset(0) driver being in use actually means,

Re: Poor X performance with Intel 8086:22b1 (Braswell)

Michael Milliman composed on 2017-05-26 19:06 (UTC-0500): > I hadn't checked the posts in the pastebin. As I > stated, the problem is a little over my head at this point, so I'm not > sure what the modeset(0) driver being in use actually means, as the OP It means he's most likely using the

Re: Poor X performance with Intel 8086:22b1 (Braswell)

On 05/26/2017 06:59 PM, Felix Miata wrote: > Michael Milliman composed on 2017-05-26 18:18 (UTC-0500): > >> ...someone mentioned checking if the package >> xserver-xorg-video-intel was installed on your system. This package >> should be installed if it is not. > > He already reported in >

Re: Poor X performance with Intel 8086:22b1 (Braswell) (was: Oh no something has gone wrong! after...)

Michael Milliman composed on 2017-05-26 18:18 (UTC-0500): > ...someone mentioned checking if the package > xserver-xorg-video-intel was installed on your system. This package > should be installed if it is not. He already reported in https://lists.debian.org/debian-user/2017/05/msg00785.html