>From ModemData.txt "Download from http://linmodems.technion.ac.il/packages/smartlink/ the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd. Unpack under Linux with:" I actually used SLMODEMD.gcc4.3.tar.gz as the 4.4 was not available. After starting gtkterm and setting the port to /dev/ttySL0 I get nothing from the modem. [root@grok SLMODEMD.gcc4.3]# ./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. [root@grok ~]# gtkterm Control signals read: Input/output error Control signals read: Invalid argument Same result if I start with slmodemd --country=USA --alsa modem:0
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.29.6-213.fc11.x86_64 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.29.6-213.fc11.x86_64 (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Tue Jul 7 21:02:57 EDT 2009 scanModem update of: 2009_08_15 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 064e:a110 Suyin Corp. HP Webcam ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser ID 0bc2:3008 Seagate RSS LLC ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor 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 103c:30cc Audio device: Intel Corporation 82801H Modem interrupt assignment and sharing: 22: 190 54962 IO-APIC-fasteoi HDA Intel --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- pci 0000:00:1b.0: reg 10 64bit mmio: [0xf8400000-0xf8403fff] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold pci 0000:00:1b.0: PME# disabled HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 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 22 PCI slot 00:1b.0 has a High Definition Audio Card The drivers are in the kernel modules tree at: /lib/modules/2.6.29.5-191.fc11.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko /lib/modules/2.6.29.6-217.2.8.fc11.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko /lib/modules/2.6.29.6-213.fc11.x86_64/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 29000 4 snd_hda_codec 65376 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel snd_pcm 79352 4 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec snd 65096 14 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer snd_page_alloc 9216 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=103c:30cc IRQ=22 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 103c:30cc 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.4.tar.gz having a compiled slmodemd. Unpack under Linux with: $ tar zxf SLMODEMD.gcc4.4.tar.gz and read instructions therein. But briefly, the modem is setup with command: 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.4.0 and the compiler used in kernel assembly: 4.4.0 Minimal compiling resources appear complete: make utility - /usr/bin/make Compiler version 4.4 linuc_headers base folder /lib/modules/2.6.29.6-213.fc11.x86_64/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: -r-xr-xr-x. 1 root root 352328 2009-03-06 01:47 /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) chmod a+x /usr/sbin/pppd or under Ubuntu related Linuxes chmod a+x /usr/sbin/pppd Checking settings of: /etc/ppp/options lock 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 tun0 virbr0 vnet0 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: slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/ files: Within /etc/modprobe.conf files: Within any ancient /etc/devfs files: Within ancient kernel 2.4.n /etc/module.conf files: --------- end modem support lines --------