Bad wifi connexion on F10 X86_64 (wifi chipset wg111v2, and module rtl8187)

ouafnico · #1 28th November 2008, 04:17 PM

Hi all

I've got some troubles with wifi chipset wg111v2, and module rtl8187. In all distributions linux it doesn't work, like F10. The signal is very low, works some seconds and fall out.

What can I do ?

ouafnico · #2 30th November 2008, 10:16 AM

nobody knows ?

54tu5qu0 · #3 6th December 2008, 05:25 PM

I have same slow networking with my Intel Pro/Wireless. I used to have 2-300 KB/s under windows XP. Now I'm down to 20-30. Any help here would be greatly appreciated. I'm a Fedora/Linux noob and need some help making light of problems. I'd appreciate all tips ,tricks, and how-to's. My AOL and Yahoo ID are posted under my profile along with my e-mail. (If I can get any of those to work with this slow or no networking issue) Thanks in advance for anyone's insight!!!

scottro · #4 6th December 2008, 06:58 PM

I've edited the title. With a subject like that, there's an excellent chance that whoever does know just overlooked the thread. People do get busy and with the increased amount of posts due to the release of F10, the more descriptive the subject line, the better.

Unfortunately, I can't help with that particular model, but with the changed title, you have a much better chance of getting help.

alextc · #5 21st January 2010, 01:06 AM

it seems that almost all of the wifi owners have the same problem!
I have the same problem

bbfuller · #6 21st January 2010, 11:10 AM

Hello alextc

Have you the same chipset in your card as the original poster?

Have you considered trying ndiswrapper?

alextc · #7 22nd January 2010, 04:15 AM

Yes i have the same cipset, but i don't know how to use ndiswrapper

bbfuller · #8 22nd January 2010, 07:26 AM

Hello alextc

A quick look on the forum doesn't really show anyone getting your chipset working well, if at all. That might mean ndiswrapper won't work wither.

Try these notes for ndiswrapper. They assume you have an internet connection to the Fedora installation though. If you haven't got that, post back and I'll put up the notes for getting the parts and transferring them.

Quote:

Code:

uname -r

to find your running kernel. That will either be PAE or not.

then:

Code:

su -

That's a space and a minus sign after the su. It gives full root rights over the machine, not just over your own environment which is what you get with plain su.

If you haven't already, install the rpmfusion repositories:

Code:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

Install ndiswrapper:

Code:

yum install kmod-ndiswrapper

or:

Code:

yum install kmod-ndiswrapper-PAE

depending on which kernel you discovered.

This should bring in the three relevant packages.

Then set up and configure ndiswrapper with:

Code:

ndiswrapper -i <path to your windows driver file>.inf

should install the driver,

Code:

ndiswrapper -l

if it is going to work should return "driver present" and "hardware present"

Code:

modprobe ndiswrapper

should load the driver into the kernel, but probably only until you reboot.

If you are lucky now and NetworkManager is running then after a short while it 'may' begin reporting wireless networks. NetworkManager is the preferred method of connecting to wireless networks with Fedora and should be located in the notification area of either KDE or Gnome just to the lefto of the clock.

If it works, or indeed if it doesn't you will also need to run:

Code:

ndiswrapper -mi

to ensure the ndiswrapper module loads each time of booting.

Please remember that ndiswrapper is only happy with Windows XP/98 drivers and doesn't get on with Windows Vista drivers. Of those it doesn't happily co-exist with all XP/98 drivers either. Be prepared to experiment if your original doesn't work.

I'm just off out for the rest of the day. I'll look for your results with interest in about10 hours.

MarcoP · #9 22nd January 2010, 09:32 AM

I've installed ndiswrapper step by step ^^^^ and had a weird problem "forcing 256 to 32" or something similar.

Code:

net5211 : driver installed
	device (168C:0013) present (alternate driver: ath5k)

At this stage wireless it's not working and lshw say that the hardware hasn't be claimed. Any idea?

EDIT:

Code:

cat /var/log/boot.log | grep loadndisdriver
loadndisdriver: load_driver(358): couldn't load driver net5211

32bits drivers for a 32bits wireless card on a 64bits arch?

alextc · #10 22nd January 2010, 04:27 PM

When i: ndiswrapper -l
i get this:

Code:

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
netrtuw : driver installed
	device (0BDA:8187) present (alternate driver: rtl8187)
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
netrtuw_x64 : driver installed
	device (0BDA:8187) present (alternate driver: rtl8187)

JEO · #11 22nd January 2010, 05:19 PM

The explanation for that is that ndiswrapper is not putting the .conf on the end of the filename it creates in /etc/modprobe.d. To get rid of the warning just rename the file so it has a .conf after the name, and you will have to do this each time you use the ndiswrapper command to change it.

alextc · #12 22nd January 2010, 05:29 PM

well i tryed to rename, but after a restart my fedora dose not starts up anymore...

PS: Check out the atachament

JEO · #13 22nd January 2010, 05:35 PM

I've never seen such a problem booting, but try booting from an installation media in rescue mode and look at what is in the file /etc/modprobe.conf and maybe rename that file and see if that fixes it.

alextc · #14 22nd January 2010, 05:39 PM

yes i will try to do that with a live fedora on stick

JEO · #15 22nd January 2010, 06:11 PM

also did you add a line to /etc/modprobe.d/blacklist.conf like:

blacklist rtl8187

That might help also, in case both drivers are trying to load.

---------- Post added at 10:11 AM CST ---------- Previous post was at 09:40 AM CST ----------

If it still won't boot, delete the ndiswrapper.conf file in /etc/modprobe.d