Edwin, It could be a detection problem? kernel 3.0.X is newer than 2.6.20, 2.6.39.X, etc. Maybe martian code is not 3.X kernel friendly, I thought that there could be error messages about some things(functions) that have changed with the new kernel releases, but the make command returns something different. I will try to check up on that and cc. to Marv in case he has some suggestions for you to try out. Regards, Antonio On Sun, Nov 20, 2011 at 10:51 PM, bartman2589 <bartman2589@xxxxxxx> wrote: > Antonio, thanks for taking the time to try to help me with this, when I try > running just 'make' from within the folder I extracted the source to I get > the following message: > > "The martian_dev.ko driver and the complementary helper martian_helper are > for use with kernels after 2.6.20. Use the martian-20080407.tar.gz for > earlier kernels." > > It's as if it isn't recognizing that my kernel is newer than 2.6.20, I also > noticed in the ModemData.txt file that it doesn't seem to notice that the > 'linux-headers-3.0.0-12-generic' package is in fact already installed > (though I think this is more of a problem with scanmodem itself). > > Thanks, > Edwin > > On 11/20/2011 12:35 PM, Antonio Olivares wrote: >> >> Edwin, >> >> On Sun, Nov 20, 2011 at 11:23 AM, bartman2589<bartman2589@xxxxxxx> wrote: >>> >>> Hi to everyone who ends up receiving this, I'm having trouble >>> compiling/installing the 'martian-full-20100123' drivers obtained from >>> http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ >>> under >>> Kubuntu 11.10 32 bit (if indeed that's the one I'm supposed to be using), >>> I've attached the output from scanmodem (the ModemData.txt file and the >>> scanout file), and here is the relevant output from the command 'sudo >>> lspci >>> -v': >>> >>> 03:01.0 Communication controller: Agere Systems 56k WinModem (rev 01) >>> Subsystem: Zoom Telephonics Inc Device 9300 >>> Flags: bus master, medium devsel, latency 0, IRQ 9 >>> Memory at feaffc00 (32-bit, non-prefetchable) [size=256] >>> I/O ports at bc00 [size=8] >>> I/O ports at b800 [size=256] >>> Capabilities: [f8] Power Management version 2 >>> >>> I'm hoping someone can help me get this working. I'm a bit of a Linux >>> newb >>> and certainly not a linux programmer, but when I try to run 'make all' >>> from >>> a shell prompt in the folder I extracted the source code into >>> (/home/edwin/martian-full-20100123), I get the following error: >>> >>> "make: *** No rule to make target `all'. Stop.'" >> >> Did you try just make? >> >> $ make >> >> if it succeeds then, run >> $ sudo make install >> afterwards. If it does not please reply to this message and post the >> error messages. >> >> You do have the correct driver as scanModem recommends: >> >> For candidate card in slot 03:01.0, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 03:01.0 11c1:0442 141b:9300 Communication controller: >> Agere Systems >> 56k WinModem >> >> Modem interrupt assignment and sharing: >> 19: 0 IO-APIC-fasteoi uhci_hcd:usb3 >> --- Bootup diagnostics for card in PCI slot 03:01.0 ---- >> [ 0.177339] pci 0000:03:01.0: [11c1:0442] type 0 class 0x000780 >> [ 0.177356] pci 0000:03:01.0: reg 10: [mem 0xfeaffc00-0xfeaffcff] >> [ 0.177366] pci 0000:03:01.0: reg 14: [io 0xbc00-0xbc07] >> [ 0.177376] pci 0000:03:01.0: reg 18: [io 0xb800-0xb8ff] >> [ 0.177421] pci 0000:03:01.0: supports D2 >> [ 0.177424] pci 0000:03:01.0: PME# supported from D2 D3hot D3cold >> [ 0.177428] pci 0000:03:01.0: PME# disabled >> >> The PCI slot 03:01.0 of the modem card may be disabled early in >> a bootup process, but then enabled later. If modem drivers load >> but the modem is not responsive, read DOCs/Bootup.txt about possible >> fixes. >> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> if help is needed. >> >> If you are able to install the driver but the modem is unresponsive >> please do as instructed above. >> >> Regards, >> >> Antonio >>> >>> I have tried searching on the Internet to find references on how to >>> correct >>> this problem but I can't seem to find anything relevant that I can make >>> sense of. So I'm turning to the Linmodems community in the hopes that >>> somebody can help me figure this out. Incidentally I'm also trying to >>> install a similar modem into another computer, but I'll wait to see what >>> I >>> learn here before I attempt to proceed further with the other system (who >>> knows I may not need any help with that one once I get this one figured >>> out >>> :) ). >>> >>> Thanks for any help anyone can provide, >>> Edwin Barton >>> >>> >>> >>> >>> > >
