ifconfig rausb0 up produces SIOCSIFFLAGS: Invalid argument

[kahealani]

I followed the instructions at:
https://help.ubuntu.com/community/WifiDocs/Device/Belkin_F5D7050_ver_3000_(Ralink_rt73_driver)?action=fullsearch&context=180&value=linkto%3A%22WifiDocs/Device/Belkin_F5D7050-ver_3000_%28Ralink_rt73_driver%29%22
for installing a Linksys WUSB54GC USB Device 13b1:0020
with the latest driver 2009_0206_RT73_Linux_STA_Drv1.1.0.2
on Kubuntu 8.04 LTS Hardy Heron:
Description: Ubuntu 8.04.2
Release: 8.04
and got as far as:
Step 7 - Install Module
sudo modprobe rt73
Check that your computer knows the device exists.
user@ubuntu:~$ iwconfig
If rausb0 is present it is time to connect to the internet.
well, iwconfig shows:
rausb0 RT73 WLAN
          Link Quality:0 Signal level:0 Noise level:113
          Rx invalid nwid:0 invalid crypt:0 invalid misc:0
and ifconfig rausb0 shows:
rausb0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          inet addr:192.168.0.98 Bcast:192.168.0.255 Mask:255.255.255.0
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
but, ifconfig rausb0 up gives:
SIOCSIFFLAGS: Invalid argument
whereas ifconfig rausb0 down gives no errors at all.

Since this was the MOST recommended Wireless USB adapter in the Linux world,
I'm a little bit hung-out-to-dry here as I try to help a friend upgrade from Windows,
to Linux, which required he replace his previous Linux-incompatible WUSB adapter.

[Andreas Gnau (rondom)]

You followed a (excuse me) damn old guide. A lot has changed since then?

Are you sure the rt73-driver doesn't work?

[Andreas Gnau (rondom)]

I meant the rt73usb-module of course.

[kahealani (angela)]

On Sunday, 2009-03-08 13:23:13 Andreas Gnau wrote:
> You followed a (excuse me) damn old guide.

OK... you're excused.
So, whose responsibility is it to maintain How-To guides,
i.e. should I file another bug report about the guide itself?

> A lot has changed since then?

You're asking me?

> Are you sure the rt73-driver doesn't work?

No. I'm sure that it's interaction with ifconfig doesn't work.

--
"(I'll) Be Seeing You..." All information and transactions are
private between the parties, and are non negotiable. All rights
reserve without prejudice, Angela Kahealani. http://kahealani.com

[kahealani (angela)]

On Sunday, 2009-03-08 18:15:20 kahealani wrote:
> On Sunday, 2009-03-08 13:23:13 Andreas Gnau wrote:
> > You followed a (excuse me) damn old guide.
>
> OK... you're excused.
> So, whose responsibility is it to maintain How-To guides,
> i.e. should I file another bug report about the guide itself?
>
> > A lot has changed since then?
>
> You're asking me?
>
> > Are you sure the rt73-driver doesn't work?

That would be "ra" not "rt" 73, right?

> No. I'm sure that it's interaction with ifconfig doesn't work.
>
> --
> "(I'll) Be Seeing You..." All information and transactions are
> private between the parties, and are non negotiable. All rights
> reserve without prejudice, Angela Kahealani. http://kahealani.com

--
"(I'll) Be Seeing You..." All information and transactions are
private between the parties, and are non negotiable. All rights
reserve without prejudice, Angela Kahealani. http://kahealani.com

[Borrelli (massageguy82)]

We have that module subversion "2.6.24-23- generic" installed on a fully updated Kubuntu Hardy installation. We also have the Rt driver installed which was mentioned in the bug report. At this point, there is nothing further we can do until either
1 the chip manufacture issues a new driver version or
2 there is an update to Kubuntu Hardy which propagates to this computer or
3 the how-to-guide gets updated.
We followed the latest instructions and and have installed the latest software and driver, which leaves us with waiting for an update to make this thing work.

[Andreas Gnau (rondom)]

My question is, if you have tried without following any guides. Ubuntu already ships a driver that should (as far as I know) work.
It is likely that if you didn't need to follow any guide it could maybe work without any problems.

[kahealani (angela)]

On Wednesday, 2009-03-11 12:40:41 Andreas Gnau wrote:
> My question is, if you have tried without following any guides.
> Ubuntu already ships a driver that should (as far as I know) work. It
> is likely that if you didn't need to follow any guide it could maybe
> work without any problems.

Yes, tried to use it without installing any drivers,
and KNetworkManager saw no Wireless interfaces UNTIL
we installed the ra73 driver, then it saw a Wireless interface,
but it was not possible to activate it, due to the use of
a pre-up command which fails, specifically the reported problem
of ifconfig rausb0 up produces SIOCSIFFLAGS: Invalid argument.

Aloha, Angela Kahealani
--
"(I'll) Be Seeing You..." All information and transactions are
private between the parties, and are non negotiable. All rights
reserve without prejudice, Angela Kahealani. http://kahealani.com

[Borrelli (massageguy82)]

Hello there...
I was just wondering if anyone has yet to find a solution to this bug? I've been without Internet access now for over a month and would really like to use this adapter!
Is there any hope or should I scratch the idea of using this with linux?
Thanx!

[heatblazer (heatblazer-gmail)]

I`ve saw this too. A friedn of mine reported me that he had the same problem after switching from LAN of PC1 to LAN of PC2. As far as I can tell all problems have a similaritu - the MAC is based on 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF... guess gotta try changing these MACs:
ifconfig eth0 down
ifconfig eth0 hw ether AF:01:BF:02:CF:03
ifconfig eth0 up
or if it`s not possible to do, run
cd /etc
sudo gedit rc.local
#input the following command before "exit 0"
ifconfig eth0 hw ether AF:01:BF:02:CF:03
save and close rc.local file
reboot
Report again.

[kahealani (angela)]

I can no longer participate in this, the friend with the hardware returned it to store for refund since we couldn't make it work for him. I'll unsubscribe from this bug therefore.