Italians, Please help SK with any local issues, He is using Open SuSE SK Do$ sudo gedit wvtestDelete the ;and on those lines replace the <xxxx> with your dialout info.Add a line: Carrier Check = noSaveTry dialing out with$ sudo wvdial --config wvtest If there is a failure, look at the suggestions at the wvdial.txtsample provided in the SLMODEM folder. The snd-atiixp-modem driver sometimes seems to die thought still loaded.If this occurs. Just stop slmodemd withCrtl-C Then unload the driver$ sudo modprobe -r snd-atiixp-modemreloadriver$ sudo modprobe snd-atiixp-modemand proceed as before. When all tests OK, Look at the /etc/wvdial.conf SuSE provides.You can copy your functional lines from wvtest into it.Then dialout will work when started by Kinternet or by a simpler$ sudo wvdial MarvS On 8/30/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>> Marvin Stodolsky ha scritto:> Sorry>> Forgot the modem activation with slmodemd>>>>> Please run> # su - root> # lsmod | grep ircomm> # modprobe snd-atiixp-modem> # lsmod | grep modem>> # slmodemd -c ITALY --alsa modem:1>> ciccio:~ # slmodemd -c ITALY --alsa modem:1> SmartLink Soft Modem: version 2.9.11 Feb 15 2007 23:08:19> symbolic link `/dev/ttySL0' -> `/dev/pts/3' created.> modem `modem:1' created. TTY is `/dev/pts/3'> Use `/dev/ttySL0' as modem device, Ctrl+C for termination.>> it seems that something is working now :D> Then on a second consolle:>> Leave running and open a 2nd console for the>>>> # wvdialconf wvtest>> ciccio:~ # wvdialconf wvtest> 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.> Port Scan<*1>: S1 S2 S3> ttyS4<Info>: No such device or address> Port Scan<*1>: S4> ttyS5<Info>: No such device or address> Port Scan<*1>: S5> ttyS6<Info>: No such device or address> Port Scan<*1>: S6> ttyS7<Info>: No such device or address> Port Scan<*1>: S7> WvModem<*1>: Cannot get information for serial port.> ttySL0<*1>: ATQ0 V1 E1 -- OK> ttySL0<*1>: ATQ0 V1 E1 Z -- OK> ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK> ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem> ttySL0<*1>: Speed 4800: AT -- OK> ttySL0<*1>: Speed 9600: AT -- OK> ttySL0<*1>: Speed 19200: AT -- OK> ttySL0<*1>: Speed 38400: AT -- OK> ttySL0<*1>: Speed 57600: AT -- OK> ttySL0<*1>: Speed 115200: AT -- OK> ttySL0<*1>: Speed 230400: AT -- OK> ttySL0<*1>: Speed 460800: AT -- OK> ttySL0<*1>: Max speed is 460800; that should be safe.> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK>> Found a modem on /dev/ttySL0.> Modem configuration written to wvtest.> ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0">> So it seems that it found a modem :D>> And now? Can I plug the cable and try a connection?>> Thanks for your precious support :D> Enrico>> P.S I owe you at least a couple of beers!>>> MarvS>> On 8/30/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>>> Marvin Stodolsky wrote:>>> SK>> Please run> # su - root> # lsmod | grep ircomm> # modprobe snd-atiixp-modem> # lsmod | grep modem> # wvdialconf wvtest> What are the outputs.>>> Hi :D> this is the complete output:>> ciccio:~ # lsmod | grep ircomm> ciccio:~ # modprobe snd-atiixp-modem> ciccio:~ # lsmod | grep modem> snd_atiixp_modem 20744 0> snd_ac97_codec 95776 2 snd_atiixp_modem,snd_atiixp> snd_pcm 87044 4> snd_atiixp_modem,snd_pcm_oss,snd_atiixp,snd_ac97_codec> snd 61444 13> snd_atiixp_modem,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_atiixp,snd_ac97_codec,snd_pcm,snd_timer> snd_page_alloc 14472 3 snd_atiixp_modem,snd_atiixp,snd_pcm> ciccio:~ # wvdialconf wvtest> 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.> Port Scan<*1>: S1 S2 S3> ttyS4<Info>: No such device or address> Port Scan<*1>: S4> ttyS5<Info>: No such device or address> Port Scan<*1>: S5> ttyS6<Info>: No such device or address> Port Scan<*1>: S6> ttyS7<Info>: No such device or address> Port Scan<*1>: S7>>> 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/wvdial/>> If you still have problems, send mail to wvdial-list@xxxxxxxxxxxxx>>>> MarvS>>> Thanks again, Enrico>>> On 8/30/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>>>> Hi, first of all sorry for being this late. I've been out of town till> today :'(>> Marvin Stodolsky wrote:> RE: Use `/dev/ttySL0' as modem device> But wvdialconf abouts at:>>> Port Scan<*1>: ircomm0> ircomm1<Info>: Device or resource busy> Port Scan<*1>: ircomm1> ircomm2<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud.>> before using /dev/ttySL0> ----------> This is actually a wvdialconf bug which I have reported.>> The work around is to block loading of drivers> ircomm-tty.ko and ircomm.ko during bootup.> Attmpting unloading after bootup with:> # modprobe -r ircomm> will fail on many Systems. But you always check with:> # lsmod | grep ircomm>> The modules are not loaded, so maybe this is not the cause.> The modem is still not working and I think I must give up. Unfortunately> this is a real pain because I need it in order to be able to sed faxes. I do> not want to swith to other distros since I think it would be the same,> neither I want to switch back to windows because I like my system :'(>> I hope to find an easy solution one day or another.>> Thanks for your help :(>> Enrico>> P.S. if you feel like helping me some more, than feel free to do so, I will> be happy to do some more testings.>>> To block bootup loading note that your System has:> --------> Within /etc/modprobe.conf files:> /etc/modprobe.conf:# Linux ACP modem (Mwave)> /etc/modprobe.d/blacklist:# ALSA PCI sound/modem modules - should be> configured via yast> /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem> /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem> /etc/modprobe.d/blacklist~:# ALSA PCI sound/modem modules - should be> configured via yast> /etc/modprobe.d/blacklist~:blacklist snd-atiixp-modem> /etc/modprobe.d/blacklist~:blacklist snd-via82xx-modem> ---------> This represents your SuSE install programs guess during the initial> installation, wrong in this case. I do not know how to use YAST for> the correction. But you should be able to use gedit:>> # gedit /etc/modprobe.d/blacklist> to achieve changes too:> /etc/modprobe.conf:# Linux ACP modem (Mwave)> /etc/modprobe.d/blacklist:# ALSA PCI sound/modem modules - should be> configured via yast> /etc/modprobe.d/blacklist:blacklist ircomm> /etc/modprobe.d/blacklist:blacklist ircomm-tty> /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem> /etc/modprobe.d/blacklist~:# ALSA PCI sound/modem modules - should be> configured via yast>> Upon a reboot, ircomm-tty & ircomm will not load> and snd-atiixp-modem will load.> You can then proceed with the modem testing again.>> Once the modem is properly working, it will likely be OK to restore> loading of ircomm-tty & ircomm. Also manual load should work with:> # modprobe ircomm> if you do need infrared functionality.>> For the /etc/wvdial.conf try> [Dialer Defaults]> # Begin comment lines> Modem = /dev/ttySL0> Baud = 57600> Init1 = ATZ> Init2 = ATQ0 V1 E1 X3 S0=0 &C1 &D2> # X3 is sometimes necessary in Italy because of low line voltages.> # It skips the dialtone check. Test with and without> Init3 => Area Code => Phone = IP_number_without_spaces> Username = LoginName> Password = LoginPassword> Ask Password = 0> Dial Command = ATDT> # avoid Stupid Mode if possible> # Stupid Mode = 1> Compuserve = 0> Force Address => Idle Seconds = 300> DialMessage1 => DialMessage2 => ISDN = 0> Auto DNS = 1>> Then try a dialout with Kinternet.>> MarvS>>> On 8/11/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>>> Sorry if I write for the second time in a so short time.> Anyhow, I've re run ./scanModem>> and the output suggested me to do the following>> modprobe -r snd_atiixp_modem> modprobe snd_atiixp_modem>> Then I made again> # slmodemd -c ITALY --alsa modem:1>> and this time the output was the following:>> SmartLink Soft Modem: version 2.9.11 Feb 15 2007 23:08:19> symbolic link `/dev/ttySL0' -> `/dev/pts/4' created.> modem `modem:1' created. TTY is `/dev/pts/4'> Use `/dev/ttySL0' as modem device, Ctrl+C for termination.>> that seems to be a correct output.> Then I made # wvdialconf wvdial.txt> and the output is the following:>> 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.> Port Scan<*1>: S1 S2 S3> ttyS4<Info>: No such device or address> Port Scan<*1>: S4> ttyS5<Info>: No such device or address> Port Scan<*1>: S5> ttyS6<Info>: No such device or address> Port Scan<*1>: S6> ttyS7<Info>: No such device or address> Port Scan<*1>: S7> ircomm0<Info>: Device or resource busy> Port Scan<*1>: ircomm0> ircomm1<Info>: Device or resource busy> Port Scan<*1>: ircomm1> ircomm2<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud.>> Now what should I do?> Thanks a lot again, have a good week end.> Enrico>> Marvin Stodolsky wrote:>>> Would someone help with the SuSE specific issues.>> Erico>> Within the SLMODEMD.gcc4.1/ folder do> # su - root> Then copy> # cp slmodemd /usr/sbin/slmodemd> # chmod +x /usr/sbin/slmodemd> /usr/sbin/ is just one of the folders for COMMANDs>> Then the modem should be activated by:> # slmodemd -c ITALY --alsa modem:1>> A next functional test is> # wvdialconf wvdial.txt> which should report finding the modem.>> SuSE uses Kinternet as a front end to wvdial and writes a file to> /etc/wvdial.conf> which I don´t want to mess up.> This is why I want some SuSE user to guide you too.>> MarvS>>> If successful> On 8/10/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>>>> Marvin Stodolsky wrote:> SK>> Download from> http://linmodems.technion.ac.il/packages/smartlink/> the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. Unpack> under Linux with:> $ tar zxf SLMODEMD.gcc4.1.tar.gz> and read instructions therein. But briefly, the modem is setup with> command:> slmodemd -c ITALY --alsa modem:1> 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.> --------> This should normally suffice.> Write back if your have problems>> MarvS>> Hi>> I've downloaded the file you suggest before deciding to ask for some help.> The fact is that the instructions are not so clear to a newbye like me, and> I was not able to understant wath to do with the file that is available in> that pakage.>> Plus, in the package that you mention I can find something specific for> SuSE (my distro), but again it is not clear what do I have to do.>> Anyhow, thanks for your help.> Enrico>>>> On 8/7/07, Spam Killer <e.fedele@xxxxxxxxxx> wrote:>>> I've run scanModem and it returned this output.>> I've read YourSystem.txt and downloaded SLMODEMD.gcc4.1.gz, but I am not> able to proceed.>> Can you please help me?> I am running an OpenSUSE 10.2 32 bit with 2.6.18.8-0.5-default i686> kernel on my Ferrari 4005 wlmi notebook.> The modem is identified as a ATI Technologies Inc ATI SB400 - AC'97> Modem Controller (rev 02).>> If you want, I may send you the windows drivers, if you think that this> may help.> I know that this is a modem/fax, and by looking at the AGRMDwxp.inf that> comes with the xp drivers, I see that this is an agere modem. The> following is a piece of code taken from the above file:>> ; Windows Modem Setup File> ; Copyright (c) 1993-2005 Microsoft Corporation> ; Manufacturer: Agere Systems> ; Last Edited 08/28/2005> ; System Audio lsy>> [Version]> CatalogFile=AGRMDwxp.cat> Signature="$CHICAGO$"> Class=Modem> ClassGUID={4D36E96D-E325-11CE-BFC1-08002BE10318}> Provider=%ModemProvider%> DriverVer=08/24/2005,2.1.59>> [DestinationDirs]> DefaultDestDir=11> Drv.Copy=12> ;Sys.Copy=11> Win.Copy=10> ;CoInstallers.Copy=11>> [Manufacturer]> %ModemProvider%=Agere_Modems>> [Agere_Modems]>> %ATI_AMR.Modem% = ATI_AMR_SA.Modem,> PCI\VEN_1002&DEV_4378&SUBSYS_007E1025>> [ControlFlags]>> ExcludeFromSelect = PCI\VEN_1002&DEV_4378&SUBSYS_007E1025>> [SM_Device_LowerFilter]> HKR,,LowerFilters,0x00010000,%ModemProvider%%ShortProductName%> HKR,,"WakeOnRing",0x00010001,1>> [HdAudSecurity.AddReg]> ; FILE_DEVICE_MODEM> HKR,,DeviceType,0x10001,0x0000002B> ; SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RWX_RES_RWX> HKR,,Security,,"D:P(A;;GA;;;SY)(A;;GRGWGX;;;BA)(A;;GRGWGX;;;WD)(A;;GRGWGX;;;RC)">> [SM_Device_Service_Inst]> DisplayName = %FullProductName%> ServiceType = 1> StartType = 3> ErrorControl = 1> ServiceBinary = %12%\AGRSM.sys>> [Strings]> ATI_AMR.Modem="Agere Systems AC'97 Modem"> FullCompanyName="Agere Systems"> FullProductName="Agere Systems Soft Modem"> ModemProvider="Agere"> ShortProductName="SoftModem"> Disk1Name="Agere Systems Soft Modem Installation Disk ">>> Thanks for your help.>> Enrico>> Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List> Server.> Do use the following as the email Subject Line:> SomeName, YourCountry> Welcome to openSUSE 10.2 (i586) - Kernel kernel 2.6.18.8-0.5-default> 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,> Welcome to openSUSE 10.2 (i586) - Kernel> Linux version 2.6.18.8-0.5-default (geeko@buildhost) (gcc version 4.1.2> 20061115 (prerelease) (SUSE Linux)) #1 SMP Fri Jun 22 12:17:53 UTC 2007> scanModem update of: 2007_August_04> The modem symbolic link is /dev/modem -> /dev/ttyACM0>> ALSAversion 1.0.14> USB modem not detected by lsusb>> Modem or host audio card candidates have firmware information:>> PCI slot PCI ID SubsystemID Name> ---------- --------- --------- --------------> 00:14.6 1002:4378 1025:007e Modem: ATI Technologies Inc ATI SB400 - AC'97> Modem Controller>> Modem interrupt assignment and sharing:> 209: 361743 IO-APIC-level ATI IXP, ATI IXP Modem>> --- Bootup diagnostics for card in PCI slot 00:14.6 ----> ACPI: PCI Interrupt 0000:00:14.6[B] -> GSI 17 (level, low) -> IRQ 209> ACPI: PCI interrupt for device 0000:00:14.6 disabled> PCI: Enabling device 0000:00:14.6 (0010 -> 0012)> ACPI: PCI Interrupt 0000:00:14.6[B] -> GSI 17 (level, low) -> IRQ 209>> The PCI slot 00:14.6 of the modem card may be disabled early in> a bootup process, but then enabled later. If modem drivers load> but the modem is not responsive, read Bootup.txt about possible fixes.> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx> if help is needed.>>> === Finished modem firmware and bootup diagnostics section. ===> === Next deducing cogent software ===>> CodecModemFile not found> A candidate driver could not be identified.> For candidate modem in PCI bus: 00:14.6> Class 0703: 1002:4378 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem> Controller> Primary PCI_id 1002:4378> Subsystem PCI_id 1025:007e> Softmodem codec or Vendor from diagnostics: SIL2f> from Archives: SIL2f>>> 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.gcc4.1.tar.gz having a compiled slmodemd. Unpack under> Linux with:> $ tar zxf SLMODEMD.gcc4.1.tar.gz> and read instructions therein. But briefly, the modem is setup with> command:> 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-00: ATI IXP AC97 : ATI IXP AC97 : playback 1 : capture 1> 01-00: ATI IXP MC97 : ATI IXP MC97 : playback 1 : capture 1>> /proc/asound/modules> -------------------------------> 0 snd_atiixp> 1 snd_atiixp_modem> /proc/asound/card1/codec97#0/mc97#1-1+regs> -------------------------------> 0:7c = 5349 and 0:7e = 4c2f> which were translated from hexadecimal code into: SIL2f>> /proc/asound/card1/codec97#0/mc97#1-1> -------------------------------> Extended modem ID: codec=1 LIN1>> and from the command:> aplay -l | grep -i modem> card 1: Modem [ATI IXP Modem], device 0: ATI IXP MC97 [ATI IXP MC97]>> ----------------end Softmodem section --------------> 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>>>> Compiling resources appear complete:> make utility - /usr/bin/make> Compiler version 4.1> kernel_headers base folder /lib/modules/2.6.18.8-0.5-default/build>>> If a driver compilation files with message including some lack of some> FileName.h (stdio.h for example.> Some additional kernel-header files need installation to /usr/include.> For Debian/Ubuntu related distributions, run the following command to> display the needed package list:> $ sudo apt-get -s install linux-kernel-devel> While some of the files may be on the install CD, others may have to be> found through http://packages.ubuntu.com>> For Ubunut feisty, additional packages required were:> build-essential curl debhelper dpkg-dev g++ g++-4.1 gettext git-core gitk> html2text intltool-debian kernel-package kernel-wedge libc6-dev> libcurl3-gnutls libdigest-sha1-perl liberror-perl libstdc++6-4.1-dev> linux-libc-dev po-debconf rcs tcl8.4 tk8.4>>> Checking pppd properties:> -rwxr-xr-x 1 root dialout 295488 25 nov 2006 /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)> chmod a+x /usr/sbin/pppd> or under Ubuntu related Linuxes> chmod a+x /usr/sbin/pppd>> Checking settings of: /etc/ppp/options> noipdefault> noauth> crtscts> lock> modem> asyncmap 0> nodetach> lcp-echo-interval 30> lcp-echo-failure 4> lcp-max-configure 60> lcp-restart 2> idle 600> noipx> file /etc/ppp/filters>> 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>> Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth1> Which can interfere with Browser naviagation.>> Don't worry about the following, it is for the experts> should trouble shooting be necessary.> ==========================================================>> Checking for modem support lines:> --------------------------------------> /device/modem symbolic link: lrwxrwxrwx 1 root root 12 7 ago 12:37> /dev/modem -> /dev/ttyACM0> slmodemd created symbolic link /dev/ttySL0:> Within /etc/udev/ files:> /etc/udev/rules.d/31-network.rules:SUBSYSTEM=="net",> ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*",> GOTO="skip_ifup"> /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/%k",> GROUP="uucp"> Within /etc/modprobe.conf files:> /etc/modprobe.conf:# Linux ACP modem (Mwave)> /etc/modprobe.d/blacklist:# ALSA PCI sound/modem modules - should be> configured via yast> /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem> /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem> /etc/modprobe.d/blacklist~:# ALSA PCI sound/modem modules - should be> configured via yast> /etc/modprobe.d/blacklist~:blacklist snd-atiixp-modem> /etc/modprobe.d/blacklist~:blacklist snd-via82xx-modem> Within any ancient /etc/devfs files:>> Within ancient kernel 2.4.n /etc/module.conf files:>> --------- end modem support lines -------->>>>>>>>>>>>>>>>>
