PLDWWW: UdevFAQ

PatrykZawadzki PatrykZawadzki at pld-linux.org
Wed Dec 28 17:33:35 CET 2005


Author: PatrykZawadzki   Date: Wed Dec 28 16:33:35 2005 GMT
Module: PLDWWW   URL: http://pld-linux.org/UdevFAQ
---- Log message:


---- Page affected: UdevFAQ

---- Diffs:

================================================================
  
  ''Minimum recommended version is 2.6.12.x'' (udev hotplug won't work with the older)
  
- == Udev doesn't load all modules for me! ==
+ == Udev doesn't load all modules ==
  
- ...that's because it loads only modules for PCI devices that meet the requirements included in udev rules. That rules allow auto-loading feature only for internal USB devices (hubs), such as `uhci-hcd` or `ehci-hcd`.
+ That's because it loads only modules for PCI devices that meet the requirements included in udev rules. That rules allow auto-loading feature only for internal USB devices (hubs), such as `uhci-hcd` or `ehci-hcd`.
  
  If you want to get the modules of all devices loaded automatically, enable `udevsynthetize` in `/etc/udev/udev.conf`. This is experimental and not fully tested though.
  
  == What about hotplug? Will my pendrive work? ==
  
- Hotplug included in current udev replaces the old hotplug completely. Paralell work of both is rather not advisable, so after udev's installation the old hotplug is uninstalled.
+ `hotplug` included in current udev replaces the old `hotplug` completely. Parallel work of both is not recommended, so after `udev` is installed the old `hotplug` package is removed.
+ 
- USB pendrive will work like a charm if you read answer no. 1.
+ USB pendrives will work like a charm if you read answer no. 1.
  
  == I'd like to connect my digital camera/scanner/other USB device to my computer. Do I have to mount /proc/bus/usb with proper permissions? ==
  
- Absolutely not. Install `udev-digicam` package, add yourself to the digicam group, and udev's agent will do the rest, no matter if that's a scanner or other USB input device you connected.
+ Absolutely not. Install `udev-digicam` package, add yourself to the ''digicam'' group, and `udev`'s agent will do the rest, no matter if the device is a scanner or another USB input device.
  
  == Can udev automatically mount partitions or cd drives it finds? ==
  
- No. There are specialized programs for this, like `gnome-volume-manager`.
+ While technically possible, `udev` is not designed to manage your ''/etc/fstab'' entries. There are specialized programs for this, like `gnome-volume-manager`.
  
  == I'm using nvidia-legacy and the /dev/nvidia* is not created! ==
  
- That's a problem of nvidia (legacy) drivers. udev has nothing to do with it. Unfortunately, you must manually create proper device files using {{{mknod}}}.
+ That's a problem of `nvidia` (legacy) drivers. `udev` has nothing to do with it. Unfortunately, you must manually create proper device files using `mknod`.
  
- You can make {{{modprobe}}} create these devices for you every time the module is loaded by adding the following line to your ''/etc/modprobe.conf'':
+ You can make `modprobe` create these devices for you every time the `nvidia` module is loaded by adding the following line to your ''/etc/modprobe.conf'':
  
  {{{
  install nvidia /sbin/modprobe --ignore-install nvidia && { mknod /dev/nvidia0 c 195 0; mknod /dev/nvidia1 c 195 1; mknod /dev/nvidia2 c 195 2; mknod /dev/nvidia3 c 195 3; mknod /dev/nvidiactl c 195 255; /bin/true; }
@@ -48, +49 @@

  
  Note that this should be all in one line.
  
- == I have to manually load modules such as psmouse or evdev! Why? ==
+ == Modules like psmouse and evdev are not loaded automatically ==
  
- The kernel's input layer is broken. It's said to be fixed in 2.6.15...
+ The kernel's input layer is broken. It's said to be fixed in 2.6.15.
  
  == Do I have to add the usb-controller alias in /etc/modprobe.conf? ==
  
  No. All `*-hcd` modules are loaded automatically.
  
- == I get the error messages about failed agents in my system's logs! ==
+ == I get the error messages about failed agents in my system logs ==
  
- They don't work because they are not there - unless you installed `udev-digicam`, which has the usb agent. That udev warnings in logs don't look nice, but they are absolutely harmless. This will be fixed if there will be a person willing to fix it ;)
+ They don't work because they are not there - unless you installed `udev-digicam`, which has the usb agent. That udev warnings in logs don't look nice, but they are absolutely harmless. This will be fixed if there is a person willing to fix it.
  
- == I've got a problem which is not covered here. How do I diagnose it? ==
+ == I've got a problem that is not covered here. How do I diagnose it? ==
  
- Set `udev_log` to "info" in `/etc/udev/udev.conf` to improve verbosity of udev, use `udevmonitor` (`man udevmonitor`) to get even more infomation, check the linux-hotplug list's archive http://marc.theaimsgroup.com/?l=linux-hotplug-devel.
+ Set `udev_log` to ''info'' in `/etc/udev/udev.conf` to improve verbosity of udev, use `udevmonitor` (see `man udevmonitor`) to get even more infomation, check the ''linux-hotplug'' list's archive at http://marc.theaimsgroup.com/?l=linux-hotplug-devel.
+ 
  If still unsure, ask your question on PLD [:MailingLists:mailing lists].
  


More information about the pld-cvs-commit mailing list