Tim, Thanks for the report.Would you please write a clear description of the problem and the fix.Send it to the List where it will acquire a URL in the archives,which I'll code to display from scanModemon Systems using snd-trident drivers. MarvS On 6/1/07, Tim Kielmann <t.kielmann@xxxxxxx> wrote:> Hi Marvin,>> Marvin Stodolsky schrieb:> > Test as before, but this time:> > $ sudo modprobe snd_intel8x0> > before the:> > $ sudo modprobe snd_intel8x0m>> This worked as well.>> So I edited /etc/modprobe.d/blacklist> blacklist snd_intel8x0m> blacklist snd_trident> and> /etc/modules> snd_intel8x0> snd_intel8x0m> and everything is fine from the start. Thanks again.>> Tim.>> > On 5/29/07, Tim Kielmann <t.kielmann@xxxxxxx> wrote:> >> Marvin Stodolsky schrieb:> >> > When you reboot, agains> >> > # lsmod | grep snd> >> > to check that the trident driver doesnot load.> >> >> >> > Then again the:> >> > # modprobe snd-intel8x0m> >> > # lsmod | grep intel8x> >> > followed by> >> > # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa modem:1> >>> >> # lsmod |grep snd> >> snd_ac97_codec 98336 0> >> ac97_bus 3200 1 snd_ac97_codec> >> snd_pcm_oss 44544 0> >> snd_mixer_oss 17408 1 snd_pcm_oss> >> snd_pcm 79876 2 snd_ac97_codec,snd_pcm_oss> >> snd_page_alloc 10888 1 snd_pcm> >> snd_util_mem 5760 0> >> snd_mpu401_uart 9472 0> >> snd_seq_dummy 4740 0> >> snd_seq_oss 32896 0> >> snd_seq_midi 9600 0> >> snd_rawmidi 25472 2 snd_mpu401_uart,snd_seq_midi> >> snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi> >> snd_seq 52592 6> >> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event> >> snd_timer 23684 2 snd_pcm,snd_seq> >> snd_seq_device 9100 5> >> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq> >> snd 54020 10> >> snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device> >>> >> soundcore 8672 1 snd> >>> >> # sudo modprobe snd-intel8x0m> >> # lsmod |grep intel8x> >> snd_intel8x0m 18700 0> >> snd_ac97_codec 98336 1 snd_intel8x0m> >> snd_pcm 79876 3 snd_intel8x0m,snd_ac97_codec,snd_pcm_oss> >> snd_page_alloc 10888 2 snd_intel8x0m,snd_pcm> >> snd 54020 11> >> snd_intel8x0m,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device> >>> >>> >> # sudo ./slmodemd -d2 -c GERMANY --alsa modem:1> >> SmartLink Soft Modem: version 2.9.11 May 5 2007 01:31:04> >> <790.094940> SmartLink Soft Modem: version 2.9.11 May 5 2007 01:31:04> >> <790.095243> modem:1: startup modem...> >> <790.095730> modem:1: update termios...> >> symbolic link `/dev/ttySL0' -> `/dev/pts/2' created.> >> modem `modem:1' created. TTY is `/dev/pts/2'> >> <790.099015> open file: /var/lib/slmodem/data.modem:1...> >> <790.217779> cannot open '/var/lib/slmodem/data.modem:1': No such file> >> or directory> >> <790.523538> main: rt applyed: SCHED_FIFO, pri 99> >> Use `/dev/ttySL0' as modem device, Ctrl+C for termination.> >>> >> # 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: ATX0DT01920786> >> --> Waiting for carrier.> >> ATX0DT01920786> >> CONNECT> >> --> Carrier detected. Starting PPP immediately.> >> --> Starting pppd at Mon May 28 18:15:23 2007> >> --> Pid of pppd: 5383> >> --> Using interface ppp0> >>> >> This did the trick, thanks a lot for your help and anyone involved.> >>> >> I could even load snd_trident afterwards and establish sound support> >> while using the modem.> >> But that seems to have some funky side-effects, so I'll leave it at> >> that.> >>> >>> >> Best,> >> Tim.> >>> >> > On 5/27/07, Tim Kielmann <t.kielmann@xxxxxxx> wrote:> >> >> Marvin Stodolsky schrieb:> >> >> > What is the output of:> >> >> > $ lsmod | grep snd> >> >>> >> >> $ lsmod |grep snd> >> >> snd_trident 44548 5> >> >> gameport 16520 2 snd_trident> >> >> snd_ac97_codec 98336 1 snd_trident> >> >> ac97_bus 3200 1 snd_ac97_codec> >> >> snd_pcm_oss 44544 0> >> >> snd_mixer_oss 17408 1 snd_pcm_oss> >> >> snd_pcm 79876 5> >> snd_trident,snd_ac97_codec,snd_pcm_oss> >> >> snd_page_alloc 10888 2 snd_trident,snd_pcm> >> >> snd_util_mem 5760 1 snd_trident> >> >> snd_mpu401_uart 9472 1 snd_trident> >> >> snd_seq_dummy 4740 0> >> >> snd_seq_oss 32896 0> >> >> snd_seq_midi 9600 0> >> >> snd_rawmidi 25472 2 snd_mpu401_uart,snd_seq_midi> >> >> snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi> >> >> snd_seq 52592 6> >> >> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event> >> >> snd_timer 23684 2 snd_pcm,snd_seq> >> >> snd_seq_device 9100 6> >> >>> >> snd_trident,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq> >> >> snd 54020 19> >> >>> >> snd_trident,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device> >>> >> >>> >> >> soundcore 8672 1 snd> >> >>> >> >> > and please send your complete ModemData.txt output from running> >> >> > ./scanModem> >> >>> >> >> Is attached.> >> >>> >> >> I already read> >> >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00448.html> >> >> but failed to unload snd_trident> >> >>> >> >> # sudo modprobe -r snd-intel8x0m> >> >> # sudo modprobe -r snd-intel8x0> >> >> # sudo modprobe -r snd-trident> >> >> FATAL: Module snd_trident is in use.> >> >>> >> >>> >> >> so I renamed it.> >> >> # cd /lib/modules/2.6.20-15-generic/kernel/sound/pci/trident/> >> >> # sudo mv snd-trident.ko snd-trident.ko~> >> >> [Reboot]> >> >> # sudo modprobe snd-intel8x0> >> >> # sudo modprobe snd-intel8x0m> >> >> # lsmod |grep snd> >> >> snd_intel8x0m 18700 0> >> >> snd_intel8x0 34204 0> >> >> snd_ac97_codec 98336 2 snd_intel8x0m,snd_intel8x0> >> >> ac97_bus 3200 1 snd_ac97_codec> >> >> snd_pcm_oss 44544 0> >> >> snd_mixer_oss 17408 1 snd_pcm_oss> >> >> snd_pcm 79876 4> >> >> snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss> >> >> snd_page_alloc 10888 3 snd_intel8x0m,snd_intel8x0,snd_pcm> >> >> snd_util_mem 5760 0> >> >> snd_mpu401_uart 9472 0> >> >> snd_seq_dummy 4740 0> >> >> snd_seq_oss 32896 0> >> >> snd_seq_midi 9600 0> >> >> snd_rawmidi 25472 2 snd_mpu401_uart,snd_seq_midi> >> >> snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi> >> >> snd_seq 52592 6> >> >> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event> >> >> snd_timer 23684 2 snd_pcm,snd_seq> >> >> snd_seq_device 9100 5> >> >> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq> >> >> snd 54020 12> >> >>> >> snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device> >>> >> >>> >> >> soundcore 8672 1 snd> >> >>> >> >> But it didn't help:> >> >> # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa /dev/slamr0> >> >> error: mixer setup: attach hw:0 error: No such device> >> >> <913.615089> main: alsa setup: cannot setup mixer: No such device> >> >> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM /dev/slamr0> >> >> error: alsa setup: cannot open playback device '/dev/slamr0': No such> >> >> file or directory> >> >> error: cannot setup device `/dev/slamr0'> >> >>> >> >> # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa modem:1> >> >> error: mixer setup: attach hw:1 error: No such device> >> >> <923.340191> main: alsa setup: cannot setup mixer: No such device> >> >> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM> >> cards.pcm.modem> >> >> error: alsa setup: cannot open playback device 'modem:1': No such> >> file> >> >> or directory> >> >> error: cannot setup device `modem:1'> >> >>> >> >> Unfortunately the thread mentioned before doesn't go any further.> >> >>> >> >>> >> >> Tim.> >> >>> >> >> > On 5/27/07, Tim Kielmann <t.kielmann@xxxxxxx> wrote:> >> >> >> Hi Marvin,> >> >> >>> >> >> >> Marvin Stodolsky schrieb:> >> >> >> > With:> >> >> >> >> >>>> [ 3356.288435] slamr: probe 1039:7013 SiS630 card...> >> >> >> >> >>>> [ 3356.392764] slamr: mc97 codec is SIL22> >> >> >> >> >>>> [ 3356.392879] slamr: slamr0 is SiS630 card.> >> >> >> > your modem setup command should be:> >> >> >> > $ sudo slmodemd -c GERMANY --alsa modem:1> >> >> >> >> >> >> >> > modem:0 and hw:0 are your audio card> >> >> >> > while slmodemd will recognize these devices, they are no dialout> >> >> >> > competent> >> >> >> >> >> >> >>> >> >> >> Thanks for your reply, but no success either:> >> >> >> #sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa modem:1> >> >> >> error: mixer setup: attach hw:1 error: No such device> >> >> >> <818.397304> main: alsa setup: cannot setup mixer: No such device> >> >> >> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM> >> >> cards.pcm.modem> >> >> >> error: alsa setup: cannot open playback device 'modem:1': No such> >> >> file> >> >> >> or directory> >> >> >> error: cannot setup device `modem:1'> >> >> >>> >> >> >> # sudo ./SLMODEMD-1.0.13/slmodemd -d2 -c GERMANY --alsa> >> /dev/slamr0> >> >> >> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM> >> /dev/slamr0> >> >> >> error: alsa setup: cannot open playback device '/dev/slamr0':> >> No such> >> >> >> file or directory> >> >> >> error: cannot setup device `/dev/slamr0'> >> >> >>> >> >> >> Maybe the output of aplay gives you an hint. SiS630 isn't> >> >> mentioned here> >> >> >> as well.> >> >> >> # aplay -l> >> >> >> **** Liste von PLAYBACK Geräten ****> >> >> >> Karte 0: SI7018 [SiS SI7018], Gerät 0: trident_dx_nx [Trident> >> 4DWave]> >> >> >> Untergeordnete Geräte: 32/32> >> >> >> Untergeordnetes Gerät '0: subdevice #0> >> >> >> Untergeordnetes Gerät '1: subdevice #1> >> >> >> Untergeordnetes Gerät '2: subdevice #2> >> >> >> Untergeordnetes Gerät '3: subdevice #3> >> >> >> Untergeordnetes Gerät '4: subdevice #4> >> >> >> Untergeordnetes Gerät '5: subdevice #5> >> >> >> Untergeordnetes Gerät '6: subdevice #6> >> >> >> Untergeordnetes Gerät '7: subdevice #7> >> >> >> Untergeordnetes Gerät '8: subdevice #8> >> >> >> Untergeordnetes Gerät '9: subdevice #9> >> >> >> Untergeordnetes Gerät '10: subdevice #10> >> >> >> Untergeordnetes Gerät '11: subdevice #11> >> >> >> Untergeordnetes Gerät '12: subdevice #12> >> >> >> Untergeordnetes Gerät '13: subdevice #13> >> >> >> Untergeordnetes Gerät '14: subdevice #14> >> >> >> Untergeordnetes Gerät '15: subdevice #15> >> >> >> Untergeordnetes Gerät '16: subdevice #16> >> >> >> Untergeordnetes Gerät '17: subdevice #17> >> >> >> Untergeordnetes Gerät '18: subdevice #18> >> >> >> Untergeordnetes Gerät '19: subdevice #19> >> >> >> Untergeordnetes Gerät '20: subdevice #20> >> >> >> Untergeordnetes Gerät '21: subdevice #21> >> >> >> Untergeordnetes Gerät '22: subdevice #22> >> >> >> Untergeordnetes Gerät '23: subdevice #23> >> >> >> Untergeordnetes Gerät '24: subdevice #24> >> >> >> Untergeordnetes Gerät '25: subdevice #25> >> >> >> Untergeordnetes Gerät '26: subdevice #26> >> >> >> Untergeordnetes Gerät '27: subdevice #27> >> >> >> Untergeordnetes Gerät '28: subdevice #28> >> >> >> Untergeordnetes Gerät '29: subdevice #29> >> >> >> Untergeordnetes Gerät '30: subdevice #30> >> >> >> Untergeordnetes Gerät '31: subdevice #31> >> >> >> Karte 0: SI7018 [SiS SI7018], Gerät 1: trident_dx_nx IEC958> >> [Trident> >> >> >> 4DWave IEC958]> >> >> >> Untergeordnete Geräte: 1/1> >> >> >> Untergeordnetes Gerät '0: subdevice #0> >> >> >>> >> >> >>> >> >> >> Tim.> >> >> >>> >> >> >> > On 5/25/07, Tim Kielmann <t.kielmann@xxxxxxx> wrote:> >> >> >> >> 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?> >> >> >> >> >> >> >>> >> >> Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx> >> >> List Server.> >> >> Do use the following as the email Subject Line:> >> >> SomeName, YourCountry Ubuntu 7.04 kernel> >> 2.6.20-15-generic> >> >> This will alert cogent experts, and distinguish cases in the> >> Archives.> >> >> YourCountry will enable Country Code guidance.> >> >> Occassionally responses are blocked by an Internet Provider mail> >> >> filters.> >> >> So in a day, also check the Archived responses at> >> >> http://www.linmodems.org .> >> >> Local Linux experts can be found through:> >> >> http://www.linux.org/groups/index.html> >> >> -------------------------- System information> >> >> ----------------------------> >> >> CPU=i686, Ubuntu 7.04> >> >> Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2> >> >> (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007> >> >> scanModem update of: 2007_May_11> >> >> The modem symbolic link is /dev/modem -> ttySL0> >> >> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0> >> >>> >> >> ALSAversion 1.0.13> >> >> USB modem not detected by lsusb> >> >>> >> >> Modem or host audio card candidates have firmware information:> >> >>> >> >> PCI slot PCI ID SubsystemID Name> >> >> ---------- --------- --------- --------------> >> >> 00:01.6 1039:7013 Modem: Silicon Integrated> >> >> Systems [SiS] AC'97 Modem Controller> >> >>> >> >> Modem interrupt assignment and sharing:> >> >> 11: 192 XT-PIC-XT eth0> >> >>> >> >> --- Bootup diagnositcs for card in PCI slot 00:01.6 ----> >> >>> >> >> === Finished modem firmware and bootup diagnostics section. ===> >> >> === Next deducing cogent software ===> >> >>> >> >> PCIbus=00:01.6> >> >> 00:01.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem> >> >> Controller (rev a0) (prog-if 00 [Generic])> >> >> Flags: medium devsel, IRQ 11> >> >> I/O ports at 3200 [size=256]> >> >> I/O ports at 3300 [size=128]> >> >> Capabilities: [48] Power Management version 2> >> >>> >> >> A candidate driver could not be identified.> >> >> For candidate modem in PCI bus: 00:01.6> >> >> Class 0703: 1039:7013 Modem: Silicon Integrated Systems [SiS]> >> >> AC'97 Modem Controller> >> >> Primary PCI_id 1039:7013> >> >> Subsystem PCI_id none> >> >> Softmodem codec or Vendor from diagnostics: SIL22, a Smartlink> >> type.> >> >> from Archives:> >> >>> >> >>> >> >> This is a NEW softmodem case! Please send the output ModemData.txt> >> >> to DISCUSS@xxxxxxxxxxxxx , even if further assistance is not needed.> >> >> It will enrich the Archive and help others!> >> >> -------------------------------------------> >> >> Lacking a dsp (digital signal processing) chip, the modem is a> >> software> >> >> intensive or "softmodem" type. Its primary controller manages the> >> >> traffic> >> >> with the CPU. But the software needed is specified in the Subsystem.> >> >> -----------------------------------------> >> >> Support type needed or chipset: slmodemd> >> >>> >> >> An ALSA (Advanced Linux Sound Architecture) modem driver:> >> >> provides Low Level support enabling contact with the modem hardware.> >> >> For all BUT Conexant chip soft modems (using hsfmodem software)> >> >> complementary High Level support is through a Smartlink utility:> >> >> slmodemd> >> >>> >> >> Download from http://linmodems.technion.ac.il/packages/smartlink/> >> >> the package SLMODEMD-1.0.13.tar.gz having a compiled slmodemd.> >> >> Unpack under Linux with:> >> >> $ tar zxf SLMODEMD-1.0.13.tar.gz> >> >> and read instructions therein. But briefly, the modem is setup with> >> >> command:> >> >> sudo slmodemd -c YOUR_COUNTRY --alsa> >> >> reporting dynamic creation of ports:> >> >> /dev/ttySL0 --> /dev/pts/N , with N some number> >> >> Read Smartlink.txt and Modem/YourSystem.txt for follow through> >> >> guidance.> >> >>> >> >>> >> >> The diagnostic outputs for this softmodem section have their raw> >> >> information in> >> >> folders and text files under /proc/asound/ which you can browse. The> >> >> information> >> >> is from files:> >> >> /proc/asound/pcm> >> >> -------------------------------> >> >> 00-01: trident_dx_nx IEC958 : Trident 4DWave IEC958 : playback 1> >> >> 00-00: trident_dx_nx : Trident 4DWave : playback 32 : capture 1> >> >>> >> >> /proc/asound/modules> >> >> -------------------------------> >> >> 0 snd_trident> >> >> /proc/asound/card0/codec97#0/mc97#1-1+regs> >> >> -------------------------------> >> >> 0:7c = 5349 and 0:7e = 4c22> >> >> which were translated from hexadecimal code into: SIL22> >> >>> >> >> /proc/asound/card0/codec97#0/mc97#1-1> >> >> -------------------------------> >> >> Extended modem ID: codec=1 LIN1> >> >>> >> >> and from the command:> >> >> aplay -l | grep -i modem> >> >>> >> >>> >> >> ----------------end Softmodem section --------------> >> >> The modem is supported by the Smartlink slamr driver> >> >> plus the slmodemd helper utility. Read the> >> >> Smartlink.txt and Modem/YourSystem.txt for follow through guidance.> >> >>> >> >> Writing Smartlink.txt> >> >> ============ end Smartlink section =====================> >> >>> >> >> Completed candidate modem analyses.> >> >>> >> >> The base of the UDEV device file system is: /dev/.udev> >> >>> >> >> Versions adequately match for the compiler installed: 4.1.2> >> >> and the compiler used in kernel assembly: 4.1.2> >> >>> >> >> Kernel-header resources needed for compiling are not manifestly> >> ready!> >> >>> >> >> If compiling is necessary packages must be installed, providing:> >> >> linux-headers-2.6.20-15-generic> >> >>> >> >>> >> >> Checking pppd properties:> >> >> -rwsr-xr-- 1 root dip 269224 2007-04-05 05:41 /usr/sbin/pppd> >> >>> >> >> In case of an "error 17" "serial loopback" problem, see:> >> >> http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html> >> >>> >> >> To enable dialout without Root permission do:> >> >> $ su - root (not for Ubuntu)> >> >> sudo chmod a+x /usr/sbin/pppd> >> >> or under Ubuntu related Linuxes> >> >> sudo chmod a+x /usr/sbin/pppd> >> >>> >> >> Checking settings of: /etc/ppp/options> >> >> asyncmap 0> >> >> noauth> >> >> 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> >> >>> >> >>> >> >> Don't worry about the following, it is for the experts> >> >> should trouble shooting be necessary.> >> >> ==========================================================> >> >>> >> >> # start/stop the daemon when the USB modem is connected> >> >> KERNEL=="slusb[0-9]*", GROUP="dialout",> >> >> RUN+="/etc/init.d/sl-modem-daemon"> >> >> Checking for modem support lines:> >> >> --------------------------------------> >> >> /device/modem symbolic link: lrwxrwxrwx 1 root root 6> >> >> 2007-05-21 21:04 /dev/modem -> ttySL0> >> >> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root> >> >> 10 2007-05-21 21:04 /dev/ttySL0 -> /dev/pts/0> >> >> Within /etc/udev/ files:> >> >> /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon> >> >> when the USB modem is connected> >> >> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",> >> >> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"> >> >> /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB> >> >> modem is connected> >> >> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",> >> >> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"> >> >> Within /etc/modprobe.conf files:> >> >> /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2> >> >> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2> >> >> /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to> >> >> blacklist unwanted modem drivers> >> >> /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem> >> >> /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem> >> >> /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe> >> >> --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr;> >> >> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0> >> >> 2>/dev/null && chgrp dialout /dev/slamr0)> >> >> Within any ancient /etc/devfs files:> >> >>> >> >> Within ancient kernel 2.4.n /etc/module.conf files:> >> >>> >> >> --------- end modem support lines -------->
