Ciao a tutti. Ho un problema a far funzionare due diverse chiavette internet ognuna con due gestori telefonici differenti sul mio acer aspire one a150 aw che monta al suo interno il sistema operativo Fedora 16. La chiavetta wind, di cui il comando lsusb dà come risultato ID 1bbb:0017 T & A Mobile Phones, ha funzionato sino a ieri; ogni volta che la inserivo dopo pochi secondi mi chiedeva il codice pin e poi si connetteva tramite nm. Da oggi invece non mi chiede più il pin; lsusb la visualizza ancora, ma la voce broadband non appare più in nm. Ho provato anche a togliere il pin, ma succede la stessa cosa, non viene più letta.
Con l’altra chiavetta invece, una K3806Z HSPA della vodafone, sempre tramite nm viene vista e si collega persino ad internet, però non naviga né su browser né da terminal. So che si collega perché la lucetta della key appena il collegamento viene effettuato si accende fissa, e l’icona della connessione mostra le tacche della banda, in più il credito diminuisce.
Per questa stessa chiavetta vodafone ho provato sakis3g che lo stesso, dopo averla connessa, non consente la navigazione né da terminal né da browser.
Chi mi aiuta a farne funzionare almeno una? Preferibilmente quella wind che sembra più facile da gestire, e soprattutto ha già funzionato.
ciao
benvenuto.
cominciamo con quella wind
togli la chiavetta, rimettila, aspetta 30 secondi e posta l’output di:
# tail -n 60 /var/log/messages[root@riddik Pettirosso]# tail -n 60 /var/log/messages
Jan 9 18:04:53 riddik NetworkManager[948]: (p1p1): deactivating device (reason ‘managed’) [2]
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (p1p1): deactivating device (reason ‘managed’) [2]
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): now managed
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): now managed
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): device state change: unmanaged -> unavailable (reason ‘managed’) [10 20 2]
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): bringing up device.
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): device state change: unmanaged -> unavailable (reason ‘managed’) [10 20 2]
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): bringing up device.
Jan 9 18:04:53 riddik kernel: 1354.124042] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): preparing device.
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): deactivating device (reason ‘managed’) [2]
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): preparing device.
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): deactivating device (reason ‘managed’) [2]
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): supplicant interface state: starting -> ready
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): device state change: unavailable -> disconnected (reason ‘supplicant-available’) [20 30 42]
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): supplicant interface state: starting -> ready
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): device state change: unavailable -> disconnected (reason ‘supplicant-available’) [20 30 42]
Jan 9 18:04:53 riddik NetworkManager[948]: (wlan0): supplicant interface state: ready -> inactive
Jan 9 18:04:53 riddik NetworkManager[948]: NetworkManager[948]: (wlan0): supplicant interface state: ready -> inactive
Jan 9 18:04:54 riddik dbus-daemon[998]: dbus[998]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jan 9 18:04:54 riddik dbus[998]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jan 9 18:04:54 riddik dbus-daemon[998]: Launching FprintObject
Jan 9 18:04:54 riddik dbus-daemon[998]: dbus[998]: [system] Successfully activated service ‘net.reactivated.Fprint’
Jan 9 18:04:54 riddik dbus[998]: [system] Successfully activated service ‘net.reactivated.Fprint’
Jan 9 18:04:54 riddik dbus-daemon[998]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jan 9 18:04:54 riddik dbus-daemon[998]: ** Message: entering main loop
Jan 9 18:04:55 riddik kernel: 1355.686102] usb 1-1: new high speed USB device number 14 using ehci_hcd
Jan 9 18:04:55 riddik kernel: 1355.806048] usb 1-1: New USB device found, idVendor=1bbb, idProduct=f000
Jan 9 18:04:55 riddik kernel: 1355.806060] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Jan 9 18:04:55 riddik kernel: 1355.806069] usb 1-1: Product: HSPA Data Card
Jan 9 18:04:55 riddik kernel: 1355.806075] usb 1-1: Manufacturer: USBModem
Jan 9 18:04:55 riddik kernel: 1355.806081] usb 1-1: SerialNumber: 1234567890ABCDEF
Jan 9 18:04:55 riddik kernel: 1355.821148] scsi11 : usb-storage 1-1:1.0
Jan 9 18:04:55 riddik mtp-probe: checking bus 1, device 14: “/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1”
Jan 9 18:04:55 riddik mtp-probe: bus: 1, device: 14 was not an MTP device
Jan 9 18:04:56 riddik logger: usb_modeswitch: using overriding config file /etc/usb_modeswitch.d/1bbb:f000; make sure this is intended
Jan 9 18:04:56 riddik logger: usb_modeswitch: please report any new or corrected settings; otherwise, check for outdated files
Jan 9 18:04:56 riddik usb_modeswitch: switching 1bbb:f000 (USBModem: HSPA Data Card)
Jan 9 18:04:56 riddik kernel: 1356.591622] usb 1-1: USB disconnect, device number 14
Jan 9 18:04:56 riddik kernel: 1356.902218] usb 1-1: new high speed USB device number 15 using ehci_hcd
Jan 9 18:04:56 riddik kernel: 1357.019555] usb 1-1: New USB device found, idVendor=1bbb, idProduct=0017
Jan 9 18:04:56 riddik kernel: 1357.019577] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Jan 9 18:04:56 riddik kernel: 1357.019594] usb 1-1: Product: HSPA Data Card
Jan 9 18:04:56 riddik kernel: 1357.019607] usb 1-1: Manufacturer: USBModem
Jan 9 18:04:56 riddik kernel: 1357.019620] usb 1-1: SerialNumber: 1234567890ABCDEF
Jan 9 18:04:56 riddik kernel: 1357.028083] scsi12 : usb-storage 1-1:1.4
Jan 9 18:04:57 riddik usb_modeswitch: switched to 1bbb:0017 (USBModem: HSPA Data Card)
Jan 9 18:04:57 riddik mtp-probe: checking bus 1, device 15: “/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1”
Jan 9 18:04:57 riddik mtp-probe: bus: 1, device: 15 was not an MTP device
Jan 9 18:04:57 riddik kernel: 1358.035861] scsi 12:0:0:0: Direct-Access ALCATEL Mass Storage 2.31 PQ: 0 ANSI: 2
Jan 9 18:04:57 riddik kernel: 1358.040658] sd 12:0:0:0: Attached scsi generic sg1 type 0
Jan 9 18:04:57 riddik kernel: 1358.043342] sd 12:0:0:0: [sdb] Attached SCSI removable disk
Jan 9 18:05:24 riddik dbus-daemon[998]: ** Message: No devices in use, exit
Jan 9 18:06:47 riddik dbus[998]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jan 9 18:06:47 riddik dbus-daemon[998]: dbus[998]: [system] Activating service name=‘net.reactivated.Fprint’ (using servicehelper)
Jan 9 18:06:47 riddik dbus-daemon[998]: Launching FprintObject
Jan 9 18:06:47 riddik dbus[998]: [system] Successfully activated service ‘net.reactivated.Fprint’
Jan 9 18:06:47 riddik dbus-daemon[998]: dbus[998]: [system] Successfully activated service ‘net.reactivated.Fprint’
Jan 9 18:06:47 riddik dbus-daemon[998]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Jan 9 18:06:47 riddik dbus-daemon[998]: ** Message: entering main loop
collegati via cavo o con altro dispositivo e dai il comando:
# yum downgrade usb_modeswitch*
conferma il downgrade, dai un reboot alla macchina.
vedi ora come va.
Purtroppo non ne ho possibilità, non esiste un’alternativa? Altrimenti posso far passare con cavo ethernet la linea della internet mobile dal pc dove funziona sino al portatile?
Niente da fare con connessioni via cavo. Non posso effettuare il downgrade in altra maniera?
fedora 16 32 bit o 64 bit ?
output di:
$ uname -aLinux riddik.localspace fedora 3.1.6-1.fc16.i686 #1 SMP Wed Dec 21 23:18:01 UTC 2011 i686 i686 i386 GNU/Linux
scaricati i pacchetti:
http://fedora.mirror.garr.it/mirrors/fedora/linux/releases/16/Everything/i386/os/Packages/usb_modeswitch-1.1.7-1.fc16.i686.rpm
http://fedora.mirror.garr.it/mirrors/fedora/linux/releases/16/Everything/i386/os/Packages/usb_modeswitch-data-20110714-1.fc16.noarch.rpm
con altra macchina, mettili su di una pennetta e copiali sulla macchina fedora, poi dai i comandi:
da root:
[code]# rpm -e --nodeps usb_modeswitch usb_modeswitch-data
cd /percorso/dove/sitrovano/i_pacchetti/usb_modeswitch
rpm -ivh --force usb_modeswitch usb_modeswitch-data[/code]
dai un reboot.
prova ora.
Mission Accomplished! E te ne sono molto grato! 
Ma qual era grosso modo il problema di usb modeswitch?
l’ultima versione di usb_modeswitch ha una regressione su alcune pennette.
escludilo dagli aggiornamenti fino a quando non hai notizia che il problema è rientrato.
E’ stato yum update di ieri allora ad avero compromesso il suo funzionamento. Come posso escluerlo dai prossimi aggiornamenti? Mi converrà ripetere questa stessa operazione suppongo.
lo escludi dando il comando:
# yum update --exclude=usb_modeswitch*ciao io ho lo stesso problema con chiavetta vodafone, cioè si collega ma non naviga con il network manager.
ho il usb_modeswitch-1.2.2-2.fc16.x86_64
dovrei risolvere anche io con un downgrade?
Usando lo script sakis3g navigo correttamente (anche se devo inserire a mano i dns)
vedere output di:
$ lsusba chiavetta inserita.
ciao , Virus!
il print è il seguente
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 005: ID 19d2:1015 ONDA Communication S.p.A.
Bus 002 Device 006: ID 04e8:60a6 Samsung Electronics Co., Ltd ciao,
togli e metti la pennetta e ci fai vedere:
# tail -n 60 /var/log/messagesMar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ttyACM0) opening serial port...
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) opening serial port...
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port ttyACM0
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port ttyACM0
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ttyACM1) closing serial port...
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM1) closing serial port...
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ttyACM1) serial port closed
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM1) serial port closed
Mar 7 20:10:58 mbisi-var modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port ttyACM1
Mar 7 20:10:58 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port ttyACM1
Mar 7 20:10:59 mbisi-var modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:10:59 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:10:59 mbisi-var modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:10:59 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:11:01 mbisi-var modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port usb0
Mar 7 20:11:01 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ZTE): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 claimed port usb0
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): now unmanaged
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): cleaning up...
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): taking down device.
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): now unmanaged
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): cleaning up...
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): taking down device.
Mar 7 20:11:01 mbisi-var vmnetBridge: RTM_NEWLINK: name:usb0 index:7 flags:0x00001002
Mar 7 20:11:01 mbisi-var vmnet-natd: RTM_NEWLINK: name:usb0 index:7 flags:0x00001002
Mar 7 20:11:01 mbisi-var avahi-daemon[970]: Withdrawing address record for fe80::e3:77ff:fef7:735b on usb0.
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): new GSM/UMTS device (driver: 'cdc_acm' ifindex: 7)
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): exported as /org/freedesktop/NetworkManager/Devices/3
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): now managed
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): deactivating device (reason 'managed') [2]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): new GSM/UMTS device (driver: 'cdc_acm' ifindex: 7)
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): exported as /org/freedesktop/NetworkManager/Devices/3
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): now managed
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): deactivating device (reason 'managed') [2]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: <info> (usb0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Mar 7 20:11:01 mbisi-var NetworkManager[942]: NetworkManager[942]: <info> (usb0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Mar 7 20:12:14 mbisi-var modem-manager[1011]: <info> (ttyACM0) opening serial port...
Mar 7 20:12:14 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) opening serial port...
Mar 7 20:12:15 mbisi-var modem-manager[1011]: <info> Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required
Mar 7 20:12:15 mbisi-var modem-manager[1011]: <info> Modem /org/freedesktop/ModemManager/Modems/0: # unlock retries is 0
Mar 7 20:12:15 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required
Mar 7 20:12:15 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> Modem /org/freedesktop/ModemManager/Modems/0: # unlock retries is 0
Mar 7 20:12:15 mbisi-var modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:12:15 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) closing serial port...
Mar 7 20:12:15 mbisi-var modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:12:15 mbisi-var dbus-daemon[999]: modem-manager[1011]: <info> (ttyACM0) serial port closed
Mar 7 20:12:36 mbisi-var dbus[999]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Mar 7 20:12:36 mbisi-var dbus-daemon[999]: dbus[999]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Mar 7 20:12:36 mbisi-var dbus-daemon[999]: Launching FprintObject
Mar 7 20:12:36 mbisi-var dbus[999]: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 7 20:12:36 mbisi-var dbus-daemon[999]: dbus[999]: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 7 20:12:36 mbisi-var dbus-daemon[999]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 7 20:12:36 mbisi-var dbus-daemon[999]: ** Message: entering main loopgrazie!
dai il comando con la rete attiva da root:
# yum install rp-pppoedai un reboot e riprova la pennetta.
[quote=virus]dai il comando con la rete attiva da root:
# yum install rp-pppoedai un reboot e riprova la pennetta.[/quote]
Palo
Package rp-pppoe-3.10-9.fc16.x86_64 already installed and latest version