Author Message

<  Device Information  ~  FRITZ!WLAN USB Stick N v2

PostPosted: Sat Sep 14, 2013 1:04 pm Reply with quote
Posts: 4 Joined: Sat Sep 14, 2013 12:28 pm
This device is stuck in CD-Rom mode by default on my Kubuntu 13.04 system.

Code:
Bus 001 Device 005: ID 057c:62ff AVM GmbH AVM Fritz!WLAN USB (in CD-ROM-mode)


Windows 7 device manager lists the same usb device as:

Code:
USB\VID_057C&PID_8501&REV_0413
USB\VID_057C&PID_8501
fwlanusb5
FRITZ!WLAN USB Stick N v2


using the message from

Code:
# AVM Fritz!Wlan USB Stick N

TargetVendor=  0x057c
TargetProduct= 0x8401

MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"


doesn't trigger the switch on my newer revision of the product.

since http://www.pcausa.com/Utilities/UsbSnoop/default.htm , from http://blogger.ziesemer.com/2008/10/all ... buntu.html is said to not work on windows 7 i used
http://blogs.msdn.com/usbcoreblog/archi ... stack.aspx

Unfortunately i haven't been able yet to find the magic MessageContent that would trigger the switch.


Offline
PostPosted: Thu Oct 03, 2013 5:30 pm Reply with quote
Posts: 4 Joined: Sat Sep 14, 2013 12:28 pm
i obviously made the classic mistake and forgot the "-I" when testing on the command line :oops:
I made a copy of the original file and adjusted it to the new v2 revision of the hardware.

filecontent of: 057c:62ff

Code:
# AVM Fritz!Wlan USB Stick N v2

TargetVendor=  0x057c
TargetProduct= 0x8501

MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"

NoDriverLoading=1
Attachments:
057c_62ff.txt [176 Bytes]
Downloaded 627 times

Offline
PostPosted: Sat Oct 12, 2013 8:51 am Reply with quote
Site Admin Posts: 6529 Joined: Sat Nov 03, 2007 12:30 am
Thanks a lot for the report!

I'm actually thinking about reversing the logic of the -I parameter in future releases ...


Offline
PostPosted: Sun Mar 16, 2014 8:52 pm Reply with quote
Posts: 4 Joined: Sat Sep 14, 2013 12:28 pm
The new AC 430 uses the same id for the cdrom mode but comes out as pid 8502 in the end, would that cause any issues with usb_modeswitch?


Offline
PostPosted: Thu May 08, 2014 7:18 pm Reply with quote
Posts: 4 Joined: Sat Sep 14, 2013 12:28 pm
i think the file needs to be updated for the new wifi dongle in the following way
Attachments:
057c_62ff_v2.txt [184 Bytes]
Downloaded 558 times

Offline
PostPosted: Fri May 09, 2014 5:27 am Reply with quote
Posts: 1261 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
Thanks for the report, the additional id will be included in the next update of the usb_modeswitch data package.

Have you ever tried the standard cdrom eject message on these two devices?
The only difference between your msg and the std eject msg is only one byte, your "ff" is "02" in std eject.


Offline
PostPosted: Thu Jul 07, 2016 2:47 pm Reply with quote
Posts: 1 Joined: Thu Jul 07, 2016 2:09 pm
In my current release (20160112) the file included is as follows:
Code:
# AVM Fritz!Wlan USB Stick N v2                                                 
TargetVendor=0x057c
TargetProductList="8501,8502"
StandardEject=1
NoDriverLoading=1


This doesn't work as apparently the device doesn't listen for a standard eject message.
Adding in the above MessageContent line however seems to fix the issue.

Could you please include the following line in your next release for file 057c:62ff?

Code:
MessageContent="5553424312345678000000000000061b000000ff0000000000000000000000"


Thanks for your time.

Kind regards,
Bart Kuivenhoven.

EDIT:
I almost forgot, you might also want to know what system I'm running.

A fresh Fedora 24 install on a 64-bits Intel machine.
Using version 2.3.0 of usb_modeswitch.

I scanned the source quickly but couldn't find a difference in message contents between the versions in terms of a standard eject though.


Offline
PostPosted: Fri Jul 08, 2016 2:52 am Reply with quote
Posts: 1261 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
bemk wrote:
I scanned the source quickly but couldn't find a difference in message contents between the versions in terms of a standard eject though.


The difference is the parameter given together with the 1b command, a parameter which can be 1 or 2 but not ff.
Fritz or his mfgr has abused a standardized command by giving it an invalid parameter instead of using any of the many cmds listed as mfgr specific.
Thanks for the report, we will revert back the config to contain ff as parameter in the next issue of the usb_modeswitch data package.


Offline

Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 1
8 posts
Users browsing this forum: Google [Bot] and 0 guests
Search for:
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum