Suzanne, USA Fedora Core release 5 (Bordeaux),Kernel kernel 2.6.15-1.2054_FC5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello all!

I've got my 3Com 5610 modem connecting, but it refuses to connect at anything above 28,800. What am I doing wrong? Thanks so much! -Suzanne

ModemData.txt below:
--------------------------  System information ----------------------------
CPU=i686,  Fedora Core release 5 (Bordeaux)
Kernel
Linux version 2.6.15-1.2054_FC5 (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 Tue Mar 14
15:48:33 EST 2006
 scanModem update of:  2006_Jan_13
The modem symbolic link is /dev/modem -> /dev/ttyS3

 USB modem not detected.

Modem or host audio card candidates have firmware information:

 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
04:09.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610

 Modem interrupt assignment and sharing:
 16:    4036811   IO-APIC-level  serial

 --- Bootup diagnositcs for card in PCI slot 04:09.0 ----
ACPI: PCI Interrupt 0000:04:09.0[A] -> Link [LNKB] -> GSI 19 (level, low) -> IRQ 16
0000:04:09.0: ttyS1 at I/O 0xc880 (irq = 16) is a 16550A

 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
00:10.1 10de:026c 10de:cb84 Audio device: nVidia Corporation MCP51 High Definition Audio

 Modem interrupt assignment and sharing:
 20:      17534   IO-APIC-level  HDA Intel

 --- Bootup diagnositcs for card in PCI slot 00:10.1 ----
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LAZA] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:10.1 to 64

 === Finished modem firmware and bootup diagnostics section. ===
 === Next deducing cogent software ===

 For candidate modem in PCI bus:  00:10.1
Class 0403: 10de:026c Audio device: nVidia Corporation MCP51 High Definition Audio
      Primary PCI_id  10de:026c
    Subsystem PCI_id  10de:cb84
    Softmodem codec or Vendor from diagnostics:
                              from    Archives:


 Lacking a dsp (digital signal processing) chip, the modem is a software
 intensive or "softmodem" type. Its primary controller manages the traffic
 with the CPU. But the software needed is specified in the Subsystem.
 -----------------------------------------
Support type needed or chipset:

Support can likely be achieved through two mutually exclusive alternatives:
1) An ALSA modem driver plus slmodemd.  Read Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.tar.gz from:
        http://linmodems.technion.ac.il/packages/smartlink/
2) The hsfmodem software for Conexant chipset modems: Read Conexant.txt

 An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-intel8x0m
 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.tar.gz having a compiled slmodemd. Unpack under Linux with:
        $ tar zxf SLMODEMD.gcc4.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
         slmodemd -c YOUR_COUNTRY --alsa modem:1
 reporting dynamic creation of ports:
        /dev/ttySL0 --> /dev/pts/N   , with N some number
 Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.


The diagnostic outputs for this softmodem section have their raw information in folders and text files under /proc/asound/ which you can browse. The information
is from files:
        /proc/asound/pcm
-------------------------------
00-01: AD198x Digital : AD198x Digital : playback 1
00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1

        /proc/asound/modules
-------------------------------
 0 snd_hda_intel
and from the command:
        aplay -l | grep -i modem


----------------end Softmodem section --------------

scanModem could not identify the Support Type needed from diagnosics or archives.
        If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System > Hardware > Device Manager > Modems > Click on the + > Modem. Double click to expand the graphic. Manufacturer information may be displayed. For example, CXT stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
    ATI3 - Agere SoftModem Version 2.1.22
    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.


 Formal support for Conexant chipset modems are available ONLY through
 http://www.linuxant.com/drivers.  Read Conexant.txt for details.
and Modem/YourSystem.txt for follow through guidance. Driver speed is limited to
 14,400 until a key is purchased.  There is NO freeware alternative.
 There are two support package types: hsfmodem  and hcflinmodem.
 http://www.lorenzobettini.it/linux/LinuxSonyVaioVGN-S5VP_B reports a
 problem and solution in stalling a key, after testing of the free low
 speed download.

 Read Conexant.txt

Writing Conexant.txt

Writing Smartlink.txt
============ end Smartlink section =====================

 For candidate modem in PCI bus:  04:09.0
Class 0700: 12b9:1008 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
      Primary PCI_id  12b9:1008
 Support type needed or chipset:        USrobotics.serial


Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology.
 Their winmodems have no Linux support. Their controller chipset modems
 are supported by the Linux serial drivers.
 The PCI id 12b9:1008 modem is Supported.

PCI ID          Name                                    Support status
-------------------------------------------------------------------------------
10b7:1006 3COM 0038TA AC101 - TF Mini-PCI winmodem, not supported 10b7:1007 3COM 3C556 V.90 Mini-PCI winmodem, not supported 12b9:1006 US Robotics 3cp803598 Voice winmodem, not supported 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported

12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported 12b9:1008 US Robotics 3cp803598 serial driver supported
     wvdialconf wvtest     , should detect the modem. Read Testing.txt
  ====== end 3COM section =======

 Completed candidate modem analyses.

 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.1.0
             and the compiler used in kernel assembly: 4.1.0

 Kernel-header resources needed for compiling are not manifestly ready!

 If compiling is necessary packages must be installed, providing:
         kernel-source-2.6.15-1.2054_FC5


Checking pppd properties:
        -r-xr-xr-x 1 root root 308292 Feb 12  2006 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
    http://phep2.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/YourSystem.txt concerning other COMM channels: eth0 ppp0
Which can interfere with Browser naviagation.

 Don't worry about the following, it is for the experts
 should trouble shooting be necessary.
==========================================================

 Checking for modem support lines:
 --------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 10 Jan 21 13:50 /dev/modem -> /dev/ttyS3
slmodemd created symbolic link /dev/ttySL0:
     Within /etc/udev/ files:
/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660"
     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 --------


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux