Hey folks,
I want to start off by mentioning that I am a complete noob at Linux. I have used Fedora and Ubuntu in the past but I never had any technical problems with them (once I did with Ubuntu but it was fixed in no time).
Anywho, like the title says, my wireless adapter is not working. And on top of that, I am not near my router so I can’t connect an ethernet to my computer. On top of all that…I am on a desktop computer. So right now I am using Windows to post here.
I would really appreciate a step by step guide, with images if possible, to help me start up my USB and be able to then use the internet.
This is what lsusb shows:
Bus 001 Device 002: ID 1737:0078 Linksys WUSB100 v2 RangePlus Wireless Network Adapter [Ralink RT3070]
I have dabbled with this stuff:
/sbin/modprobe -v rt2800usb
echo "1737 0078" > /sys/bus/usb/drivers/rt2800usb/new_id
I have gone into YAST and changed the settings there to use Network Manager and I have figured out how to show Network Manager in the task bar thingy on the right.
Oh, iwconfig shows the wlan0 interface after I run the above commands but its not connected. After each reboot though it goes away.
Pretty desperate for it to run so please help.
Okay, so I went over to my openSUSE 12.1 install and got more accurate information in hopes that someone can help me fix this problem.
uname -r:
3.1.0-1.2-desktop
lsusb:
Bus 001 Device 004: ID 1737:0078 Linksys WUSB100 v2 RangePlus Wireless Network Adapter [Ralink RT3070]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 002: ID 093a:2622 Pixart Imaging, Inc.
Bus 001 Device 005: ID 0d7d:1920 Phison Electronics Corp.
iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:25:11:8F:F1:E0
UP 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)
Interrupt:42
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8161 (7.9 Kb) TX bytes:8161 (7.9 Kb)
More in the next post.
dmesg:
Couldn’t paste the whole thing here so I have put it up here dmesg for openSUSE 12.1 - Pastebin.com
Oh just wanted to say that I have read about kernel-firmware thing but seeing that I dont have any internet on openSUSE, if there is a way to manually install it, i.e. download here in Windows and then take it to openSUSE and install it there, then I would really appreciate being told about that.
On 03/15/2012 08:46 AM, nickecarlo wrote:
>
> Hey folks,
>
> I want to start off by mentioning that I am a complete noob at Linux. I
> have used Fedora and Ubuntu in the past but I never had any technical
> problems with them (once I did with Ubuntu but it was fixed in no
> time).
>
> Anywho, like the title says, my wireless adapter is not working. And on
> top of that, I am not near my router so I can’t connect an ethernet to
> my computer. On top of all that…I am on a desktop computer. So right
> now I am using Windows to post here.
>
> I would really appreciate a step by step guide, with images if
> possible, to help me start up my USB and be able to then use the
> internet.
>
> This is what lsusb shows:
>
>
> Code:
> --------------------
> Bus 001 Device 002: ID 1737:0078 Linksys WUSB100 v2 RangePlus Wireless Network Adapter [Ralink RT3070]
> --------------------
>
>
> I have dabbled with this stuff:
>
>
> Code:
> --------------------
>
> /sbin/modprobe -v rt2800usb
> echo “1737 0078”> /sys/bus/usb/drivers/rt2800usb/new_id
> --------------------
>
>
> I have gone into YAST and changed the settings there to use Network
> Manager and I have figured out how to show Network Manager in the task
> bar thingy on the right.
>
> Oh, iwconfig shows the wlan0 interface after I run the above commands
> but its not connected. After each reboot though it goes away.
>
> Pretty desperate for it to run so please help.
What version of openSUSE are you using? Based on what you report, it is probably
11.4. If so, you should install the version of compat-wireless for your kernel,
but without a network connection in Linux, this will be difficult. Thus we will
try for a work-around.
The setting of new_id cannot survive a reboot, thus losing wlan0 after a reboot
is expected.
I do not think you have the firmware for the RT3070 installed. The file you
probably need is /lib/firmware/rt2870.bin, but the output of dmesg would show
for certain. The firmware files are contained in the package kernel-firmware,
but again that would be difficult to install without a network connection. Once
we have you running, then you should do that, but in the meantime you can get
all the Ralink firmware files from http://www.lwfinger.com/firmware. Use
whatever network connection you have to download all the files whose name starts
with “rt” and copy them to the directory /lib/firmware on the Linux system. Once
you do that and run the 2 commands above, you should be able to scan with ‘sudo
/usr/sbin/iwlist wlan0 scan’ and configure the connection.
lwfinger,
You are a GENIUS! I am on openSUSE 12.1 and followed your instructions. They worked!
I am assuming that this thing ain’t permanent. I did paste my dmesg on pastebin and have provided the link to it in one of the posts above.
What do I need to do to make this permanent now?
On 03/15/2012 11:46 AM, nickecarlo wrote:
>
> lwfinger,
>
> You are a GENIUS! I am on openSUSE 12.1 and followed your instructions.
> They worked!
>
> I am assuming that this thing ain’t permanent. I did paste my dmesg on
> pastebin and have provided the link to it in one of the posts above.
>
> What do I need to do to make this permanent now?
Your dmesg posting was obviously made before you installed the firmware. With
12.1, you should not need to either manually load the driver or use the new_id
command; however, if you have not updated, the distribution kernel may have been
configured incorrectly - the current one is OK. With your network up, run the
command
sudo zypper up
After this finishes, reboot. Does the network come up now? If not, check to make
sure that rt2800usb is not blacklisted in /etc/modprobe.d/50-blacklist.conf.
Okay,
Its still not working automatically. I mean, its a great improvement from before (I am writing this out of openSUSE) but still doesn’t work automatically. Each time, I gotta do the new_id commands.
After it worked for the first time, this is what I did:
zypper update
zypper in kernel-firmware
Then you told me to do:
sudo zypper up
After all of this and rebooting, it still didn’t work automatically. Here’s the dmesg file after I rebooted but before I put the new_id commands: dmesg v.2 openSUSE 12.1 - Pastebin.com
I wanted to put up the dmesg output after I connected to the network as well, but I don’t know how safe it is to put it out in public since it contains my network information (or I think it does).
Oh also the blacklist file does not contain anything related to RaLink, I didn’t see any rt drivers there.
On 03/15/2012 03:16 PM, nickecarlo wrote:
>
> Okay,
>
> Its still not working automatically. I mean, its a great improvement
> from before (I am writing this out of openSUSE) but still doesn’t work
> automatically. Each time, I gotta do the new_id commands.
>
> After it worked for the first time, this is what I did:
>
>
> Code:
> --------------------
> zypper update
>
> zypper in kernel-firmware
> --------------------
>
>
> Then you told me to do:
>
>
> Code:
> --------------------
> sudo zypper up
> --------------------
>
>
> After all of this and rebooting, it still didn’t work automatically.
> Here’s the dmesg file after I rebooted but before I put the new_id
> commands: ‘dmesg v.2 openSUSE 12.1 - Pastebin.com’
> (http://pastebin.com/XQuP1Y3Y)
>
> I wanted to put up the dmesg output after I connected to the network as
> well, but I don’t know how safe it is to put it out in public since it
> contains my network information (or I think it does).
>
> Oh also the blacklist file does not contain anything related to RaLink,
> I didn’t see any rt drivers there.
The only thing that gets listed in the dmesg output is the MAC address of the
AP. Your ESSID and keys/secrets are not.
The only thing that comes to mind to explain the problem is that your USB
subsystem and/or udev are not working correctly. I can see the system detect
your device, but it does not try to load the driver the way it should.
As root, edit /etc/init.d/boot.local and add the following two lines:
/sbin/modprobe rt2800usb
echo "1737 0078" > /sys/bus/usb/drivers/rt2800usb/new_id
After these changes, the device will come up running every time you reboot.
Thank you! That did the trick. Do you want me to post my dmesg now? Would that tell us what’s wrong with my USB subsystems or udev (I have no idea what that is)? Or is it normal for that stuff to be screwed up at times?
On 03/15/2012 04:16 PM, nickecarlo wrote:
>
> Thank you! That did the trick. Do you want me to post my dmesg now?
> Would that tell us what’s wrong with my USB subsystems or udev (I have
> no idea what that is)? Or is it normal for that stuff to be screwed up
> at times?
No on posting dmesg. It does not matter. I have no interest in debugging the
underlying problem. The udev code is the part that initiates loading of the
driver that services a particular USB or PCI ID, and also reacts to the firmware
loading calls by the driver. In addition, udev handles device naming and a few
other things.
One of the ways this sort of thing pops up when your hardware is peculiar and
needs some special quirk in the standard driver to make it work. These kind of
things are quite rare, particularly when a driver is as old as 3.1.9. In the rc
phase of a new kernel, they happen all the time, but are usually fixed as soon
as they are found.
Well, thanks a lot for helping me out with this. It works flawlessly now. I don’t know what the problem is but after 48 hours of worrying about the wireless I think I will enjoy it for now. I have installed Ubuntu 11.10, Mint 12, Fedora 16 and now openSUSE 12.1 all in the last two weeks. Hoping to, now, stick with openSUSE. It seems a lot more mature and stable than the rest of them.
Thanks again.