Robin, Try dialing out with /dev/modem as the modem port. See if you can connect. On several attempts of mine with agrsm, intel536 modem I see wvdialconf find no modem port, but specifying it I can connect try that and report back. I believe that this time it will work :) Regards, Antonio On 3/15/10, Robin <modem@xxxxxxxxxx> wrote: > Hi Joshua, > > Thank you for your suggestions. > > Firstly I tried to compile agrsm-20080203.tar.gz with my original 2.6.26 > kernel (as is shipped with debian lenny). This compiled properly, > unfortunately there was no change in behavior when I ran wvdialconf. It > still didn't respond to the ATZ command as i demonstrated in one of my > previous posts. > > Secondly i tried your recommendation for using the 2.6.29 kernel, with > the 2.6.29 kernel I reinstalled agrsm048pci-2.1.60_worked20100108_i386.deb. > This also had no effect, no response to the ATZ command. > > Besides that I finally was able to have the PCI card placed in a > different slot on the motherboard (as i do not have direct acces to the PC). > This had a unexpected result: > After modprobing them /var/log/messages returns the usual: > > agrmodem: module license 'Proprietary' taints kernel. > agrsm 0000:01:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 > agrsm: created 1 infos > ttyAGS3 at I/O 0xd800 (irq = 21) is a AgereModem > agrserial: Loading module Agere Modem Interface driver version > 2.1.60.0.Linspire (2005-11-16) > > After setting up the symbolic links (/dev/modem and /dev/ttySAGR) I run > wvdialconf again, but this time it stalls: > > # wvdialconf /etc/wvdial.conf > Editing `/etc/wvdial.conf'. > > 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 S2 S3 > > This is where it stalls for about a minute.... and then contiues. > > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > > This stalling happens on both the 2.6.29 and 2.6.26 kernels. > > As a last ditch effort to get this modem working I attached the output > of lspci -vv to this post. Maybe you can spot a conflict, if you can't > find one i think I'm going to give up on this modem. > > Thanks in advance, > - Robin > > # lspci -vv > 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM > Controller/Host-Hub Interface (rev 03) > Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM > Controller/Host-Hub Interface > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort+ >SERR- <PERR- INTx- > Latency: 0 > Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M] > Capabilities: [e4] Vendor Specific Information <?> > Kernel driver in use: agpgart-intel > Kernel modules: intel-agp > > 00:02.0 VGA compatible controller: Intel Corporation > 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) > (prog-if 00 [VGA controller]) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M] > Region 1: Memory at ffa80000 (32-bit, non-prefetchable) [size=512K] > Capabilities: [d0] Power Management version 1 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel modules: intelfb > > 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 16 > Region 4: I/O ports at e800 [size=32] > Kernel driver in use: uhci_hcd > Kernel modules: uhci-hcd > > 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin B routed to IRQ 19 > Region 4: I/O ports at e880 [size=32] > Kernel driver in use: uhci_hcd > Kernel modules: uhci-hcd > > 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM > (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin C routed to IRQ 18 > Region 4: I/O ports at ec00 [size=32] > Kernel driver in use: uhci_hcd > Kernel modules: uhci-hcd > > 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 > EHCI Controller (rev 02) (prog-if 20 [EHCI]) > Subsystem: Intel Corporation Device 5247 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin D routed to IRQ 23 > Region 0: Memory at ffa7fc00 (32-bit, non-prefetchable) [size=1K] > Capabilities: [50] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [58] Debug port: BAR=1 offset=0080 > Kernel driver in use: ehci_hcd > Kernel modules: ehci-hcd > > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82) (prog-if > 00 [Normal decode]) > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR+ INTx- > Latency: 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 > I/O behind bridge: 0000d000-0000dfff > Memory behind bridge: ff800000-ff8fffff > Prefetchable memory behind bridge: e6a00000-e6afffff > Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort+ <SERR- <PERR- > BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- > PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- > Kernel modules: shpchp > > 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC > Interface Bridge (rev 02) > Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Kernel modules: iTCO_wdt, intel-rng > > 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller > (rev 02) (prog-if 8a [Master SecP PriP]) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 18 > Region 0: I/O ports at 01f0 [size=8] > Region 1: I/O ports at 03f4 [size=1] > Region 2: I/O ports at 0170 [size=8] > Region 3: I/O ports at 0374 [size=1] > Region 4: I/O ports at ffa0 [size=16] > Region 5: Memory at 10000000 (32-bit, non-prefetchable) [size=1K] > Kernel driver in use: PIIX_IDE > Kernel modules: piix > > 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) > SMBus Controller (rev 02) > Subsystem: Intel Corporation Device 5247 > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin B routed to IRQ 17 > Region 4: I/O ports at e480 [size=32] > Kernel driver in use: i801_smbus > Kernel modules: i2c-i801 > > 01:00.0 Communication controller: Agere Systems V.92 56K WinModem (rev 02) > Subsystem: Agere Systems Device 044c > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 32 (63000ns min, 3500ns max) > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at ff8ffc00 (32-bit, non-prefetchable) [size=256] > Region 1: I/O ports at dc00 [size=8] > Region 2: I/O ports at d800 [size=256] > Capabilities: [f8] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA > PME(D0-,D1-,D2+,D3hot+,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: agrsm > > 01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) > Ethernet Controller (rev 82) > Subsystem: Intel Corporation Device 3011 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 20 > Region 0: Memory at ff8fe000 (32-bit, non-prefetchable) [size=4K] > Region 1: I/O ports at d480 [size=64] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=2 PME- > Kernel driver in use: e100 > Kernel modules: e100 > > > > On 03/15/2010 01:27 AM, Joshua Gordon Crawford wrote: >> On 14 March 2010 00:35, Robin<modem@xxxxxxxxxx> wrote: >> >>> Hi, >>> >> G'day Robin. Sorry for the late reply. I'm the quasi-maintainer of the >> agrsm 11c1:048c/f driver. >> >> >>> I'm in the process of installing a WinModem from Agere/Lucent on Debian >>> Lenny. >>> >>> According to scanModem the modem's PCI ID is 11c1:048c. >>> Knowing this I successfully installed the driver from >>> agrsm048pci-2.1.60_20100106_i386.deb onto my system. >>> Inserting the created kernel modules (agrmodem& agrserial) don't give >>> any >>> errors in /var/log/messages. >>> After confirming that /dev/ttyAGR3 exists and creating symbolic links to >>> it >>> (/dev/ttySAGR& /dev/modem) I try to run wvdialconf to confirm that >>> everything went correctly. >>> >>> But unfortunatly wvdialconf returns the following: >>> >>> box:/home/me# wvdialconf /etc/wvdial.conf >>> Editing `/etc/wvdial.conf'. >>> >>> 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 S2 S3 >>> ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>> ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>> baud >>> ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>> >>> >>> Sorry, no modem was detected! Is it in use by another program? >>> Did you configure it properly with setserial? >>> >>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial >>> >>> If you still have problems, send mail to<wvdial-list@xxxxxxxxxxxx>. >>> >>> I tried changing kernels, 2.6.30 and 2.6.32, both have the same behaviour >>> ( >>> >> So far, I've only updated the code to work on 2.6.29.*. It does >> include an update that should work on 2.6.31, but I don't have that >> kernel to test it. >> >> The driver works well on 2.6.29.6. I've currently been connected for >> over 2 weeks, at 53666 baud. >> >> I'll have to wait and see about later versions when the next >> Slackware release comes out. This machine unfortunately cannot be >> taken down for testing, only major upgrades. >> >> You've mentioned several kernel versions. Which version do you normally >> use? >> >> >>> 2.6.26 won't compile citing an error in a struct definition). >>> >> The struct uart_info in the kernel changed a bit around that time. Use >> an older code package for older kernels. The driver has only been >> updated to follow the kernel changes, there are no functionality >> updates. >> >> This link is to an older version, which I think should work on that >> kernel. It's source only and not dkms capable, so you'll have to >> compile and install manually. Always make sure to remove old modules >> before installing new ones. >> <http://linmodems.technion.ac.il/packages/ltmodem/sv92/agrsm-20080203.tar.gz> >> >> Marv, Jacques: I notice newer 048c/f packages are going in the >> 11c11040 directory instead of sv92. Why is that? >> >> >>> Also tried various boot parameters: pci=pollirq pci=routeirq pci=noacpi >>> and >>> >> These shouldn't be necessary since an update in 2008. >> >> >>> disabling the on-board soundcard. >>> >> This is not needed unless there is an IRQ conflict. Run 'lspci -v', to >> check that. Or send us the output of scanModem so we can check it. >> >> >>> And i tried older versions of the driver >>> (agrsm048pci-2.1.60_20090905_i386.deb) and compiling by hand >>> (agrsm048pci-2.1.60_20100108.tar.gz) >>> >>> Seeing as there are no error message I don't know where to look for a >>> problem, can anyone point me in the right direction? >>> >>> P.S. I don't quite understand the relationship between the agrsm driver >>> and >>> ALSA, should my modem be listed in /proc/asound/cards ? Because it >>> currently >>> reports: --- no soundcards --- >>> >> The 11c1:048c/f is on a stand-alone PCI card and is not part of the >> sound device, as more recent Agere modems have been. So this driver >> does not use ALSA, and ALSA doesn't know anything about this modem. >> > >
