Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#3995 - Virtually useless MODULES array
Attached to Project:
Arch Linux
Opened by Jaroslaw Swierczynski (swiergot) - Saturday, 18 February 2006, 11:02 GMT
Opened by Jaroslaw Swierczynski (swiergot) - Saturday, 18 February 2006, 11:02 GMT
|
DetailsSince loading modules from rc.conf's MODULES array has been moved before udev, the array is mostly useless. I have lirc-serial and em8300 in the array and here is my modprobe.conf:
install lirc-serial setserial /dev/ttyS0 uart none ; modprobe -i lirc-serial ; true install em8300 modprobe adv717x ; modprobe -i em8300 ; true It all worked before but initscripts 0.7.1-21 broke it. When setserial is executed, /dev/ttyS0 does not exist although serial port support is built into kernel. As for em8300, it can't create device files because udev is not running (FYI, em8300 is not detected by udev). As a result, I might as well remove the modules from the MODULES array because I have to load them anew in rc.local anyway. I fail to understand why this was done but obviously it's wrong. |
This task depends upon
if [ `pidof -o %PPID /sbin/udevd` ]; then
pidof gives more than one number which causes syntax error. The fix is simple:
if [ "`pidof -o %PPID /sbin/udevd`" ]; then
Now, the answer to you question is yes and no. Yes - the em8300 module creates all devices. No - /dev/ttyS0 still doesn't exist and setserial fails. May I ask why the MODULES array is processed before starting udev?
is module laoding still triggered before starting udev?