Hi there,
I feel that posting about such obscure hardware is something of a forlorn hope, but all comments gratefully received.
I'm trying to install a Conexant PCI ADSL modem on a Gentoo box using the drivers at <http://patrick.spacesurfer.com/linux_conexant_pci_adsl.html>.
The modem works perfectly using the 6.1.2.007-PIM-2.6-1.1 version of the driver against the Gentoo sources 2.6.9-r13 kernel (which also seem to include suitable ATM libraries) and ppp-2.4.3-r1 with the atm USE flag set. A script is provided to load the firmware into the modem, and an audible "click" occurs when this is run; the connection status can be viewed using `cat /proc/net/atm/CnxAdsl:0` and ppp subsequently seems to work - I get allocated an IP address & can ping the Intarweb & stuff.
A week or three ago a new version of this driver was released to accommodate API changes in kernels later than 2.6.10 (see <http://patrick.spacesurfer.com/ linux_conexant_pci_adsl_history.html#2.6>), and it's this one I seem to be having problems with. The author reports no problems from anyone else, but I get the same thing using Gentoo sources 2.6.10-r6, 2.6.11-r4 & 2.6.11-r5 and vanilla sources 2.6.11.4 on my Gentoo system:
# depmod -a CnxADSL # modprobe -iv CnxADSL insmod /lib/modules/2.6.11-gentoo-r5/extra/CnxADSL.ko # /etc/Conexant/cnxadslload /etc/Conexant/ bad ioctl 400c2502, Status=c00000b5 Last record not found - load terminating download ARM micro code (downLoadMicroCode) failed, NTStatus=c0000001
`dmesg` shows these entries:
CnxADSL: module license 'unspecified' taints kernel.
CnxADSL: CnxtDsl_init Starting
CnxADSL: calBusCtlP46RegisterInterrupt
CnxADSL: ARMALIoctl TIG_LOAD_START Prepare device for download command=1074537729
CnxADSL: CmgmtProcIOCTL ARM Load command failed, command=1074537730, Status=0xc00000b5
I have no idea what any of this means.
I'm sure that my newer kernels are built with all the right options and each time I have rebuilt the CnxADSL module using `make clean` with the `/usr/src/linux` symlink pointing to the right place.
Since the newer driver is required because of an API change in the kernel I have tried emerging linux-headers-2.6.11, and subsequently remerging glibc, binutils & hotplug, all to no avail.
I'm feeling all pretty stumped on this, so all suggestions gratefully received - I've stopped short of `emerge -e world` because I'm too clueless to pin the masked linux-headers-2.6.11 against my otherwise stable-x86 system. My best idea right now is to recompile the firmware loader with debug enabled & to learn how to use gdb - I haven't used that before, so any if anyone can suggest a numpties guide for building & debugging kernel modules, then that would be great.
Cheers,
Stroller.
-- [email protected] mailing list
