I just went to SUSE studio and made my own OS. I’m delighted! But when I was loading what I wanted, I was careful to load wireless. Problem was I overlooked loading anything pertaining to usb! I’m using a usb belkin wireless, but nothing shows up in wireless. Even worse, when I run lsusb, it comes back command not found! How can I get my system to recognize usb?
Sounds like you need at least the usbutils package installed.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Hey,that worked. Thanks!
Now to find out why network connections doesn’t show anything in wireless. lsusb now shows it, though, so I guess it’s time to read the sticky at the top of the page. Thanks again.
I’m doing RTFM. Yast showed the belkin in hardware, but wireless doesn’t see it. I ran iwconfig and got:
linux-mttm:/home/pottzie # iwconfig
lo no wireless extensions.
irda0 no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Looks like wlan knows it's there. What am I missing?
Tried rebooting thinking that udev would pick it up, but no such luck. Shouldn’t hal kick in and see the usb? Assuming that hal and udev are onboard, that is.
Is wlan0 for your Belkin wireless device? If so, have you tried configuring your wireless device with
YaST > Network Devices > Network Settings
assuming you’re are using the traditional “ifup” method. If you’re using Network Manager, then choose ‘New Connection’ and configure from there. Read the wireless sticky for a guide:
That made a little headway. Network Settings said that everything was controlled by the network connections and I had to change to ifup to let Network Settings run. I did, and got “need to download firmware from the manufacturer.”
Problem is that every distro I have has recognised this belkin! I’ve run into big problems before getting drivers that wound up duelling with conflicting drivers, and I know that this wireless unit works with almost any kernel since Eisenhower was president. I’m real reluctant to go firmware hunting for something that’s probably already there. Then again, that’s what it said. At least Network Settings saw it, unlike Network Manager.
When I ran ifup I no longer could connect through the ehternet hard wire connection, so I changed back to Network Manager.
Two things that may affect this. I built this setup from SUSE Studio. All I wanted was internet, so all I loaded was gnome and everything that I thought was needed as far as wireless, ethernet, and after getting this up, even dial up, since that’s all we have at the shop.
The second detail is that this is running on an old Thinkpad, an a22 from around 2000 or so. It had Vector linux on it, and the wireless belkin worked with Vector. And as I said, I’ve used this belkin with several distros without any problem. I think the answer is going to be somewhere in the software repositories, but how can I check the firmware issue out?
I ran dmesg | less. All I saw was
5.054864] usb 1-1: New USB device found, idVendor=050d, idProduct=705a
5.054880] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
5.054890] usb 1-1: Product: Belkin 54g USB Network Adapter
5.054899] usb 1-1: Manufacturer: Belkin
5.055247] usb 1-1: configuration #1 chosen from 1 choice
5.491341] PM: Marking nosave pages: 0000000000002000 - 0000000000006000
5.491368] PM: Marking nosave pages: 000000000009f000 - 0000000000100000
5.491380] PM: Basic memory bitmaps created
5.516194] PM: Basic memory bitmaps freed
5.644307] PM: Starting manual resume from disk
5.644326] PM: Resume from partition 8:1
5.644332] PM: Checking hibernation image.
5.660627] PM: Resume from disk failed.
5.983896] EXT4-fs (sda2): barriers enabled
6.013840] kjournald2 starting: pid 209, dev sda2:8, commit interval 5 seconds
That last part probably doesn’t have anything to do with the belkin. wlan didn’t show up anywhere as far as I know.
Hey. What’s this?
15.460222] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
15.460377] usbcore: registered new interface driver rt2500usb
dmesg | grep firmware :
44.502582] rt73usb 1-1:1.0: firmware: requesting rt73.bin
44.553328] phy1 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
Problem is that when I Google rt73usb it directs to firmware…just not firmware for a belkin!
rt73usb - Linux Wireless
It shows Linksys and D-Link as well as a few others, but not a belkin. Dunno. Decisions, decisions.
I’m not familiar with Belkin devices, but they can contain a variety of chipsets (as with many wireless/network devices). I found this reference:
Using the Belkin USB Wireless G key under Linux
which outlines the use of open source and windows (with ndiswrapper) drivers.
Another useful HCL reference:
HCL/Network Adapters (Wireless) - openSUSE
Anyway, back on topic, do you have the ralink-firmware package installed? If not you can find the repo with Webpin like I did. (Make sure you search for the relevant openSUSE version though).
lsmod shows;
rt2500usb 23524 0
The “0” is in the column:“used by.”
Some of the documentation I’ve read suggests using modprobe. Wikipedia says udev relies on modprobe. Doesn’t that mean that modprobe already runs at start up?
I put “modprobe” in the terminal, but all it returned was a guide/instruction output, not information about what I’ve got onboard.
Diging a little more, ‘modprobe usb’ came back “fatal.Module usb not found.”
The second link has something about “ralink-firmware’ package required -> auto installed by YaST.” Is that something I need to do manualy, or is it done automatically? If it was supposed to be automatic, something that was supposed to happen didn’t. As I said, this unit worked straight out of the box with several distros, including opensuse 11.2
Some of the documentation I’ve read suggests using modprobe. Wikipedia says udev relies on modprobe. Doesn’t that mean that modprobe already runs at start up?
I put “modprobe” in the terminal, but all it returned was a guide/instruction output, not information about what I’ve got onboard.
Diging a little more, ‘modprobe usb’ came back “fatal.Module usb not found.”
You seem to be a bit confused. The modprobe command is used to load/unload drivers. If the driver for your hardware is present, then any yast configuration will make sure it gets loaded at boot, or via network manager etc. If lsmod shows that the driver module is loaded, you don’t need to load it manually, or otherwise.
The second link has something about “ralink-firmware’ package required -> auto installed by YaST.” Is that something I need to do manualy, or is it done automatically? If it was supposed to be automatic, something that was supposed to happen didn’t. As I said, this unit worked straight out of the box with several distros, including opensuse 11.2
Just check that the your software manager shows that it is still installed. Search for ‘ralink-firmaware’.
First, from the hardware manager, “Way too much” information:
Hmm. Tried to copy from hardware information only to find that I can’t. Tried to save as a file without success either.
It shows a belkin 54usb network adapter,driver rt73usb, with module(s) rt2500usb. Active:yes, modprobe:yes.Kernel driver rt73usb, old unique key and parent unique ID, HW address, Wireless lan authorized modes (open, sharedkey), then at the bottom system ID and belkin info.
I’m going to have to figure out how to check the software manager (gotta find it!) to see about ralink firmware. Install software didn’t have it. Where is the software manager at? Or can I do it in the terminal?
Software Manager doesn’t show or list “ralink firmware.”
Command line?
I think I got it! I’m online wirelessly typing this! I don’t know if it was the link deano_ferrari posted or RPM Search OpenSuSE ralink-firmware-1.0-25.1.noarch.rpm as I downloaded from both. took my newbie self a lot of mucking with the downloads to figure how to get something to open (you know how hard ‘point,click’ gets. No, really…)
Had to go back in to yast and rerun network settings a few times. May have bolixed the ethernet hard wire too, as I don’t know if it works as well as the wireless, seems that network settings and network manager can’t both rule the roost. I had to go to ifup, but I also rebooted, so I don’t know if network manager still worked from that or not after the reboot.
Thanks everyone.
Well, you got there in the end. Thats what counts.