Hi all,

I have a Fujitsu S6240 laptop running SuSe 10.0 and I'm having trouble finding a driver for my winmodem (evil). I did chance upon the ScanModem script, but it seems(?) to say that what I have has not been reported before. sad.gif Thanks for any help you can give me. I'm kind of a beginner with Linux (OK, Newbie with a capital N), so be kind. I'm posting the output of Scanmodem at the end of this post (sorry if it's a bit long, I'm not sure what you really need).


Thanks for your time,

Katjum


*****************************************************
DO use the following line as the email Subject Line, to alert cogent experts:
scanModem,
Welcome to SUSE LINUX 10.0 (i586) - Kernel kernel 2.6.13-15-default
Occassionally reponses are blocked by an Internet Provider mail filters.
So do in a day also check the Archived responses at DISCUSS@linmodems.org
Code updated on: 2005_Dec_13
------------ -------------- System information ------------------------

Welcome to SUSE LINUX 10.0 (i586) - Kernel
on System with processor: i686
currently under kernel: 2.6.13-15-default
USB modem not detected.


The kernel was assembled with compiler: 4.0.2
with current System compiler GCC=4.0.2
Modem candidates are at PCI_buses: 00:1b.0

Providing detail for device at 00:1b.0
with vendor-ID:device-ID
----:----
Class 0403: 8086:2668 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
SubSystem 10cf:1326 Fujitsu Limited.: Unknown device 1326
Flags: bus master, fast devsel, latency 0, IRQ 10
Checking for IRQ 10 sharing with modem.
XT-PIC uhci_hcd:usb3, uhci_hcd:usb4, HDA Intel, yenta, ipw2200, i915@pci:0000:00:02.0


-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default CPU
./scanModem test 8086:2668 10cf:1326 SuSE 2.6.13-15-default 4.0.2 4.0.2 i686
This combination of softmodem controller and Subsystem:
Primary 8086:2668
SubSystem 10cf:1326
has not been previously reported.

for this pair, -----PCI_IDs-------, a modem codec is not in the records.

Acessing archival information on all codecs used by SubVendor 10cf , for all Modem controllers
SIL21
SIL27
SIL27
SIL22
SIL21



The controller: 8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller
is capable of supporting soft modem chips from AT LEAST manufacturers:
Conexant
Smartlink
The Subsystem PCI id does not itself identify the modem Codec.
Checking for autoloaded ALSA modem drivers
Modem support within the snd-hda-intel driver is included in 2.6.14 and later kernels

Driver snd-hda-intel may enable codec acquisition
=== Begin mc97 codec query ===
=== End mc97 codec query ===

Beginning check for older ac97_codec modems.
An older ac97_modem codec was not detected.


Please rerun scanModem after login as
# su - root
WithIn Modem/Slmodem.txt, see the slamr test for an explanation.


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

SmartLink at http://www.smlink.com/ owns vendor IDs 163c, 2000, 2003, and 2004
The official download site is: http://www.smlink.com/main/index1.php?ln=en&main_id=40 ,
with slmodem-2.9.10 and later releases only licensed for Smartlink chipsets.

A series maintaining a much broader license for other chipset support,
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-CurrentVersion.tar.gz - 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

== Checking PCI IDs through modem chip suppliers ==

Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, 537 soft modem
http://developer.intel.com/design/modems/ . Also produced are
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 Intel-537ep drivers through: http://developer.intel.com/design/modems/s...ort/drivers.htm
Also check at: http://linmodems.technion.ac.il/packages/Intel/537/
for beta releases and perhaps Already compiled drivers for some Linux distributions
A very detailed installation report cogent to 537 type modems is at:
http://linmodems.technion.ac.il/archive-fi...h/msg00541.html

Setup call id with:
Type 1 : When the phone line is not in use at+vcid=1
Type 2 : When the phone line is already in use on a call at+pcw=0
---------------------

======= PCI_ID checking completed ======
Update=2005_Dec_13

Analyzing information for PCMCIA device at PCI Bus 06:03.0
06:03.0 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 20)
Subsystem: Fujitsu Limited.: Unknown device 131e
Flags: bus master, stepping, slow devsel, latency 168, IRQ 10
GREPping for an inserted PCMCIA modem with filter: ommunication
If a PCMCIA modem is currently inserted and the sockets activated by
/etc/init.d/pcmcia start
then the PCMCIA bridge is NOT transparent.

If the modem is known to have a Lucent digital signal processing chipset,
then PCMCIA.tar.gz variant assembled by Joern Wustenfeld is necessary,
rather than the standard ltmodem-8.31a10.tar.gz at http://ltmodem.heby.de/

The kernel-2.6.13-15-default was compiled with CONFIG_REGPARM, providing more compact and faster code.


Adequate match of gcc versions of the compiler and kernel.
Checking for kernel-headers needed for compiling.
The kernel-headers have base folder:
/lib/modules/2.6.13-15-default/build -> /usr/src/linux-2.6.13-15-obj/i386/default
/usr/src/linux -> linux-2.6.13-15
/usr/src/linux-2.6.13-15
A /dev/modem symbolic link is not set.

drwxr-xr-x 2 root root 520 2005-12-23 16:04 /dev/.udevdb
There is an active UDEV file system, creating device nodes in volatile RAM.
However information from Proprietary drivers is soon to be excluded from
the supporting /sys/ file structure. Thus device nodes for Proprietary modem drivers
will then have to be created by bootup scripts.

Checking for modem symbolic link support lines within /etc/udev/ files


For information on modem port creation under the UDEV device file system see:
http://linmodems.technion.ac.il/archive-fo...h/msg03299.html for Conexnant modems
http://linmodems.technion.ac.il/archive-fi...h/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:# ppp over ethernet
/etc/modprobe.conf:# the kernel 2.2 uses pppox
/etc/modprobe.conf:# the kernel 2.4 uses pppoe
/etc/modprobe.conf:alias char-major-108 ppp_generic
/etc/modprobe.conf:alias char-major-144 pppoe
/etc/modprobe.conf:alias net-pf-24 pppoe
/etc/modprobe.conf:# the kernel 2.2 uses ppp.o as ppp driver,
/etc/modprobe.conf:# the kernel 2.4 uses ppp_generic.o
/etc/modprobe.conf:alias ppp0 ppp_generic
/etc/modprobe.conf:alias ppp1 ppp_generic
/etc/modprobe.conf:alias tty-ldisc-3 ppp_async
/etc/modprobe.conf:alias ppp-compress-18 ppp_mppe
/etc/modprobe.conf:alias ppp-compress-21 bsd_comp
/etc/modprobe.conf:alias ppp-compress-24 ppp_deflate
/etc/modprobe.conf:alias ppp-compress-26 ppp_deflate
-------------------------------------
Resident PPP support modules are properly uncompressed .
COMM services are not active
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 -------
ACPI: local apic disabled
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
IO window: disabled.
PREFETCH window: disabled.
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
apm: BIOS not found.
audit: initializing netlink socket (disabled)

The following packages should be installed to support compiling and modem testing:
make, glibc-devel, gcc-3.3 , libasound2-dev, wvdial and kernel-source-2.6.13-15-default
SuSE 9.0 and later has pre-compiled drivers supporting the following modem chipsets:
Intel HaM and 536ep
Conexant HSF (but not the HCF)
Lucent/AgereSystems ltmodem (Digital Siggnal Processing type)
IBM wmave
Smart Link soft modems
Unfortunately only the Intel HaM and 536ep are on the 3 CD Personal set, pending an update.
Locations on the 6 CD Professional set are:
CD4/suse/i586/smartlink-softmodem-2.7.9-89.i586.rpm - the slmodemd daemon
CD3/suse/i586/km_smartlink-softmodem-2.7.9-89.i586.rpm - slmodem driver compiling
CD4/suse/i586/hsfmodem-5.03.27mbsibeta02122600-92.i586.rpm - softmodem configuration
CD4/suse/i586/km_hsfmodem-5.03.27mbsibeta02122600-92.i586.rpm -softmodem driver code
installation report - http://linmodems.technion.ac.il/archive-fo...h/msg00350.html
CD4/suse/i586/ltmodem-8.26a-54.i586.rpm - a patch from SuSE may be needed for function
installation report - http://linmodems.technion.ac.il/archive-fo...h/msg00458.html
CD4/suse/i586/Intel-536ep-4.51-200.i586.rpm
CD4/suse/i586/Intel-v92ham-4.51-244.i586.rpm
CD4/suse/i586/mwavem-1.0.4-110.i586.rpm
Some pre-compiled SuSE 9.0 packages for the 2.4.21-99-default kernel are available at:
http://linmodems.technion.ac.il/packages/SuSE-9.0/
including AgereSoftModem and the Intel537 modems

IMPORTANT - The kernel-source-144/README.SuSE informs that the pre-assembled kernel-headers installed
from the 9.0 kernel-source-99 have some flaws. Upgrading to a later kernel, such as 2.4.21-144 with matching kernel-source is the simplest may of avoiding problems.

SuSE 9.1 comes with a SmartLink slamr.ko driver installed,
aiding identification of softmodem codecs by:
dmesg | grep slamr

For the 9.1 Personal (single CD installation) winmodem packages
have be downloaded from the SuSE 9.1 repository
Should compiling drivers may be necessary, the following additional packages
will have to be downloaded and installed:
make, glibc-devel, gcc-3.3.3 and kernel-source.
The kernel-headers are co-installed with the kernel-source.
Thus subsequent driver compiling does Not require additional preparations.