scanModem, Fedora Core release 3 (Heidelberg), Kernel kernel 2.6.11-1.35_FC3

From: M.Hockings (veeshooter_at_hockings.net)
Date: 07/16/05

  • Next message: Gerald Thompson: "Re: Easy way to update Fedora"
    To: fedora-list@redhat.com
    Date: Fri, 15 Jul 2005 23:58:59 -0400
    
    

    I am trying to get a ltmodem driver going for my computer. The machine
    is an older P400 IBM Aptiva that came with an internal v90/fax/voice
    modem. Now that the machine has Fedora Core 3 installed the modem is
    identified as an "unknown device" with the name "LT Win Modem". The
    pnpdump tool identifies it as "GVC5719/1710593[0] {LT Win Modem}".
    Looking at the hardware it is an ISA card with a big black plastic
    shroud over most of the card. The scanModem output is at the bottom of
    the note.

    Being unable to find a pre-built RPM for FC3 I thought I'd have a go at
    building the source. So far I have tried two versions with mixed unsuccess.
      http://alk.at.tut.by/ltmodem-2.6-alk-4.tar.bz2
    and
    http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/ltmodem-2.6-7alk.src.rpm

    I have followed the instructions diligently to the best of my ability
    and for both the result is the same. That is, when I try to do
      insmod ltmodem
    it works fine, but
      isnmod ltserial
    gives me the message
    insmod: error inserting 'ltserial.ko': -1 No such device

    Any ideas what I can do to track down why ltserial is objecting?

    Kind regards,

    Mike

    =============================================================================

    [root@aptiva ltmodem-2.6-alk-4]# make clean
    rm -f lt_modem.o ltmodem.o ltserial.ko serial.o ltserial.o
    ltserial.mod.* ltmodem.mod.o ltmodem.ko ltmodem.mod.c
    [root@aptiva ltmodem-2.6-alk-4]# make
    make -C /lib/modules/`uname -r`/build SUBDIRS=/usr/src/ltmodem-2.6-alk-4
    modules
    make[1]: Entering directory `/lib/modules/2.6.11-1.35_FC3/build'
      CC [M] /usr/src/ltmodem-2.6-alk-4/lt_modem.o
    /usr/src/ltmodem-2.6-alk-4/lt_modem.c: In function `GetLtModemInterface':
    /usr/src/ltmodem-2.6-alk-4/lt_modem.c:391: warning: assignment from
    incompatible pointer type
      CC [M] /usr/src/ltmodem-2.6-alk-4/serial.o
      LD [M] /usr/src/ltmodem-2.6-alk-4/ltmodem.o
      LD [M] /usr/src/ltmodem-2.6-alk-4/ltserial.o
      Building modules, stage 2.
      MODPOST
    Warning: could not find /usr/src/ltmodem-2.6-alk-4/.ltmdmobj.o.cmd for
    /usr/src/ltmodem-2.6-alk-4/ltmdmobj.o
      CC /usr/src/ltmodem-2.6-alk-4/ltmodem.mod.o
      LD [M] /usr/src/ltmodem-2.6-alk-4/ltmodem.ko
      CC /usr/src/ltmodem-2.6-alk-4/ltserial.mod.o
      LD [M] /usr/src/ltmodem-2.6-alk-4/ltserial.ko
    make[1]: Leaving directory `/lib/modules/2.6.11-1.35_FC3/build'

    =============================================================================

    [root@aptiva ltmodem-2.6-alk-7]# make
    make -C /lib/modules/`uname -r`/build SUBDIRS=/usr/src/ltmodem-2.6-alk-7
    modules
    make[1]: Entering directory `/lib/modules/2.6.11-1.35_FC3/build'
      CC [M] /usr/src/ltmodem-2.6-alk-7/lt_modem.o
    /usr/src/ltmodem-2.6-alk-7/lt_modem.c: In function `lt_get_modem_interface':
    /usr/src/ltmodem-2.6-alk-7/lt_modem.c:308: warning: assignment from
    incompatible pointer type
    /usr/src/ltmodem-2.6-alk-7/lt_modem.c:317: warning: assignment from
    incompatible pointer type
      CC [M] /usr/src/ltmodem-2.6-alk-7/serial.o
    /usr/src/ltmodem-2.6-alk-7/serial.c: In function `lt_init':
    /usr/src/ltmodem-2.6-alk-7/serial.c:804: warning: assignment from
    incompatible pointer type
      LD [M] /usr/src/ltmodem-2.6-alk-7/ltmodem.o
      LD [M] /usr/src/ltmodem-2.6-alk-7/ltserial.o
      Building modules, stage 2.
      MODPOST
    Warning: could not find /usr/src/ltmodem-2.6-alk-7/.ltmdmobj.o.cmd for
    /usr/src/ltmodem-2.6-alk-7/ltmdmobj.o
      CC /usr/src/ltmodem-2.6-alk-7/ltmodem.mod.o
      LD [M] /usr/src/ltmodem-2.6-alk-7/ltmodem.ko
      CC /usr/src/ltmodem-2.6-alk-7/ltserial.mod.o
      LD [M] /usr/src/ltmodem-2.6-alk-7/ltserial.ko
    make[1]: Leaving directory `/lib/modules/2.6.11-1.35_FC3/build'

    =============================================================================

    Code updated on: 2005_July_13
    ------------ -------------- System information ------------------------
      Fedora Core release 3 (Heidelberg)
    Kernel
      on System with processor: i686
      currently under kernel: 2.6.11-1.35_FC3

    There are emerging complications under 2.6.10 and later kernels.
    Concerning code for:
    Smartlink slmodem :
        slmodem-2.9.9d.tar.gz at
    http://linmodems.technion.ac.il/packages/smartlink/
           has the current fixes. Related messages are:
        http://www.datiku.com/documents/2610_migration.php
        http://www.ussg.iu.edu/hypermail/linux/kernel/0409.3/0345.html
        http://linmodems.technion.ac.il/archive-fourth/msg03736.html .
        http://linmodems.technion.ac.il/packages/smartlink/ has an
    upgrab-winmodem.tar.gz,
            providing a driver to alleviate inappropriate capture of a
    winmodem by a serial port driver.
    Lucent/Agere DSP/ltmodem:
       http://linmodems.technion.ac.il/archive-fourth/msg03733.html
    Concerning Intel-536ep and 537
        http://www.ubuntulinux.org/wiki/IntelFiveThreeSixEPModemHowto/
        http://linmodems.technion.ac.il/archive-fifth/msg00280.html
        http://linmodems.technion.ac.il/archive-fifth/msg00881.html

      The kernel-2.6.11-1.35_FC3 was compiled with CONFIG_REGPARM, providing
    more compact and faster code.

      The kernel was assembled with compiler: 3.4.3
      with current System compiler GCC=3.4.3

    Checking for kernel-headers needed for compiling.
    The kernel-headers have base folder:
    /lib/modules/2.6.11-1.35_FC3/build
    Please install the package WVDIAL for modem testing and dialout.

      Modem symbolic link is: /dev/modem -> /dev/ttyLT0
      USB modem not detected.

    --------- lspci scan ----------------
      PCI_bus
    00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
    (rev 02)
    00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
    (rev 02)
    00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
    00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
    00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
    00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
    00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
    (rev 05)
    00:10.0 Multimedia video controller: 3Dfx Interactive, Inc. Voodoo 2
    (rev 02)
    01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP
    1X/2X (rev 5c)
    -------------------------------------

      A modem was not detected among the above PCI devices.
      This indicates that the modem, if present has a non-standard or ISA
    bridge.
      Please follow the directions in Modem/SoftModem.txt for identifying
    the modem properties
      when booting under Microsoft Windows. Also access any documentation
    sources
      on yourchipset. Guidance can only be provided AFTER
      the chipset and/or its drivers have been identified.

      The IBM mwave modem does have a driver within 2.6.n kernel+module
    releases. If is at:
               /lib/modules//kernel/drivers/char/mwave/mwave.ko
    and can be loaded only if Mwave hardware is present Test with:
      # su - root
      followed by
      # modprobe wmave
      If successful see:
              http://tedfelix.com/Mwave/
              http://www.linuxdocs.org/HOWTOs/mini/ACP-Modem/ , section 2.4 and
    later.
              http://www.freenetpages.co.uk/hp/mjbou/dwtpul.html
            http://tedfelix.com/Mwave/
            
      A failure response has output like:
              FATAL: Error inserting mwave
    (/lib/modules/2.6.10-1-686/kernel/drivers/char/mwave/mwave.ko):
    Input/output error
    indicating absence of an Mwave modem

       ======= PCI_ID checking completed ======
      Update=2005_July_13
    A PCMCIA CardBus is not detected on this System.
    GCCversion=3.4.3

    For information on modem port creation under the UDEV device file system
    see:
        http://linmodems.technion.ac.il/archive-fourth/msg03299.html for
    Conexnant modems
        http://linmodems.technion.ac.il/archive-fifth/msg01177.html for
    Lucent/Agere DSP modems

    The following information blocks just query some ppp support items.

    ====================================================
        grep -rs ppp /etc/modprobe.*
    -------------------------------------
    /etc/modprobe.conf.dist:alias tty-ldisc-3 ppp_async
    /etc/modprobe.conf.dist:alias tty-ldisc-14 ppp_synctty
    /etc/modprobe.conf.dist:alias ppp-compress-18 ppp_mppe
    /etc/modprobe.conf.dist:install ppp-compress-21 /bin/true
    /etc/modprobe.conf.dist:alias ppp-compress-24 ppp_deflate
    /etc/modprobe.conf.dist:alias ppp-compress-26 ppp_deflate
    -------------------------------------
      PPP support module bsd_comp.ko not found!
      Resident PPP support modules are properly uncompressed .
    ----active COMM services are ------------
    eth0 Link encap:Ethernet HWaddr 00:04:AC:36:79:B4
               inet6 addr: fe80::204:acff:fe36:79b4/64 Scope:Link
    This COMM mode should be closed before using the modem, or DNS services
    may fail.
      Be sure to read the Ethernet section of Modem/YourModem.txt
    DEVPPP=crw------- 1 root root 108, 0 Jul 14 19:29 /dev/ppp

       The current modem symbolic link is: /dev/modem -> /dev/ttyLT0
       The ports /dev/ttyS0 or 1,2,3 are for standard Controller chip modems

      No devfsd.conf file found, indicated absense of the devfsd daemon package
      for device file system (devfs) symbolic link support.

    DEVFSD=
      ---- dmesg queries -------
    ACPI: BIOS age (1998) fails cutoff (2001), acpi=force is required to
    enable ACPI
    ACPI: Interpreter disabled.
    pnp: PnP ACPI: disabled
    IBM machine detected. Enabling interrupts during APM calls.
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    audit: initializing netlink socket (disabled)

       Beginning with Fedora 2 kernel-2.6.6-1.427, kernel-headers needed
       for compiling drivers are provide at: /lib/modules/kernel-version/build/
       Thus upgrading above kernel 2.6.5-1.358 to 2.6.6-* is Stongly Recommended

       pppd version 2.4.2 may not be fully compatible with 2.6.8 kernel
    releases.
       If an initial CONNECT is achieved without PPP being subsequently
    established,
       drop back to a 2.4.1 version. This has worked for PCTEL AMR modem users,
       supported by the http://www.smlink.com slmodem software.
       Check pppd version with:
         pppd --version
       See http://linmodems.technion.ac.il/archive-fourth/msg03167.html

      For kernel-version 2.4.20-8 , a failure in automatic loading of PPP
    related modules
      has been reported. It was necessary to manually load with:
       /sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_generic
       /sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_deflate
       /sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_synctty
       /sbin/modprobe /lib/modules/2.4.20-8/kernel/drivers/net ppp_async
      or dialout efforts failed.

       The Internet Configuration Wizard writes a configuration file:
         /etc/wvdial.conf
       containing a line default line
         Stupid Mode = yes
       Better dialup performance may be achieved by commenting out this line as:
         # Stupid Mode = yes
       Also non-USA Users may need to add to the [Modem0] block:
         Init2 = AT+GCI=hexadecimal_country_code
       but test without it first.

       redhat is not yet providing pre-compiled drivers for WinModems

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Gerald Thompson: "Re: Easy way to update Fedora"

    Relevant Pages

    • Compiling the drivers for a ADSL Modem (IceData500)
      ... My modem model is IceData500 and the vendor says it is compatible with RH ... The unicorn driver is a standard Linux ... PPPoE, PPPoA or RFC2684 protocols, the kernel may need to be patched. ... To compile the drivers, ...
      (Fedora)
    • modem Sagem Fast800 dont syncronize
      ... I'm having trouble to put the modem Sagem Fast800 working. ... installing the driver eagle-usb-2.3.2 and plugin the modem I have this: ... Diagnostic driver eagle-usb 20060824033640 ... available gcc and the version used to compile the kernel differ ...
      (Ubuntu)
    • Re: Canon Pixma MP750?
      ... Canon as an AIO is not as mature. ... lack of driver refinement. ... On a device that has a fax modem all one needs to use is use ... see the need to offer pc to fax support on an AIO as pc to fax support ...
      (comp.periphs.printers)
    • Driver for Lucent modem
      ... I have problem configuring my modem within etch. ... I have Lucent modem that worked with 2.4 kernel in sarge. ... Driver that I used does not compile now. ...
      (Debian-User)
    • Re: Dialup problems (random disconnect
      ... the code is given in the pppd man page under 'EXIT CODES' ... Well, if it needs a module or driver, it's not a full hardware modem;-) ... is that binary only modules are rxactly tied to the kernel for which they ...
      (comp.os.linux.setup)