LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://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 (https://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'

matters 01-17-2010 07:07 PM

@allend thanks, thats great info. how did you find out where is it located in what header?

ill try to see with upgrading from 12.2 to 13 and then to current, you think if i would do with slackpkg upgrading from slack13 to slackware -current that white screen on kde4.3.4 should dissapear?

allend 01-18-2010 12:38 AM

Quote:

how did you find out where is it located in what header?
Google gave me the filename and then 'grep $filename /var/log/packages/*' gave me the package name.
Quote:

you think if i would do with slackpkg upgrading from slack13 to slackware -current that white screen on kde4.3.4 should dissapear?
Slack 13.0 came with KDE 4.2.4.
The white screen was a consequence when KDE 4.2.4 was upgraded to KDE 4.3.x without also upgrading the qt package. If you use slackpkg correctly, this will not be a problem for you.

NB: Upgrading to slackware-current from Slackware 13.0 at this time has a trickiness with the naming of hard disk partitions. If you are using a system with an 82865 chipset, then I suspect that this issue will affect you. Please read rworkman's recent thread on this.
http://www.linuxquestions.org/questi...8/#post3817086

matters 01-18-2010 08:22 AM

@allend after upgrading back to 12.2 via slackpkg and do clean-system then upgrading back to 13 with upgradepkg --install-new X -configure error that i described vanished. At that time i had 2.6.29.6-generic-smp kernel with its modules, headers,firmware and source installed

i was able to login into X with vesa driver in xorg , i tried then to upgrade to xf86-video intel 2.9.0 from vitek and to 2.6.32-3-generic-smp with its modules, source etc.

then rebooted

tried to do X -configure
no errors everything cool, then i tried X -config /root/xorg.conf.new i got black screen hang

then i tried to do after reboot startx to see how that would behave guess what X runs but hangs, mouse freeze, no matter if i put in /etc/X11/xorg.conf vesa or intel driver, then i tried to upgrade to witek 2.9.1 to see if it will change something same thing, after startx mouse freeze x trying to load but hangs, then i downgrade back to 2.6.29.6-generic-smp with its modules etc. and again downgrade to 2.8.0 inel driver when X worked fine afeter upgrading from 12.2 to 13 now
when executing startx x Windows start but still mouse freeze and x hangs :)

im wondering what now caused the issue... is it maybe that ive done X -configure, i think not, or lastest kernel?

i was thinking if i would downgrade back to all original 13, when everything worked before would fix the problem but it didnt.

wondering what caused the issue?

allend 01-18-2010 06:55 PM

With my current setup using the 82865 chipset, I do not have a /etc/X11/xorg.conf file. The autodetected parameters work for me.
Perhaps you have some old configuration file in /etc/X11/ that is being used when X is started.
I know that I had a problem with the new X until I found that it was using an old XF86Config file that was present in /etc/X11. Perhaps you could move all the normal files out of /etc/X11/ and try doing startx. If you still have problems, then the output of /var/log/Xorg.0.log may hold a clue.

Quote:

then i tried X -config /root/xorg.conf.new i got black screen hang
I have also found this to be unreliable.

matters 01-19-2010 09:29 AM

Quote:

Originally Posted by allend (Post 3831514)
Perhaps you could move all the normal files out of /etc/X11/ and try doing startx.

what normal files you meant? btw i guess you intalled fresh slack 13 and by default 2.6.29.6 hanged when entering X? and mouse freeze? correct?

im wondering how from upgrading 12.2 to 13 vesa at least worked, untill ive done X -configure :)

btw ive tried to remove xorg from /etc/X11 but same results ive also removed xorg-vesa

im just wondering what you meant by normal files which files you meant in that dir and did you mean to move it completely so that they are no longer in /etc/X11?


did you create packages of modules, and slackware 2.6.31.4 or you have done everything as usual kernel installation?


thanks.

allend 01-19-2010 09:54 AM

Quote:

what normal files you meant?
I meant all regular files, but not directories.
Quote:

btw i guess you intalled fresh slack 13 and by default 2.6.29.6 hanged when entering X? and mouse freeze? correct?
Actually this box has been regularly upgraded since Slackware 9.
Upon upgrade to Slack 13.0, yes I had hanging with the 2.6.29.6 kernel when using the Intel driver. I could run X using the vesa driver, but this does not allow DRI and so no fancy desktop effects.
Quote:

im just wondering what you meant by normal files which files you meant in that dir and did you mean to move it completely so that they are no longer in /etc/X11?
Move all the regular files out to a temporary location, so that you can copy back anything you want.
Quote:

did you create packages of modules, and slackware 2.6.31.4 or you have done everything as usual kernel installation?
I compiled a custom kernel and modules from the 2.6.31.4 kernel source.

witek 01-19-2010 04:13 PM

I`ve just built intel 2.10.0 driver on kernel 2.6.32.3 along with libdrm it depends on (libdrm is with and without kernel mode settings). The driver is not working for me but maybe it will work for you. I wasn`t able to build the driver depending on libdrm with KMS thus there is only one version. Grab for testing from here:
http://advamacs.com/pub/intel-slackware/

[EDIT] It works but one needs to add to lilo
Code:

append = "i915.modeset=1"
(thanks matters :) )

matters 01-20-2010 06:20 PM

I upgraded to slackkware-current used libdrm-2.4.17 from witek and lastest driver, i removed xorg.conf from /etc/X11
i tried separately libdrm2.4.17k but that didnt work out, because in it didnt have inteldrv.so
so i had to upgrade only to 2.4.17, wich had inteldrv.so

after i tried to launch x and guess what i have composite active, i have enabled desktop effects and i have direct rendering yes

does it mean that finally intel driver does works for me? :)

im asking because of this: low fps still when i do this:
Code:

glxgears
1381 frames in 5.0 seconds = 275.994 FPS
1496 frames in 5.0 seconds = 298.797 FPS
1433 frames in 5.0 seconds = 286.498 FPS
1458 frames in 5.0 seconds = 291.594 FPS
1453 frames in 5.0 seconds = 290.573 FPS
1471 frames in 5.0 seconds = 294.148 FPS

is there a way to get more fps? or its this as it is?

thanks guys sorry for delay in reply i was testing all the way

btw what do we get with kms? if i understood right witek said that he didnt create package libdrm with kms?

witek what those 2 packages represents? im asking because on libdrm2.4.17k package is missing inteldrv.so if i remember right

do i need to install all 2 packages? (i suspect only one is needed)

i forgot to say thanks to allend aswell thanks bro for all the effort

witek 01-21-2010 03:01 AM

This might seem funny but I don`t know exactly what KMS is for and how it works despite I`ve compiled these files :)

I`ve just built libdrm with standard configuration (no kms) and then intel driver.
I guess these: libdrm without kms and the intel driver should work together fine.

Then I built libdrm with kms enabled, it compiled fine (this version has kms in its name). Then I tried to build intel driver based on libdrm with kms but I couldn`t as there were errors, so I don`t know exactly what would it work like with kms.
This libdrm with kms is only for your experimentation as you might try to built your own intel driver based on it.

Good to hear the driver works for you as I said before it woudn`t work for me :(

matters 01-21-2010 03:43 AM

@witek how did you instruct to build libdrm on kms?? and where did you get lastest intel driver source from?

im just wondering how many fps do you guys get with glxgears compared to mine, since still kde for me is kinda slow although all is enabled :)

so im wondering what might that be that kde is kinda slow? how can i diagnose it. i mean it works but browsing when i open 6 or 7 firefox browser windows, skype, pidgin etc it starts to lag and composite start to switch off

also kde 4.3.4 now crtl+alt+backspace does not react i have to enter to console and interupt it manually with ctrl+c

is there a way that i can make it to work?
so wondering if you guys have similar expiriences, although when i was on kde 3.5 12.2 i didnt have dri enabled and everything was much faster so im wondering if kms would faster things up

thanks guys

witek 01-21-2010 05:38 AM

@matters:
Intel driver can be downloaded from here:
http://intellinuxgraphics.org/
which then leads you to:
http://xorg.freedesktop.org/archive/individual/driver/

Regarding building libdrm (and anything else). One always can do

./configure --help

then analyse what can be set and unset and configure according to one`s needs :)

As regards KDE I stopped using it from version KDE4 as it was too slow on my machine. I use XFCE and only some of KDE4 apps like kmail, okular and sometimes konqueror.

matters 01-21-2010 11:28 AM

@witek thanks.

im just wondering now how many fps you guys have with glxgears? to compare with mine? can anyone post me results, just wondering if you guys get faster than i do


btw on xfce, is xfce based on /etc/X11/xorg.conf if that file is available, and if its not where i could manually tweak xfce config and under what file?


at least xfce i like better now :)

matters 01-28-2010 09:33 AM

ive build libdrm 2.4.17 and 2.10 intel driver with kms based on kernel 2.6.32.5-smp everything works.

i would like to inform you that with kms i got better fps with glxgears

glxgears
1999 frames in 5.0 seconds = 399.746 FPS
2142 frames in 5.0 seconds = 428.332 FPS
2148 frames in 5.0 seconds = 429.442 FPS
2147 frames in 5.0 seconds = 429.338 FPS
2152 frames in 5.0 seconds = 430.256 FPS
2148 frames in 5.0 seconds = 429.579 FPS
2140 frames in 5.0 seconds = 427.997 FPS
2140 frames in 5.0 seconds = 427.844 FPS

heres link to test it with
http://rapidshare.com/files/34243935...kmsmatters.txz
http://rapidshare.com/files/34244223...kmsmatters.txz

hopefully it will help others.
im wondering if theres special file for xfce like xorg.conf to be governed with or xorg.conf is the only file to edit and will be applied for both xorg and xfce?

thanks guys

witek 01-29-2010 03:18 PM

Downloading from rapidshare is troublesome (at least for me). If you don`t mind, send me those files in an e-mail (mozga[at]trimen.pl), and I put them on my server where they could be downloaded more easily :)

matters 01-30-2010 05:56 AM

@witek done, can you check how many fps do you get with glxgears and report please?

@allend can you please do the same?

wondering if we can speed things up even more :) im still not satisfied with fps im getting and i suspect that you guys are getting better results

thanks

witek 01-30-2010 08:01 AM

matters, I`ve just uploaded your packages to http://advamacs.com/pub/intel-slackware/

trumpet_tom 02-03-2010 05:21 AM

Just came across this thread. I've been having the same trouble with X, sometimes it just leaves me at a black screen instead of loading to kdm. I'm now running libdrm-2.4.17-i486-1kmsmatters.txz and xf86-video-intel-2.10.0-i486-1kmsmatters.txz. So far so good!

I'm not sure if it's a placebo effect but kde seems a bit more snappy with these two packages installed. My glxgears is a meager ~155fps but all the kwin animations seem to be running smoothly. This is on my eeepc with my own 2.6.32.7 kernel build, kms enabled.

Mol_Bolom 02-03-2010 10:14 AM

Quote:

Originally Posted by witek (Post 3846058)
matters, I`ve just uploaded your packages to http://advamacs.com/pub/intel-slackware/

[EDIT] The driver won`t work for me :( I`m staying with 2.9.0 which works and gives me ca. 290fps on my old chipset-integrated card 82845G/GL

@witek:

What is the size of the display that gave you 290fps?

At 1152x864 res glxinfo at full screen, on dwm, is giving me
Code:

188 frames in 5.0 seconds = 37.506 FPS
Is that normal or can I get more? I have the same chipset, so I'm very curious to see if I can get more out of this old machine.

witek 02-03-2010 01:28 PM

I have 1280x1024 resolution. You must keep in mind that glxgears is not a perect tool for performace analysis. My fps result comes from default small window of glxgears. When I maximize it I have only 29 fps.
Anyway I don`t care much about glxgears result. What I need more is stability which suffers recently on intel video.

matters 02-04-2010 03:20 AM

@witek regarding 2.9.0 driver that works for you just wondering, in which combination it works? specific kernel or lastest kernel works as well? ive also rebuilded libdrm and intel with kms based on 2.6.32.7-smp works good.

witek 02-04-2010 08:12 AM

2.9.0 worked with kernel that came with Slack 13 and now it works with 2.6.32.7-smp as well. There is improvement as glxgears are now properly displayed, unlike with 2.6.29. However I`m not sure if kernel has got much to do with video displaying. Maybe when it comes to KMS.

[EDIT] @matters: I tested your new driver and it works. I had to append to lilo
Code:

append = "i915.modeset=1"
as you suggested. I put the driver on my server.

Mol_Bolom 02-04-2010 10:10 AM

Quote:

Originally Posted by witek (Post 3851172)
I have 1280x1024 resolution. You must keep in mind that glxgears is not a perect tool for performace analysis. My fps result comes from default small window of glxgears. When I maximize it I have only 29 fps.
Anyway I don`t care much about glxgears result.

True, but unfortunately, it's the best there is, but at least it gives a ball park.

Quote:

What I need more is stability which suffers recently on intel video.
Well, after several hours yesterday, exiting xorg, running games, testing it to make sure it wouldn't crash, I thought I was out of the water...Nope...After several hours it crashed, keyboard & mouse useless. Then after that it only lasted a few minutes before it happened. This is running off of your packages.

Anyway. I just found that drm is reading my 845g card as i915, so I'm gonna do a bit more searching. Hopefully, that is the last problem I'll have once I fix it...Fingers crossed...
<Edit> So I learned that the i915 doesn't mean anything...While searching, came to the conclusion that I probably need a newer kernel...Go trying out 2.6.33.rcx...

witek 02-07-2010 12:55 PM

Thanks to matters I finally made 2.10.0 working for me. I just had to explicitly enable kms during boot by adding this line to lilo:
Code:

append = "i915.modeset=1"
Thanks again, matters :)


All times are GMT -5. The time now is 01:37 AM.