[SOLVED] xf86-video-intel-2.9.0-i486-1.tgz how to identify to xorg.conf to make sure it runs
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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
@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 18.104.22.168-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.
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 22.214.171.124-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.
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.
then i tried X -config /root/xorg.conf.new i got black screen hang
btw i guess you intalled fresh slack 13 and by default 126.96.36.199 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 188.8.131.52 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.
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.
did you create packages of modules, and slackware 184.108.40.206 or you have done everything as usual kernel installation?
I compiled a custom kernel and modules from the 220.127.116.11 kernel source.
I`ve just built intel 2.10.0 driver on kernel 18.104.22.168 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/
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:
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
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
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