Arch Linux

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!
Tasklist

FS#14557 - udev, load-modules.sh wants to load modules which are none

Attached to Project: Arch Linux
Opened by Thomas Bohn (tehabe) - Saturday, 02 May 2009, 11:52 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 03 May 2009, 09:30 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When I boot my eeePC 1000H, I get this messages in my messages.log:

---snip---
May 2 13:31:40 proton load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
May 2 13:31:40 proton load-modules.sh: 'pci:v00008086d000027A6sv00001043sd00008340bc03sc80i00' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: Not loading module 'snd_pcsp' for alias 'platform:pcspkr' because it is blacklisted
May 2 13:31:41 proton load-modules.sh: 'platform:vesafb' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:SYN0A04:SYN0A00:SYN0002:PNP0F13:' is not a valid module or alias name
May 2 13:31:41 proton load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
May 2 13:31:42 proton load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr1902:bd03/25/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:' is not a valid module or alias name
May 2 13:31:43 proton load-modules.sh: 'usb:v04F2pB071d1544dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
---snip---

Installed udev 141-1
Installed kernel 2.6.29.2-1.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 03 May 2009, 09:30 GMT
Reason for closing:  Duplicate
Additional comments about closing:  13852
Comment by Jan de Groot (JGC) - Saturday, 02 May 2009, 13:56 GMT
This is normal when using hotplugging. Udev tries to autoload modules for each and every hardware device it finds in your system. Unfortunate, not every device has a module that suits this alias, so you'll get these messages.

Loading...