LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2001-01-30 16:44:59 +00:00
parent e7ff589851
commit 45b09458c9
1 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
LDP/howto/docbook/i810-HOWTO.sgml
View File

@ -8,11 +8,11 @@
<author>
<firstname>Toby</firstname><surname>Russell</surname>
</author>
<pubdate>v0.5, January 2001</pubdate>
<pubdate>v0.55, January 2001</pubdate>
<abstract>
<para>
This HOWTO describes getting XFree86 4.x running on Intel's i810 graphics chipset by using special features of the 2.4.0 kernel.
This HOWTO describes getting XFree86 4.x running on Intel's i810 graphics chipset by using special features of the 2.2.18 and 2.4.0 kernels.
</para>
</abstract>
</artheader>
@ -21,7 +21,7 @@ This HOWTO describes getting XFree86 4.x running on Intel's i810 graphics chipse
<title>Introduction</title>
<para>
This document has a very specific purpose; to help people who are failing to get X working on Intel's i810 graphics chipset (hereafter "the i810"). It is written by a beginner (me), and it is imagined that it will be of use primarily to other beginners. The author would be flattered to hear that he has helped anyone more skilled than he. Furthermore, I know that the i810 works with XFree86 3.3.6, but I personally have not trod that path. My experience comes purely from XFree86 4.0 (hereafter "X4.x") and the 2.4.0 kernel, and consequently this HOWTO tackles that solution, or procedure, alone.
This document has a very specific purpose; to help people who are failing to get X working on Intel's i810 graphics chipset (hereafter "the i810"). It is written by a beginner (me), and it is imagined that it will be of use primarily to other beginners. The author would be flattered to hear that he has helped anyone more skilled than he. Furthermore, I know that the i810 works with XFree86 3.3.6, but I personally have not trod that path. My experience comes purely from XFree86 4.0 (hereafter "X4.x") and the i810/agpgart support available in the 2.2.18 and 2.4.0 kernels, and consequently this HOWTO tackles that solution, or procedure, alone. The instructions that follow were written to the 2.2.18 compile tune, but the procedure is similar enough to be translatable to the 2.4.0 (if you feel safe with this beast (see below)). Use your head, as Tony Buzan would say.
</para>
<para>
@ -55,7 +55,7 @@ get and install X4.x
<listitem>
<para>
get and compile kernel 2.4.0 (including mknod agpgart stuff)
get and compile kernel 2.2.18 or 2.4.0 (including mknod agpgart stuff)
</para>
</listitem>
@ -121,14 +121,14 @@ That is the end of this stage.
</sect2>
<sect2>
<title>Get and compile kernel 2.4.0 (including mknod agpgart stuff)</title>
<title>Get and compile kernel 2.2.18 or 2.4.0 (including mknod agpgart stuff)</title>
<para>
You can get kernel 2.4.0 from <ulink url="ftp://ftp.kernel.com"></ulink>. Of course, read everything called README while you are at it.
You can get either kernel from <ulink url="ftp://ftp.kernel.com"></ulink>. Of course, read everything called README while you are at it. When I first fixed this i810 problem I used a test kernel (2.4.0-test1) which worked fine for me. Since the official 2.4.0 has come out I have tried to compile it on both Red Hat and Debian, but without success. At the moment my suspiscion is that there are errors in the Makefile (any help with this would be greatly appreciated!) which seem to be producing a bad bzImage. Anyway, at reboot the new kernel hangs before it even gets going. For this reason I suggest you use either 2.2.18, or if you are the daring kind, 2.4.0-test1. I know both of them work. If you have had no problems with the 2.4.0 kernel proper, please let me know.
</para>
<para>
For each of the kernel updates/compiles I have done, I have always chucked the kernel source file in my home directory, then run the following sequence, which I learned from a linuxnewbie article to which you should refer if my directions are not clear enough for you. It can be found at the following address; <ulink url="http://www.linuxnewbie.org/nfh/intel/compiling/kernel_update.html"></ulink>. Of course, the location of the still-packed kernel is not really relevant, it only matters that it is unpacked in a conventional place. I personally use my home directory for no stronger reason than it seems neat and is easy to remember. OK, now for the commands:
For each of the kernel updates/compiles I have done, I have always chucked the kernel source file in my home directory, then run the following sequence, which I learned from a linuxnewbie article (to which you should refer if my directions are not clear enough for you). It can be found at the following address; <ulink url="http://www.linuxnewbie.org/nfh/intel/compiling/kernel_update.html"></ulink>. Of course, the location of the still-packed kernel is not really relevant, it only matters that it is unpacked in a conventional place. I personally use my home directory for no stronger reason than it seems neat and is easy to remember. OK, now for the commands:
<simplelist type=vert columns=1>
<member><userinput>cd /usr/src</userinput></member>
@ -155,7 +155,7 @@ Then open the sources file
</para>
<para>
<userinput>tar -xzvf /home/[whatever]/linux-2.4.0.tar.gz</userinput>
<userinput>tar -xzvf /home/[whatever]/linux-2.2.18.tar.gz</userinput>
</para>
<para>
@ -163,7 +163,7 @@ and watch the screen spew out pages of information about what's happening. When
</para>
<para>
<userinput>mv linux linux-2.4.0</userinput>
<userinput>mv linux linux-2.2.18</userinput>
</para>
<para>
@ -171,11 +171,11 @@ then create a new symbolic link as follows:
</para>
<para>
<userinput>ln -s linux-2.4.0 linux</userinput>
<userinput>ln -s linux-2.2.18 linux</userinput>
</para>
<para>
This is a more important stage than it appears. Some scripts refer to <filename class=directory>/usr/src/linux</filename> and if they do not find it they will not run. And it is useful to name the kernel source folders themselves by their release number for two reasons. First for clarity and second because if you are compiling various kernels you will probably want to keep the ones you know are stable for safety reasons. If you are <emphasis>sure</emphasis> you will only need the 2.4.0 kernel, then you need only store the one source folder and call it simply <filename class=directory>/usr/src/linux</filename>, in which case, all the stuff I have included here is of no relevence to you. Again, I invite the reader to use his/her imagination.
This is a more important stage than it appears. Some scripts refer to <filename class=directory>/usr/src/linux</filename> and if they do not find it they will not run. And it is useful to name the kernel source folders themselves by their release number for two reasons. First for clarity and second because if you are compiling various kernels you will probably want to keep the ones you know are stable for safety reasons. If you are <emphasis>sure</emphasis> you will only need the 2.2.18 kernel, then you need only store the one source folder and call it simply <filename class=directory>/usr/src/linux</filename>, in which case, all the stuff I have included here is of no relevence to you. Again, I invite the reader to use his/her imagination.
</para>
<para>
@ -269,10 +269,10 @@ Now have a look at the <filename class=directory>/boot</filename> directory. You
Then new symbolic links need to be created to the about-to-be-copied-over-while-simultaneously-being-renamed, recently created files. It goes like this (assuming you have an i386 computer):
<simplelist type=vert columns=1>
<member><userinput>cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.0</userinput></member>
<member><userinput>ln -s /boot/vmlinuz-2.4.0 /boot/vmlinuz</userinput></member>
<member><userinput>cp /usr/src/linux/System.map /boot/System.map-2.4.0</userinput></member>
<member><userinput>ln -s /boot/System.map-2.4.0 /boot/System.map</userinput></member>
<member><userinput>cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.18</userinput></member>
<member><userinput>ln -s /boot/vmlinuz-2.2.18 /boot/vmlinuz</userinput></member>
<member><userinput>cp /usr/src/linux/System.map /boot/System.map-2.2.18</userinput></member>
<member><userinput>ln -s /boot/System.map-2.2.18 /boot/System.map</userinput></member>
</simplelist>
</para>
@ -286,7 +286,7 @@ You don't need to use absolute pathnames if you are within <filename class=direc
Now you need to tell <command>lilo</command> about all your masterly work. This is achieved thusly. First edit your <filename class=headerfile>/etc/lilo.conf</filename> file as follows, by adding the following type of thing somewhere after the first (generic) stanza:
<simplelist type=vert columns=1>
<member><computeroutput>image=/boot/vmlinuz-2.4.0</computeroutput></member>
<member><computeroutput>image=/boot/vmlinuz-2.2.18</computeroutput></member>
<member><computeroutput>label=[what-ever-you-want-that-is-relevant-easy-to-type-and-remember]</computeroutput></member>
<member><computeroutput>read-only</computeroutput></member>
<member><computeroutput>root=/dev/hda[n]</computeroutput></member>
@ -429,7 +429,7 @@ So if X reports errors about a "shape extender" or "shape extension", you may we
<title>Thank you</title>
<para>
I must point out that I would not have known how to fix the i810 and X4.x problem if it were not for the pioneering efforts of Val Henson who guided me through the process and recommended the 2.4.0 kernel in the first place. And now that this is an ammended version, I would also like to thank Heron Ordonez for pointing out a few problems which I have in part addressed, and will fully address in due course. This is an open process and all comments (politely phrased of course!) are welcome.
I must point out that I would not have known how to fix the i810 and X4.x problem if it were not for the pioneering efforts of Val Henson who guided me through the process and recommended the 2.4.0 kernel in the first place. And now that this is an ammended version, I would also like to thank Heron Ordonez for pointing out a few problems which I have in part addressed, and will fully address in due course. Curtis Stone pointed out to me that the features I thought only available in the 2.4.0 kernel were present in 2.2.18. Thanks to him too. If this process carries on in this fashion the 'Thank you' will one day be the largest section of this HOWTO. This is an open process and all comments (politely phrased of course!) are welcome.
</para>
</sect1>