Hi, It is a laptop. In Windows 7 the modem is shown as: "Agere Systems HDA Modem" Windows Modem-HardwareIDs HDAUDIO\FUNC_02&VEN_11C1&DEV_1040&SUBSYS_11C10001&REV_1002 HDAUDIO\FUNC_02&VEN_11C1&DEV_1040&SUBSYS_11C10001 Driver Details: C:\Windows\system32\Drivers\AGRSM.sys LSI Corp 2.2.89.2 Modem-Test: ATQ0V1E0 - OK AT+GMM - H.324 video-ready rev. 1.0 AT+FCLASS=? - 0,1,8 AT#CLS=? - BEFEHL WIRD NICHT UNTERSTÜTZT AT+GCI? - +GCI:04 AT+GCI=? - +GCI:(00,01,02,04,06,07,09,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,19,1A,1B,1D,1 E,1F,20,21,22,23,24,25,26,27,29,2B,2D,2E,2F,30,31,32,33,35,36,37,38,3C,3D,40 ,41,43,44,45,46,47,48,49,4B,4C,4D,4E,4F,50,51,52,53,54,57,58,59,5A,5B,5E,5F, 61,62,63,64,66,68,69,6A,6B,6C,6D,6F,70,72,73,74,77,78,7A,7B,7C,7D,7E,7F,80,8 1,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F,90,93,96,97,98,99,9B,9C,9F,A0,A1 ,A3,A4,A5,A6,A7,A8,A9,AA,AC,AD,AE,B2,B3,B4,B5,B6,B7,B8,BB,BC,BF,C1,C2,C4) ATI1 - OK ATI2 - OK ATI3 - LSI Softmodem Version 2.2.89.2 ATI4 - Built on 11/10/2008 09:51:51 ATI5 - 2.2.89.2, HDA MB, HDA, A35 S-Rev:2 L-Rev:3, 06 ATI6 - OK ATI7 - HDA MB Benjamin -----Ursprüngliche Nachricht----- Von: Jacques Goldberg [mailto:Jacques.Goldberg@xxxxxxx] Gesendet: Montag, 8. März 2010 18:00 An: Benjamin Colling Cc: discuss@xxxxxxxxxxxxx Betreff: Re: agere softmodem HDA + Intel Ibex Peak High Definition Audio Benjamin, In your scanModem output there is no sign of presence of any Agere modem hardware (which would couple to the agrsm driver). The driver is a program, not hardware. You can always send soem data to any program: perhaps the driver tries to do soemthing, but whatever it will do will be sent into vacuum, The presence of the agrsm can only cause trouble when trying to use the right driver. The Intel HECI controller can in no way drive a modem. HECI has nothing to do with that. Thus scanModem has not found anything resembling a modem in your computer. "Hopefully" (poor you) you may have Windows running on the same machine. In the folder where scanModem created its output (the file ModemData.txt), there is information of using Windows in identifying some of the modem information, often enough to know how to proceed under Linux. Please try that approach. It would help us a lot to know if your computer is a laptop or a desktop. If destop, open the box and follow back the cable connected to the modem jack until you land on a card or on a chip, and copy for us anything readable on the card or chip. Jacques Benjamin Colling wrote: > Hi, > > agrsm-11c11040 packages was not recommended by scanModem utility. But I did > not find any other software. > > >>> What does the following reports? >>> >>>>> sudo wvdialconf /etc/wvdial.conf >>>>> > > Wvdial (original numSupportedDevice) > --> WvDial: Internet dialer version 1.60 > --> Initializing modem. > --> Sending: ATZ > --> Sending: ATQ0 > --> Re-Sending: ATZ > --> Modem not responding. > > Kernel-Msg: > [ 1757.377343] ==> codecType = 0x31 > [ 1757.377349] ERR: Control Interface failed > > > >>> I run 'nm agrmodemlib.o_shipped | grep numSupportedDevice' >>> and it tells me the binary blob is using the variable in some way. >>> Maybe something inside that blob maxed out when you added the line? >>> What if instead of adding the line you replace some existing >>> line with your line? >>> > > I changed an existing line but get this output, when accessing the device > with wvdial: > > [ 1949.953524] * Hello Agere Driver ** > [ 1949.953585] usbcore: registered new interface driver agr12dec2006 > [ 1951.198280] Loading module Agere Modem Controller driver version 2.1.80 > (2007-10-01) > [ 1960.368259] serial8250_register_ports: BaseAddress 0x0400 Irq 3 > [ 1960.368267] ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem > [ 1960.368685] agrserial - ret_val 0, call: lt_modem_ops.init_modem > [ 1960.368690] Loading module Agere Modem Interface driver version 2.1.80.0 > (2007-10-01) > [ 1975.377046] ==> codecType = 0x6c466174 > > > > > Here is the output of scanModem: > > -------------------------- System information ---------------------------- > CPU=i686, debian , ALSA_version=1.0.21 > Linux version 2.6.32.6 (root@Knoppix) (gcc version 4.4.3 20100108 > (prerelease) (Debian 4.4.2-9) ) #8 SMP PREEMPT Thu Jan 28 10:51:16 CET 2010 > scanModem update of: 2010_02_25 > The modem symbolic link is /dev/modem -> /dev/ttyAGS3 > /etc/lsb-release not found > > > Presently install your Linux Distributions dkms package. It provides for > automated driver updates, > following upgrade of your kernel. For details see > http://linux.dell.com/projects.shtml#dkms > > There are no blacklisted modem drivers in /etc/modprobe* files > > Potentially useful modem drivers now loaded are: > snd_hda_intel agrmodem agrserial > > Attached USB devices are: > ID 3538:0054 Power Quotient International Co., Ltd Flash Drive (2GB) > ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > 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 > > Candidate PCI devices with modem chips are: > 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series > Chipset HECI Controller (rev 06) > 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT > Controller (rev 06) > 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High > Definition Audio (rev 06) > High Definition Audio cards can host modem chips. > > For candidate card in slot 00:16.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:16.0 8086:3b64 8086:3b64 Communication controller: > Intel Corporation 5 Series/3400 Series Chipset HECI Controller > > Modem interrupt assignment and sharing: > 25: 0 0 0 0 HPET_MSI-edge hpet3 > --- Bootup diagnostics for card in PCI slot 00:16.0 ---- > > For candidate card in slot 00:16.3, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:16.3 8086:3b67 8086:3b67 Serial controller: Intel > Corporation 5 Series/3400 Series Chipset KT Controller > > Modem interrupt assignment and sharing: > 17: 14 17 11 10 IO-APIC-fasteoi yenta > --- Bootup diagnostics for card in PCI slot 00:16.3 ---- > [ 15.421013] serial 0000:00:16.3: PCI INT B -> GSI 17 (level, low) -> IRQ > 17 > [ 15.421260] 0000:00:16.3: ttyS1 at I/O 0x6080 (irq = 17) is a 16550A > > For candidate card in slot 00:1b.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:3b56 8086:3b56 Audio device: Intel > Corporation 5 Series/3400 Series Chipset High Definition Audio > > Modem interrupt assignment and sharing: > 22: 1003 995 1012 1007 IO-APIC-fasteoi > ehci_hcd:usb1, HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 15.098895] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> > IRQ 22 > [ 15.098931] HDA Intel 0000:00:1b.0: setting latency timer to 64 > > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.4.3 > and the compiler used in kernel assembly: 4.4.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.4 > linuc_headers base folder /lib/modules/2.6.32.6/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. > > > Compressed files at: /usr/src/linux-source-2.6.32.6.tar.bz2 > > For Debian and some related distributions, a package kernel-kbuild-2.6-32 > may be needed to support driver compiling. > > > 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: > -rwsr-xr-- 1 root dip 274760 28. Nov 2008 /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 > auth > 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 > > For guidance on FAX usage, get from > http://linmodems.technion.ac.il/packages/ get faxing.tar.gz > It has samples for a modem using port /dev/ttySL0, which must be changed to > match your modem's port. > > Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1 > 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: lrwxrwxrwx 1 root root 12 8. Mär 17:46 > /dev/modem -> /dev/ttyAGS3 > 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/alsa-base-blacklist.conf:# Uncomment these entries in order > to blacklist unwanted modem drivers > /etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-atiixp-modem > /etc/modprobe.d/alsa-base-blacklist.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 -------- > > For Debian users, the linux-headers-2.6.32.6.deb can be used instead of > kernel-source/ > >
