I’m brand new to Linux. In face, I installed and used Linux for the first time through openSUSE 12.1. My problem is that I cannot figure out how to make my RT3062 card work on SUSE. When booted to desktop, the card does not even turn on. It is only after I use YAST to check the network settings that the card turns on. Even then, it cannot connect to the internet and wants me to configure it. The problem is that I don’t know how.
Knowing that openSUSE offers free drivers for various hardware devices, I downloaded the official RPM pack (ralink-firmware-1.2-1.2.src.rpm) and installed it. It should be appreciated that I was prompted to delete the default network drivers for SUSE, and did so in order to be able to update to the 12.1 RALINK driver pack. After updating it, I still cannot connect to the internet, and the card still does not turn on during boot either >:(.
I do have the CD for the network card, which contains the RT2860 (I know: the version does not match my card model [3062], but it’s the latest driver that they have, even on their website!) for my native Windows XP as well as for Linux. I attempted to install the Linux pack to the computer, but the instructions were simply the most complicated installation instructions I had ever had to deal with in my life. :’(
I simply have no idea left on what to do to resolve the problem and get the card to work. Could someone please let me know what I have to do? Thanks in advance. lol!
On 11/18/2011 10:36 AM, Dragon32 wrote:
>
> Found this link, it might help you:
>
> ‘Setting up a Wireless Network on Linux: Ralink 3062 and Network
> Manager | K-Squared Ramblings’
> (http://www.hyperborea.org/journal/2010/08/wifi-ralink-3062/)
With 12.1, you do not need to compile an out-of-kernel driver for this device.
Have you read the stickies at the beginning of this Forum? In particular, you
need to confirm that the driver rt2800pci is loaded using ‘lsmod | grep rt28’,
that the firmware is available by confirming that the package kernel-firmware is
installed using ‘sudo zypper in kernel-firmware’, and that your wireless radio
is not blocked. To do the latter test, install rfkill with ‘sudo zypper in
rfkill’ and run the command ‘/usr/sbin/rfkill list’. If the answer is “yes” on
any of the lines, that is a problem. In particular, is your wireless switch on?
Note: Drivers are a part of the kernel, not the distro. Any versions of Linux
with the same kernel release will have the same drivers installed.
Dragon32:
That whole installation of the official Linux Ralink drivers was just impossibly confusing. I couldn’t get past step 5 before I had no clue about what I was supposed to do. I don’t know what was meant by “Build it by typing make in the main folder of the source archive.” I neither had an idea of were I was supposed to put the exact files, or where the “wireless” folder was at. :X
Regardless of the difficulties, I really appreciate your aid. rotfl! Could you please clarify for me though what I’m supposed to do though? I’m really just a complete newb to Linux. :S
lwfinger:
I did not look at the stickies. They looked really complicated and long, and when I searched for the “rt” lettering referring to the driver in the stickies no results came out.
Lol, how do I confirm that the driver is loaded with ‘lsmod | grep rt28’??
What is that ‘sudo zypper’ thing I have to use to make sure that the hardware is installed right??
As far as the antenna goes, I am completely confident that it is not blocked in any form or way. When I boot into Windows XP it works correctly without me having to move the antenna around or fiddle about with settings, which proves that the problem in linux is coming from the hardware not working together with its firmware.
I got rfkill downloaded, but I don’t know how to use that ‘sudo zypper’ thing. And where would I run the command line?
Thanks a lot for the note. I really did notice that there are actually a lot of rt****.bin files in the lib folder. I really appreciate your help with my problem. lol!
> Dragon32:
> That whole installation of the official Linux Ralink drivers was just
> impossibly confusing. I couldn’t get past step 5 before I had no clue
> about what I was supposed to do. I don’t know what was meant by “Build
> it by typing make in the main folder of the source archive.” I neither
> had an idea of were I was supposed to put the exact files, or where the
> “wireless” folder was at. :X
> Regardless of the difficulties, I really appreciate your aid. rotfl!
> Could you please clarify for me though what I’m supposed to do though?
> I’m really just a complete newb to Linux. :S
>
> lwfinger:
> I did not look at the stickies. They looked really complicated and
> long, and when I searched for the “rt” lettering referring to the driver
> in the stickies no results came out.
> Lol, how do I confirm that the driver is loaded with ‘lsmod | grep
> rt28’??
You open a terminal from kickoff and type the stuff inside the single quotes.
> What is that ‘sudo zypper’ thing I have to use to make sure that the
> hardware is installed right??
No, it is for installing software.
> As far as the antenna goes, I am completely confident that it is not
> blocked in any form or way. When I boot into Windows XP it works
> correctly without me having to move the antenna around or fiddle about
> with settings, which proves that the problem in linux is coming from the
> hardware not working together with its firmware.
That is not correct. AFAIK, Windows XP does not pay much attention to the rfkill
signals. For safety, Linux does. Rfkill has NOTHING to do with the antenna.
> I got rfkill downloaded, but I don’t know how to use that ‘sudo zypper’
> thing. And where would I run the command line?
As I said before, in a terminal. Think of it as cmd.exe on steroids. Many of us
will give you commands to execute because (1) ‘sudo zypper in rfkill’ is a lot
simpler than saying Start => YaST => Software Management => Search for rfkill
and install the package, and (2) there are a lot of very useful commands that do
not have a GUI equivalent.
> Thanks a lot for the note. I really did notice that there are actually
> a lot of rt****.bin files in the lib folder. I really appreciate your
> help with my problem. lol!
The files should be in /lib/firmware, not /lib. Your device will need rt2800.bin.
Oh that’s what you meant with the codes. It seems to me that when people talk about doing things in Linux-like OSs, it is a given to them that you already know what is implied by what they are telling you to do. But for novices like me, that’s not the case. But anyways…
Could you explain to me what an rfkill switch is? And I thought that you meant physical blockage of the antenna, not something having to do with the hardware.
But I used the commands you told me. Here is what came up for ‘lsmod | grep rt28’ command:
And for the ‘sudo zypper in kernel-firmware’ command, which kept on trying to download even though I had used the abort (a) switch:
Martin@linux-y0sr:~> sudo zypper in kernel-firmware
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
root’s password:
Sorry, try again.
root’s password:
Retrieving repository ‘Updates for openSUSE 12.1 12.1-1.4’ metadata ]
Download (curl) error for ‘http://download.opensuse.org/update/12.1/repodata/repomd.xml’:
Error code: Connection failed
Error message: Could not resolve host: download.opensuse.org (Could not contact DNS servers)
Abort, retry, ignore? [a/r/i/?] (a):
I appreciate your support.
Note: I cannot receive an internet connection through openSUSE. And as you stated, the files were actually in /lib/firmware.
Edit: I forgot to mention that I actually predownloaded the rfkill software on Windows but could not figure out how to install it when I was in Linux. It told me to type some “make” to “build” the file, but I could not figure out what I was supposed to do. Could you let me know how “build” linux files?? Thank you once again.
On 11/19/2011 10:36 AM, Maht33n wrote:
>
> Oh that’s what you meant with the codes. It seems to me that when
> people talk about doing things in Linux-like OSs, it is a given to them
> that you already know what is implied by what they are telling you to
> do. But for novices like me, that’s not the case. But anyways…
I would sooner have a novice like you ask “what do you mean?” than insult
someone with more experience. Just becaquse you just came from Windows does not
automatically mean that you know nothing of the command line.
> Could you explain to me what an rfkill switch is? And I thought that
> you meant physical blockage of the antenna, not something having to do
> with the hardware.
It is a switch that disables ALL the radios. You need to use it when on an
airplane, or in a blasting zone. For safety, it MUST be obeyed.
> But I used the commands you told me. Here is what came up for ‘lsmod |
> grep rt28’ command:
>
> Martin@linux-y0sr:~> lsmod | grep rt28
> rt2800pci 18340 0
> rt2800lib 52907 1 rt2800pci
> crc_ccitt 12595 1 rt2800lib
> rt2x00pci 14202 1 rt2800pci
> rt2x00lib 52347 3 rt2800pci,rt2800lib,rt2x00pci
> mac80211 298525 3 rt2800lib,rt2x00pci,rt2x00lib
> eeprom_93cx6 12653 1 rt2800pci
> Martin@linux-y0sr:~> ^C
Your driver is loaded.
> And for the ‘sudo zypper in kernel-firmware’ command, which kept on
> trying to download even though I had used the abort (a) switch:
>
> Martin@linux-y0sr:~> sudo zypper in kernel-firmware
>
> We trust you have received the usual lecture from the local System
> Administrator. It usually boils down to these three things:
>
> #1) Respect the privacy of others.
> #2) Think before you type.
> #3) With great power comes great responsibility.
>
> root’s password:
> Sorry, try again.
> root’s password:
> Retrieving repository ‘Updates for openSUSE 12.1 12.1-1.4’ metadata
> ]
> Download (curl) error for
> ‘http://download.opensuse.org/update/12.1/repodata/repomd.xml’:
> Error code: Connection failed
> Error message: Could not resolve host: download.opensuse.org (Could not
> contact DNS servers)
>
> Abort, retry, ignore? [a/r/i/?] (a):
>
>
> I appreciate your support.
>
> Note: I cannot receive an internet connection through openSUSE. And as
> you stated, the files were actually in /lib/firmware.
If you do not have network in openSUSE, then the ‘zypper in’ commands will not
work for obvious reasons.
Well I didn’t mean to offend you, but I was just making an observation. But that’s just trivial towards the resolution of the problem. At first, I did not think that the phrases in ‘xxxx’ were actually commands to use on the terminal, which is the reason why I was so confused. I do have plenty of experience with using the Command Prompt in Windows OSs.
And thanks for letting me know what it meant. I now see how it could have related to this problem, since the network card does not even turn on when SUSE is started.
And I attempted your commands. The first one did not provide an output (dmesg | grep firmware):
And now it just occurred in my mind that by saying “firmware” you might have wanted me to put in the name of the driver as done in the lsmod command (RT28). Is this correct??
The second one provided this output (sudo /usr/sbin/iwlist scan):
Martin@linux-y0sr:~> sudo /usr/sbin/iwlist scan
root's password:
lo Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Network is down
eth0 Interface doesn't support scanning.
Martin@linux-y0sr:~>
> And I attempted your commands. The first one did not provide an output
> (dmesg | grep firmware):
That means the firmware is not included. You should have gotten a “Loading
firmware” message. Earlier, you said that there were rt2*.bin files in /lib. Did
you mean that, or are they in /lib/firmware?
Post the output of the following:
ls /lib/rt2*
ls /lib/firmware/rt2*
And now it just occurred in my mind that by saying “firmware” you
might have wanted me to put in the name of the driver as done in the
lsmod command (RT28). Is this correct??
No, I meant “firmware”. If I want the name of the driver, I’ll say so.
The second one provided this output (sudo /usr/sbin/iwlist scan):
Code:
Martin@linux-y0sr:~> sudo /usr/sbin/iwlist scan
root’s password:
lo Interface doesn’t support scanning.
wlan0 Interface doesn’t support scanning : Network is down
eth0 Interface doesn’t support scanning.
The “Network is down” message may mean that the rfkill switch is set. Does your
computer have a wireless switch? If so, does changing it help?
To know for sure, we will need the rfkill utility. As you have no network access
in openSUSE, we will need to download the necessary RPM from the openSUSE web
site, transfer it to Linux using removable media, and then install it.
I mistakenly posted that the drivers were on /lib, when they were in fact in /lib/firmware. Sorry for that.
This is the output for the ls /lib/rt2* command, which as expected, showed that no drivers were found:
Martin@linux-y0sr:~> ls /lib/rt2*
ls: cannot access /lib/rt2*: No such file or directory
Martin@linux-y0sr:~>
This is the output for the ls /lib/firmware/rt2* command, which shows the rt firmwares available:
Martin@linux-y0sr:~> ls /lib/firmware/rt2*
/lib/firmware/rt2561.bin /lib/firmware/rt2661.bin /lib/firmware/rt2870.bin
/lib/firmware/rt2561s.bin /lib/firmware/rt2860.bin
Martin@linux-y0sr:~>
After fiddling around a little bit with the command in the terminal, I managed to install rfkill and run the /usr/sbin/rfkill list command:
Martin@linux-y0sr:~> sudo rpm -i rfkill-0.4-10.1.3.i586.rpm
root's password:
Sorry, try again.
root's password:
Sorry, try again.
root's password:
error: open of rfkill-0.4-10.1.3.i586.rpm failed: No such file or directory
Martin@linux-y0sr:~> sudo rpm -i /home/Documents/rfkill-0.4-10.1.3.i586.rpm
error: open of /home/Documents/rfkill-0.4-10.1.3.i586.rpm failed: No such file or directory
Martin@linux-y0sr:~> sudo rpm -i /home/Martin/Documents/rfkill-0.4-10.1.3.i586.rMartin@linux-y0sr:~> /usr/sbin/rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Martin@linux-y0sr:~>
I’m not sure if there is a kill switch on the card. And even if there was one, I don’t think that it is a problem since I get full internet access on XP without having to change anything on the card.
Once again, thanks for your help and speedy responses. lol!
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Martin@linux-y0sr:~>
> --------------------
>
>
> I’m not sure if there is a kill switch on the card. And even if there
> was one, I don’t think that it is a problem since I get full internet
> access on XP without having to change anything on the card.
I don’t care about XP. I’m never sure it does anything right.
As rfkill does not show any hard or soft blocks, that is not your problem.
As far as I can tell, you only need to configure the card and it should work.
Using YaST => Network Devices => Network Settings, make certain that your
network is controlled by NetworkManager, not by ifup, and complete the
configuration. As I cannot find that you said whether you are using KDE or
Gnome, I cannot be more specific.
At least we can clear that out as the issue. I’m using KDE. I actually did switch it a few times to NetworkManager but could not figure out how to do it. Could you help me configure it? I appreciate your help
On 11/19/2011 10:36 PM, Maht33n wrote:
>
> At least we can clear that out as the issue. I’m using KDE. I actually
> did switch it a few times to NetworkManager but could not figure out
> how to do it. Could you help me configure it? I appreciate your help
I tend not to help with NM configuration problems, but you need to make certain
that NM is running, and then add the plasmoid connection manager applet to your
taskbar if it is not running. At that point use the Connection Manager to
establish the wireless connection.
Yes, I know I’m being vague about the details, but I find that teaching is more
effective when the student has to work a bit to get the answer. Think of it as
the kind of work needed to get Windows 7 to do much of anything!
So after spending a long time looking up NetworkManager and that plasmoid thing, I read in an openSUSE article that I needed to add a widget to the task bar. After doing that, I saw that my home network came up and I connected to it successful. Pssst, this post is actually being written through openSUSE 12.1
:shame:
I really appreciate your support and help throughout this matter! rotfl!
On 11/20/2011 11:06 AM, Maht33n wrote:
>
> lwfinger;2406980 Wrote:
>> On 11/19/2011 10:36 PM, Maht33n wrote:
>>>
>>> At least we can clear that out as the issue. I’m using KDE. I
>> actually
>>> did switch it a few times to NetworkManager but could not figure out
>>> how to do it. Could you help me configure it? I appreciate your help
>>
>>
>> I tend not to help with NM configuration problems, but you need to make
>> certain
>> that NM is running, and then add the plasmoid connection manager applet
>> to your
>> taskbar if it is not running. At that point use the Connection Manager
>> to
>> establish the wireless connection.
>>
>> Yes, I know I’m being vague about the details, but I find that teaching
>> is more
>> effective when the student has to work a bit to get the answer. Think
>> of it as
>> the kind of work needed to get Windows 7 to do much of anything!
>
> So after spending a long time looking up NetworkManager and that
> plasmoid thing, I read in an openSUSE article that I needed to add a
> widget to the task bar. After doing that, I saw that my home network
> came up and I connected to it successful. Pssst, this post is actually
> being written through openSUSE 12.1
> :shame:
> I really appreciate your support and help throughout this matter!
> rotfl!
See how much you learned by researching it yourself, rather than me telling you
to add the plasmoid widget.
