@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?

Google gave me the filename and then 'grep $filename /var/log/packages/*' gave me the package name.
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 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.

I have also found this to be unreliable.

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.

I meant all regular files, but not directories.
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.
Move all the regular files out to a temporary location, so that you can copy back anything you want.
I compiled a custom kernel and modules from the 2.6.31.4 kernel source.

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
(thanks matters )

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:
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

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