Salve a tutti!
Da alcuni giorni ho installato sul mio PC il sisteme operativo Ubuntu 8.04 che convive con Win Vista. Anch'io come molti altri (ho letto il forum) ho problemi di connessione internet tremite modem interno Motorola SM56 Data Fax Modem.
Seguendo la guida del wiki per l'installazione e configurazione dei driver “slmodem” e “winmodem”, tutto ok fino al comando make, che mi da il seguente errore:
ubu@ubu-desktop:~/slmodem-2.9.11-20070505/drivers$ make
cc -I/lib/modules/2.6.24-19-generic/build/include -o kernel-ver kernel-ver.c
kernel-ver.c:6:19: error: stdio.h: No such file or directory
kernel-ver.c: In function ‘main’:
kernel-ver.c:14: warning: incompatible implicit declaration of built-in function ‘printf’
make: *** [kernel-ver] Error 1
ubu@ubu-desktop:~/slmodem-2.9.11-20070505/drivers$
Sicuramente molti di voi conosceranno questo sistema operativo molto meglio di me essendo io un "neonato linuxiano".
Ho fatto altre ricerche (nei forum e in Google) ma non sono riuscito a rislovere il problema.
Per favore aiutatemi, così potro finalmente liberarmi di Windows!
Grazie.
Quella che segue è la mia configurazione hardware:
ubu@ubu-desktop:~/slmodem-2.9.11-20070505/drivers$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02)
00:03.0 Communication controller [0780]: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller [8086:29c4] (rev 02)
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC-2 Gigabit Network Connection [8086:294c] (rev 02)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 02)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 02)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 02)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IH (ICH9DH) LPC Interface Controller [8086:2912] (rev 02)
00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller [8086:2920] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller [8086:2926] (rev 02)
01:00.0 VGA compatible controller [0300]: nVidia Corporation Geforce 9600 GT 512mb [10de:0622] (rev a1)
03:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 interface [11ab:6101] (rev b2)
[glow=red,2,300]07:00.0 Modem [0703]: Motorola SM56 Data Fax Modem [1057:3052] (rev 04)[/glow]
07:01.0 Network controller [0280]: RaLink RT2561/RT61 rev B 802.11g [1814:0302]
07:03.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) [104c:8023]
ubu@ubu-desktop:~/slmodem-2.9.11-20070505/drivers$
[Risolto] Motorola SM56 Data Fax Modem - problema con "make"
[Risolto] Motorola SM56 Data Fax Modem - problema con "make"
Ultima modifica di ubu@maury il giovedì 30 ottobre 2008, 21:33, modificato 1 volta in totale.
Re: Motorola SM56 Data Fax Modem - problema con "make"
Io ho lo stesso tuo modem e, con un po' di sbattimenti, sono riuscito a farlo funzionare.
Andiamo per ordine. Che versione di kernel hai ?
Postami l'output del comando
Ciao.
Andiamo per ordine. Che versione di kernel hai ?
Postami l'output del comando
Codice: Seleziona tutto
uname -arRe: Motorola SM56 Data Fax Modem - problema con "make"
Ciao teimcrr,
questo è l'output che hai chiesto:
ubu@ubu-desktop:~$ uname -ar
Linux ubu-desktop 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux
ubu@ubu-desktop:~$
PS!: grazie per l'aiuto!!!!
questo è l'output che hai chiesto:
ubu@ubu-desktop:~$ uname -ar
Linux ubu-desktop 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux
ubu@ubu-desktop:~$
PS!: grazie per l'aiuto!!!!
Re: Motorola SM56 Data Fax Modem - problema con "make"
Con questa versione di kernel potresti evitare di compilare.
Scaricati il pacchetto precompilato da http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
Quello che corrisponde al tuo kernel dovrebbe essere slamr-2.6.24-19-generic.tar.gz.
Scompattalo in una cartella; vai dentro la cartella col terminale e dai il comando
Dovrebbe installare tutto lui.
Postami il risultato e poi vediamo.
Scaricati il pacchetto precompilato da http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
Quello che corrisponde al tuo kernel dovrebbe essere slamr-2.6.24-19-generic.tar.gz.
Scompattalo in una cartella; vai dentro la cartella col terminale e dai il comando
Codice: Seleziona tutto
sudo ./setupPostami il risultato e poi vediamo.
Re: Motorola SM56 Data Fax Modem - problema con "make"
Ecco li risultato del comando:
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505.tar.gz
Downloads Pubblici ungrab-winmodem-20070505
Examples Scrivania ungrab-winmodem-20070505.tar.gz
Immagini slamr-2.6.24-19-generic.tar.gz Video
Modelli slmodem-2.9.11-20070505
ubu@ubu-desktop:~$ tar zxf slamr-2.6.24-19-generic.tar.gz
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ cd slamr-2.6.24-19-generic
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$ [glow=red,2,300]sudo ./setup[/glow]
installing drivers for kernel version 2.6.24-19-generic
driver=slamr
Installing the Debian packages supporting autoloading
(Lettura del database ... 95856 file e directory attualmente installati.)
Mi preparo a sostituire sl-modem-daemon 2.9.10+2.9.9d+e-pre2-5ubuntu4 (con sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Shutting down SmartLink Modem driver normally ... no slmodemd daemon running.
Unloading modem driver from kernel ... slamr.
Spacchetto il sostituto di sl-modem-daemon ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
The user `Slmodemd' already exists. Exiting.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Copying over newer files
Making folder /lib/modules/2.6.24-19-generic/extra
Copying drivers to /lib/modules/2.6.24-19-generic/extra
Checking driver install
slamr.ko slusb.ko ungrab-winmodem.ko
Copying newer slmodemd to /usr/sbin/
Checking slmodemd version. Should be 2.9.11
SmartLink Soft Modem: version 2.9.11 Apr 28 2008 08:04:56
Finished installs.
Informing the System
Starting function tests, loading drivers:
Running diagnostic:
[ 576.116180] slamr: module license 'Smart Link Ltd.' taints kernel.
[ 576.119444] slamr: SmartLink AMRMO modem.
[ 576.119489] slamr: probe 1057:3052 SL1900 card...
[ 576.371769] slamr: slamr0 is SL1900 card.
[ 962.344197] slamr: SmartLink AMRMO modem.
[ 962.344244] slamr: probe 1057:3052 SL1900 card...
[ 962.434276] slamr: slamr0 is SL1900 card.
ports should be created by:
slmodemd -c USA /dev/slamr0
error: mdm setup: cannot open dev `/dev/slamr0': Device or resource busy
error: cannot setup device `/dev/slamr0'
Checking for success
Running wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan: S1 S2 S3
WvModem: Cannot get information for serial port.
ttySL0: ATQ0 V1 E1 -- OK
ttySL0: ATQ0 V1 E1 Z -- OK
ttySL0: ATQ0 V1 E1 S0=0 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0: Speed 4800: AT -- OK
ttySL0: Speed 9600: AT -- OK
ttySL0: Speed 19200: AT -- OK
ttySL0: Speed 38400: AT -- OK
ttySL0: Speed 57600: AT -- OK
ttySL0: Speed 115200: AT -- OK
ttySL0: Speed 230400: AT -- OK
ttySL0: Speed 460800: AT -- OK
ttySL0: Max speed is 460800; that should be safe.
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySL0.
Modem configuration written to /etc/wvdial.conf.
ttySL0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
Modem detection successful
Read wdial.txt
Then edit /etc/wvdial.conf with:
sudo gedit /etc/wvdial.conf
at the lines beginning with ; and deleting the ;
Then dialout with:
sudo wvdial
Running setup again is NOT necessary. Only for dialout the:
sudo wvdial
Read the Slamr.txt record, other *.txt files and the sample wvdial.conf .
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$
help me!!!
grazie.
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505.tar.gz
Downloads Pubblici ungrab-winmodem-20070505
Examples Scrivania ungrab-winmodem-20070505.tar.gz
Immagini slamr-2.6.24-19-generic.tar.gz Video
Modelli slmodem-2.9.11-20070505
ubu@ubu-desktop:~$ tar zxf slamr-2.6.24-19-generic.tar.gz
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ cd slamr-2.6.24-19-generic
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$ [glow=red,2,300]sudo ./setup[/glow]
installing drivers for kernel version 2.6.24-19-generic
driver=slamr
Installing the Debian packages supporting autoloading
(Lettura del database ... 95856 file e directory attualmente installati.)
Mi preparo a sostituire sl-modem-daemon 2.9.10+2.9.9d+e-pre2-5ubuntu4 (con sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Shutting down SmartLink Modem driver normally ... no slmodemd daemon running.
Unloading modem driver from kernel ... slamr.
Spacchetto il sostituto di sl-modem-daemon ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
The user `Slmodemd' already exists. Exiting.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Copying over newer files
Making folder /lib/modules/2.6.24-19-generic/extra
Copying drivers to /lib/modules/2.6.24-19-generic/extra
Checking driver install
slamr.ko slusb.ko ungrab-winmodem.ko
Copying newer slmodemd to /usr/sbin/
Checking slmodemd version. Should be 2.9.11
SmartLink Soft Modem: version 2.9.11 Apr 28 2008 08:04:56
Finished installs.
Informing the System
Starting function tests, loading drivers:
Running diagnostic:
[ 576.116180] slamr: module license 'Smart Link Ltd.' taints kernel.
[ 576.119444] slamr: SmartLink AMRMO modem.
[ 576.119489] slamr: probe 1057:3052 SL1900 card...
[ 576.371769] slamr: slamr0 is SL1900 card.
[ 962.344197] slamr: SmartLink AMRMO modem.
[ 962.344244] slamr: probe 1057:3052 SL1900 card...
[ 962.434276] slamr: slamr0 is SL1900 card.
ports should be created by:
slmodemd -c USA /dev/slamr0
error: mdm setup: cannot open dev `/dev/slamr0': Device or resource busy
error: cannot setup device `/dev/slamr0'
Checking for success
Running wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan: S1 S2 S3
WvModem: Cannot get information for serial port.
ttySL0: ATQ0 V1 E1 -- OK
ttySL0: ATQ0 V1 E1 Z -- OK
ttySL0: ATQ0 V1 E1 S0=0 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0: Speed 4800: AT -- OK
ttySL0: Speed 9600: AT -- OK
ttySL0: Speed 19200: AT -- OK
ttySL0: Speed 38400: AT -- OK
ttySL0: Speed 57600: AT -- OK
ttySL0: Speed 115200: AT -- OK
ttySL0: Speed 230400: AT -- OK
ttySL0: Speed 460800: AT -- OK
ttySL0: Max speed is 460800; that should be safe.
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySL0.
Modem configuration written to /etc/wvdial.conf.
ttySL0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
Modem detection successful
Read wdial.txt
Then edit /etc/wvdial.conf with:
sudo gedit /etc/wvdial.conf
at the lines beginning with ; and deleting the ;
Then dialout with:
sudo wvdial
Running setup again is NOT necessary. Only for dialout the:
sudo wvdial
Read the Slamr.txt record, other *.txt files and the sample wvdial.conf .
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$
help me!!!
grazie.
Re: Motorola SM56 Data Fax Modem - problema con "make"
L'installazione sembra OK.
Ora controlla che i due moduli del driver siano caricati.
Dai i comandi
L'output dev'essere del tipo
(i numeri possono cambiare)
Se è così, passiamo a configurare wvdial
Dai il comando
e incollaci le seguenti righe alla fine:
Metti i tuoi dati (Numero, utente e password). Poi salva ed esci
A questo punto dando il comando
si dovrebbe connettere. CTRL+C per disconnettersi.
Fammi sapere.
Ciao
Ora controlla che i due moduli del driver siano caricati.
Dai i comandi
Codice: Seleziona tutto
lsmod |grep slamr
lsmod |grep ungrabCodice: Seleziona tutto
slamr 433448 2
ungrab_winmodem 3584 0 Se è così, passiamo a configurare wvdial
Dai il comando
Codice: Seleziona tutto
sudo gedit /etc/wvdial.confCodice: Seleziona tutto
[Dialer SM56]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
Check Def Route = on
Phone = Numero_di_telefono_del_tuo_provider
Idle Seconds = 0
Abort on Busy = off
Modem Type = Analog Modem
Stupid Mode = on
Baud = 57600
Auto DNS = on
Dial Command = ATM1L3DT
Dial Attempts = 3
Ask Password = off
Init = ATX3
ISDN = 0
Username = Tuo_nome_utente_per_loggarti_a_internet
Password = Tua_password_per_loggarti_a_internet
Dock = on
Carrier Check = off
Auto Reconnect = on
Modem = /dev/ttySL0
A questo punto dando il comando
Codice: Seleziona tutto
wvdial SM56Fammi sapere.
Ciao
Re: Motorola SM56 Data Fax Modem - problema con "make"
Grazie mille teimcrr!!!
Sono riuscito a collegarmi (ad una velocita molto bassa) però una sola volta.
Le volte succesive che ho provato non ha funzionato.
Questo è il messaggio che mi da il wdialer SM56:
ubu@ubu-desktop:~$ wvdial SM56
--> WvDial: Internet dialer version 1.60
--> Cannot open /dev/ttySL0: Permission denied
--> Cannot open /dev/ttySL0: Permission denied
--> Cannot open /dev/ttySL0: Permission denied
ubu@ubu-desktop:~$ sudo -s
root@ubu-desktop:~#
root@ubu-desktop:~# wvdial SM56
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
--> Sending: ATQ0
--> Re-Sending: ATX3
--> Modem not responding.
root@ubu-desktop:~#
Mi sembra di capire che c'è un problema con la porta seriale?!?!?
Comunque grazie al tuo aiuto sono, nonostante questo intoppo, sulla buona strada!
Help me!!!!!!!
Sono riuscito a collegarmi (ad una velocita molto bassa) però una sola volta.
Le volte succesive che ho provato non ha funzionato.
Questo è il messaggio che mi da il wdialer SM56:
ubu@ubu-desktop:~$ wvdial SM56
--> WvDial: Internet dialer version 1.60
--> Cannot open /dev/ttySL0: Permission denied
--> Cannot open /dev/ttySL0: Permission denied
--> Cannot open /dev/ttySL0: Permission denied
ubu@ubu-desktop:~$ sudo -s
root@ubu-desktop:~#
root@ubu-desktop:~# wvdial SM56
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
--> Sending: ATQ0
--> Re-Sending: ATX3
--> Modem not responding.
root@ubu-desktop:~#
Mi sembra di capire che c'è un problema con la porta seriale?!?!?
Comunque grazie al tuo aiuto sono, nonostante questo intoppo, sulla buona strada!
Help me!!!!!!!
Re: Motorola SM56 Data Fax Modem - problema con "make"
In effetti ho letto che ci può essere questo problema che funziona una volta e poi si intoppa.
Puoi aggirare il problema dando il comando
prima di ridare
vedrai che rifunziona.
Al limite fatti uno script che raggruppa i due comandi.
Inoltre tieni presente che se in futuro aggiorni il kernel perdi il driver e, o trovi un pacchetto precompilato per il nuovo kernel o ti tocca compilare da te.
Ciao.
Puoi aggirare il problema dando il comando
Codice: Seleziona tutto
sudo sl-modem-daemon restartCodice: Seleziona tutto
wvdial SM56Al limite fatti uno script che raggruppa i due comandi.
Inoltre tieni presente che se in futuro aggiorni il kernel perdi il driver e, o trovi un pacchetto precompilato per il nuovo kernel o ti tocca compilare da te.
Ciao.
Re: Motorola SM56 Data Fax Modem - problema con "make"
@teimcrr
ora mi scollego da vista e poi provo da ubuntu.
Scusa la mia ignoranza ma cos'è uno script e, nel caso specifico, cosa devo fare?
grazie ancora per il tuo prazioso aiuto!!!!!!
ora mi scollego da vista e poi provo da ubuntu.
Scusa la mia ignoranza ma cos'è uno script e, nel caso specifico, cosa devo fare?
grazie ancora per il tuo prazioso aiuto!!!!!!
Re: Motorola SM56 Data Fax Modem - problema con "make"
Uno script è un normale file di testo con dentro dei comandi.
Fai così: apri il terminale nella tua home e dai il comando
All'interno del file metti i comandi
Salva, poi dai il comando
che serve per rendere eseguibile il file.
A questo punto, dalla home, il comando per connettersi è:
Al posto di "dialup" puoi usare qualunque nome.
Però non ti meravigliare se ogni tanto ti da qualche problema.
Purtroppo il supporto di questo tipo di modem è un po' deficitario.
Ciao.
Fai così: apri il terminale nella tua home e dai il comando
Codice: Seleziona tutto
gedit dialupCodice: Seleziona tutto
sudo sl-modem-daemon restart
wvdial SM56
Codice: Seleziona tutto
chmod 777 ./dialup
A questo punto, dalla home, il comando per connettersi è:
Codice: Seleziona tutto
./dialup
Però non ti meravigliare se ogni tanto ti da qualche problema.
Purtroppo il supporto di questo tipo di modem è un po' deficitario.
Ciao.
Re: Motorola SM56 Data Fax Modem - problema con "make"
@teimcrr,
ti ringrazio per le esaurienti spiegazioni!
Possiedo anche un modem esterno usb "Hamlet Silver Surfer USB V.92" che vorrei installare; anche per questo ho fatto una ricerca nel forum e in rete. In un primo momento credevo di aver trovato una soluzione sul sito www.hamletcom.com ma poi ho scoperto che non era così (si trattava di un'alto modem).
Ciao
ti ringrazio per le esaurienti spiegazioni!
Possiedo anche un modem esterno usb "Hamlet Silver Surfer USB V.92" che vorrei installare; anche per questo ho fatto una ricerca nel forum e in rete. In un primo momento credevo di aver trovato una soluzione sul sito www.hamletcom.com ma poi ho scoperto che non era così (si trattava di un'alto modem).
Ciao
Re: Motorola SM56 Data Fax Modem - problema con "make"
Per vedere se il modem viene visto devi usare Scanmodem.
Guarda il wiki http://wiki.ubuntu-it.org/Hardware/Modem/Dialup/Scanmodem
In bocca al lupo.
Guarda il wiki http://wiki.ubuntu-it.org/Hardware/Modem/Dialup/Scanmodem
In bocca al lupo.
Re: Motorola SM56 Data Fax Modem - problema con "make"
Ciao teimcrr,
ho seguito il wiki per scanModem:
questo è il file ModemData.txt
0pt]Only plain text email is forwarded by the Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.24-19-generic
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@Linmodems.org are sometimes blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008
scanModem update of: 2008_10_24
The modem symbolic link is /dev/modem -> ttySL0
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 04f2:0403 Chicony Electronics Co., Ltd
ID 04d9:0499 Holtek Semiconductor, Inc.
ID 0572:1300 Conexant Systems (Rockwell), Inc.
ID 08ec:0008 M-Systems Flash Disk Pioneers
ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
USB modems not recognized
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:29c4 8086:5044 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Modem interrupt assignment and sharing:
16: 4 4 IO-APIC-fasteoi heci
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 35.484827] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 35.484852] PCI: Setting latency timer of device 0000:03:00.0 to 64
[ 43.251014] ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 43.251018] PCI: Setting latency timer of device 0000:00:03.0 to 64
For candidate card in slot 07:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
07:00.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
21: 1105805 1105248 IO-APIC-fasteoi uhci_hcd:usb2, libata, libata, SL1900
--- Bootup diagnostics for card in PCI slot 07:00.0 ----
[ 33.832624] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 33.832780] 0000:07:00.0: ttyS1 at I/O 0x1008 (irq = 21) is a 16450
[ 33.832880] 0000:07:00.0: ttyS2 at I/O 0x1010 (irq = 21) is a 8250
[ 33.832980] 0000:07:00.0: ttyS3 at I/O 0x1018 (irq = 21) is a 16450
[ 33.833014] Couldn't register serial port 0000:07:00.0: -28
[ 35.484964] BAR5:00:00 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00 0B:00 0C:01 0D:00 0E:00 0F:00
[ 43.455440] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 43.568976] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 151.123199] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 151.153507] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 811.081080] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 811.106933] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
The PCI slot 07:00.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:293e 8086:0001 Audio device: Intel Corporation 82801I
Modem interrupt assignment and sharing:
23: 3217 3247 IO-APIC-fasteoi HDA Intel, 0000:07:01.0
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 44.556618] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
[ 44.556633] PCI: Setting latency timer of device 0000:00:1b.0 to 64
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.16
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-04: ALC883 Analog : ALC883 Analog : capture 1
00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x93220000 irq 23
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.24-19-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 001:
Modem chipset detected on
SLOT="Bus 001 Device 004:"
NAME="Conexant Systems (Rockwell), Inc. "
bus=001
USBmodemID=0572:1300
IDENT=hsfmodem
Driver=hsfmodem
For candidate modem in: 001
Conexant Systems (Rockwell), Inc.
Primary device ID: 0572:1300
Support type needed or chipset: hsfmodem
Writing DOCs/Intel.txt
For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt
Start at http://www.linuxant.com/drivers/hsf/dow ... icense.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion: 2.6.24_19_generic
They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm
From http://www.linuxant.com/drivers/hsf/ful ... tu-x86.php
download hsfmodem-7.68.00.12full_k2.6.24_19_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.
Read DOCs/Conexant.txt
Writing DOCs/Conexant.txt
Predictive diagnostics for card in bus 07:00.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=21
IDENT=slamr
For candidate modem in: 07:00.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch ... 00846.html
http://linmodems.technion.ac.il/bigarch ... 00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch ... 00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
From http://linmodems.technion.ac.il/package ... nk/Ubuntu/ ,
download the package slamr-2.6.24-19-generic.tar.gz
Under Linux, open a terminal and unpack with:
$ tar zxvf slamr*.tar.gz
Move into the unpacked folder
$ cd slamr-2.6.24-19-generic
Look around
$ ls
Run the
$ sudo ./setup
Afterwards do:
$ slmodemd --help
$ slmodemd --countrylist &> Clist.txt
If not in the USA, look for your COUNTRY_NAME therein.
Do and edit with:
$ sudo gedit /etc/default/sl-modem-daemon
and therein replace the USA in the line:
SLMODEMD_COUNTRY=USA
This will provide for the correct Country setting in the automated:
slmodemd -c COUNTRY /dev/slamr0
Read the DOCs/Smartlink.txt and DOCs/YourSystem.txt
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 00:03.0:
Modem chipset not detected on
NAME="Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller "
CLASS=0780
PCIDEV=8086:29c4
SUBSYS=8086:5044
IRQ=16
For candidate modem in: 00:03.0
0780 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Primary device ID: 8086:29c4
Support type needed or chipset:
----------------end Softmodem section --------------
scanModem could not identify the Support Type needed from diagnosics or archives.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801I "
CLASS=0403
PCIDEV=8086:293e
SUBSYS=8086:0001
IRQ=23
HDA=8086:293e
SOFT=8086:293e.HDA
High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
and many are supported by the ALSA audio+modem driver snd-hda-intel
A modem was not detected on HDA card 8086:293e.
If another modem card is present, then most likely 8086:293e does not host a modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 8086:293e, as Conexant chips
are frequently not detectable by ALSA diagnostics
2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
sudo wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801I
Primary device ID: 8086:293e
Subsystem PCI_id 8086:0001
Softmodem codec or chipset from diagnostics:
from Archives:
Support type needed or chipset:
Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.2.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.2.3
and the compiler used in kernel assembly: 4.2.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24-19-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-- 1 root dip 269256 2007-10-04 21:57 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmode ... 02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch ... 04656.html
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0 wlan0 wmaster0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 6 2008-10-26 12:45 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 2008-10-26 12:45 /dev/ttySL0 -> /dev/pts/0
Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules:ungrab-winmodem
--------- end modem support lines --------
Vedi se puoi darmi qualche consiglio per questo modem Usb.
Grazie mille!!!
ho seguito il wiki per scanModem:
questo è il file ModemData.txt
0pt]Only plain text email is forwarded by the Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.24-19-generic
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for dialup service.
Responses from Discuss@Linmodems.org are sometimes blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008
scanModem update of: 2008_10_24
The modem symbolic link is /dev/modem -> ttySL0
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 04f2:0403 Chicony Electronics Co., Ltd
ID 04d9:0499 Holtek Semiconductor, Inc.
ID 0572:1300 Conexant Systems (Rockwell), Inc.
ID 08ec:0008 M-Systems Flash Disk Pioneers
ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
USB modems not recognized
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:29c4 8086:5044 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Modem interrupt assignment and sharing:
16: 4 4 IO-APIC-fasteoi heci
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 35.484827] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 35.484852] PCI: Setting latency timer of device 0000:03:00.0 to 64
[ 43.251014] ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 43.251018] PCI: Setting latency timer of device 0000:00:03.0 to 64
For candidate card in slot 07:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
07:00.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
21: 1105805 1105248 IO-APIC-fasteoi uhci_hcd:usb2, libata, libata, SL1900
--- Bootup diagnostics for card in PCI slot 07:00.0 ----
[ 33.832624] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 33.832780] 0000:07:00.0: ttyS1 at I/O 0x1008 (irq = 21) is a 16450
[ 33.832880] 0000:07:00.0: ttyS2 at I/O 0x1010 (irq = 21) is a 8250
[ 33.832980] 0000:07:00.0: ttyS3 at I/O 0x1018 (irq = 21) is a 16450
[ 33.833014] Couldn't register serial port 0000:07:00.0: -28
[ 35.484964] BAR5:00:00 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00 0B:00 0C:01 0D:00 0E:00 0F:00
[ 43.455440] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 43.568976] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 151.123199] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 151.153507] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
[ 811.081080] ACPI: PCI interrupt for device 0000:07:00.0 disabled
[ 811.106933] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 21 (level, low) -> IRQ 21
The PCI slot 07:00.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:293e 8086:0001 Audio device: Intel Corporation 82801I
Modem interrupt assignment and sharing:
23: 3217 3247 IO-APIC-fasteoi HDA Intel, 0000:07:01.0
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 44.556618] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
[ 44.556633] PCI: Setting latency timer of device 0000:00:1b.0 to 64
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.16
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-04: ALC883 Analog : ALC883 Analog : capture 1
00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x93220000 irq 23
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.24-19-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 001:
Modem chipset detected on
SLOT="Bus 001 Device 004:"
NAME="Conexant Systems (Rockwell), Inc. "
bus=001
USBmodemID=0572:1300
IDENT=hsfmodem
Driver=hsfmodem
For candidate modem in: 001
Conexant Systems (Rockwell), Inc.
Primary device ID: 0572:1300
Support type needed or chipset: hsfmodem
Writing DOCs/Intel.txt
For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt
Start at http://www.linuxant.com/drivers/hsf/dow ... icense.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion: 2.6.24_19_generic
They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm
From http://www.linuxant.com/drivers/hsf/ful ... tu-x86.php
download hsfmodem-7.68.00.12full_k2.6.24_19_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.
Read DOCs/Conexant.txt
Writing DOCs/Conexant.txt
Predictive diagnostics for card in bus 07:00.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=21
IDENT=slamr
For candidate modem in: 07:00.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch ... 00846.html
http://linmodems.technion.ac.il/bigarch ... 00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch ... 00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
From http://linmodems.technion.ac.il/package ... nk/Ubuntu/ ,
download the package slamr-2.6.24-19-generic.tar.gz
Under Linux, open a terminal and unpack with:
$ tar zxvf slamr*.tar.gz
Move into the unpacked folder
$ cd slamr-2.6.24-19-generic
Look around
$ ls
Run the
$ sudo ./setup
Afterwards do:
$ slmodemd --help
$ slmodemd --countrylist &> Clist.txt
If not in the USA, look for your COUNTRY_NAME therein.
Do and edit with:
$ sudo gedit /etc/default/sl-modem-daemon
and therein replace the USA in the line:
SLMODEMD_COUNTRY=USA
This will provide for the correct Country setting in the automated:
slmodemd -c COUNTRY /dev/slamr0
Read the DOCs/Smartlink.txt and DOCs/YourSystem.txt
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 00:03.0:
Modem chipset not detected on
NAME="Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller "
CLASS=0780
PCIDEV=8086:29c4
SUBSYS=8086:5044
IRQ=16
For candidate modem in: 00:03.0
0780 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Primary device ID: 8086:29c4
Support type needed or chipset:
----------------end Softmodem section --------------
scanModem could not identify the Support Type needed from diagnosics or archives.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801I "
CLASS=0403
PCIDEV=8086:293e
SUBSYS=8086:0001
IRQ=23
HDA=8086:293e
SOFT=8086:293e.HDA
High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
and many are supported by the ALSA audio+modem driver snd-hda-intel
A modem was not detected on HDA card 8086:293e.
If another modem card is present, then most likely 8086:293e does not host a modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 8086:293e, as Conexant chips
are frequently not detectable by ALSA diagnostics
2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
sudo wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801I
Primary device ID: 8086:293e
Subsystem PCI_id 8086:0001
Softmodem codec or chipset from diagnostics:
from Archives:
Support type needed or chipset:
Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.2.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.2.3
and the compiler used in kernel assembly: 4.2.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24-19-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-- 1 root dip 269256 2007-10-04 21:57 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmode ... 02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch ... 04656.html
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0 wlan0 wmaster0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 6 2008-10-26 12:45 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 2008-10-26 12:45 /dev/ttySL0 -> /dev/pts/0
Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules:ungrab-winmodem
--------- end modem support lines --------
Vedi se puoi darmi qualche consiglio per questo modem Usb.
Grazie mille!!!
Re: Motorola SM56 Data Fax Modem - problema con "make"
Ad occhio si direbbe che il tuo Hamlet abbia un chipset Conexant.
Qui ti so aiutare meno. Puoi provare a leggere questo post
http://forum.ubuntu-it.org/viewtopic.php?t=110077
P.S.
Ma alla fine il modem SM56 ti funziona ?
Ciao.
Qui ti so aiutare meno. Puoi provare a leggere questo post
http://forum.ubuntu-it.org/viewtopic.php?t=110077
P.S.
Ma alla fine il modem SM56 ti funziona ?
Ciao.
Re: Motorola SM56 Data Fax Modem - problema con "make"
(good) Ciao teimcrr,
il motorola funziona bene; ogni tanto cade la linea ma assastanza di rado!
Scusa se non t'ho risposto subito ma sono stato impegnato inaltre faccende.
Per l'hmlet andrò a vedere il link e poi ti farò sapere.
Grazie mille per tutto il tuo aiuto!!!
il motorola funziona bene; ogni tanto cade la linea ma assastanza di rado!
Scusa se non t'ho risposto subito ma sono stato impegnato inaltre faccende.
Per l'hmlet andrò a vedere il link e poi ti farò sapere.
Grazie mille per tutto il tuo aiuto!!!
"Odio i ricchi con le loro stronzate da ricchi" dal film "il grande Lebowski"
Re: Motorola SM56 Data Fax Modem - problema con "make"
??? Ciao teimcrr,
la connessione con il motorola sm56 non mi funziona +, o meglio: sento che il modem parte facendo i clessici suoni, poi però si interrompe e non va +.
Ho ripetuto questa procedura
ubu@ubu-desktop:~$ tar zxf slamr-2.6.24-19-generic.tar.gz
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ cd slamr-2.6.24-19-generic
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$ sudo ./setup
installing drivers for kernel version 2.6.24-19-generic
driver=slamr
Installing the Debian packages supporting autoloading
(Lettura del database ... 95856 file e directory attualmente installati.)
Mi preparo a sostituire sl-modem-daemon 2.9.10+2.9.9d+e-pre2-5ubuntu4 (con sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Shutting down SmartLink Modem driver normally ... no slmodemd daemon running.
Unloading modem driver from kernel ... slamr.
Spacchetto il sostituto di sl-modem-daemon ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
The user `Slmodemd' already exists. Exiting.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Per una volta ha funzionato! Quando c'ho riprovato, più volte, con ./dialup) m'ha dato il seguente messaggio
ubu@ubu-desktop:~$ sudo -s
root@ubu-desktop:~# ./dialup
Shutting down SmartLink Modem driver normally.
Unloading modem driver from kernel ... slamr.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
ATX3
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
OK
--> Modem initialized.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
NO CARRIER
--> No Carrier! Trying again.
--> Sending: ATM1L3DT7020187187
--> for.
ATM1L3DT7020187187
NO CARRIER
--> No Carrier! Trying again.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
[1]+ Stopped ./dialup
root@ubu-desktop:~#
Non so cosa significhi "Carrier", ma penso che il problema sia lì ::)
Aiutami se puoi.
Grazie!!!
la connessione con il motorola sm56 non mi funziona +, o meglio: sento che il modem parte facendo i clessici suoni, poi però si interrompe e non va +.
Ho ripetuto questa procedura
ubu@ubu-desktop:~$ tar zxf slamr-2.6.24-19-generic.tar.gz
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ ls
Documenti Musica slmodem-2.9.11-20070505
Downloads Pubblici slmodem-2.9.11-20070505.tar.gz
Examples Scrivania ungrab-winmodem-20070505
Immagini slamr-2.6.24-19-generic ungrab-winmodem-20070505.tar.gz
Modelli slamr-2.6.24-19-generic.tar.gz Video
ubu@ubu-desktop:~$ cd slamr-2.6.24-19-generic
ubu@ubu-desktop:~/slamr-2.6.24-19-generic$ sudo ./setup
installing drivers for kernel version 2.6.24-19-generic
driver=slamr
Installing the Debian packages supporting autoloading
(Lettura del database ... 95856 file e directory attualmente installati.)
Mi preparo a sostituire sl-modem-daemon 2.9.10+2.9.9d+e-pre2-5ubuntu4 (con sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ...
Shutting down SmartLink Modem driver normally ... no slmodemd daemon running.
Unloading modem driver from kernel ... slamr.
Spacchetto il sostituto di sl-modem-daemon ...
Configuro sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ...
The user `Slmodemd' already exists. Exiting.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Per una volta ha funzionato! Quando c'ho riprovato, più volte, con ./dialup) m'ha dato il seguente messaggio
ubu@ubu-desktop:~$ sudo -s
root@ubu-desktop:~# ./dialup
Shutting down SmartLink Modem driver normally.
Unloading modem driver from kernel ... slamr.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
ATX3
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
OK
--> Modem initialized.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
NO CARRIER
--> No Carrier! Trying again.
--> Sending: ATM1L3DT7020187187
--> for.
ATM1L3DT7020187187
NO CARRIER
--> No Carrier! Trying again.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
[1]+ Stopped ./dialup
root@ubu-desktop:~#
Non so cosa significhi "Carrier", ma penso che il problema sia lì ::)
Aiutami se puoi.
Grazie!!!
Re: Motorola SM56 Data Fax Modem - problema con "make"
Postami il risultato di cat /etc/wvdial.conf
Controlla che nella sezione [Dialer SM56] ci sia la riga
Carrier Check = off
Controlla che nella sezione [Dialer SM56] ci sia la riga
Carrier Check = off
Re: Motorola SM56 Data Fax Modem - problema con "make"
Ciao teimcrr,
questo e l'output "cat":
ubu@ubu-desktop:~$ cat /etc/wvdial.conf
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
; Phone =
ISDN = 0
; Password =
; Username =
Modem = /dev/ttySL0
Baud = 460800
[Dialer SM56]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
Dial Attempts = 3
Password = Telecom
Check Def Route = on
Phone = 7020187187
Idle Seconds = 0
Abort on Busy = off
Modem Type = Analog Modem
Stupid Mode = on
Baud = 57600
Dial Command = ATM1L3DT
Modem = /dev/ttySL0
Auto DSN = on
Init = ATX3
ISDN = 0
Dock = on
Username = Telecom
Password = Telecom
Carrier Check = off
Auto Reconnect = on
ubu@ubu-desktop:~$
ho già aggiunto io "Carrier Check = off" (l'altra volta avevo scritto male!).
Ora funziona bene tranne che ora mi mette dei punti di domanda "?" (indirizzi IP) invece che dei numeri:
root@ubu-desktop:~# ./dialup
Shutting down SmartLink Modem driver normally.
Unloading modem driver from kernel ... slamr.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
ATX3
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
OK
--> Modem initialized.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
CONNECT 46667
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Wed Oct 29 09:11:03 2008
--> Pid of pppd: 8331
--> Using interface ppp0
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> local IP address 80.104.14.216
--> pppd: ��[06][08]��[06][08]
--> remote IP address 217.141.106.6
--> pppd: ��[06][08]��[06][08]
--> primary DNS address 62.211.69.150
--> pppd: ��[06][08]��[06][08]
--> secondary DNS address 212.48.4.15
--> pppd: ��[06][08]��[06][08]
Comunque si connette bene!!!!!
Grazie Mille ancora.
questo e l'output "cat":
ubu@ubu-desktop:~$ cat /etc/wvdial.conf
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
; Phone =
ISDN = 0
; Password =
; Username =
Modem = /dev/ttySL0
Baud = 460800
[Dialer SM56]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
Dial Attempts = 3
Password = Telecom
Check Def Route = on
Phone = 7020187187
Idle Seconds = 0
Abort on Busy = off
Modem Type = Analog Modem
Stupid Mode = on
Baud = 57600
Dial Command = ATM1L3DT
Modem = /dev/ttySL0
Auto DSN = on
Init = ATX3
ISDN = 0
Dock = on
Username = Telecom
Password = Telecom
Carrier Check = off
Auto Reconnect = on
ubu@ubu-desktop:~$
ho già aggiunto io "Carrier Check = off" (l'altra volta avevo scritto male!).
Ora funziona bene tranne che ora mi mette dei punti di domanda "?" (indirizzi IP) invece che dei numeri:
root@ubu-desktop:~# ./dialup
Shutting down SmartLink Modem driver normally.
Unloading modem driver from kernel ... slamr.
Starting SmartLink Modem driver for: slamr0.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATX3
ATX3
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 +MS=90
OK
--> Modem initialized.
--> Sending: ATM1L3DT7020187187
--> Waiting for carrier.
ATM1L3DT7020187187
CONNECT 46667
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Wed Oct 29 09:11:03 2008
--> Pid of pppd: 8331
--> Using interface ppp0
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> pppd: ��[06][08]��[06][08]
--> local IP address 80.104.14.216
--> pppd: ��[06][08]��[06][08]
--> remote IP address 217.141.106.6
--> pppd: ��[06][08]��[06][08]
--> primary DNS address 62.211.69.150
--> pppd: ��[06][08]��[06][08]
--> secondary DNS address 212.48.4.15
--> pppd: ��[06][08]��[06][08]
Comunque si connette bene!!!!!
Grazie Mille ancora.
-
antuneleta
- Prode Principiante
- Messaggi: 23
- Iscrizione: sabato 19 luglio 2008, 11:37
Re: [Risolto] Motorola SM56 Data Fax Modem - problema con "make"
ciao a tutti!! (b2b)
Sono passata a Linux da qualche giorno e oggi mi sono cimentata a installare il modem motorola integrato nel portatile seguendo le istruzioni della pagina http://wiki.ubuntu-it.org/Hardware/Modem/Dialup/MotorolaSm56. Purtroppo si verificano problemi col make.
A questo punto, ho le mani legate e non so più come muovermi...
Allego il testo del file ModemData ottenuto con scanModem (normalmente mi connetto col wireless Intel ma ho bisogno del modem 56k che non viene rilevato)
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
scanModem update of: 2008_11_06
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 1d6b:0002 Linux Foundation 2.0 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
USB modems not recognized
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:2668 1734:107c Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
16: 612169 IO-APIC-fasteoi uhci_hcd:usb4, sata_via, HDA Intel, radeon@pci:0000:03:00.0
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.577798] PCI: 0000:00:1b.0 reg 10 64bit mmio: [ffef8000, ffefbfff]
[ 0.577837] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.577842] pci 0000:00:1b.0: PME# disabled
[ 17.368161] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 17.368188] HDA Intel 0000:00:1b.0: setting latency timer to 64
The PCI slot 00:1b.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.17
The modem cards detected by "aplay -l" are:
scheda 0: Intel [HDA Intel], dispositivo 6: Si3054 Modem [Si3054 Modem]
The /proc/asound/pcm file reports:
-----------------------
00-04: ALC880 Analog : ALC880 Analog : capture 2
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 1
00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xffef8000 irq 16
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.27-9-generic/kernel/sound/pci/hda/snd-hda-intel.ko
If not a Conexant modem, the driver snd-hda-intel with its dependent drivers:
snd_hda_intel 381488 3
snd_pcm 83204 2 snd_hda_intel,snd_pcm_oss
snd 63268 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
snd_page_alloc 16136 2 snd_hda_intel,snd_pcm
----------
provide audio + modem support with the modem chip residing on the subsystem.
Any particular card can host any one of several soft modem chips.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset detected on
NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
CLASS=0403
PCIDEV=8086:2668
SUBSYS=1734:107c
IRQ=16
HDA=8086:2668
SOFT=8086:2668.HDA
ArchivedChip=0x10573055
IDENT=slmodemd
SLMODEMD_DEVICE=hw:0,6
Driver=snd-hda-intel
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:2668
Subsystem PCI_id 1734:107c
Softmodem codec or chipset from diagnostics:
from Archives: 0x10573055
Support type needed or chipset: slmodemd supporting the snd-hda-intel audio+modem driver
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-hda-intel
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.3.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.3.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.3.2
and the compiler used in kernel assembly: 4.3.2
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.27-9-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch ... 04656.html
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1
Which can interfere with Browser naviagation.
Don't worry about the following, it is for 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:
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
un saluto! :-)
Sono passata a Linux da qualche giorno e oggi mi sono cimentata a installare il modem motorola integrato nel portatile seguendo le istruzioni della pagina http://wiki.ubuntu-it.org/Hardware/Modem/Dialup/MotorolaSm56. Purtroppo si verificano problemi col make.
A questo punto, ho le mani legate e non so più come muovermi...
Allego il testo del file ModemData ottenuto con scanModem (normalmente mi connetto col wireless Intel ma ho bisogno del modem 56k che non viene rilevato)
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
scanModem update of: 2008_11_06
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 1d6b:0002 Linux Foundation 2.0 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
USB modems not recognized
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:2668 1734:107c Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
16: 612169 IO-APIC-fasteoi uhci_hcd:usb4, sata_via, HDA Intel, radeon@pci:0000:03:00.0
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.577798] PCI: 0000:00:1b.0 reg 10 64bit mmio: [ffef8000, ffefbfff]
[ 0.577837] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.577842] pci 0000:00:1b.0: PME# disabled
[ 17.368161] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 17.368188] HDA Intel 0000:00:1b.0: setting latency timer to 64
The PCI slot 00:1b.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.17
The modem cards detected by "aplay -l" are:
scheda 0: Intel [HDA Intel], dispositivo 6: Si3054 Modem [Si3054 Modem]
The /proc/asound/pcm file reports:
-----------------------
00-04: ALC880 Analog : ALC880 Analog : capture 2
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 1
00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xffef8000 irq 16
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.27-9-generic/kernel/sound/pci/hda/snd-hda-intel.ko
If not a Conexant modem, the driver snd-hda-intel with its dependent drivers:
snd_hda_intel 381488 3
snd_pcm 83204 2 snd_hda_intel,snd_pcm_oss
snd 63268 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
snd_page_alloc 16136 2 snd_hda_intel,snd_pcm
----------
provide audio + modem support with the modem chip residing on the subsystem.
Any particular card can host any one of several soft modem chips.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset detected on
NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
CLASS=0403
PCIDEV=8086:2668
SUBSYS=1734:107c
IRQ=16
HDA=8086:2668
SOFT=8086:2668.HDA
ArchivedChip=0x10573055
IDENT=slmodemd
SLMODEMD_DEVICE=hw:0,6
Driver=snd-hda-intel
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:2668
Subsystem PCI_id 1734:107c
Softmodem codec or chipset from diagnostics:
from Archives: 0x10573055
Support type needed or chipset: slmodemd supporting the snd-hda-intel audio+modem driver
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-hda-intel
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.3.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.3.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.3.2
and the compiler used in kernel assembly: 4.3.2
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.27-9-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ .
For martian_modem, additional required packages are needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed packages.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch ... 04656.html
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1
Which can interfere with Browser naviagation.
Don't worry about the following, it is for 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:
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
un saluto! :-)
aNtUnElEtA
meglio pentirsi di averci provato che pentirsi di non averci provato affatto.
meglio pentirsi di averci provato che pentirsi di non averci provato affatto.
Re: [Risolto] Motorola SM56 Data Fax Modem - problema con "make"
Ciao antuneleta,
prova a seguire questa procedura http://jeanpierree.wordpress.com/2008/1 ... ibex/ 
poi fammi sapere com'è andata!!
prova a seguire questa procedura http://jeanpierree.wordpress.com/2008/1 ... ibex/
poi fammi sapere com'è andata!!
Chi c’è in linea
Visualizzano questa sezione: 0 utenti iscritti e 12 ospiti