Linmodems Mailing list Archives
Return-Path: <xaval@email.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 3641 invoked from network); 13 Mar 2006 09:48:48 -0000
Received: from webmail-outgoing2.us4.outblaze.com (HELO webmail-outgoing.us4.outblaze.com) (205.158.62.67)
by pdam.crynwr.com with SMTP; 13 Mar 2006 09:48:48 -0000
Received: from unknown (unknown [192.168.9.180])
by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 6402618001D6
for <discuss@linmodems.org>; Mon, 13 Mar 2006 09:49:37 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.51)
by wfilter.us4.outblaze.com; 13 Mar 2006 09:49:25 -0000
Received: by ws1-5.us4.outblaze.com (Postfix, from userid 1001)
id 9F2B18402F; Mon, 13 Mar 2006 09:49:25 +0000 (GMT)
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-3"
MIME-Version: 1.0
From: =?iso-8859-3?B?WGF2aWVyIFZhbGVudO0=?= <xaval@email.com>
To: discuss@linmodems.org
Date: Mon, 13 Mar 2006 10:49:25 +0100
Subject: scanModem, Ubuntu 5.10 "Breezy Badger" kernel 2.6.12-10-386
Received: from [81.34.222.203] by ws1-5.us4.outblaze.com with http for
xaval@email.com; Mon, 13 Mar 2006 10:49:25 +0100
X-Originating-Ip: 81.34.222.203
X-Originating-Server: ws1-5.us4.outblaze.com
Message-Id: <20060313094925.9F2B18402F@ws1-5.us4.outblaze.com>
Dear friends,
Can somebody guide me through the modem configuration process? I=20
can't make the system detect the modem. And I can't see any light in the en=
d of the tunnel.
After the scanModem this is my ModemData.txt:
------------ -------------- System information ------------------------
Ubuntu 5.10 "Breezy Badger"
on System with processor: i686
currently under kernel: 2.6.12-10-386
https://wiki.ubuntu.com/DialupModemHowto has good general guidance.
Be sure to read the Ethernet section of Modem/YourSystem.txt
A /dev/modem symbolic link is not present
USB modem not detected.
Checking for audio card
0000:00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI=20
AC-Link Controller Audio Device (rev 02)
Reading /proc/asound/pcm
00-00: ALI 5451 : ALI 5451 : playback 32 : capture 1
00-01: ALI 5451 modem : ALI 5451 modem : playback 1 : capture 1
The kernel was assembled with compiler: 3.4.5
with current System compiler GCC=3D4.0.2
Found make utility.
Checking for kernel-headers needed for compiling.
Kernel-headers supporting compiling are resident:
Modem candidates are at PCI_buses: 0000:00:06.0
0000:00:08.0
Providing detail for device at 0000:00:06.0
with vendor-ID:device-ID
----:----
Class 0401: 10b9:5451 Multimedia audio controller: ALi Corporation=20
M5451 PCI AC-Link Controller Audio Device (rev 02)
SubSystem 103c:0850 Hewlett-Packard Company: Unknown device 0850
Flags: bus master, medium devsel, latency 64, IRQ 5
Checking for IRQ 5 sharing with modem.
XT-PIC ALI 5451
XT-PIC ide1
-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default C=
PU
./scanModem test 10b9:5451 103c:0850 debian_version 2.6.12-10-386=20=20
3.4.5 4.0.2 i686
The audio card 10b9:5451 may carry a soft modem chip.
-------------------------------
The modem should setup with:
sudo slmodemd --alsa -c YOUR_COUNTRY hw:0,1
Get the SLMODEMD.gcc3 from http://linmodems.technion.ac.il/packages/smartli=
nk/
and follow guidance therein.
The soft modem in the 8086:2668 High Definition Audio has low level=20
support by
the snd-hda-intel driver, beginning with the 2.6.14 kernels.
The Conexant soft modem chipset is not supported by snd-hda-intel =
and
http://www.Linuxant.com is developing support for these modems.
For snd-ali5451.ko compiling instructions, see=20
http://phep2.technion.ac.il/linmodems/archive/msg04955.html.
Modem support within the snd-ali5451 driver is included in some=20
2.6.12 and later kernels
for this pair, -----PCI_IDs-------, a modem codec is not in the records.
Acessing archival information on all codecs used by SubVendor 103c=20
, for all Modem controllers
CXT
CXT
SIL27
CXT
SIL27
CXT
SIL27
CXT
The controller: 10b9:5451 ALI 5451
is capable of supporting soft modem chips from AT LEAST manufacturers:
AgereSystems
Smartlink
Archive records show that 103c:???? Subsystems from HP with the=20
exception of 103c:006b and 103c:3081
have a Conexant chip. Thus first test hsfmodem software from=20
http://www.linuxant.com/drivers
Should that support fail, the alternate route is described in=20
Modem/Slmodem-ALSA.txt
Checking for autoloaded ALSA modem drivers
snd_ali5451 22596 2
snd_ac97_codec 72188 1 snd_ali5451
snd_pcm 78344 4 snd_ali5451,snd_ac97_codec,snd_pcm_oss
snd 48644 9=20
snd_ali5451,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
Driver snd-ali5451 may enable codec acquisition
=3D=3D=3D Begin mc97 codec query =3D=3D=3D
=09
Files under /proc/asound/ do not include modem codec information.
If more decisive information is not given below,
this is a tentative signature of a Conexant hsfmodem. Download a=20
hsfmodem package from
http://www.linuxant.com/drivers or your installation CDs. For=20
SuSE/Novell, install both
km_hsfmodem and hsfmodem packages, for drivers and configuration=20
tools respectively.
=3D=3D=3D End mc97 codec query =3D=3D=3D
Beginning check for older ac97_codec modems.
An older ac97_modem codec was not detected.
Information on several modem chipset providers is provided below,
because ambiguities remain on the correct choice of supporting software.
=3D=3D Checking PCI IDs through modem chip suppliers =3D=3D
Vendor 11c1 corresponds to Lucent Technologies or subsidiary Agere=20
Systems, Inc.
Information is at: http://www.agere.com/client/modem_dsp.html.=20
Produced are both:
1) modems identifiable from their primary PCI IDs and
2) soft modem Subystem chips requiring identification through=20
codec readouts.
Lucent/Agere Mars/WinModem drivers from version 8.30 onwards have
the necessary fix for SMP machines which includes machines with
hyperthreading turned on (virtually acting as two CPUs).
AgereSoftModem drivers only support AC97 or MC97 modem controllers=20
with codecs charcterized by one of:
SIL_id =3D 39
mc97 codec is SIL27
0x27 , as output by modem diagnostics under Microsoft Windows
If uncertain, identity the softmodem codec through tests described=20
in Modem/SoftModem.txt
Support is currently ONLY for 2.4.n kernels and the following modem=20
controllers:
8086:(2416 2426 2446 7196 2486 24C6) , with 8086 =3D=3D Intel
1039:7013 SIS
1106:3068 VIA
Access the soft modem software through code sponsor IBM at:
http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=3DMIGR-526=
98
The SmartLink slmodem-2.9.9 may serve for modems not served by this=20
AgereSystems software.
If may be necessary to add -DMODVERSIONS to the compile flags,
depending on whether your kernel was thus compiled. See
http://linmodems.technion.ac.il/archive-fourth/msg01408.html
Under the controller 10b9:5451 ALI 5451 ,
with modem subSystem 103c:0850
Alternative supporting packages are the SmartLink slmodem-2.9.n=20
using its proprietary slamr driver,
or dependent on 10b9:5451 ALI 5451 , an Open Source driver from=20
the ALSA package.
See Modem/Slmodem-ALSA.txt for details.
A sample compilation is shown in:=20
http://linmodems.technion.ac.il/archive-fifth/msg02567.html
For SuSE 9.2 users, there is an update for driver slamr.ko loading=20
during bootup.
To find it easily, search for "slamr" within=20=20
http://www.novell.com/linux/download/updates/92_i386.html
SmartLink at http://www.smlink.com/ owns vendor IDs 163c, 2000,=20
2003, and 2004
The official download site is:=20=20
http://www.smlink.com/main/index1.php?ln=3Den&main_id=3D40
But a more recent code and a much broader license for other chipset suppo=
rt,
can be downloaded from http://linmodems.technion.ac.il/packages/smartlink/
Though not always needed, download the files:
slmodem-CurrentVersion.tar.gz - provides the most general code package.
SLMODEMD.gcc3 - provides a compiled slmodemd
ungrab-winmodem.tar.gz - may be needed for usage with slamr.
Details on their usage are in Slmodem.txt, Slmodem-ALSA.txt and
http://linmodems.technion.ac.il/slmodem-serial.html
=3D=3D Checking PCI IDs through modem chip suppliers =3D=3D
Vendor 10b9 is Acer Labs, producing highly integrated motherboards=20
and Ali components.
The tight integration unfortunately ofter blocks identification of=20
the modem chipset.
Desired information may be gained by using a COMM console under MS Window=
s,
and using ATI commands to elicit chipset and driver information.
10b9:5450 ALI 5450 and 10b9:5451 ALI 5451 are controllers for=20
unsupported "sound modems"
Providing detail for device at 0000:00:08.0
with vendor-ID:device-ID
----:----
Class 0703: 10b9:5457 Modem: ALi Corporation M5457 AC'97 Modem=20
Controller (prog-if 00 [Generic])
SubSystem 103c:0850 Hewlett-Packard Company: Unknown device 0850
Flags: medium devsel, IRQ 10
Checking for IRQ 10 sharing with modem.
XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, ohci1394, eth0,=20
radeon@pci:0000:01:05.0, serial
-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default C=
PU
./scanModem test 10b9:5457 103c:0850 debian_version 2.6.12-10-386=20=20
3.4.5 4.0.2 i686
From records, 103c:0850 has soft modem codec type CXT
The hsfmodem drivers from http://www.linuxant.com/drivers are the=20
ONLY support of ConeXanT codec modems under Linux!!
The controller: 10b9:5457 ALI 5457 AC-Link
is capable of supporting soft modem chips from AT LEAST manufacturers:
Pctel
Conexant
Intel
Smartlink
Archive records show that 103c:???? Subsystems from HP with the=20
exception of 103c:006b and 103c:3081
have a Conexant chip. Thus first test hsfmodem software from=20
http://www.linuxant.com/drivers
Should that support fail, the alternate route is described in=20
Modem/Slmodem-ALSA.txt
Checking for autoloaded ALSA modem drivers
snd_ali5451 22596 2
snd_ac97_codec 72188 1 snd_ali5451
snd_pcm 78344 4 snd_ali5451,snd_ac97_codec,snd_pcm_oss
snd 48644 9=20
snd_ali5451,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
Driver snd-intel8x0m may enable codec acquisition
---------------------------------------------------------------------------=
-------------
After, I downloaded the SLMODEMD.gcc3 as recommended and I followed=20
the guidance therein. No success. I tryed to follow these instructions with=
no luck:
Installation
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
1. Unpack tar.gz package file:
$ gzip -dc slmodem-2.9.X.tar.gz | tar xf -
2. 'cd' to package directory:
$ cd slmodem-2.9.X
3. Review and edit 'Makefile' (if need):
In many cases you will need to correct path to your local kernel
source tree:
KERNEL_DIR=3D/path/to/linux
Default KERNEL_DIR is '/lib/modules/<kerne-version>/build'. Many Linux
Distributions use directory '/usr/src/linux-<version>' also.
Note: If you are using Linux kernel 2.4, only header files should be
available for build in $(KERNEL_DIR)/include
Another way to pass right value KERNEL_DIR is to use command line
parameter while running 'make':
$ make KERNEL_DIR=3D/path/to/linux ...
4. Run 'make' command to compile package:
$ make
5. Install. As 'root' user run:
# make install
It will install:
- application 'slmodemd' under '/usr/sbin' directory
- hardware specific drivers (kernel modules) 'slamr' and 'slusb'
under conventional kernel modules directory
- character device nodes '/dev/slamr0-3' with major number 212
(for pci modems) and '/dev/slusb0-3' with major number 213
(for usb modems).
- config modules for autoloading (by editing file '/etc/modules.conf')
(only with 2.4 kernels)
But this is the result I got and I'm stacked now:
me@computer:~$ gzip -dc /home/me/SLMODEMD.gcc3.tar.gz | tar xf -
me@computer:~$ cd SLMODEMD.gcc3
me@computer:~/SLMODEMD.gcc3$ KERNEL_DIR=3D/LIB/MODULES/2.6.12-10-386/build
me@computer:~/SLMODEMD.gcc3$ make KERNEL_DIR=3D/LIB/MODULES/2.6.12-10-386/b=
uild
make: *** No targets specified and no makefile found. Stop.
Thanks if you can help me. Thanks if not.
--
--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/
Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003