Jaysen the slmodemd activation must be maintained while you open a 2nd console to: $ sudo wvdial after you have done the wvdial.conf edit GnomePPP is just a front end to wvdial. So use wvdial directly until all is working MarvS On Thu, Jul 23, 2009 at 11:01 PM, Jaysen Johnson<jaysen@xxxxxxxxxxxx> wrote: > Just tried that, no go. Can not detect modem. > > Marvin Stodolsky wrote: >> >> You have to run the gnomeppp setup, including addition of a line >> Carrier Check = no >> >> OR >> $ sudo gedit /etc/wvdial.conf >> putting in your personal info while deleting symbols < > ; >> and adding a line >> Carrier Check = no >> >> Then dialout with: >> $ sudo wvdial >> >> MarvS >> >> On Thu, Jul 23, 2009 at 12:37 AM, Jaysen Johnson<jaysen@xxxxxxxxxxxx> >> wrote: >>> >>> Marvin, >>> >>> Ok, I tried that and this is what I get >>> >>> jaysen@jaysens-laptop:~$ sudo wvdialconf >>> [sudo] password for jaysen: >>> Editing `/etc/wvdial.conf'. >>> >>> 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. >>> Modem configuration written to /etc/wvdial.conf. >>> ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" >>> >>> >>> So it looks like it found it. Then when I try to dial out with >>> gnome-ppp. >>> This is what happens. Note, I attempted to dial out with and without >>> SLMODEMD running with the same results. >>> >>> jaysen@jaysens-laptop:~$ sudo gnome-ppp >>> WVCONF: /root/.wvdial.conf >>> GNOME PPP: STDOUT: Editing `/dev/null'. >>> GNOME PPP: STDERR: Modem Port Scan<*1>: S0 S1 S2 S3 >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDERR: WvModem<*1>: Cannot get information for serial port. >>> GNOME PPP: STDOUT: Scanning your serial ports for a modem. >>> GNOME PPP: STDERR: ttySL0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next >>> try: 9600 baud >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDERR: ttySL0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next >>> try: 115200 baud >>> GNOME PPP: STDERR: ttySL0<*1>: ATQ0 V1 E1 -- and failed too at 115200, >>> giving up. >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDOUT: Sorry, no modem was detected! Is it in use by another >>> program? >>> GNOME PPP: STDOUT: Did you configure it properly with setserial? >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDOUT: Please read the FAQ at http://open.nit.ca/wiki/?WvDial >>> GNOME PPP: STDOUT: >>> GNOME PPP: STDOUT: If you still have problems, send mail to >>> <wvdial-list@xxxxxxxxxxxx>. >>> >>> >>> Jaysen >>> >>> >>> >>> >>> >>> >>> Marvin Stodolsky wrote: >>>> >>>> Jaysen >>>> >>>> wvdialconf must be run with admin/root permission with slmodemd left >>>> running. So after the modem activation open a 2nd console and: >>>> $ sudo wvdialconf >>>> >>>> MarvS >>>> >>>> On Wed, Jul 22, 2009 at 3:50 PM, Jaysen Johnson<jaysen@xxxxxxxxxxxx> >>>> wrote: >>>>> >>>>> Marvin, >>>>> >>>>> I am still having trouble with the modem. When I run sudo ./setup >>>>> This >>>>> is >>>>> what I get. >>>>> >>>>> >>>>> >>>>> jaysen@jaysens-laptop:~$ cd Downloads/ >>>>> jaysen@jaysens-laptop:~/Downloads$ cd SLMODEMD.gcc4.3/ >>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ sudo ./setup >>>>> [sudo] password for jaysen: >>>>> >>>>> ./setup: 4: slmodemd: not found >>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking >>>>> for >>>>> version 2.9.11 >>>>> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 >>>>> Version verified: 2.9.11 >>>>> >>>>> With root permission, the typical activation command is: >>>>> for modems hosted on High Definition Audio cards >>>>> slmodemd -c USA --alsa hw:0,6 >>>>> for modems of the AC'97 family >>>>> slmodemd -c USA --alsa modem:1 >>>>> for modems on ALI5451 sound cards >>>>> slmodemd -c USA --alsa hw:0,1 >>>>> for Smartlink chipset PCI card modems: >>>>> slmodemd -c USA /dev/slamr0 >>>>> for Smartlink chipset USB modems >>>>> slmodemd -c USA /dev/slusb0 >>>>> >>>>> If not in the USA, replace USA with a country from the output of: >>>>> slmodemd --countrylist >>>>> For other slmodemd parameters, query with: >>>>> slmodemd --help >>>>> >>>>> Report any problems to discuss@xxxxxxxxxxxxx >>>>> >>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ >>>>> >>>>> >>>>> Then when I run sudo slmodemd -c USA --alsa hw:0,6 I get this. >>>>> >>>>> >>>>> >>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ sudo slmodemd -c USA >>>>> --alsa hw:0,6 >>>>> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 >>>>> 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. >>>>> >>>>> >>>>> Finally when I run sudo wvdialconf, I get this. >>>>> >>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ sudo wvdialconf >>>>> Editing `/etc/wvdial.conf'. >>>>> >>>>> Scanning your serial ports for a modem. >>>>> >>>>> Modem Port Scan<*1>: S0 S1 S2 S3 >>>>> >>>>> >>>>> 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/wiki/?WvDial >>>>> >>>>> If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. >>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ >>>>> >>>>> >>>>> Still confused here. Last night it acted like the modem was detected. >>>>> gnome-ppp even detected it but now it can't find it. I don't know what >>>>> is >>>>> going on. Can you help? >>>>> >>>>> Jaysen >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Marvin Stodolsky wrote: >>>>>> >>>>>> Jaysen, >>>>>> >>>>>> The Makefile stuff refers to the original slmodem software set, which >>>>>> I used to compile the slmodemd you just installed. >>>>>> So just ignore it as already done. >>>>>> >>>>>>>>> PCI slot 00:1b.0 has a High Definition Audio Card >>>>>>>>> The drivers are in the kernel modules tree at: >>>>>>>>> >>>>>>>>> /lib/modules/2.6.28-13-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>>>>>>>> >>>>>>>>> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>>>>>>>> The modem codec file for the HDA card is: >>>>>>>>> /proc/asound/card0/codec#1 >>>>>>>>> -------------------------------------------------------- >>>>>>>>> Codec: Motorola Si3054 >>>>>>>>> Address: 1 >>>>>>>>> Vendor Id: 0x10573055 >>>>>> >>>>>> Your audio + modem driver is the snd-hda-intel.ko automatically >>>>>> installed in support of the High Definition Audio Card >>>>>> whose Subsystem hosts the Motorola Si3054 0x10573055 modem chip >>>>>> Such chips do little more then specify which software should be used >>>>>> under Microsoft, which would be a Motorola software package >>>>>> instructing the CPU what to do. >>>>>> >>>>>> Under Linux there is no Motorola software, but instead the Smart >>>>>> slmodemd utility (not a driver) substitutes. >>>>>> >>>>>> The >>>>>> $ sudo slmodemd -c USA --alsa hw:0,6 >>>>>>> >>>>>>> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 >>>>>>> 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. >>>>>> >>>>>> did effectively activate the modem. The Ubuntu sl-modem-daemon >>>>>> package does the same thing, additionally running upon bootup the: >>>>>> slmodemd -c USA --alsa hw:0,6 >>>>>> You don't need the sl-modem-source package, as it is not for HDA modem >>>>>> type hardware >>>>>> >>>>>> With the modem activated, you should be able to open a console and >>>>>> further test the modem. >>>>>> But first do while online >>>>>> $ sudo apt-get install wvdial >>>>>> >>>>>> When done >>>>>> $ sudo wvdialconf >>>>>> should find the modem >>>>>> >>>>>> Read the wvdial.txt sample and >>>>>> $ sudo gedit /etc/wvdial.conf >>>>>> to edit in your dialout info. >>>>>> >>>>>> They shut down ethernet/LAN/wireless or they will block new DNS for >>>>>> the >>>>>> modem. >>>>>> THen try a dialout with >>>>>> $ sudo wvdial >>>>>> >>>>>> Please write to the List, not me directly as I am ony online in the >>>>>> evening. >>>>>> >>>>>> MarvS >>>>>> >>>>>> >>>>>> On Mon, Jul 20, 2009 at 10:15 PM, Jaysen Johnson<jaysen@xxxxxxxxxxxx> >>>>>> wrote: >>>>>>> >>>>>>> Hi Marvin, >>>>>>> >>>>>>> I am very confused. I downloaded the package, extracted it and ran >>>>>>> the >>>>>>> sudo >>>>>>> ./setup Then I read the README file which tells me about a MAKEFILE >>>>>>> that >>>>>>> I >>>>>>> need to review and edit if necessary but no MAKEFILE exists in the >>>>>>> package. >>>>>>> ??? >>>>>>> >>>>>>> when I run sudo slmodemd -c USA --alsa hw:0,6 I get the following >>>>>>> output >>>>>>> below. >>>>>>> >>>>>>> >>>>>>> jaysen@jaysens-laptop:~/Downloads/SLMODEMD.gcc4.3$ sudo slmodemd -c >>>>>>> USA >>>>>>> --alsa hw:0,6 >>>>>>> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 >>>>>>> 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. >>>>>>> >>>>>>> Ubuntu 9.04 has an Softmodem driver that i can install from the >>>>>>> restricted >>>>>>> drivers manager which basically installed the slmodemd application. >>>>>>> How >>>>>>> is >>>>>>> this method different? I really am stuck here. >>>>>>> >>>>>>> >>>>>>> Jaysen >>>>>>> >>>>>>> >>>>>>> >>>>>>> Marvin Stodolsky wrote: >>>>>>>> >>>>>>>> Jaysen >>>>>>>> >>>>>>>> Try: >>>>>>>> Download from http://linmodems.technion.ac.il/packages/smartlink/ >>>>>>>> the package SLMODEMD.gcc4.3.tar.gz having a compiled slmodemd. >>>>>>>> Unpack >>>>>>>> under Linux with: >>>>>>>> $ tar zxf SLMODEMD.gcc4.3.tar.gz >>>>>>>> and read instructions therein. But briefly, the modem is setup with >>>>>>>> command: >>>>>>>> sudo slmodemd -c USA --alsa hw:0,6 >>>>>>>> reporting dynamic creation of ports: >>>>>>>> /dev/ttySL0 --> /dev/pts/N , with N some number >>>>>>>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow >>>>>>>> through guidance. >>>>>>>> >>>>>>>> Within the SLMODEMD.gcc4.3 folder, run >>>>>>>> $ sudo ./setup >>>>>>>> >>>>>>>> which will run elementary tests and output instructions. This "sudo >>>>>>>> ./setup" does not have to be repeated again. >>>>>>>> Read the instructions in the SLMODEMD.gcc4.3/ folder for details. >>>>>>>> Info us in some detail at which step you may run into trouble. >>>>>>>> >>>>>>>> MarvS >>>>>>>> scanmodem maintainer >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jul 20, 2009 at 9:02 PM, Jaysen Johnson<jaysen@xxxxxxxxxxxx> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I am trying to configure a SmartLink modem under Ubuntu 9.04 Jaunty >>>>>>>>> Jackalope 64Bit. I am having a hard time getting it to work. I am >>>>>>>>> in >>>>>>>>> the >>>>>>>>> USA and sending my ModemData.txt file. >>>>>>>>> >>>>>>>>> If you need more information to help me. Please let me know. >>>>>>>>> >>>>>>>>> Thank You, >>>>>>>>> >>>>>>>>> Jaysen >>>>>>>>> >>>>>>>>> >>>>>>>>> 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.28-13-generic >>>>>>>>> With this Subject Line cogent experts will be alerted, and useful >>>>>>>>> case >>>>>>>>> names left in the Archive. >>>>>>>>> YourCountry will enable Country specific guidance. Linux experts >>>>>>>>> in >>>>>>>>> YourCountry >>>>>>>>> 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=x86_64, >>>>>>>>> Linux version 2.6.28-13-generic (buildd@yellow) (gcc version 4.3.3 >>>>>>>>> (Ubuntu >>>>>>>>> 4.3.3-5ubuntu4) ) #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 >>>>>>>>> scanModem update of: 2009_07_17 >>>>>>>>> The modem symbolic link is /dev/modem -> ttySL0 >>>>>>>>> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2 >>>>>>>>> >>>>>>>>> Some modem drivers can only be used in 32 bit modem on x86_64 >>>>>>>>> systems, >>>>>>>>> while some others are competent on x86_64 Systems. Cases are: >>>>>>>>> 1) >>>>>>>>> >>>>>>>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html >>>>>>>>> for the snd-hda-intel audio+modem driver. Also applicable to AC97 >>>>>>>>> modem >>>>>>>>> controllers. >>>>>>>>> In both cases, 32 bit libraries must be installed to support the >>>>>>>>> slmodemd >>>>>>>>> helper having a precompiled 32 bit component. >>>>>>>>> 2) For USB modems using the slusb.ko driver. 32 bit libraries must >>>>>>>>> be >>>>>>>>> installed to support the slmodemd helper having a precompiled 32 >>>>>>>>> bit >>>>>>>>> component >>>>>>>>> 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes >>>>>>>>> are >>>>>>>>> x86_64 competent. >>>>>>>>> >>>>>>>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>>>>>>> Potentially useful modem drivers now loaded are: >>>>>>>>> snd_hda_intel >>>>>>>>> >>>>>>>>> Attached USB devices are: >>>>>>>>> ID 04f2:b018 Chicony Electronics Co., Ltd Video Device >>>>>>>>> ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth >>>>>>>>> If a cellphone is not detected, see >>>>>>>>> http://ubuntuforums.org/archive/index.php/t-878554.html >>>>>>>>> A sample report is: >>>>>>>>> >>>>>>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html >>>>>>>>> >>>>>>>>> If a USB modem or cellphone is attached and was not detected, >>>>>>>>> please >>>>>>>>> provide available information in your request to >>>>>>>>> discuss@xxxxxxxxxxxxx >>>>>>>>> >>>>>>>>> For candidate card in slot 00:1b.0, firmware information and bootup >>>>>>>>> diagnostics are: >>>>>>>>> PCI slot PCI ID SubsystemID Name >>>>>>>>> ---------- --------- --------- -------------- >>>>>>>>> 00:1b.0 8086:284b 14c0:0025 Audio device: Intel >>>>>>>>> Corporation 82801H >>>>>>>>> >>>>>>>>> Modem interrupt assignment and sharing: >>>>>>>>> 20: 1346 1349 IO-APIC-fasteoi HDA Intel >>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>>>>>>>> [ 0.549224] pci 0000:00:1b.0: reg 10 64bit mmio: >>>>>>>>> [0xf8400000-0xf8403fff] >>>>>>>>> [ 0.549266] pci 0000:00:1b.0: PME# supported from D0 D3hot >>>>>>>>> D3cold >>>>>>>>> [ 0.549271] pci 0000:00:1b.0: PME# disabled >>>>>>>>> [ 13.797697] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 20 (level, >>>>>>>>> low) >>>>>>>>> -> >>>>>>>>> IRQ 20 >>>>>>>>> [ 13.797784] HDA Intel 0000:00:1b.0: setting latency timer to 64 >>>>>>>>> >>>>>>>>> The PCI slot 00:1b.0 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 DOCs/Bootup.txt about >>>>>>>>> possible >>>>>>>>> fixes. >>>>>>>>> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >>>>>>>>> if help is needed. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ===== 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. >>>>>>>>> >>>>>>>>> The ALSA verion is 1.0.18 >>>>>>>>> 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-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1 >>>>>>>>> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 >>>>>>>>> >>>>>>>>> about /proc/asound/cards: >>>>>>>>> ------------------------ >>>>>>>>> 0 [Intel ]: HDA-Intel - HDA Intel >>>>>>>>> HDA Intel at 0xf8400000 irq 20 >>>>>>>>> ===== 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. >>>>>>>>> >>>>>>>>> The ALSA verion is 1.0.18 >>>>>>>>> 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-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1 >>>>>>>>> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 >>>>>>>>> >>>>>>>>> about /proc/asound/cards: >>>>>>>>> ------------------------ >>>>>>>>> 0 [Intel ]: HDA-Intel - HDA Intel >>>>>>>>> HDA Intel at 0xf8400000 irq 20 >>>>>>>>> >>>>>>>>> PCI slot 00:1b.0 has a High Definition Audio Card >>>>>>>>> The drivers are in the kernel modules tree at: >>>>>>>>> >>>>>>>>> /lib/modules/2.6.28-13-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>>>>>>>> >>>>>>>>> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>>>>>>>> The modem codec file for the HDA card is: >>>>>>>>> /proc/asound/card0/codec#1 >>>>>>>>> -------------------------------------------------------- >>>>>>>>> Codec: Motorola Si3054 >>>>>>>>> Address: 1 >>>>>>>>> Vendor Id: 0x10573055 >>>>>>>>> Subsystem Id: 0x10573055 >>>>>>>>> Revision Id: 0x100700 >>>>>>>>> Modem Function Group: 0x1 >>>>>>>>> >>>>>>>>> The audio card hosts a softmodem chip: 0x10573055 >>>>>>>>> >>>>>>>>> The softmodem chip 0x10573055 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/bigarch/archive-eighth/msg00838.html >>>>>>>>> >>>>>>>>> If not a Conexant modem, the driver snd-hda-intel with its >>>>>>>>> dependent >>>>>>>>> drivers: >>>>>>>>> snd_hda_intel 557492 6 >>>>>>>>> snd_pcm 99336 4 snd_hda_intel,snd_pcm_oss >>>>>>>>> snd 78792 19 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device >>>>>>>>> snd_page_alloc 18704 2 snd_hda_intel,snd_pcm >>>>>>>>> ---------- >>>>>>>>> provide audio + modem support with the modem chip residing on the >>>>>>>>> subsystem. >>>>>>>>> Any particular card can host any one of several soft modem chips. >>>>>>>>> >>>>>>>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>>>>>>> software. >>>>>>>>> === >>>>>>>>> >>>>>>>>> Predictive diagnostics for card in bus 00:1b.0: >>>>>>>>> Modem chipset detected on >>>>>>>>> NAME="Audio device: Intel Corporation 82801H " >>>>>>>>> CLASS=0403 >>>>>>>>> PCIDEV=8086:284b >>>>>>>>> SUBSYS=14c0:0025 >>>>>>>>> IRQ=20 >>>>>>>>> HDA=8086:284b >>>>>>>>> SOFT=8086:284b.HDA >>>>>>>>> HDAchipVendorID=1057 >>>>>>>>> CHIP=0x10573055 >>>>>>>>> IDENT=slmodemd >>>>>>>>> SLMODEMD_DEVICE=hw:0,6 >>>>>>>>> Driver=snd-hda-intel >>>>>>>>> >>>>>>>>> For candidate modem in: 00:1b.0 >>>>>>>>> 0403 Audio device: Intel Corporation 82801H >>>>>>>>> Primary device ID: 8086:284b >>>>>>>>> Subsystem PCI_id 14c0:0025 >>>>>>>>> Softmodem codec or chipset from diagnostics: 0x10573055 >>>>>>>>> from Archives: >>>>>>>>> The HDA card softmodem chip is 0x10573055 >>>>>>>>> >>>>>>>>> >>>>>>>>> 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.3.tar.gz having a compiled slmodemd. >>>>>>>>> Unpack >>>>>>>>> under >>>>>>>>> Linux with: >>>>>>>>> $ tar zxf SLMODEMD.gcc4.3.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 DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow >>>>>>>>> through >>>>>>>>> guidance. >>>>>>>>> >>>>>>>>> >>>>>>>>> Writing DOCs/Intel.txt >>>>>>>>> Writing DOCs/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.3.3 >>>>>>>>> and the compiler used in kernel assembly: 4.3.3 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Minimal compiling resources appear complete: >>>>>>>>> make utility - /usr/bin/make >>>>>>>>> Compiler version 4.3 >>>>>>>>> linuc_headers base folder /lib/modules/2.6.28-13-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 needed. The >>>>>>>>> also >>>>>>>>> required headers of package libc6 are commonly installed by >>>>>>>>> default. >>>>>>>>> Compiling hsfmodem drivers does require linux-libc-dev and >>>>>>>>> libc6-dev >>>>>>>>> packages, for kernels 2.6.24 and later versions. >>>>>>>>> In not included on your install CD, search for them at >>>>>>>>> http://packages.ubuntu.com >>>>>>>>> or comparable Repository for other Linux distros. >>>>>>>>> When compiling ALSA drivers, the utility "patch" will also be >>>>>>>>> needed. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 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 packages. >>>>>>>>> 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 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/DOCs/YourSystem.txt concerning other COMM channels: eth0 >>>>>>>>> wlan0 >>>>>>>>> wmaster0 >>>>>>>>> Which can interfere with Browser naviagation. >>>>>>>>> >>>>>>>>> Don't worry about the following, it is for experts should trouble >>>>>>>>> shooting >>>>>>>>> be necessary. >>>>>>>>> ========================================================== >>>>>>>>> >>>>>>>>> Checking for modem support lines: >>>>>>>>> -------------------------------------- >>>>>>>>> /device/modem symbolic link: lrwxrwxrwx 1 root root 6 2009-07-20 >>>>>>>>> 17:19 >>>>>>>>> /dev/modem -> ttySL0 >>>>>>>>> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root >>>>>>>>> 10 >>>>>>>>> 2009-07-20 17:19 /dev/ttySL0 -> /dev/pts/2 >>>>>>>>> Within /etc/udev/ files: >>>>>>>>> >>>>>>>>> Within /etc/modprobe.conf files: >>>>>>>>> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in >>>>>>>>> order >>>>>>>>> to >>>>>>>>> blacklist unwanted modem drivers >>>>>>>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem >>>>>>>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem >>>>>>>>> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >>>>>>>>> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >>>>>>>>> Within any ancient /etc/devfs files: >>>>>>>>> >>>>>>>>> Within ancient kernel 2.4.n /etc/module.conf files: >>>>>>>>> >>>>>>>>> --------- end modem support lines -------- >>>>>>>>> >>>>>>>>> >>>>>>>>> >> >
