Subject: Re: slmodem 2.9.7 - msg#00083

Previous Message by Date: click to view message preview

Lucent modem, mandrake Mandrake Linux release 9.2 (Erbium) for amd64 2.4.22-24mdk

Distribution: Mandrake 9.2 (AMD64) Kernel: 2.4.22-24mdk Modem: PCI "Dynalink PCI Card56" (1456VQH-T4 56k) Chipset: vendor 11C1 device 044C Chipset manufacturer: Was AT&T MicroElectronics, now Lucent/Agere. Basically, I see the issue is that I need to trick the compilation process into thinking my CPU is x86 (which it is backward compatible with). The process stops when it IDs my CPU as AMD_64. Unfortunately, as a newbie to linux , I don't know how to pull this trick off. I've attached the BLDrecord.txt file for people to browse. If anyone could help, it'd be much appreciated. Cheers, Bruce BLDrecord.txt Description: Text document

Next Message by Date: click to view message preview

LTinstallRPM

Hi, I am having trouble getting my Lucent Winmodem (DSP Chipset) installed under Debian Linux (2.4.26-1-686). Trying to install the packapge ltmodem-2.4.26-1-686_8.31a3_i386.deb did not work. I am sending the output from dpkg -i ltmodem-2.4.26-1-686_8.31a3_i386.deb as well as LTinsatll.txt that was created during the installation attempt.I also have the kernel 2.6.6-1-686 available, but I have not found a Debian package for that kernel yet. Would be nice if somebody could help. Thanks, Helge LTinstall.txt Description: Text document LTinstall.txt.2 Description: Text document ltmodem-2.4.26-1-686_8.31a3_i386.log Description: Text document

Previous Message by Thread: click to view message preview

Re: slmodem 2.9.7

Howdy Folks, I'm trying to run vgetty with my Smartlink PCI561 based modem. I've installed slmodem 2.9.9 and it works fine for data but vgetty cannot get started. Jan claimed the driver does work with vgetty since 2.9.7! This is an Athlon system running Fedora Core 2 with kernel 2.6.5-1.358.8kstacks. The logfile looks like this: -- 07/03 19:10:33 SL0 vgetty: experimental test release 0.9.32 / 24Dec01 07/03 19:10:33 SL0 mgetty: experimental test release 1.1.30-Dec16 07/03 19:10:33 SL0 reading generic configuration from config file /etc/mgetty+sendfax/voice.conf 07/03 19:10:33 SL0 reading program vgetty configuration from config file /etc/mgetty+sendfax/voice.conf 07/03 19:10:33 SL0 reading port ttySL0 configuration from config file /etc/mgetty+sendfax/voice.conf 07/03 19:10:33 SL0 check for lockfiles 07/03 19:10:33 SL0 locking the line 07/03 19:10:33 SL0 tio_get_rs232_lines: TIOCMGET failed: Invalid argument 07/03 19:10:33 SL0 WARNING: DSR is off - modem turned off or bad cable? 07/03 19:10:33 SL0 lowering DTR to reset Modem 07/03 19:10:33 SL0 TIOCMBIC failed: Invalid argument 07/03 19:10:33 SL0 send: \dATQ0V1H0[0d] 07/03 19:10:34 SL0 waiting for ``OK'' ** found ** 07/03 19:10:34 SL0 send: ATS0=0Q0&D3&C1[0d] 07/03 19:10:34 SL0 waiting for ``OK'' ** found ** 07/03 19:10:34 SL0 mdm_send: 'ATI' 07/03 19:10:34 SL0 non-numeric ID string: 'SmartLink Soft Modem' 07/03 19:10:34 SL0 mdm_send: 'AT+FCLASS=2.0' -> ERROR 07/03 19:10:34 SL0 mdm_send: 'AT+FCLASS=2' -> ERROR 07/03 19:10:34 SL0 detecting voice modem type 07/03 19:10:36 SL0 V253 modem detected 07/03 19:10:36 SL0 initializing V253 voice modem 07/03 19:10:37 SL0 vgetty: Modem returned ERROR 07/03 19:10:37 SL0 setting ringback delay didn't work 07/03 19:10:37 SL0 vgetty: Modem returned ERROR 07/03 19:10:37 SL0 waiting... ...at which point it is running but not answering the phone! Cheers --Jasper On Thursday 29 April 2004 18:37, Jan De Luyck wrote: > F.Y.I.: The Smartlink slmodem-2.9.7 driver was released today. > > ftp://ftp.smlink.com/linux/unsupported/slmodem-2.9.7.tar.gz Forgot the changes: * Version 2.9.7 - Support for SL2800 modem cards - V90/V92 improvements - Voice modem (V253 like, supports vgetty) - V23 fixes - CID, ring detection fixes - misc improvements and fixes Jan -- "Hello," he lied. -- Don Carpenter, quoting a Hollywood agent

Next Message by Thread: click to view message preview

scanModem, mandrake kernel 2.6.3-14mdk

Hi everybody, Well, is this the mail list where you can get your modem working in Linux? Is it possible? Are you wizards? ;-) I read through Linmodems.org and ran scanModem.However, I am not able to understand the output files. I would like not to waste your time, but I do not know which should be my next step. I attach the ModemData.txt and I provide all the information I currently have. (Please, ask me whatever else you should need) I have a Toshiba Satellite Pro M10 I found various names for the modem: TOSHIBA Software Modem AMR from Linux Support for Toshiba PC [1] Softmodem (Lucent SCORPIO) from Toshiba Installation Infos [2] IRQ 11 TOSHIBA Software Modem AMR from the Windows XP Device Manager Best regards, Manuel. [1] http://linux.toshiba-dme.co.jp/linux/eng/pc/satProM10_report.htm [2] http://newsletter.toshiba-tro.de/main/index.html The most recent update of scanModem accessed at http://linmodems.technion.ac.il/packages/scanModem.gz should ALWAYS be used!! Current UPDATE=2004 June 22 URLs to cogent advice are regularly entered and updated, and your problem may be solved therein. If further help is needed, send a description of your problem to: discuss@xxxxxxxxxxxxx with this ModemData.txt Attached, using the following in the email Subject Line: scanModem, mandrake kernel 2.6.3-14mdk Always send this ENTIRE ModemData.txt. It includes subtle diagnostic ouputs needed to best guide you. If your PC is a laptop, please provide Make and Modem information. For instructions to UNSUBSCRIBE from discuss@xxxxxxxxxxxxx, send an email to: discuss-help@xxxxxxxxxxxxx -------------- System information ------------------------ mandrake Mandrake Linux release 10.0 (Official) for i586 on System with processor: i686 supported by kernel: 2.6.3-14mdk assembled with compiler: 3.3.2 with current System compiler GCC=3.3.2 /usr/bin/gcc -> /etc/alternatives/gcc A /dev/modem symbolic link is not set. ----active COMM services are ------------ eth0 Link encap:Ethernet HWaddr 00:00:39:3A:8D:3E inet6 addr: fe80::200:39ff:fe3a:8d3e/64 Scope:Link This COMM mode should be closed before using the modem, or DNS services may fail. Under 2.6.n kernels, there is currently modem support by: the more expensive Controller chipset modems using the open source serial code Conexant software downloaded through http://www.linuxant.com SmartLink slmodem drivers, including USB hardware USB modems using the Open Source acm.ko driver Lucent DSP (digital signal processing) chipsets but NOT: soft modems Red Hat fedora kernels For Intel537 modems, a release supporting 2.6.n is projected for mid June 2004 For all other modems, support projections are not available as of this update=2004 June 22 The following ppp related modules should be unpacked by root with: # gunzip PathTo/ModuleName.ko.gz /lib/modules/2.6.3-7mdk/kernel/drivers/net/bsd_comp.ko.gz /lib/modules/2.6.3-13mdk/kernel/drivers/net/bsd_comp.ko.gz /lib/modules/2.6.3-14mdk/kernel/drivers/net/bsd_comp.ko.gz /lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_async.ko.gz /lib/modules/2.6.3-13mdk/kernel/drivers/net/ppp_async.ko.gz /lib/modules/2.6.3-14mdk/kernel/drivers/net/ppp_async.ko.gz /lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_generic.ko.gz /lib/modules/2.6.3-13mdk/kernel/drivers/net/ppp_generic.ko.gz /lib/modules/2.6.3-14mdk/kernel/drivers/net/ppp_generic.ko.gz /lib/modules/2.6.3-7mdk/kernel/drivers/net/slhc.ko.gz /lib/modules/2.6.3-13mdk/kernel/drivers/net/slhc.ko.gz /lib/modules/2.6.3-14mdk/kernel/drivers/net/slhc.ko.gz /lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_deflate.ko.gz /lib/modules/2.6.3-13mdk/kernel/drivers/net/ppp_deflate.ko.gz /lib/modules/2.6.3-14mdk/kernel/drivers/net/ppp_deflate.ko.gz /lib/modules/2.6.3-7mdk/kernel/lib/zlib_deflate/zlib_deflate.ko.gz /lib/modules/2.6.3-13mdk/kernel/lib/zlib_deflate/zlib_deflate.ko.gz /lib/modules/2.6.3-14mdk/kernel/lib/zlib_deflate/zlib_deflate.ko.gz On most Systems, this will driven by installing the wvdial.rpm and the package providing the KPPP graphical dialing interface. mandrake is not yet providing pre-compiled drivers for WinModems An AC'97 modem codec was not detected Path to lspci is: /usr/bin/lspci --------- lspci scan ---------------- PCI_bus 00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03) 00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03) 00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03) 00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03) 00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03) 00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 83) 00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corp. 82801DBM Ultra ATA Storage Controller (rev 03) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio Controller (rev 03) 00:1f.6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go] (rev a3) 02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 02:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 83) 02:0a.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) 02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32) 02:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32) 02:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03) ------------------------------------- Modem candidates are at PCI_buses: 00:1f.6 Providing detail for device at PCI_bus 00:1f.6 with vendor-ID:device-ID ----:---- Class 0703: 8086:24c6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03) (prog-if 00 [Generic]) SubSystem 1179:0001 Toshiba America Info Systems: Unknown device 0001 Flags: medium devsel, IRQ 11 I/O ports at 1800 [size=256] I/O ports at 1080 [size=128] Internal_test: ./scanModem test 8086:24c6 1179:0001 mandrake 2.6.3-14mdk 3.3.2 The soft modem Subsystem operates under a controller 8086:24c6 82801DB ICH4 with Subsystem chipset POSSIBLY from: Broadcom AgereSystems Conexant Intel Smartlink Softmodem chipset identification is ambiguous because modem drivers are thenselves necessary to surely identity the Subsystem softmodem chip. Follow the guidance in ModemGeneral.txt for identifying the chip under Microsoft; include the ATI output information and ModemData.txt with your email to discuss@xxxxxxxxxxxxx Alternatively install the latest slmodem-2.9.n SmartLink drivers, which also support MANY non-Smartlink softmodem chips. At a minimum the driver can serve in identifying the true chipset even if it does not fully support the modem. After installing the driver, reboot and rerun ./scanModem The Smartlink section below has implementation details. First accessing chipset provider and modem assembler information for the modem SubSystem under the AC'97 or MC97 Controller. === Checking 1179 through chipset providers and modem assemblers ==== Vendors 14e4 is BroadCom, producing modems for Dell laptops, desktops and Others? 14e4:4212 is a BCM V.90 56k modem Subsystem 14e4:4d64 has mc97 codec BCM64 under Intel 8086:24c6 ICH4 Modem controller, It is NOT supported by the SmarkLink drivers. in a Inspiron 1100 laptop, as a BCM9415M modem, FCC Reg: 6KYMM01BBRCM1004 BCMSM drivers under Microsoft There is 2.2.n kernel support at: http://support.ap.dell.com/ap/en/filelib/download/index.asp?fileid=R47114 However the code has not been updated for some time. A fix by Giacomo Comes must be used for current 2.4 kernels: http://linmodems.technion.ac.il/archive-third/msg01652.html Vendor 1179 is Toshiba, using some motherboards with soft modems. Below are outputs from ATI commands under MS Windows for Subsystem: 1179:0001 ATI3 TOSHIBA V.90 Data+Fax Software Modem Version 3.1.89 ATI5 3.1.89, AMR Intel MB, AC97 ID:SIL REV:0x27, 19 Vendors 127a and 14f1 are Conexant, successor to Vendor=148d Rockwell technology. With respect to software support there are two main types, hcflinmodem* and hsflinmodem* . The HCF (Host Controller Free) which have a digital signal processsing (DSP) chipset, while the HSF in the soft modem family without a dsp. HSF support of version 5.03 is included with SuSE 9.0 for support of 2.4.21 version kernels. For support of 2.6.n kernels, new releaseses are provided at http://www.Linuxant.com/drivers/ Linuxant is providing free test packages for low speed CONNECTs. There is a one time subscription fee for full high speed support. A detailed software installation example is provided at: http://linmodems.technion.ac.il/archive-fourth/msg00350.html SuSE Conexant installation Re: Emergency!!! /Date:/ Wed, 11 Feb 2004 06:10:39 -0500 Modems with the following PCI_IDs also have Conexant HCF (Controller free) chipsets. 1024:1024 (Zenith Data Systems) 148D:1003 (DIGICOM Systems) 158B:0015 (Allied Data Technologies Tornado VFM56x-PRC) 141A:1035 (Apache Micro) The following six may be either HCF of HSF modems. Test the HSF package first (127a,14f1):(1025,1085, 2005) Should a HCF driver installation fail to serve among there, then uninstall and instead try the HSF driver resource. Subsystem HSF Conexant soft modems serve under AC'97 or MC97 controllers. These include: 14f1:(5422 2002) , plus many others with vendors assigned PCI IDs. SubSystem 104d:814e under a 1039:7013 Silicon Integrated Systems modem controlled has a Conexant chip After loading of HSF drivers, there will be displayed by command: /sbin/lsmod Module Size Used by Tainted: P hsfich 119116 0 (autoclean) hsfserial 26388 0 (autoclean) hsfengine 1126348 0 (autoclean) [hsfserial] hsfosspec 35328 0 (autoclean) [hsfich hsfserial hsfengine] plus many others not modem related. While drivers are pre-compiled for some Linux distributions, the installation of the HCF/HSF packages DOES in general require kernel-source/ preparation, as described in ModemDriverCompiling.txt. A post install suggestion for adjusting PCI latency is: http://phep2.technion.ac.il/linmodems/archive/msg05210.html Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, 537 soft modem and AC'97 and MC97 controllers managing a varierty of non-Intel soft modem subSystems. These subSystems often have PCI_IDs assigned by the modem assembler, rather than the chip provider. Download available drivers from: http://developer.intel.com/design/modems/support/drivers.htm Also check at: http://linmodems.technion.ac.il/resources.html for beta releases and perhaps Already compiled drivers for some Linux distributions --------------------- The installer code candidate is: Intel-537AA-2.27.39.0.ZIP for MDC controllers Intel-537EA-2.27.39.0.ZIP for CNR controllers But the Intel 537 readout needs confirmation !! Sadly there are a few mis-designations in the pciids dataset, which ./scanModem relies on Too many modems are being labeled Intel537 types. http://linmodems.technion.ac.il/archive-third/msg02463.html http://linmodems.technion.ac.il/archive-third/msg02476.html This includes the distinct Agere, Conexant and SmartLink chipsets types. Conseqeuntly YOU must manually obtain further information under Microsoft Windows through modem ATI tests/queries as instructed in ModemGeneral.txt Please include this information in any report to discuss@xxxxxxxxxxxxx Vendor 11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc. Information is at: http://www.agere.com/client/modem_dsp.html ----------- Under the controller 8086:24c6 82801DB ICH4 , the modem subSystem 1179:0001 will ONLY be supported by AgereSoftModem drivers if it has an Agere chipset. Thus establish identity of the softmodem chipset through tests described in ModemGeneral.txt ----------- Software access is initiated through code sponsor IBM: http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52698 AC'97/MC97 link modems may evoke a modem_codec with SIL_id = 39. Should the Agere software fail the SmartLink slmodem-2.9.n or slmdm-2.7.10 may serve. Current support from AgereSystems is only under 2.4.n kernels and for the following modem controllers: 8086:(2416 2426 2446 7196 2486 24C6) , with 8086 == Intel 1039:7013 SIS 1106:3068 VIA ---------------- Under the controller 8086:24c6 82801DB ICH4 , the modem subSystem 1179:0001 may be supported by the SmartLink slmodem-2.9.n drivers, even for non-SmartLink chipsets. ------------------------------ SmartLink owns vendor IDs 163c 2000 2003 2004, with general information at http://www.smlink.com/ Download software through: ftp://ftp.smlink.com/linux/unsupported/ Use the current slmodem-2.9.n series in preference to the older slmdm-versions The slmodem-2.9.n drivers are competent for Fedora and 2.6.nn Linux kernels. They also support MANY non-SmartLink soft modem chipsets under AC'97/MC97 controllers. There may be a warning about a not-SmartLink modem as the drivers load. But just proceed with modem functionality tests, as described in ModemTesting.txt The slmodem-2.9.6 installation report: http://linmodems.technion.ac.il/archive-fourth/msg00176.html is cogent to both USB and PCI modems, except that for PCI modems, the driver is slamr.o and the port created with: slmodemd --country=YourCountry /dev/slamr0 Beginning with slmodem-2.9.4 , a report on the softmodem chipset identity is provided. Display it after bootup by querying the dmesg buffer: # dmesg | grep slam Please report this information to discuss@xxxxxxxxxxxxx, if not already included in ModemGeneral.txt See IMPORTANT details concerning slmodem usage in ModemGeneral.txt Smartlink products include the: 163c:5459 SmartPCI561 modem and chipsets for other Brandname PCI modems; a chipset for USB modems, the SmartUSB56 (ST7554) based modems with vendor/product usb ids: 0483:7554 supported, and a chipset incorporated in many BrandName softmodems. === Checking 8086 through chipset providers and modem assemblers ==== Vendors 14e4 is BroadCom, producing modems for Dell laptops, desktops and Others? 14e4:4212 is a BCM V.90 56k modem Subsystem 14e4:4d64 has mc97 codec BCM64 under Intel 8086:24c6 ICH4 Modem controller, It is NOT supported by the SmarkLink drivers. in a Inspiron 1100 laptop, as a BCM9415M modem, FCC Reg: 6KYMM01BBRCM1004 BCMSM drivers under Microsoft There is 2.2.n kernel support at: http://support.ap.dell.com/ap/en/filelib/download/index.asp?fileid=R47114 However the code has not been updated for some time. A fix by Giacomo Comes must be used for current 2.4 kernels: http://linmodems.technion.ac.il/archive-third/msg01652.html ======= PCI_ID checking completed ====== Update=2004 June 22 The following information blocks just query some ppp support items. ==================================================== grep ppp /etc/modprobe.conf ------------------------------------- ------------------------------------- Be sure to read the section about ppp related modules and aliases in ModemGeneral.txt Be sure to read the Ethernet section of ModemGeneral.txt DEVPPP=crw------- 1 root root 108, 0 ene 1 1970 /dev/ppp DEVFS=active DEVFSD=/etc/devfsd.conf ---- dmesg queries ------- Local APIC disabled by BIOS -- reenabling. PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off' apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac) apm: overridden by ACPI. toshiba_acpi: Toshiba Laptop ACPI Extras version 0.17 toshiba_acpi: HCI method: \_SB_.VALD.GHCI The ModemDriverCompiling.txt is a MUST READ, if you are not experienced in configuring kernel-source/ or get "unresolved symbols" upon driver insertion. Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html