Folks, Have any of you install Ubuntu Hardy yet. If so please return the outputs of $ aplay --version $ find /lib/modules/`uname -r`/ -name snd-hda-intel.ko $ find /lib/modules/`uname -r`/ -name snd-via82xx-modem.ko ======== Larry, Technically you have done OK, with the residual problem: ----------------------------------------- In the last three days of dialing I was successsful twice to get connected, but now I am back to a non working modem. This advice was effective with an older kernel 2.6.20 era ------------------------------------- > Modem support under STAC92xx audio card hosts may require upgrade > of snd-hda-intel + its dependent drivers to ALSA version 1.0.16. > The following modem only worked after the upgrade to 1.0.16 from 1.0.14 ------------------------------------- however it fails under your Ubuntu Gutsy. The normal installation position for ALSA modem drivers is in folder: /lib/modules/2.6.22-14-generic/kernel/sound/pci/ BUT Ubuntu has done some modes of the /lib/modules/ structure including: ls /lib/modules/2.6.22-14-generic/updates/ snd-hda-codec.ko snd-hda-intel.ko Thus if you want to do the upgrade to ALSA 1.0.16 from 1.0.14 if will require some manual shifting around of the drivers afterward. The general instruction for such an upgrade are at: http://linmodems.technion.ac.il/archive-seventh/msg00282.html The alternative is to use the maturing Hardy release,' But first let's get some feedback from those who have it installed. MarvS On Tue, Apr 22, 2008 at 9:50 PM, <lkraemer@xxxxxxxxxx> wrote: > > > I am requesting help to get Ubuntu Ver 7.10 working with my internal modem. > I have the modem drivers installed, wvdial configured, ppp configured, but > the modem still will not connect either with wvdial or ppp. What am I missing? > > Ubuntu 7.10 - Motorola SM56 Speakerphone Modem installed in Gateway MT6840 Laptop > as per Windows XP Control Panel. > > STEPS I have done so far: > > 1. Download scanModem, and execute it to find the modems information. > > NOTE: Always use the most recent update of scanModem accessed ONLY at > http://linmodems.technion.ac.il/packages/scanModem.gz > > > 2. Review document /modem/ModemData.txt ..... as follows: > > Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, > as HTML can contain viruses. Use as the email Subject Line: > YourName, YourCountry kernel 2.6.22-14-generic > With this Subject Line cogent experts will be alerted, and useful case names left in the Archive. > YourCountry will enable Country specific guidance. Your contry's local Linux experts > can be found through: http://www.linux.org/groups/index.html. > They will know your Country's modem code, which may be essential for dialup service. > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) > (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12 07:42:25 UTC 2008 scanModem update of: 2008_04_16 > > There are no blacklisted modem drivers in /etc/modprobe* files > USB modem not detected by lsusb > > For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:27d8 107b:0366 Audio device: Intel Corporation 82801G > > Modem interrupt assignment and sharing: > 21: 752 0 IO-APIC-fasteoi HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 14.532000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21 > [ 14.532000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > > > ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== > The ALSA packages provide audio support and also drivers for some modems. > ALSA diagnostics are written during bootup to /proc/asound/ folders. > PCI slot 00:1b.0 has a High Definition Audio Card > > The ALSA verion is 1.0.14 > The modem cards detected by "aplay -l" are: > card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem] > > The /proc/asound/pcm file reports: > ----------------------- > 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 > 00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 2 > > about /proc/asound/cards: > ------------------------ > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xd8240000 irq 21 > > Modem support under STAC92xx audio card hosts may require upgrade > of snd-hda-intel + its dependent drivers to ALSA version 1.0.16. > The following modem only worked after the upgrade from to 1.0.16 from 1.0.14 > PCI ID SubsystemID Name > --------- --------- -------------- > 8086:27d8 107b:0366 Audio device: Intel Corporation 82801G > with ALSA diagnostics > 00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 2 > 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 > Codec: Motorola Si3054 > for 107b:0366 hosted modem chip: 0x10573057 > > For a standard Ubuntu system needed to support the driver compilation were > > The modem codec file for the the HDA card is: /proc/asound/card0/codec#1 > -------------------------------------------------------- > Codec: Motorola Si3054 > Address: 1 > Vendor Id: 0x10573057 > Subsystem Id: 0x10001 > Revision Id: 0x100100 > > The audio card hosts a softmodem chip: 0x10573057 > > The softmodem chip 0x10573057 is in principle supported by the COMM support of slmodemd > and the joint snd-hda-intel audio+modem driver, begun with ALSA version 1.0.13. > For HDA cards with ALC883 chips, an upgrade to ALSA verions 1.0.15 way be necessary. > Instructions for upgrading snd-hda-intel and its dependent driver set are at: > http://linmodems.technion.ac.il/archive-seventh/msg00282.html > > === Finished firmware and bootup diagnostics, next deducing cogent software. === > > Predictive diagnostics for card in bus 00:1b.0: > Modem chipset detected on > CLASS="Class 0403: 8086:27d8" > NAME="Audio device: Intel Corporation 82801G " > PCIDEV=8086:27d8 > SUBSYS=107b:0366 > IRQ=21 > HDA=8086:27d8 > SOFT=8086:27d8.HDA > CodecArchived=10573057 > CHIP=0x10573057 > IDENT=slmodemd > SLMODEMD_DEVICE=hw:0,6 > Driver=snd-hda-intel > > For candidate modem in: 00:1b.0 > Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > Primary PCI_id 8086:27d8 > Subsystem PCI_id 107b:0366 > Softmodem codec or chipset from diagnostics: 0x10573057 > from Archives: 0x10573057 > The HDA card softmodem chip is 0x10573057 > > > Support type needed or chipset: slmodemd supporting the snd-hda-intel audio+modem driver > > An ALSA (Advanced Linux Sound Architecture) modem driver: snd-hda-intel > 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: > sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6 > 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. > > ----------------end Softmodem section -------------- > > Writing Intel.txt > 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.3 > and the compiler used in kernel assembly: 4.1.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.22-14-generic/build > > However some compilations and executable functions may need additional files, > in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ . > For martian_modem, additional required packages are libc6-dev (and for Debian/Ubuntu, linux-libc-dev). > The also required headers of package libc6 are commonly installed by default. > > > > If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then > Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev > and any of its dependents, under Ubuntu linux-libc-dev > > If an alternate ethernet connection is available, > $ apt-get update > $ apt-get -s install linux-kernel-devel > will install needed package > For Debian/Ubuntu related distributions, run the following command to display the needed package list: > > Otherwise packages have to be found through http://packages.ubuntu.com > Once downloaded and transferred into a Linux partition, > they can be installed alltogether with: > $ sudo dpkg -i *.deb > > > Checking pppd properties: > -rwsr-xr-- 1 root dip 269256 2007-10-04 12:57 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://linmodems.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 > > Read Modem/YourSystem.txt concerning other COMM channels: eth0 > 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: > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > > 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 > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > > > 3.Downloaded slmodemd & installed modem driver > > http://linmodems.technion.ac.il/packages/smartlink/ > the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. > Open a Terminal window > Unpack under Linux with: > gzip -d scanModem.gz > chmod 777 scanModem > sudo ./scanModem > > > tar zxf SLMODEMD.gcc4.1.tar.gz > > cd SLMODEMD.gcc4.1 > sudo chmod a+x slmodemd > sudo cp slmodemd /usr/sbin > > Note: > find /usr -name slmodemd > should ONLY report the newly copied slmodemd > Should another older slmodemd copy be found rename it slmodem.old > > Locate the ALSA Modem driver from the choices below: > Compatible primary modem controllers currently are : > PCI ID modem controller name/source low_level_driver > ======= =============== ======= ================= > 1002:434d ATI snd-atiixp-modem > 1002:4379 ATI " > 1106:3068 VIA snd-via82xx-modem > 10b9:5451 ALI 5451 audio with modem snd-ali5451 > 8086:???? many Intel controllers snd-intel8x0m > 10de:00d9 Nvidia Corp " > 1039:7013 SIS 630 " > Others? " > Under each of these controllers, may different Subsystems can be hosted, > and having a variety of modem codecs, with most meeting a mc97 standard. > All are potentially supported by slmodemd with one exceptional family. > > First insert an ALSA modem driver. (Format:# modprobe low_level_driver) > > sudo modprobe snd-hda-intel > > sudo lsmod ........shows snd_hda_intel as being installed....... > > 4. ##Open Terminal Window and start slmodemd, then keep it running > and minimize terminal window. > > larry@LK-MT6840:~$ sudo slmodemd -c USA --alsa hw:0,6 > [sudo] password for larry: > > 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. > > > 5. Test wvdial > larry@LK-MT6840:~$ sudo wvdialconf wvtest > Editing `wvtest'. > > Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 S1 S2 S3 > 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. > wvtest<Warn>: Can't open 'wvtest' for reading: No such file or directory > wvtest<Warn>: ...starting with blank configuration. > Modem configuration written to wvtest. > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > > > > 6. #configure wvdial in another Terminal window. > > ##Wvdial.conf follows: > > [Dialer defaults] > # Lines begining with # are comments. > # wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc > # > # Redhat/Fedora have an Internet Connection Wizard in the popup menus > # ICW will write a two part /etc/wvdial.conf supporting multiple modem usage. > # > #Modem = ModemPort > # typically a symbolic link to the true port is used, /dev/modem or /dev/ttyS* > # wvdialconf will test all port names /dev/modem and /dev/ttyS* > Modem = /dev/ttySL0 > > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > # Changed &C1 to &C0 to not use Carrier Detect > # Lack of dialtone acquisition can be due to low line voltage, > # a common problem in Italy. > # Try inserting a "dial without waiting": X3 > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > # In case of connection instabilities, specify a lower frequency: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 > # a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols: > # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ISDN = 0 > Modem Type = Analog Modem > #Dial Command = ATDP > ## replaces Touch Tone prefix ATDT to Dialout_phone_number, with older Pulse prefix ATDP > Baud = 115200 > Phone = 8374162 > # if going through a switch board, a perhaps necessary pause can produced with a comma: > # Phone = 1,Dialout_phone_number > Username = mylogin@xxxxxxxxxx > # if Internet Provider is MSN.net, use under Linux: MSN/LoginName > Password = mypassword > > # the following lines is NEEDED only for usage with slmodemd or martian_helper > > Carrier check = no > > # Kinternet appears to add it automatically. > > ## If CONNECT is achieved but browsing fails, try activating the following line > > Auto DNS = yes > > ## To make a logfile wvdial.out > # wvdial 2>&1 | tee wvdial.out > # # For some Internet providers, the following line is necessary > > Stupid Mode = yes > > ## for other wvdial options, do "man wvdial" or see the documentation in > ## /usr/share/doc/wvdial/ > > # to dial an alternate provide use "wvdial 2nd" which will preferentially read: > # [Dialer 2nd] > # Phone = 2nd_phone_number > # Username = 2nd_LoginName > # Password = 2nd_PassWord > > ## End wvdial config file > > > 7. #Open a Terminal window and configure ppp, then SAVE the file and EXIT: > sudo pppconfig > > 8. Verify PPP & wvdial files are correct for: > > /etc/passwd > /etc/ppp/chap-secrets > /etc/ppp/pap-secrets > /etc/ppp/peers/provider > /ect/wvdial.conf > > 9. Dial out with wvdial > > # If you have accessed the Internet via Ethernet the following > # Also shutdown ethernet function before dialing out: > # $ ifconfig > # If an eth0 block is shown > # $ sudo ifconfig eth0 down > # check with > # $ ifconfig > # When you are done with Dial-up > # sudo ifconfig eth0 up > # I have tried both ways and it doesn't appear to make any difference! > #Open Terminal Window and start Wvdial > > > larry@LK-MT6840:/etc$ sudo wvdial --config /etc/wvdial.conf > 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 &C0 &D2 +FCLASS=0 > WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C0 &D2 +FCLASS=0 > WvDial Modem<*1>: OK > WvDial<*1>: Modem initialized. > WvDial<*1>: Sending: ATDT8374162 > WvDial<*1>: Waiting for carrier. > WvDial Modem<*1>: ATDT8374162 > WvDial<Warn>: Timed out while dialing. Trying again. > WvDial<*1>: Sending: ATDT8374162 > WvDial<*1>: Waiting for carrier. > WvDial Modem<*1>: NO CARRIER > WvDial Modem<*1>: ATDT8374162 > WvDial<Warn>: No Carrier! Trying again. > WvDial<*1>: Sending: ATDT8374162 > WvDial<*1>: Waiting for carrier. > WvDial Modem<*1>: NO CARRIER > WvDial Modem<*1>: ATDT8374162 > WvDial<Warn>: No Carrier! Trying again. > > > I have tried Dialing out with PPP and also WVDIAL and both have the same problem > of not detecting a Carrier. Both programs never detect the Carrier. > > Modem will go OFFHOOK, Dial out using TONE, and never detect a Carrier even though > copper.net is transmitting. I have listened on an extension phone and copper.net > keeps trying to communicate with my moden that appears to go DEAF! System works > fine with Win XP and same modem and XP Drivers. What am I missing? Could there be > a timing issue? > > I have tried Gnome-ppp and it doesn't recognize the /dev/ttySL0 port, even though > slmodemd is running in a terminal window. I haven't downloaded smodemd with Synaptics. > > In the last three days of dialing I was successsful twice to get connected, but > now I am back to a non working modem. > > Any suggestions? > > Thanks > > LKraemer > > > > >
