Jacques Goldberg schrieb: > You should then have aumixer , alsamixer, and xfce-mixer , one of > which at least able to control the status of the hook among many other > features. I couldn't find a way to do this with a commandline tool, so I used xfce4-mixer and checked the Off-hook-box. No success: # sudo wvdial --> WvDial: Internet dialer version 1.56 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 X3 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 X3 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Modem initialized. --> Sending: ATX0DT019164284 --> Waiting for carrier. ATX0DT019164284 --> Timed out while dialing. Trying again. --> Sending: ATX0DT019164284 --> Waiting for carrier. NO CARRIER ATX0DT019164284 --> No Carrier! Trying again. The checkbox was automatically unchecked when I stopped wvdial and then again checked when I started wvdial once more. Tim. > Tim Kielmann wrote: >> Hi Jacques, >> >> Jacques Goldberg schrieb: >>> Do you have a line >>> Carrier Check = no >>> in your file wvdial.conf ? >> >> Yes, wvdial.conf also is in my initial mail. >>> If you already have it, use the alsa mixer to switch the Modem on/off >>> hook status. >> >> How do I do that? Sorry, >> # man amixer >> didn't help me with this. >> >> # amixer | grep -i hook >> Simple mixer control 'Off-hook',0 >> >>> Finally, if you are using KDE, are you aware that it resets ALSA to >>> being off when you login? >> >> No, Xubuntu uses Xfce. >> >> >> Thanks, >> Tim. >> >>> Tim Kielmann wrote: >>>> Hello Joern, >>>> >>>> Joern Wuestenfeld schrieb: >>>>> did you take a look at the files in /proc/asound? >>>>> >>>>> There should be a directory called card0. Inside this directory there >>>>> should be two files named "codec#0" and "codec#1". Normally >>>>> "codec#1" is >>>>> the modem codec. Do a `cat codec#1`. >>>> # find /proc/asound/card0 -iname "codec*" >>>> /proc/asound/card0/codec97#0 >>>> >>>> # ls -l /proc/asound/card0/ >>>> insgesamt 0 >>>> dr-xr-xr-x 2 root root 0 2007-05-25 11:31 codec97#0 >>>> -r--r--r-- 1 root root 0 2007-05-25 11:31 id >>>> -rw-r--r-- 1 root root 0 2007-05-25 11:31 oss_mixer >>>> dr-xr-xr-x 3 root root 0 2007-05-25 11:31 pcm0c >>>> dr-xr-xr-x 34 root root 0 2007-05-25 11:31 pcm0p >>>> dr-xr-xr-x 3 root root 0 2007-05-25 11:31 pcm1p >>>> -r--r--r-- 1 root root 0 2007-05-25 11:31 sis7018 >>>> >>>> # ls -l /proc/asound/card0/codec97#0/ >>>> insgesamt 0 >>>> -r--r--r-- 1 root root 0 2007-05-25 11:32 ac97#0-0 >>>> -r--r--r-- 1 root root 0 2007-05-25 11:32 ac97#0-0+regs >>>> -r--r--r-- 1 root root 0 2007-05-25 11:32 mc97#1-1 >>>> -r--r--r-- 1 root root 0 2007-05-25 11:32 mc97#1-1+regs >>>> >>>> # cat /proc/asound/card0/codec97#0/mc97#1-1 >>>> 1-1/0: Silicon Laboratory Si3036,8 rev 2 >>>> >>>> Extended modem ID: codec=1 LIN1 >>>> Modem status : GPIO MREF ADC1 DAC1 PRE(ADC2) PRF(DAC2) PRG(HADC) >>>> PRH(HDAC) >>>> Line1 rate : 8000Hz >>>> >>>>> If this seems to be the modem >>>>> (identified by Id), then look at the directories named pcmXY, where >>>>> X is >>>>> the device number and Y is either c (capture) or p (playback). >>>>> Important >>>>> is the device number. >>>>> Normally 0 is the audio device, and the modem is 1. But it can be any >>>>> other number also. Look in one of the directories with the higher >>>>> number >>>>> at the file named "info". It should clearly point out whether its the >>>>> audio or the modem device. >>>> Can't say it does (for me at least), but playback only wouldn't >>>> make too >>>> much sense, right? >>>> >>>> # cat /proc/asound/card0/pcm1p/info >>>> >>>> card: 0 >>>> device: 1 >>>> subdevice: 0 >>>> stream: PLAYBACK >>>> id: trident_dx_nx IEC958 >>>> name: Trident 4DWave IEC958 >>>> subname: subdevice #0 >>>> class: 0 >>>> subclass: 0 >>>> subdevices_count: 1 >>>> subdevices_avail: 1 >>>> >>>> # cat /proc/asound/card0/pcm0c/info >>>> card: 0 >>>> device: 0 >>>> subdevice: 0 >>>> stream: CAPTURE >>>> id: trident_dx_nx >>>> name: Trident 4DWave >>>> subname: subdevice #0 >>>> class: 0 >>>> subclass: 0 >>>> subdevices_count: 1 >>>> subdevices_avail: 0 >>>> >>>> # cat /proc/asound/card0/pcm0p/info >>>> card: 0 >>>> device: 0 >>>> subdevice: 0 >>>> stream: PLAYBACK >>>> id: trident_dx_nx >>>> name: Trident 4DWave >>>> subname: subdevice #0 >>>> class: 0 >>>> subclass: 0 >>>> subdevices_count: 32 >>>> subdevices_avail: 31 >>>> >>>> >>>>> If you found the modem device, restart >>>>> slmodemd with hw:0,X. Where X is the number from the pcmXY directory. >>>>> This tells slmodemd, which sub device to use. >>>> # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa hw:0,1 >>>> error: alsa setup: cannot open playback device 'hw:0,1': No such >>>> file or >>>> directory >>>> >>>> error: cannot setup device `hw:0,1' >>>> >>>> # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa hw:0,0 >>>> SmartLink Soft Modem: version 2.9.11 May 5 2007 01:31:04 >>>> <743.689064> SmartLink Soft Modem: version 2.9.11 May 5 2007 01:31:04 >>>> <743.689271> hw:0,0: startup modem... >>>> <743.689737> hw:0,0: update termios... >>>> symbolic link `/dev/ttySL0' -> `/dev/pts/0' created. >>>> modem `hw:0,0' created. TTY is `/dev/pts/0' >>>> <743.692947> open file: /var/lib/slmodem/data.hw:0,0... >>>> <743.695291> main: rt applyed: SCHED_FIFO, pri 99 >>>> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >>>> >>>> >>>> wvdial fails like before. >>>> >>>> Is it relevant that slamr identifies a SiS630 card >>>> # dmesg |grep slamr >>>> [ 3356.143884] slamr: module license 'Smart Link Ltd.' taints kernel. >>>> [ 3356.288180] slamr: SmartLink AMRMO modem. >>>> [ 3356.288435] slamr: probe 1039:7013 SiS630 card... >>>> [ 3356.392764] slamr: mc97 codec is SIL22 >>>> [ 3356.392879] slamr: slamr0 is SiS630 card. >>>> >>>> but apart from that SiS630 is never mentioned? >
