diamond supra modem file

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


Hi all,

I would really appreciate what assistance you could provide.  I was
able to get this Diamond Supra working at one point but now it's back
to "no modem was found on your system".  There is an internal winmodem
which is why there's a second device listed.

Is there a step I'm missing?  Also, did the driver get wiped out by
some boot script or something once I installed it?  I just can't
recreate the solution which got it to start up a few weeks ago.


Thank you in advance,
anna



 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.35-25-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,  Ubuntu ,  ALSA_version=1.0.23
Linux version 2.6.35-25-generic (buildd@palmer) (gcc version 4.4.5
(Ubuntu/Linaro 4.4.4-14ubuntu5) ) #44-Ubuntu SMP Fri Jan 21 17:40:48
UTC 2011
 scanModem update of:  2011_02_04

Distrib_ID=Ubuntu
DistribCodeName=maverick


Presently install your Linux Distributions dkms package. It provides
for automated driver updates,
following upgrade of your kernel.  For details see
http://linux.dell.com/projects.shtml#dkms

 There are no blacklisted modem drivers in /etc/modprobe*  files

 Potentially useful modem drivers now loaded are:


If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx

Candidate PCI devices with modem chips are:
00:03.1 Communication controller: 3Com Corporation Mini PCI 56k
Winmodem (rev 20)
High Definition Audio cards can host modem chips.

For candidate card in slot 00:03.1, firmware information and bootup
diagnostics are:
 PCI slot    PCI ID        SubsystemID    Name
 ----------    ---------    ---------    --------------
 00:03.1    10b7:1007    10b7:6159    Communication controller: 3Com
Corporation Mini PCI 56k Winmodem

 Modem interrupt assignment and sharing:
 11:       6839    XT-PIC-XT        uhci_hcd:usb1, yenta, yenta, eth0, CS46XX
 --- Bootup diagnostics for card in PCI slot 00:03.1 ----
[    0.824370] pci 0000:00:03.1: reg 10: [io  0x2000-0x20ff]
[    0.824386] pci 0000:00:03.1: reg 14: [mem 0xe8101c00-0xe8101cff]
[    0.824402] pci 0000:00:03.1: reg 18: [mem 0xe8101800-0xe810187f]
[    0.824456] pci 0000:00:03.1: supports D2
[    0.824465] pci 0000:00:03.1: PME# supported from D0 D2 D3hot D3cold
[    0.824476] pci 0000:00:03.1: PME# disabled

 The PCI slot 00:03.1 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.


=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus 00:03.1:
    Modem chipset  detected on
NAME="Communication controller: 3Com Corporation Mini PCI 56k Winmodem "
CLASS=0780
PCIDEV=10b7:1007
SUBSYS=10b7:6159
IRQ=11
IDENT=3COM.winmodem

 For candidate modem in:  00:03.1
   0780 Communication controller: 3Com Corporation Mini PCI 56k Winmodem
      Primary device ID:  10b7:1007
 Support type needed or chipset:    3COM.winmodem
 Under Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read
DOCs/InfoGeneral.txt about alternatives.

 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 10b7:1007 modem is Not_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

  ====== 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.4.5
             and the compiler used in kernel assembly: 4.4.5

 linux-headers-2.6.35-25-generic resources needed for compiling are
not manifestly ready!
 The patch utility is needed for compiling ALSA drivers, and possibly others.

 If compiling is necessary packages must be installed, providing:
     linux-headers-2.6.35-25-generic


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 273248 2010-07-09 09:41 /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

For guidance on FAX usage, get from
http://linmodems.technion.ac.il/packages/ ; get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be
changed to match your modem's port.

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 --------



[Linux DVB]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Xfree86]     [Fedora Women]     [Linux USB]

Powered by Linux