I just upgraded to kernel 2.2.5 and the baycom driver does not work.
The culprit seems to be in hdlcdrv. The setup works fine in 2.1.127.
The baycom.txt file is dated 7 Jun 1998 and does not mention the 2.2.x
kernels.
Bill
kg6ol
My setup:
kernel: 2.2.5
pppd: 2.3.7
modutils: 2.1.121
gcc: 2.7.2.3
depmod -a returns:
/lib/modules/2.2.5/net/mkiss.o: unresolved symbol(s)
/lib/modules/2.2.5/net/hdlcdrv.o: unresolved symbol(s)
insmod baycom_ser_fdx returns:
/lib/modules/2.2.5/net/baycom_ser_fdx.o: unresolved symbol hdlcdrv_unregister_hdlcdrv
/lib/modules/2.2.5/net/baycom_ser_fdx.o: unresolved symbol hdlcdrv_transmitter
/lib/modules/2.2.5/net/baycom_ser_fdx.o: unresolved symbol hdlcdrv_arbitrate
/lib/modules/2.2.5/net/baycom_ser_fdx.o: unresolved symbol hdlcdrv_register_hdlcdrv
/lib/modules/2.2.5/net/baycom_ser_fdx.o: unresolved symbol hdlcdrv_receiver
insmod hdlcdrv returns:
/lib/modules/2.2.5/net/hdlcdrv.o: unresolved symbol ax25_encapsulate
/lib/modules/2.2.5/net/hdlcdrv.o: unresolved symbol ax25_rebuild_header
modprobe baycom_ser_fdx returns:
/lib/modules/2.2.5/net/hdlcdrv.o: unresolved symbol ax25_encapsulate
/lib/modules/2.2.5/net/hdlcdrv.o: unresolved symbol ax25_rebuild_header
hdlcdrv: No such file or directory
--
[EMAIL PROTECTED] -- Public Access User -- Not affiliated with Teleport
[EMAIL PROTECTED] -- Public Access User -- Not affiliated with Pacifier
finger -l [EMAIL PROTECTED] for public key
