Leslie, The martian drivers are certainly correct for your hardware. 0445 -- Apollo 2 Global Board data/fax only : Modem/LAN combo board Apollo behind an Intel 82559 11c1:0445 Serial controller: Agere Systems LT WinModem Re: Modem interrupt assignment and sharing: 11: 24863 XT-PIC-XT yenta, yenta, 164x, uhci_hcd:usb1, ESS Maestro, ndiswrapper, eth0 --------- There is a lot of resource sharing on IRQ 11, That may be a contributing problem. 164x represents the modem, I think You could try shutting down these competing processes, each time testing for modem access with: # wvdialconf wvtest Start by ejecting any card in the PCMCIA slots (yenta support module) Identity the dependent module set with: # lsmod | grep yenta Shutdown eth0, which must be done before any dialout to avoid DNS conflicts: # ifconfig eth0 down Remove the external USB devices and try unloading any associated drivers. Lastly stop audio, and retest modem access. MarvS On Sun, Dec 21, 2008 at 8:14 PM, Leslie Katz <lesliek@xxxxxxxxxxxxxx> wrote: > Thanks both to Antonio and Marvin for your replies. > > As to Antonio's suggestion, when I followed it, I got: > > "--> WvDial: Internet dialer .version 1.60 > --> Cannot open /dev/ttySM0: No such file or directory" > > As to Marv's request, following is my entire ModemData.txt file: > > " Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List > Server, > as HTML can contain viruses. Use as the email Subject Line: > YourName, YourCountry kernel 2.6.25.4 > With this Subject Line cogent experts will be alerted, and useful case names > left in the Archive. > YourCountry will enable Country specific guidance. Linux experts in > YourCountry > can be found through: http://www.linux.org/groups/index.html. > They will know your Country's modem code, which may be essential for dialup > service. > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet > Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org > -------------------------- System information ---------------------------- > CPU=i686, Linux version 2.6.25.4 (root@zenwalk) (gcc version 4.2.3) #1 SMP > PREEMPT Fri May 16 14:10:46 CEST 2008 > scanModem update of: 2008_11_06 > > Modem drivers blocked from loading during bootup are listed in > /etc/modprobe* file lines: > /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem > /etc/modprobe.d/blacklist:blacklist snd-intel8x0m > > Attached USB devices are: > ID 1d6b:0001 Linux Foundation 1.1 root hub > > USB modems not recognized > > For candidate card in slot 00:09.1, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:09.1 11c1:0445 8086:2204 Serial controller: Agere Systems LT > WinModem > > Modem interrupt assignment and sharing: > 11: 24863 XT-PIC-XT yenta, yenta, 164x, uhci_hcd:usb1, ESS > Maestro, ndiswrapper, eth0 > --- Bootup diagnostics for card in PCI slot 00:09.1 ---- > ACPI: PCI Interrupt 0000:00:09.1[A] -> Link [C187] -> GSI 11 (level, low) -> > IRQ 11 > ACPI: PCI interrupt for device 0000:00:09.1 disabled > ACPI: PCI Interrupt 0000:00:09.1[A] -> Link [C187] -> GSI 11 (level, low) -> > IRQ 11 > > The PCI slot 00:09.1 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 00:09.1: > Modem chipset detected on > NAME="Serial controller: Agere Systems LT WinModem" > CLASS=0700 > PCIDEV=11c1:0445 > SUBSYS=8086:2204 > IRQ=11 > IDENT=Agere.DSP > > For candidate modem in: 00:09.1 > 0700 Serial controller: Agere Systems LT WinModem > Primary device ID: 11c1:0445 > Support type needed or chipset: Agere.DSP > > > ----------------end Softmodem section -------------- > > 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. > > > Vendor 11c1 is Lucent Technologies with modem technology now under LSI Inc. > Their Linux code developer/maintainer is Soumyendu Sarkar. Support for a > chipset and its > continued maintenance is only initiated at the request of a major chipset > buyer, > or comparable sponsor. Several different modem chipset types are produced: > with varying support under Linux. > Device ID Support Name Comment > --------- ------------- ----------- ----------------------------- > 0480 serial_drivers Venus controller chipset 1673JV7 > 0440-045d martian Mars/Apollo DSP (digital signal processing) > chipsets > 0462 none 56K.V90/ADSL Wildwire > 048d none SV2P soft modem > 048(c or f) AGRSM SV2P soft modem > 0600 none soft modem, very few in the field. > 0620 AGRSM Pinball soft modem, in some HP desktop PCs > 011c11040 AGRSM hosted on High Definition Audio cards > 062(1-3) none SV92PP,Pinball soft modem, in some HP desktop > PCs > > martian - At > http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ > AGRSM - At http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > Compiling resources for a driver module pair: agrmodem.ko + agrserial.ko > Use the agrsm-HDA-20080721-ALSA15.tar.bz2 or agrsm-HDA-20080721.tar.bz2 > Read the agrsm_howto.txt. For 11c11040 chips, also the > HOWTO-Agere-11c11040-HDA.html > > 0x0445 -- Apollo 2 Global Board data/fax only : Modem/LAN combo board Apollo > behind an Intel 82559 > -------------- 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.2.3 > and the compiler used in kernel assembly: 4.2.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.2 > linuc_headers base folder /lib/modules/2.6.25.4/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 pppd properties: > -rwxr-xr-x 1 root root 366440 2006-07-01 18:27 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html > > To enable dialout without Root permission do: > $ su - root (not for Ubuntu) > chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > chmod a+x /usr/sbin/pppd > > Checking settings of: /etc/ppp/options > asyncmap 0 > crtscts > lock > modem > proxyarp > lcp-echo-interval 30 > lcp-echo-failure 4 > > 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 wlan0 > 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/blacklist:# ALSA modules to support sound modems. These > should be loaded manually > /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines --------" > > Can I please add one thing? I'm able now to get onto the Internet with the > computer via either Ethernet or wirelessly. However, that's only in Sydney. > I'd also like to travel with the computer to places in the country where > dial-up is my only option and that's why I'm pursuing this. Right now, I > have to take another laptop running Windows when I go to such places. > > Thanks again, > > Leslie > > > Marvin Stodolsky wrote: >> >> Leslie, >> >> Please send us your entire ModemData.txt , from running scanModem >> >> MarvS >> >> >> On Sun, Dec 21, 2008 at 4:32 PM, Antonio Olivares >> <olivares14031@xxxxxxxxx> wrote: >> >>> >>> Leslie, >>> >>> Why don't you try /dev/ttySM0 as the modem port and attempt the >>> connection? >>> >>> Try a wvdial.conf like >>> >>> [Dialer Defaults] >>> Modem = /dev/ttySM0 >>> Baud = 460800 >>> Init1 = ATZ >>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>> ISDN = 0 >>> Modem Type = Analog Modem >>> Carrier Check = No >>> ; Dial Command = ATDP >>> ; Phone = <Target Phone Number> >>> ; Username = <Your Login Name> >>> ; Password = <Your Password> >>> >>> except please remove the ";" and "<" and ">" add your own username, >>> phone number and password. Try to connect out and post the error >>> messages if you get any. >>> >>> Regards, >>> >>> Antonio >>> >>> On 12/21/08, Leslie Katz <lesliek@xxxxxxxxxxxxxx> wrote: >>> >>>> >>>> 1. "which wvdial" shows wvdial is installed. ("wvdial --version" shows >>>> that it's version 1.60.) >>>> 2. I run "wvdialconf /etc/wvdial.conf". >>>> 3. I get: >>>> >>>> "Scanning your serial ports for a modem. >>>> >>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> Modem Port Scan<*1>: S1 >>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> Modem Port Scan<*1>: S3 >>>> WvModem<*1>: Cannot get information for serial port. >>>> ttySM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttySM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttySM0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> >>>> >>>> Sorry, no modem was detected!" >>>> >>>> 4. I am using the Martian module and application ( the versions dated >>>> 20080625). The module is loaded and, before running wvdialconf, I have >>>> run "martian_modem" as root and got as output "martian: info: Your port >>>> is /dev/ttySM0". >>>> 5. Step 5 of your instructions says: "If wvdialconf does not find modem >>>> ..., your modem installation is not good even if it seemed Ok. Go back >>>> to modem driver installation. Be sure to slowly and carefully read all >>>> the installation instructions." >>>> >>>> I don't know what to do next. As best I can understand it, the output I >>>> got when running "martian_modem" confirms that my modem installation WAS >>>> good and I believe that I've followed the installation instructions. >>>> >>>> I'd appreciate guidance. Should I be posting my ModemData.txt file for >>>> that purpose? >>>> >>>> Thank you, >>>> >>>> Leslie >>>> >>>> -------------------------------------------------- >>>> View my Social Science Research Network Author page: >>>> http://ssrn.com/author=1164057 >>>> -------------------------------------------------- >>>> >>>> >> >> > > -- > -------------------------------------------------- > View my Social Science Research Network Author page: > http://ssrn.com/author=1164057 > -------------------------------------------------- > >
