| View previous topic :: View next topic |
| Author |
Message |
GaugeTheory
Apprentice
Joined: 03 Oct 2004
Posts: 212
Location: Genoa, Italy
|
 Posted: Tue Dec 21, 2004 6:43 pm Post subject: Fotocamera usb |
 |
|
Ho una fotocamera digitale usb Sony nuova.
Vorrei poter scaricare le foto con linux, e non necessariamente da root. Non ho la minima idea di cosa fare.
Da altri posts ho sentito che sono necessati alcuni moduli nel kernel: sapete quali?
Ho sentito parlare anche di udev ed autofs: cosa sono? A cosa servono?
Grazie 
Ciao !!
_________________
Considerate la vostra semenza:.................Consider your seed:
Fatti non foste a viver come bruti,.............You weren't made to live like brutes,
Ma per seguir virtute e conoscenza..........But to follow wisdom and knowledge.
(Dante Alighieri) |
|
| Back to top |
|
 |
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Tue Dec 21, 2004 6:47 pm Post subject: |
|
|
Faresti bene a fare una ricerca sul forum e iniziare con leggere qualcosa.
Poi non appena hai un problema chiaro da esporre ce lo presenti.
P.S. Il mio è solo un consiglio 
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
flocchini
Veteran
Joined: 17 May 2003
Posts: 1124
Location: Milano, Italy
|
| Posted: Wed Dec 22, 2004 1:52 am Post subject: |
|
|
sottoscrivo quanto detto da gutter, ma siccome 'e natale aggiungo qualcosina... 
Solitamente (mica detto pero' eh  ) le fotocamere usb vengono riconosciute come dischi scsi: abilita quindi gli opportuni moduli del kernel e dai un'occhiata al dmesg quando colleghil'apparecchio, dovresti vedere a quale device viene associato, comodamente montabile dove meglio credi. Olympus, fuji e kodak si comportano come ho detto, almeno i modelli da me provati
_________________
~~ Per amore della rosa si sopportano le spine... ~~ |
|
| Back to top |
|
|
stefanonafets
l33t
Joined: 10 Feb 2003
Posts: 644
|
| Posted: Wed Dec 22, 2004 2:10 am Post subject: |
|
|
Per essere ancora + precisi, i moduli che ti servono sono scsi_mod, sd_mod, usbcore, uno tra ohci_hcd ehci_hcd o uhci_hcd (dipende dal chip della mobo), e (se nn erro) usb_storage.
Dando #dmesg dopo aver caricato i moduli ed aver inserito la fotocametra, potrai controllare che nome ha dato al dispositivo (in genere sdxy, ddove xy sono due numeri).
_________________
registered Linux user number #411324
sed 's/ke/che/g'
<The Deployment Slave is initializing> |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31461
Location: here
|
| Posted: Wed Dec 22, 2004 6:44 am Post subject: |
|
|
@flocchini e stefanonafets: Non necessariamente e' la fotocamera che deve permettere il usb-storage se no deve usare i driver gphoto
@GaugeTheory: che modello e'?
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
GaugeTheory
Apprentice
Joined: 03 Oct 2004
Posts: 212
Location: Genoa, Italy
|
| Posted: Fri Jan 07, 2005 8:22 pm Post subject: |
|
|
Dove si trovano, su xconfig, i moduli scsi_mod, sd_mod ?
_________________
Considerate la vostra semenza:.................Consider your seed:
Fatti non foste a viver come bruti,.............You weren't made to live like brutes,
Ma per seguir virtute e conoscenza..........But to follow wisdom and knowledge.
(Dante Alighieri) |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31461
Location: here
|
| Posted: Fri Jan 07, 2005 8:45 pm Post subject: |
|
|
| GaugeTheory wrote: | | Dove si trovano, su xconfig, i moduli scsi_mod, sd_mod ? |
| Code: | Device Drivers ---> SCSI device support --->
<*> SCSI device support
<*> SCSI disk support
<*> SCSI generic support |
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
GaugeTheory
Apprentice
Joined: 03 Oct 2004
Posts: 212
Location: Genoa, Italy
|
| Posted: Mon Jan 10, 2005 5:41 pm Post subject: |
|
|
Ho controllato, e ho tutte le voci richieste attivate nel kernel, alcune come built-in altre come moduli. Ho dati il comando dmesg e questo è il risultato: | Code: | >Calibrating delay loop... 4276.22 BogoMIPS (lpj=2138112)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 3000+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: IRQ9 SCI: Level Trigger.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfa440, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0, disabled.
ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0, disabled.
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled.
ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Using ACPI for IRQ routing
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:10.1[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:10.2[B] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:10.3[B] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:10.4[C] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:13.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 10 (level, low) -> IRQ 10
Machine check exception polling timer started.
gx-suspmod: error: no MediaGX/Geode processor found!
speedstep-smi: No Intel CPU detected.
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with large block numbers, no debug enabled
Initializing Cryptographic API
Real Time Clock Driver v1.12
Non-volatile memory driver v1.2
vesafb: ATI Technologies Inc., R350, 01.00 (OEM: ATI R350)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:577e
vesafb: pmi: set display start = c00c5812, set palette = c00c585e
vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2 a0b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
vesafb: framebuffer at 0xd8000000, mapped to 0xf8880000, size 16384k
fb0: VESA VGA frame buffer device
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU0] (supports C1)
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Using cfq io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
8139too Fast Ethernet driver 0.9.27
ACPI: PCI interrupt 0000:00:13.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf8802000, 00:0d:61:27:c1:60, IRQ 11
eth0: Identified 8139 chip type 'RTL-8101'
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 5 (level, low) -> IRQ 5
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0xc800-0xc807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xc808-0xc80f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: MAXTOR 6L040J2, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: PIONEER DVD-RW DVR-107D, ATAPI CD/DVD-ROM drive
hdd: LITE-ON LTR-48246S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 128KiB
hda: 78177792 sectors (40027 MB) w/1820KiB Cache, CHS=65535/16/63, UDMA(33)
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 p6 p7 p8 p9 >
hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
libata version 1.02 loaded.
sata_via version 0.20
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 11 (level, low) -> IRQ 11
sata_via(0000:00:0f.0): routed to hard irq line 11
ata1: SATA max UDMA/133 cmd 0xB000 ctl 0xB402 bmdma 0xC000 irq 11
ata2: SATA max UDMA/133 cmd 0xB800 ctl 0xBC02 bmdma 0xC008 irq 11
ata1: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:407f
ata1: dev 0 ATA, max UDMA/133, 72303840 sectors: lba48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_via
ata2: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:407f
ata2: dev 0 ATA, max UDMA/133, 72303840 sectors: lba48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_via
Vendor: ATA Model: WDC WD360GD-00FN Rev: 35.0
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD360GD-00FN Rev: 35.0
Type: Direct-Access ANSI SCSI revision: 05
st: Version 20040403, fixed bufsize 32768, s/g segs 256
SCSI device sda: 72303840 512-byte hdwr sectors (37020 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1 p4 < p5 p6 p7 p8 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 72303840 512-byte hdwr sectors (37020 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host1/bus0/target0/lun0: p1 p4 < p5 p6 p7 p8 >
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Processor cpuid 6a0 not supported
ACPI: (supports S0 S1 S4 S5)
ACPI wakeup devices:
PCI0 USB0 USB1 USB2 USB6 USB7 USB8 USB9 UAR1 LPT1
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb8 ...
md: adding sdb8 ...
md: sdb7 has different UUID to sdb8
md: sdb5 has different UUID to sdb8
md: sdb1 has different UUID to sdb8
md: adding sda8 ...
md: sda7 has different UUID to sdb8
md: sda5 has different UUID to sdb8
md: sda1 has different UUID to sdb8
md: created md3
md: bind<sda8>
md: bind<sdb8>
md: running: <sdb8><sda8>
raid1: raid set md3 active with 2 out of 2 mirrors
md: considering sdb7 ...
md: adding sdb7 ...
md: sdb5 has different UUID to sdb7
md: sdb1 has different UUID to sdb7
md: adding sda7 ...
md: sda5 has different UUID to sdb7
md: sda1 has different UUID to sdb7
md: created md2
md: bind<sda7>
md: bind<sdb7>
md: running: <sdb7><sda7>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering sdb5 ...
md: adding sdb5 ...
md: sdb1 has different UUID to sdb5
md: adding sda5 ...
md: sda1 has different UUID to sdb5
md: created md1
md: bind<sda5>
md: bind<sdb5>
md: running: <sdb5><sda5>
md1: setting max_sectors to 64, segment boundary to 16383
raid0: looking at sdb5
raid0: comparing sdb5(6144704) with sdb5(6144704)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sda5
raid0: comparing sda5(6144704) with sdb5(6144704)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 12289408 blocks.
raid0 : conf->hash_spacing is 12289408 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
VFS: Mounted root (reiser4 filesystem) readonly.
Freeing unused kernel memory: 184k freed
Adding 1052216k swap on /dev/sda6. Priority:-1 extents:1
Adding 1052216k swap on /dev/sdb6. Priority:-2 extents:1
ReiserFS: md2: found reiserfs format "3.6" with standard journal
ReiserFS: md2: using ordered data mode
ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: md2: checking transaction log (md2)
ReiserFS: md2: Using r5 hash to sort names
ReiserFS: md3: found reiserfs format "3.6" with standard journal
ReiserFS: md3: using ordered data mode
ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: md3: checking transaction log (md3)
ReiserFS: md3: Using r5 hash to sort names
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:11.5 to 64
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: AGP aperture is 128M @ 0xd0000000
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:00:10.0: irq 10, io base 0000cc00
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.1[A] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller(#2)
uhci_hcd 0000:00:10.1: irq 10, io base 0000d000
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.2[B] -> GSI 5 (level, low) -> IRQ 5
uhci_hcd 0000:00:10.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller(#3)
uhci_hcd 0000:00:10.2: irq 5, io base 0000d400
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.3[B] -> GSI 5 (level, low) -> IRQ 5
uhci_hcd 0000:00:10.3: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller(#4)
uhci_hcd 0000:00:10.3: irq 5, io base 0000d800
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.4[C] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 0000:00:10.4: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:00:10.4: irq 11, pci mem f9b2a000
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:10.4: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 10 (level, low) -> IRQ 10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[ea002000-ea0027ff] Max Packet=[2048]
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
usb 5-3: new high speed USB device using address 2
hub 5-3:1.0: USB hub found
hub 5-3:1.0: 4 ports detected
usb 4-1: new full speed USB device using address 2
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4004
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00000d6100244f26]
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
lp0: using parport0 (polling).
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x1000000
atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
usb 5-3.1: new high speed USB device using address 4
atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
|
Non ci capisco granché 
_________________
Considerate la vostra semenza:.................Consider your seed:
Fatti non foste a viver come bruti,.............You weren't made to live like brutes,
Ma per seguir virtute e conoscenza..........But to follow wisdom and knowledge.
(Dante Alighieri) |
|
| Back to top |
|
|
randomaze
Bodhisattva
Joined: 21 Oct 2003
Posts: 9985
|
| Posted: Mon Jan 10, 2005 6:57 pm Post subject: |
|
|
| GaugeTheory wrote: | Ho dati il comando dmesg e questo è il risultato:
|
E'solo la mia impressione oppure quel comando lo hai dato senza aver collegato la macchina fotografica?
_________________
Ciao da me! |
|
| Back to top |
|
|
iDreamer
Guru
Joined: 23 Jan 2004
Posts: 317
Location: Corigliano Calabro(CS)
|
| Posted: Mon Jan 10, 2005 7:54 pm Post subject: |
|
|
anche secondo me..
per quando riguarda se scsi lo è al99,9% dei casi perchè ha detto che è nuova e per esperianza personale me la prende come scsi..
@GaugeTheory:cmq basta che posti le ultime 10 righe...
e cmq ti deve apparire una cosa del genere o molto simile
| Code: | scsi4 : SCSI emulation for USB Mass Storage devices
Vendor: Shuttle Model: MasQSt Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda: unknown partition table
Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi4, channel 0, id 0, lun 0, type 0
USB Mass Storage device found at 10
|
_________________
.::..::.iDreamer.::..::.
^__^ -> HH: Happy Hacking |
|
| Back to top |
|
|
Spacerabbit
n00b
Joined: 06 Nov 2003
Posts: 69
Location: Beta Fornax
|
| Posted: Mon Jan 10, 2005 10:59 pm Post subject: |
|
|
anch'io ho una fotocamera usb casio, ma non ho l'esperienza dei miei illustrissimi e stimatissimi amici.
Una volta che sarai riuscito a riconoscere l'hw caricando tutti i moduli detti, modifica /etc/fstab in modo da montare il disco scsi (che in realta' e' la fotocamera) in vfat, dandogli le opzioni per il montaggio da utente come fosse una partizione fat32. In questo modo io ho ottenuto cio' che volevo: l'utente puo' montare la macchina e ci posso browsare dentro come fosse un disco.
spero di esserti stata utile |
|
| Back to top |
|
|
Crema83
Apprentice
Joined: 06 Oct 2004
Posts: 207
Location: Settimo Milanese (MI)
|
| Posted: Tue Jan 11, 2005 8:52 am Post subject: |
|
|
| Spacerabbit wrote: | anch'io ho una fotocamera usb casio, ma non ho l'esperienza dei miei illustrissimi e stimatissimi amici.
Una volta che sarai riuscito a riconoscere l'hw caricando tutti i moduli detti, modifica /etc/fstab in modo da montare il disco scsi (che in realta' e' la fotocamera) in vfat, dandogli le opzioni per il montaggio da utente come fosse una partizione fat32. In questo modo io ho ottenuto cio' che volevo: l'utente puo' montare la macchina e ci posso browsare dentro come fosse un disco.
spero di esserti stata utile |
Non sarebbe meglio utilizzare l'opzione auto per il tipo di filesystem???
_________________
Cream
" We live as we dream : ALONE " |
|
| Back to top |
|
|
scheggia
n00b
Joined: 16 Apr 2003
Posts: 11
|
| Posted: Tue Jan 11, 2005 11:17 am Post subject: |
|
|
| Per curiosità, che modello è della Sony ? Io ne uso tranquillamente una con gphoto2. |
|
| Back to top |
|
|
GaugeTheory
Apprentice
Joined: 03 Oct 2004
Posts: 212
Location: Genoa, Italy
|
| Posted: Tue Jan 11, 2005 11:30 am Post subject: |
|
|
Ho una Sony Cyber-shot DSC-W1
Per quanto riguarda il collegamento, ho fatto così, non so se sia la procedura giusta:
1) ho collegato il cavo usb alla macchina fotografica e a un ripetitore anteriore usb del computer
2) ho acceso la macchina fotografica.
Dopo ho dato il comando dmesg
_________________
Considerate la vostra semenza:.................Consider your seed:
Fatti non foste a viver come bruti,.............You weren't made to live like brutes,
Ma per seguir virtute e conoscenza..........But to follow wisdom and knowledge.
(Dante Alighieri) |
|
| Back to top |
|
|
Spacerabbit
n00b
Joined: 06 Nov 2003
Posts: 69
Location: Beta Fornax
|
| Posted: Tue Jan 11, 2005 1:41 pm Post subject: |
|
|
| Crema83 wrote: |
Non sarebbe meglio utilizzare l'opzione auto per il tipo di filesystem??? |
beh non ci avevo pensato ma penso di si
ora aggiorno il mio fstab
grazie Crema83 |
|
| Back to top |
|
|
lavish
Bodhisattva
Joined: 13 Sep 2004
Posts: 4296
|
| Posted: Tue Jan 11, 2005 1:57 pm Post subject: |
|
|
| Spacerabbit wrote: | | Crema83 wrote: |
Non sarebbe meglio utilizzare l'opzione auto per il tipo di filesystem??? |
beh non ci avevo pensato ma penso di si
ora aggiorno il mio fstab
grazie Crema83 |
Oppure ancora meglio impostare varie regole di udev (mettendo udev ) per i vari devices che si hanno... e creare stringhe dedicate in fstab
_________________
minimalblue.com | secgroup.github.io/ |
|
| Back to top |
|
|
Crema83
Apprentice
Joined: 06 Oct 2004
Posts: 207
Location: Settimo Milanese (MI)
|
| Posted: Tue Jan 11, 2005 5:25 pm Post subject: |
|
|
| lavish wrote: |
Oppure ancora meglio impostare varie regole di udev (mettendo udev ) per i vari devices che si hanno... e creare stringhe dedicate in fstab
|
Effettivamente sarebbe la cosa migliore... Io però ho provato a seguire le indicazioni trovate sul nuovo Wiki di Gentoo-Italia (http://wiki.gentoo-italia.net/index.php/Mappare_i_device_con_udev) ma non ci sono riuscito...non mi riconosceva i device che avevo creato... 
_________________
Cream
" We live as we dream : ALONE " |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Forum italiano (Italian)
