swift 13/03/20 20:44:09 Modified: udev-guide.xml Log: Further fix bug #462488 - Updates on udev guide
Revision Changes Path 1.58 xml/htdocs/doc/en/udev-guide.xml file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.58&view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.58&content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.57&r2=1.58 Index: udev-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v retrieving revision 1.57 retrieving revision 1.58 diff -u -r1.57 -r1.58 --- udev-guide.xml 20 Mar 2013 15:58:35 -0000 1.57 +++ udev-guide.xml 20 Mar 2013 20:44:09 -0000 1.58 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.57 2013/03/20 15:58:35 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.58 2013/03/20 20:44:09 swift Exp $ --> <guide> <title>Gentoo udev Guide</title> @@ -23,7 +23,7 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>13</version> +<version>14</version> <date>2013-03-20</date> <chapter> @@ -136,113 +136,12 @@ </chapter> <chapter> -<title>Known Issues</title> -<section> -<title>No Consistent Naming between DevFS and udev</title> -<body> - -<p> -Even though our intention is to have a consistent naming scheme between both -dynamical device management solutions, sometimes naming differences do occur. -</p> - -<p> -One reported clash is with a HP Smart Array 5i RAID controller (more precisely -the <c>cciss</c> kernel module). With udev, the devices are named -<path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the -devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from -<path>/dev/cciss/cXdY</path>. -</p> - -<p> -If this is the case, don't forget to update your <path>/etc/fstab</path> and -bootloader configuration files accordingly. -</p> - -<p> -The same happens with all-round symlinks that used to exist in -<path>/dev</path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't -create anymore. Be certain to check your X configuration file and see if the -Device rule for your mouse points to an existing device file. -</p> - -<p> -Another issue is the difference in naming of terminals between devfs and udev. -While devfs calls its terminals <c>tty</c>, udev calls them <c>vc</c> and -<c>tty</c>. This could lead to a problem in case you are restricting root -logins from consoles using <path>/etc/securetty</path>. You will need to make -sure that both <c>tty1</c> and <c>vc/1</c> are listed in -<path>/etc/securetty</path> to ensure that root can login using the console. -</p> - -</body> -</section> -<section> -<title>udev loads modules in an unpredictable order</title> -<body> - -<p> -Sometimes udev loads modules in an undesired, unpredictable, or seemingly random -order. This is especially common for systems that have multiple devices of the -same type, as well as multimedia devices. This can affect the assigned numbers -of devices; for example, sound cards may sometimes swap numbers. -</p> - -<p> -There are a few solutions to fix device numbers and/or module load order. -Ideally, you can just use module parameters to specify your desired device -number. Some modules, such as ALSA, include the "index" parameter. Modules that -use the index parameter can be adjusted as shown. This example is for a system -with two sound cards. The card with an index of 0 is designated as the first -card. Once the parameters are changed, the module config files must be updated. -</p> - -<pre caption="Specifying module parameters"> -# <i>echo "option snd-ice1724 index=0" >> /etc/modprobe.d/alsa.conf</i> -# <i>echo "option snd-ymfpci index=1" >> /etc/modprobe.d/alsa.conf</i> -# <i>update-modules</i> -</pre> - -<p> -The above example is the preferred solution, but not all modules support -parameters such as index. For these modules, you'll have to force the correct -module load order. First, you must stop udev from autoloading the modules by -blacklisting them. Be sure to use the exact name of the module being loaded. -For PCI devices, you'll need to use the module names obtained from the output of -<c>lspci -k</c>, available in the <c>pciutils</c> package. The following example -uses DVB modules. -</p> - -<pre caption="Blacklisting modules"> -# <i>echo "blacklist b2c2-flexcop-pci" >> /etc/modprobe.d/dvb</i> -# <i>echo "blacklist budget" >> /etc/modprobe.d/dvb</i> -# <i>update-modules</i> -</pre> - -<p> -Next, load the modules in the correct order. Add them to -<path>/etc/conf.d/modules</path> <e>in the exact order you want -them loaded</e>. -</p> - -<pre caption="Loading modules in the correct order"> -# <i>nano -w /etc/conf.d/modules</i> - -modules="<i>budget b2c2-flexcop-pci</i>" -</pre> - -</body> -</section> -</chapter> - -<chapter> <title>Resources & Acknowledgements</title> <section> <body> <p> -<uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames";> -Documentation for using the new predictable network interface names.</uri> +Documentation for using <uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames";>the new predictable network interface names.</uri> </p> <p>
