Re: Fwd: Re: Support for new USB Modem 4G drive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2014-03-21 11:33, Julio Araujo wrote:

Hello Bjørn,

I made the test like you suggested and I couldn't find any difference
between the printout for lsusb before and after the command.

What else I've been tried after read the page
http://www.draisberghof.de/usb_modeswitch/ was:
1 - For the file /etc/usb_modeswitch.conf I changed the EnableLogging to
1 to create a log file in /var/log, the file was created with the follow
name: /var/log/usb_modeswitch_1-1.3

2 - In the file /lib/udev/rules.d/40-usb_modeswitch.rules I copied the
information regarding to a device from the same vendor but with another
idProduct to my idProduct, so it was like this:

Information that I use as reference
# Olivetti Olicard 145, 155
ATTR{idVendor}=="0b3c", ATTR{idProduct}=="f000", RUN+="usb_modeswitch
'%b/%k'"

This lines was what I inserted in the file
# Olivetti Olicard 500, test only
ATTR{idVendor}=="0b3c", ATTR{idProduct}=="f017", RUN+="usb_modeswitch
'%b/%k'"

But it does not work, and shows the following information in the file
/var/log/usb_modeswitch_1-1.3
----------------
USB values from sysfs:
  manufacturer    USBModem
  product    Olicard 500
  serial
----------------
bNumConfigurations is 1 - don't check for active configuration
Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz
Aargh! Config file missing for 0b3c:f017! Exit


3 - In the file /usr/share/usb_modeswitch/configPack.tar.gz I found the
configuration information regarding to a idVendor and idProduct like a
did in the file 40-usb_modeswitch.rules and I copy to a new file with
name 0b3c:f017 with the same information from the file 0d3c:f000.

Original file 0b3c:f000
julio@mynote:~/Documentos/Modem4G-Olicard500/tmp$ more 0b3c:f000
# Olivetti Olicard 145, 155
TargetVendor=  0x0b3c
TargetProductList="c003,c004"
MessageContent="5553424312345678c000000080010606f50402527000000000000000000000"
NeedResponse=1

New file 0b3c:f017 that I created:
# Olivetti Olicard 500, test only
TargetVendor=  0x0b3c
TargetProductList="c500"
MessageContent="5553424312345678c000000080010606f50402527000000000000000000000"
NeedResponse=1

As you can see I used the same MessageContent, but it does not work.

Is there anything else that I could try?

I'm not an expert but in my opinion my device is not recognizing the
message that we sent in the command usb_modeswitch, so is there a way to
figure out what should be the information that we should use to send the
message to the device?

Thanks,
Julio Araujo


Em 20-03-2014 13:02, Bjørn Mork escreveu:
Dan Williams <dcbw@xxxxxxxxxx> writes:

 From the information below, it appears the modem is not being switched
correctly to modem mode from storage mode.  The tool that does that is
usb_modeswitch, but usb_modeswitch does not have specific support for
your new device.

So the next steps are for you to contact the usb_modeswitch project and
work with them to get the modem successfully switched from storage mode
to modem mode.

http://www.draisberghof.de/usb_modeswitch/

Hello, did you have a chance to look into this yet?

As Dan says, this is a mode switch problem initially.  We will look
further at the drivers after the device has been successfully switched
to modem mode.

The device isn't yet known in the usb_modeswitch database.  But chances
are good that it is similar to other, already known, Olivetti devices.
You can try installing the usb-modeswitch package from Ubuntu and a
config similar to the "Olivetti Olicard 145, 155" (0b3c:f000) one:

  # Olivetti Olicard 145, 155
  TargetVendor=  0x0b3c
  TargetProductList="c003,c004"
MessageContent="5553424312345678c000000080010606f50402527000000000000000000000"
  NeedResponse=1


To test, try something like this on the command line:

sudo usb_modeswitch -V 0b3c -P f017 -M 5553424312345678c000000080010606f50402527000000000000000000000

and see what happens.  If it switches identities, then pleast rerun the
"lsusb -v -d ..." command using the new device ID.



Bjørn


Those usb_modeswitch cmd line switches are not the correct ones so will not work. The linux_usb mailing list is not the right place for getting the device supported for mode switching so I suggest you follow Dan Williams advice and get over to the usb_modeswitch forum where Josh or I will try to help you switching the device into modem mode. I'm sure Björn will help you here later on by creating patches for the linux drivers when we know which type of interfaces the device has after mode switching.

http://www.draisberghof.de/usb_modeswitch/bb/viewforum.php?f=3 is the right place
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux