Ralink Wirless Driver Help

changedsoul · November 11, 2012, 10:47pm

I got myself a brand spankin new laptop, and I know driver support will be lacking for a while. Surprisingly though everytyihng works out of the box except my wireless. I searched the web and cant seem to find much about it. I was hoping someone here might have had success with this wirless card.
My lspci -nnk output is:


02:00.0 Network controller [0280]: Ralink corp. Device [1814:539b]            
        Subsystem: Hewlett-Packard Company Device [103c:18ed]

I searched my dmesg for anything related to firmware, etc, but nothing shows up. Does anyone know if this might be related to another wirleess card that I could use its driver for?

lwfinger · November 11, 2012, 11:22pm

On 11/11/2012 03:56 PM, changedsoul wrote:
>
> I got myself a brand spankin new laptop, and I know driver support will
> be lacking for a while. Surprisingly though everytyihng works out of the
> box except my wireless. I searched the web and cant seem to find much
> about it. I was hoping someone here might have had success with this
> wirless card.
> My lspci -nnk output is:
>
> Code:
> --------------------
>
> 02:00.0 Network controller [0280]: Ralink corp. Device [1814:539b]
> Subsystem: Hewlett-Packard Company Device [103c:18ed]
>
> --------------------
>
>
> I searched my dmesg for anything related to firmware, etc, but nothing
> shows up. Does anyone know if this might be related to another wirleess
> card that I could use its driver for?

That device uses rt2800pci as the driver; however, that device ID was added to
the kernel on May 10, 2012. As a result, the standard kernel from any version of
openSUSE is too old.

Install the compat-wireless package for your kernel. Due to lack of information
regarding your version, I cannot be more specific.

changedsoul · November 13, 2012, 12:38am

I searched yast for compat-wirless and didnt find anything. My kernel version is: 3.4.11-2.16-desktop

Any help?

samrat_rao · November 14, 2012, 11:08am

Hi,

As per this topic http://forums.opensuse.org/english/get-technical-help-here/wireless/480382-atheros-ar8162-fast-ethernet-1969-1090-rev-10-not-detected.html it is available here: Index of /repositories/driver:/wireless/openSUSE_12.2

I think it is also available if you add these repos:

changedsoul · November 17, 2012, 2:19am

Thanks for the link to them repos. I have tried installing from them with no luck. Ill cut my losses I guess until a newer kernel comes out and it works with it. I consider myself pretty fortunate my wireless is the only thing that doesnt work on this, and even that I have a external usb wireless to get me by.

CMOB · January 20, 2013, 7:49pm

Hi folks,

Just wondering if there is any progress on a fix for this problem.
I am having a similar problem, new install of SUSE and the ralink wireless controller (1814:539b) is not working.
The thread linked above is about a different driver as far as I can see.

Not a hardware issue as it worked in Ubuntu and Windows 8.

I gather it takes rt2800pci driver.
How do I get this working on my system?

Cheers.

CMOB · January 20, 2013, 9:54pm

This is part of the output of lspci -v

01:00.0 Network controller: Ralink corp. Device 539b
        Subsystem: Hewlett-Packard Company Device 18ed
        Flags: bus master, fast devsel, latency 0
        Memory at c2500000 (32-bit, non-prefetchable) [size=64]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-00-51-d4-64-23-94-68

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
        Subsystem: Hewlett-Packard Company Device 183f
        Flags: bus master, fast devsel, latency 0, IRQ 44
        I/O ports at 3000 [size=256]
        Memory at c2404000 (64-bit, prefetchable) [size=4]
        Memory at c2400000 (64-bit, prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
        Kernel driver in use: r8169

does the absence of “kernel driver in use:” after the ralink device mean it has no driver?

output of lsmod | grep rt2800

rt2800pci              18528  0 
rt2800lib              58478  1 rt2800pci
crc_ccitt              12667  1 rt2800lib
rt2x00pci              14475  1 rt2800pci
rt2x00lib              54852  3 rt2800pci,rt2800lib,rt2x00pci
mac80211              555559  3 rt2800lib,rt2x00pci,rt2x00lib
eeprom_93cx6           13302  1 rt2800pci

iwconfig:


eth0      no wireless extensions.

lo        no wireless extensions.

/usr/sbin/iwlist wlan0 scan


wlan0     Interface doesn't support scanning.

That suggets that drivers are there doesn’t it?
This worked out of the box on Ubuntu…[/size][/size][/size][/size]

CMOB · January 20, 2013, 10:35pm

Ok,

I got it kind of working but it doesn’t persist after reboot.

What worked was going YaST> Kernel Settings > PCI ID setup and adding an entry.
Driver: pci:rt2800pci
SysFS Directory: rt2800pci
PCI Device:
RaLink Network Controller (0000:01:00.0)

But after reboot this doesn’t work.

SO I go to /sys/bus/pci/drivers and see that rt2800pci is NO LONGER THERE???

Alright…
/sbin/modprobe -v rt2800pci

then
redo the kernel settings in yast gui and I get prompted for my wireless password.

PLEASE:
How do I get the modprobe change to persist past reboot?

Also how do I do the kernel setting thing from command line?

Thanks in advance.

CMOB · January 20, 2013, 11:08pm

HACK.

I added a file to /etc/modules-load.d called it rt2800pci.conf
with the line rt2800pci.

Which apparently loads the module on boot.
Half way.

But I still need to start YaST and renew the kernel settings thing.

lwfinger · January 21, 2013, 12:27am

On 01/20/2013 04:16 PM, CMOB wrote:
>
> HACK.
>
> I added a file to /etc/modules-load.d called it rt2800pci.conf
> with the line rt2800pci.
>
> Which apparently loads the module on boot.
> Half way.
>
> But I still need to start YaST and renew the kernel settings thing

What version of openSUSE are you using? Your device was added to the rt2800pci
driver in kernel 3.4, thus you need to be running at least 12.2.

Drivers are automatically loaded based on their PCI ID. When one fails to load,
either that ID is not in a driver’s table, or it is blacklisted by some entry in
/etc/modprobe.d/.

Extraordinary measures of the type you describe may get the driver loaded, but
it still will not work unless the driver contains that ID.

CMOB · January 21, 2013, 12:43am

First up, thanks for responding.

Its a new install of 12.2.

I have just rebooted. The driver is loaded and if I go into the PCI ID setting tool in YaST it will work.
But I want it to work on startup

How do I know if the ID is in the drivers table?
I’m pretty sure its not on the blacklist.

deano_ferrari · January 21, 2013, 12:46am

How do I know if the ID is in the drivers table?

modinfo rt200pci

However, I’m running openSUSE 12.2 and I don’t see your chipset listed

# modinfo rt2800pci |grep 1814
alias:          pci:v00001814d0000539Fsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Asv*sd*bc*sc*i*
alias:          pci:v00001814d00005390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003593sv*sd*bc*sc*i*
alias:          pci:v00001814d00003592sv*sd*bc*sc*i*
alias:          pci:v00001814d00003562sv*sd*bc*sc*i*
alias:          pci:v00001814d00003062sv*sd*bc*sc*i*
alias:          pci:v00001814d00003060sv*sd*bc*sc*i*
alias:          pci:v00001814d00003390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003092sv*sd*bc*sc*i*
alias:          pci:v00001814d00003091sv*sd*bc*sc*i*
alias:          pci:v00001814d00003090sv*sd*bc*sc*i*
alias:          pci:v00001814d00000781sv*sd*bc*sc*i*
alias:          pci:v00001814d00000701sv*sd*bc*sc*i*
alias:          pci:v00001814d00000681sv*sd*bc*sc*i*
alias:          pci:v00001814d00000601sv*sd*bc*sc*i*

CMOB · January 21, 2013, 12:55am

alias:          pci:v00001814d0000539Fsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Asv*sd*bc*sc*i*
alias:          pci:v00001814d00005390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003593sv*sd*bc*sc*i*
alias:          pci:v00001814d00003592sv*sd*bc*sc*i*
alias:          pci:v00001814d00003562sv*sd*bc*sc*i*
alias:          pci:v00001814d00003062sv*sd*bc*sc*i*
alias:          pci:v00001814d00003060sv*sd*bc*sc*i*
alias:          pci:v00001814d00003390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003092sv*sd*bc*sc*i*
alias:          pci:v00001814d00003091sv*sd*bc*sc*i*
alias:          pci:v00001814d00003090sv*sd*bc*sc*i*
alias:          pci:v00001814d00000781sv*sd*bc*sc*i*
alias:          pci:v00001814d00000701sv*sd*bc*sc*i*
alias:          pci:v00001814d00000681sv*sd*bc*sc*i*
alias:          pci:v00001814d00000601sv*sd*bc*sc*i*

Me neither…
Everything but it would seem.
So what do I do now? Do i need to update it?

deano_ferrari · January 21, 2013, 1:10am

CMOB:

alias:          pci:v00001814d0000539Fsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Asv*sd*bc*sc*i*
alias:          pci:v00001814d00005390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003593sv*sd*bc*sc*i*
alias:          pci:v00001814d00003592sv*sd*bc*sc*i*
alias:          pci:v00001814d00003562sv*sd*bc*sc*i*
alias:          pci:v00001814d00003062sv*sd*bc*sc*i*
alias:          pci:v00001814d00003060sv*sd*bc*sc*i*
alias:          pci:v00001814d00003390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003092sv*sd*bc*sc*i*
alias:          pci:v00001814d00003091sv*sd*bc*sc*i*
alias:          pci:v00001814d00003090sv*sd*bc*sc*i*
alias:          pci:v00001814d00000781sv*sd*bc*sc*i*
alias:          pci:v00001814d00000701sv*sd*bc*sc*i*
alias:          pci:v00001814d00000681sv*sd*bc*sc*i*
alias:          pci:v00001814d00000601sv*sd*bc*sc*i*

Me neither…
Everything but it would seem.
So what do I do now? Do i need to update it?

You could try building a newer kernel. I’m not sure whay it didn’t make it to 3.4 as Larry suggested was the case.

One of our members has simplified this job for you:

https://forums.opensuse.org/blogs/jdmcdaniel3/s-k-c-suse-automated-kernel-compiler-version-2-78-34/

CMOB · January 21, 2013, 1:26am

Well that sounds like a bit of work and I wouldn’t have the first clue.
Also, I’m out of time.

Thanks anyway.

deano_ferrari · January 21, 2013, 1:40am

Well you could compile the driver, but maybe that’s too much for you?

It might also be possible to achieve by editing /lib/modules/<your kernel version>>/modules.alias directly, although as Larry has hinted at already, this kind of hack may not be sufficient in getting the rt2800pci module to recognise your card.

You’d need to edit with root privileges of course. Find the entries pertaining to this driver…

alias pci:v00001814d0000539Fsv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d0000539Asv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00005390sv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00003593sv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00003592sv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00003562sv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00003062sv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00003060sv*sd*bc*sc*i* rt2800pci

then add your chipset like this

alias pci:v00001814d0000539Bsv*sd*bc*sc*i* rt2800pc

However, any kernel upgrade will overwrite this system file.

lwfinger · January 21, 2013, 4:03am

On 01/20/2013 06:46 PM, deano ferrari wrote:
>
> Well you could compile the driver, but maybe that’s too much for you?
>
> It might also be possible to achieve by editing /lib/modules/<your
> kernel version>>/modules.alias directly, although as Larry has hinted at
> already, this kind of hack may not be sufficient in getting the
> rt2800pci module to recognise your card.
>
> You’d need to edit with root privileges of course. Find the entries
> pertaining to this driver…
>
>
> Code:
> --------------------
> alias pci:v00001814d0000539Fsvsdbcsci* rt2800pci
> alias pci:v00001814d0000539Asvsdbcsci* rt2800pci
> alias pci:v00001814d00005390svsdbcsci* rt2800pci
> alias pci:v00001814d00003593svsdbcsci* rt2800pci
> alias pci:v00001814d00003592svsdbcsci* rt2800pci
> alias pci:v00001814d00003562svsdbcsci* rt2800pci
> alias pci:v00001814d00003062svsdbcsci* rt2800pci
> alias pci:v00001814d00003060svsdbcsci* rt2800pci
> --------------------
>
> then add your chipset like this
>
> Code:
> --------------------
> alias pci:v00001814d0000539Bsvsdbcsci* rt2800pc
> --------------------
>
> However, any kernel upgrade will overwrite this system file.

Do not even bother with that. The changes to get that device working were more
than adding the ID to the table, otherwise I would have given you to appropriate
command to write new_id.

If you install the compat-wireless package, then the driver should work.

deano_ferrari · January 21, 2013, 4:13am

Do not even bother with that. The changes to get that device working were more
than adding the ID to the table, otherwise I would have given you to appropriate
command to write new_id.

I was sure that would be the case, although CMOB seemed to have success wit the YaST >> Hardware >> Kernel Settings, andadding the PCI ID, so I thought there might be a chance to make it persistent via modules.alias…ah well.

deano_ferrari · January 21, 2013, 4:15am

If you install the compat-wireless package, then the driver should work.

That is good to know. Does it contain a list of new device IDs or similar?

lwfinger · January 21, 2013, 4:57am

On 01/20/2013 09:16 PM, deano ferrari wrote:
>
>> If you install the compat-wireless package, then the driver should work.
>>
> That is good to know. Does it contain a list of new device IDs or
> similar?

Compat-wireless contains the wireless drivers from 3.7. Any
changes/updates/additions in the 9-12 months between 3.4 and 3.7 will be included.