On Thu, Jun 3, 2010 at 3:14 AM, wrote:
> OK, I suppose the ID is right, but odd, when I plug it in I get
> "invalid interface number" messages, no matter what port I plug it into.
>
> new full speed USB device using ehci_hcd and address 5
> config 1 has an invalid interface number: 1 but max is 0
OK, I suppose the ID is right, but odd, when I plug it in I get
"invalid interface number" messages, no matter what port I plug it into.
new full speed USB device using ehci_hcd and address 5
config 1 has an invalid interface number: 1 but max is 0
config 1 has no interface number 0
New USB devic
BTW, if you are interested in udev and module loading, see
http://wiki.archlinux.org/index.php/ModaliasPrimer for a good
explanation.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Wed, Jun 2, 2010 at 2:55 AM, wrote:
> Here's one of the files from the Windows driver set that my buddy gave
> me with the computer back in town that is actually used when the antenna
> works (perfectly) under windows.
The NetGtks.inf confirms that Windows uses its prism2 driver for your
card
On Tue, Jun 1, 2010 at 8:44 AM, wrote:
> I have determined the device must be in fact a an
> 03eb Atmel Corp.
> 7605 at76c503a 802.11b Adapter
> maybe that is why all the prism stuff doesn't work.
Inside the tarball he sent you, in setup/usb_src/vnetusba.h we can find this:
#define VNet
TV> I suggest you try running these commands a number of times:
TV> sudo wlanctl-ng lnxreq_ifstate ifstate=disable
TV> sudo wlanctl-ng lnxreq_ifstate ifstate=enable
TV> Then see if you get something else than the previous CTLX error in
TV> dmesg. I have some weak memories from having to run these
On Mon, May 31, 2010 at 8:08 PM, wrote:
> Can I even find what version of the firmware already inside it using Linux?
> Maybe it isn't even prism... I don't think dmesg will tell much as one
> probably has to load the extra firmware to see the firmware version.
If the driver succeeds to load, it
TV> Maybe you can try connecting through a USB hub?
Same with and without.
TV> Karl suggests that you try upgrading the eeprom firmware on your card,
TV> using Windows and the reflashing tools available there. These pages
TV> mentions a WinUpdate program, which also can report which firmware
TV> v
> All I know is I can do exact tests you tell me and send you the results.
>
Neither Karl (the kernel developer who has worked the most on this
CTLX issues) or I can reproduce the problem. It can be your card is a
bit different, or your USB ports, etc. Maybe you can try connecting
through a USB hu
I tried plugging in ten times as mentioned in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454684#30
and ended up hosing USB an needing to reboot, upon which I had to
modprobe prism2_usb manually. Anyways
TV>
http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=blob;f=drivers/sta
As is also seen in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454684#25 this CTLX
failure is an old known problem. It has been tried worked around like
here:
http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=blob;f=drivers/staging/wlan-ng/hfa384x_usb.c;h=a41db5dc8c7c592a0f8c6
TV> This must therefore be a bug in the prism2_usb kernel module. Which
TV> kernel are you using?
linux-image-2.6.32-5-686:
Installed: 2.6.32-13
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
BTW, as a temporary workaround, maybe you can try the userland
firmware loading mechanism provided by linux-wlan-ng-firmware and see
if that works better? In this case, remove the firmware file from the
/lib/firmware directory (or remove the prism2-usb-firmware-installer
package).
--
To UNSUBSC
> prism2_usb: prism2_ru.fw will be processed, size 90662
It seems like the firmware file is available and the size is right.
prism2-usb-firmware-installer also checksums the firmware file, so it
is unlikely to be corrupted. This must therefore be a bug in the
prism2_usb kernel module. Which kernel
Package: prism2-usb-firmware-installer
Version: 0.2.9+dfsg-4
All this does not work. Syslog says:
usb 3-1: new full speed USB device using uhci_hcd and address 5
usb 3-1: config 1 has an invalid interface number: 1 but max is 0
usb 3-1: config 1 has no interface number 0
usb 3-1: New USB device f
15 matches
Mail list logo
