John, The accumulated experience we have with cases like yours can be easily summarized. When a modem on a HIgh Definition Audio (HDA) card is not working reliably, try upgrading the driver to a more recent release. The snd-hda-intel driver is being continually improved, and some List members have acquired reliable function through driver upgrades. After an upgrade if the problem persists, a bug report should be sent to the snd-hda-intel maintainer at ALSA So here at the upgrade instructions. Your case is very similar to Anita's who is also working on an upgrade presently. Make a working folder $ sudo mkdir -p /usr/src/modules/alsa Assuming your login name is John, $ sudo chown -R john:john /usr/src/modules/ This make it permissible to work therein without "sudo" thereafter in modules/ and its sub folders You will need to download from http://www.alsa-project.org/main/index.php/Main_Page the current stable packages, now the alsa-driver-1.0.16 and alsa-lib-1.0.16 $ cd /usr/src/modules/alsa to unpack therein. Prefix the PATH_to the package, to unpack with commands: $ tar jxf PATH_to/alsa-driver*.tar.bz2 $ tar jxf PATH_to/alsa-lib*.tar.bz2 with the j calling the needed bunzip2 action. Move into the driver folder $ cd alsa-driver-1.0.16 where the work will be done, with calls to the parallel alsa-lib-1.0.16/ folder Browse a bit. Set a useful termporary defintion HEADERS=/lib/modules/2.6.22-14-generic/build Check for validity with: $ ls $HEADERS should show files like: arch include lib scripts block init Makefile security crypto ipc mm sound drivers fs kernel net usr ---------------- This definition does not survive a shutdown and must be redone upon reboot, when a new driver compiling is necessary. $ make clean Do the configuration with with the following command on ONE LINE: $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel Get some coffee while it runs. If the configuration is successful, the driver set will be compiled with: $ make Get more coffee. When completed the replacement driver set is displayed by: $ ls modules and installed by $ sudo make install Then reboot to have the new drivers used and retest. Report back presently. MarvS On Fri, Mar 7, 2008 at 8:29 PM, Smaknj <Smaknj@xxxxxxxxxxx> wrote: > Hi, I need help with wvdial and/or pppd. I previously sent this message > to wvdial@xxxxxx but that site is no longer up. I also tried > discuss-get.123_145@xxxxxxxxxxxxx but received no reply. > > I am trying to locate someone from wvdial that could help as I think > this is the proper starting point. > > > If someone who can help with wvdial is available: > > Please read the 'forwarded message' attachment to start. > > Jacques Goldberg provided me with a debug script. Its output contains > most of what should be needed to get an idea of the problem. Attached > are a few attempts to connect, some succeeded, some failed after > succeeding, some never connected at all, some even cause slmodemd to fail. > > We can start wherever you like. I am a newbie in linux. > > Thanks for your help. > > John. > > > ---------- Forwarded message ---------- > From: Jacques Goldberg <Jacques.Goldberg@xxxxxxx> > To: John Gammon <Syntactics@xxxxxxxxxxx> > Date: Sat, 01 Mar 2008 21:31:16 +0200 > Subject: Re: John CANADA Kernel 2.6.22-14-generic > John, > This has reached a level too difficult for me. > Transmitting to the list. > Please reply to "Reply-to".discuss-get.123_145@xxxxxxxxxxxxx > > LIST: I have made my best, with no success, to try to find why his > slmodemd compatible modem fails under Ubuntu 7.10 2.6.22-24.generic. > The communication behaves erratically at random, sometimes connect, > sometimes not, sometimes hangs while connected, sometimes not. > > PLEASE TAKE OVER .... > > John Gammon wrote: > > Jacques, > > > > when the 'sudo wvdial' command fails while trying to connect: > > > > smaknj@Smaknj-Laptop:~$ sudo wvdial > > WvDial<*1>: WvDial: Internet dialer version 1.56 > > WvModem<*1>: Cannot get information for serial port. > > WvDial<*1>: Initializing modem. > > WvDial<*1>: Sending: ATZ > > WvDial Modem<*1>: ATZ > > WvDial Modem<*1>: OK > > WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > > WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > > WvDial Modem<*1>: OK > > WvDial<*1>: Modem initialized. > > WvDial<*1>: Sending: ATDT7804218500 > > WvDial<*1>: Waiting for carrier. > > WvDial Modem<*1>: ATDT7804218500 > > WvDial Modem<*1>: NO CARRIER > > WvDial<Warn>: No Carrier! Trying again. > > WvDial<*1>: Disconnecting at Fri Feb 29 11:19:57 2008 > > smaknj@Smaknj-Laptop:~$ > > > > It causes the slmodemd to fail > > > > smaknj@Smaknj-Laptop:~$ sudo slmodemd -c CANADA --alsa hw:0,6 > > SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10 > > symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > > modem `hw:0,6' created. TTY is `/dev/pts/1' > > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > > error: cannot update delay: 0 instead of 384. > > smaknj@Smaknj-Laptop:~$ > > > > > >> My understanding... (which may be false) is that slmodemd dynamically > > creates a symbolic link to the modem hardware, and remains alive > > to perform certain duties unknown to me. > > > > Wvdial is then executed, which (via its wvdial.conf entry 'modem = > > ttysL0') points to the modem and talks to the codec running on the > > modem, telling it to dial out to the designated phone number. > > > > Wvdial will try to negotiate the connection and (if successful) > > startup pppd (which has its own 'provider' file, with connection > > settings that match the wvdial.conf file). pppd will then take > > over as the primary communication and packet handler, talking with > > the peer ppp software. > > > > If wvdial cannot negotiate a connection, it quits. > >> End My understanding.... > > > > does this 'slmodemd' error: > > > > error: cannot update delay: 0 instead of 384. > > > > possibly indicate what kind of problem wvdial is having? > > > > Since pppd is not launched, I conclude that wvdial is the > > component that is failing. However, what I do in the wvdial.conf > > file either prevents connecting entirely, or allows connecting, but > > not every time. The default settings work the best. > > > > I realize I am grasping at straws now. So I am trying to understand > > the 'behind the scenes' activity, to try to isolate which component > > is the one failing.... slmodemd or wvdial or pppd or ? > > > > I picked up a phone line splitter and I'm able to listen on the phone > > to the protocols. I notice that the protocol sequence starts out > > normal (like my other pc), but within a few seconds the chatter becomes > > very high pitched and "sparky" or "chirpy", not the usual lower tones > > I'm used to hearing. > > > > Is the modem itself the problem? > > > > On my desktop panel, I can select 'dialup connections' from the network > > icon, and launch 'Connect to ppp0 via modem. I thought it should have > > said 'Connect to modem via ppp0', but it doesn't work anyway. > > > > Since the /etc/ppp/options file contains 'redial' capabilities, it seems > > that pppd is also capable of dialling out on its own. > > > > Any ideas? > > > > thanks > > > > John. > > > >
