Ryan, Your modem is supported by martian-20080625.tar.gz code^(2). However as scanModem detects you have a modem interrupt assignment^(3) and also some additional packages are needed^(1): 1) For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default. Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions. In not included on your install CD, search for them at http://packages.ubuntu.com 2) The modem has a Lucent/Agere/LSI Mars or Apollo DSP (digital signal processing) chipset. Support packages for 2.6.n kernels are at: http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ Always use the most update for kernels after 2.6.20, currently martian-full-20080625.tar.gz For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz. See DOCs/AgereDSP.txt for Details. 3) Modem interrupt assignment and sharing: =================================== The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not functional!! The CPU cannot control the modem until this situation is corrected!! Possible corrections are: 1) Within the boot up BIOS, change from a Windows to a non-PNP/Other Operating System type. Instructions for accessing BIOS are at: http://linmodems.technion.ac.il/resources.html within: Additional Resourcces. 2a) Add an option "pci=routeirq" to the kernel boot up line. Here is an example paragraph from /boot/grub/menu.lst : title Ubuntu, kernel 2.6.15-26-686 root (hd0,6) kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq initrd /boot/initrd.img-2.6.15-26-686 savedefault 2b) Same as above, but use "pollirq" instead of "pci=routeirq". 3) Within some BIOS setups, IRQ assignments can be changed. 4) On non-laptop systems, moving the modem card to another slot has helped. 5) Sometimes upgrading the kernel changes IRQ assignment. ===================================== --- Bootup diagnostics for card in PCI slot 01:0b.0 ---- [ 0.580328] pci 0000:01:0b.0: reg 10 32bit mmio: [0xe6800000-0xe68000ff] [ 0.580337] pci 0000:01:0b.0: reg 14 io port: [0xb800-0xb807] [ 0.580344] pci 0000:01:0b.0: reg 18 io port: [0xb400-0xb4ff] [ 0.580373] pci 0000:01:0b.0: supports D2 [ 0.580375] pci 0000:01:0b.0: PME# supported from D2 D3hot D3cold [ 0.580380] pci 0000:01:0b.0: PME# disabled The PCI slot 01:0b.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 something does not work as advertised, please let us know so we can see how to help. Regards, Antonio On 7/21/09, Ryan Fothergill <snowman2005@xxxxxxxxx> wrote: > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 > (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 > scanModem update of: 2009_07_17 > > The dialer utility package WVDIAL does not appear to be installed on > your System. > Please read Modem/DOCs/wvdial.txt > > There are no blacklisted modem drivers in /etc/modprobe* files > Potentially useful modem drivers now loaded are: > > > Attached USB devices are: > ID 05e3:0715 Genesys Logic, Inc. USB 2.0 microSD Reader > ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver > If a cellphone is not detected, see > http://ubuntuforums.org/archive/index.php/t-878554.html > A sample report is: > http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html > > If a USB modem or cellphone is attached and was not detected, please > provide available information in your request to discuss@xxxxxxxxxxxxx > > For candidate card in slot 01:0b.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 01:0b.0 11c1:044c 11c1:044c Communication controller: Agere Systems > LT WinModem > > Modem interrupt assignment and sharing: > =================================== > The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not functional!! > The CPU cannot control the modem until this situation is corrected!! > Possible corrections are: > 1) Within the boot up BIOS, change from a Windows to a > non-PNP/Other Operating System type. > Instructions for accessing BIOS are at: > http://linmodems.technion.ac.il/resources.html within: > Additional Resourcces. > 2a) Add an option "pci=routeirq" to the kernel boot up line. > Here is an example paragraph from /boot/grub/menu.lst : > title Ubuntu, kernel 2.6.15-26-686 > root (hd0,6) > kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq > initrd /boot/initrd.img-2.6.15-26-686 > savedefault > 2b) Same as above, but use "pollirq" instead of "pci=routeirq". > 3) Within some BIOS setups, IRQ assignments can be changed. > 4) On non-laptop systems, moving the modem card to another slot has > helped. > 5) Sometimes upgrading the kernel changes IRQ assignment. > ===================================== > > --- Bootup diagnostics for card in PCI slot 01:0b.0 ---- > [ 0.580328] pci 0000:01:0b.0: reg 10 32bit mmio: [0xe6800000-0xe68000ff] > [ 0.580337] pci 0000:01:0b.0: reg 14 io port: [0xb800-0xb807] > [ 0.580344] pci 0000:01:0b.0: reg 18 io port: [0xb400-0xb4ff] > [ 0.580373] pci 0000:01:0b.0: supports D2 > [ 0.580375] pci 0000:01:0b.0: PME# supported from D2 D3hot D3cold > [ 0.580380] pci 0000:01:0b.0: PME# disabled > > The PCI slot 01:0b.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. > > > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > Predictive diagnostics for card in bus 01:0b.0: > Modem chipset detected on > NAME="Communication controller: Agere Systems LT WinModem " > CLASS=0780 > PCIDEV=11c1:044c > SUBSYS=11c1:044c > IRQ=255 > IDENT=Agere.DSP > > For candidate modem in: 01:0b.0 > 0780 Communication controller: Agere Systems LT WinModem > Primary device ID: 11c1:044c > Support type needed or chipset: Agere.DSP > > > > The modem has a Lucent/Agere/LSI Mars or Apollo DSP (digital signal > processing) chipset. > Support packages for 2.6.n kernels are at: > http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ > Always use the most update for kernels after 2.6.20, currently > martian-full-20080625.tar.gz > For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz. > > See DOCs/AgereDSP.txt for Details. > > At http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ > get the martian-full-20080625.tar.gz and follow Readme-NOW.html > 0x044c -- Mars 3 Perseus data/fax only:North America and Global board > 0x044c -- Mars 3.2 Mercury data fax only when no eeprom is present, > North America DAA > -------------- end Agere Systems section ------------------- > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.3.3 > and the compiler used in kernel assembly: 4.3.3 > > The patch utility is needed and is needed for compiling ALSA drivers, > and possibly others. > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.3 > linuc_headers base folder /lib/modules/2.6.28-11-generic/build > > However some compilations and executable functions may need additional > files, > in the FileNames.h (so called kernel "h"eaders) collection installed > in /usr/include/ . > For martian_modem, additional required packages are needed. The also > required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev > packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at > http://packages.ubuntu.com > or comparable Repository for other Linux distros. > When compiling ALSA drivers, the utility "patch" will also be needed. > > > > > If a driver compilation fails, with message including some lack of > some FileName.h (stdio.h for example), then > Some additional kernel-header files need installation to /usr/include. > The minimal additional packages are libc6-dev > and any of its dependents, under Ubuntu linux-libc-dev > > If an alternate ethernet connection is available, > $ apt-get update > $ apt-get -s install linux-kernel-devel > will install needed packages. > For Debian/Ubuntu related distributions, run the following command to > display the needed package list: > > Otherwise packages have to be found through http://packages.ubuntu.com > Once downloaded and transferred into a Linux partition, > they can be installed alltogether with: > $ sudo dpkg -i *.deb > > Checking settings of: /etc/ppp/options > asyncmap 0 > noauth > crtscts > lock > hide-password > modem > proxyarp > lcp-echo-interval 30 > lcp-echo-failure 4 > noipx > > In case of a message like: > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied > see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for experts should trouble > shooting be necessary. > ========================================================== > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > > Within /etc/modprobe.conf files: > /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 > /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 > /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in > order to blacklist unwanted modem drivers > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- >