login as user causes dozens of modprobes

fatblueduck · 04-10-2005, 02:26 PM

I'm using kernel 2.4.29

Whenever I login as my user, half a dozen faild modprobes are performed.

Quote:

pond login: duck
Password:
login(pam_unix)[1304]: session opened for user duck by (uid=0)
modprobe: Can't locate module ttyS* which is needed for /dev/ttyS*
modprobe: Can't locate module audio* which is needed for /dev/audio*
modprobe: Can't locate module sequencer* which is needed for /dev/sequencer*
modprobe: Can't locate module admm* which is needed for /dev/admm*
modprobe: Can't locate module adsp* which is needed for /dev/adsp*
modprobe: Can't locate module adsp* which is needed for /dev/adsp*
modprobe: Can't locate module aload* which is needed for /dev/aload*
modprobe: Can't locate module amidi* which is needed for /dev/amidi*
modprobe: Can't locate module amidi* which is needed for /dev/amidi*
modprobe: Can't locate module dmfm* which is needed for /dev/dmfm*
modprobe: Can't locate module dmmidi* which is needed for /dev/dmmidi*
modprobe: Can't locate module dmmidi* which is needed for /dev/dmmidi*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate cdwriter* which is needed for /dev/cdwriter*
modprobe: Can't locate module scanner* which is needed for /dev/usb/scanner*
modprobe: Can't locate module dc2xx* which is needed for /dev/usb/dc2xx*
modprobe: Can't locate module mdc800* which is needed for /dev/usb/mdc800*
modprobe: Can't locate module fb[0-9]* which is needed for /dev/fb[0-9]*
modprobe: Can't locate module js[0-9]* which is needed for /dev/js[0-9]*
modprobe: Can't locate module video* which is needed for /dev/video*
modprobe: Can't locate module radio* which is needed for /dev/radio*
modprobe: Can't locate module winradio* which is needed for /dev/winradio*
modprobe: Can't locate module vtx* which is needed for /dev/vtx*
modprobe: Can't locate module vbi* which is needed for /dev/vbi*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module scd* which is needed for /dev/scd*
modprobe: Can't locate module sg* which is needed for /dev/sg*
modprobe: Can't locate module pcd* which is needed for /dev/pcd*
modprobe: Can't locate module pg* which is needed for /dev/pg*
modprobe: Can't locate module * which is needed for /dev/scsi/*
modprobe: Can't locate module dabusb* which is needed for /dev/usb/dabusb*
modprobe: Can't locate module mdc800* which is needed for /dev/usb/mdc800*
modprobe: Can't locate module ttyUSB* which is needed for /dev/ttyUSB*
Last login: Sat Apr 9 16:56:13 on vc/1

I've never seen this happen. Why are these modprobes happening? When they do happen, why are they not working? For example, I have the usb scanner device compiled INTO the kernel.

There has got to be a simple explanation for this, because I have just performed this install over the last day or two. I've double checked everything and I can't seem to figure out the problem.

***edit
almost forgot... none of the modprobing happens when I login as root

sludink · 04-10-2005, 03:05 PM

-Check your /etc/modules.autoload.d/kernel-2.4 file. Only modules you need should be listed. If some module-name is in here, the init-process try to load it, also if you compiled it in-kernel.
-Check /etc/login and see if it contains the word modprobe
-Check your ~/.login and see if it contains the word modprobe
-Look in your system logs,
#cat /var/log/debug
#cat /var/log/kernel
(Don't know where it might be)
You're login probably tries to load some modules as normal user, and it can't locate the modules because you don't have permissions to search in the module directories. But you shouldn't load modules as normal user anyway.
So I suspect it's in ~/.login, but I'm not sure.
Hopefully the log files turn op some helpful messages.

fatblueduck · 04-10-2005, 03:22 PM

- /etc/modules.autoload.d/kernel-2.4 only has two or three modules loading. One for my sound and the others for my ethernet
- I have two /etc/login folders (login.defs and login.access) and neither of them contain the word 'modprobe'
- I don't find a ~/.login folder or directory. I've looked for it as user and as root in the /home/duck directory, but I can't find it.
- system logs. There are four logs in /var/log, 1) emerge.log 2)lastlog 3)news 4)wtmp; none of them has readable information in them

sludink · 04-10-2005, 04:10 PM

You don't have a system logger installed by the way.

Maybe that's also the reason of the modprobes, but install a system-logger first (gives you a much better looking login procedure also)

Try (as root):

#emerge vixie-cron
#rc-update add vixie-cron default

And log in again.
If you got the modprobe-problems again, look in the log files I mentioned,they will be existing then!

(Oh sorry, I meand /etc/profile instead of /etc/login, but you won't find it there I guess)