Re: strange behaviour of MC7700 with sierra_net

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

 



Phil Sutter <phil@...> writes:
> 
> Dan,

Hello Phil and Dan;

(I don't english native writer, sorry same errors)



> 
> Thanks for the quick reply!
> 
> On Wed, Jul 27, 2011 at 02:40:40PM -0500, Dan Williams wrote:
> > I wonder if the firmware changed and Sierra hasn't updated the driver
> > yet.  I've got a usb306 which also uses sierra_net which doesn't have
> > this problem.  It looks like the driver tries to sync with the firmware
> > right after binding to the net interface, so that means at least a
> > couple of SYNC requests have already happened by the time you start
> > getting errors.  My first thought here is simply that the firmware on
> > the MC7700 doesn't work like the rest of the devices that sierra_net
> > expects, and for that you'd have to get Sierra to weigh in on the
> > required changes :(
> 
> That's exactly the case. My printf-debugging shows that ~30 calls to
> sierra_net_dosync() sycceed before it starts failing. Why the heck does
> that work if I set the interface up? When doing so, the driver
> immediately receives a whole bunch of restart-messages. Looks
> like the number matches the number of successfully sent sync-messages.

I have this problem with a 2.6.38 kernel using my Sierra AirCard 305 USB. When 
connect the modem, its not recognized and the syslog show the messages:

sierra_net 1-1:1.7: wwan0: Send SYNC failed


After most logs analyses, I solve the problem editing the sierra.c and 
sierra_net.c and insertig the correctly values of the product and vendor ID. 

The source code of drivers contais the entries writed using UPERCASE caracters 
for descript the products:

>From the sierra_net.c

965 static const struct usb_device_id products[] = {
966         {USB_DEVICE(0x1199, 0x68A3), /* Sierra Wireless USB-to-WWAN modem */
967         .driver_info = (unsigned long) &sierra_net_info_68A3},

The lsusb output:

Bus 001 Device 003: ID 1199:68a3 Sierra Wireless, Inc. 

Then I just edit the sierra_net.c and siarra.c files writing the values using 
lowcase 68a3 against the original writed with UPERCASE 68A3 (in my case, only 
the "A" caracter for my product). After edition, I make the modules compilation 
and install the sierra nmodules and bee happy again with 3g connection and 
2.6.38 kernel!!!!


I send the bug report from the kernel's mantainers.

Cheers from Brazil!!!!


--
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