Configurazione Internet Key da terminale.

Ritratto di mcortese
mcortese
(Moderatore)
Offline
Moderatore
Iscritto: 27/02/2009
Messaggi: 2918

Ti fanno scaricare il kernel da www.kernel.org. Peccato che il 3.1.6 non sia tra quelli manutenuti! Sad (non so nemmeno se sia compatibile con la GPL: secondo me se distribuiscono il kernel 3.1.6 devono mettere a disposizione i sorgenti del 3.1.6)

Allora prova a scaricare il kernel 3.2.40 o il 3.0.68, contando sul fatto che le risorse con cui si interfaccia il modulo option non siano cambiate. Scompatta l'archivio e crea un link simbolico in modo che /usr/src/linux punti alla directory radice del kernel (quella in cui ci sono i file COPYING, CREDITS...). Ad esempio:

# ln -s /usr/src/linux-3.2.40 /usr/src/linux

Poi segui le istruzioni del README sul Patching e Configuring e fermati al Customizing. A questo punto dovresti poter andare a vedere se c'è il file option.c e già che ci sei fai questa verifica:

grep -i 0x0017 option.c
Se compare l'ALCATEL_PRODUCT_X220_X500D sei a cavallo.

A questo punto il comando giusto dovrebbe essere

$ make -C /usr/src/linux M=$PWD modules

Ritratto di daxter92
daxter92
(Junior)
Offline
Junior
Iscritto: 28/02/2013
Messaggi: 40

Mh ok, per me sembra abbastanza complicato, però ci provo Smile Ti faccio sapere come venno le cose! Ma quindi in sostanza il file .PATH è come se fosse un estensione del kernel che poi andrò a configurare? Purtroppo sono proprio ignorante in materia Worried

Emilio

Ritratto di mcortese
mcortese
(Moderatore)
Offline
Moderatore
Iscritto: 27/02/2009
Messaggi: 2918

Se ti è sfuggita una "C" e parli di un file "patch" (in italiano "toppa") allora è un insieme di modifiche da apportare a un sorgente per farlo assomigliare ad un altro. A volte è chiamato anche "diff" perché elenca le differenze tra due sorgenti.

Nel tuo caso dovrebbe contenere tutte le modifiche da apportare ad un kernel "vergine" (o "vanilla" con riferimento al gusto del gelato che non sa di niente - tieni conto che gli americani hanno inventato il gelato Häagen-Dazs perché gli altri non erano abbastanza succulenti) per renderlo uguale a quello che hanno personalizzato loro per l'hardware specifico.

Un file patch si applica con il comando omonimo. Nel tuo caso:

$ cd /usr/src/linux
$ patch -p1 <file/patch/con/tutto/il/suo/percorso

Attenzione però che potrebbe non andare a buon fine se è stato ottenuto a partire dal kernel 3.1.6 e tu cerchi di applicarlo a una versione diversa. Tieni comunque conto che a te non interessa compilare l'intero kernel, ma solo il modulo option. Se questa parte non è toccata dalla patch non hai ragione di applicarla. Verificalo con un po' di grep:

$ grep usb/serial file/patch/con/tutto/il/suo/percorso

Ritratto di mcortese
mcortese
(Moderatore)
Offline
Moderatore
Iscritto: 27/02/2009
Messaggi: 2918

Ho appena provato su una macchina con Debian testing (kernel 3.2.qualcosa) e devo correggere legermente quanto detto prima. Vista l'interdipendenza tra i moduli option, usb_wwan e usbserial, il comando completo è:

make -C /usr/src/linux M=$PWD \
CONFIG_USB_SERIAL=m \
CONFIG_USB_SERIAL_OPTION=m \
CONFIG_USB_SERIAL_WWAN=m \
modules

A compilazione avvenuta, devi caricare i tre moduli con

# insmod usbserial.ko
# insmod usb_wwan.ko
# insmod option.ko

A questo punto compare la directory /sys/bus/usb-serial/drivers/option1 con dentro il file new_id in cui devi scrivere "1bbb 0017" con il comando:
# echo '1bbb 0017' >/sys/bus/usb-serial/drivers/option1/new_id

Qui funziona...

Ritratto di daxter92
daxter92
(Junior)
Offline
Junior
Iscritto: 28/02/2013
Messaggi: 40

Io adesso salvo tutto quello che posso salvare, vedo magari di fare un backup e poi formatto così da avere tutto con le impostazioni iniziali, dopodiché scarico la PATCH nella cartella di cui abbiamo parlato, scarico il Kernel che mi hai detto e provo a fare i vari passaggi cher hai scritto, un oretta al massimo e ti dico com'è andata Smile

Emilio

Ritratto di daxter92
daxter92
(Junior)
Offline
Junior
Iscritto: 28/02/2013
Messaggi: 40

Ok, ho un problema. Ho formattato tutto quanto e aggiornato, in modo da avere il sistema bello pulito. Ho installato wget per scaricare i file, nella cartella /usr/src/ ho scaricato questo "SBC Kernel Development Package" e, essendo in formato tar.gz l'ho scompattato così che ora ho: /usr/src/phidgetsbc2_kerneldev_1.0.1.20120327# con all'interno il file README, quello che ti avevo postato, e il file linux-3.1.6-phidget_sbc2.patch. Fatto questo dovevo scaricare il kernel dal sito che mi hai dato, ho scaricato in /usr/src/ il kernel linux-3.2.40.tar.xz! Solo che non riesco a scompattarlo, come devo fare?

P.S. Fino qui ho fatto tutto giusto?

Emilio

Ritratto di homeless
homeless
(Guru)
Offline
Guru
Iscritto: 21/10/2011
Messaggi: 1359

daxter92 ha scritto:

ho scaricato in /usr/src/ il kernel linux-3.2.40.tar.xz! Solo che non riesco a scompattarlo, come devo fare?


wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.40.tar.gz
tar zxf linux-3.2.40.tar.gz

Ritratto di daxter92
daxter92
(Junior)
Offline
Junior
Iscritto: 28/02/2013
Messaggi: 40

Provato, ma quando scompatto:

tar: linux-3.2.40/tools/perf/util/dwarf-aux.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/dwarf-aux.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/environment.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/event.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/event.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/evlist.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/evlist.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/evsel.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/evsel.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/exec_cmd.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/exec_cmd.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/generate-cmdlist.sh: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/header.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/header.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/help.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/help.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/hist.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/hist.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/hweight.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/alternative-asm.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/asm-offsets.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/bug.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/byteorder.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/cpufeature.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/dwarf2.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/hweight.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/swab.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/system.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/asm/uaccess.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/dwarf-regs.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/bitmap.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/bitops.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/compiler.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/const.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/ctype.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/hash.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/kernel.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/linkage.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/list.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/module.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/poison.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/prefetch.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/rbtree.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/string.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/include/linux/types.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/levenshtein.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/levenshtein.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/map.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/map.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/pager.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/parse-events.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/parse-events.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/parse-options.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/parse-options.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/path.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/probe-event.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/probe-event.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/probe-finder.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/probe-finder.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/pstack.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/pstack.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/python.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/quote.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/quote.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/run-command.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/run-command.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/scripting-engines: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/scripting-engines/trace-event-perl.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/scripting-engines/trace-event-python.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/session.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/session.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/setup.py: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/sigchain.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/sigchain.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/sort.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/sort.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strbuf.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strbuf.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strfilter.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strfilter.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/string.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strlist.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/strlist.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/svghelper.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/svghelper.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/symbol.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/symbol.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/thread.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/thread.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/thread_map.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/thread_map.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/top.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/top.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/trace-event-info.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/trace-event-parse.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/trace-event-read.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/trace-event-scripting.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/trace-event.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/types.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browser.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browser.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browsers: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browsers/annotate.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browsers/hists.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browsers/map.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/browsers/map.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/helpline.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/helpline.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/keysyms.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/libslang.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/progress.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/progress.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/setup.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/ui.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/util.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/ui/util.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/usage.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/util.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/util.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/values.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/values.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/wrapper.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/xyarray.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/perf/util/xyarray.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/.gitignore: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/README: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/ToDo: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/README-BENCH: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/benchmark.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/benchmark.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/config.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/cpufreq-bench_plot.sh: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/cpufreq-bench_script.sh: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/example.cfg: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/main.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/parse.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/parse.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/system.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/bench/system.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386/centrino-decode.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386/dump_psb.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386/intel_gsic.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/i386/powernow-k8-decode.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/kernel: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/kernel/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/kernel/cpufreq-test_tsc.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/x86_64: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/debug/x86_64/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/lib: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/lib/cpufreq.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/lib/cpufreq.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/lib/sysfs.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/lib/sysfs.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower-frequency-info.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower-frequency-set.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower-info.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower-monitor.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower-set.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/man/cpupower.1: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po/cs.po: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po/de.po: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po/fr.po: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po/it.po: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/po/pt.po: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/builtin.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpufreq-info.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpufreq-set.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpuidle-info.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpupower-info.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpupower-set.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/cpupower.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/amd.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/bitmask.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/bitmask.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/cpuid.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/helpers.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/misc.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/msr.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/pci.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/sysfs.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/sysfs.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/helpers/topology.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/amd_fam14h_idle.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/cpuidle_sysfs.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/cpupower-monitor.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/idle_monitors.def: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/idle_monitors.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/mperf_monitor.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/nhm_idle.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/idle_monitor/snb_idle.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/cpupower/utils/version-gen.sh: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/x86/turbostat: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/x86/turbostat/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86/turbostat/turbostat.8: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86/turbostat/turbostat.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86/x86_energy_perf_policy: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/power/x86/x86_energy_perf_policy/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86/x86_energy_perf_policy/x86_energy_perf_policy.8: Cannot open: No such file or directory
tar: linux-3.2.40/tools/power/x86/x86_energy_perf_policy/x86_energy_perf_policy.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/slub: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/slub/slabinfo.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/testing: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/testing/ktest: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/testing/ktest/compare-ktest-sample.pl: Cannot open: No such file or directory
tar: linux-3.2.40/tools/testing/ktest/ktest.pl: Cannot open: No such file or directory
tar: linux-3.2.40/tools/testing/ktest/sample.conf: Cannot open: No such file or directory
tar: linux-3.2.40/tools/usb: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/usb/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/usb/ffs-test.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/usb/hcd-tests.sh: Cannot open: No such file or directory
tar: linux-3.2.40/tools/usb/testusb.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/virtio/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/linux: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/virtio/linux/device.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/linux/slab.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/linux/virtio.h: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/vhost_test: Cannot mkdir: No such file or directory
tar: linux-3.2.40/tools/virtio/vhost_test/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/vhost_test/vhost_test.c: Cannot open: No such file or directory
tar: linux-3.2.40/tools/virtio/virtio_test.c: Cannot open: No such file or directory
tar: linux-3.2.40/usr: Cannot mkdir: No space left on device
tar: linux-3.2.40/usr/.gitignore: Cannot open: No such file or directory
tar: linux-3.2.40/usr/Kconfig: Cannot open: No such file or directory
tar: linux-3.2.40/usr/Makefile: Cannot open: No such file or directory
tar: linux-3.2.40/usr/gen_init_cpio.c: Cannot open: No such file or directory
tar: linux-3.2.40/usr/initramfs_data.S: Cannot open: No such file or directory
tar: linux-3.2.40/virt: Cannot mkdir: No space left on device
tar: linux-3.2.40/virt/kvm: Cannot mkdir: No such file or directory
tar: linux-3.2.40/virt/kvm/Kconfig: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/assigned-dev.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/async_pf.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/async_pf.h: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/coalesced_mmio.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/coalesced_mmio.h: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/eventfd.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/ioapic.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/ioapic.h: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/iodev.h: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/iommu.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/irq_comm.c: Cannot open: No such file or directory
tar: linux-3.2.40/virt/kvm/kvm_main.c: Cannot open: No such file or directory
tar: Exiting with failure status due to previous errors

Emilio

Ritratto di homeless
homeless
(Guru)
Offline
Guru
Iscritto: 21/10/2011
Messaggi: 1359

Non hai i permessi di scrittura nella directory nella quale stai scompattando il file.

Ritratto di daxter92
daxter92
(Junior)
Offline
Junior
Iscritto: 28/02/2013
Messaggi: 40

Ah ecco, per attivarli devo fare

chmod 777 xz

O comunque qualcosa di simile?

Emilio