Risposte al Forum Create
-
AutoreArticoli
-
20 Aprile, 2008 alle 18:00 in risposta a: Openmamba su Toshiba M30X-162 non legge le chede SD #23202
aragorn71
Membro14 Aprile, 2008 alle 20:49 in risposta a: Openmamba su Toshiba M30X-162 non legge le chede SD #23144aragorn71
Membro::Allora, nel Device Manager, e per la precisione in System Peripheral, ho trovato una voce “MMC/SD Host Adapter”.
In System Peripheral noto nella chiave “linux.vendor”, alla voce “value”, alla stringa:”ENE Technology Inc”, che dovrebbe essere quella relativa al lettore di schede, ma non compare alcun dispositivo (../dev/…).
In “MMC/SD Host Adapter” ho diverse voci ma nessuna che mi indichi qualcosa di comprensibile, almeno per me. Ti riporto le diverse chiavi, la maggior parte di tipo “string”:
info.capabilities –> string –> mmc_host
info.category –> string –> mmc_host
info.parent –> string –> /org/freedesktop/Hal/devices/pci_1524_550
info.product –> string –> MC/SD Host Adapter
info.udi –> string –> /org/freedesktop/Hal/devices/pci_1524_550_mmc_host
linux.hotplug_type –> int32 –> 2 (0x2)
linux.subsystem –> string –> mmc_host
linux.sysfs_path –> string –> /sys/devices/pci0000:00/0000:00:1e0/0000:02:04.2/mmc_host/mmc0
mmc_host.host –> int32 –>0 (0x0)
Se può servire.
Ti dicono qualcosa Silvan?
14 Aprile, 2008 alle 18:07 in risposta a: Openmamba su Toshiba M30X-162 non legge le chede SD #23132aragorn71
Membro14 Aprile, 2008 alle 14:13 in risposta a: Openmamba su Toshiba M30X-162 non legge le chede SD #23128aragorn71
Membro14 Aprile, 2008 alle 11:36 in risposta a: Openmamba su Toshiba M30X-162 non legge le chede SD #23124aragorn71
Membroaragorn71
Membroaragorn71
Membroaragorn71
Membroaragorn71
Membro::Scusa Silvan ma mi ero allontanato dal PC. Allora, l’esito del comando richiesto è:
02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
Subsystem: Toshiba America Info Systems Unknown device ff01
Flags: bus master, medium devsel, latency 168, IRQ 16
Memory at d0203000 (32-bit, non-prefetchable)
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
Memory window 0: 54000000-57fff000 (prefetchable)
Memory window 1: 58000000-5bfff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
16-bit legacy interface ports at 0001
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket
02:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
Subsystem: Toshiba America Info Systems Unknown device ff00
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at d0201c00 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
02:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (prog-if 01)
Subsystem: Toshiba America Info Systems Unknown device ff01
Flags: bus master, medium devsel, latency 32, IRQ 17
Memory at d0202000 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
Kernel driver in use: sdhci
Kernel modules: sdhci
02:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc:
Subsystem: Toshiba America Info Systems Unknown device ff00
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at d0202400 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
aragorn71
Membroaragorn71
Membro::innanzitutto grazie per il vostro aiuto. Allora l’esito del comando “lsusb” è:
Bus 4 Device 1: ID 0000:0000
Bus 3 Device 1: ID 0000:0000
Bus 2 Device 1: ID 0000:0000
Bus 1 Device 1: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
mentre per il comando “lspci” è:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC’97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC’97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
02:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
02:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller
02:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc:
Ci vedete qualcosa??? Consigli?
aragorn71
Membroaragorn71
Membro::Grazie per avermi risposto. Ti posto le ultime righe della shell dopo il comando dmesg:
PRIMA DI INSERIRE LA SCHEDA SD
…..Ultime decine di righe…..
fuse init (API version 7.9)
vboxdrv: Trying to deactivate the NMI watchdog permanently…
vboxdrv: Successfully done.
vboxdrv: TSC mode is ‘synchronous’, kernel timer mode is ‘normal’.
vboxdrv: Successfully loaded version 1.5.6 (interface 0x00050002).
fusd: starting, $Revision: 1.97-kor-hacked-11 $, $Date: 2003/07/11 22:29:39 $, debuglevel=2
cdev control id: 260046848
fusd: registration successful
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=4138 DPT=7741 LEN=24
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=2955 DPT=137 LEN=58
DROPPED IN=eth0 OUT= MAC= SRC=192.168.1.9 DST=192.168.1.0 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=9488 SEQ=0
DROPPED IN=eth0 OUT= MAC= SRC=192.168.1.9 DST=192.168.1.255 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=9488 SEQ=0
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=229 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=209
eth0: no IPv6 routers present
ACPI: EC: non-query interrupt received, switching to interrupt mode
DROPPED IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1c:a2:6a:b3:3c:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x60 TTL=1 ID=4837 DF PROTO=2
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=229 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=209
DOPO L’INSERIMENTO DELLA SCHEDA
…..Ultime decine di righe…..
fuse init (API version 7.9)
vboxdrv: Trying to deactivate the NMI watchdog permanently…
vboxdrv: Successfully done.
vboxdrv: TSC mode is ‘synchronous’, kernel timer mode is ‘normal’.
vboxdrv: Successfully loaded version 1.5.6 (interface 0x00050002).
fusd: starting, $Revision: 1.97-kor-hacked-11 $, $Date: 2003/07/11 22:29:39 $, debuglevel=2
cdev control id: 260046848
fusd: registration successful
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=96 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 DPT=137 LEN=76
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth1: link is not ready
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=4138 DPT=7741 LEN=24
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=2955 DPT=137 LEN=58
DROPPED IN=eth0 OUT= MAC= SRC=192.168.1.9 DST=192.168.1.0 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=9488 SEQ=0
DROPPED IN=eth0 OUT= MAC= SRC=192.168.1.9 DST=192.168.1.255 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=9488 SEQ=0
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=229 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=209
eth0: no IPv6 routers present
ACPI: EC: non-query interrupt received, switching to interrupt mode
DROPPED IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1c:a2:6a:b3:3c:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x60 TTL=1 ID=4837 DF PROTO=2
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=229 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=209
DROPPED IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1c:a2:6a:b3:3c:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x60 TTL=1 ID=4838 DF PROTO=2
DROPPED IN= OUT=eth0 SRC=192.168.1.9 DST=192.168.1.255 LEN=229 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=209
Trovi qualche messaggio strano?
Proposte? AIUTOOOO
-
AutoreArticoli