On Tue, 14 Oct 2003, Phil Dibowitz wrote: > It seems that this patch causes a problem. The sd_mod module still sees > the device and gives: > > Oct 14 21:40:50 rider kernel: hub 1-0:0: debounce: port 2: delay 100ms > stable 4 status 0x101 > Oct 14 21:40:50 rider kernel: hub 1-0:0: new USB device on port 2, > assigned address 3 > Oct 14 21:40:50 rider kernel: scsi0 : SCSI emulation for USB Mass > Storage devices
Could you try running this with verbose usb-storage debugging turned on, and post the debugging log? It may have some clues. It's very odd that this one change should have such a big effect. All it does is tell the driver to use values supplied by the device rather than values stored in the unusual_dev table -- but the values are the same! That's what the "unneeded SubClass and Protocol entries" message means. > But it never alocates a device for it. When I switch back to the old > version of the driver I get: > > Oct 14 21:46:17 rider kernel: Initializing USB Mass Storage driver... > Oct 14 21:46:17 rider kernel: usb-storage: This device (07cf,1001,5010 S > 05 P 01) has unneeded SubClass and Protocol entries in unusual_devs.h > Oct 14 21:46:17 rider kernel: Please send a copy of this message to > <[EMAIL PROTECTED]> > Oct 14 21:46:17 rider kernel: scsi1 : SCSI emulation for USB Mass > Storage devices > Oct 14 21:46:17 rider kernel: Vendor: Casio Model: QV > DigitalCamera Rev: 5010 > Oct 14 21:46:17 rider kernel: Type: Direct-Access > ~ ANSI SCSI revision: 02 > Oct 14 21:46:17 rider kernel: SCSI device sda: 20208 512-byte hdwr > sectors (10 MB) > Oct 14 21:46:17 rider kernel: sda: Write Protect is off > Oct 14 21:46:17 rider scsi.agent[15463]: how to add device type= at > /devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2:0/host1/1:0:0:0 ?? > Oct 14 21:46:17 rider kernel: sda: cache data unavailable > Oct 14 21:46:17 rider kernel: sda: sda1 > Oct 14 21:46:17 rider kernel: Attached scsi removable disk sda at scsi1, > channel 0, id 0, lun 0 > Oct 14 21:46:17 rider kernel: drivers/usb/core/usb.c: registered new > driver usb-storage > Oct 14 21:46:17 rider kernel: USB Mass Storage support registered. > > > I can make the new module work if I use the OLD module, mount the > camera, umount the camera, unload the old module, move the new module > into place, run depmod, then load the new module.... And that sounds truly weird. Could there be any other differences between the two modules that would account for it? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
