Linux-Hams archive - December 1996: Re: ax25-2.1.9a and baycom

Re: ax25-2.1.9a and baycom

Thomas Sailer (gynmdfm.wqhbg@bpsi.net)
Mon, 02 Dec 1996 10:31:42 +0100


> You see socket(2) is called with four arguments (hence the error) the third of
> which is nul. I know call.c has not been tampered with and it always calls
> socket(2) with three arguments. I can't figure out what's wrong.
It seems that you compiled ax25 as a module and it is not loaded.
For some reason or other, kerneld fails to load it at the socket
call. Try inserting it manually.

73s de Tom