Hi,
are any users of this driver on these lists?
Could you send me lsusb -v for your devices working with this driver?
Regards
Oliver
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
This signature is a legal requirement
On Mon, Mar 05, 2007 at 01:06:49AM +0100, Michael Mauch wrote:
Alan Stern wrote:
On Sun, 4 Mar 2007, Ingo Rohloff wrote:
I have got a mobile phone and I want to charge the battery
of the phone via the USB port.
It really wouldn't have hurt to mention the brand and model of the
phone.
My phone, a Nextel i830 (motorola) draws as much as 750mA when
charging a low battery and transmitting at the same time.
I've modified the datacable to try to charge from USB, but the
per-port current limit quickly kicks in and puts an end to it.
As I understand it, the 500mA as per the usb 2.0
On Mon, 12 Mar 2007, Gordon McLellan wrote:
My phone, a Nextel i830 (motorola) draws as much as 750mA when
charging a low battery and transmitting at the same time.
I've modified the datacable to try to charge from USB, but the
per-port current limit quickly kicks in and puts an end to it.
I'm trying to figure out how to get this drive to mount properly.
First problem is that it's hybrid - it acts like a CD plus a HDD - which
means, I believe, that I need to enable CONFIG_SCSI_MULTI_LUN in my kernel
and reboot. In the mean time, I need to pay attention to dmesg and do this:
On Monday 12 March 2007 14:07, Darin McBride wrote:
I'm trying to figure out how to get this drive to mount properly.
Sorry ... found out I had to first attach it to a Windows box to disable its
security, and then it mounts just fine. Posting a question to the
appropriate forum usually solves
On Thu, 2007-03-08 at 13:54 -0800, Gordon Messmer wrote:
Yeah... From FC4's configuration, simply changing to CONFIG_HZ=1000
isn't sufficient. It would seem that a combination of configuration
items are required. I'm still working on tracking them down.
OK, I've got it. If I start with
Gordon Messmer wrote:
OK, I've got it. If I start with FC4's kernel configuration, and a
vanilla kernel, the mouse works correctly. If I then turn on kernel
preemption, and set HZ=1000, the problem comes up. Neither of those
settings, by themselves, seem to trigger the problem.
---
