Modem Pci Intel 537ep. Come installarlo?

13 risposte [Ultimo messaggio]
Ritratto di pinguinopaesano
Iscritto: 30/06/2006
Messaggi: 418

Si. mi da ancora quell'errore.

Ritratto di sunrots
Iscritto: 04/01/2005
Messaggi: 510

Da quel che si legge facendo una ricerca su forum e newsgroups, l'errore indicato si origina per incompatibilità di librerie e di kernel tra il sistema installato ed il pacchetto da cui proviene il modulo (in sostanza o kernel differente o librerie gcc diverse).
A questo punto posso solo consigliare di dare uno sguardo a questo altro post e di seguire la procedura per utilizzare l'utility scanmodem.
A partire dal report ottenuto si cercherà di capire se è possibile utilizzare con maggior successo un altro pacchetto.


Non più attivo qui. Mi troverete su Wink

Ritratto di pinguinopaesano
Iscritto: 30/06/2006
Messaggi: 418

A mesi e mesi di distanza, non sono ancora riuscito in nessuna maniera a far funzionare questo stramaledetto modem.

Su consiglio di sunrots sono andato a leggere il topic per il quale non riesco a trovare una soluzione definitiva.

questo il responso di modemdata.txt

Only plain text email is forwarded by the List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry
Welcome to SUSE LINUX 10.1 (i586) - Kernel kernel
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at .
Local Linux experts can be found through:
-------------------------- System information ----------------------------
Welcome to SUSE LINUX 10.1 (i586) - Kernel
Linux version (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 Tue Sep 19 07:26:15 UTC 2006
scanModem update of: 2007_Feb_21

USB modem not detected by lsusb

Modem or host audio card candidates have firmware information:

PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:05.0 8086:1080 1028:1000 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI

Modem interrupt assignment and sharing:
169: 422 IO-APIC-level Intel 82801DB-ICH4, eth0

--- Bootup diagnositcs for card in PCI slot 01:05.0 ----
ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 169
0000:01:05.0: ttyS1 at I/O 0xde08 (irq = 169) is a 16450
0000:01:05.0: ttyS2 at I/O 0xde10 (irq = 169) is a 8250
0000:01:05.0: ttyS3 at I/O 0xde18 (irq = 169) is a 16450
Couldn't register serial port 0000:01:05.0: -28

=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

For candidate modem in PCI bus: 01:05.0
Class 0703: 8086:1080 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
Primary PCI_id 8086:1080
Support type needed or chipset: INTEL537EP

In 2006, Intel appears to have ceased updates for Linux.
For the INTEL537 and INTEL536 chipset modems, the most current support is provided at:
But regular support is not available, see:
The outdated official Intel support packages can be accessed through:
Read Intel.txt and Modem/YourSystem.txt for follow through guidance.

Writing Intel.txt

Completed candidate modem analyses.

The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.1.0
and the compiler used in kernel assembly: 4.1.0

Compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
kernel_headers base folder /lib/modules/

Checking pppd properties:
-rwxr-xr-x 1 root dialout 291796 2006-04-23 04:38 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:

To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd

Checking settings of: /etc/ppp/options
asyncmap 0
lcp-echo-interval 30
lcp-echo-failure 4
lcp-max-configure 60
lcp-restart 2
idle 600
file /etc/ppp/filters

In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied

Read Modem/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.

Don't worry about the following, it is for the 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:
/etc/udev/rules.d/31-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*", GOTO="skip_ifup"
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp"
/etc/udev/rules.d/50-udev-default.rules:# 219 /dev/modems/mwave MWave modem firmware upload
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/%k"
Within /etc/modprobe.conf files:
/etc/modprobe.conf:# Linux ACP modem (Mwave)
/etc/modprobe.d/Intel537:# intel 537ep modem support
/etc/modprobe.d/blacklist:# ALSA PCI sound/modem modules - should be configured via yast
/etc/modprobe.d/blacklist:blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist:blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

Chi me lo traduce? grazie