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 |
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? |
Quote:
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 |
@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 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 |
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 |
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 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 |
The 82865 chipset almost certainly isn't going to work with Xorg from Slackware 13.0. Stay with 12.2.
|
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 |
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:
Quote:
|
@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! |
Quote:
Quote:
http://www.linuxquestions.org/questi...ml#post3701312 |
@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 |
Quote:
Perhaps you should consider a fresh install of Slackware 13.0 and build from there. |
@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 |
Quote:
The include file picturestr.h is part of the xorg-server-1.6.3 package on the box I am posting from. Quote:
With 13.0, I am currently running kernel 2.6.31.4 and the Intel 2.9.0 driver, and DRI is enabled. Quote:
Using slackpkg can be easier for steps 3 and 4. Quote:
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' |
@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? |
Quote:
Quote:
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 |
@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? |
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:
|
Quote:
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. |
Quote:
Quote:
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:
Quote:
|
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" |
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 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 |
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 :( |
@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 |
@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. |
@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 :) |
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 |
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 :)
|
@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 |
matters, I`ve just uploaded your packages to http://advamacs.com/pub/intel-slackware/
|
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. |
Quote:
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 |
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. |
@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.
|
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" |
Quote:
Quote:
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... |
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" |
All times are GMT -5. The time now is 01:37 AM. |