slackware 13 e momodesign H3G
Moderatore: Staff
Regole del forum
1) Citare sempre la versione di Slackware usata e la versione del Kernel. Questi dati aiutano le persone che possono rispondere.
2) Citare il tipo di hardware coinvolto in modo dettagliato.
3) Leggere attentamente le risposte ricevute
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT. Non usare termini gergali come procio, mobo e simili per identificare i componenti hardware.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
1) Citare sempre la versione di Slackware usata e la versione del Kernel. Questi dati aiutano le persone che possono rispondere.
2) Citare il tipo di hardware coinvolto in modo dettagliato.
3) Leggere attentamente le risposte ricevute
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT. Non usare termini gergali come procio, mobo e simili per identificare i componenti hardware.
6) Appena registrati è consigliato presentarsi nel forum dedicato.
La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
slackware 13 e momodesign H3G
salve a tutti ho cercatoin lungo e in largo ma non ho trovato una soluzione al mio problema... il trhead su questo forum purtroppo contiene un link che non porta da nessuna parte e quindi non si può procedere alla configurazione di questa chiavetta che da giorni mi tiene impeganto...
qualcuno mi riesce ad indicare una qualche guida in giro perla rete per configurare con slack la momodesign?
grazie mille
qualcuno mi riesce ad indicare una qualche guida in giro perla rete per configurare con slack la momodesign?
grazie mille
- ZeroUno
- Staff
- Messaggi: 5441
- Iscritto il: ven 2 giu 2006, 14:52
- Nome Cognome: Matteo Rossini
- Slackware: current
- Kernel: slack-current
- Desktop: ktown-latest
- Distribuzione: 01000000-current
- Località: Roma / Castelli
- Contatta:
Re: slackware 13 e momodesign H3G
Innanzitutto dicci cosa hai provato a fare e cosa sei riuscito a fare; poi togli la chiavetta, dai un reboot e, dopo aver inserito la chiavetta e atteso una trentina di secondi, dacci l'output di lsusb, dmesg e lsmod.ginoilmago ha scritto:salve a tutti ho cercatoin lungo e in largo ma non ho trovato una soluzione al mio problema... il trhead su questo forum purtroppo contiene un link che non porta da nessuna parte e quindi non si può procedere alla configurazione di questa chiavetta che da giorni mi tiene impeganto...
qualcuno mi riesce ad indicare una qualche guida in giro perla rete per configurare con slack la momodesign?
grazie mille
poi dacci il modello ESATTO della chiavetta; per qualcuna la 3 stessa fornisce i driver per linux, altre funzionano semplicemente con il modulo usbserial.
Io ho una HUAWEY e 3 mi ha fornito il driver e il suo tool di connessione, e funziona perfettamente, meglio di windows (considerando che windows 7 non è nativamente supportato )
Ciao
Packages finder: slakfinder.org | Slackpkg+, per aggiungere repository a slackpkg
Codice: Seleziona tutto
1011010 1100101 1110010 1101111 - 0100000 - 1010101 1101110 1101111
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
Re: slackware 13 e momodesign H3G
ho provato a configurare direttamente kppp con i seguenti parametri:ZeroUno ha scritto: Innanzitutto dicci cosa hai provato a fare e cosa sei riuscito a fare;
AT+CPIN=XXXX
AT+CGDCONT=1,"ip","datacard.tre.it"
username:tre
password:tre
DNS 62.13.171.2 e 62.13.171.1
la connessione va a buon fine ma non riesco a navigare
allora ho provato con wvdial e questo è il mio wvdial.conf:
Codice: Seleziona tutto
[Dialer Defaults]
Modem = /dev/ttyUSB0
ISDN = off
Modem Type = Analog Modem
Baud = 460800
#Init = AT+CPIN = 1185
Init2 = ATX3
Init3 = AT+COPS?
Init4 =AT+CGDCONT=1,"ip","datacard.tre.it"
Phone = *99#
Dial Attempts = 1
Dial Command = ATM1L3DT
Ask Password = off
Username = tre
Password = tre
Auto Reconnect = off
Abort on Busy = off
Carrier Check = off
Check Def Route = on
Abort on No Dialtone = on
Stupid Mode = on
Idle Seconds = 0
Auto DNS = on
Codice: Seleziona tutto
Caught signal 2: Attempting to exit gracefully...
--> Terminating on signal 15
--> Connect time 0.5 minutes.
--> Disconnecting at Wed Apr 28 08:37:26 2010
lsusb:ZeroUno ha scritto: poi togli la chiavetta, dai un reboot e, dopo aver inserito la chiavetta e atteso una trentina di secondi, dacci l'output di lsusb, dmesg e lsmod.
Codice: Seleziona tutto
Bus 001 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
Codice: Seleziona tutto
it_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT 3FEE636D, 3B0B (r1 Sony J1 20051025 PTL 20030224)
ACPI: FACS 3FEFAFC0, 0040
ACPI: BOOT 3FEE9FD8, 0028 (r1 Sony J1 20051025 PTL 1)
ACPI: MCFG 3FEE9F9C, 003C (r1 Sony J1 20051025 PTL 5F)
ACPI: SSDT 3FEE6195, 01D4 (r1 Sony J1 20051025 PTL 20030224)
ACPI: SSDT 3FEE5D50, 0235 (r1 Sony J1 20051025 PTL 20030224)
ACPI: SSDT 3FEE5B35, 021B (r1 Sony J1 20051025 PTL 20030224)
ACPI: SSDT 3FEE591C, 0219 (r1 Sony J1 20051025 PTL 20030224)
ACPI: Local APIC address 0xfee00000
134MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 00000000 - 377fe000
bootmap 00011000 - 00017f00
(8 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 0000b30674] TEXT DATA BSS ==> [0000100000 - 0000b30674]
#4 [0000b31000 - 0000b35000] INIT_PG_TABLE ==> [0000b31000 - 0000b35000]
#5 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000]
#6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
#7 [0000011000 - 0000018000] BOOTMAP ==> [0000011000 - 0000018000]
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x0003fee0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0003fee0
On node 0 totalpages: 261743
free_area_init_node: node 0, pgdat c09da700, node_mem_map c1000200
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3951 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 270 pages used for memmap
HighMem zone: 34260 pages, LIFO batch:7
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
SMP: Allowing 2 CPUs, 1 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000dc000
PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Allocating 40960 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259697
Kernel command line: BOOT_IMAGE=Linux ro root=305 vt.default_utf8=0
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 1729.402 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1027124k/1047424k available (6817k kernel code, 19560k reserved, 2484k data, 456k init, 138120k highmem)
virtual kernel memory layout:
fixmap : 0xffe19000 - 0xfffff000 (1944 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc0a22000 - 0xc0a94000 ( 456 kB)
.data : 0xc07a8437 - 0xc0a15520 (2484 kB)
.text : 0xc0100000 - 0xc07a8437 (6817 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 3458.80 BogoMIPS (lpj=1729402)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20081204
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Pentium(R) M processor 1.73GHz stepping 08
Brought up 1 CPUs
Total of 1 processors activated (3458.80 BogoMIPS).
net_namespace: 956 bytes
xor: automatically using best checksumming function: pIII_sse
pIII_sse : 4624.000 MB/sec
xor: using function: pIII_sse (4624.000 MB/sec)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: EC: driver started in interrupt mode
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0x80000000-0x80003fff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0x1800-0x181f]
pci 0000:00:1d.1: reg 20 io port: [0x1820-0x183f]
pci 0000:00:1d.2: reg 20 io port: [0x1840-0x185f]
pci 0000:00:1d.3: reg 20 io port: [0x1860-0x187f]
pci 0000:00:1d.7: reg 10 32bit mmio: [0x80004000-0x800043ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 1180-11bf claimed by ICH6 GPIO
pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
pci 0000:00:1f.1: reg 18 io port: [0x00-0x07]
pci 0000:00:1f.1: reg 1c io port: [0x00-0x03]
pci 0000:00:1f.1: reg 20 io port: [0x1880-0x188f]
pci 0000:00:1f.3: reg 20 io port: [0x18a0-0x18bf]
pci 0000:01:00.0: reg 10 32bit mmio: [0xa0000000-0xa0ffffff]
pci 0000:01:00.0: reg 14 64bit mmio: [0xc0000000-0xcfffffff]
pci 0000:01:00.0: reg 1c 64bit mmio: [0x90000000-0x90ffffff]
pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:00:01.0: bridge 32bit mmio: [0x90000000-0xafffffff]
pci 0000:00:01.0: bridge 32bit mmio pref: [0xc0000000-0xcfffffff]
pci 0000:06:03.0: reg 10 32bit mmio: [0x000000-0x000fff]
pci 0000:06:03.0: supports D1 D2
pci 0000:06:03.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:06:03.0: PME# disabled
pci 0000:06:03.2: reg 10 32bit mmio: [0xb0004000-0xb00047ff]
pci 0000:06:03.2: reg 14 32bit mmio: [0xb0000000-0xb0003fff]
pci 0000:06:03.2: supports D1 D2
pci 0000:06:03.2: PME# supported from D0 D1 D2 D3hot
pci 0000:06:03.2: PME# disabled
pci 0000:06:03.3: reg 10 32bit mmio: [0xb0005000-0xb0005fff]
pci 0000:06:03.3: supports D1 D2
pci 0000:06:03.3: PME# supported from D0 D1 D2 D3hot
pci 0000:06:03.3: PME# disabled
pci 0000:06:04.0: reg 10 32bit mmio: [0xb0006000-0xb0006fff]
pci 0000:06:04.0: PME# supported from D0 D3hot D3cold
pci 0000:06:04.0: PME# disabled
pci 0000:06:08.0: reg 10 32bit mmio: [0xb0007000-0xb0007fff]
pci 0000:06:08.0: reg 14 io port: [0x2000-0x203f]
pci 0000:06:08.0: supports D1 D2
pci 0000:06:08.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:06:08.0: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge io port: [0x2000-0x2fff]
pci 0000:00:1e.0: bridge 32bit mmio: [0xb0000000-0xb00fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 *4 5 6 7 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 *3 4 5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 *7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 *5 6 7 11 12 14 15)
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
hpet clockevent registered
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 8 devices
ACPI: ACPI bus type pnp unregistered
system 00:04: ioport range 0x380-0x383 has been reserved
system 00:04: ioport range 0x800-0x80f has been reserved
system 00:04: ioport range 0x1000-0x107f has been reserved
system 00:04: ioport range 0x1180-0x11bf has been reserved
system 00:04: ioport range 0x1640-0x164f has been reserved
system 00:04: iomem range 0xf0008000-0xf000bfff has been reserved
system 00:04: iomem range 0xf0000000-0xf0003fff has been reserved
system 00:04: iomem range 0xf0005000-0xf0005fff has been reserved
system 00:04: iomem range 0xf0004000-0xf0004fff has been reserved
system 00:04: iomem range 0xe0000000-0xefffffff has been reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: disabled
pci 0000:00:01.0: MEM window: 0x90000000-0xafffffff
pci 0000:00:01.0: PREFETCH window: 0x000000c0000000-0x000000cfffffff
pci 0000:06:03.0: CardBus bridge, secondary bus 0000:07
pci 0000:06:03.0: IO window: 0x002400-0x0024ff
pci 0000:06:03.0: IO window: 0x002800-0x0028ff
pci 0000:06:03.0: PREFETCH window: 0x50000000-0x53ffffff
pci 0000:06:03.0: MEM window: 0x54000000-0x57ffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:06
pci 0000:00:1e.0: IO window: 0x2000-0x2fff
pci 0000:00:1e.0: MEM window: 0xb0000000-0xb00fffff
pci 0000:00:1e.0: PREFETCH window: 0x00000050000000-0x00000053ffffff
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:06:03.0: enabling device (0000 -> 0003)
pci 0000:06:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:01: resource 0 mem: [0x0-0x0]
pci_bus 0000:01: resource 1 mem: [0x90000000-0xafffffff]
pci_bus 0000:01: resource 2 mem: [0xc0000000-0xcfffffff]
pci_bus 0000:01: resource 3 mem: [0x0-0x0]
pci_bus 0000:06: resource 0 io: [0x2000-0x2fff]
pci_bus 0000:06: resource 1 mem: [0xb0000000-0xb00fffff]
pci_bus 0000:06: resource 2 mem: [0x50000000-0x53ffffff]
pci_bus 0000:06: resource 3 io: [0x00-0xffff]
pci_bus 0000:06: resource 4 mem: [0x000000-0xffffffff]
pci_bus 0000:07: resource 0 io: [0x2400-0x24ff]
pci_bus 0000:07: resource 1 io: [0x2800-0x28ff]
pci_bus 0000:07: resource 2 mem: [0x50000000-0x53ffffff]
pci_bus 0000:07: resource 3 mem: [0x54000000-0x57ffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Simple Boot Flag at 0x36 set to 0x1
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NTFS driver 2.1.29 [Flags: R/W].
JFS: nTxBlock = 8026, nTxLock = 64213
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
GFS2 (built Aug 17 2009 00:51:32) installed
msgmni has been set to 1736
alg: No test for cipher_null (cipher_null-generic)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for fcrypt (fcrypt-generic)
alg: No test for stdrng (krng)
async_tx: api initialized (async)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:00.0: Boot video device
pci 0000:06:08.0: Firmware left e100 interrupts enabled; disabling
pcieport-driver 0000:00:01.0: setting latency timer to 64
pcieport-driver 0000:00:01.0: irq 24 for MSI/MSI-X
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
vesafb: framebuffer at 0xc0000000, mapped to 0xf8500000, using 1536k, total 32768k
vesafb: mode is 1024x768x8, linelength=1024, pages=3
vesafb: protected mode interface info at c000:d310
vesafb: pmi: set display start = c00cd346, set palette = c00cd3b0
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
floppy0: no floppy controllers found
brd: module loaded
loop: module loaded
Compaq SMART2 Driver (v 2.6.0)
HP CISS Driver (v 3.6.20)
input: Macintosh mouse button emulation as /devices/virtual/input/input0
Uniform Multi-Platform E-IDE driver
piix 0000:00:1f.1: IDE controller (0x8086:0x266f rev 0x03)
pci 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
piix 0000:00:1f.1: IDE port disabled
piix 0000:00:1f.1: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1880-0x1887
Probing IDE interface ide0...
hda: HTS541010G9AT00, ATA DISK drive
hdb: SONY DVD RW DW-Q58A, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/100 mode selected
hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide-gd driver 1.18
hda: max request size: 512KiB
hda: 195371568 sectors (100030 MB) w/7539KiB Cache, CHS=16383/255/63
hda: cache flushes supported
hda: hda1 hda2 < hda5 hda6 hda7 >
ide-cd driver 5.00
ide-cd: hdb: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
Loading iSCSI transport class v2.0-870.
rdac: device handler registered
hp_sw: device handler registered
emc: device handler registered
alua: device handler registered
fcoe_transport_register:fcoesw
Adaptec aacraid driver 1.1-5[2456]-ms
scsi: <fdomain> Detection failed (no card)
sym53c416.c: Version 1.0.0-ac
qlogicfas: no cards were found, please specify I/O address and IRQ using iobase= and irq= options<6>QLogic Fibre Channel HBA Driver: 8.03.00-k4
iscsi: registered transport (qla4xxx)
QLogic iSCSI HBA Driver
Emulex LightPulse Fibre Channel SCSI driver 8.3.0
Copyright(c) 2004-2008 Emulex. All rights reserved.
Failed initialization of WD-7000 SCSI card!
DC390: clustering now enabled by default. If you get problems load
with "disable_clustering=1" and report to maintainers
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megasas: 00.00.04.01 Thu July 24 11:41:51 PST 2008
GDT-HA: Storage RAID Controller Driver. Version: 3.05
3ware Storage Controller device driver for Linux v1.26.02.002.
3ware 9000 Storage Controller device driver for Linux v2.26.02.011.
nsp32: loading...
ipr: IBM Power RAID SCSI Device Driver version: 2.4.1 (April 24, 2007)
RocketRAID 3xxx/4xxx Controller driver v1.3 (071203)
stex: Promise SuperTrak EX Driver version: 3.6.0000.1
st: Version 20081215, fixed bufsize 32768, s/g segs 256
Driver 'st' needs updating - please use bus_type methods
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
I2O subsystem v1.325
i2o: max drivers = 8
I2O Configuration OSM v1.323
I2O Bus Adapter OSM v1.317
I2O Block Device OSM v1.325
I2O SCSI Peripheral OSM v1.316
I2O ProcFS OSM v1.316
Fusion MPT base driver 3.04.07
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.07
Fusion MPT FC Host driver 3.04.07
Fusion MPT SAS Host driver 3.04.07
ohci1394 0000:06:03.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[18] MMIO=[b0004000-b00047ff] Max Packet=[2048] IR/IT contexts=[4/8]
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0x80004000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.29.6-smp ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
116x: driver isp116x-hcd, 03 Nov 2005
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001800
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.29.6-smp uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001820
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.29.6-smp uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.29.6-smp uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001860
usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.29.6-smp uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
sl811: driver sl811-hcd, 19 May 2005
r8a66597_hcd: driver r8a66597_hcd, 10 Apr 2008
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 613 MB/s
raid6: int32x2 687 MB/s
raid6: int32x4 621 MB/s
raid6: int32x8 468 MB/s
raid6: mmxx1 1804 MB/s
raid6: mmxx2 2046 MB/s
raid6: sse1x1 1296 MB/s
raid6: sse1x2 2109 MB/s
raid6: sse2x1 2296 MB/s
raid6: sse2x2 2609 MB/s
raid6: using algorithm sse2x2 (2609 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: multipath personality registered for level -4
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
cpuidle: using governor ladder
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Using IPI No-Shortcut mode
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
ReiserFS: hda5: found reiserfs format "3.6" with standard journal
ReiserFS: hda5: using ordered data mode
ReiserFS: hda5: journal params: device hda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda5: checking transaction log (hda5)
ReiserFS: hda5: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly on device 3:5.
Freeing unused kernel memory: 456k freed
usb 3-1: new low speed USB device using uhci_hcd and address 2
usb 3-1: New USB device found, idVendor=062a, idProduct=0000
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 3-1: configuration #1 chosen from 1 choice
input: HID 062a:0000 as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input2
generic-usb 0003:062A:0000.0001: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0000] on usb-0000:00:1d.1-1/input0
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0800460301fedad3]
ACPI: AC Adapter [ADP1] (on-line)
input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4
ACPI: Lid Switch [LID0]
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
ACPI: Power Button (CM) [PWRB]
i2c_core: exports duplicate symbol i2c_smbus_xfer (owned by kernel)
i2c_core: exports duplicate symbol i2c_smbus_xfer (owned by kernel)
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ACPI: Battery Slot [BAT0] (battery absent)
Linux agpgart interface v0.103
intel_rng: FWH not detected
sony-laptop: Sony Notebook Control Driver v0.6.
input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:18/SNY5001:00/input/input6
input: Sony Vaio Jogdial as /devices/virtual/input/input7
input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:01/device:02/input/input8
ACPI: Video Device [NGFX] (multi-head: yes rom: no post: no)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
input: PS/2 Mouse as /devices/platform/i8042/serio4/input/input9
input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input10
ACPI: CPU0 (power states: C1[C1] C2[C2])
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [CPU0] (supports 8 throttling states)
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (42 C)
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Marking TSC unstable due to TSC halts in idle
Clocksource tsc unstable (delta = -81992699 ns)
nvidia: module license 'NVIDIA' taints kernel.
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module 195.36.15 Thu Mar 11 21:41:46 PST 2010
tifm_7xx1 0000:06:03.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
yenta_cardbus 0000:06:03.0: CardBus bridge found [104d:818f]
yenta_cardbus 0000:06:03.0: Enabling burst memory read transactions
yenta_cardbus 0000:06:03.0: Using CSCINT to route CSC interrupts to PCI
yenta_cardbus 0000:06:03.0: Routing CardBus interrupts to PCI
yenta_cardbus 0000:06:03.0: TI: mfunc 0x01001b22, devctl 0x64
e100: Intel(R) PRO/100 Network Driver, 3.5.23-k6-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
tifm_core: MMC/SD card detected in socket 0:0
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
rtc_cmos 00:05: RTC can wake from S4
rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: setting latency timer to 64
yenta_cardbus 0000:06:03.0: ISA IRQ mask 0x0cf8, PCI irq 16
yenta_cardbus 0000:06:03.0: Socket status: 30000006
pci_bus 0000:06: Raising subordinate bus# of parent bus (#06) from #07 to #0a
yenta_cardbus 0000:06:03.0: pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x2000-0x2fff: clean.
yenta_cardbus 0000:06:03.0: pcmcia: parent PCI bridge Memory window: 0xb0000000 - 0xb00fffff
yenta_cardbus 0000:06:03.0: pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x53ffffff
e100 0000:06:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e100 0000:06:08.0: PME# disabled
e100: eth0: e100_probe: addr 0xb0007000, irq 20, MAC addr 00:01:4a:ee:36:e2
ipw2200 0000:06:04.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
eth1 (ipw2200): not using net_device_ops yet
ipw2200 0000:06:04.0: firmware: requesting ipw2200-bss.fw
ipw2200: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
Adding 2000052k swap on /dev/hda6. Priority:-1 extents:1 across:2000052k
fuse init (API version 7.11)
parport 0x378 (WARNING): CTR: wrote 0x0c, read 0xff
parport 0x378 (WARNING): DATA: wrote 0xaa, read 0xff
parport 0x378: You gave this address, but there is probably no parallel port there!
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
ppdev: user-space parallel port driver
lp0: using parport0 (interrupt-driven).
lp0: console ready
powernow: This module only works with AMD K7 CPUs
cpufreq: No nForce2 chipset.
e100: eth0 NIC Link is Up 100 Mbps Full Duplex
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth0: no IPv6 routers present
usb 1-1: new high speed USB device using ehci_hcd and address 3
usb 1-1: New USB device found, idVendor=12d1, idProduct=1003
usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 1-1: Product: HUAWEI Mobile
usb 1-1: Manufacturer: HUAWEI Technology
usb 1-1: configuration #1 chosen from 1 choice
usb-storage: probe of 1-1:1.0 failed with error -1
scsi3 : SCSI emulation for USB Mass Storage devices
usb 1-1: USB disconnect, address 3
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb_storage: module is already loaded
usb_storage: module is already loaded
usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: New USB device found, idVendor=12d1, idProduct=1003
usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 1-1: Product: HUAWEI Mobile
usb 1-1: Manufacturer: HUAWEI Technology
usb 1-1: configuration #1 chosen from 1 choice
usb-storage: probe of 1-1:1.0 failed with error -5
usb-storage: probe of 1-1:1.1 failed with error -5
usb-storage: probe of 1-1:1.2 failed with error -1
usb_storage: module is already loaded
usb-storage: probe of 1-1:1.3 failed with error -1
usb_storage: module is already loaded
usb_storage: module is already loaded
usb_storage: module is already loaded
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usb_storage: module is already loaded
USB Serial support registered for GSM modem (1-port)
option 1-1:1.0: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1:1.1: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
usb_storage: module is already loaded
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
Codice: Seleziona tutto
Module Size Used by
ppp_deflate 4412 0
bsd_comp 5244 0
ppp_async 8668 0
crc_ccitt 1628 1 ppp_async
ppp_generic 22472 3 ppp_deflate,bsd_comp,ppp_async
slhc 5404 1 ppp_generic
option 19744 0
usbserial 29448 1 option
snd_seq_dummy 2464 0
snd_seq_oss 29792 0
snd_seq_midi_event 5980 1 snd_seq_oss
snd_seq 47984 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6088 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37728 0
snd_mixer_oss 14300 1 snd_pcm_oss
ipv6 243508 16
cpufreq_ondemand 6632 1
speedstep_lib 3840 0
acpi_cpufreq 7500 0
freq_table 3420 2 cpufreq_ondemand,acpi_cpufreq
lp 9316 0
ppdev 7200 0
parport_pc 24036 1
parport 30700 3 lp,ppdev,parport_pc
fuse 54008 1
pcmcia 33772 0
snd_hda_codec_realtek 188544 1
tifm_sd 9572 0
snd_hda_intel 23624 6
mmc_core 45304 1 tifm_sd
rtc_cmos 10124 0
ipw2200 139688 0
snd_hda_codec 53788 2 snd_hda_codec_realtek,snd_hda_intel
e100 30660 0
yenta_socket 23848 1
rtc_core 15992 1 rtc_cmos
tifm_7xx1 5404 0
snd_hwdep 6816 1 snd_hda_codec
nvidia 9936196 41
rsrc_nonstatic 10876 1 yenta_socket
joydev 9504 0
libipw 25952 1 ipw2200
mii 4380 1 e100
snd_pcm 68128 5 snd_pcm_oss,snd_hda_intel,snd_hda_codec
tifm_core 6328 2 tifm_sd,tifm_7xx1
rtc_lib 2332 1 rtc_core
pcmcia_core 32016 3 pcmcia,yenta_socket,rsrc_nonstatic
thermal 15096 1
lib80211 5216 2 ipw2200,libipw
snd_timer 19108 4 snd_seq,snd_pcm
processor 38600 3 acpi_cpufreq,thermal
intel_agp 25628 0
snd 50820 19 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
video 16492 6
sony_laptop 31544 0
agpgart 29256 2 nvidia,intel_agp
soundcore 5824 1 snd
thermal_sys 10756 3 thermal,processor,video
battery 9856 0
psmouse 41676 0
i2c_i801 8784 0
output 2396 1 video
snd_page_alloc 7972 2 snd_hda_intel,snd_pcm
hwmon 2104 1 thermal_sys
serio_raw 5024 0
button 5708 0
evdev 9152 14
ac 3840 0
sulla chiavetta non è indicato nulla a parte MD-@ HSUPA e dovrebbe corrispondere a quella che sul sito HUAWEY è indicata come E180ZeroUno ha scritto: poi dacci il modello ESATTO della chiavetta; per qualcuna la 3 stessa fornisce i driver per linux, altre funzionano semplicemente con il modulo usbserial.
grazie mille
- ZeroUno
- Staff
- Messaggi: 5441
- Iscritto il: ven 2 giu 2006, 14:52
- Nome Cognome: Matteo Rossini
- Slackware: current
- Kernel: slack-current
- Desktop: ktown-latest
- Distribuzione: 01000000-current
- Località: Roma / Castelli
- Contatta:
Re: slackware 13 e momodesign H3G
Il tuo non è un problema di driver; hai un chipset compatibile E220 (product id=1003) che è supportato dal kernel di linux.
Io ho una E122 che non è supportato dal kernel (product id=1446) ma al suo interno ho il driver per linux, che mi emula l'id 1003, e il software di connessione della tre (che è lo stesso di windows).
Come prima cosa occhio all'apn (io ci ho sbattuto la testa):
3 in abbonamento è datacard.tre.it
3 in ricaricabile è tre.it
quando usavo kppp mi sembra che in /etc/ppp/options avevo dovuto mettere noauth (e togliere username ecc)
se vuoi ti posso passarti quel software (non saprei dove scaricarlo).
sono c.a. 6M più la java virtual machine da scaricare dal sito ufficiale.
Oltre che sulla mia l'ho provato anche sulla 156G e funziona.
Come quello di windows mostra la rete a cui si è connessi (H3G,UMTS..), la potenza del segnale e la velocità di down/upload
Ne volevo fare un pacchetto slacky ma non ho avuto tempo (e non so se avrei potuto farlo, sinceramente; i driver sono distribuiti in GPL2, il tool non lo so)
Ciao
01
Io ho una E122 che non è supportato dal kernel (product id=1446) ma al suo interno ho il driver per linux, che mi emula l'id 1003, e il software di connessione della tre (che è lo stesso di windows).
Come prima cosa occhio all'apn (io ci ho sbattuto la testa):
3 in abbonamento è datacard.tre.it
3 in ricaricabile è tre.it
quando usavo kppp mi sembra che in /etc/ppp/options avevo dovuto mettere noauth (e togliere username ecc)
se vuoi ti posso passarti quel software (non saprei dove scaricarlo).
sono c.a. 6M più la java virtual machine da scaricare dal sito ufficiale.
Oltre che sulla mia l'ho provato anche sulla 156G e funziona.
Come quello di windows mostra la rete a cui si è connessi (H3G,UMTS..), la potenza del segnale e la velocità di down/upload
Ne volevo fare un pacchetto slacky ma non ho avuto tempo (e non so se avrei potuto farlo, sinceramente; i driver sono distribuiti in GPL2, il tool non lo so)
Ciao
01
Packages finder: slakfinder.org | Slackpkg+, per aggiungere repository a slackpkg
Codice: Seleziona tutto
1011010 1100101 1110010 1101111 - 0100000 - 1010101 1101110 1101111
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
Re: slackware 13 e momodesign H3G
siccome mi collego ad internet ma non riesco ad andare in rete mi pare proprio che sia un problame non di driver ma di impostazioni della connessione... mipotresti dare qualche dritta in più in merito al file /etc/ppp/options???ZeroUno ha scritto:Il tuo non è un problema di driver; hai un chipset compatibile E220 (product id=1003) che è supportato dal kernel di linux.
quando usavo kppp mi sembra che in /etc/ppp/options avevo dovuto mettere noauth (e togliere username ecc)
- ZeroUno
- Staff
- Messaggi: 5441
- Iscritto il: ven 2 giu 2006, 14:52
- Nome Cognome: Matteo Rossini
- Slackware: current
- Kernel: slack-current
- Desktop: ktown-latest
- Distribuzione: 01000000-current
- Località: Roma / Castelli
- Contatta:
Re: slackware 13 e momodesign H3G
Ora uso il tool, ma quando usavo kppp se ricordo bene
invece il tool della 3 al ps mostra:
in cui huwei-ppp-on-dialer è
(che alla fine dovrebbe essere il pppscript)
Ciao
01
Codice: Seleziona tutto
lock
defaultroute
noipdefault
modem
/dev/ttyUSB0
460800
crtscts
# Uncomment the line below for more verbose error reporting:
#debug
noauth
passive
asyncmap 0
#name "guest"
Codice: Seleziona tutto
pppd linkname HuaweiMobile telephone "*99#" -chap lock crtscts modem /dev/ttyUSB_utps_modem 115200 usepeerdns noauth noipdefault defaultroute name password connect /usr/local/hw_pppd/etc/ppp/huawei-ppp-on-dialer
Codice: Seleziona tutto
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
# Modify: Derek116@huawei.com
#
MYHWPATH=/usr/local/hw_pppd
"$MYHWPATH"/sbin/chat -v \
TIMEOUT 25 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
ABORT '\nUsername/Password Incorrect\r' \
SAY "Beginning...\n" \
'' AT \
'' ATH0 \
SAY "Dialing up...$TELEPHONE\n" \
OK ATDT$TELEPHONE \
CONNECT \c \
SAY "Logging...\n" \
Ciao
01
Packages finder: slakfinder.org | Slackpkg+, per aggiungere repository a slackpkg
Codice: Seleziona tutto
1011010 1100101 1110010 1101111 - 0100000 - 1010101 1101110 1101111
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
Re: slackware 13 e momodesign H3G
nulla ho provato con tutti i settaggi che mi hai consigliato ma non ho risolto nulla... mi sa tanto che è un problema di DNS domini e cose del genere...perchè il modem è riconosciuto a si collega solo che non naviga e non pinga....
- joe
- Iper Master
- Messaggi: 3797
- Iscritto il: ven 27 apr 2007, 11:21
- Slackware: 15.0
- Kernel: 5.15.38
- Desktop: dwm
Re: slackware 13 e momodesign H3G
Ma scusa, se dai
ifconfig ppp0
cosa dice?
Con quello vedi se sei connesso.
Inoltre, prova a pingare un indirizzo numerico, ad esempio confronta i due comandi seguenti:
Se un comando funziona (quello con indirizzo numerico) e l'altro no, allora è probabilmente proprio un problema di dns, pertanto modifica /etc/resov.conf, mettendo per esempio i dns di opendns, tanto per provare:
Vedi un po'.
Io in ogni caso preferisco gestire a mano la connessione, uso un cellulare e sono con tim.
Me lo vede come /dev/rfcomm0 in quanto lo collego via bluetooth.
Uso due files:
/etc/ppp/peers/btgprs
/etc/ppp/gprs
e avvio la connessione col comando:
pppd call btgprs
Saluti.
ifconfig ppp0
cosa dice?
Con quello vedi se sei connesso.
Inoltre, prova a pingare un indirizzo numerico, ad esempio confronta i due comandi seguenti:
Codice: Seleziona tutto
# ping maya.ngi.it
PING maya.ngi.it (88.149.128.3) 56(84) bytes of data.
64 bytes from maya.ngi.it (88.149.128.3): icmp_seq=1 ttl=50 time=779 ms
64 bytes from maya.ngi.it (88.149.128.3): icmp_seq=2 ttl=50 time=999 ms
^C
--- maya.ngi.it ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 3795ms
rtt min/avg/max/mdev = 779.597/889.746/999.896/110.153 ms
# ping 88.149.128.3
PING 88.149.128.3 (88.149.128.3) 56(84) bytes of data.
64 bytes from 88.149.128.3: icmp_seq=1 ttl=50 time=435 ms
64 bytes from 88.149.128.3: icmp_seq=2 ttl=50 time=486 ms
64 bytes from 88.149.128.3: icmp_seq=3 ttl=50 time=441 ms
64 bytes from 88.149.128.3: icmp_seq=4 ttl=50 time=474 ms
^C
--- 88.149.128.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3025ms
rtt min/avg/max/mdev = 435.778/459.562/486.316/21.306 ms
Codice: Seleziona tutto
# cat /etc/resolv.conf
# open dns
#
nameserver 208.67.222.222
nameserver 208.67.220.220
Io in ogni caso preferisco gestire a mano la connessione, uso un cellulare e sono con tim.
Me lo vede come /dev/rfcomm0 in quanto lo collego via bluetooth.
Uso due files:
/etc/ppp/peers/btgprs
/etc/ppp/gprs
e avvio la connessione col comando:
pppd call btgprs
Saluti.
-
- Linux 0.x
- Messaggi: 17
- Iscritto il: gio 6 gen 2005, 0:00
- Nome Cognome: Luciano Rinaldi
- Slackware: 13.0
- Kernel: 2.6.29.6
- Desktop: xfce 4.6.1
- Località: Brescia
Re: slackware 13 e momodesign H3G
Ciao,
io ho la tua stessa chiavetta:
lsusb:
Bus 001 Device 006: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
cat /var/log/messages
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: new high speed USB device using ehci_hcd and address 6
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: New USB device found, idVendor=12d1, idProduct=1003
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: Product: HUAWEI Mobile
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: Manufacturer: HUAWEI Technology
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: configuration #1 chosen from 1 choice
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver usbserial
Apr 30 20:51:02 HP-CIANO kernel: USB Serial support registered for generic
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver usbserial_generic
Apr 30 20:51:02 HP-CIANO kernel: usbserial: USB Serial Driver core
Apr 30 20:51:02 HP-CIANO kernel: USB Serial support registered for GSM modem (1-port)
Apr 30 20:51:02 HP-CIANO kernel: option 1-4:1.0: GSM modem (1-port) converter detected
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
Apr 30 20:51:02 HP-CIANO kernel: option 1-4:1.1: GSM modem (1-port) converter detected
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver option
Apr 30 20:51:02 HP-CIANO kernel: option: v0.7.2:USB Driver for GSM modems
Per collegarmi io uso kppp:
ho creato una nuova connessione con queste caratteristiche:
numero da chiamare *99#
autenticazione PAP
Modem /dev/ttyUSB0
non credo di avere cambiato altro....
Metto solo un nome qualsiasi per connettermi, e poi navigo come adesso....
Ciao.
io ho la tua stessa chiavetta:
lsusb:
Bus 001 Device 006: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
cat /var/log/messages
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: new high speed USB device using ehci_hcd and address 6
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: New USB device found, idVendor=12d1, idProduct=1003
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: Product: HUAWEI Mobile
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: Manufacturer: HUAWEI Technology
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: configuration #1 chosen from 1 choice
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver usbserial
Apr 30 20:51:02 HP-CIANO kernel: USB Serial support registered for generic
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver usbserial_generic
Apr 30 20:51:02 HP-CIANO kernel: usbserial: USB Serial Driver core
Apr 30 20:51:02 HP-CIANO kernel: USB Serial support registered for GSM modem (1-port)
Apr 30 20:51:02 HP-CIANO kernel: option 1-4:1.0: GSM modem (1-port) converter detected
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
Apr 30 20:51:02 HP-CIANO kernel: option 1-4:1.1: GSM modem (1-port) converter detected
Apr 30 20:51:02 HP-CIANO kernel: usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
Apr 30 20:51:02 HP-CIANO kernel: usbcore: registered new interface driver option
Apr 30 20:51:02 HP-CIANO kernel: option: v0.7.2:USB Driver for GSM modems
Per collegarmi io uso kppp:
ho creato una nuova connessione con queste caratteristiche:
numero da chiamare *99#
autenticazione PAP
Modem /dev/ttyUSB0
non credo di avere cambiato altro....
Metto solo un nome qualsiasi per connettermi, e poi navigo come adesso....
Ciao.
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
Re: slackware 13 e momodesign H3G
a me pare proprio un problema di indirizzi e cose del genere cercherò di risolvere in qualche modo....durante l'installazione ho inserito qualche configurazione su hostname domainname e cose del genere non vorrei che dipenda da quello...
- joe
- Iper Master
- Messaggi: 3797
- Iscritto il: ven 27 apr 2007, 11:21
- Slackware: 15.0
- Kernel: 5.15.38
- Desktop: dwm
Re: slackware 13 e momodesign H3G
Ma hai provato la procedura che ti avevo suggerito? Almeno sgombri i dubbi dalla questione dns. è un test che ti impiega una manciata di secondi.
Dopo se non risolverai allora potrai controllare più accuratamente altri aspetti, secondo me un po' più complicati...
Dopo se non risolverai allora potrai controllare più accuratamente altri aspetti, secondo me un po' più complicati...
-
- Linux 0.x
- Messaggi: 24
- Iscritto il: ven 10 set 2004, 0:00
Re: slackware 13 e momodesign H3G
risolto....ho dato un netconfig... dopo di che mi sono connesso e con:
ho risolto...
grazie mille a tutti gli intervenuti per il supporto
Codice: Seleziona tutto
route add default ppp0
grazie mille a tutti gli intervenuti per il supporto
- joe
- Iper Master
- Messaggi: 3797
- Iscritto il: ven 27 apr 2007, 11:21
- Slackware: 15.0
- Kernel: 5.15.38
- Desktop: dwm
Re: slackware 13 e momodesign H3G
Aggiungo che la direttiva:
defaultroute
messa nello script di pppd, o attraverso kppp o wvdial o chi per esso, crea automaticamente il defualt route attraverso ppp0 alla connessione.
defaultroute
messa nello script di pppd, o attraverso kppp o wvdial o chi per esso, crea automaticamente il defualt route attraverso ppp0 alla connessione.