Messages in this thread | | | Date | Thu, 15 Jan 2004 21:51:46 +0100 (CET) | Subject | Re: modprobe failed: digest_null | From | "Andreas Schrell" <> |
| |
i am quite sure this message comes from freeswan 2.04.
programs/pluto/kernel_netlink.c: { SADB_X_AALG_NULL, "digest_null" },
Think it could be fixed by replacing digest_null with crypto_null (or modprobing crypto_null manually before starting freeswan) but then the next problem with
kernel: request_module: failed /sbin/modprobe -- ripemd160. error = 256
from same freeswan source file...
Andreas
PS: sorry, Randy for dublette...
> On Thu, 15 Jan 2004 09:08:15 +0100 martin f krafft <madduck@madduck.net> wrote: > > | also sprach Rusty Russell <rusty@rustcorp.com.au> [2004.01.15.0022 +0100]: > | > Upgrade module-init-tools to 0.9.14 or one of the 3.0 -pres. > | > | diamond:~# modprobe -V > | module-init-tools version 3.0-pre5 > > Yes, and I'm using 0.9.14 and seeing similar messages. > > -- > ~Randy > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |