Alan, We have figured out the problem. The version of insmod we are using is from the android toolbox binary. In their version of insmod, they separate each of the args, in the args string passed to init_module(), with a space and '\0'. I recompiled their code so that just a space is used to delimit the args and I was then able to successfully specify stall (as well as more than just one argument) on the command line. I'm not sure why they implemented insmod this way. Rob -----Original Message----- From: Alan Stern [mailto:stern@xxxxxxxxxxxxxxxxxxx] Sent: Wednesday, September 08, 2010 2:30 PM To: Murphy, Robert Cc: Gadiyar, Anand; Greg KH; linux-usb@xxxxxxxxxxxxxxx Subject: RE: Windows fails to install FBSG based drive On Wed, 8 Sep 2010, Murphy, Robert wrote: > I removed the hard coded value and then tried: > stall=0 > stall=1 > stall=N > stall=n > > Each time, I got the following: > # cat /sys/module/g_file_storage/parameters/stall > Y Then there must be a bug in your copy of insmod or in the kernel's dynamic module loader. That's the first time I've heard of something like this. What version of the module-init-tools package do you have? Does the same thing happen with modprobe? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
