Arch Linux

wriggary

Member

Registered: 2009-06-30

Posts: 65

load-modules.sh and other log stuff that i'm worried about

Hello everyone.

I was going through my log files today.  Its been the first time I've really looked at them since I reinstalled (about two weeks ago).

Anyway, some interesting stuff in there this time. 

First off load-modules.sh is dropping a lot of errors into everything.log (the other stuff is there so you know where in the log you are looking):

Feb 17 14:32:23 leviathon kernel: skge eth0: Link is up at 100 Mbps, full duplex, flow control both
Feb 17 14:32:23 leviathon kernel: NET: Registered protocol family 10
Feb 17 14:32:23 leviathon kernel: lo: Disabled Privacy Extensions
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001106d00002282sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001106d00004282sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr1010.003:bd01/26/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001106d00007282sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001022d00001100sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001106d00003282sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001106d00001282sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001022d00001101sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001002d00004E48sv00001002sd00004F72bc03sc00i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: Not loading module alias 'pcspkr' because it is blacklisted
Feb 17 14:32:16 leviathon load-modules.sh: 'pci:v00001002d00004E68sv00001002sd00004F73bc03sc80i00' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:LNXSYBUS:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:16 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0501:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:PNP0501:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:17 leviathon load-modules.sh: 'acpi:device:' is not a valid module or alias name
Feb 17 14:32:21 leviathon init: Entering runlevel: 5

Its a builder board, an asus A8V deluxe, with a radeon 9800 AIW for the graphics.  I'm using udev 151-3 and mkinitcpio 0.6.2-1 from core.

Should load-modules.sh be trying all these aliases?  I do have autodetect as one of my mkinitcpio.conf hooks.  Is that hook responsible for trying to load all these aliases?  If so, I'm pretty sure I can get by with less in my initcpio.  I don't even have a sata drive in this box, so I should be able to get by with HOOKS="base udev pata filesystems"

And on a slightly related note, does anyone else get these while they are running X?

Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02a2000-d02b2000
Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02b2000-d02c2000
Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02c2000-d02d2000
Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02d2000-d02e2000
Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02e2000-d02f2000
Feb 18 14:13:47 leviathon kernel: X:3373 freeing invalid memtype d02f2000-d0302000

It used to happen sometimes on the xorg-server 1.6 line, but seems to happen much more while I'm running xorg-server 1.7.  A quick count through everything.log, there are about 80 of those messages with a simultaneous timestamp, and about 40 earlier from me playing the UT2004 demo, all in adjacent memory ranges.

Could this be causing it? (this is while X is loading)

Feb 18 14:13:48 leviathon kernel: agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
Feb 18 14:13:48 leviathon kernel: agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
Feb 18 14:13:48 leviathon kernel: pci 0000:01:00.0: putting AGP V3 device into 8x mode
Feb 18 14:13:49 leviathon kernel: [drm] Setting GART location based on new memory map
Feb 18 14:13:49 leviathon kernel: [drm] Loading R300 Microcode
Feb 18 14:13:49 leviathon kernel: platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin
Feb 18 14:13:49 leviathon kernel: [drm] Num pipes: 2
Feb 18 14:13:49 leviathon kernel: [drm] writeback test succeeded in 1 usecs
Feb 18 14:13:49 leviathon load-modules.sh: 'platform:radeon_cp' is not a valid module or alias name

Also, in Xorg.0.log, there is a message about radeon microcode:

(EE) RADEON(0): Microcode: cannot load microcode

Note: I have kernel modesetting disabled for the time being.  I couldn't get it to start early or late.  Both gave me out-of-sync errors on my monitor.

Any advice?

max.bra

Member

From: Bologna - Italy

Registered: 2008-06-02

Posts: 93

Re: load-modules.sh and other log stuff that i'm worried about

dunno why but, to me, this happens when i blacklist modules in MODULES rc.conf section
if you blacklist stuffs in modprobe.d/<whatyouwant> and add it to mkinitcpio.conf problem disappear
[edit] anyway, it's harmless for me. things are done correctly in all cases
don't have had time to investigate init scripts

sorry but no advice for X problem

Last edited by max.bra (2010-02-19 09:35:56)