Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
Chris Rees wrote: 2009/2/25 Paul B. Mahol : On 2/24/09, SDH Support wrote: I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt handling: I've been able to get /most/ wireless cards working with ndiswrapper. *BSD doesnt have ndiswrapper. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Yeah it does... [ch...@amnesiac]~% ndisgen == -- Windows(r) driver converter --- == This script is designed to guide you through the process of converting a Windows(r) binary driver module and .INF specification file into a FreeBSD ELF kernel module for use with the NDIS compatibility system. The following options are available: 1] Learn about the NDIS compatibility system 2] Convert individual firmware files 3] Convert driver 4] Exit Enter your selection here and press return: "ndiswrapper" refers to the linux version of the Bill Paul's project for freebsd. They are very different; though have the same goal. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
> On 2/24/09, SDH Support wrote: >> >>> I tried using my ath based D-Link DWL G650, which still seems to have >>> some issues in regard to interrupt handling: >> >> >> I've been able to get /most/ wireless cards working with ndiswrapper. > > *BSD doesnt have ndiswrapper. There is the ndis driver in FreeBSD. I've used a lot ndis with an Intel 2200 BG card. iwi was not reliable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
2009/2/25 Christian Walther : > 2009/2/24 SDH Support : >> >>> I tried using my ath based D-Link DWL G650, which still seems to have >>> some issues in regard to interrupt handling: >> >> >> I've been able to get /most/ wireless cards working with ndiswrapper. >> > This is just my personal opinion, and I tend to make scarce use of the > word "hate" - but in this case: I really hate ndiswrapper. > It might be suitable for some people, but I rather get some piece > hardware that is properly supported. Bugs are bad luck, of course, as > well as a kernel module author who stops working. But at least I don't > have to rely on a windows driver. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > True, but ndiswrapper for me was an epiphany of the incredible things free software can do. I found it right back in Debian Woody, where my Ralink card wasn't supported. I got sick of Linux and moved to BSD, where the ral driver was instantly recognised and loaded. -- R< $&h ! > $- ! $+ $@ $2 < @ $1 .UUCP. > (sendmail.cf) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
2009/2/25 Paul B. Mahol : > On 2/24/09, SDH Support wrote: >> >>> I tried using my ath based D-Link DWL G650, which still seems to have >>> some issues in regard to interrupt handling: >> >> >> I've been able to get /most/ wireless cards working with ndiswrapper. > > *BSD doesnt have ndiswrapper. > > > -- > Paul > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > Yeah it does... [ch...@amnesiac]~% ndisgen == -- Windows(r) driver converter --- == This script is designed to guide you through the process of converting a Windows(r) binary driver module and .INF specification file into a FreeBSD ELF kernel module for use with the NDIS compatibility system. The following options are available: 1] Learn about the NDIS compatibility system 2] Convert individual firmware files 3] Convert driver 4] Exit Enter your selection here and press return: -- R< $&h ! > $- ! $+ $@ $2 < @ $1 .UUCP. > (sendmail.cf) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
2009/2/24 SDH Support : > >> I tried using my ath based D-Link DWL G650, which still seems to have >> some issues in regard to interrupt handling: > > > I've been able to get /most/ wireless cards working with ndiswrapper. > This is just my personal opinion, and I tend to make scarce use of the word "hate" - but in this case: I really hate ndiswrapper. It might be suitable for some people, but I rather get some piece hardware that is properly supported. Bugs are bad luck, of course, as well as a kernel module author who stops working. But at least I don't have to rely on a windows driver. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
On Wed, Feb 25, 2009 at 8:26 AM, Paul B. Mahol wrote: > On 2/24/09, SDH Support wrote: >> >>> I tried using my ath based D-Link DWL G650, which still seems to have >>> some issues in regard to interrupt handling: >> >> >> I've been able to get /most/ wireless cards working with ndiswrapper. > > *BSD doesnt have ndiswrapper. Yes, it does: http://www.freebsd.org/cgi/man.cgi?query=ndis&manpath=FreeBSD+7.1-RELEASE -- My preferred quotation of Robert Louis Stevenson is "You cannot make an omelette without breaking eggs". Not because I like the omelettes, but because I like the sound of eggs being broken. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
On 2/24/09, SDH Support wrote: > >> I tried using my ath based D-Link DWL G650, which still seems to have >> some issues in regard to interrupt handling: > > > I've been able to get /most/ wireless cards working with ndiswrapper. *BSD doesnt have ndiswrapper. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
> I tried using my ath based D-Link DWL G650, which still seems to have > some issues in regard to interrupt handling: I've been able to get /most/ wireless cards working with ndiswrapper. --- Kevin www.stardothosting.com/linux-vps-hosting ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
Hi Kevin, lets say it this way: Right now the DWL-G650 works. I'm not sure why, but I did reset the BIOS configurations to its default and started manually configuration some of the used interrupts. This is why the snippets of the logfiles I sent in my previous mail don't match the current configuration. Currently, the card uses irq 5 as supplied by cbb0. The last messages I received concerning the issue were: Feb 23 19:43:52 hasking kernel: interrupt storm detected on "irq5:"; throttling interrupt source Feb 23 19:43:53 hasking kernel: interrupt storm detected on "irq5:"; throttling interrupt source Feb 23 19:43:54 hasking kernel: ath0: link state changed to UP Feb 23 19:43:54 hasking kernel: ath0: link state changed to DOWN Feb 23 19:43:58 hasking kernel: ath0: link state changed to UP Feb 23 19:43:58 hasking kernel: ath0: link state changed to DOWN Feb 23 19:44:03 hasking kernel: ath0: link state changed to UP Feb 23 19:44:03 hasking kernel: ath0: link state changed to DOWN Feb 23 19:44:05 hasking kernel: interrupt storm detected on "irq5:"; throttling interrupt source Feb 23 19:44:05 hasking kernel: ath0: link state changed to UP Feb 23 19:44:05 hasking kernel: ath0: link state changed to DOWN Feb 23 19:44:09 hasking kernel: ath0: rx FIFO overrun; resetting Feb 23 19:44:20 hasking kernel: ath0: link state changed to UP This has actually been the last time that I've seen those errors. I even transferred a PCBSD DVD iso image to my server using FTP. I guess I made two mistakes during my entire testing phase: 1. I wrongly assumed that the issue with the ath card was the same as the one I experienced some time ago, including some HAL issue locking the card, interrupt storms during usage and crashes on removal of the card. 2. After I did the BIOS reset I obviously just tested my iwi card. While there are still some interrupt storm related messages, they seem to appear during boot (HW init) only. Kevin, thank you for your input, which made me review the issue again. The only problem that remains is that my machine crashes when I remove the card. I'll review this later. Thanks again for your help, I'm happy that I can use this card as expected, and that I don't need to get another one. Regards Christian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
> Date: Mon, 23 Feb 2009 16:21:17 +0100 > From: Christian Walther > Sender: owner-freebsd-sta...@freebsd.org > > Hi, > > after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 > (with ZFS root on encrypted geli, works great). > Config is: > > FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu > Feb 5 21:10:45 CET 2009 > r...@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 > > I tried using my ath based D-Link DWL G650, which still seems to have > some issues in regard to interrupt handling: > > Feb 17 20:15:21 hasking kernel: ath0: mem > 0xd021-0xd021 irq 3 at device 0.0 on cardbus0 > Feb 17 20:15:21 hasking kernel: ath0: [ITHREAD] > Feb 17 20:15:21 hasking kernel: ath0: WARNING: using obsoleted > if_watchdog interface > Feb 17 20:15:21 hasking kernel: ath0: Ethernet address: 00:19:5b:3a:82:be > Feb 17 20:15:21 hasking kernel: ath0: mac 7.9 phy 4.5 radio 5.6 > ... > Feb 17 21:39:19 hasking kernel: ath0: link state changed to UP > Feb 17 21:39:19 hasking kernel: ath0: link state changed to DOWN > Feb 17 21:39:23 hasking kernel: ath0: link state changed to UP > Feb 17 21:39:23 hasking kernel: ath0: link state changed to DOWN > Feb 17 21:39:24 hasking kernel: interrupt storm detected on "irq3:"; > throttling interrupt source > > > Next I gave the following card a try: > iwi0: mem 0xd020-0xd0200fff irq 5 > at device 2.0 on pci2 > iwi0: Ethernet address: 00:15:00:31:f3:76 > iwi0: [ITHREAD] > > ...and it regularly drops/looses connection to the WLAN router, as > stated in the following PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=124767 > > Basically, my question is if there is a fix for any of these issues > that I haven't found so far, so that I can eventually use one of my > existing wireless cards, or if I should switch to a different > brand/model. If the latter is the case I'd like to know which one to > choose. I'm not sure what the problem you are seeing with the Atheros 5212 might be, but I use that wireless card in my T43 and it has worked very well for years. I'm not sure what is using irq3, but it is normally COMM2, which i believe only exists on the T30 when the unit is in a docking station. Could you check on the output of 'vmstat -i' to see what might be using it? Are you running with APIC? I know that it has to be disabled on the T43 and it may need to be on the T30. (It's been a while since I've used the T30.) Add 'hint.apic.0.disabled=1' to /boot/loader to do this. Finally, try 'ifconfig ath0 -bgscan'. Several people have reported that this fixes periodic loss of association on the 5212. By default, background scanning is done every 5 minutes and makes roaming work much better, but seems to have some issues on this card. I'm not at all confident that this will lead to fixing the problem, but it's easy to check on and may point in the right direction. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
Hi, after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 (with ZFS root on encrypted geli, works great). Config is: FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu Feb 5 21:10:45 CET 2009 r...@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt handling: Feb 17 20:15:21 hasking kernel: ath0: mem 0xd021-0xd021 irq 3 at device 0.0 on cardbus0 Feb 17 20:15:21 hasking kernel: ath0: [ITHREAD] Feb 17 20:15:21 hasking kernel: ath0: WARNING: using obsoleted if_watchdog interface Feb 17 20:15:21 hasking kernel: ath0: Ethernet address: 00:19:5b:3a:82:be Feb 17 20:15:21 hasking kernel: ath0: mac 7.9 phy 4.5 radio 5.6 ... Feb 17 21:39:19 hasking kernel: ath0: link state changed to UP Feb 17 21:39:19 hasking kernel: ath0: link state changed to DOWN Feb 17 21:39:23 hasking kernel: ath0: link state changed to UP Feb 17 21:39:23 hasking kernel: ath0: link state changed to DOWN Feb 17 21:39:24 hasking kernel: interrupt storm detected on "irq3:"; throttling interrupt source Next I gave the following card a try: iwi0: mem 0xd020-0xd0200fff irq 5 at device 2.0 on pci2 iwi0: Ethernet address: 00:15:00:31:f3:76 iwi0: [ITHREAD] ...and it regularly drops/looses connection to the WLAN router, as stated in the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=124767 Basically, my question is if there is a fix for any of these issues that I haven't found so far, so that I can eventually use one of my existing wireless cards, or if I should switch to a different brand/model. If the latter is the case I'd like to know which one to choose. Regards Christian Walther ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
