- Timestamp:
- 03/25/2006 12:56:15 PM (19 years ago)
- Children:
- 11d4252
- Parents:
- 6d8d38c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/udev.xml
r6d8d38c rc0d9af5 89 89 available to userspace processes and to <command>udevd</command> for device 90 90 node creation.</para> 91 91 92 </sect3> 92 93 … … 113 114 have already been registered with the kernel by forcing them to raise 114 115 hotplug events which <command>udevd</command> will then handle.</para> 116 115 117 </sect3> 116 118 … … 135 137 rules configuration files are available in 136 138 <filename>/usr/share/doc/udev-&udev-version;/index.html</filename></para> 139 137 140 </sect3> 138 141 … … 167 170 <para>The kernel itself is also able to load modules for network 168 171 protocols, filesystems and NLS support on demand.</para> 172 169 173 </sect3> 170 174 … … 176 180 generates a hotplug event. This hotplug event is then handled by 177 181 <command>udevd</command> as described above.</para> 182 178 183 </sect3> 179 184 … … 188 193 <sect3> 189 194 <title>A kernel module is not loaded automatically</title> 195 190 196 <para>Udev will only load a module if it has a bus-specific alias and the 191 197 bus driver properly exports the necessary aliases to <systemitem … … 202 208 <filename class="directory">/sys/bus</filename> and check whether there is 203 209 a <filename>modalias</filename> file there.</para> 204 210 205 211 <para>If the <filename>modalias</filename> file exists in <systemitem 206 212 class="filesystem">sysfs</systemitem>, the driver supports the device and … … 214 220 this bus type. With Linux-&linux-version;, this is the case with ISA and 215 221 IDE busses. Expect this issue to be fixed in later kernel versions.</para> 216 222 217 223 <!-- Remove IDE from the list above after Linux-2.6.16 --> 218 224 … … 220 226 <emphasis>snd-pcm-oss</emphasis> and non-hardware drivers such as 221 227 <emphasis>loop</emphasis> at all.</para> 228 222 229 </sect3> 223 230 … … 233 240 wrapped module. To do this, add an <quote>install</quote> line in 234 241 <filename>/etc/modprobe.conf</filename>. For example:</para> 235 <screen role="nodump">install snd-pcm modprobe -i snd-pcm ; modprobe \ 236 snd-pcm-oss ; true</screen> 237 242 243 <screen role="nodump"><literal>install snd-pcm modprobe -i snd-pcm ; modprobe \ 244 snd-pcm-oss ; true</literal></screen> 245 238 246 <para>If the module in question is not a wrapper and is useful by itself, 239 247 configure the <command>S05modules</command> bootscript to load this … … 241 249 <filename>/etc/sysconfig/modules</filename> file on a separate line. 242 250 This works for wrapper modules too, but is suboptimal in that case.</para> 251 243 252 </sect3> 244 253 … … 249 258 <filename>/etc/modprobe.conf</filename> file as done with the 250 259 <emphasis>forte</emphasis> module in the example below:</para> 251 <screen role="nodump">blacklist forte</screen> 260 261 <screen role="nodump"><literal>blacklist forte</literal></screen> 252 262 253 263 <para>Blacklisted modules can still be loaded manually with the 254 264 explicit <command>modprobe</command> command.</para> 265 255 266 </sect3> 256 267 … … 263 274 Increase the logging verbosity of Udev, find the offending rule by 264 275 examining the logs and make it more specific.</para> 276 265 277 </sect3> 266 278 267 279 <sect3> 268 280 <title>Udev rule works unreliably</title> 281 269 282 <para>This may be another manifestation of the previous problem. If not, 270 283 and your rule uses <systemitem class="filesystem">sysfs</systemitem> … … 273 286 <systemitem class="filesystem">sysfs</systemitem> attribute and appending 274 287 it to the <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename> 275 file. Please notify the LFS Development list if you do so and it helps. 276 </para> 277 </sect3> 278 288 file. Please notify the LFS Development list if you do so and it 289 helps.</para> 290 291 </sect3> 292 279 293 <sect3> 280 294 <title>Udev does not create a device</title> 295 281 296 <para>Further text assumes that the driver is built statically into the 282 297 kernel or already loaded as a module, and that you have already checked 283 298 that Udev doesn't create a misnamed device.</para> 284 299 285 300 <para>Udev has no information needed to create a device node if a kernel 286 301 driver does not export its data to <systemitem … … 294 309 <filename class="directory">/dev</filename> by the 295 310 <command>S10udev</command> bootscript.</para> 296 </sect3> 297 311 312 </sect3> 313 298 314 <sect3> 299 315 <title>Device naming order changes randomly after rebooting</title> 316 300 317 <para>This is due to the fact that Udev, by design, handles uevents and 301 318 loads modules in parallel, and thus in an unpredictable order. This will … … 306 323 See also the network interface renaming example in 307 324 <xref linkend="ch-scripts-network"/>.</para> 308 </sect3> 309 325 326 </sect3> 327 310 328 </sect2> 311 329
Note:
See TracChangeset
for help on using the changeset viewer.