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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
I have two old Thinkpad T43s onto which I installed Slackware 14.0. One T43 has ATi graphics, and Slack 14 works perfectly.
The other T43 has the intel 915GM graphics chip which uses the increasingly awful i915 driver. The version of the driver in kernel 3.2.29 shows all the usual i915 bugs on this T43: frozen X screens, blank screen before login, inability to change or force the change of resolutions, etc. The usual solutions (enabling modeset in the kernel, editing modelines in the xorg.conf, etc.) could improve some of these issues on this machine, but not the inability to alter resolution/refresh rate. Nor could compiling/installing the most current version of the driver from Intel's site.
After noticing some Arch user's complaint that he began experiencing i915 driver trouble (a few years ago) when he moved to kernel 2.34.x, I installed kernel-huge-smp-188.8.131.52_smp-i686-1.txz (and its related module set) from Slack 13.1 into the Slackware 14.0 installation. This kernel includes the i915 1.6.0 20080730, and so far, the Intel graphics on this T43 Thinkpad have worked perfectly, with no additional editing, fussing, or tweaking beyond the simple installation.
But my question is this: 184.108.40.206 is a very old kernel for Slack 14. It seems to work fine now, but am I courting ext4 filesystem, bootup, udev, or other disaster down the road by using it in an otherwise normal Slack 14 setup? My initial thought was to compile the older i915 driver on a current kernel, but a search of Intel's downloads doesn't seem to show any source from versions earlier than 2011. Nor do I seem to be able to determine from kernel source (short of compiling and running a particular kernel to check dmesg output) which version of the i915 it includes, in case i915 version 1.6.0 20080730 continued in use with kernels much more recent than 220.127.116.11. Is it known when i915 version 1.6.0 20080730 was dropped?
Thanks, but I don't think I can blacklist the i915 on this machine, since the 915GM northbridge functions as the motherboard chipset and also incorporates the integrated media adapter. On other T43s with the 915PM chipset, the graphics are handled separately by the ATi adapter.
I have not tried enabling the shadow in 3.2.29 and may try it at some point, but my major interest is in continuing to use the full features of the known-good i915 1.6.0 20080730, and whether a) it is reasonably safe to continue to use 18.104.22.168 with this i915 version in an otherwise unmodified Slack 14; b) it is known which 2.6.x (or 3.x.x) kernel version was the last to incorporate this version of the i915 driver, so that I may compile and install a more recent kernel with i915 1.6.0 20080730 and use it with Slack 14 on this machine, or c) whether the source for this version of the driver alone may be obtained somewhere, so that I can try to compile the older driver source on the default 3.2.29 kernel to see whether it continues to function correctly.
The Thinkpad has been running this OS/kernel combination for about 3 days so far without any incidents I can see, but I'm keeping the backups fresh and frequent, just in case.
Originally posted by caravel
If you want to continue with a 2.6.x kernel you would be better off just sticking with Slackware 13.x on that machine.
You must, generally speaking, be correct. But on a pure 13.1 system I'll end up having to back-level much of the application software I use on the machine. I suspect 22.214.171.124 from Slack 13.37 includes a considerably later problematic version of the i915 driver, but I guess I'll need to try it to find out.
When I get an opportunity, I'll also try the vesa driver on the 3.2.29 kernel. But in the meantime, the 126.96.36.199 kernel continues to handle everything without instability or issues, and its i915 is working fine, so I suppose I'll leave everything as is for the moment, unless a fatal problem suddenly pops up.