Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Yes, that is a driver, but it's old driver, version 2.5.0. Latest Intel driver is 2.8.1. Newest drivers have many bug fixes. Even the driver before 2.8.0 version had so many problems that it made some distros look bad, like Ubuntu for example. Maybe this qoute from one of the Ubuntu users describes that problem in the best way;
There is hope for Ubuntu users with Intel graphics.
You can try to install that driver (2.5.0), if it's made for Fedora it should work, just be sure that you have all dependencies installed too.
But as I said, I recommend installing the newest driver.
If you follow the guide that I've linked, you should have no problems and there are lots of us here who will help you if needed. Don't give up, you can do it and it's not a headache, it's about how do you approach to the problem.
I checked my install and ... I already seem to have the driver installed, a 2.5 to be exact, though never actively used, thus never updated. Let me change the "vesa" in my xorg.conf in "i810" - I tried "intel" and got a grey blank screen...
You need to check what modules are loaded on your system. You can do this with lsmod command. Now if you see vesa there you should remove it with modprobe -r vesa or modprobe -r vesa.ko, then you need to blacklist that module. In Debian I would go to /etc/modprobe.d/blacklist to do that. Then you need to load "intel" driver into the kernel if it's not already. You would do this with modprobe command too. If I'd want to know some specifics about certain module I'd use modinfo nvidia for example, if I'd like to check nvidia module specifics. If I would want to load certain module on boot I would add an entry in /etc/modules.
license: GPL and additional rights
description: Intel i810
author: VA Linux Systems Inc.
vermagic: 126.96.36.199-170.2.82.fc10.i686 SMP mod_unload 686 4KSTACKS
I make a symlink in /etc/X11 so the xorg.conf can find it, full rwx rights are in place.
The X11 still cannot find the driver.
Compiling may be a little beyond my current capacities...though I am willing to give it a whack...