Usb Storage

[dlj0]

How about:

modprobde ohci-hcd?

If that works, then simply add ohci-hcd to /etc/modules so that the module will load automatically when the system boots up.

Or ask the gurus?  

oh yeah i forgot the ohci-hcd stuff ..
unhopefully, i now have a curious message as i plug the key :

rejected 1 configuration due to insufficient available bus power
...........

I got that message at one time, then got a powered usb hub -- very convenient for multiple devices.  But with debian I have been able to just plug in my usb keychain device, and it works.  The proper modules just load, once I start ohci-hcd.

[dlj0]

I got the same error when plugging in my Sony Ericsson w800i (which can function as a USB mass storage device).

hmm
i've just try to plug in my PSP (which has its own power!) and .. it works!
so is it a kernel problem or some config files to tweak ?

I believe the limited power available to the usb port would be a hardware limitation, not something that could be re-configured.

[dlj0]

sda: unknown partition table
sd 1:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete

Then I used mount:

debian:/# mount /dev/sda1 /media/cf -t vfat

mount: special device /dev/sda1 does not exist


So I have used fdisk and will now format the stick as ext2 and see what happens

Huh.  Mine works fine with whatever fs (vfat, probably) that came on the thing.  I guess you have managed to mount it successfully on another machine, but that would be worth testing.  And, keeping the fs vfat makes the device usable on more machines.

[ZDevil]

I believe the limited power available to the usb port would be a hardware limitation, not something that could be re-configured.

But my Z can connect and use the SE w800i phone in pdaX without trouble, while there is a error showing not enough power in Debian. So I rather think it is not really hardware limitation in some cases.

[tux]

sda: unknown partition table
sd 1:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete

Then I used mount:

debian:/# mount /dev/sda1 /media/cf -t vfat

mount: special device /dev/sda1 does not exist


So I have used fdisk and will now format the stick as ext2 and see what happens

Huh.  Mine works fine with whatever fs (vfat, probably) that came on the thing.  I guess you have managed to mount it successfully on another machine, but that would be worth testing.  And, keeping the fs vfat makes the device usable on more machines.

 In fact, any device that actually works at all will work with whatever format is on it. I was just checking if there was a problem with the default partitions on the device. There are some that seem to have a system all of their own.  

The interesting thing to me, was that the CF card reader worked. But I could only mount the CF card after I ran fdisk on /dev/sda. I didn't actually have to alter anything, just use it and quit. Then the CF card could be mounted.  

Some devices, like the swapped out 6GB drive, just hung when I ran fdisk. (Works fine in the CF slot.)

Strange happenings.

 

[Marcin iwi Iwinski]

I know that topic is quite old - but i'm having the "bus power" problem as well. I'm using sharp version of yongguns's 2.6.24. Did anyone find any solution ?

[speculatrix]

when I first started using linux on the desktop full time (oh, about 7 years ago) I was trying to use a particular memory card reader with a sony memstick, and it just wouldn't work. then I discovered I had to do some patches to the kernel - scary stuff - and it worked. I investigated and found that apparently many manufacturers did not create hardware that properly fulfils the USB specifications, but that Windows was very lax about enforcing any standards, and thus the manufacturers got away with it. This means that linux had to add kludges to allow the hardware to work.
I would hope that in theory things are better now, but quite possibly not.

So, it's quite possible that the hardware will work, but reports the wrong information to the Z, which assumes that the usb device isn't functioning, reports an incorrect error, and fails to fire it up?

[Marcin iwi Iwinski]

I've found something eventually

https://www.oesf.org/forum/index.php?showto...&hl=pegasus

[ZDevil]

I've found something eventually
https://www.oesf.org/forum/index.php?showto...&hl=pegasus

Does this trick work?

[radiochickenwax]

Does this trick work?

Yes, this trick works... but it's kind of a pain to do this every time.

*EDIT*

I was thinking about trying to change the kernel configs for this reason.  Does anyone know which line it is to change this behavior?  Or is it not even the kernel?

*EDIT2*  

Udev might be a good workaround, according to post #5 in the following:

http://ubuntuforums.org/showthread.php?p=3533694#post3533694

*EDIT3*

FWIW, there's a good deal of info at

http://www.mjmwired.net/kernel/Documentati...-management.txt

[pelrun]

The udev trick is the way to go, see my old post: https://www.oesf.org/forum/index.php?showto...st&p=177297