Maybe you have a device that rejects to work, because it claims to need
500mA or so. But in fact it works, just it claims to need much more
energy than it really needs.
Here is a small hack to work-around this problem and force the device to
start without any interaction:
/lib/udev/rules.d/40-ralink.rules:
# Ignore power requirement for Ralink 3070. It can run with 170mA.
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="07b8",
ATTRS{idProduct}=="3071", RUN+="/bin/sh -c 'echo 1 >/sys%p/bConfigurationValue'"
If you have more similar USB IDs, then it may make sense to make a list
and create an Angstrom package for that.
(Note that the current Ralink 3070 driver requires 4x 256kB of
contiguous kernel memory to start. It is really awkward, and I have
often to call echo 3 >/proc/sys/vm/drop_caches and/or
dd if=/dev/zero of=/dev/null bs=62M count=1 to wipe or swap out some
data.)
--
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
_______________________________________________
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
