SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Guys, every OSS software package is known to make such kind of vanilla warnings. I remember reading something like that, but didn't even recognize the significance of this info (relegated to the separate file, too).
As Slackware is known for its healthy conservatism, to be really noticed, such thing as the capitally reworked X graphics drivers for one of the major vendors ought to be advertised in capitals, like WARNING UNSURE QUALITY INTEL DRIVERS - or better yet, that's new (2.8/2.9) variants that ought to "be there in /extra for me to try", not stable (2.6/2.7) variants.
Multiple fixes (need 2.6.32-rc1+ kernel) to make the driver stable for 8xx chipsets (The 2.8 driver series were extremely unstable with many of these chipsets)
BTW I just downloaded and compiled libdrm 2.4.14, Mesa 7.5.2 (not ready yet for 7.6), and xorg.server 1.6.4. The xorg server refused to run without the newer 2.9.0 driver so I compiled it. Now I'm running xorg-server 1.6.4, Mesa 7.5.2 (not yet 7.6, but it says it had fixes for Intel chipsets), and the Intel 2.9 driver. By the way I'm using the 2.6.30.5 kernel with KMS activated. It's stable. 745 fps on my i945.
I'm not willing to recompile my kernel yet or to build Mesa 7.6, but if what they say is true, it might work.
These are the headers describing the kernel's userspace API - i.e. any userspace libraries and apps that interface with the kernel use this.
These headers - the API - don't change with maintenance upgrades, i.e. all 2.6.27.xx kernels are good to go with this particular version of the headers.
The API may change in important ways with different major revisions of the kernel. In practice, of course, really significant changes tend to be avoided if at all possible. In practice, you could get away with running a 2.4 kernel header'ed system with a 2.6 kernel but the other way around would undoubtedly be a fail.
Probably Slack could package kernel-headers without the minor revision number since in theory that's redundant information.
We might reasonably expect, in practice, if you're up-rev'ing the kernel then the "old" kernel headers are likely to work. However, I presume you can see where I get the caveat that "something odd" could come out of mixing and matching kernel-headers with an API for whatever previous version and some later actual API. I imagine that some kind of important bug-fix might have been put in to stop a buffer overflow, for instance, that could cause grief with things compiled against inappropriate headers.
That's just one reason why it's not a great idea to dick around with Patrick's official Slackware distro unless you really know what you're doing or you don't particularly care about the results and you're fine with it randomly breaking. (A reason to stick with official Slack packages from slackware.org or Slackbuilds.)
The Intel 82865G chipset works with the 2.6.31.4 kernel.
I have tested with the Intel 2.8.0 driver as well as the Intel 2.9.0 driver.
The boot time to KDE after startx is noticeably shorter with the 2.9.0 driver.
intel 82865G WORKS HERE - 2.6.32-rc5 kernel + zen patch + witek's xorg intel v2.9.0
I'm happy to report, I am up and running GREAT with intel 82865G video hardware + DRI enabled + composite effects in KDE4 on default slackware 13.0 x86 install -- on taking poncezadvice, the difference from a default install is I've installed linux 2.6.32-rc5 kernel + zen kernel patch + using witek's xorg intel v2.9.0 video driver
[+]NOTE :: when "lilo" got updated/ran (from the make&&make install... line), I recieved an error "Fatal: Bitmap table has space for only 3 images"...
google searches didnt bring up too much, but asking around on ##slackware @ freenode.net a guy named Camarade_Tux helped me out, and suggested I just remove the BMP-related lines in lilo.conf (I made sure only 2 bootup logos were enabled in linux kernel config), once I did that and ran "lilo" it went thru without error - this is the top part of my lilo.conf that I commented out + and the "message =" line I enabled ;;
Maybe - in a stunning break from tradition - Slackware should rush out a Slack 13.1 that does play with the Intel driver. If there's any chance of that, I would test an RC on my 82865G HP-Compaq which is currently stuck at 12.2 (which does work very nicely and even runs things like Cinelerra).
Multiple fixes (need 2.6.32-rc1+ kernel) to make the driver stable for 8xx chipsets (The 2.8 driver series were extremely unstable with many of these chipsets)
BTW I just downloaded and compiled libdrm 2.4.14, Mesa 7.5.2 (not ready yet for 7.6), and xorg.server 1.6.4. The xorg server refused to run without the newer 2.9.0 driver so I compiled it. Now I'm running xorg-server 1.6.4, Mesa 7.5.2 (not yet 7.6, but it says it had fixes for Intel chipsets), and the Intel 2.9 driver. By the way I'm using the 2.6.30.5 kernel with KMS activated. It's stable. 745 fps on my i945.
I'm not willing to recompile my kernel yet or to build Mesa 7.6, but if what they say is true, it might work.
I am using mesa 7.6 with libdrm 2.4.14, and it works well.
If anybody is able to prepare the packages for testing it would be nice. I tried to build the intel driver alone but failed Building X server is outside my capabilities yet :-\
update of my results :: my poor dell inspiron 1100 which runs intel 845G video hardware is still a sitting duck running slackware 13.0 + KDE4 with any combo suggested in this thread. I've tried every version of xf86-video-intel-* drivers that came on slackware 13.0 x86 DVD, I've tried witek's 2.9.0 driver, upgraded to 2.6.32-rc5, tried zen patches 1 & 2 for 2.6.32-rc5, upgraded to libdrm 2.4.14 & mesa-7.6 ... nothing helps. reading witek's last post/link, it sure sounds like the fix for this intel 845G graphics chip is gonna be either xf86-video-intel-2.9.1 and/or X11R7.5 ... sigh. I haven't given up yet... I will continue to work on this until I get the latest slackware + KDE4 working on this laptop if it kills me! ha, until then dual-booting backtrack4 has been my solution (bt4 has KDE 3.5.x which works great).
update of my results :: my poor dell inspiron 1100 which runs intel 845G video hardware is still a sitting duck running slackware 13.0 + KDE4 with any
...
Did you try setting Option "Tiling" "false"? I sort of solved my problem (Latitude 100L with Intel 852) with switching to 2.9.1 driver AND this option setting.
Did you try setting Option "Tiling" "false"? I sort of solved my problem (Latitude 100L with Intel 852) with switching to 2.9.1 driver AND this option setting.
I do not think I've tried that yet... I will give that a shot here in a few hours when I get back to my laptop. thanks for the suggestion! hey, u said u are running 2.9.1 driver, any chance u have a slackware package u could post for us to try/download? I'd love to try it but, I dont know howto go about recompiling X from scratch... any help would be much appreciated, I will report back with my results of = Option "Tiling" "false" as well.
I do not think I've tried that yet... I will give that a shot here in a few hours when I get back to my laptop. thanks for the suggestion! hey, u said u are running 2.9.1 driver, any chance u have a slackware package u could post for us to try/download? I'd love to try it but, I dont know howto go about recompiling X from scratch... any help would be much appreciated, I will report back with my results of = Option "Tiling" "false" as well.
peas out
No need to bother with a packages, in this case. You just download the source for new version from intellinuxgraphics.org (some 800K) and compile and install just that (make && make install ).
if it compiles on the normal Slackware building tree?
./x11.SlackBuild xserver xorg-server
I tried to compile it and compilation seemed to be successful, however when I started X the system hanged with black screen.
I thought about recompiling everything including libs, but when I looked into the complicated structure of directories and milions of files I quit as I had no idea how to download only upgraded files from X mirror.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.