Re: [suse-linux-s] Ver el contenido de MuVo USB en SuSE 9.1
Yo tenía un problema similar con un pen drive de 256 MB hasta que conseguí un parche para el módulo usb_storage:
===== drivers/usb/storage/scsiglue.c 1.74 vs edited =====
--- 1.74/drivers/usb/storage/scsiglue.c Sat Apr 24 22:25:50 2004
+++ edited/drivers/usb/storage/scsiglue.c Tue May 18 10:02:17 2004
@@ -48,12 +48,15 @@
#include "usb.h"
#include "debug.h"
#include "transport.h"
+#include "protocol.h"
#include
Angel Martín
8/12/04 2:15:09 >>> Hola amigos,
en SuSE 9.1 cuando pincho un pendrive USB de 128 megas puedo ver su contenido en /media/usb-storage-xxxxxx. Pero cuando pincho un Creative MuVo de 128 megas que, en SuSE 9.0 me lo reconoce como un disco fat, me sale el siguiente log en /var/log/messages Dec 8 02:04:40 linux kernel: usb 3-1: new full speed USB device using address 9 Dec 8 02:04:40 linux kernel: usb 3-1: Product: NOMAD MuVo Dec 8 02:04:40 linux kernel: usb 3-1: Manufacturer: Creative Tech Dec 8 02:04:40 linux kernel: usb 3-1: SerialNumber: 000000000000 Dec 8 02:04:40 linux /etc/hotplug/usb.agent[7149]: need a device for this command Dec 8 02:04:40 linux kernel: scsi3 : SCSI emulation for USB Mass Storage devices Dec 8 02:04:40 linux kernel: Vendor: CREATIVE Model: NOMAD_MUVO Rev: 0001 Dec 8 02:04:40 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Dec 8 02:04:40 linux kernel: SCSI device sda: 256001 512-byte hdwr sectors (131 MB) Dec 8 02:04:40 linux kernel: sda: assuming Write Enabled Dec 8 02:04:40 linux kernel: sda: assuming drive cache: write through Dec 8 02:04:40 linux /etc/hotplug/block.agent[7199]: try 1 while waiting for /block/sda's bus_id 3:0:0:0 Dec 8 02:04:40 linux kernel: sda:end_request: I/O error, dev sda, sector 256000 Dec 8 02:04:40 linux kernel: Buffer I/O error on device sda, logical block 256000 Dec 8 02:04:41 linux /etc/hotplug/block.agent[7199]: try 2 while waiting for /block/sda's bus_id 3:0:0:0 Dec 8 02:04:42 linux /etc/hotplug/block.agent[7199]: try 3 while waiting for /block/sda's bus_id 3:0:0:0 Dec 8 02:04:43 linux /etc/hotplug/block.agent[7199]: try 4 while waiting for /block/sda's bus_id 3:0:0:0 Dec 8 02:04:44 linux /etc/hotplug/block.agent[7199]: try 5 while waiting for /block/sda's bus_id 3:0:0:0 Dec 8 02:04:45 linux /etc/hotplug/block.agent[7199]: new block device /block/sda y no monta el /media/usb-storage-xxxxxx ¿teneis idea de la solución? He estado mirando los correos de meses anteriores en la lista y no he conseguido dar con ello. Gracias y saludos. -- Para dar de baja la suscripción, mande un mensaje a: suse-linux-s-unsubscribe@suse.com Para obtener el resto de direcciones-comando, mande un mensaje a: suse-linux-s-help@suse.com
On Thu, 09 Dec 2004 09:12:11 +0100
"Juan Aguilar Pérez"
Yo tenía un problema similar con un pen drive de 256 MB hasta que conseguí un parche para el módulo usb_storage:
===== drivers/usb/storage/scsiglue.c 1.74 vs edited ===== --- 1.74/drivers/usb/storage/scsiglue.c Sat Apr 24 22:25:50 2004 +++ edited/drivers/usb/storage/scsiglue.c Tue May 18 10:02:17 2004 @@ -48,12 +48,15 @@ #include "usb.h" #include "debug.h" #include "transport.h" +#include "protocol.h"
#include
#include #include #include +#define SKIP_MODE_SENSE_PAGE_3F 1 +
/*********************************************************************** * Host functions @@ -68,10 +71,13 @@ { /* * Set default bflags. These can be overridden for individual - * models and vendors via the scsi devinfo mechanism. + * models and vendors via the scsi devinfo mechanism. The only + * flag we need is to force 36-byte INQUIRYs; we don't use any + * of the extra data and many devices choke if asked for more or + * less than 36 bytes. */ - sdev->sdev_bflags = (BLIST_MS_SKIP_PAGE_08 | BLIST_MS_SKIP_PAGE_3F | - BLIST_USE_10_BYTE_MS); + sdev->sdev_bflags = BLIST_INQUIRY_36; + return 0; }
@@ -95,11 +101,46 @@ * reduce the maximum transfer size to 64 KB = 128 sectors. */
#define USB_VENDOR_ID_GENESYS 0x05e3 // Needs a standard location + if (us->pusb_dev->descriptor.idVendor == USB_VENDOR_ID_GENESYS && - us->pusb_dev->speed == USB_SPEED_HIGH) + us->pusb_dev->speed == USB_SPEED_HIGH && + sdev->request_queue->max_sectors > 128) blk_queue_max_sectors(sdev->request_queue, 128);
- /* this is to satisify the compiler, tho I don't think the + /* We can't put these settings in slave_alloc() because that gets + * called before the device type is known. Consequently these + * settings can't be overridden via the scsi devinfo mechanism. */ + if (sdev->type == TYPE_DISK) { + + /* Disk-type devices use MODE SENSE(6) if the protocol + * (SubClass) is Transparent SCSI, otherwise they use + * MODE SENSE(10). */ + if (us->subclass != US_SC_SCSI) + sdev->use_10_for_ms = 1; + + /* Many disks only accept MODE SENSE transfer lengths of + * 192 bytes (that's what Windows uses). */ + sdev->use_192_bytes_for_3f = 1; + + /* A number of devices have problems with MODE SENSE for + * page x08, so we will skip it. */ + sdev->skip_ms_page_8 = 1; + + /* Some devices may not like MODE SENSE with page=0x3f. + * Now that we're using 192-byte transfers this may no + * longer be a problem. So this will be a compile-time + * option. */ + sdev->skip_ms_page_3f = SKIP_MODE_SENSE_PAGE_3F; + + } else { + + /* Non-disk-type devices don't need to blacklist any pages + * or to force 192-byte transfer lengths for MODE SENSE. + * But they do need to use MODE SENSE(10). */ + sdev->use_10_for_ms = 1; + } + + /* this is to satisfy the compiler, tho I don't think the * return code is ever checked anywhere. */ return 0; }
Así que parcheé el código fuente del módulo recoompilé los módulos, los instalé y dejó de dar problemas.
Perdona mi torpeza. En /lib/modules/2.6.5-7.111.5-default/kernel/drivers/usb/storage sólo tengo el siguiente módulo: usb-storage.ko En el código que me envías aparece 1.74/drivers/usb/storage/scsiglue.c ¿Esto dónde está?¿Tengo que bajarme los fuentes del kernel? Cuando dices parchear ¿te refieres a sustituir el código de scsiglue.c por el que me envías? Una vez sustituido, ¿se recompila con make o hay que hacer algo más? Y, por último, imagino que instalar los módulos es colocar el/los módulos compilados en .../drivers/usb/storage, no? Saludos.
participants (2)
-
Angel Martín
-
Juan Aguilar Pérez