net-pf-10, 2.6.1
--text follows this line--
* On Sat Jan 31 2004 - 21:36:58 EST, Steve Youngs wrote:
|> > |> > install net-pf-10 /bin/true |> |> This _is_ what you want in your modprobe.conf file. Or possibly |> `install net-pf-10-* /bin/true', but I'm pretty sure that Rusty has |> added some backward compatibility code so that either _should_ work. |> |> The other thing that you need to do once you have updated |> modprobe.conf is to run `depmod' to regenerate the dependency |> files.
I've tried the variations I can think of---putting the line:
install net-pf-10 /bin/true
in /lib/modules/modprobe.conf via update-modules, or directly by hand-editing. Then depmod; then reboot. Also:
install net-pf-10-* /bin/true
install net-pf-* /bin/true
All variations still lead to:
Jan 31 23:08:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256 Jan 31 23:23:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
on each run of exim from cron (Debian exim has ipv6 support compiled in). If I run modprobe manually, I get:
ohlone# modprobe net-pf-10
FATAL: Module ipv6 not found.
indicating that modprobe knows about the alias, but is not running /bin/true when requested to load the module.
However: if I manually edit /etc/modprobe.d/aliases (which you're not supposed to do), so as to comment out:
# alias net-pf-10 ipv6
and then add:
install ipv6 /bin/true
(update-modules; depmod; reboot), `modprobe ipv6' from the command-line completes silently and without error (but without loading the module, of course, since it doesn't exist). Which I think is the expected behaviour.
But even at that point, in the logs we still get:
Feb 1 00:53:01 ohlone /USR/SBIN/CRON[280]: (mail) CMD ( if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi) Feb 1 00:53:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
(because exim is trying to load the module under the name net-pf-10??)
Here are some pointers to what seems to be the same or a similar problem:
http://www.mail-archive.com/[email protected]/msg66557.html
http://www.spinics.net/lists/kernel/msg236360.html
http://lkml.org/lkml/2004/1/13/72
http://forum.hardware.fr/hardwarefr/OSAlternatifs/citer-24424-387523-58.htm
Oh well, it is a very small problem (all it does is clutter the log-files). Thanks very much to all who helped,
Jim
Quoted 9 lines · Jim McCloskey
I've tried the variations I can think of---putting the line:
install net-pf-10
/bin/truein
/lib/modules/modprobe.confvia update-modules, or directly by hand-editing. Then depmod; then reboot. Also:install net-pf-10-*
/bin/true
install net-pf-*/bin/true
AFAIK, this was fixed in 3.0-pre6 version of module-init-tools:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107449592106965&w=2
Why don't you just upgrade it and forget those ugly workarounds?
I don't know which distro you are running, 3.0-pre9-1 got into debian sid today or yesterday.
Cheers
Signature · 1 line
Kiko
* Kiko Piris ([email protected]) wrote:
|> AFAIK, this was fixed in 3.0-pre6 version of module-init-tools: |> |> http://marc.theaimsgroup.com/?l=linux-kernel&m=107449592106965&w=2 |> |> Why don't you just upgrade it and forget those ugly workarounds? |> |> I don't know which distro you are running, 3.0-pre9-1 got into debian |> sid today or yesterday.
Thank you indeed for this. I upgraded to the version in Debian unstable (3.0-pre9-1, as you say) and all works as expected.
I'm grateful to all who helped and especially for your patience.
Jim
Quoted 5 lines · Jim McCloskey
I've tried the variations I can think of---putting the line:
install net-pf-10
/bin/truein
/lib/modules/modprobe.confvia update-modules, or directly by hand-editing.
The first thing to note is that the kernel tries to insert modules for non-existent network protocols by calling modprobe with net-pf-N where N is the protocol number. N=10 for IPv6.
Quoted 5 lines
ohlone# modprobe net-pf-10
FATAL: Module ipv6 not found.indicating that modprobe knows about the alias, but is not running
/bin/truewhen requested to load the module.
... because the module is now known as ipv6 not net-pf-10.
Quoted 8 lines
However: if I manually edit
/etc/modprobe.d/aliases(which you're not supposed to do), so as to comment out:# alias net-pf-10 ipv6and then add:
install ipv6
/bin/true
You've made two changes at the same time - no wonder you're getting confused. In the first change, you've told it to no longer alias net-pf-10 to ipv6, so it won't go anywhere near "ipv6" anymore. In the second change, you've told it to use /bin/true to insert the ipv6 module - which it doesn't find because its still looking for "net-pf-10"
Golden rule: only make one change at a time.
Here's the practical examples showing what's going on:
[root@cps /root]# cat /etc/modprobe.conf
[root@cps /root]# modprobe net-pf-10
FATAL: Module net_pf_10 not found.
[root@cps /root]#
---
[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
[root@cps /root]# modprobe net-pf-10
FATAL: Module ipv6 not found.
[root@cps /root]#
---
[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
install net-pf-10 /bin/true
[root@cps /root]# modprobe net-pf-10
FATAL: Module ipv6 not found.
[root@cps /root]#
---
[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
install ipv6 /bin/true
[root@cps /root]# modprobe net-pf-10
[root@cps /root]#
Signature · 4 lines
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core