dear my kernel got updated to kernel 2.6.28-14-generic so is that same method will be useful? On 8/10/09, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Ankur, > > scanModem recommends > > Predictive diagnostics for card in bus 04:06.0: > Modem chipset detected on > NAME="Modem: Motorola SM56 Data Fax Modem " > CLASS=0703 > PCIDEV=1057:3052 > SUBSYS=1057:3020 > IRQ=21 > IDENT=slamr > > For candidate modem in: 04:06.0 > 0703 Modem: Motorola SM56 Data Fax Modem > Primary device ID: 1057:3052 > Support type needed or chipset: slamr > > > > Writing DOCs/Intel.txt > > 1057:3052 has a Motorola chipset, poorly supported by Motorola itself > However Zello discovered that drivers written to support Smartlink > modems do support the 1057:3052 chipset!! > It sufficed to add 1057:3052 to the list of modem cards recognized by > the Smartlink slamr driver. > There is a ungrab-winmodem driver used in conjunction with slamr, > which must have 1057:3052 > similarly added. See messages from Zello: > > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html > > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html > and Alvaro Aguirre about the ungrab-winmodem fix: > > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html > For general guidance on ungrab-winmodem + slamr usage, read the > DOCs/Smartlink.txt > > The modem is supported by the Smartlink > plus the slmodemd helper utility. Read the > DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through > guidance. > > > For 2.6.28-11-generic compiling drivers is necessary. As of October > 2007 the current packages at > http://linmodems.technion.ac.il/packages/smartlink/ are the > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz > > Writing DOCs/Smartlink.txt > ============ end Smartlink section ===================== > > Download > > http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/slamr-2.6.28-11-generic.tar.gz > > extract it and run > $ sudo ./setup > > Then run > $ sudo slmodemd -C INDIA /dev/slamr0 > > leave it running and fire up another terminal/tab and run > $ sudo wvdialconf /etc/wvdial.conf > > and edit your_username, phone, password add a line Carrier Check = no. > Try to connect and if you have questions or are not able to connect > report back. > > Regards, > > Antonio > > > On 8/9/09, Ankur Joshi <pharmankur@xxxxxxxxx> wrote: >> 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-11-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=i686, >> Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 >> (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 >> scanModem update of: 2009_07_17 >> >> The dialer utility package WVDIAL does not appear to be installed on >> your System. >> Please read Modem/DOCs/wvdial.txt >> >> 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 1307:0163 Transcend Information, Inc. 512MB USB Flash Drive >> 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 04:06.0, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 04:06.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem >> >> Modem interrupt assignment and sharing: >> --- Bootup diagnostics for card in PCI slot 04:06.0 ---- >> [ 0.445978] pci 0000:04:06.0: reg 10 32bit mmio: >> [0xff700000-0xff700fff] >> [ 0.445985] pci 0000:04:06.0: reg 14 io port: [0xd000-0xd0ff] >> [ 0.446021] pci 0000:04:06.0: PME# supported from D0 D3hot D3cold >> [ 0.446025] pci 0000:04:06.0: PME# disabled >> [ 1.453362] serial 0000:04:06.0: PCI INT A -> GSI 21 (level, low) -> >> IRQ >> 21 >> [ 1.453455] 0000:04:06.0: ttyS1 at I/O 0xd008 (irq = 21) is a 16450 >> [ 1.453517] 0000:04:06.0: ttyS2 at I/O 0xd010 (irq = 21) is a 8250 >> [ 1.453578] 0000:04:06.0: ttyS3 at I/O 0xd018 (irq = 21) is a 16450 >> [ 1.453595] Couldn't register serial port 0000:04:06.0: -28 >> >> The PCI slot 04:06.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. >> >> >> 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 8086:d608 Audio device: Intel Corporation 82801G >> >> Modem interrupt assignment and sharing: >> 16: 1956 1979 IO-APIC-fasteoi uhci_hcd:usb5, HDA Intel >> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> [ 0.444976] pci 0000:00:1b.0: reg 10 64bit mmio: >> [0xff980000-0xff983fff] >> [ 0.445004] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> [ 0.445007] pci 0000:00:1b.0: PME# disabled >> [ 40.796685] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >> low) -> IRQ 16 >> [ 40.796742] 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: None >> >> >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-00: ALC888 Analog : ALC888 Analog : playback 1 : capture 1 >> 00-01: ALC888 Digital : ALC888 Digital : playback 1 >> 00-02: ALC888 Analog : ALC888 Analog : capture 1 >> >> about /proc/asound/cards: >> ------------------------ >> 0 [Intel ]: HDA-Intel - HDA Intel >> HDA Intel at 0xff980000 irq 16 >> >> 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-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> UNEXPECTED HDA diagnostic outcome. >> === Finished firmware and bootup diagnostics, next deducing cogent >> software. >> === >> >> Predictive diagnostics for card in bus 04:06.0: >> Modem chipset detected on >> NAME="Modem: Motorola SM56 Data Fax Modem " >> CLASS=0703 >> PCIDEV=1057:3052 >> SUBSYS=1057:3020 >> IRQ=21 >> IDENT=slamr >> >> For candidate modem in: 04:06.0 >> 0703 Modem: Motorola SM56 Data Fax Modem >> Primary device ID: 1057:3052 >> Support type needed or chipset: slamr >> >> >> >> Writing DOCs/Intel.txt >> >> 1057:3052 has a Motorola chipset, poorly supported by Motorola itself >> However Zello discovered that drivers written to support Smartlink >> modems do support the 1057:3052 chipset!! >> It sufficed to add 1057:3052 to the list of modem cards recognized by >> the Smartlink slamr driver. >> There is a ungrab-winmodem driver used in conjunction with slamr, >> which must have 1057:3052 >> similarly added. See messages from Zello: >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html >> and Alvaro Aguirre about the ungrab-winmodem fix: >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html >> For general guidance on ungrab-winmodem + slamr usage, read the >> DOCs/Smartlink.txt >> >> The modem is supported by the Smartlink >> plus the slmodemd helper utility. Read the >> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >> guidance. >> >> >> For 2.6.28-11-generic compiling drivers is necessary. As of October >> 2007 the current packages at >> http://linmodems.technion.ac.il/packages/smartlink/ are the >> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz >> >> Writing DOCs/Smartlink.txt >> ============ end Smartlink section ===================== >> >> >> Predictive diagnostics for card in bus 00:1b.0: >> Modem chipset not detected on >> NAME="Audio device: Intel Corporation 82801G " >> CLASS=0403 >> PCIDEV=8086:27d8 >> SUBSYS=8086:d608 >> IRQ=16 >> HDA=8086:27d8 >> SOFT=8086:27d8.HDA >> >> >> High Definition Audio (HDA) cards MAY host a modem chip in their >> Subsystem, >> and many are supported by the ALSA audio+modem driver snd-hda-intel >> A modem was not detected on HDA card 8086:27d8. >> If another modem card is present, then most likely 8086:27d8 does not >> host a modem. >> If another modem card has not been detected, then possibilities are: >> 1) A Conexant modem chip is present on 8086:27d8, as Conexant chips >> are frequently not detectable by ALSA diagnostics >> 2) The modem may be of the older non-PCI Controller Chipset (hardware) >> type. >> Try detection with Root permission: >> sudo wvdialconf /etc/wvdial.conf >> >> For candidate modem in: 00:1b.0 >> 0403 Audio device: Intel Corporation 82801G >> Primary device ID: 8086:27d8 >> Subsystem PCI_id 8086:d608 >> Softmodem codec or chipset from diagnostics: >> from Archives: >> >> >> >> Support type needed or chipset: >> >> Support can likely be achieved through two mutually exclusive >> alternatives: >> 1) The hsfmodem software for Conexant chipset modems: Read >> DOCs/Conexant.txt >> The following ALSA alternative CANNOT work with Conexant modems. >> >> 2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for >> details, >> and >> to test get the package SLMODEMD.gcc4.3.tar.gz from: >> http://linmodems.technion.ac.il/packages/smartlink/ >> >> >> 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-11-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 pppd properties: >> -rwsr-xr-- 1 root dip 277352 2009-02-20 22:55 /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/DOCs/YourSystem.txt concerning other COMM channels: eth0 >> 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: >> slmodemd created symbolic link /dev/ttySL0: >> Within /etc/udev/ files: >> >> Within /etc/modprobe.conf files: >> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >> /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 >> Within any ancient /etc/devfs files: >> >> Within ancient kernel 2.4.n /etc/module.conf files: >> >> --------- end modem support lines -------- >> >> >> >> -- >> Regards, >> Ankur Joshi >> > -- Regards, Ankur Joshi
