PDA

View Full Version : Linux & modem



Prescott
16-12-2004, 09:23 PM
howdy doodly,
as you may know i have yoper linux installed, and i have a 56k external modem, the thing is that it connects at 9600kbps, and it is soo slow on the net compare to when i am in xp, what can i do to get this thing to go faster? :confused:

also in another post somewhere, in the old pf1, i wanted to detect and configure my pci modem and chilling_silence gave me a link for me to download a tar.gz file, i think it was called scanmodem? i have extracted that and i am left with several files which one do you need to check out?

cheers

b1naryb0y
16-12-2004, 09:29 PM
Navigate to the directory you extracted the files to and run

./scanModem

make sure to include the "./"

Baldy
19-12-2004, 10:57 PM
Navigate to the directory you extracted the files to and run

./scanModem

make sure to include the "./"

Can you post the link to the program, as I have a winmodem and would like to go online with Linux, but can't get it to recognise the winmodem (if you get what I mean) I think I need to download some drivers or something

Prescott
19-12-2004, 11:03 PM
thats the thing, i cant seem to find my old thread from the old fourm and there is a link on that :confused:
chill gave me the link maybe he will know.
im currently having problems with my internet and i have found the problem, it is the fence lines and i cant seem to find any faults so i cant use my internal modem so it disconnects like crazy, so im using my old external 56k modem which doesnt seem to disconnect that much.

what sort of modem you got baldy?

what file do you guys need to see??

b1naryb0y
19-12-2004, 11:12 PM
You can find scanModem here (http://linmodems.technion.ac.il)

Here is a direct link to scanModem (http://linmodems.technion.ac.il/packages/scanModem.gz)

Links to resources and drivers for your Winmodem, including all popular chipsets can be found here (http://linmodems.technion.ac.il/resources.html)

For the most popular Winmodem (Lucent/Agere based) you can find source code and pre-compiled binaries on this page (http://www.heby.de/ltmodem)

Note that scanModem does not install any drivers, it merely helps you indentify the chipset :)

Prescott
19-12-2004, 11:16 PM
ive done that, chill was saying to post in a file here modem.txt? is that right?
darn i still cant find my old thread, its probley gone ......

b1naryb0y
19-12-2004, 11:24 PM
The output file you want is ModemData.txt.

Futher information can be found in ModemData.txt.2, this includes:

summary of modem Support under Linux
description of the SIL_ID test
some output from scanModem specific to your System
an explanation of the GCC 2.95 compiler warning
ethernet Interference with DNS (domain name service)
COMPILING DRIVERS. Please Linux Newbies read carefully!!
Followup Actions, to get online, with dialout examples.

Prescott
20-12-2004, 12:47 PM
ok here is the modemdata.txt, be warned its pretty big, sorry.


The most recent update of scanModem accessed at
http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used!! This update was done on: 2004_Dec_04
URLs to cogent advice are regularly updated, so your problem may be solved therein.
If further help is needed, send a description of your problem to:
discuss@linmodems.org with this ENTIRE file Attached,
It includes subtle diagnostic ouputs needed to best guide you.
If your PC is a laptop, please provide Make and Model information.
DO use the following line as the email Subject Line, to alert cogent experts:
scanModem, Yoper Linux 2.1.0-4 (for i686) kernel 2.6.8.1-3
Occassionally reponses are blocked by an Internet Providers mail filters.
So do in a day also check the Archived responses at DISCUSS@linmodems.org
------------ -------------- System information ------------------------
Yoper Linux 2.1.0-4 (for i686)
on System with processor: i686
currently under kernel: 2.6.8.1-3
/etc/issue=Yoper Linux 2.1.0-4 (for i686)
assembled with compiler: 3.4.1)
with current System compiler GCC=3.4.1
A /dev/modem symbolic link is not set.
Path to lspci is: /sbin/lspci
--------- lspci scan ----------------
PCI_bus
00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AQ [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AQ [Radeon 9600] (Secondary)
02:01.0 Communication controller: Ambient Technologies Inc HaM controllerless modem (rev 02)
02:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (CNR) Ethernet Controller (rev 81)
02:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
-------------------------------------

Modem candidates are at PCI_buses: 02:01.0

Providing detail for device at PCI_bus 02:01.0
with vendor-ID:device-ID
----:----
Class 0780: 1813:4000 Communication controller: Ambient Technologies Inc HaM controllerless modem (rev 02)
SubSystem
Flags: medium devsel, IRQ 12
Memory at e4100000 (32-bit, non-prefetchable)
I/O ports at a000 [size=256]
Capabilities: <available only to root>

-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default CPU
./scanModem test 1813:4000 Not_identified 2.6.8.1-3 3.4.1) 3.4.1 i686


Information on several modem chipset providers is provided below,
because ambiguities remain on the correct choice of supporting software.

== Checking PCI IDs through modem chip suppliers ==

Vendor=1813 Ambient Tech was acquired by Intel with its HaM (Host assisted Modem) chipsets.
Intel-v92ham-453.tgz is the most recent update, available at:
http://linmodems.technion.ac.il/packages/Intel/ham/
http://developer.intel.com/design/modems/support/drivers.htm
The 453 code release is also the last for this older chipset (relates Intel maintainer Dorian Araneda).
It is NOT functional when compiled under 2.6.n kernels.
But under the 2.4.nn kernels, all HaM chipsets are supported,
with a single EXCEPTION: the odd PCI_ID 1813:4100 modems. For the explanation, see message:
http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:9448:200210:fbhcoigfcimgkjdedjad


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 AC97 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 Modem/DriverCompiling.txt.

There is a conflict between modules snd-intel8x0m and hsfmc97ich.
The snd-intel8x0m Must be loaded first or the system may hang upon hsfmc97ich insertion.
http://linmodems.technion.ac.il/archive-fourth/msg03027.html

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

======= PCI_ID checking completed ======
Update=2004_Dec_04
A PCMCIA CardBus is not detected on this System.
The following information blocks just query some ppp support items.

================================================== ==
grep ppp /etc/modprobe.conf
-------------------------------------

-------------------------------------
Resident PPP support modules are properly uncompressed .
----active COMM services are ------------
ppp0 Link encap:Point-to-Point Protocol
This COMM mode should be closed before using the modem, or DNS services may fail.
Be sure to read the section about ppp related modules and aliases in Modem/General.txt
DEVPPP=crw-rw---- 1 root wheel 108, 0 2004-08-16 12:25 /dev/ppp
A /dev/modem symbolic link is not present

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

DEVFSD=
---- dmesg queries -------
CPU: Hyper-Threading is disabled
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
audit: initializing netlink socket (disabled)
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
apm: Unknown parameter `2'
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
Not_identified is not yet providing pre-compiled drivers for WinModems


The Modem/DriverCompiling.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

Prescott
22-12-2004, 10:48 PM
bump, anyone know what they can get out of this?, you guys need this to see what modem or something i have for linux...............

beama
22-12-2004, 11:26 PM
Modem candidates are at PCI_buses: 02:01.0

Providing detail for device at PCI_bus 02:01.0
with vendor-ID:device-ID
----:----
Class 0780: 1813:4000 Communication controller: Ambient Technologies Inc HaM controllerless modem (rev 02)
SubSystem
Flags: medium devsel, IRQ 12
Memory at e4100000 (32-bit, non-prefetchable)
I/O ports at a000 [size=256]
Capabilities: <available only to root>

-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default CPU
./scanModem test 1813:4000 Not_identified 2.6.8.1-3 3.4.1) 3.4.1 i686


Information on several modem chipset providers is provided below,
because ambiguities remain on the correct choice of supporting software.

== Checking PCI IDs through modem chip suppliers ==

Vendor=1813 Ambient Tech was acquired by Intel with its HaM (Host assisted Modem) chipsets.
Intel-v92ham-453.tgz is the most recent update, available at:
http://linmodems.technion.ac.il/packages/Intel/ham/
http://developer.intel.com/design/m...ort/drivers.htm (http://developer.intel.com/design/modems/support/drivers.htm)
The 453 code release is also the last for this older chipset (relates Intel maintainer Dorian Araneda).
It is NOT functional when compiled under 2.6.n kernels.
But under the 2.4.nn kernels, all HaM chipsets are supported,
with a single EXCEPTION: the odd PCI_ID 1813:4100 modems. For the explanation, see message:
http://linmodems.org/cgi-bin/ezmlm-...igfcimgkjdedjad (http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:9448:200210:fbhcoigfcimgkjdedjad)
It appears you have a Ham modem the links are provided for more infomation /updated drivers also read the Exception and check your kernel release (uname -a)

johnd
23-12-2004, 08:06 PM
As far as I know, all external modems are full hardware modems that should just work with Linux with no additional drivers (this has been my experience to date). Not sure why it would connect at 9600bps unless it is faulty??

Caesius
23-12-2004, 11:38 PM
Which program are you using to connect (KPPP, wvdial etc)? Does /etc/ppp/ppp.conf exist on your system?

Prescott
24-12-2004, 01:15 PM
KPPP

Graham L
24-12-2004, 01:55 PM
An external modem shouldn't be giving PCI information. :D


Scanmodem is looking at the internal winmodem. :rolleyes:


Remove the internal modem. You might be able to disable it in the BIOS, but I'd remove it physically (unless it's part of the motherboard :eek: ).

Then the startup routines should find the external modem on the serial port. (unless it's a USB modem, which might be opening another can of worms.)

Use dmesg | less to see what has been seen at boot time.