Ok I have a Belkin or as I like to call it a belchin lol, but anyways I have a Belkin Wireless G USB adapter its code it F5D7050 and it wont work with KDE openSUSE my brother spent 2 hours trying to fix the problem…
We tried Ndiswrapper with the correct driver and when we tried to use that module it wouldnt display any networks…
Using the Default module it could see networks and connect to them but when we launched a browser it wouldnt connect.
Any help would be great…
Please go to the wireless subforum and read the 3 stickies at the
beginning of that section. You will learn how to report the
information that we need to tell you how to get your device running.
Incidentally, we do not suggest the usage of ndiswrapper and the
Windows driver until all other options are exhausted.
Ok this is beginning to get stupid! on the Ubuntu forums you dont get answers like:
DONT POST THINGS SAYING LIKE I NEED HELP THIS WONT WORK!
OK WAIT I posted in the forum in the first place is to say I need help… Not to have to read a 300 or more line doc before I can post I need answers FAST!
Im not just installing SUSE for enjoyment I WILL GET FIRED IF I CANT GET THIS WORKING!!!
I have a job I cant read a 300 line document…
Ok, thanks for the quick reply.
I saw the info on that page you were talking about it said that yast worked out of the box with my adapter with openSUSE 11.1, I use SUSE 11.1 so it should work right?
Any way the info you wanted from yast:
model: F5D7050 v5012
chipset/driver: rtl8187
I have never used a USB Wireless device. But if in Yast you switch to Network Manager for managing the network, how do you get on configuring the connection from the NetworkManager in the tray?
You’ll need to scan for a new access point
Setup the SSID and network security WPA key…etc…
On 11/04/2009 11:26 PM, javageek1212 wrote:
>
> Ok, thanks for the quick reply.
> I saw the info on that page you were talking about it said that yast
> worked out of the box with my adapter with openSUSE 11.1, I use SUSE
> 11.1 so it should work right?
>
> Any way the info you wanted from yast:
> model: F5D7050 v5012
> chipset/driver: rtl8187
Thank you caf9246 for the endorsement. I don’t want to pat myself on
the back too hard, but I am also one of the authors of the rtl8187 driver!
That device WILL work. It doesn’t need external firmware or any
other fancy stuff; however, it will work better with the
compat-wireless package for your kernel than it will with the standard
2.6.27 kernel of 11.1. If you do not want to install that package,
then you might consider getting 11.2, either the current RC2, which is
very stable, or the final release when it comes out.
See how much information you get when you finally tell us which device
you really have?
javageek1212 wrote:
> I am running Windows as a dual boot until this is fixed. So what is
> your evil plan?
My evil plan is to get you to do what you should have done in the first place!
With the standard 11.1 kernel, the rtl8187 driver works! You need to unload any
Windows drivers that are installed using ndiswrapper, and then uninstall
ndiswrapper. If you blacklisted anything, you need to remove that as well. You
probably did not, but just in case.
Check that rtl8187 is in fact loaded by opening a terminal and entering the
command ‘lsmod | grep rtl’. You should see several lines of output with the
first one starting with rtl8187.
Next, issue the command ‘sudo /usr/sbin/iwlist scan’. It should show scan data
for your AP.
Finally, click on the NetworkManager applet in the lower right-hand corner of
the screen. Click on “New Connection” and select your wireless interface. Fill
in the data on ALL screens until the “Next” button is not illuminated, then
you should select the “Connect and Save” entry. Be sure to select the
“Autoconnect” box on the last screen.
In all you complaining about how much we made you read, you never gave even the
barest details about your setup, so I have to shoot in the dark. If your AP uses
WEP, be sure to enter the Hex Key. Using a passphrase is unlikely to work. As
you do not like to read, I won’t burden you with the reason!
I used YaST to configure as well as the