WiMAX driver crash on load

[charles zhuang]

I bought from Asus. I intend to use it on a linux device, but found out
this model, WUSB25E2V2, is only for windows. The open source linux code
can't be used directly on this dongle.

Charles

-----Original Message-----
From: Nicolas GIRARD [mailto:ngirard at gmail.com] 
Sent: Tuesday, January 06, 2009 10:29 AM
To: charles zhuang
Cc: 'Perez-Gonzalez, Inaky'; 'Andrew Zabolotny'; wimax at linuxwimax.org
Subject: Re: WiMAX driver crash on load


Hi all,

I'm looking to purchase an Intel-based WiMAX USB dongle. Could you  
tell me where you bought yours ? Appreciate it. Thanks

Nicolas

On Nov 19, 2008, at 3:29 PM, charles zhuang wrote:

> Andrew,
> I believe I got the same Asus dongle, WUSB25E2V2, as yours. Just
> wondering why on my host (linux, windows) it's showing as a mass  
> storage
> device? Do you need to do anything special on your linux host?
>
> Thanks,
> Charles
>
> -----Original Message-----
> From: wimax-bounces at linuxwimax.org
[mailto:wimax-bounces at linuxwimax.org 
> ]
> On Behalf Of Perez-Gonzalez, Inaky
> Sent: Sunday, November 16, 2008 11:52 PM
> To: Andrew Zabolotny; wimax at linuxwimax.org
> Subject: RE: WiMAX driver crash on load
>
>> From: Andrew Zabolotny
>>
>> I'm trying the latest WiMax driver on a Fedora9 x86_64 system.  
>> Besides
>> a few warnings during compilation (mismatch sizes in printk() format
>> strings) I get a kernel crash when I insert the WiMax USB dongle into
>> ..
>>
>> Does anybody have a positive experience with the drivers on x86_64
>> and/or Fedora9 and/or kernel 2.6.26?
>
> I think I know this one. It was my brain not being in proper gear and
> miscalculating an allocation's size, which causes memory overruns in
> drivers/net/wimax/id-table.c.
>
> Would you please try this patch?
>
> --- a/drivers/net/wimax/id-table.c	Tue Oct 28 11:06:38 2008 -0700
> +++ b/drivers/net/wimax/id-table.c	Tue Oct 28 14:43:07 2008 -0700
> @@ -83,7 +83,8 @@ int wimax_id_table_add(int id, struct wi
> 	 * we just create one slot -- I sure doubt most machines will
> 	 * have more than one wimax adapter.*/
> 	new_size = wimax_id_table_size? 2 * wimax_id_table_size : 1;
> -	new_table = krealloc(wimax_id_table, new_size, GFP_ATOMIC);
> +	new_table = krealloc(wimax_id_table, new_size *
> sizeof(new_table[0]),
> +			     GFP_ATOMIC);
> 	if (unlikely(new_table == NULL)) {
> 		result = -ENOMEM;
> 		goto out_unlock;
>
> Next driver release should have all the 64 bit glitches fixed.
>
> On the other hand; currently the user space code is supported only  
> in 32
> bits; on one hand, nobody has had the time to make sure it is 64 bit
> clean. On the other, the binary supplicant is still (sadly) binary  
> ia32.
> Yes, we
> keep trying to clean up the red tape, but I doubt we'll be able in the
> coming weeks to make the code 64 bit clean.
>
> _______________________________________________
> wimax mailing list
> wimax at linuxwimax.org
> http://www.linuxwimax.org/mailman/listinfo/wimax
>
> _______________________________________________
> wimax mailing list
> wimax at linuxwimax.org
> http://www.linuxwimax.org/mailman/listinfo/wimax