Alles Suse oder was

Hi!
Ich bin Linux Neuling und habe ein Problem mit meinem notebook winmodem.
Ich weiß nicht, wie ich es unter Suse 9.0 installiere.

Nachdem die Handbücher nichts mehr hergaben, habe ich im Internet gesucht und bin auf das Problem mit den Softmodems gestoßen. Das Program Scanmodem habe ich unter Linux zum Laufen gebracht und folgendes (leicht gekürzt) kam dabei heraus:

*************************************************************************

SuSE SuSE Linux 9.0 (i586)
VERSION = 9.0
on System with processor: i686
supported by kernel: 2.4.21-166-default
assembled with compiler: 3.3.1
no gcc compiler installed
Modem symbolic link is: /dev/modem -> /dev/ttyACM0
COMM services are not active


SuSE 9.0 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/hsflinmodem-5.03.27mbsibeta02122600-92.i586.rpm - softmodem configuration
CD4/suse/i586/km_hsflinmodem-5.03.27mbsibeta02122600-92.i586.rpm -softmodem driver code
installation report - http://linmodems.technion.ac.il/archive-fourth/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-fourth/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
YaST does not yet appear competent to report PCI winmodem cards,
though they are displayed within the output of
# lspci
SuSE has been informed of these problems and updates will surely come.
But meanwhile 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

An AC'97 modem codec was not detected

Path to lspci is: /sbin/lspci
--------- lspci scan ----------------
PCI_bus

00:1f.6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03)
-------------------------------------

Modem candidates are at PCI_buses: 00:1f.6

Providing detail for device at PCI_bus 00:1f.6
with vendor-ID:device-ID
----:----
Class 0703: 8086:24c6 Modem: Intel Corp. 82801DB24c6 82801DB ICH4 > + a c i b . AC'97 Modem Controller (rev 03) (prog-if 00 [Generic])
SubSystem 1179:0001 Toshiba America Info Systems: Unknown device 0001
Flags: medium devsel, IRQ 10
I/O ports at 2400
I/O ports at 2000

Internal_test: ./scanModem test 8086:24c6 1179:0001 SuSE 2.4.21-166-default 3.3.1

The soft modem Subsystem operates under a controller
8086:24c6 82801DB ICH4 with Subsystem chipset POSSIBLY from:
Broadcom
AgereSystems
Conexant
Intel
Smartlink
Softmodem chipset identification is ambiguous because modem drivers
are thenselves necessary to surely identity the Subsystem softmodem chip.
Follow the guidance in ModemData.txt.2 for identifying the chip under Microsoft;
include the ATI output information and ModemData.txt with your email to discuss@linmodems.org
Alternatively install the slmodem-2.9.6 SmartLink drivers,
which also support MANY non-Smartlink softmodem chips.
At a minimum the driver can serve in identifying the true chipset
even if it does not fully support the modem.
The Smartlink section below has implementation details.

Install kernel-source package, the slmodem and km_slmodem packages.
If necessary, set a symbolic link needed for slmodem compiling:
# ln -s /usr/src/kernel-headers-2.4.21-166-default /lib/modules/2.4.21-166-default/build
Then install the packages and compile the drivers.
The compiling process is described in:
http://linmodems.technion.ac.il/archive-fourth/msg00176.html



Vendor 1179 is Toshiba, using some motherboards with soft modems.

Below are outputs from ATI commands under MS Windows for Subsystem: 1179:0001
ATI3 TOSHIBA V.90 Data+Fax Software Modem Version 3.1.89
ATI5 3.1.89, AMR Intel MB, AC97 ID:SIL REV:0x27, 19


Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, 537 soft modem
and AC'97 and MC97 controllers managing a varierty of non-Intel soft modem subSystems.
These subSystems will in have PCI_IDs assigned by the modem assembler, not Intel.
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
---------------------

Under the controller 8086:24c6 82801DB ICH4 ,
the modem subSystem 1179:0001
may be supported by the SmartLink slmodem-2.9.n drivers, even for non-SmartLink chipsets.
------------------------------

They also support MANY non-SmartLink soft modem chipsets under AC'97/MC97 controllers.
There may be a warning about a not-SmartLink modem as the drivers load.
But just proceed with modem functionality tests, as described in ModemTesting.txt
The slmodem-2.9.6 installation report: http://linmodems.technion.ac.il/archive-fourth/msg00176.html
is cogent to both USB and PCI modems, except that for PCI modems
except for PCI modems, the driver is slamr.o and the port created with:
slmodemd -country=YourCountry /dev/slamr0
Beginning with slmodem-2.9.4 , a report on the softmodem chipset identity is provided.
Display it after bootup by querying the dmesg buffer:
# dmesg | grep slam
# dmseg | grep SIL
Please report this information to discuss@linmodems.org,
if not already included in ModemData.txt.2
See IMPORTANT details concerning slmodem usage in ModemData.txt.2
Smartlink products include the:
163c:5459 SmartPCI561 modem and chipsets for other Brandname PCI modems;
a chipset for USB modems, the SmartUSB56 (ST7554) based modems
with vendor/product usb ids: 0483:7554 supported,
and a chipset incorporated in many BrandName softmodems.


======= PCI_ID checking completed ======
Update=2004 March 23
The following information blocks just query some ppp support items.
==============================================
grep ppp /etc/modules.conf
-------------------------------------
# ppp over ethernet
# the kernel 2.2 uses pppox
# the kernel 2.4 uses pppoe
alias char-major-144 pppox
post-install pppox insmod mssclampfw
pre-remove pppox rmmod mssclampfw
alias char-major-108 ppp_generic
alias char-major-144 pppoe
alias net-pf-24 pppoe
# the kernel 2.2 uses ppp.o as ppp driver,
# the kernel 2.4 uses ppp_generic.o
alias ppp0 ppp
alias ppp1 ppp
alias tty-ldisc-3 ppp
alias ppp0 ppp_generic
alias ppp1 ppp_generic
alias tty-ldisc-3 ppp_async
alias ppp-compress-18 ppp_mppe
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
-------------------------------------
DEVPPP=crw-rw---- 1 root root 108, 0 2003-09-23 20:01 /dev/ppp

The current modem symbolic link is: /dev/modem -> /dev/ttyACM0
The ports /dev/ttyS0 or 1,2,3 are for standard Controller chip modems


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

DEVFSD=
---- dmesg queries -------

****************************************************
Ich habe kein Problem das Englisch zu verstehen, ABER - was nun?
Das größere Problem ist, dass ich bisher nur unter kde "gearbeitet" habe und nichts von der Shell verstehe.
Also, was muß ich wissen um obig beschriebene Herausforderung zu meistern?

Für jegliche Anregungen, Tips, Verweise und whatever else wäre ich sehr dankbar!
gruß,
der flix

 

nette signatur

btw. muss ich schon sagen, dass ich nach letzten recherchen linus garnicht viel symphatischer finde als gates



ciao

 

Ich kann nur sagen geh zu

http://google.at/linux

und gib die Bezeichnung deines Modems ein (bei mir wars HSP56 MR) - Dann findest du vielleicht einen Treiber von irgendeinem freak. - meinst ohne dokumentation.

Ich hab für mein Modem zwar einen gefunden, aber bis heute nicht zu laufen gebracht - *gg*

greez pt

 

ich habe im Moment wenig Zeit um dir ausführlich zu helfen .. aber als erste Einschätzung --- dein WinModem ist das Problem -- in der Regel findet man für linux

keine Treiber für solche Geräte --