Errore all'inserimento chiavetta Onda mt825up

Buona giornata.

Sempre con lo spirito di imparare la prassi per segnalare problemi, condivido quello che accade sul mio sistema.

Fino a qualche giorno fa (non riesco ad essere preciso perché non usavo il pc da giorni) io utilizzavo la chiavetta in oggetto senza alcun problema in Fedora 17, anche se con qualche problema relativo all’ordine con cui effettuavo le operazioni (la chiavetta doveva essere inserita prima del boot di fedora oppure se inserita dopo il boot dovevo fare un chiudi sessione affinche non mi partisse di nuovo il wizard per la creazione di una connessione 3g).

Dopo l’ultimo aggiornamento del kernel (kernel-PAE-3.6.8-2.fc17.i686) inserendo la pennetta dalla modalità grafica il pc mi passa a quella testo che “spara” due pagine velocissime e poi si ferma di fatto bloccando il sistema.

Ho provato a fare il boot (sia a caldo con il reset che a freddo) ma con la pennetta inserita il sistema non va avanti (si ferma quando la F di fedora si riempe).

Grazie ai consigli di precedenti post degli amministratori del forum ho sempre cancellato i kernel che non usavo (perché mi avevano segnalato che dopo 3 kernel con l’update di un quarto veniva cancellato automaticamente l’ultimo a meno di interventi manuali su dei files che al momento io evito per ovvie ragioni di incompetenza) mantenendo sempre quello primario che funziona sempre (scrivo con la pennetta inserita con un altro kernel)

Se non inserisco la pennetta il sistema con l’ultimo kernel fa il boot ed in basso vedo il “bug reporter” (non so come si chiama correttamente) che effettivamente mi segnala dei problemi, ma non posso “inviarli” perche non ho la connessione internet (mi ricorda la situazione di errore delle bios che dice “tastiera non trovata, premere f1 per continuare” :wink: ).

Quali sono i passi da fare per poter recuperare i dati per la risoluzione del problema?

P.S: usando una connessione wi-fi il pc si collega ad internet. Questo soluzione non posso usarla per spedire il report perché la prova è stata fatto usando il cellulare di un amico come hotspot.

Grazie

inserisci la pennetta col kernel che non funziona, aspetta una decina di secondi,poi dai i comandi da root:

[code]# lsusb

tail -n 80 /var/log/messages[/code]

posta gli output.

O_O Virus sei un bot, dici la verità, mica sei un umano?

A volte mi preoccupo e mi guardo con sospetto dietro la sedia per vedere se sei li ad aspettare che immetta una domanda!! Complimenti.

Adesso mi scollego e provo l’operazione che mi hai detto, ma ti chiedo:

i messaggi del log che creò fedora li salva da qualche parte oppure devo fare uno screenshot dello stesso?

magari sono solo due righe e basta copiarsele a mano ma a volte ho visto listati lunghissimi.

Intanto provo e vediamo quanto sono lunghi.

Buona appettito ovviamente.

dopo il comando che ha suggerito virus è sufficiente fare un copia/incolla dal terminale al forum. Usando magari il tag code ] (il pulsante a sinistra delle faccine)

p.s. Virus non è né un bot né un umano. è un uraniano, per questo ha doti che per noi sembrano eccezionali.

i log li salva tutti nella directory /var/log/
dipende da quale ti interessa, per quelli generici devi consultare /var/log/messages
per quelli di lancio servizi /var/log/boot.log
per quelli di dracut /var/log/dracut.log
per quelli del server X /var/log/Xorg.0.log
per quelli di sicurezza /var/log/secure
per quelli del display manager /var/log/gdm…

ma ti conviene rispondere alle mie domande, invece di porne altre.

AVE Virus

io trovo invece interessante le risposte aggiuntive, sempre nell’ottica dell’imparare e non ti essere sempre solo assistito.

Torniamo al punto.

Devo essermi spiegato male rispetto alla situazione in cui si trova il sistema dopo l’inserimento della pennetta, almeno a giudicare dalle richieste di Yattatux.

Ho ricreato la situazione e quello che mi trovo è una schermata in cui oltre tutti i messaggi numerati (sono tra parentesi quadrate con numeri progressivi, quasi fossero le righe di un codice) è uno stallo.

Ho aspettato più di un minuto ma nulla cambiava. Si Vede anche l’icona trasparente del mouse che riesco a muovere ma ovviamente non c’è interfaccia grafica.

Ho provato allora ad “uscire” da questa situazione cliccando su CTRL+C ed in effetti è apparsa una riga vuota senza cursore.

Qualsiasi tasto premevo avevo la echo sullo schermo (^C, tastierino numerico etc.) ma nessuna reazione.

Ho provato con comandi tipo exit e quit seguiti da invio ma rimanevo in questa specie di limbo.

Ho riavviato e mi sono collegato con il vecchio kernel.

Dove recupero i dati che vi servono e partendo da quale kernel?

Grazias

io non ho fatto alcuna richiesta, ho ribadito quello che ti aveva chiesto Virus chiedendoti di postare nel tag code ], ovvero [quote=virus]inserisci la pennetta col kernel che non funziona, aspetta una decina di secondi,poi dai i comandi da root:

[code]# lsusb

tail -n 80 /var/log/messages[/code]

posta gli output.[/quote]
Tutto qui. :slight_smile:

Per postare qualche dato, ho lanciato il kernel funzionante e dato i comandi da console come richiesto, ed ho imparato che il primo serve ad elencare le periferice sub collegate e come le vede il kernel, +1

lsusb 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 1ee8:000b Bus 003 Device 002: ID 0e8f:0012 GreenAsia Inc. USB Wireless 2.4GHz Gamepad Bus 003 Device 003: ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R) Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Bus 004 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse Bus 004 Device 003: ID 045e:0750 Microsoft Corp. Wired Keyboard 600

La pennetta era collegata quando ho dato questo comando.

Poi

tail -n 80 /var/log/messages Dec 10 14:18:02 phenom rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="727" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

e questo non so cosa sia è mi devo documentare

Ho letto la documetazione di tail [MAN TAIL]

ed ho capito cosa cercava virus per cui ho fatto così

tail -n 80 /var/log/messages-20121210 Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) starting connection 'TIM Lucio' Dec 10 13:38:28 phenom NetworkManager[683]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0] Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete. Dec 10 13:38:28 phenom dbus-daemon[746]: modem-manager[769]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting) Dec 10 13:38:28 phenom modem-manager[769]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting) Dec 10 13:38:28 phenom dbus-daemon[746]: modem-manager[769]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected) Dec 10 13:38:28 phenom modem-manager[769]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected) Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled... Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting... Dec 10 13:38:28 phenom NetworkManager[683]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0] Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful. Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled. Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete. Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started... Dec 10 13:38:28 phenom NetworkManager[683]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0] Dec 10 13:38:28 phenom NetworkManager[683]: <info> starting PPP connection Dec 10 13:38:28 phenom NetworkManager[683]: <info> pppd started with pid 1381 Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete. Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started... Dec 10 13:38:28 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete. Dec 10 13:38:28 phenom pppd[1381]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Dec 10 13:38:28 phenom NetworkManager[683]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Dec 10 13:38:28 phenom kernel: 148.522863] PPP generic driver version 2.4.2 Dec 10 13:38:28 phenom pppd[1381]: pppd 2.4.5 started by root, uid 0 Dec 10 13:38:28 phenom pppd[1381]: Using interface ppp0 Dec 10 13:38:28 phenom pppd[1381]: Connect: ppp0 <--> /dev/ttyUSB1 Dec 10 13:38:28 phenom NetworkManager[683]: Using interface ppp0 Dec 10 13:38:28 phenom NetworkManager[683]: Connect: ppp0 <--> /dev/ttyUSB1 Dec 10 13:38:28 phenom NetworkManager[683]: Remote message: Icera PPP - Password Verified OK Dec 10 13:38:28 phenom NetworkManager[683]: PAP authentication succeeded Dec 10 13:38:28 phenom pppd[1381]: Remote message: Icera PPP - Password Verified OK Dec 10 13:38:28 phenom pppd[1381]: PAP authentication succeeded Dec 10 13:38:28 phenom NetworkManager[683]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Dec 10 13:38:28 phenom kernel: 148.665698] PPP BSD Compression module registered Dec 10 13:38:28 phenom kernel: 148.681074] PPP Deflate Compression module registered Dec 10 13:38:31 phenom pppd[1381]: local IP address 62.18.238.59 Dec 10 13:38:31 phenom pppd[1381]: remote IP address 10.0.0.1 Dec 10 13:38:31 phenom pppd[1381]: primary DNS address 213.230.130.222 Dec 10 13:38:31 phenom pppd[1381]: secondary DNS address 217.200.200.42 Dec 10 13:38:31 phenom NetworkManager[683]: <info> PPP manager(IP Config Get) reply received. Dec 10 13:38:31 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Dec 10 13:38:31 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started... Dec 10 13:38:31 phenom NetworkManager[683]: local IP address 62.18.238.59 Dec 10 13:38:31 phenom NetworkManager[683]: remote IP address 10.0.0.1 Dec 10 13:38:31 phenom NetworkManager[683]: primary DNS address 213.230.130.222 Dec 10 13:38:31 phenom NetworkManager[683]: secondary DNS address 217.200.200.42 Dec 10 13:38:32 phenom NetworkManager[683]: <info> (ttyUSB1): device state change: ip-config -> activated (reason 'none') [70 100 0] Dec 10 13:38:32 phenom NetworkManager[683]: <info> Policy set 'TIM Lucio' (ppp0) as default for IPv4 routing and DNS. Dec 10 13:38:32 phenom NetworkManager[683]: <info> Activation (ttyUSB1) successful, device activated. Dec 10 13:38:32 phenom NetworkManager[683]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete. Dec 10 13:38:32 phenom dbus-daemon[746]: dbus[746]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Dec 10 13:38:32 phenom dbus[746]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Dec 10 13:38:32 phenom dbus-daemon[746]: dbus[746]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 10 13:38:32 phenom dbus[746]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 10 13:38:33 phenom systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start. Dec 10 13:38:34 phenom systemd[1]: PID 827 read from file /run/sm-client.pid does not exist. Dec 10 13:51:00 phenom systemd-tmpfiles[1539]: stat(/run/user/nexus6/gvfs) failed: Permission denied Dec 10 13:51:38 phenom dbus-daemon[746]: dbus[746]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.2" (uid=0 pid=714 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.34" (uid=1000 pid=972 comm="gnome-session ") Dec 10 13:51:38 phenom dbus[746]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.2" (uid=0 pid=714 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.34" (uid=1000 pid=972 comm="gnome-session ") Dec 10 14:05:44 phenom dbus-daemon[746]: dbus[746]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 14:05:44 phenom dbus[746]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 14:05:44 phenom dbus-daemon[746]: Launching FprintObject Dec 10 14:05:44 phenom dbus-daemon[746]: dbus[746]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 14:05:44 phenom dbus[746]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 14:05:44 phenom dbus-daemon[746]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 10 14:05:44 phenom dbus-daemon[746]: ** Message: entering main loop Dec 10 14:05:48 phenom dbus-daemon[746]: dbus[746]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.2" (uid=0 pid=714 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.34" (uid=1000 pid=972 comm="gnome-session ") Dec 10 14:05:48 phenom dbus[746]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.2" (uid=0 pid=714 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.34" (uid=1000 pid=972 comm="gnome-session ") Dec 10 14:06:14 phenom dbus-daemon[746]: ** Message: No devices in use, exit Dec 10 14:14:35 phenom dbus-daemon[746]: dbus[746]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 14:14:35 phenom dbus[746]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 14:14:35 phenom dbus-daemon[746]: Launching FprintObject Dec 10 14:14:35 phenom dbus-daemon[746]: dbus[746]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 14:14:35 phenom dbus-daemon[746]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 10 14:14:35 phenom dbus-daemon[746]: ** Message: entering main loop Dec 10 14:14:35 phenom dbus[746]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 14:15:06 phenom dbus-daemon[746]: ** Message: No devices in use, exit

In sostanza per i niubbi come me, ho capito che quando un files di log diventa troppo grande, il sistema ne crea uno nuovo ed archivia quello precedente con la data in cui effettua l’archiviazione. Interessante.

Tornando al problema non so se può essere indicativo quello postato, magari se mi dici cosa cercare mi smazzo io a leggere il files log intero per la data di oggi.

Mi sono portato un po’ avanti con il lavoro Virus.

Profittando del fatto che il files log era pulito (aveva solo una riga) mi sono scollegato, ho ricreato la situazione di blocco e mi sono ricollegato con il kernel funzionante.

Cosi ho una serie di messaggi ad un ora precisa relativa al problema e ti ho tirato fuori il TAIL lungo abbastanza per contenere quelli che FORSE sono i messaggi che chiedevi (mancano tutti quelli iniziali che sembrano gli stessi di tutti gli altri orari e credo si riferiscano sempre all’hardware in uso, etc.)

Fammi sapere

Dec 10 14:41:33 phenom NetworkManager[715]: <info> trying to start the modem manager...
Dec 10 14:41:33 phenom NetworkManager[715]: <info> monitoring kernel firmware directory '/lib/firmware'.
Dec 10 14:41:33 phenom dbus[771]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Dec 10 14:41:33 phenom dbus-daemon[771]: dbus[771]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  ModemManager (version 0.6.0.0-1.fc17) starting...
Dec 10 14:41:33 phenom modem-manager[789]: <info>  ModemManager (version 0.6.0.0-1.fc17) starting...
Dec 10 14:41:33 phenom dbus[771]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 10 14:41:33 phenom dbus-daemon[771]: dbus[771]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 10 14:41:33 phenom kernel:    20.651919] ADDRCONF(NETDEV_UP): p6p1: link is not ready
Dec 10 14:41:33 phenom kernel:    20.651986] ATL1E 0000:02:00.0: p6p1: NIC Link is Up <1000 Mbps Full Duplex>
Dec 10 14:41:33 phenom kernel:    20.652173] ADDRCONF(NETDEV_CHANGE): p6p1: link becomes ready
Dec 10 14:41:33 phenom NetworkManager[715]: <info> WiFi enabled by radio killswitch; enabled by state file
Dec 10 14:41:33 phenom NetworkManager[715]: <info> WWAN enabled by radio killswitch; enabled by state file
Dec 10 14:41:33 phenom NetworkManager[715]: <info> WiMAX enabled by radio killswitch; enabled by state file
Dec 10 14:41:33 phenom NetworkManager[715]: <info> Networking is enabled by state file
Dec 10 14:41:33 phenom NetworkManager[715]: <warn> failed to allocate link cache: (-10) Operation not supported
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): carrier is OFF
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): new Ethernet device (driver: 'ATL1E' ifindex: 2)
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): exported as /org/freedesktop/NetworkManager/Devices/0
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): now managed
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): bringing up device.
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): preparing device.
Dec 10 14:41:33 phenom dbus[771]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): deactivating device (reason 'managed') [2]
Dec 10 14:41:33 phenom NetworkManager[715]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Dec 10 14:41:33 phenom NetworkManager[715]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Dec 10 14:41:33 phenom bluetoothd[790]: Bluetooth daemon 4.99
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'X22X'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Option'
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): carrier now ON (device state 20)
Dec 10 14:41:33 phenom NetworkManager[715]: <info> modem-manager is now available
Dec 10 14:41:33 phenom NetworkManager[715]: <info> (p6p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Dec 10 14:41:33 phenom dbus[771]: [system] Successfully activated service 'org.bluez'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Ericsson MBM'
Dec 10 14:41:33 phenom bluetoothd[790]: Starting SDP server
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'MotoC'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Option High-Speed'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Huawei'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Longcheer'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'AnyData'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Wavecom'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Gobi'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Nokia'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'SimTech'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Sierra'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Novatel'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'ZTE'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Samsung'
Dec 10 14:41:33 phenom kernel:    20.726332] Bluetooth: Core ver 2.16
Dec 10 14:41:33 phenom kernel:    20.726383] NET: Registered protocol family 31
Dec 10 14:41:33 phenom kernel:    20.726384] Bluetooth: HCI device and connection manager initialized
Dec 10 14:41:33 phenom kernel:    20.726386] Bluetooth: HCI socket layer initialized
Dec 10 14:41:33 phenom kernel:    20.726388] Bluetooth: L2CAP socket layer initialized
Dec 10 14:41:33 phenom kernel:    20.726392] Bluetooth: SCO socket layer initialized
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Linktop'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Cinterion'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Iridium'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Loaded plugin 'Generic'
Dec 10 14:41:33 phenom modem-manager[789]: <info>  Successfully loaded 20 plugins
Dec 10 14:41:33 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'X22X'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Option'
Dec 10 14:41:33 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'org.bluez'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Ericsson MBM'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'MotoC'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Option High-Speed'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Huawei'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Longcheer'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'AnyData'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Wavecom'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Gobi'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Nokia'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'SimTech'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Sierra'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Novatel'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'ZTE'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Samsung'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Linktop'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Cinterion'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Iridium'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Loaded plugin 'Generic'
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  Successfully loaded 20 plugins
Dec 10 14:41:33 phenom bluetoothd[790]: bluetoothd[790]: Bluetooth daemon 4.99
Dec 10 14:41:33 phenom bluetoothd[790]: bluetoothd[790]: Starting SDP server
Dec 10 14:41:33 phenom bluetoothd[790]: bluetoothd[790]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Dec 10 14:41:33 phenom kernel:    20.742045] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec 10 14:41:33 phenom kernel:    20.742048] Bluetooth: BNEP filters: protocol multicast
Dec 10 14:41:33 phenom bluetoothd[790]: bluetoothd[790]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Dec 10 14:41:33 phenom bluetoothd[790]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Dec 10 14:41:33 phenom bluetoothd[790]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB0) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB0) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB0): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB1) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB1): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB2) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB2): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB3) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB3): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB4) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB4): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB5) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB5): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB6) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB6): port attributes not fully set
Dec 10 14:41:33 phenom modem-manager[789]: <info>  (ttyUSB7) opening serial port...
Dec 10 14:41:33 phenom modem-manager[789]: <warn>  (ttyUSB7): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB0): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB1): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB2) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB2): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB3) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB3): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB4) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB4): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB5) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB5): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB6) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB6): port attributes not fully set
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB7) opening serial port...
Dec 10 14:41:33 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB7): port attributes not fully set
Dec 10 14:41:33 phenom systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start.
Dec 10 14:41:33 phenom kernel:    20.846189] RPC: Registered named UNIX socket transport module.
Dec 10 14:41:33 phenom kernel:    20.846197] RPC: Registered udp transport module.
Dec 10 14:41:33 phenom kernel:    20.846202] RPC: Registered tcp transport module.
Dec 10 14:41:33 phenom kernel:    20.846206] RPC: Registered tcp NFSv4.1 backchannel transport module.
Dec 10 14:41:33 phenom rpc.statd[824]: Version 1.2.6 starting
Dec 10 14:41:33 phenom sm-notify[825]: Version 1.2.6 starting
Dec 10 14:41:35 phenom avahi-daemon[743]: Registering new address record for fe80::226:18ff:fe9c:b483 on p6p1.*.
Dec 10 14:41:35 phenom systemd[1]: Startup finished in 2s 528ms 139us (kernel) + 3s 927ms 790us (initrd) + 15s 864ms 263us (userspace) = 22s 320ms 192us.
Dec 10 14:41:35 phenom dbus-daemon[771]: dbus[771]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Dec 10 14:41:35 phenom dbus[771]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Dec 10 14:41:35 phenom accounts-daemon[864]: started daemon version 0.6.21
Dec 10 14:41:35 phenom dbus[771]: [system] Successfully activated service 'org.freedesktop.Accounts'
Dec 10 14:41:35 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'org.freedesktop.Accounts'
Dec 10 14:41:35 phenom systemd-logind[732]: New session 1 of user gdm.
Dec 10 14:41:35 phenom systemd-logind[732]: Linked /tmp/.X11-unix/X0 to /run/user/gdm/X11-display.
Dec 10 14:41:35 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) closing serial port...
Dec 10 14:41:35 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) serial port closed
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (ttyUSB1) closing serial port...
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (ttyUSB1) serial port closed
Dec 10 14:41:36 phenom dbus-daemon[771]: modem-manager[789]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-2 claimed port ttyUSB1
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-2 claimed port ttyUSB1
Dec 10 14:41:36 phenom dbus-daemon[771]: dbus[771]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Dec 10 14:41:36 phenom dbus[771]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Dec 10 14:41:36 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 10 14:41:36 phenom dbus[771]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 10 14:41:36 phenom dbus-daemon[771]: dbus[771]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Dec 10 14:41:36 phenom dbus[771]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Dec 10 14:41:36 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Dec 10 14:41:36 phenom dbus[771]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Dec 10 14:41:36 phenom rtkit-daemon[927]: Successfully made thread 926 of process 926 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Dec 10 14:41:36 phenom rtkit-daemon[927]: Successfully made thread 941 of process 926 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 10 14:41:36 phenom rtkit-daemon[927]: Successfully made thread 942 of process 926 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 10 14:41:36 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB3) closing serial port...
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (ttyUSB3) closing serial port...
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (ttyUSB3) serial port closed
Dec 10 14:41:36 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB3) serial port closed
Dec 10 14:41:36 phenom modem-manager[789]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-2 claimed port ttyUSB3
Dec 10 14:41:36 phenom dbus-daemon[771]: modem-manager[789]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:12.2/usb1/1-2 claimed port ttyUSB3
Dec 10 14:41:36 phenom rtkit-daemon[927]: Successfully made thread 943 of process 926 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 10 14:41:36 phenom rtkit-daemon[927]: Successfully made thread 944 of process 926 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 10 14:41:37 phenom dbus-daemon[771]: dbus[771]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 10 14:41:37 phenom dbus[771]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Dec 10 14:41:37 phenom dbus-daemon[771]: Launching FprintObject
Dec 10 14:41:37 phenom dbus-daemon[771]: dbus[771]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 10 14:41:37 phenom dbus-daemon[771]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Dec 10 14:41:37 phenom dbus-daemon[771]: ** Message: entering main loop
Dec 10 14:41:37 phenom dbus[771]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB0) closing serial port...
Dec 10 14:41:51 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB0) closing serial port...
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB0) serial port closed
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB2) closing serial port...
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB2) serial port closed
Dec 10 14:41:51 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB4) closing serial port...
Dec 10 14:41:51 phenom modem-manager[789]: <info>  (ttyUSB4) serial port closed
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB0) serial port closed
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB2) closing serial port...
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB2) serial port closed
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB4) closing serial port...
Dec 10 14:41:51 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB4) serial port closed
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB5) closing serial port...
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB5) serial port closed
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB6) closing serial port...
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB6) serial port closed
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB7) closing serial port...
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB7) serial port closed
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB1) opening serial port...
Dec 10 14:41:52 phenom modem-manager[789]: <warn>  (ttyUSB1): port attributes not fully set
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB5) closing serial port...
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB5) serial port closed
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB6) closing serial port...
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB6) serial port closed
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB7) closing serial port...
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB7) serial port closed
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) opening serial port...
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <warn>  (ttyUSB1): port attributes not fully set
Dec 10 14:41:52 phenom NetworkManager[715]: <warn> (ttyUSB1): failed to look up interface index
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): new GSM/UMTS device (driver: 'option1' ifindex: 0)
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): exported as /org/freedesktop/NetworkManager/Devices/1
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): now managed
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): deactivating device (reason 'managed') [2]
Dec 10 14:41:52 phenom NetworkManager[715]: <info> (ttyUSB1): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) closing serial port...
Dec 10 14:41:52 phenom dbus-daemon[771]: modem-manager[789]: <info>  (ttyUSB1) serial port closed
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB1) closing serial port...
Dec 10 14:41:52 phenom modem-manager[789]: <info>  (ttyUSB1) serial port closed
Dec 10 14:42:08 phenom dbus-daemon[771]: ** Message: No devices in use, exit

Chi fa questo è logrotate.

Ho imparato quel che fa dopo che il server dello studio si impiantò.

la macchina parte con il nuovo kernel ?

Si, Virus.

Parte se non inserisco la chiavetta.

Posso provare ad inserire un’altra chiavetta (me la faccio prestare) per avere un ulteriore riscontro?

no.

dopo che è partito e funzionante
inserisci la chiavetta, e dopo 10 secondi ci posti da root:

[code]# lsusb

tail -n 80 /var/log/messages[/code]

Ok, mi copio i comandi da qualche parte, poi rientro con il kernel funzionante

lsusb Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Bus 003 Device 002: ID 0e8f:0012 GreenAsia Inc. USB Wireless 2.4GHz Gamepad Bus 003 Device 003: ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R) Bus 004 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse Bus 004 Device 003: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

tail -n 80 /var/log/messages Dec 10 17:34:50 phenom bluetoothd[789]: bluetoothd[789]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Dec 10 17:34:51 phenom systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start. Dec 10 17:34:51 phenom kernel: 20.032166] RPC: Registered named UNIX socket transport module. Dec 10 17:34:51 phenom kernel: 20.032173] RPC: Registered udp transport module. Dec 10 17:34:51 phenom kernel: 20.032176] RPC: Registered tcp transport module. Dec 10 17:34:51 phenom kernel: 20.032180] RPC: Registered tcp NFSv4.1 backchannel transport module. Dec 10 17:34:51 phenom rpc.statd[827]: Version 1.2.6 starting Dec 10 17:34:51 phenom sm-notify[828]: Version 1.2.6 starting Dec 10 17:34:52 phenom systemd[1]: Startup finished in 1s 519ms 202us (kernel) + 3s 257ms 679us (initrd) + 16s 295ms 322us (userspace) = 21s 72ms 203us. Dec 10 17:34:52 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' Dec 10 17:34:52 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' Dec 10 17:34:52 phenom accounts-daemon[863]: started daemon version 0.6.21 Dec 10 17:34:52 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.Accounts' Dec 10 17:34:52 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.Accounts' Dec 10 17:34:52 phenom avahi-daemon[736]: Registering new address record for fe80::226:18ff:fe9c:b483 on p6p1.*. Dec 10 17:34:52 phenom systemd-logind[720]: New session 1 of user gdm. Dec 10 17:34:52 phenom systemd-logind[720]: Linked /tmp/.X11-unix/X0 to /run/user/gdm/X11-display. Dec 10 17:34:53 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' Dec 10 17:34:53 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' Dec 10 17:34:53 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.UPower' Dec 10 17:34:53 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.UPower' Dec 10 17:34:53 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Dec 10 17:34:53 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Dec 10 17:34:53 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Dec 10 17:34:53 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Dec 10 17:34:53 phenom rtkit-daemon[926]: Successfully made thread 925 of process 925 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Dec 10 17:34:53 phenom rtkit-daemon[926]: Successfully made thread 937 of process 925 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Dec 10 17:34:53 phenom rtkit-daemon[926]: Successfully made thread 941 of process 925 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Dec 10 17:34:53 phenom rtkit-daemon[926]: Successfully made thread 942 of process 925 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Dec 10 17:34:53 phenom rtkit-daemon[926]: Successfully made thread 943 of process 925 (/usr/bin/pulseaudio) owned by '42' RT at priority 5. Dec 10 17:34:54 phenom dbus-daemon[758]: dbus[758]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 17:34:54 phenom dbus[758]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 17:34:54 phenom dbus-daemon[758]: Launching FprintObject Dec 10 17:34:54 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 17:34:54 phenom dbus-daemon[758]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 10 17:34:54 phenom dbus-daemon[758]: ** Message: entering main loop Dec 10 17:34:54 phenom dbus[758]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 17:35:25 phenom dbus-daemon[758]: ** Message: No devices in use, exit Dec 10 17:36:28 phenom systemd-logind[720]: New session 2 of user nexus6. Dec 10 17:36:28 phenom systemd-logind[720]: Linked /tmp/.X11-unix/X0 to /run/user/nexus6/X11-display. Dec 10 17:36:28 phenom systemd-logind[720]: Removed session 1. Dec 10 17:36:28 phenom gdm-simple-slave[783]: WARNING: Child process 867 was already dead. Dec 10 17:36:29 phenom kernel: 118.182604] fuse init (API version 7.20) Dec 10 17:36:30 phenom rtkit-daemon[926]: Successfully made thread 1161 of process 1161 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Dec 10 17:36:30 phenom rtkit-daemon[926]: Successfully made thread 1162 of process 1161 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Dec 10 17:36:30 phenom rtkit-daemon[926]: Successfully made thread 1164 of process 1161 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Dec 10 17:36:30 phenom rtkit-daemon[926]: Successfully made thread 1167 of process 1161 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Dec 10 17:36:30 phenom rtkit-daemon[926]: Successfully made thread 1168 of process 1161 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Dec 10 17:36:31 phenom rtkit-daemon[926]: Successfully made thread 1170 of process 1170 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11. Dec 10 17:36:31 phenom pulseaudio[1170]: [pulseaudio] pid.c: Daemon already running. Dec 10 17:36:31 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' Dec 10 17:36:31 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' Dec 10 17:36:31 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.ColorManager' Dec 10 17:36:31 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.ColorManager' Dec 10 17:36:31 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.colord-sane' unit='colord-sane.service' Dec 10 17:36:31 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.colord-sane' unit='colord-sane.service' Dec 10 17:36:32 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.colord-sane' Dec 10 17:36:32 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.colord-sane' Dec 10 17:36:32 phenom dbus-daemon[758]: dbus[758]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Dec 10 17:36:32 phenom dbus[758]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Dec 10 17:36:32 phenom udisksd[1190]: udisks daemon version 1.94.0 starting Dec 10 17:36:32 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.UDisks2' Dec 10 17:36:32 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.UDisks2' Dec 10 17:36:32 phenom udisksd[1190]: Acquired the name org.freedesktop.UDisks2 on the system message bus Dec 10 17:36:32 phenom dbus-daemon[758]: dbus[758]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 10 17:36:32 phenom dbus[758]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 10 17:36:33 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 10 17:36:33 phenom dbus[758]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 10 17:36:39 phenom goa[1315]: goa-daemon version 3.4.2 starting [main.c:112, main()] Dec 10 17:36:41 phenom kernel: 129.903011] UDF-fs: Partition marked readonly; forcing readonly mount Dec 10 17:36:41 phenom kernel: 129.963932] UDF-fs: INFO Mounting volume 'MMH6 - EFIGS', timestamp 2011/09/19 15:42 (103c) Dec 10 17:36:41 phenom udisksd[1190]: Mounted /dev/sr1 at /run/media/nexus6/MMH6 - EFIGS on behalf of uid 1000 Dec 10 17:37:09 phenom dbus-daemon[758]: dbus[758]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 17:37:09 phenom dbus[758]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 10 17:37:09 phenom dbus-daemon[758]: Launching FprintObject Dec 10 17:37:09 phenom dbus-daemon[758]: dbus[758]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 17:37:09 phenom dbus[758]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 10 17:37:09 phenom dbus-daemon[758]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 10 17:37:09 phenom dbus-daemon[758]: ** Message: entering main loop Dec 10 17:37:39 phenom dbus-daemon[758]: ** Message: No devices in use, exit

dai il comando da root:

# modprobe usbserial vendor=0x1ee8 product=0x000b

togli e metti la pennetta .
vediamo ora :

[code]# lsusb

tail -n 80 /var/log/messages[/code]

Virus, mi devo essere spiegato male.

Se io metto la pennetta il sistema crasha e va in modalità testo senza accettare comandi. (kernerl panic secondo goggles se faccio la foto dello schermo, che se credi allego se mi indicate come)

Quel comando è stato dato con il kernel nuovo SENZA la pennetta.

Intanto ho fatto la prova con una pennetta ZTE e con quella non crasha (ma ho fatto solo un tentativo e non so se basta per validare quanto dico).

La pennetta Onda è la stessa con cui sono collegato adesso con il kernel vecchio, sempre collegata alla stessa porta.

EDIT

ho caricato una foto che è solo la seconda pagina di quello che appare prima che si blocchi tutto.
https://skydrive.live.com/?cid=a2678891991083a9#cid=A2678891991083A9&id=A2678891991083A9!319

ci fai vedere cosa c’è scritto in:

# cat /etc/grub/default

Scusami virus, ma ho letto solo adesso e non mi sto collegando ad internet per evitare crash.

quella directory sembra che io non l’abbia

in etc con grub ho solo:

grub2.cfg grub.d

Al momento sono collegato con kernel vecchio e funzionante, appena posso provo a rifarmi prestare l’altra chiavetta che non fa crashare il nuovo kernel.

Comunque siccome ho sempre avuto strani problemi con fedora e questa chiavetta, non scarterei l’ipotesi che possa essere l’hardware di questa chiavetta in particolare (intendo la mia non tutte quelle di questo modello) che fa qualche bizza.

grazie in anticipo, sono curioso anche io di vedere come si fa questo debug ma pensate prima e sempre a cose più importanti che a me che utilizzo da poco il sistema