modprobe log entries
Does anyone know how to have the modprobe in hamm display more descriptive log messages when it can't load a module? I've been getting messages in my log like: May 14 13:27:41 cush modprobe: can't locate module and I've been trying to track them down, (they appear whenever netscape is started) but it would really help if I knew what module it is that modprobe can't locate (as a test, doing 'insmod IMnothere' gives the identical log entry - no clue of what module was asked for). I seem to remember that modutils from bo would actually tell you in the logs what was being looked for. (Can someone running bo confirm this for me? That is, that the unfound module is mentioned in the logs, not just as output of insmod.) I'm running hamm, modutils version 2.1.85-10. And just to head off some of the 'try this and see if it works' replies, yes I do have alias net-pf-3 off alias net-pf-4 off alias net-pf-5 off in my /etc/conf.modules. Hmmm... this may be a bug against modutils, as I'm almost certain that bo gave you a clue in the logs. -- Daniel Martin, who doesn't really have a good sig yet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modprobe log entries
Yes /var/log/daemon.log records unfound modules on my bo system (2.0.30), May 8 14:10:00 raemac modprobe: can't locate module binfmt-0 May 8 14:10:00 raemac modprobe: can't locate module binfmt-0 I only see this after a reboot. Does anyone know the purpose of binfmt-0? John On Thu, 14 May 1998, Daniel Martin at cush wrote: Does anyone know how to have the modprobe in hamm display more descriptive log messages when it can't load a module? I've been getting messages in my log like: May 14 13:27:41 cush modprobe: can't locate module and I've been trying to track them down, (they appear whenever netscape is started) but it would really help if I knew what module it is that modprobe can't locate (as a test, doing 'insmod IMnothere' gives the identical log entry - no clue of what module was asked for). I seem to remember that modutils from bo would actually tell you in the logs what was being looked for. (Can someone running bo confirm this for me? That is, that the unfound module is mentioned in the logs, not just as output of insmod.) I'm running hamm, modutils version 2.1.85-10. And just to head off some of the 'try this and see if it works' replies, yes I do have alias net-pf-3 off alias net-pf-4 off alias net-pf-5 off in my /etc/conf.modules. Hmmm... this may be a bug against modutils, as I'm almost certain that bo gave you a clue in the logs. -- Daniel Martin, who doesn't really have a good sig yet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modprobe log entries
Daniel Martin at cush [EMAIL PROTECTED] writes: Does anyone know how to have the modprobe in hamm display more descriptive log messages when it can't load a module? I've been getting messages in my log like: May 14 13:27:41 cush modprobe: can't locate module and I've been trying to track them down, (they appear whenever netscape is started) but it would really help if I knew what module it is that modprobe can't locate Well, I don't know what I thought I was doing before, because modprobe appears to still give full module information when it can't find a module; it's just that in this case the module being asked for is the empty string (); kerneld is calling modprobe with something equivalent to: /sbin/modprobe -k -s '' So maybe this is a bug against kerneld, as I can't imagine a normal situation that would cause it to ask for an empty module. And I have no idea what module binfmt-0 might be; it doesn't appear as one of the aliases on my machine's modprobe -c. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
modprobe log entries
Does anyone know how to have modprobe display more descriptive log messages when it can't load a module? I've been getting messages in my log like: Apr 22 16:38:52 cush modprobe: can't locate module and I've been trying to track them down, (they appear whenever netscape is started) but it would really help if I knew what module it is that modprobe can't locate (as a test, doing 'insmod IMnothere' gives the identical log entry - no clue of what module was asked for). I seem to remember that modutils from bo would actually tell you in the logs what was being looked for. (Can someone running bo confirm this for me? That is, that the unfound module is mentioned in the logs, not just as output of insmod.) I'm running hamm, modutils version 2.1.85-10. And just to head off some of the 'try this and see if it works' replies, yes I do have alias net-pf-3 off alias net-pf-4 off alias net-pf-5 off in my /etc/conf.modules. Hmmm... this may be a bug against modutils, as I'm almost certain that bo gave you a clue in the logs. -- Daniel Martin, who doesn't really have a good sig yet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
