Changeset 4064

Timestamp:

07/02/06 22:15:09 (2 years ago)

Author:

ruik

Message:

Transion to new website, part2 - move more links, fix the CVS->SVN

Files:

• lm-sensors/trunk/README (modified) (1 diff)
• lm-sensors/trunk/README.directories (modified) (1 diff)
• lm-sensors/trunk/doc/FAQ (modified) (8 diffs)
• lm-sensors/trunk/doc/busses/i2c-piix4 (modified) (1 diff)
• lm-sensors/trunk/doc/developers/genpasswd.pl (deleted)
• lm-sensors/trunk/doc/developers/makefiles (modified) (1 diff)
• lm-sensors/trunk/doc/developers/new_drivers (modified) (2 diffs)
• lm-sensors/trunk/doc/fancontrol.txt (modified) (1 diff)
• lm-sensors/trunk/doc/lm_sensors-FAQ.html (modified) (112 diffs)
• lm-sensors/trunk/doc/lm_sensors-FAQ.texi (modified) (9 diffs)
• lm-sensors/trunk/kernel/busses/i2c-sis645.c (modified) (1 diff)
• lm-sensors/trunk/prog/detect/sensors-detect (modified) (1 diff)
• lm-sensors/trunk/prog/pwm/fancontrol (modified) (1 diff)
• lm-sensors/trunk/version.h (modified) (1 diff)

lm-sensors/trunk/README

@@ -47 +47 @@
-
-
-CVS
+SVN
-the cutting edge. Things may not even compile! On the other hand, you will
-be the first to profit from new drivers and other changes. Have fun!

lm-sensors/trunk/README.directories

@@ -1 +1 @@
-The directories within this package:
-
-* CVS
-  The CVS directories. Do not touch these!
-* doc
-  Documentation about the modules within this package, and all other things.

lm-sensors/trunk/doc/FAQ

@@ -121 +121 @@
-6 How to Contribute
-  6.1 How to write a driver
-CVS
+SVN
-  6.3 How to donate hardware to the project
-  6.4 How to join the project mailing lists
@@ -193 +193 @@
-   * `http://www.national.com'
-
-
-
-
+
+
-
-2 Sensor and Bus Basics
@@ -359 +358 @@
-  4. Check the Motherboard Monitor (http://mbm.livewiredev.com/)
-     website and the "links"
-
-
-
+
+
-
-3.2.2 Do you support motherboard XYZ?
@@ -376 +374 @@
-
-   * Sorted by Manufacturer:
-2.lm-sensors.nu/~lm78/supported.html
+.lm-sensors.org/wiki/SupportedDevices
-
-   * Sorted by Sensor Driver:  `doc/chips/SUMMARY'
-
-   * Newest Driver Status:
-2.lm-sensors.nu/~lm78/newdrivers.html
+.lm-sensors.org/wiki/NewDrivers
-
-3.2.4 Anybody working on a driver for chip XYZ?
------------------------------------------------
-
-2.lm-sensors.nu/~lm78/newdrivers.html
+.lm-sensors.org/wiki/NewDrivers
-
-3.3 Which modules should I insert?
@@ -739 +737 @@
-which does the job, though you might want to examine one of the
-graphical monitor programs under X, see
-2.lm-sensors.nu/~lm78/useful_addresses.html
+.lm-sensors.org/wiki/UsefulLinks
-
-4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?
@@ -1101 +1099 @@
-
-   When you know what chips you have, check the Newest Driver Status
-2.lm-sensors.nu/~lm78/newdrivers.html) web page to see if
-support 
+.lm-sensors.org/wiki/NewDrivers) web page to see if support
+
-
-4.25 Sensors says `Error: Line xxx: zzzzzzz'
@@ -1273 +1271 @@
-
-   Instead of using email, you can also use the web-based support area,
- helped
-
-
+
+
+will be 
-
-   Here's what you should send us:
@@ -1449 +1447 @@
-See `doc/developers/new_drivers' in our package for instructions.
-
-CVS
+SVN
-=========================
-
-
-
-
-
-
-
-
-
-
+
+
+
+
-
-6.3 How to donate hardware to the project
-=========================================
-
-2.lm-sensors.nu/~lm78/author.html#contac
+.lm-sensors.org/wiki/FeedbackAndSuppor
-
-6.4 How to join the project mailing lists

lm-sensors/trunk/doc/busses/i2c-piix4

@@ -98 +98 @@
-the SMBus on all IBM systems (detected using DMI data.)
-
-
-
+

lm-sensors/trunk/doc/developers/makefiles

@@ -33 +33 @@
-    a user-supplied version number.
-  * package
-CVS
+SVN
-  * src/lm78.o, i2c/i2c-core.o, ...
-    You can of course also specify one or more targets to make.

lm-sensors/trunk/doc/developers/new_drivers

@@ -26 +26 @@
-* Consider subscribing to the mailing list.
-
-CVS
+SVN
-  You should use this as a base for your development.
-  See instructions on our download page.
@@ -125 +125 @@
-  new driver so we know you are giving it to us under the GPL.
-
-
-
-
-
-
-
-
-
+
+
+
-
-* If you want to have your driver integrated to Linux 2.6, you have to

lm-sensors/trunk/doc/fancontrol.txt

@@ -8 +8 @@
-configuration from a file, then calculates fan speeds from temperatures and
-sets the corresponding pwm outputs to the computed values.  It is included in
-CVS
+SVN
-at http://www.hdev.de/fancontrol/ For easy configuration, there's a script
-named pwmconfig which lets you interactively write your configuration file for

lm-sensors/trunk/doc/lm_sensors-FAQ.html

@@ -4 +4 @@
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Sensors FAQ for lm_sensors version 2.18">
-7
+8
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
@@ -15 +15 @@
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-
-
+
+
+
---></style>
-</head>
@@ -72 +73 @@
-</li></ul>
-<li><a href="#Section-3_002e3">3.3 Which modules should I insert?</a>
-pan class="file">/etc/sensors.conf</span
+amp><span class="file">/etc/sensors.conf</span></samp
-<ul>
-pan class="command">sensors</span
-pan class="command">sensors</span
-pan class="file">/etc/sensors.conf</span
+amp><span class="command">sensors</span></samp
+amp><span class="command">sensors</span></samp
+amp><span class="file">/etc/sensors.conf</span></samp
-<li><a href="#Section-3_002e4">3.4.4 One sensor isn't hooked up on my board!</a>
-pan class="file">sensors.conf</span
-pan class="file">sensors.conf</span
+amp><span class="file">sensors.conf</span></samp
+amp><span class="file">sensors.conf</span></samp
-</li></ul>
-<span class="samp">No such file or directory</span>
+`<samp><span class="samp">No such file or directory</span></samp>'
-<li><a href="#Section-3_002e6">3.6 I get all kinds of weird compilation errors?</a>
-<ul>
-<span class="samp">No rule to make target xxxx needed by xxxx</span>
+`<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>'
-</li></ul>
-<li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a>
-pan class="command">make install</span
-pan class="command">modprobe</span
+amp><span class="command">make install</span></samp
+amp><span class="command">modprobe</span></samp
-<li><a href="#Section-3_002e10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a>
-</li></ul>
@@ -112 +113 @@
-<li><a href="#Section-4_002e11">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</a>
-<li><a href="#Section-4_002e12">4.12 My BIOS reports a much higher CPU temperature than your modules!</a>
-pan class="file">/proc</span
+amp><span class="file">/proc</span></samp
-<li><a href="#Section-4_002e14">4.14 How do I set new limits?</a>
-<ul>
@@ -132 +133 @@
-</li></ul>
-<li><a href="#Section-4_002e18">4.18 How do I configure two chips (LM87) differently?</a>
-<span class="samp">Upgrade BIOS</span>
+`<samp><span class="samp">Upgrade BIOS</span></samp>'
-<ul>
-<span class="samp">use force_addr=0xaddr</span>
+`<samp><span class="samp">use force_addr=0xaddr</span></samp>'
-</li></ul>
-<span class="samp">Can't access procfs/sysfs file</span>
-<span class="samp">No sensors found!</span>
+`<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'
+`<samp><span class="samp">No sensors found!</span></samp>'
-<li><a href="#Section-4_002e22">4.22 Sensors output is not correct!</a>
-<li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a>
@@ -151 +152 @@
-<li><a href="#Section-4_002e24">4.24.3 Sensors-detect doesn't find any sensors!</a>
-</li></ul>
-<span class="samp">Error: Line xxx: zzzzzzz</span>
+`<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'
-<li><a href="#Section-4_002e26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a>
-<span class="samp">ERROR: Can't get xxxxx data!</span>
+`<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'
-<li><a href="#Section-4_002e28">4.28 Sensors doesn't find any sensors, just eeproms.</a>
-<li><a href="#Section-4_002e29">4.29 Inserting modules hangs my board</a>
@@ -186 +187 @@
-<ul>
-<li><a href="#Section-6_002e1">6.1 How to write a driver</a>
-CVS
+SVN
-<li><a href="#Section-6_002e3">6.3 How to donate hardware to the project</a>
-<li><a href="#Section-6_002e4">6.4 How to join the project mailing lists</a>
@@ -200 +201 @@
-<div class="node">
-<p><hr>
-
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>
-
+
-</div>
-
@@ -223 +225 @@
-<div class="node">
-<p><hr>
-
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+
-</div>
-
@@ -239 +242 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
-
+
-</div>
-
@@ -259 +264 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e1">Section 1.1</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
-
+
-</div>
-
@@ -284 +291 @@
-
-   <p>Most other sensor chips have comparable functionality. Each supported
-
-
-
-
-
+
+
+
+
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
-
+
-</div>
-
@@ -307 +316 @@
-</ul>
-
-2.lm-sensors.nu/~lm78/useful_addresses.html">http://www2.lm-sensors.nu/~lm78/useful_addresses.html
+.lm-sensors.org/wiki/UsefulLinks">http://www.lm-sensors.org/wiki/UsefulLinks
-for links to other companies' websites.
-
-<div class="node">
-<p><hr>
-
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Overview">Overview</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+
-</div>
-
@@ -331 +341 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -339 +351 @@
-
-<p>Sensor chips reside on either the ISA bus, the SMBus, or both. 
-pan class="file">doc/chips/SUMMARY</span
+amp><span class="file">doc/chips/SUMMARY</span></samp
-
-   <p>To communicate with chips on the ISA bus, the software uses
@@ -349 +361 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e1">Section 2.1</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -377 +391 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e2">Section 2.2</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -390 +406 @@
-where many "legacy" functions, such as keyboard and interrupt controllers,
-are found. It isn't necessarily a separate physical bus. 
-pan class="file">/proc/ioports</span
+amp><span class="file">/proc/ioports</span></samp
-the "ISA Bus" in your system. If you don't like the term "ISA Bus"
-think "I/O Space".
@@ -396 +412 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e3">Section 2.3</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -411 +429 @@
-have circuitry for measuring the the electrical properties of
-an external diode and converting this data to a temperature. 
-pan class="file">doc/chips/SUMMARY</span
+amp><span class="file">doc/chips/SUMMARY</span></samp
-has support for more than one temperature supports external temperature sensing.
-
@@ -438 +456 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e4">Section 2.4</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -456 +476 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
-
+
-</div>
-
@@ -468 +490 @@
-the actual chip if both are supported; the LM80, for example, has only
-IRQ interrupts): IRQ interrupts and SMI interrupts.  IRQ stands for
-pan class="file">/proc/interrupts</span
+amp><span class="file">/proc/interrupts</span></samp
-SMI stands for System Management Interrupt, and is a special interrupt which
-puts the processor in a secure environment independent of any other things
@@ -482 +504 @@
-<div class="node">
-<p><hr>
-
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Basics">Basics</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
-
+
-</div>
-
@@ -494 +517 @@
-<li><a accesskey="2" href="#Section-3_002e2">Section 3.2</a>:      How do I know which chips I own? 
-<li><a accesskey="3" href="#Section-3_002e3">Section 3.3</a>:      Which modules should I insert? 
-pan class="file">/etc/sensors.conf</span
-<span class="samp">No such file or directory</span>
+amp><span class="file">/etc/sensors.conf</span></samp
+`<samp><span class="samp">No such file or directory</span></samp>'
-<li><a accesskey="6" href="#Section-3_002e6">Section 3.6</a>:      I get all kinds of weird compilation errors? 
-<li><a accesskey="7" href="#Section-3_002e7">Section 3.7</a>:      It still does not compile or patch! 
-pan class="command">make install</span
-pan class="command">modprobe</span
+amp><span class="command">make install</span></samp
+amp><span class="command">modprobe</span></samp
-<li><a href="#Section-3_002e10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
-</ul>
@@ -505 +528 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
@@ -518 +543 @@
-   <p>Here are two simple guidelines:
-     <ul>
-pan class="command">sensors-detect</span
-pan class="command">modprobe</span>, not <span class="command">insmod</span
-
-
-pan class="file">doc/modules</span
+amp><span class="command">sensors-detect</span></samp
+amp><span class="command">modprobe</span></samp>, not <samp><span class="command">insmod</span></samp
+
+
+amp><span class="file">doc/modules</span></samp
-
-   <p><a name="How-do-I-know-which-chips-I-own"></a>
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e1">Section 3.1</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
@@ -536 +563 @@
-
-<p>We have an excellent program that scans all your hardware. 
-pan class="file">sensors-detect</span> and is installed in <span class="file">/usr/local/sbin</span
-pan class="command">make install</span
+amp><span class="file">sensors-detect</span></samp> and is installed in <samp><span class="file">/usr/local/sbin</span></samp
+amp><span class="command">make install</span></samp
-
-   <p>Chip detection in the drivers is fairly good. That means that it is
@@ -563 +590 @@
-<li>Check the manufacturer's website or ask their support
-<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website and the
-2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/useful_addresses.html
-2.lm-sensors.nu/~lm78/
+.lm-sensors.org/wiki/UsefulLinks
+.lm-sensors.org
-        </ol>
-
@@ -579 +606 @@
-<p>This we have good answers for.
-     <ul>
-pan class="file">README</span
-2.lm-sensors.nu/~lm78/supported.html">http://www2.lm-sensors.nu/~lm78/supported.html
-pan class="file">doc/chips/SUMMARY</span
-2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html
+amp><span class="file">README</span></samp
+.lm-sensors.org/wiki/SupportedDevices">http://www.lm-sensors.org/wiki/SupportedDevices
+amp><span class="file">doc/chips/SUMMARY</span></samp
+.lm-sensors.org/wiki/NewDrivers">http://www.lm-sensors.org/wiki/NewDrivers
-</ul>
-
@@ -589 +616 @@
-<h4 class="subsection">3.2.4 Anybody working on a driver for chip XYZ?</h4>
-
-
-
-
-
-
+
+
+
+
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e2">Section 3.2</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
-<h3 class="section">3.3 Which modules should I insert?</h3>
-
-pan class="command">sensors-detect</span> will tell you. Take the <span class="command">modprobe</span
-pan class="file">/etc/rc.d/xxxx</span
+amp><span class="command">sensors-detect</span></samp> will tell you. Take the <samp><span class="command">modprobe</span></samp
+amp><span class="file">/etc/rc.d/xxxx</span></samp
-to be executed at startup.
-
-   <p>You need one module for each sensor chip and bus adapter you own;
-pan class="file">i2c-isa.o</span
+amp><span class="file">i2c-isa.o</span></samp
-for each type of chip you own. That's all. On my computer, I could use the
-following lines:
-     <ul>
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e3">Section 3.3</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
-
-
-pan class="file">/etc/sensors.conf</span
-
-pan class="file">libsensors,</span
-pan class="command">sensors</span
+
+
+
+amp><span class="file">/etc/sensors.conf</span></samp
+
+amp><span class="file">libsensors,</span></samp
+amp><span class="command">sensors</span></samp
-It tells libsensors how to translate the values the chip
-measures to real-world values. This is especially important for voltage
-inputs. The default configuration file should usually do the trick. 
-pan class="file">/etc/sensors.conf</span
+amp><span class="file">/etc/sensors.conf</span></samp
-overwrite any existing file with that name.
-
-   <p><a name="Section-3_002e4_002e1"></a>
-
-pan class="command">sensors</span
+amp><span class="command">sensors</span></samp
-
-<p>Every motherboard is different. You can customize the labels
-pan class="file">/etc/sensors.conf</span
-pan class="file">lib/chips.c</span> and <span class="file">/etc/sensors.conf</span
+amp><span class="file">/etc/sensors.conf</span></samp
+amp><span class="file">lib/chips.c</span></samp> and <samp><span class="file">/etc/sensors.conf</span></samp
-a template.
-
-   <p><a name="Section-3_002e4_002e2"></a>
-
-pan class="command">sensors</span
-
-pan class="file">/etc/sensors.conf</span
+amp><span class="command">sensors</span></samp
+
+amp><span class="file">/etc/sensors.conf</span></samp
-
-   <p><a name="Section-3_002e4_002e3"></a>
-
-pan class="file">/etc/sensors.conf</span
-
-pan class="command">sensors -s</span
+amp><span class="file">/etc/sensors.conf</span></samp
+
+amp><span class="command">sensors -s</span></samp
-
-   <p><a name="Section-3_002e4_002e4"></a>
@@ -661 +692 @@
-<h4 class="subsection">3.4.4 One sensor isn't hooked up on my board!</h4>
-
-pan class="command">ignore</span> line in <span class="file">/etc/sensors.conf</span
-pan class="command">sensors</span
+amp><span class="command">ignore</span></samp> line in <samp><span class="file">/etc/sensors.conf</span></samp
+amp><span class="command">sensors</span></samp
-
-   <p><a name="Section-3_002e4_002e5"></a>
-
-pan class="file">sensors.conf</span
+amp><span class="file">sensors.conf</span></samp
-
-<p>There is detailed help at the top of that file.
@@ -672 +703 @@
-   <p><a name="Section-3_002e4_002e6"></a>
-
-pan class="file">sensors.conf</span
+amp><span class="file">sensors.conf</span></samp
-
-<p>No. Good idea though. If you would like to set one up on your website
@@ -679 +710 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e4">Section 3.4</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
-
-
-<span class="samp">No such file or directory</span>
+
+
+
+`<samp><span class="samp">No such file or directory</span></samp>'
-
-<p>Don't worry about them. The dependency files (which tell which
-files should be recompiled when certain files change) are created
-pan class="command">make</span
+amp><span class="command">make</span></samp
-notices they are not there, and warns about that - and the first thing
-it will do is generate them. So all is well.
@@ -695 +728 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e5">Section 3.5</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
@@ -704 +739 @@
-
-<p>Check that the correct i2c header files are used. Depending on
-pan class="file">/usr/local/include</span
-pan class="file">/usr/src/linux*/include</span>. Try to edit the <span class="file">Makefile</span
+amp><span class="file">/usr/local/include</span></samp
+amp><span class="file">/usr/src/linux*/include</span></samp>. Try to edit the <samp><span class="file">Makefile</span></samp
-
-   <p><a name="Section-3_002e6_002e1"></a>
-
-<span class="samp">No rule to make target xxxx needed by xxxx</span>
+`<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>'
-
-     <ul>
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e6">Section 3.6</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
@@ -737 +774 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e7">Section 3.7</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e8">Section 3.8</a>,
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
-
-
-pan class="command">modprobe</span
+
+
+
+amp><span class="command">modprobe</span></samp
-
-<p>Example:
@@ -763 +804 @@
-     i2c_bit_del_bus_R92b18f49
-</pre>
-pan class="command">depmod -a -e</span
+amp><span class="command">depmod -a -e</span></samp
-
-   <p>These are module versioning problems. Generally you did not compile
@@ -769 +810 @@
-have is not for the kernel you are running. 
-You must compile our package against the source for the kernel you
-pan class="command">make LINUX=/usr/src/linux-2.4.14</span
+amp><span class="command">make LINUX=/usr/src/linux-2.4.14</span></samp
-
-   <p>Try the following to be sure:
-
-     <ul>
-pan class="command">nm --extern MODULE.o</span
+amp><span class="command">nm --extern MODULE.o</span></samp
-Filter out the kernel symbols, like <code>kmalloc</code>, <code>printk</code> etc. and note the
-number code behind them, like <code>printk_R1b7d4074</code>. If there is no numeric
-code after them, note this too. 
-pan class="command">grep SYMBOL /proc/ksyms</span
+amp><span class="command">grep SYMBOL /proc/ksyms</span></samp
-Substitute SYMBOL by the basename of the symbols above, like <code>kmalloc</code>,
-<code>printk</code> etc. Note the number code behind them, or the lack thereof. 
@@ -788 +829 @@
-<div class="node">
-<p><hr>
-
+
+
+
-Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
-
+
-</div>
-
@@ -801 +844 @@
-
-     <ol type=1 start=1>
-pan class="command">rpm -qa | grep i2c</span
-pan class="file">kernel-i2c,</span
+amp><span class="command">rpm -qa | grep i2c</span></samp
+amp><span class="file">kernel-i2c,</span></samp
-<li>&lt;as root&gt;
-pan c