LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-16-2016, 04:53 PM   #46
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled

Hi,

Quote:
Interesting that DRI 3 reports 'SNA initialized with Skylake (gen9) backend' whereas others report a 'generic' backend.
Probably, because it has appeared here for the first time, which is many commits ahead of d167280.

--
Best regards,
Andrzej Telszewski
 
Old 04-16-2016, 05:00 PM   #47
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Rep: Reputation: Disabled
Odd. Skylake is 6th gen, not 9th
 
Old 04-16-2016, 05:07 PM   #48
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by lazardo View Post
Odd. Skylake is 6th gen, not 9th
Are you sure?

I'm on Broadwell and seem to have correct report:
Code:
$ grep -i gen8 /var/log/Xorg.0.log
[     8.324] (II) intel(0): SNA initialized with Broadwell (gen8) backend
--
Best regards,
Andrzej Telszewski
 
Old 04-16-2016, 05:19 PM   #49
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Rep: Reputation: Disabled
'intel skylake "6th generation" site:intel.com' produces 4K hits vs 1 if '9th' is substituted, but I've seen it both ways. Marketing vs software?

Interesting. Seems to depend on max DRI:
Code:
$ egrep -i 'gen|skylake' /var/log/Xorg.0.log*
/var/log/Xorg.0.log:[    15.604] (--) intel(0): gen9 engineering sample
/var/log/Xorg.0.log:[    15.630] (II) intel(0): SNA initialized with generic backend
/var/log/Xorg.0.log.old:[    16.293] (--) intel(0): gen9 engineering sample
/var/log/Xorg.0.log.old:[    16.327] (II) intel(0): SNA initialized with Skylake (gen9) backend

Last edited by lazardo; 04-16-2016 at 11:36 PM. Reason: cant type, cant spell apparently
 
Old 04-16-2016, 05:48 PM   #50
archfan
Member
 
Registered: Mar 2016
Location: /dev/hug
Distribution: Slackware 14.2 x64
Posts: 85

Rep: Reputation: 32
Just upgraded to the latest intel-driver from git as the old driver from February is somewhat unresponsive and slow on my Skylake system.

The weird glitches seem to be a thing of the past now, even with DRI3 and SNA enabled.

Quote:
I'm on SNA, since UXA is unacceptably slow in Senmonkey.
Agreed. Avoid UXA at all cost. UXA is pure FOSS crap, secretly invented by Microsoft's underlings. Beware.

Last edited by archfan; 04-16-2016 at 05:57 PM.
 
Old 04-16-2016, 06:02 PM   #51
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled
Hi,

Quote:
the latest intel-driver from git
You mean f2a4645 ?

--
Best regards,
Andrzej Telszewski
 
Old 04-17-2016, 12:50 AM   #52
ppencho
Member
 
Registered: Jan 2004
Location: Bulgaria
Distribution: Slackware64-current
Posts: 94

Rep: Reputation: Disabled
I upgraded to f2a4645 and cannot see the desktop artifacts anymore. Everything looks fine for now.
 
Old 04-17-2016, 07:02 AM   #53
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 598

Original Poster
Blog Entries: 3

Rep: Reputation: 194Reputation: 194
Updated to 14.2RC2 and everything seems fine so far, no more graphical problems. Still using SNA.
 
Old 04-17-2016, 07:32 AM   #54
archfan
Member
 
Registered: Mar 2016
Location: /dev/hug
Distribution: Slackware 14.2 x64
Posts: 85

Rep: Reputation: 32
Quote:
Originally Posted by atelszewski View Post
Hi,


You mean f2a4645 ?

--
Best regards,
Andrzej Telszewski

Correct.
 
Old 04-17-2016, 07:59 AM   #55
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 169

Rep: Reputation: 67
Quote:
Originally Posted by BratPit View Post
One word

Option "TearFree" "true"

is useless with

Option "AccelMethod" "uxa"

it work with SNA
Yeah, well I keep the conf unchanged when I switch between uxa and sna for testing.
Anyway I'm generally using uxa because I use Cairo Dock, which is known to misbehave with sna.

Btw, with 4.6-rc3 and patch from https://bugs.freedesktop.org/show_bug.cgi?id=94161#c28 i915.enable_rc6=0 seems no longer needed and overall temperature stays lower (patch is a workaround rather than a full fix).
 
Old 04-17-2016, 02:08 PM   #56
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled
Hi,

I have automated all the packaging and installation.
Also I have atom feed, so I know when there is a commit and can easily see what has changed.
As of now, I'm at git_20160417_81029be, so far, so good.

The way to type less and upgrade fast:

Note: everything is happening on behalf of the invoking user, only the last step requires root privileges and the script asks for the password.

1. I have generic git fetcher and packager
Code:
$ cat git-get-mksrctarball.sh 
#!/bin/sh

REPODIR=/home/software/src/01-git
PACKDIR=/home/software/src

set -e

ADDRESS=$1
DESTDIR=$2
BRANCH=${3:-master}

if [ -z "${ADDRESS}" ] || [ -z "${DESTDIR}" ]; then
  echo "usage: $0 ADDRESS DESTDIR [branch]"
  exit 1
fi

UMASK=$(umask)
umask 022

cd "${REPODIR}"

if [ -e "${DESTDIR}" ]; then
  cd "${DESTDIR}"
    git checkout master
    git pull -f
  cd ..
else
  git clone "${ADDRESS}" "${DESTDIR}"
fi

cd "${DESTDIR}"
  git checkout "${BRANCH}"
  VERSION="git_$( git log -1 --format=%ad_%h --date=format:%Y%m%d )"
cd ..

cp -a "${DESTDIR}" "${DESTDIR}-${VERSION}"
( cd "${DESTDIR}-${VERSION}" && find . -type d -name ".git*" -exec rm -rf {} \; 2>/dev/null ) || true

umask ${UMASK}
tar -Jvcf "${DESTDIR}-${VERSION}.tar.xz" "${DESTDIR}-${VERSION}"
md5sum "${DESTDIR}-${VERSION}.tar.xz" > "${DESTDIR}-${VERSION}.tar.xz.md5"

rm -rf "${DESTDIR}-${VERSION}"

mv "${DESTDIR}-${VERSION}.tar.xz"     "${PACKDIR}"
mv "${DESTDIR}-${VERSION}.tar.xz.md5" "${PACKDIR}"

echo
echo "${DESTDIR} packaged as ${PACKDIR}/${DESTDIR}-${VERSION}.tar.xz"
echo
echo "PACKAGE=${DESTDIR}"
echo "VERSION=${VERSION}"
echo "TARBALL=${PACKDIR}/${DESTDIR}-${VERSION}.tar.xz"
echo
This script is in my $PATH so I can invoke it from whatever directory.
It expects 2 arguments: git address and directory name.
The branch can be selected with the third argument, if empty, master branch is selected.

The two variables, REPODIR and PACKDIR define, respectively, where the source code from git is downloaded and where the packaged source code is placed.

So, if the script is invoked like that:
Code:
git-get-mksrctarball.sh git://git.freedesktop.org/git/xorg/driver/xf86-video-intel/ xf86-video-intel
and
Code:
REPODIR=/home/software/src/01-git
PACKDIR=/home/software/src
after the script completes, there will be:
a) /home/software/src/01-git/xf86-video-intel git repository,
b) /home/software/src/xf86-video-intel-git_DATE_BRANCH.tar.xz packaged source code.

Also, once the script completes, it prints the following:
Code:
xf86-video-intel packaged as /home/software/src/xf86-video-intel-git_20160417_81029be.tar.xz

PACKAGE=xf86-video-intel
VERSION=git_20160417_81029be
TARBALL=/home/software/src/xf86-video-intel-git_20160417_81029be.tar.xz
The last 3 lines are made so to ease the parsing by another script.

2. Address and directory name for the git repository
That's just a place holder for convenience and it reads like that:
Code:
$ cat /home/software/src/01-git/xf86-video-intel.url 
git://git.freedesktop.org/git/xorg/driver/xf86-video-intel/ xf86-video-intel
3. Fetch/build/upgrade script:

ARCH, RELEASE and BASDIR all are set up in a way to build up path to the x11 source directory in Slackware's source code tree.
Code:
$ cat xf86-video-intel-upgrade.sh 
#!/bin/sh

set -e

ARCH=64
RELEASE=current
BASDIR=/home/software/slackware/mirror
X11SRC=${BASDIR}/slackware${ARCH}-${RELEASE}/source/x/x11
LOGFILE=$(mktemp)

git-get-mksrctarball.sh \
  $(cat /home/software/src/01-git/xf86-video-intel.url) "$@" | \
  tee ${LOGFILE}
TARBALL=$(grep ^TARBALL= ${LOGFILE} | tail -n1 | cut -f2 -d=)
rm ${LOGFILE}
[ ! -f "${TARBALL}" ] && exit 42

cd ${X11SRC}/src/driver
rm xf86-video-intel-*.tar.xz || true
ln -s ${TARBALL}

echo "Executing: x11.SlackBuild driver xf86-video-intel"
su -l -c "cd ${X11SRC} && ./x11.SlackBuild driver xf86-video-intel"
This script:
1) invokes git-get-mksrctarball.sh to fetch the git source code,
2) parses git-get-mksrctarball.sh output (through temporary file) to get the location of the packaged source code,
3) goes to x11 source code tree, removes the current xf86-video-intel driver source code and soft links the just downloaded source code,
4) invokes x11.SlackBuild to build and upgrade the driver.

The arguments passed to xf86-video-intel-upgrade.sh are passed to git-get-mksrctarball.sh, so in the end, with the first argument to xf86-video-intel-upgrade.sh it's possible to specify the desired commit, and if empty, the 'master' is the default.


Hope this helps (and lets you type less).

--
Best regards,
Andrzej Telszewski
 
2 members found this post helpful.
Old 04-17-2016, 07:31 PM   #57
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Rep: Reputation: Disabled
mark this one solved?
 
Old 04-18-2016, 09:50 AM   #58
archfan
Member
 
Registered: Mar 2016
Location: /dev/hug
Distribution: Slackware 14.2 x64
Posts: 85

Rep: Reputation: 32
No. There are still some annoying bugs on Skylake platforms.

For instance this one: https://bugs.freedesktop.org/show_bug.cgi?id=94161#c28
 
Old 04-18-2016, 01:25 PM   #59
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Rep: Reputation: Disabled
'solved' in that progress has been made from the original post towards some usability and understanding of the components rather than the usual sense of [solved].

Skylake graphics looks to be a really long event horizon that might be better served by separate, related posts rather than a longer thread that makes it hard to find usable information.

Cheers,
 
Old 04-18-2016, 03:58 PM   #60
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,504

Rep: Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461Reputation: 8461
Quote:
Originally Posted by lazardo View Post
'solved' in that progress has been made from the original post towards some usability and understanding of the components rather than the usual sense of [solved].

Skylake graphics looks to be a really long event horizon that might be better served by separate, related posts rather than a longer thread that makes it hard to find usable information.
I'm finding having this information in one place to be easier to go through, if my opinion counts.
 
2 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Graphical issues with Mupen64Plus UltrasonicMadness Linux - Games 2 07-28-2014 07:36 AM
Graphical Issues On My Moms Linux vbj4 Linux - Newbie 3 02-13-2010 09:16 PM
Help Graphical Interface Issues. silverbear Mandriva 4 03-30-2006 04:46 PM
Mandriva Graphical Login Issues neyoung Mandriva 3 11-09-2005 03:21 AM
Mouse buttons , graphical login issues........AGAIN Jeebizz Slackware 6 06-22-2005 12:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration