Hi, Dererk > Having that explained, I'm not really keen to the idea of implementing > dkms on something I might not be able to test. I still have the > hardware, but I lack any possible telephone jack (for real!) where to > test it from.
You don't need to have a telephone jack to test the code. The connection itself is managed by another package -- martian-modem -- a daemon that works with wvdial, kppp and so on. I'm testing the code in a qemu (virtual) machine, with no modem. The idea is: get the tarball -> compile it with dkms -> have the module When we unpack a tarball, we usually have three files: $ ls $ README lib src I tried to create a fourth file -- dkms.conf -- following the instructions from this site: https://help.ubuntu.com/community/DKMS This is the file dkms.conf I wrote: MAKE="make -C src/ KERNELDIR=/lib/modules/${kernelver}/build" CLEAN="make -C src/ clean" BUILT_MODULE_NAME=martian_dev BUILT_MODULE_LOCATION=src/ PACKAGE_NAME=martian-modem-modules PACKAGE_VERSION=20080625-2 REMAKE_INITRD=yes I have installed the package dkms previously (as a "dependency") and I don't know what went wrong. Can you help me and the other users of that old piece of hardware? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
