When I switched to 11.0 I got the problem with my wireless card.
I am using D-Link DWL-G122 ver B1 usb dongle (kernel module: rt2500usb)
I use WPA-PSK encryption in my network
Everything worked well on 10.3 out of the box, but on 11.0 i got some problems.
First of all, I can scan for wireless networks and connect to them (via updated knetworkmanager). But when it comes to usage - the behavior is rather starnge. Here is an output of ping command. This is a single output (not a mix of different ones)
kolyanoid@linuxclient:~> ping 192.168.100.100
PING 192.168.100.100 (192.168.100.100) 56(84) bytes of data.
From 192.168.100.107 icmp_seq=1 Destination Host Unreachable
From 192.168.100.107 icmp_seq=2 Destination Host Unreachable
From 192.168.100.107 icmp_seq=4 Destination Host Unreachable
From 192.168.100.107 icmp_seq=5 Destination Host Unreachable
64 bytes from 192.168.100.100: icmp_seq=6 ttl=64 time=6.97 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
64 bytes from 192.168.100.100: icmp_seq=28 ttl=64 time=1003 ms
64 bytes from 192.168.100.100: icmp_seq=29 ttl=64 time=3.83 ms
64 bytes from 192.168.100.100: icmp_seq=30 ttl=64 time=1.04 ms
As you can see, it is pretty weird.
I tried using both - yast configuration and knetworkmanager.
I dont, actually, have opportunity to check other encryption methods, rather than wpa-psk.
The question is - what’s the reason for that? And how shall I make my D’link dongle work in my network?
P.S.
The network is working OK. The 192.168.100.100 - is 100% reachable from other PCs (it is my personal gateway\server)
the Dlink dongle connects to my AP router (not PC)
Tried installing ralink-firmware and rt2500-cvs-kmp-default packages, but with them the usb dongle did not work - no indication lights worked (but I could scan the air for wireless lan, as far as I remember).
Kolyanoid wrote:
> Thanks for reply!
>
> As I mentioned, this is a USB dongle. Here is the output for
> /usr/sbin/lsusb
>
>
> Code:
> --------------------
> linuxclient:/home/kolyanoid # /usr/sbin/lsusb -s 007:006 -v
>
> Bus 007 Device 006: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. B1 [ralink]
Your device is handled by rt2500usb.ko, but that driver is not found in the
2.6.25.5… kernel that came on the CD and/or DVD. It is in the 2.6.25.9…
kernel. You need to upgrade the kernel using YaST’s “Online Upgrade”. For me,
the automatic upgrade did not install the new kernel. After you upgrade and
reboot, you should be able to configure your wifi.
As I mentioned before, I can scan for wireless networks and even connect to them.
I set some “experiments” on it and found out, that my wifi works more stable when I get the my D’link dongle closer to the AP. In terms of wifi the change is not significant. Usually I use it on distance of 4 meters from the AP (AP is behind a single wall). I moved it to 3 meters and the things got better (strange). The knetworkmanager started to show almost 100% signal. When it is so, the connection works OK - I can access the internet and intranet.
From 4 meter distance the signal is shown as approx. 50% strength. In this case the connection is absolutely unstable. Here is another ping output:
kolyanoid@linuxclient:~> ping 192.168.100.100
PING 192.168.100.100 (192.168.100.100) 56(84) bytes of data.
From 192.168.100.106: icmp_seq=1 Destination Host Unreachable
From 192.168.100.106 icmp_seq=1 Destination Host Unreachable
From 192.168.100.106 icmp_seq=2 Destination Host Unreachable
From 192.168.100.106 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.100.100: icmp_seq=4 ttl=64 time=8.83 ms
64 bytes from 192.168.100.100: icmp_seq=5 ttl=64 time=1.37 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
^C
--- 192.168.100.100 ping statistics ---
50 packets transmitted, 2 received, +4 errors, 96% packet loss, time 68164ms
rtt min/avg/max/mdev = 1.375/5.102/8.830/3.728 ms, pipe 3
The kernel update has not not changed a thing. To tell uou the truth, I got this problem since the first OpenSUSE 11 betas were released.
Again, in 10.3 everything works fine!
And there was no problem in configuration - I always could configure with yast or knetworkmanager. Yast always suggested the rt2500usb kernel module for this device, which is OK. That did not depend on kernel version.
PS.
I don’t want to use ndiswrapper, if there is some other better way…
I used it on 10.0 - there was no other way…
Kolyanoid schrieb:
> No, this didn’t work…
>
> As I mentioned before, I can scan for wireless networks and even
> connect to them.
Trouble is your original post doesn’t show up in this group
(opensuse.org.help.network-internet.wireless). The thread starts
here only with your posting dated Sat, 12 Jul 2008 12:56:03 GMT.
Looks like your previous postings went somewhere else, so the
readers of this group cannot know what you mentioned in them.
Perhaps it would be best to re-post that information.
That’s pretty strange, as I see it with no problems… Anyway, here it is reposted:
When I switched to 11.0 I got the problem with my wireless card.
I am using D-Link DWL-G122 ver B1 usb dongle (kernel module: rt2500usb)
I use WPA-PSK encryption in my network
Everything worked well on 10.3 out of the box, but on 11.0 i got some problems.
First of all, I can scan for wireless networks and connect to them (via updated knetworkmanager). But when it comes to usage - the behavior is rather starnge. Here is an output of ping command. This is a single output (not a mix of different ones)
kolyanoid@linuxclient:~> ping 192.168.100.100
PING 192.168.100.100 (192.168.100.100) 56(84) bytes of data.
From 192.168.100.107 icmp_seq=1 Destination Host Unreachable
From 192.168.100.107 icmp_seq=2 Destination Host Unreachable
From 192.168.100.107 icmp_seq=4 Destination Host Unreachable
From 192.168.100.107 icmp_seq=5 Destination Host Unreachable
64 bytes from 192.168.100.100: icmp_seq=6 ttl=64 time=6.97 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
64 bytes from 192.168.100.100: icmp_seq=28 ttl=64 time=1003 ms
64 bytes from 192.168.100.100: icmp_seq=29 ttl=64 time=3.83 ms
64 bytes from 192.168.100.100: icmp_seq=30 ttl=64 time=1.04 ms
As you can see, it is pretty weird.
I tried using both - yast configuration and knetworkmanager.
I dont, actually, have opportunity to check other encryption methods, rather than wpa-psk.
The question is - what’s the reason for that? And how shall I make my D’link dongle work in my network?
P.S.
The network is working OK. The 192.168.100.100 - is 100% reachable from other PCs (it is my personal gateway\server)
the Dlink dongle connects to my AP router (not PC)
Tried installing ralink-firmware and rt2500-cvs-kmp-default packages, but with them the usb dongle did not work - no indication lights worked (but I could scan the air for wireless lan, as far as I remember).
Wireless support (at least as far as cards with rt2500 and rt61 chipsets) is totally broken in OpenSUSE 11.0 and just about every other distro using kernel versions newer than 2.6.22. The move to a “new” wireless driver infrastructure was an absolute disaster, but the upstream Linux kernel maintainers are unwilling to admit it and fix their mistake. Until they do so, I’m sticking with 10.3 (and its 2.6.22 kernel that actually WORKS)
rt2x00 is horribly broken in 2.6.25,26 and from reading the kernel changelogs the fixes have not yet been merged into the 2.6.27 kernel. I agree that rt2500 under 10.3 was/is great with both ndiswrapper & native support.
A mostly working setup for me involves ndiswrapper and the rt2500 drivers from ralink along with wicd managing the wireless connection. However, associating with the access point using WPA is not reliable (again all of this was under 10.3). To combat this I have wicd run a script which does
during the pre-connect phase. With this I get about a 60-70% success rate at associating on a given attempt. Additionally, the ndis driver seems to do a good job tuning the link - much better than my previous experience with the linux native driver which would bounce link rate up and down freqently.
Latest updates have fixed wireless … among other things. Anyone still having problems with wireless it would be related to their particular wireless brand and not with with any problems in KDE 4.1.1 or older. If you are using “unstable” repos to get the latest snapshots of KDE4.1.1 (alpha) I can’t vouch for a working internet connection.
I am using a linksys WPC54G.v3.
Here is my sbin readout:
03:00.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)
Subsystem: Linksys WPC54G-EU version 3 [Wireless-G Notebook Adapter][1737:0048]
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at 3c000000 (32-bit, non-prefetchable) [size=8]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Am fully updated on the online updates.
Have tried ndiswrapper install. no luck
Have tried madwifi install, simply to cover the basis. no luck.
I need wifi on this machine, but its not working, please advise.
You need to install the firmware if you haven’t. Check the stickies at the start of the wireless section for instructions for b43. BTW, you would have been better starting your own topic instead of tacking on the end of someone else’s,it might have been noticed sooner
do you not have a wired connection ? if not, before you perform the commands,ensure you have the kernel sources,gcc/gcc++ & make installed. All can be found on the dvd. If you do have a wired connection & if you have a broadcom chip-set,this command, in a console, may help
bmccall17 wrote:
> I tried to install the firmware, but got this error during the sudo
> command:
> “sudo: ./bcm43xx-fwcutter-006/bcm43xx-fwcutter: command not found”
>
> also previously, the “make” command did nothing after i was in the cd
> bcm43xx-fwcutter-006 directory.
You missed one very important part of the sticky message. OpenSUSE
11.0 already has fwcutter installed. There is no reason to build it.
Instead, open a terminal and enter the following command:
sudo /usr/sbin/install_bcm43xx_firmware
For the above command to work, you need Internet access while in
Linux. If you do not, then reread the sticky entitled “Additional
Wireless Bits”. It will tell you the workaround.
bmccall17 wrote:
> this worked magically!
> thank you everyone. wished i had caught that sticky ahead of time.
>
> again, thank you.
> next on the list, WINE!!
If wine gives you a problem, an alternative for running Windows
programs is to use VirtualBox and your Windows distribution to create
a virtual machine running XP, or whatever you need. I use two Windows
programs - a cookbook and TurboTax. Both work well in the VM.
