Typo If necessary, also $ sudo modprobe should have been If necessary, also $ sudo modprobe -r agrmodem MarvS On Wed, Mar 23, 2011 at 1:19 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > Aliet, > > > Try unloading the drivers > $ sudo modprobe -r agrserial > This will likely be enough to unload both drivers. ÂCheck with: > $ lsmod | grep agr > If necessary, also > $ sudo modprobe > > Then reload, > $ sudo modprobe agrserial > > If that doesn't cure, I don't have a solution, because of the major > Closed Source component of the agrmodem driver > > MarvS > scanModem maintainer > > On Wed, Mar 23, 2011 at 1:07 AM, Aliet Exposito > <exposito.ssp@xxxxxxxxxxxxxx> wrote: >> Greetings from Cuba, >> I am having a etcurious problem with an Agere Lucent 11c1:0620 Modem: >> --------------------------------------------------------------------- >> $ sudo lspci -s 02:02.0 -v >> 02:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax >> Modem >> Subsystem: Agere Systems Lucent V.92 Data/Fax Modem >> Flags: fast Back2Back, medium devsel, IRQ 17 >> I/O ports at 1000 [size=256] >> Capabilities: [f8] Power Management version 3 >> --------------------------------------------------------------------- >> I'm using 'agrsm06pci-2.1.80~20100106.tar.gz' drivers with Ubuntu Lucid >> Lynx 10.04.1 LTS and they work just fine until I Suspend or Hibernate my >> PC, you can see the 'ModemData-before-hibernation.txt' attached for >> detailed information. >> Whenever I resume the PC from a suspended/hibernated state the Modem >> fails to work, although the drivers are still loaded. >> Using 'wvdial' hangs the OS for about 30 sec and fails: >> --------------------------------------------------------------------- >> $ time wvdial >> --> WvDial: Internet dialer version 1.60 >> --> Initializing modem. >> --> Sending: ATZ >> --> Sending: ATQ0 >> --> Re-Sending: ATZ >> --> Modem not responding. >> >> real 0m26.185s >> user 0m0.004s >> sys 0m15.241s >> --------------------------------------------------------------------- >> 'wvdialconf' hangs too when trying with '115200 baud', and fails in >> detecting the Modem: >> --------------------------------------------------------------------- >> $ wvdialconf /tmp/delme >> Editing `/tmp/delme'. >> >> Scanning your serial ports for a modem. >> >> WvModem<*1>: Cannot set information for serial port. >> 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? >> --------------------------------------------------------------------- >> Normally the output of 'wvdialconf' is like this: >> --------------------------------------------------------------------- >> $ wvdialconf /tmp/delme >> Editing `/tmp/delme'. >> >> Scanning your serial ports for a modem. >> >> WvModem<*1>: Cannot set information for serial port. >> 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 >> WvModem<*1>: Cannot set information for serial port. >> ttySAGR<*1>: ATQ0 V1 E1 -- OK >> ttySAGR<*1>: ATQ0 V1 E1 Z -- OK >> ttySAGR<*1>: ATQ0 V1 E1 S0=0 -- OK >> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK >> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK >> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK >> ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.80.0 >> ttySAGR<*1>: Speed 4800: AT -- OK >> ttySAGR<*1>: Speed 9600: AT -- OK >> ttySAGR<*1>: Speed 19200: AT -- OK >> ttySAGR<*1>: Speed 38400: AT -- OK >> ttySAGR<*1>: Speed 57600: AT -- OK >> ttySAGR<*1>: Speed 115200: AT -- OK >> ttySAGR<*1>: Max speed is 115200; that should be safe. >> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK >> >> Found a modem on /dev/ttySAGR. >> /tmp/delme<Warn>: Can't open '/tmp/delme' for reading: No such file or >> directory >> /tmp/delme<Warn>: ...starting with blank configuration. >> Modem configuration written to /tmp/delme. >> ttySAGR<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" >> --------------------------------------------------------------------- >> The other attachment 'ModemData-after-hibernation.txt' which is as its >> name suggests 'ModemData.txt' after an hibernate/suspend shows subtle >> differences in 'Modem interrupt assignment and sharing' from the >> original one, I can only assume the issue is with assigning IRQs for the >> Modem and conflicting with the Sound Card, but I'm just guessing here... >> --------------------------------------------------------------------- >> The workaround that I've been using is unloading the drivers *before* >> hibernating/suspending: >> --------------------------------------------------------------------- >> $ sudo modprobe -r agrserial && sudo modprobe -r agrmodem >> --------------------------------------------------------------------- >> ...and reloading it again *after* resuming: >> --------------------------------------------------------------------- >> $ sudo modprobe agrmodem && sudo modprobe agrserial >> $ if test ! -L /dev/modem -a ! -L /dev/ttySAGR; then \ >> sudo ln -s /dev/ttyAGS3 /dev/ttySAGR && \ >> sudo ln -s /dev/ttyAGS3 /dev/modem; \ >> fi >> --------------------------------------------------------------------- >> If I try to unload/load the drivers *after* a problematic >> hibernate/suspend (without unloading the drivers previously) the OS >> hangs, becoming unresponsive even to Alt+SysRq keys, leaving me only >> with the hard way to reboot :/ >> >> I tried to set the subject the most generic way possible, I know this >> affects all Ubuntu 10.04 PC using this specific Modem and Drivers, I've >> tried this configuration in other two PCs, with the same results. >> >> Any help would be greatly appreciated, if there is no solution at the >> moment, I gladly would like to help fixing it with the help of experts >> out there. >> >> Regards, >> Aliet >> >> >> -- >> >> Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas >> >> Infomed: http://www.sld.cu/ >> >
