SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No need to bother with a packages, in this case. You just download the source for new version from intellinuxgraphics.org (some 800K) and compile and install just that (make && make install ).
Not quite. I tried to cimpile intel 2.9.1 driver and got this:
Code:
Making all in uxa
CC uxa.o
In file included from uxa-priv.h:331,
from uxa.c:37:
/usr/include/xorg/shmint.h:27:35: error: X11/extensions/shmstr.h: Nie ma takiego pliku ani katalogu
In file included from uxa-priv.h:331,
from uxa.c:37:
/usr/include/xorg/shmint.h:34: error: expected declaration specifiers or '...' before 'ShmFuncsPtr'
In file included from uxa.c:37:
uxa-priv.h:344: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'uxa_shm_funcs'
uxa.c: In function 'uxa_driver_init':
uxa.c:528: error: 'uxa_shm_funcs' undeclared (first use in this function)
uxa.c:528: error: (Each undeclared identifier is reported only once
uxa.c:528: error: for each function it appears in.)
uxa.c:528: error: too many arguments to function 'ShmRegisterFuncs'
Not quite. I tried to cimpile intel 2.9.1 driver and got this:
Code:
...
/usr/include/xorg/shmint.h:27:35: error: X11/extensions/shmstr.h: Nie ma takiego pliku ani katalogu
...
I compiled mine w/o any problem on Slackware 13.0 with xorg 1.6.3 (which is required for newer intel drivers). Did you run ` configure --prefix=/usr ' beforehand?
I compiled mine w/o any problem on Slackware 13.0 with xorg 1.6.3 (which is required for newer intel drivers). Did you run ` configure --prefix=/usr ' beforehand?
Yes, I tried --prefix but in vain. I also have Slackware 13 with xorg 1.6.3. I successfully compiled 2.9.0 before.
According to xorg wiki, for radeon the build order should be macros->proto->xserver->libdrm->ddx(videodriver)->mesa. Try upgrading libdrm to 2.4.15 before compiling the new driver for your intel card. Don't rebuild the server, just libdrm. You can use this script to play with libdrm and step back if anything goes wrong:
Quote:
#!/bin/sh
# Copyright 2006, 2007, 2008, 2009 Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# Compress and link manpages, if any:
if [ -d $PKG/usr/man ]; then
( cd $PKG/usr/man
for manpagedir in $(find . -type d -name "man*") ; do
( cd $manpagedir
for eachpage in $( find . -type l -maxdepth 1) ; do
ln -s $( readlink $eachpage ).gz $eachpage.gz
rm $eachpage
done
gzip -9 *.?
)
done
)
fi
# Compress info files, if any:
if [ -d $PKG/usr/info ]; then
( cd $PKG/usr/info
rm -f dir
gzip -9 *
)
fi
# Add a documentation directory:
mkdir -p $PKG/usr/doc/${PKGNAM}-$VERSION
cp -a \
README \
$PKG/usr/doc/${PKGNAM}-$VERSION
No need to bother with a packages, in this case. You just download the source for new version from intellinuxgraphics.org (some 800K) and compile and install just that (make && make install ).
I was able to easily build + upgrade to xf86-video-intel-2.9.1-i486-1 (of mention I am using libdrm-2.4.14, and mesa-7.6) package no problem on my dell inspiron 1100 laptop (intel 845G) using src2pkg. this time KDE4 comes up to the black + white bubbles background, and goes thru the startup icons, but again after completing it's flashing of each KDE4 startup icon, ending with the K - I then get a black screen (on my other non-intel-based video hardware computers with slack13, I never get that black screen, it just fades to my desktop. this blackscreen issue is ONLY on my intel boxen). I tried using the following in my xorg.conf to no avail;
Code:
Option "Tiling" "false"
I also tried no xorg.conf, and X -configure, then that just xorg.conf.new plain-jane to /etc/X11/xorg.conf, but same issues!
sooo, this had me thinking maybe, just maybe it's a KDE4 thing... so I upgraded to slackware-current x86, which has kde 4.3.2 - but, same deal! X starts up, gets the KDE4 bubble background (blue & white this time with KDE 4.3.2), after finishing it comes up to a black screen, yet I can move and see my mouse cursor just fine. so, no fixie for me yet. still looking for that illusive/magic FIX for my intel 845G + KDE4 issue. I can say this tho, using any other window manager works, and actually seems to be quicker with this new driver = 2.9.1.
thanks for the help everyone... I will continue to work on this, if anyone else has pointers let me know!
PS: I notice after I startx with KDE4 and it hits that black background, and I then hit CONTROL+BACKSPACE to get to a prompt again... upon checking dmesg I see the following OVER & OVER again (which Im thinking has something to do with the intel xorg driver crapping out?) ;;
Code:
[drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
then at the bottom after the above repeats ~30+times, dmesg shows this
Code:
[drm:i915_gem idle] *ERROR* hardware wedged
mtrr: no MTRR for e0000000,8000000
Last edited by agentdcooper; 10-31-2009 at 03:40 PM.
Yes, I tried --prefix but in vain. I also have Slackware 13 with xorg 1.6.3. I successfully compiled 2.9.0 before.
Well, I've re-checked, and I am actually able to build both with or without specifying the /usr prefix.
I would definitely say you have a wrong prefix somewhere in your build, or, possibly some files missing OR dislocated, even. Wrong symlink or "fancy" layout in your /usr filesystem?? Some xorg packages missing?? No offence, but do you actually have a /usr/include/X11 dir on your system?
I've noticed before how Slack's symlinking "up n dirs" for the X11 subsystem may get incorrect. Unfortunately, can't remember the details, so can't be more specific).
On the Slackware-13.0, the shmint.h (which you have) belongs to the xorg-server-1.6.3-i486-1 package, and shmstr.h would belong to the xextproto-7.0.5-noarch-1 package.
On the Slackware-13.0, the shmint.h (which you have) belongs to the xorg-server-1.6.3-i486-1 package, and shmstr.h would belong to the xextproto-7.0.5-noarch-1 package.
Thanks a lot! I forgot I`ve been tinkering with my xorg recently when I was trying to upgrade to 1.7. I failed but some of packages remained upgraded, among them I had xextproto-7.1.1 instead of xextproto-7.0.5. When I downgraded I was able to compile intel driver at last (by the way: I was sure that having upgraded package doesn`t hurt. I was wrong apparently).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.