Bug 437959

its in the kernel-<flavour> package.

do we pack them for the Live CDs?

of course kernel-<flavor> is part of the live cd.

find /lib/modules/ | grep rt2860sta
returns nothing, so it looks like the driver is not there.

The driver should be part of the kernel-default-extra package which should be on the media.  Kernel team, does the rt2x driver really support this?

rt2860sta.ko is definitely the driver that is needed, I tested this on Ubuntu.

The driver is not on opensuse 11.1 yet.
Its not in the mainline kernel in 2.6.28-rc1 either.

Btw, the
home:etrash:eeePC/openSUSE_11.0 repo
has RPMs already, no need to build them yourself. Perhaps update the HOWTO.


Greg, do you want to pick it up for our kernel, or do you want me to put in a KMP if possible? (I guess for upstream iot should come via the wireless guys).

Marcus, I'll take this one, it needs to get merged upstream, I'll handle getting it there, and into our distro...

thanks!

i wanted to build a KMP for 11.1, but this driver opens a userland file from kernel space, which to IRC#suse comments is not acceptable. (but you will see this yourself, just fyi ;)

Yes, I am well aware of the crazy user interface interactions of this driver :)

I'm working on getting this into the staging tree, which will make it fine to import it into our tree as well.
Over time the user interface mess will be cleaned up, but for now, we can live with such a horrible thing just to get the hardware working.

Now added to the staging kernel tree, and to our kernel cvs.

It should be included in Beta 5, Beta 4 deadline was missed, sorry.  Or you can try the kernel-of-the-day if you wish to try this out sooner.

*** Bug 441155 has been marked as a duplicate of this bug. ***

I'm with kernel 2.6.27.4-6-default right now...the module rt2860sta loads just fine but networkmanager doesn't see my wireless card. Also ifconfig just shows eth0...this on a  eeepc 901

In openSUSE 11.1 Beta 5 the wireless card is not shown in the Network Manager. So I am reopening this bug, since from the perspective of an user nothing has changed since the initial report.

But does the driver bind properly to the device?

Can you attach the output of 'hwinfo' on Beta5 for this hardware?

66: None 00.0: 10701 Ethernet
  [Created at net.124]
  Unique ID: GHP6.ndpeucax6V1
  SysFS ID: /class/net/ra0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Device File: ra0
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Yes, ra0 shows up in iwconfig.

does not using networkmanager work properly for this hardware then?

I was able to connect to the network using the following commands:

ifconfig ra0 down
ifconfig ra0 up
ifconfig ra0 down
ifconfig ra0 up
iwpriv ra0 set SSID=XXXXX
iwconfig ra0 essid XXXXX
iwconfig ra0 mode Managed
iwconfig ra0 rate 54M
iwpriv ra0 set AuthMode=WPAPSK
iwpriv ra0 set EncrypType=TKIP
iwpriv ra0 set WPAPSK= XXXXX
ifconfig ra0 up
dhclient ra0

However, Network Manger still shows nothing.

Thanks, this shows the kernel driver is working properly.  As this is a "staging" driver, the userspace interface might not work properly for all programs.

I'll reassign this to the networkmanager developers to see what they can do about it on their end.

Thank you. Maybe this information is useful: When I install the .ko in Ubuntu, then their Network Manager is able to handle it correctly.

Greg, at least the following two config variables should be set to 'y'. Otherwise the driver does not expose wext correctly and cannot be used with wpa_supplicant (and NM).

--- /dev/null
+++ b/drivers/staging/rt2860/config.mk
@@ -0,0 +1,245 @@
...
+# Support Wpa_Supplicant
+HAS_WPA_SUPPLICANT=n
+
+# Support Native WpaSupplicant for Network Maganger
+HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n

(In reply to comment #21 from Helmut Schaa)
> Greg, at least the following two config variables should be set to 'y'.
> Otherwise the driver does not expose wext correctly and cannot be used with
> wpa_supplicant (and NM).
> 
> --- /dev/null
> +++ b/drivers/staging/rt2860/config.mk
> @@ -0,0 +1,245 @@
> ...
> +# Support Wpa_Supplicant
> +HAS_WPA_SUPPLICANT=n
> +
> +# Support Native WpaSupplicant for Network Maganger
> +HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n

Heh, config.mk in that directory does nothing for the build of that driver.

Give me a minute, and I'll tweak the Makefile properly...

Ok, fix is now made and checked into the kernel tree. Should be resolved in the next kernel update or beta release, which ever happens first.

If not, please reopen and let me know.

Greg, it seems to work fine on my eeepc 901. I've also tested it with wpa. No problems so far...a BIG thank you to you! :)

just one thing...is the module automatically loaded on boot? on my system I had to add it to /etc/sysconfig/kernel. This may be a little hard for a new user to do...

it should be.

hwinfo --netcard 

shows if it is autodetected.

Works using Network Manager in RC1. Thank you very much.

I'm sorry to reopen this but I'm facing a nasty bug on my 901 and I really suspect that this ralink driver is the root of the problem...
I described the problem I have here:
https://bugzilla.novell.com/show_bug.cgi?id=448959
First I didn't suspected it was a problem caused by this driver but then I saw this:
http://wiki.eeeuser.com/bugfixes:blackscreenhang901
Maybe we should change something in the userspace program to work around this?
feel free to close the bug report if you think that I'm completely wrong about this...
Giovanni

(In reply to comment #28 from Giovanni Masucci)
> I'm sorry to reopen this but I'm facing a nasty bug on my 901 and I really
> suspect that this ralink driver is the root of the problem..

No, this is a separate issue, it will be addressed in the original bug report, not here, sorry.

Closing out.