Progress, Got the compile to work per below, using the dgcmodem tar.gz . There was one fix of the type ==== below needed in modules/mod_dgcusbdcp.c modules/osdcp.c === 1. static spinlock_t foobar = SPIN_LOCK_UNLOCKED; needs to be replaced bye DEFINE_SPINLOCK -static spinlock_t drm_mem_lock = SPIN_LOCK_UNLOCKED; +static DEFINE_SPINLOCK(drm_mem_lock); === A Debian installer package was made (read the INSTALL): $ make debdist which did install per below. The module loads without crashing my system: :~/Desktop/dgcmodem-1.13$ sudo modprobe dgcusbdcp WARNING: All config files need .conf: /etc/modprobe.d/dgc, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/dgc.conflicts, it will be ignored in a future release. ~/Desktop/dgcmodem-1.13$ lsmod | grep dgc dgcusbdcp 18348 0 But lacking the modem hardware, I can't test further. With respect to the above WARNING, just Once fix with: $ sudo mv /etc/modprobe.d/dgc /etc/modprobe.d/dgc.conf I'll send you the deb package separately. MarvS /dgcmodem-1.13/modules$ make (cd /lib/modules/3.2.0-40-lowlatency/build && make "CNXT_KERNELSRC=/lib/modules/3.2.0-40-lowlatency/build" "M=/home/marv/Desktop/dgcmodem-1.13/modules" "CC=gcc" modules) make[1]: Entering directory `/usr/src/linux-headers-3.2.0-40-lowlatency' CC [M] /home/marv/Desktop/dgcmodem-1.13/modules/mod_dgcusbdcp.o /home/marv/Desktop/dgcmodem-1.13/modules/mod_dgcusbdcp.c: In function ‘dgcUsbWrite’: /home/marv/Desktop/dgcmodem-1.13/modules/mod_dgcusbdcp.c:173:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘size_t’ [-Wformat] CC [M] /home/marv/Desktop/dgcmodem-1.13/modules/osdcp.o LD [M] /home/marv/Desktop/dgcmodem-1.13/modules/dgcusbdcp.o Building modules, stage 2. MODPOST 1 modules CC /home/marv/Desktop/dgcmodem-1.13/modules/dgcusbdcp.mod.o LD [M] /home/marv/Desktop/dgcmodem-1.13/modules/dgcusbdcp.ko make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-40-lowlatency' /dgcmodem-1.13/modules$ ls -l *.ko -rw-rw-r-- 1 marv marv 30659 May 14 16:26 dgcusbdcp.ko ---------- :~/Desktop/dgcmodem-1.13$ sudo dpkg -i packages/DEBS/amd64/*.deb (Reading database ... 252736 files and directories currently installed.) Unpacking dgcmodem (from .../amd64/dgcmodem_1.13_amd64.deb) ... (Noting disappearance of dgcmodem:i386, which has been completely replaced.) Setting up dgcmodem (1.13) ... Conexant DGC USB modem driver, version 1.13 If you need assistance or more information, please go to: http://www.linuxant.com/ When reporting a problem for the first time, please send us the file generated by "dgcconfig --dumpdiag". No pre-built modules for: Ubuntu-12.04.2 linux-3.2.0-40-lowlatency x86_64-SMP Trying to automatically build the driver modules... (this requires a C compiler and proper kernel sources to be installed) Building modules for kernel 3.2.0-40-lowlatency, using source directory /lib/modules/3.2.0-40-lowlatency/build. Please wait... done. ================= On Tue, May 14, 2013 at 12:45 PM, Olemis Lang <olemis@xxxxxxxxx> wrote: > On 5/14/13, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: >> Olemis, >> >> The generic problem is that commercial support for modem drivers under >> Linux has been non-existent for a few years. Nethertheless, a few of >> us List members are still attempting to provide upgrades/support. >> But this becomes increasing difficult to impossible as the Linux code >> itself rapidly evolves. > > Yes . I'm aware of this difficulties and thank you all for keeping > this kind of support alive . > :) > > [...] >> >> For your particular problem with the Linxant dgc package, I have just >> taken a look at the dgcmodem-1.13.tar.gz which is the one to be used >> for x86_64/amd64 systems. Trying the simple compile of the drivers, >> there was the warning and then fatal Spin_Lock error shown below. >> Likely I can correct the Spin_Lock problem, as we have encountered it >> before. As I am traveling however, it may take a few days before I >> further respond. >> > > Thanks . Looking forward to know if compilation succeeds after doing so . > >> Even when the compile is successful, there is no gaurantee that the >> driver will serve under a current kernel, for your particular USB >> hardware. The problem is that the pre-compiled.o section of the code >> may be too old to serve with current kernels >> > > Mmmm ... good to know . > > -- > Regards, > > Olemis. > > Apache™ Bloodhound contributor > http://issues.apache.org/bloodhound > > Blog ES: http://simelo-es.blogspot.com/ > Blog EN: http://simelo-en.blogspot.com/ > > Featured article:
