LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   xf86-video-intel-2.9.0-i486-1.tgz how to identify to xorg.conf to make sure it runs (http://www.linuxquestions.org/questions/slackware-14/xf86-video-intel-2-9-0-i486-1-tgz-how-to-identify-to-xorg-conf-to-make-sure-it-runs-782257/)

matters 01-14-2010 04:11 PM

xf86-video-intel-2.9.0-i486-1.tgz how to identify to xorg.conf to make sure it runs
 
hi, i was wondering what name i have to put in Driver directive in to make sure it loads its modules from the package xf86-video-intel-2.9.0-i486-1.tgz ,because when i write driver with name intel it wont startx seems to me it looks for moodules in /usr/lib/modules where they are not originaly from the driver.and package installs in /usr/lib/xorg/modules/drivers

thanks alot

thanks

abrouwers 01-14-2010 07:07 PM

You shouldn't need to specify ANY driver in xorg.conf - with open-source drivers and hot-pluggy x.org (like slackware ships), xorg will find the driver on its own.

In the event you do use a xorg.conf file, "intel" is indeed correct. Where did you get this package? Slackware has yet to provide a 2.9.x driver.

Did you upgrade to it, or use "installpkg" on top of the original intel driver?

The "/usr/lib/xorg/modules" is correct, and kind of a slackware-specific directory. Did you steal this package from another distro?

witek 01-15-2010 02:37 AM

Quote:

Originally Posted by matters (Post 3826776)
package xf86-video-intel-2.9.0-i486-1.tgz

You probably are talking about my package I prepared some time ago as I had serious problems with 2.8 intel drivers and published it in a topic devoted to intel video: http://www.linuxquestions.org/questi...2F#post3702384

You should just upgrade package and then reboot machine. I`m not sure why reboot is necessary but it is. I still occasionally get random X problems such as black screen and what I try first is init 3 then init 4 and this sequence doesn`t help. Reboot is necessary.

So just upgrage, reboot. If you need some manual tweaks (I didn`t) just create your xorg.conf as root at runlevel 3 with X -configure

you might alternatively try 1.9.1 driver but on my machine 1.9.0 works better:
http://advamacs.com/pub/intel-slackware

matters 01-15-2010 08:55 AM

@witek yes im talking about your package, im going back and forth upgrading from 12.2 to current for one reason to get my 82865g up and running with DRI enabled however when going glxinfo i always see direct rendering no

i have 2.6.32.3-generic-smp kernel and ive upgraded to 2.9.1 as u suggested and reboot

when i execute in runlevel 3 X -configure i get

Code:

X -configure

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux parade 2.6.32.3-smp #1 SMP Thu Jan 7 18:40:14 CST 2010 i686
Build Date: 30 June 2008  11:35:29PM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 15 15:39:11 2010
List of video drivers:
        radeon
        cyrix
        dummy
        siliconmotion
        newport
        i128
        rendition
        ati
        intel
        tdfx
        ast
        vmware
        savage
        mach64
        via
        imstt
        nsc
        i740
        glint
        tseng
        tga
        ark
        sisusb
        neomagic
        nv
        mga
        s3
        chips
        geode
        s3virge
        apm
        sis
        trident
        v4l
        cirrus
        ztv
        openchrome
        radeonhd
        r128
        voodoo
        fbdev
        vesa
        vga
dlopen: libdrm_intel.so.1: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)
(++) Using config file: "/root/xorg.conf.new"


Xorg detected your mouse at device /dev/input/mice.
Please check your config if the mouse is still not
operational, as by default Xorg tries to autodetect
the protocol.

Your xorg.conf file is /root/xorg.conf.new

To test the server, run 'X -config /root/xorg.conf.new'

in xorg.conf i have specified driver vesa

however dlopen: libdrm_intel.so.1: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)

now after reboot it searches for intel driver good path but i dont have libdrm_intel.so.1

where to get this file from?

thanks all for helping me out

adamk75 01-15-2010 11:08 AM

libdrm_intel is part of libdrm. Slackware does not come with a version of libdrm that supports KMS on intel or radeon GPUs. You would need a newer version of libdrm compiled with intel KMS support.

Adam

matters 01-15-2010 12:15 PM

after upgrading from libdrm-2.3.0 to 2.4.12 of slackware

heres what X -configure gives
Code:

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux parade 2.6.32.3-smp #1 SMP Thu Jan 7 18:40:14 CST 2010 i686
Build Date: 30 June 2008  11:35:29PM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 15 19:06:46 2010
List of video drivers:
        radeon
        cyrix
        dummy
        siliconmotion
        newport
        i128
        rendition
        ati
        intel
        tdfx
        ast
        vmware
        savage
        mach64
        via
        imstt
        nsc
        i740
        glint
        tseng
        tga
        ark
        sisusb
        neomagic
        nv
        mga
        s3
        chips
        geode
        s3virge
        apm
        sis
        trident
        v4l
        cirrus
        ztv
        openchrome
        radeonhd
        r128
        voodoo
        fbdev
        vesa
        vga
dlopen: /usr/lib/xorg/modules//intel_drv.so: undefined symbol: PictureScreenPrivateKey
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)
(++) Using config file: "/root/xorg.conf.new"


Xorg detected your mouse at device /dev/input/mice.
Please check your config if the mouse is still not
operational, as by default Xorg tries to autodetect
the protocol.

Your xorg.conf file is /root/xorg.conf.new

To test the server, run 'X -config /root/xorg.conf.new'

this is the problem now

dlopen: /usr/lib/xorg/modules//intel_drv.so: undefined symbol: PictureScreenPrivateKey
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)
(++) Using config file: "/root/xorg.conf.new"


what version should i get of libdrm and how do i compile it to have libdrm compiled with kms?

wondering whats the error about?

EDIT: i was googling around and many post says that its about different org header compared to new xorg installed?
if thats true how can i check what headers are installed(if they are) compared to xorg?

thanks guys

rworkman 01-15-2010 06:58 PM

The 82865 chipset almost certainly isn't going to work with Xorg from Slackware 13.0. Stay with 12.2.

matters 01-16-2010 02:19 AM

the problem is,i downgraded and im on 12.2 and it dosent work, i posted the problem that im having what should i check to fix this problem? also how i can find out if i have xorg headers installed and what version?

thanks

allend 01-16-2010 06:46 AM

The 82865 chipset does not work with standard Slackware 13.0. However it can be made to work by a kernel and driver update.
http://www.linuxquestions.org/questi...ml#post3725538

Quote:

i have 2.6.32.3-generic-smp kernel and ive upgraded to 2.9.1
I have not tried this exact kernel and driver combination, but I would expect that it would work.
Quote:

in xorg.conf i have specified driver vesa
You will not get DRI with the vesa driver. Try specifying the intel driver.

matters 01-16-2010 07:26 AM

@allend for intel driver specified this is what i get :

dlopen: /usr/lib/xorg/modules//intel_drv.so: undefined symbol: PictureScreenPrivateKey
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)

now upgraded to libdrm-2.4.17

many posts says about this error on google like that its about different xorg header compared to new xorg installed

what im trying to figure out wheter if its true or not? since ive upgrading/downgrading slackware current, im wondering whats the package name for X11 headers? to see if headers mismatch with org?

what should i try to fix the problem?

also wondering what kind of problem did you get when kernel and driver combination didnt work?

thanks alot!

allend 01-16-2010 08:01 AM

Quote:

also wondering what kind of problem did you get when kernel and driver combination didnt work?
http://www.linuxquestions.org/questi...ml#post3685107
Quote:

what should i try to fix the problem?
Have you tried building the Intel driver package from source?
http://www.linuxquestions.org/questi...ml#post3701312

matters 01-16-2010 08:57 AM

@allend since 2.9.0 requires xorg server 1.6 onwards and im on 1.4.2 since im on slackkware 12.2 i decided to remove it and install install xf86-video-intel-2.4.3 from official slackware mirror site

however it still gives the same error:

dlopen: /usr/lib/xorg/modules//intel_drv.so: undefined symbol: PictureScreenPrivateKey
(EE) Failed to load /usr/lib/xorg/modules//intel_drv.so
(EE) Failed to load module "intel" (loader failed, 7)

at least we are moving :) im wondering what is this error,
and to see what package contains x11 header files, to see if this is possible error regarding xorg headers and actual xorg.

please advise

thanks to all

allend 01-16-2010 09:37 AM

Quote:

im going back and forth upgrading from 12.2 to current
From your posts in this thread and another that you started, I am of the opinion that your setup is probably in some hybrid state. My posts have been describing what was necessary for me to get the 82865 chipset working on a full installation of Slackware 13.0, which was a kernel upgrade as well as a driver upgrade.
Perhaps you should consider a fresh install of Slackware 13.0 and build from there.

matters 01-16-2010 10:40 AM

@allend yes but then i wouldnt learn where the problem is, i still want to solve the error.

what kernel and driver combination works for you on 13 as well as on 12.2

would slackpkg clean-system, then current-upgrade then upgrade-all would do the trick for fresh one? but i would prefer in sticking solving the problem please :)
still dont know package regarding x-org headers to find out which one is installed

thanks

allend 01-16-2010 07:28 PM

Quote:

dlopen: /usr/lib/xorg/modules//intel_drv.so: undefined symbol: PictureScreenPrivateKey
The symbol PictureScreenPrivateKey is defined in /usr/include/xorg/picturestr.h.
The include file picturestr.h is part of the xorg-server-1.6.3 package on the box I am posting from.
Quote:

what kernel and driver combination works for you on 13 as well as on 12.2
I was using stock 12.2 on the box with the 82865 chipset. I was using the vesa driver at that time, so no DRI. (The box mainly works as a file/print server and I use a GUI mainly for performing backups to optical disks and administering CUPS).
With 13.0, I am currently running kernel 2.6.31.4 and the Intel 2.9.0 driver, and DRI is enabled.
Quote:

would slackpkg clean-system, then current-upgrade then upgrade-all would do the trick for fresh one?
The procedure to update from 12.2 to 13.0 is detailed in UPGRADE.TXT.
Using slackpkg can be easier for steps 3 and 4.
Quote:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
The worst part of the whole process is updating the configuration files in /etc. Remember to look carefully at /etc/passwd, /etc/group and /etc/shadow. Slackpkg does not prompt about the changes in these files.

Just a heads up. There is a minor error in step 5 of UPGRADE.TXT. It reads '/usr/man/man.conf.new" but should be '/usr/lib/man.conf.new'


All times are GMT -5. The time now is 09:40 AM.