Example Errors: Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp1 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp2 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp3 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp4 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp5 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp6 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp7 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp8 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp9 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp10 Mar 10 22:51:38 starscream modprobe: modprobe: Can't locate module /dev/usb/lp11 This occurs constantly when X is running, I have already tried updating to the latest devfs 1.3.25-r3 and also recompiling my kernel several times, with several different configurations. Reproducible: Always Steps to Reproduce: I don't know where the problem lies for me to reproduce... It is constant but, on every boot. From what I can tell, this is a problem with devfs... some people were having trouble with this and an emerge of the latest devfs solved the problem... others are in the same position as myself... All my devices still work ok, so I am unsure how deep this problem goes.
I had this too for the longest time, I tryied several different kernels and emerged devfsd several times but nothing really seemed to work and then after deleting my /lib/modules/* and kernel and starting everything from scratch and after several reboots the problem went away but I cant be certain which step I took is the one that resolved the issue.. but people with this problem have reproduced my steps and the problem has not been resolved for them ... This link explains the issue and what we have tried to do so far to resolve it: http://forums.gentoo.org/viewtopic.php?t=40596&start=0&postdays=0&postorder=asc&highlight=&sid=346b1676af12947d9ee587069ebb187a
I had this too with the new baselayout, then it went away and then came back almost randomly.
Do you have module-init-tools installed ?
> Do you have module-init-tools installed ? yes, tried remerging.. no change
Yes, but from your logs it seems you are using a 2.4 kernel, right ? If so, please try to unmerge module-init-tools, and remerge modutils, and let me know if that fixed it.
And ?
Did as you said, still no luck... Kernel is 2.4 but also tried 2.5, same problem... Sorry for slowness of reply... back to uni :(
try update to the latest modutils-2.4.25
My system is bleeding edge... already updated to 2.4.25 and tried remerging
I have this problem now also, using the latest bleeding edge ~x86 packages. It happens with all non-root logins. I am going to try a few suggestions and see what packages I can change to remove the problem. Some people have mentioned baselayout, others modutils, others gawk (?!), etc.
Ok, I had a look through all the files, the differences between running the latest stable and unstable ~x86 is only in baselayout (stable 1.8.5.9 vs unstable 1.8.6.6). I did the whole re-emerge thing, that didn't make any difference. Then I had a play around in /etc/devfsd.conf and spotted this: # Uncomment this to let PAM manage devfs REGISTER .* CFUNCTION /lib/security/pam_console_apply_devfsd.so pam_console_apply_single $devpath I uncommented that line, rebooted, and voila! - no more modprobe errors for non-root logins messages. It appears to be a problem with the devfsd package settings in devfsd.conf, as I noticed other lines in that file in regards to /dev/cdrw for the cdrw group, were commented out also. Note: when I logout now, I get a message "gnrmgram" something about the CD Writer. I assume that's related to the cdrw lines commented out in devfsd.conf also ? (I didn't check).
I did as you said... still have the problem... by any chance did you change any other settings? Also, there has been reports of it just "dissapearing" as shown in the forum thread listed... could this be why? Cheers
It could also be related to hotplug .... please uninstall/disable it if you use it.
Neo, I did a reinstall of my Gentoo on my box, because I realised during the install process, I had forgotten to do the 'mount -t proc proc /mnt/gentoo/proc' step correctly (I missed it, exited out of my chrooted environment, did the mount, then did the chroot again). During the reinstall, I made sure I did the mount of /proc correctly, and at the end of it, I didn't have the problems with PAM. I didn't even have to edit the file I mentioned. So it is a very strange problem.
I could have possibly missed this step as well, is it possible to solve it without a complete reinstall, I have my system just running the way I want it, and I don't want to have to start again :)
"gnrmgram"-errors (getgrnam, isn't it?) can be cleared up by changing the last field on the fifth to last line (line 76) on /etc/security/console.perms from "root.cdwriter" to "root.cdrw". This is because Gentoo's group file has a cdrw group rather than a cdwriter group.
Welp, basically I believe these warnings/errors are caused by the interaction between PAM and devfs, specifically through the pam_console suite of PAM utilities and modules. These seem to include the module pam_console.so, the pam_console_apply utility, and the pam_console_apply_devfsd.so module. When I comment the line session optional /lib/security/pam_console.so out of /etc/pam.d/login, my warnings go away; but so does the functionality of this module, which is to give you access to devices in /dev that you would not normally have (e.g. if you have some IDE CD/DVD devices, watch the permissions on /dev/ide/host0/bus?/target?/lun0 before and after you log out on a non-root user). What I believe is happening is that pam_console is just trying to work on devices that aren't there . . . resulting in the "modprobe: Can't locate module..." messages. I consider these to be warnings -- not errors. My solution is to comment out any devices I don't use in /etc/security/console.perms (file used by pam_console_apply to determine which devices to modify perms on). Alternate solutions could include, as mentioned above, commenting the pam_console module out of /etc/pam.d/login or setting devfsd.conf to ignore messages generated regarding this problem (since I do not believe there is any harm being done to the system . . . it's just a warning/annoyance). I don't know the syntax for the latter solution off the top of my head.
Oh, you could also just disable devfsd's module auto-loading functionality entirely by commenting out the line: LOOKUP .* MODLOAD in /etc/devfsd.conf
I'm getting the same modprobe errors on the console after upgrading to baselayout 1.8.6.8-r1 and it's driving me nuts. Everything still works ok, but it is horrible to look at. So I did some testing and here is what I found. Not sure if it will help or not, but can't hurt I guess. First, thing I stumbled upon is that when I removed nfs from the default runlevel I no longer saw the modprobe messages on the console. This was after taking hotplug out of the default runlevel mind you so taking out hotplug didn't help anything. So I took a look at the /etc/init.d/nfs script and started playing with it. One thing I'm not quite sure of in this script is the after quota line in the depend section of the script. I couldn't find anything else that provided quota and nothing regarding quota showed up in /var/lib/init.d/deptree. So I noticed that sshd was one of my last services to run. So what I did was appended sshd to the end of the after line in the depend section of the /etc/init.d/nfs script to force it to start after sshd. I rebooted and didn't see the error messages at all and nfs up started up without a problem. So I'm not sure if this maybe something to do with depscan.sh or what but I thought i would share that info.
I have got the same problem... So, I started the computer whithout hotplug... The problem was stil there... So, I re-emerged hotplug, and now, I get more errors... (/dev/usblp..., /dev/ttyS..., /dev/parallel, /dev/par...)... I have this problem since last full update (2003-06-22)... The main package that was updated is baselayout (1.8.6.8-r1)... The packages that were updated at the same moment are: 16:27 debianutils-1.16.7-r2 16:29 gawk-3.1.2-r3 16:30 baselayout-1.8.6.8-r1 16:32 texinfo-4.5 16:33 miscfiles-1.3-r2 16:37 groff-1.18.1-r2 16:37 man-1.5l-r6 16:39 grep-2.5.1-r1 16:46 PDL-2.4.0 16:48 grub-0.93.20030118 16:49 procps-3.1.9 16:50 Net-SSLeay-1.22 16:50 lsof-4.67 16:51 psmisc-21.2-r2 16:54 pam-login-3.11 16:58 util-linux-2.11z-r4 16:58 quota-3.06-r1 17:01 fileutils-4.1.11-r1 17:02 net-tools-1.60-r7 17:04 star-1.5_alpha14 17:05 iproute-20010824-r3 17:06 PodParser-1.22 17:06 Net-DNS-0.37 17:06 Time-Local-1.05 17:07 Mail-SpamAssassin-2.55-r1 18:14 epm-0.8.4
I also have had this same problem. Attempted to comment out: LOOKUP .* MODLOAD in /etc/devfsd.conf, but this only removed some errors (the remaining ones seemed to do with sound devices, although my sound still works) and also stopped my floppy from being mountable (no /dev/fd0)
yea, I get lots of modprobe: Can't locate module /dev/snd errors as well when utilizing my sound card. I don't really know what causes this.
dont know what cause this, but the solution that worked for me was to emerge -u --deep devfsd emerge -u devfsd still having modprobe errors related to audio devices after the boot process thought.
Please reopen this bug if the problem persists.
