/[gentoo]/xml/htdocs/doc/en/udev-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/udev-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.53 Revision 1.54
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.53 2011/03/12 05:44:14 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.54 2011/09/11 08:43:18 swift Exp $ -->
4 4
5<guide> 5<guide>
6<title>Gentoo udev Guide</title> 6<title>Gentoo udev Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
21 21
22<!-- The content of this document is licensed under the CC-BY-SA license --> 22<!-- The content of this document is licensed under the CC-BY-SA license -->
23<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 23<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
24<license/> 24<license/>
25 25
26<version>8</version> 26<version>9</version>
27<date>2011-03-11</date> 27<date>2011-09-11</date>
28 28
29<chapter> 29<chapter>
30<title>What is udev?</title> 30<title>What is udev?</title>
31<section> 31<section>
32<title>The /dev Directory</title> 32<title>The /dev Directory</title>
189<title>udev and nvidia</title> 189<title>udev and nvidia</title>
190<body> 190<body>
191 191
192<p> 192<p>
193If you use the proprietary driver from nVidia and the X server fails to start on 193If you use the proprietary driver from nVidia and the X server fails to start on
194a udev-only system, then make sure you have: 194a udev-only system, then make sure you have the <c>nvidia</c> module listed in
195<path>/etc/conf.d/modules</path>.
195</p> 196</p>
196
197<ul>
198 <li>
199 the <c>nvidia</c> module listed in
200 <path>/etc/modules.autoload.d/kernel-2.6</path>
201 </li>
202 <li>
203 a version of baselayout equal to or greater than
204 <c>sys-apps/baselayout-1.8.12</c>
205 </li>
206</ul>
207 197
208</body> 198</body>
209</section> 199</section>
210<section> 200<section>
211<title>No Consistent Naming between DevFS and udev</title> 201<title>No Consistent Naming between DevFS and udev</title>
345# <i>update-modules</i> 335# <i>update-modules</i>
346</pre> 336</pre>
347 337
348<p> 338<p>
349Next, load the modules in the correct order. Add them to 339Next, load the modules in the correct order. Add them to
350<path>/etc/modules.autoload.d/kernel-2.6</path> <e>in the exact order you want 340<path>/etc/conf.d/modules</path> <e>in the exact order you want
351them loaded</e>. 341them loaded</e>.
352</p> 342</p>
353 343
354<pre caption="Loading modules in the correct order"> 344<pre caption="Loading modules in the correct order">
355# <i>echo "budget" >> /etc/modules.autoload.d/kernel-2.6</i> 345# <i>nano -w /etc/conf.d/modules</i>
356# <i>echo "b2c2-flexcop-pci" >> /etc/modules.autoload.d/kernel-2.6</i> 346
347modules="<i>budget b2c2-flexcop-pci</i>"
357</pre> 348</pre>
358 349
359</body> 350</body>
360</section> 351</section>
361<section> 352<section>
362<title>Other issues</title> 353<title>Other issues</title>
363<body> 354<body>
364
365<p>
366If device nodes are not created when a module is loaded from
367<path>/etc/modules.autoload.d/kernel-2.6</path> but they appear when you load
368the module manually with modprobe then you should try upgrading to
369<c>sys-apps/baselayout-1.8.12</c> or later.
370</p>
371 355
372<p> 356<p>
373Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the 357Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the
374kernel starting from version 2.6.6-rc2. 358kernel starting from version 2.6.6-rc2.
375</p> 359</p>

Legend:
Removed from v.1.53  
changed lines
  Added in v.1.54

  ViewVC Help
Powered by ViewVC 1.1.20