Pagina 1 di 2
problema card reader interno
Inviato: venerdì 7 ottobre 2011, 12:02
da ormo
Apro un nuovo thread dato che il vecchio col tag risolto è gia caduto in terza pagina.
Ciao
Ho trovato e letto il thread dopo una ricerca su sangoogle
Ho il medesimo problema con un card reader interno "dynamode"
Cercando di ripetere la sequenza di comandi esploratuivi credo di aver capito che sto reader non viene granchè preso in considerazione dal sistema:
lspci restituisce:
Codice: Seleziona tutto
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation 2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.7 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 8 (rev b5)
00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation P67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation Device 1244 (rev a1)
01:00.1 Audio device: nVidia Corporation Device 0bee (rev a1)
03:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
06:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
08:00.0 PCI bridge: Device 1b21:1080 (rev 01)
09:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
0a:00.0 SATA controller: Marvell Technology Group Ltd. Device 9172 (rev 11)
lsusb:
Codice: Seleziona tutto
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0b05:179c ASUSTek Computer, Inc.
Bus 002 Device 003: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0cf2:6230 ENE Technology, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsmod:
Codice: Seleziona tutto
Module Size Used by
mmc_block 18053 0
pci_stub 12622 1
vboxpci 23190 0
vboxnetadp 13382 0
vboxnetflt 23435 0
vboxdrv 286726 3 vboxpci,vboxnetadp,vboxnetflt
nls_iso8859_1 12713 0
nls_cp437 16991 0
vfat 21708 0
fat 61374 1 vfat
binfmt_misc 17565 1
dm_crypt 22993 0
parport_pc 36959 0
ppdev 17113 0
vesafb 13761 1
snd_hda_codec_hdmi 28167 4
rfcomm 47694 8
snd_hda_codec_realtek 336771 1
sco 18187 2
bnep 18308 2
l2cap 53570 16 rfcomm,bnep
snd_hda_intel 33176 6
snd_hda_codec 103804 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13604 1 snd_hda_codec
snd_seq_midi 13324 0
snd_pcm 96391 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_rawmidi 30486 1 snd_seq_midi
snd_seq_midi_event 14899 1 snd_seq_midi
snd_seq 61621 2 snd_seq_midi,snd_seq_midi_event
snd_timer 29602 2 snd_pcm,snd_seq
snd_seq_device 14462 3 snd_seq_midi,snd_rawmidi,snd_seq
snd 67382 21 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
lp 17825 0
nvidia 10709116 28
btusb 18600 2
soundcore 12680 1 snd
bluetooth 72320 9 rfcomm,sco,bnep,l2cap,btusb
eeepc_wmi 19323 0
snd_page_alloc 18529 2 snd_hda_intel,snd_pcm
parport 46458 3 parport_pc,ppdev,lp
sparse_keymap 13898 1 eeepc_wmi
usbhid 46956 0
hid 91020 1 usbhid
usb_storage 53538 1
uas 17996 0
firewire_ohci 40370 0
firewire_core 62646 1 firewire_ohci
crc_itu_t 12707 1 firewire_core
xhci_hcd 77643 0
r8169 48022 0
ahci 25951 5
libahci 26642 1 ahci
non vedo nulla io o sbaglio qualcosa?
La periferica è connessa con il connettore usb interno alla mobo.
Quando inserisco una pendrive usb nel pannello di questo card reader essa viene montata automaticamente e accedo RW
quando inserisco una sd apparentemente non fa nulla ma:
nell'imediato dmesg:
Codice: Seleziona tutto
[69092.714523] sde: detected capacity change from 4030726144 to 0
[69094.831610] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[69094.832071] sd 8:0:0:3: [sde] Assuming drive cache: write through
[69094.833223] sd 8:0:0:3: [sde] Assuming drive cache: write through
dopo 5 minuti accoda:
Codice: Seleziona tutto
[69274.717142] sd 8:0:0:3: timing out command, waited 180s
[69274.717152] sd 8:0:0:3: [sde] Unhandled sense code
[69274.717155] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[69274.717158] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[69274.717163] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[69274.717167] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[69274.717176] end_request: I/O error, dev sde, sector 0
[69274.717180] quiet_error: 1 callbacks suppressed
[69274.717183] Buffer I/O error on device sde, logical block 0
[69454.593033] sd 8:0:0:3: timing out command, waited 180s
[69454.593043] sd 8:0:0:3: [sde] Unhandled sense code
[69454.593045] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[69454.593049] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[69454.593054] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[69454.593058] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[69454.593067] end_request: I/O error, dev sde, sector 0
[69454.593071] Buffer I/O error on device sde, logical block 0
stessa cosa con una transflash oppure quando pluggo una nikon D40, con sd inserita, tramite connessione usb.
la macchina viene riconosciuta ma poi i soliti hardware error.
che ne pensate?
Re: problema card reader interno
Inviato: sabato 8 ottobre 2011, 22:48
da magozurlinux
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0b05:179c ASUSTek Computer, Inc.
Bus 002 Device 003: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0cf2:6230 ENE Technology, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
quello evidenziato in rosso è il tuo card reader interno.
Un utente a cui ho risolto il problema del card reader; il suo era su scheda PCI e non usb.
Prova così:
da terminale dai questo comando:
inserisci una SD nel lettore per vedere se la legge correttamente.
Re: problema card reader interno
Inviato: domenica 9 ottobre 2011, 17:57
da ormo
Niente da fare, non monta
dmesg:
Codice: Seleziona tutto
[318617.936439] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[318617.937047] sd 8:0:0:3: [sde] Assuming drive cache: write through
[318617.938147] sd 8:0:0:3: [sde] Assuming drive cache: write through
[318797.806448] sd 8:0:0:3: timing out command, waited 180s
[318797.806459] sd 8:0:0:3: [sde] Unhandled sense code
[318797.806461] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[318797.806465] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[318797.806470] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[318797.806474] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[318797.806483] end_request: I/O error, dev sde, sector 0
[318797.806487] quiet_error: 154 callbacks suppressed
[318797.806490] Buffer I/O error on device sde, logical block 0
per curiosità come hai fatto ad individuare l'hardware?
A prescindere, girovagando sono arrivato qui:
http://hardware4linux.info/manufacturer/1281/65/
e poi qui:
http://cateee.net/lkddb/web-lkddb/USB_ENESTORAGE.html
Mi pare di aver capito che devo compilare se non il solo driver devo mettere mani al kernel?
Re: problema card reader interno
Inviato: domenica 9 ottobre 2011, 19:27
da magozurlinux
Altrimenti che mago sarei!
basta immettere sul motore di ricerca VendorID e ProductID (
0cf2:6230) e ti dice a quale dispositivo si riferisce, oppure puoi dare questo comando da terminale:
Re: problema card reader interno
Inviato: domenica 9 ottobre 2011, 19:35
da magozurlinux
Da terminale col card reader inserito postami questo comando:
forse con una regola udev è possibile forzare il funzionamento del tuo card reader; però non ti garantisco che funziona, perchè mi sto cimentando ora a provare delle regole udev.
Ciao
Re: problema card reader interno
Inviato: domenica 9 ottobre 2011, 19:41
da ormo
ls:
Codice: Seleziona tutto
ormo@dabox:~$ ls /sys/class/block
loop0 loop3 loop6 ram1 ram12 ram15 ram4 ram7 sda sda5 sda8 sdd
loop1 loop4 loop7 ram10 ram13 ram2 ram5 ram8 sda1 sda6 sdb sde
loop2 loop5 ram0 ram11 ram14 ram3 ram6 ram9 sda2 sda7 sdc sr0
ho trovato qualcosa riguardante il card reader, lo pasto pure qui:
http://hardware4linux.info/manufacturer/1281/65/
http://cateee.net/lkddb/web-lkddb/USB_ENESTORAGE.html
nel secondo link ci sono un paio di link a dei .c
da compilare... e poi come caricare?...se non sto dicendo baggianate.
cmq grazie dello sbattimento.
Re: problema card reader interno
Inviato: lunedì 10 ottobre 2011, 12:21
da magozurlinux
Prego, di nulla.
da terminale dai questo comando:
inserisci una SD nel lettore di schedine, vedi se visualizza il contenuto.
Da terminale con la SD inserita postami questi comandi:
Re: problema card reader interno
Inviato: lunedì 10 ottobre 2011, 17:00
da ormo
fdisk
Codice: Seleziona tutto
Disco /dev/sda: 1000.2 GB, 1000204886016 byte
255 testine, 63 settori/tracce, 121601 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x0002dd94
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 1 30401 244189184 83 Linux
/dev/sda2 30401 121602 732570625 5 Esteso
/dev/sda5 30401 32370 15819776 82 Linux swap / Solaris
/dev/sda6 32371 62765 244140032 83 Linux
/dev/sda7 62765 72977 82030592 83 Linux
/dev/sda8 72977 121602 390577152 83 Linux
ma resta appeso fino a quando non estraggo la scheda...
dmesg
Codice: Seleziona tutto
[400981.447711] sde: detected capacity change from 4030726144 to 0
[401103.486170] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[401103.486771] sd 8:0:0:3: [sde] Assuming drive cache: write through
[401103.487866] sd 8:0:0:3: [sde] Assuming drive cache: write through
[401283.356179] sd 8:0:0:3: timing out command, waited 180s
[401283.356188] sd 8:0:0:3: [sde] Unhandled sense code
[401283.356191] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[401283.356195] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[401283.356199] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[401283.356204] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[401283.356213] end_request: I/O error, dev sde, sector 0
[401283.356216] quiet_error: 5 callbacks suppressed
[401283.356219] Buffer I/O error on device sde, logical block 0
[401463.232092] sd 8:0:0:3: timing out command, waited 180s
[401463.232101] sd 8:0:0:3: [sde] Unhandled sense code
[401463.232104] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[401463.232108] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[401463.232112] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[401463.232117] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[401463.232126] end_request: I/O error, dev sde, sector 0
[401463.232129] Buffer I/O error on device sde, logical block 0
al solito, riconoscimento della capacità, dall'inserimento ai 3 minuti di timeout poi i/o error.
Re: problema card reader interno
Inviato: lunedì 10 ottobre 2011, 19:41
da magozurlinux
Proviamo a scrivere una regola udev.
ormo@dabox:~$ ls /sys/class/block
loop0 loop3 loop6 ram1 ram12 ram15 ram4 ram7 sda sda5 sda8 sdd
loop1 loop4 loop7 ram10 ram13 ram2 ram5 ram8 sda1 sda6 sdb sde
loop2 loop5 ram0 ram11 ram14 ram3 ram6 ram9 sda2 sda7 sdc sr0
[400981.447711] sde: detected capacity change from 4030726144 to 0
[401103.486170] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[401103.486771] sd 8:0:0:3: [sde] Assuming drive cache: write through
[401103.487866] sd 8:0:0:3: [sde] Assuming drive cache: write through
[401283.356179] sd 8:0:0:3: timing out command, waited 180s
[401283.356188] sd 8:0:0:3: [sde] Unhandled sense code
[401283.356191] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[401283.356195] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[401283.356199] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[401283.356204] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[401283.356213] end_request: I/O error, dev sde, sector 0
[401283.356216] quiet_error: 5 callbacks suppressed
[401283.356219] Buffer I/O error on device sde, logical block 0
[401463.232092] sd 8:0:0:3: timing out command, waited 180s
[401463.232101] sd 8:0:0:3: [sde] Unhandled sense code
[401463.232104] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[401463.232108] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[401463.232112] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[401463.232117] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[401463.232126] end_request: I/O error, dev sde, sector 0
[401463.232129] Buffer I/O error on device sde, logical block 0
Da terminale postami questo comando colla scheda SD inserita
oppure se non dovesse visualizzare nulla, postami questo:
Re: problema card reader interno
Inviato: lunedì 10 ottobre 2011, 20:56
da ormo
Rieccheme!
sudo udevadm info -a -p /sys/class/block/sde:
Codice: Seleziona tutto
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0/8:0:0:3/block/sde':
KERNEL=="sde"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="1"
ATTR{ro}=="0"
ATTR{size}=="7872512"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{capability}=="51"
ATTR{stat}==" 1 0 8 180010 0 0 0 0 1 185340 185340"
ATTR{inflight}==" 1 0"
ATTR{events}=="media_change"
ATTR{events_async}==""
ATTR{events_poll_msecs}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0/8:0:0:3':
KERNELS=="8:0:0:3"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="1"
ATTRS{type}=="0"
ATTRS{scsi_level}=="0"
ATTRS{vendor}=="USB2.0 "
ATTRS{model}=="CardReader SD "
ATTRS{rev}=="0100"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0x63d8"
ATTRS{iodone_cnt}=="0x63d8"
ATTRS{ioerr_cnt}=="0x63d0"
ATTRS{evt_media_change}=="0"
ATTRS{dh_state}=="detached"
ATTRS{queue_depth}=="1"
ATTRS{queue_type}=="none"
ATTRS{max_sectors}=="240"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0':
KERNELS=="target8:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8':
KERNELS=="host8"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0':
KERNELS=="1-1.4:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{supports_autosuspend}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4':
KERNELS=="1-1.4"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="498mA"
ATTRS{urbnum}=="391130"
ATTRS{idVendor}=="0cf2"
ATTRS{idProduct}=="6230"
ATTRS{bcdDevice}=="0100"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="3"
ATTRS{devpath}=="1.4"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="ENE Flash "
ATTRS{product}=="UB623X "
ATTRS{serial}=="606569746801"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="149"
ATTRS{idVendor}=="8087"
ATTRS{idProduct}=="0024"
ATTRS{bcdDevice}=="0000"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{devpath}=="1"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="6"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="24"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0002"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="2"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.38-11-generic ehci_hcd"
ATTRS{product}=="EHCI Host Controller"
ATTRS{serial}=="0000:00:1a.0"
ATTRS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1a.0':
KERNELS=="0000:00:1a.0"
SUBSYSTEMS=="pci"
DRIVERS=="ehci_hcd"
ATTRS{vendor}=="0x8086"
ATTRS{device}=="0x1c2d"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{subsystem_device}=="0x844d"
ATTRS{class}=="0x0c0320"
ATTRS{irq}=="23"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f"
ATTRS{local_cpulist}=="0-3"
ATTRS{numa_node}=="-1"
ATTRS{dma_mask_bits}=="32"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{enable}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
ATTRS{companion}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
sudo udevadm info -a -p /sys/class/block/sd
non ritorna nulla.
Re: problema card reader interno
Inviato: martedì 11 ottobre 2011, 18:37
da magozurlinux
Da terminale dai questo comando:
copia ed incolla queste righe:
Codice: Seleziona tutto
KERNEL="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="CardReader SD ", SYMLINK+="cfrdr%n", OPTIONS+="all_partitions"
salva ed esci dall'editor di testo.
Da terminale dai questo comando:
Riavvia il pc.
Re: problema card reader interno
Inviato: martedì 11 ottobre 2011, 20:49
da ormo
Purtroppo non è cambiato nulla, devo dare qualche permesso di avvio alla regola? tipo 755
Re: problema card reader interno
Inviato: giovedì 13 ottobre 2011, 12:58
da magozurlinux
No, non devi dare il permesso 755.
Facciamo quest'altra prova; da terminale dai questo comando:
cancella il contenuto ed incolla questo:
Codice: Seleziona tutto
KERNEL=="sd6", SUBSYSTEMS=="block", ", ATTRS{model}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
KERNEL=="sd6", SUBSYSTEMS=="block", ", ATTRS{model}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
KERNEL=="sd6", SUBSYSTEMS=="block", ", ENV{ID_MODEL}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
salva ed esci dall'editor di testo.
Da terminale dai questo comando:
Riavvia il pc.
Re: problema card reader interno
Inviato: giovedì 13 ottobre 2011, 16:30
da ormo
Nemmeno con questa regola mi legge la carta, sempre i soliti hardware error come sopra riportato.
Proverò a cambiare il connettore sulla scheda madre, se non ricordo male avevo altri punti dove collegare... magari che ne so gli piace di più.
Comincio a vagliare pure il campo del culo...
Comunque ti ringrazio ancora una volta.
Re: problema card reader interno
Inviato: giovedì 13 ottobre 2011, 19:04
da magozurlinux
Prego, di nulla.
Proviamo a cambiare numerazione alla regola udev per vedere se così funziona.
Da terminale dai questo comando:
Codice: Seleziona tutto
sudo mv /etc/udev/rules.d/15-cardreader.rules /etc/udev/rules.d/59-cardreader.rules
da terminale dai questo comando:
Riavvia il pc.
Re: problema card reader interno
Inviato: venerdì 14 ottobre 2011, 2:12
da ormo
Ancora n on ci siamo però.
Ho variato un po' la cosa in questo senso
ho sostituito sd6 con sde nlle righe della regola udev.
o non ci ho mai fatto caso io oppure è una novità questa che dopo il timeout di 180 secondi avevo un output in dmesg ora mi sta sembrando nuovo
dmesg dall'inserimento fino al timeout
Codice: Seleziona tutto
[ 42.269068] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ 42.269554] sd 8:0:0:3: [sde] Assuming drive cache: write through
[ 42.270675] sd 8:0:0:3: [sde] Assuming drive cache: write through
[ 222.150979] sd 8:0:0:3: timing out command, waited 180s
[ 222.150995] sd 8:0:0:3: [sde] Unhandled sense code
[ 222.150997] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 222.151000] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[ 222.151003] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[ 222.151007] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[ 222.151014] end_request: I/O error, dev sde, sector 0
[ 222.151017] quiet_error: 18 callbacks suppressed
[ 222.151019] Buffer I/O error on device sde, logical block 0
[ 241.175870] INFO: task blkid:1823 blocked for more than 120 seconds.
[ 241.175873] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 241.175876] blkid D 0000000000000002 0 1823 1 0x00000000
[ 241.175880] ffff8801d8eb5b48 0000000000000086 ffff8801d8eb5fd8 ffff8801d8eb4000
[ 241.175884] 0000000000013d00 ffff8801f67f3178 ffff8801d8eb5fd8 0000000000013d00
[ 241.175888] ffff88020ed2db80 ffff8801f67f2dc0 0000000000800040 ffff88020ba816e0
[ 241.175891] Call Trace:
[ 241.175899] [<ffffffff815c2397>] __mutex_lock_slowpath+0xf7/0x180
[ 241.175903] [<ffffffff815c1deb>] mutex_lock+0x2b/0x50
[ 241.175916] [<ffffffff81199720>] __blkdev_get+0x50/0x3e0
[ 241.175920] [<ffffffff81199b11>] blkdev_get+0x61/0x2c0
[ 241.175924] [<ffffffff815c365e>] ? _raw_spin_lock+0xe/0x20
[ 241.175928] [<ffffffff81199d70>] ? blkdev_open+0x0/0x80
[ 241.175931] [<ffffffff81199dd5>] blkdev_open+0x65/0x80
[ 241.175936] [<ffffffff81162d2e>] __dentry_open+0xce/0x2f0
[ 241.175940] [<ffffffff8116ef73>] ? generic_permission+0x23/0xc0
[ 241.175944] [<ffffffff81164221>] nameidata_to_filp+0x71/0x80
[ 241.175949] [<ffffffff81173428>] finish_open+0xc8/0x1b0
[ 241.175952] [<ffffffff81172617>] ? do_path_lookup+0x87/0x160
[ 241.175956] [<ffffffff81173be8>] do_filp_open+0x2c8/0x7c0
[ 241.175962] [<ffffffff812e6e47>] ? __strncpy_from_user+0x27/0x60
[ 241.175967] [<ffffffff81180f17>] ? alloc_fd+0xf7/0x150
[ 241.175970] [<ffffffff8116429a>] do_sys_open+0x6a/0x150
[ 241.175974] [<ffffffff811643a0>] sys_open+0x20/0x30
[ 241.175978] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Ancora una cosa che prima non avevo notato per via della non repentinità a fare un dmesg al boot, quindi una volta riavviata la macchina ho notato questo in dmesg:
Codice: Seleziona tutto
[ 3.553781] scsi 8:0:0:0: Direct-Access USB2.0 CardReader CF 0100 PQ: 0 ANSI: 0
[ 3.554268] scsi 8:0:0:1: Direct-Access USB2.0 CardReader SM XD 0100 PQ: 0 ANSI: 0
[ 3.554757] scsi 8:0:0:2: Direct-Access USB2.0 CardReader MS 0100 PQ: 0 ANSI: 0
[ 3.555256] scsi 8:0:0:3: Direct-Access USB2.0 CardReader SD 0100 PQ: 0 ANSI: 0
[ 3.555528] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 3.555597] sd 8:0:0:1: Attached scsi generic sg3 type 0
[ 3.555660] sd 8:0:0:2: Attached scsi generic sg4 type 0
[ 3.555723] sd 8:0:0:3: Attached scsi generic sg5 type 0
[ 3.563123] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 3.564015] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 3.564869] sd 8:0:0:2: [sdd] Attached SCSI removable disk
[ 3.565744] sd 8:0:0:3: [sde] Attached SCSI removable disk
Forse può tornare utile?
Edit:
ho virtualizzato con oracle virtualbox una macchina win7, ho aggiunto alle periferiche usb (perchè li virtualbox lo piazza) questo famoso "ENE Flash UB623X [0100]" e mi legge la cartina tranquillamente.
forse è pure cambiato qualcosa in dmesg ma è passato troppo tempo, dovrei riavviare e fare tutto in fretta.
intanto mi salvo le foto della carta.........
Re: problema card reader interno
Inviato: venerdì 14 ottobre 2011, 12:21
da magozurlinux
Nel modo di correggere la regola udev per errore ho digitato 6 anzichè e; quindi ora come rileva il card reader?
Da terminale postami questo comando:
Re: problema card reader interno
Inviato: venerdì 14 ottobre 2011, 18:39
da ormo
dmesg greppato:
Codice: Seleziona tutto
ormo@dabox:~$ dmesg |grep sde
[ 3.544799] sd 8:0:0:3: [sde] Attached SCSI removable disk
ormo@dabox:~$
in dmesg tra le prime righe:
Codice: Seleziona tutto
[ 2.812628] usb 2-1.7: new full speed USB device using ehci_hcd and address 4
[ 3.532828] scsi 8:0:0:0: Direct-Access USB2.0 CardReader CF 0100 PQ: 0 ANSI: 0
[ 3.533305] scsi 8:0:0:1: Direct-Access USB2.0 CardReader SM XD 0100 PQ: 0 ANSI: 0
[ 3.533812] scsi 8:0:0:2: Direct-Access USB2.0 CardReader MS 0100 PQ: 0 ANSI: 0
[ 3.534437] scsi 8:0:0:3: Direct-Access USB2.0 CardReader SD 0100 PQ: 0 ANSI: 0
[ 3.534718] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 3.534790] sd 8:0:0:1: Attached scsi generic sg3 type 0
[ 3.534854] sd 8:0:0:2: Attached scsi generic sg4 type 0
[ 3.534916] sd 8:0:0:3: Attached scsi generic sg5 type 0
[ 3.542169] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 3.543058] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 3.543932] sd 8:0:0:2: [sdd] Attached SCSI removable disk
[ 3.544799] sd 8:0:0:3: [sde] Attached SCSI removable disk
[ 11.346624] <30>udev[361]: starting version 167
[ 11.356758] lp: driver loaded but no devices found
Le ultime due righe riguardano il nostro amico card reader secondo te/voi?
comunque allo stato attuale con la regola così composta:
Codice: Seleziona tutto
KERNEL=="sde", SUBSYSTEMS=="block", ", ATTRS{model}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
KERNEL=="sde", SUBSYSTEMS=="block", ", ATTRS{model}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
KERNEL=="sde", SUBSYSTEMS=="block", ", ENV{ID_MODEL}=="CardReader SD ", NAME{all_partitions}="card-sd", group=plugdev
il contenuto della carta non viene letto ed in dmesg ho:
Codice: Seleziona tutto
[ 445.063062] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ 445.063603] sd 8:0:0:3: [sde] Assuming drive cache: write through
[ 445.065085] sd 8:0:0:3: [sde] Assuming drive cache: write through
al timeout:
Codice: Seleziona tutto
[ 600.896988] INFO: task udisks-daemon:1559 blocked for more than 120 seconds.
[ 600.896991] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 600.896995] udisks-daemon D 0000000000000003 0 1559 1558 0x00000000
[ 600.897000] ffff8801f4feb8f8 0000000000000086 ffff8801f4febfd8 ffff8801f4fea000
[ 600.897004] 0000000000013d00 ffff88020a3903b8 ffff8801f4febfd8 0000000000013d00
[ 600.897009] ffff88020ed444a0 ffff88020a390000 ffff8800def918e8 ffff8800ded93d00
[ 600.897013] Call Trace:
[ 600.897023] [<ffffffff8110c0f0>] ? sync_page+0x0/0x50
[ 600.897029] [<ffffffff815c1320>] io_schedule+0x70/0xc0
[ 600.897033] [<ffffffff8110c130>] sync_page+0x40/0x50
[ 600.897038] [<ffffffff815c1b4a>] __wait_on_bit_lock+0x5a/0xc0
[ 600.897042] [<ffffffff8110c0c7>] __lock_page+0x67/0x70
[ 600.897048] [<ffffffff81087ff0>] ? wake_bit_function+0x0/0x50
[ 600.897053] [<ffffffff81198b28>] ? blkdev_readpage+0x18/0x20
[ 600.897057] [<ffffffff8110cd87>] do_read_cache_page+0x157/0x180
[ 600.897061] [<ffffffff81198b10>] ? blkdev_readpage+0x0/0x20
[ 600.897065] [<ffffffff8110cdf9>] read_cache_page_async+0x19/0x20
[ 600.897069] [<ffffffff8110ce0e>] read_cache_page+0xe/0x20
[ 600.897074] [<ffffffff811cbf00>] read_dev_sector+0x30/0xa0
[ 600.897079] [<ffffffff811cd01a>] adfspart_check_ICS+0x7a/0x2a0
[ 600.897084] [<ffffffff812e5604>] ? snprintf+0x34/0x40
[ 600.897088] [<ffffffff811ccfa0>] ? adfspart_check_ICS+0x0/0x2a0
[ 600.897093] [<ffffffff811cc61c>] check_partition+0xfc/0x210
[ 600.897097] [<ffffffff811ccd6a>] rescan_partitions+0xda/0x310
[ 600.897102] [<ffffffff813f0d54>] ? sd_open+0x174/0x1f0
[ 600.897106] [<ffffffff8119998a>] __blkdev_get+0x2ba/0x3e0
[ 600.897110] [<ffffffff81199b11>] blkdev_get+0x61/0x2c0
[ 600.897113] [<ffffffff815c365e>] ? _raw_spin_lock+0xe/0x20
[ 600.897117] [<ffffffff81199d70>] ? blkdev_open+0x0/0x80
[ 600.897120] [<ffffffff81199dd5>] blkdev_open+0x65/0x80
[ 600.897125] [<ffffffff81162d2e>] __dentry_open+0xce/0x2f0
[ 600.897129] [<ffffffff8116ef73>] ? generic_permission+0x23/0xc0
[ 600.897133] [<ffffffff81164221>] nameidata_to_filp+0x71/0x80
[ 600.897138] [<ffffffff81173428>] finish_open+0xc8/0x1b0
[ 600.897141] [<ffffffff81172617>] ? do_path_lookup+0x87/0x160
[ 600.897145] [<ffffffff81173be8>] do_filp_open+0x2c8/0x7c0
[ 600.897150] [<ffffffff813b6ef7>] ? put_device+0x17/0x20
[ 600.897154] [<ffffffff813dd6a4>] ? scsi_device_put+0x44/0x60
[ 600.897159] [<ffffffff812e6e47>] ? __strncpy_from_user+0x27/0x60
[ 600.897164] [<ffffffff81180f17>] ? alloc_fd+0xf7/0x150
[ 600.897168] [<ffffffff8116429a>] do_sys_open+0x6a/0x150
[ 600.897171] [<ffffffff81162c30>] ? filp_close+0x60/0x90
[ 600.897174] [<ffffffff811643a0>] sys_open+0x20/0x30
[ 600.897179] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
[ 600.897197] INFO: task blkid:2059 blocked for more than 120 seconds.
[ 600.897199] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 600.897201] blkid D 0000000000000003 0 2059 511 0x00000000
[ 600.897205] ffff8801d3a43b48 0000000000000086 ffff8801d3a43fd8 ffff8801d3a42000
[ 600.897210] 0000000000013d00 ffff8801d3a583b8 ffff8801d3a43fd8 0000000000013d00
[ 600.897214] ffff88020ed444a0 ffff8801d3a58000 0000000000800040 ffff88020b995d60
[ 600.897218] Call Trace:
[ 600.897223] [<ffffffff815c2397>] __mutex_lock_slowpath+0xf7/0x180
[ 600.897227] [<ffffffff815c1deb>] mutex_lock+0x2b/0x50
[ 600.897231] [<ffffffff81199720>] __blkdev_get+0x50/0x3e0
[ 600.897235] [<ffffffff81199b11>] blkdev_get+0x61/0x2c0
[ 600.897238] [<ffffffff815c365e>] ? _raw_spin_lock+0xe/0x20
[ 600.897242] [<ffffffff81199d70>] ? blkdev_open+0x0/0x80
[ 600.897245] [<ffffffff81199dd5>] blkdev_open+0x65/0x80
[ 600.897249] [<ffffffff81162d2e>] __dentry_open+0xce/0x2f0
[ 600.897252] [<ffffffff8116ef73>] ? generic_permission+0x23/0xc0
[ 600.897256] [<ffffffff81164221>] nameidata_to_filp+0x71/0x80
[ 600.897259] [<ffffffff81173428>] finish_open+0xc8/0x1b0
[ 600.897263] [<ffffffff81172617>] ? do_path_lookup+0x87/0x160
[ 600.897267] [<ffffffff81173be8>] do_filp_open+0x2c8/0x7c0
[ 600.897271] [<ffffffff812e6e47>] ? __strncpy_from_user+0x27/0x60
[ 600.897275] [<ffffffff81180f17>] ? alloc_fd+0xf7/0x150
[ 600.897279] [<ffffffff8116429a>] do_sys_open+0x6a/0x150
[ 600.897283] [<ffffffff811643a0>] sys_open+0x20/0x30
[ 600.897286] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Questo è quanto purtroppo.
Re: problema card reader interno
Inviato: sabato 15 ottobre 2011, 19:25
da magozurlinux
Prova a cambiare questo parametro dalla regola udev a tutte e tre le righe:
salva ed esci dall'editor di testo.
Da terminale dai questo comando:
Riavvia il pc.
Re: problema card reader interno
Inviato: domenica 16 ottobre 2011, 21:10
da ormo
fuffa!
regola cambiata e riavviato.
dmesg:
Codice: Seleziona tutto
[ 135.177735] sd 8:0:0:3: [sde] 7872512 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ 135.178341] sd 8:0:0:3: [sde] Assuming drive cache: write through
[ 135.179467] sd 8:0:0:3: [sde] Assuming drive cache: write through
[ 315.051131] sd 8:0:0:3: timing out command, waited 180s
[ 315.051147] sd 8:0:0:3: [sde] Unhandled sense code
[ 315.051149] sd 8:0:0:3: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 315.051152] sd 8:0:0:3: [sde] Sense Key : Hardware Error [current]
[ 315.051155] sd 8:0:0:3: [sde] Add. Sense: Unrecovered read error
[ 315.051159] sd 8:0:0:3: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[ 315.051166] end_request: I/O error, dev sde, sector 0
[ 315.051169] Buffer I/O error on device sde, logical block 0
lsusb:
Codice: Seleziona tutto
ormo@dabox:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0b05:179c ASUSTek Computer, Inc.
Bus 002 Device 003: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0cf2:6230 ENE Technology, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub