Re: iwn driver on 7.1
2009/1/18 Brandon Gooch jamesbrandongo...@gmail.com I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). Wonderfull to say the least ! Seeing that you run successfully 7.1 on a X300 is excellent ! Did you manage to get suspend/resume aka hibernation working somehow ? Thanks Eriam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
iwn driver on 7.1
I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwn driver on 7.1
On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon Sounds like you got to it before I did- thank god! :) Question though: have you got it figured for a channels yet? I'll test it for you and keep you updated with my results. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwn driver on 7.1
Da Rock wrote: On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon Sounds like you got to it before I did- thank god! :) Question though: have you got it figured for a channels yet? I'll test it for you and keep you updated with my results. Thanks for working on the driver! The only difference to the version of gavin that I could see is that the bands in iwn_bands that got commented out were brought back. Or did I miss something? Do you know why they were commented out and it was unnecessary? Or was it just to fix the crash? I did a few test runs: It does not crash immediately as the version from gavin, but the error I had with the perforce version iwn0: error, INTR=8200SW_ERROR,RX_INTR STATUS=0x1 iwn0: iwn_config: could not set power mode, error 35 is there -- in 3 out of 3 tries. So nothing improved there. (I hit that error on first use in about 50% of the cases before.) Moreover, at 3 out of 4 tries to 'kldunload if_iwn' after hitting the error (after '/etc/rc.d/netif stop iwn0' and 'ifconfig iwn0 down'), there was a crash: 2 page faults and 1 freeze. I have not had that with the perforce version. (Maybe once long ago, but I think I forgot to stop iwn0 at that time.) The one time I actually got the (WPA2) connection up, I was able to transfer with a similar speed as with the perforce version. Thus, for me, there are no improvement over the (old) perforce version. Probably by chance, but I had more crashes. I think the thread on stable@ should rather be continued than the one on questions@, but since Da Rock answered on questions@, I reinclude both. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwn driver on 7.1
On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon I get messages saying it can't read the eeprom- is this right? Other than that it seems good. Incidentally, I answered here because thats where the message was originally posted- should I move this discussion to stable? I'm subscribed there too I believe, so its no problem if its a matter of policy. #kldload if_iwn iwn0: Intel(R) Pro/Wireless 4965BGN mem 0xfe5fe000-0xfe5f irq 17 at device 0.0 on pci7 iwn0: could not read EEPROM iwn0: Reg Domain: spadesiwn0:could not read EEPROM, address 00:00:00:00:00:00 iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: could not read EEPROM iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11na MCS: 6.5Mbps 13Mbps 19.5Mbps 26Mbps 39Mbps 52Mbps 58.5Mbps 65Mbps 13Mbps 26Mbps 39Mbps 52Mbps 78Mbps 104Mbps 117Mbps 130Mbps iwn0: 11ng MCS: 6.5Mbps 13Mbps 19.5Mbps 26Mbps 39Mbps 52Mbps 58.5Mbps 65Mbps 13Mbps 26Mbps 39Mbps 52Mbps 78Mbps 104Mbps 117Mbps 130Mbps #wpa_supplicant -i iwn0 -c /etc/wpa_supplicant.conf iwn0: error, INTR=200SW_ERROR STATUS=0x0 #wpa_supplicant -i iwn0 -c /etc/wpa_supplicant.conf Trying to associate with ap mac (SSID='ssid name' freq=2442 MHz) Authentication with ap mac timed out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwn driver on 7.1
The kernel panic was due to a NULL pointer dereference in the module. The code that was commented out created a situation in which the array of structs (line 2412): static const struct iwn_chan_band iwn_bands[] contained only 2 items. The code following the struct array that obtained the list of authorized channels: /* read the list of authorized channels */ for (i = 0; i N(iwn_bands)-2; i++) iwn_read_eeprom_band(sc, iwn_bands[i]); didn't actually get a list of anything, since N(iwn_bands)-2 evaluates to zero in this case. The NULL pointer part comes in when the call to ieee80211_sort_channels() on line 2436 sends a list of no items with a value of 0 for ic-ic_nchans. The backported insertion sort code from 8.0-CURRENT's 802.11 stack fails somewhere because of this value, due to access of some memory address in the chancompar() or swap(?) -- I didn't really dig that far into it. I guess the purpose of commenting out the A channels in the iwn_bands[] was to keep the driver from potentially using them, but honestly, I'm not sure if that's the appropriate way to do that (I'm just getting into this stuff). I'm sure the MFC'd VAP stuff that Sam Leffler is working on will alleviate all of this, but I wanted a working iwn(4) for now ;) On Sun, Jan 18, 2009 at 4:10 PM, Jan Henrik Sylvester m...@janh.de wrote: Da Rock wrote: On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon Sounds like you got to it before I did- thank god! :) Question though: have you got it figured for a channels yet? I'll test it for you and keep you updated with my results. Thanks for working on the driver! The only difference to the version of gavin that I could see is that the bands in iwn_bands that got commented out were brought back. Or did I miss something? Do you know why they were commented out and it was unnecessary? Or was it just to fix the crash? I did a few test runs: It does not crash immediately as the version from gavin, but the error I had with the perforce version iwn0: error, INTR=8200SW_ERROR,RX_INTR STATUS=0x1 iwn0: iwn_config: could not set power mode, error 35 is there -- in 3 out of 3 tries. So nothing improved there. (I hit that error on first use in about 50% of the cases before.) Moreover, at 3 out of 4 tries to 'kldunload if_iwn' after hitting the error (after '/etc/rc.d/netif stop iwn0' and 'ifconfig iwn0 down'), there was a crash: 2 page faults and 1 freeze. I have not had that with the perforce version. (Maybe once long ago, but I think I forgot to stop iwn0 at that time.) The one time I actually got the (WPA2) connection up, I was able to transfer with a similar speed as with the perforce version. Thus, for me, there are no improvement over the (old) perforce version. Probably by chance, but I had more crashes. I think the thread on stable@ should rather be continued than the one on questions@, but since Da Rock answered on questions@, I reinclude both. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
iwn driver on 7.1
I've tried the driver on 7.0- 8.0 current is out of the question as it still doesn't fully function either- but I'm trying to sort out 7.1 (might as well, I have many other issues to work out so I might as well fix them on this :) ). The driver patches compiles (iwn-7 from gavin), but when I load it goes through the channels and errors and finally dies with a full page fault. SO, firstly what info is needed here to help resolve this issue? Second, the full functionality of the card is not there- no encryption in transmission (no wep, wpa, etc), a channels not working, etc. Again is there someone who I could work with to help get this card working? For reference (Wojciech will be happy to know his suspicions are indeed correct :) ) linux has gone to the crapper and even debian can barely hold its own with the intel 4965. Incidentally none of the linuxes have consistent success at all, and I failed miserably on debian and fedora. Although it did work somewhat with fedora 8- strange huh? And its not the only area, drivers, kernel, software all seems deeply flawed now: seems the project is starting to crumble! I'm struggling to keep my tv server up and running on fedora 10 - there appears I may have a light at the end of my tunnel in that I may be able to get drivers working for freebsd! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [Fwd: iwn driver on 7.1]
Sam Fourman Jr. wrote: From: Da Rock rock_on_the_web at comcen.com.au I've tried the driver on 7.0- 8.0 current is out of the question as [...] The driver patches compiles (iwn-7 from gavin), but when I load it goes through the channels and errors and finally dies with a full page fault. for what it is worth I too would very much like iwn working on freebsd 7.1, it works ok on 8-current See my previous post to stable@ in December, which was unfortunately unanswered: http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047142.html Short: The version from gavin crashes for me, too, but the initial version from perforce (before vap was introduced) works -- with some issues. There are only very few differences between those 2 versions. I guess someone with knowledge of vap would have to go through the perforce and current changes to find the stabilizing changes. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[Fwd: iwn driver on 7.1]
---BeginMessage--- I've tried the driver on 7.0- 8.0 current is out of the question as it still doesn't fully function either- but I'm trying to sort out 7.1 (might as well, I have many other issues to work out so I might as well fix them on this :) ). The driver patches compiles (iwn-7 from gavin), but when I load it goes through the channels and errors and finally dies with a full page fault. SO, firstly what info is needed here to help resolve this issue? Second, the full functionality of the card is not there- no encryption in transmission (no wep, wpa, etc), a channels not working, etc. Again is there someone who I could work with to help get this card working? For reference (Wojciech will be happy to know his suspicions are indeed correct :) ) linux has gone to the crapper and even debian can barely hold its own with the intel 4965. Incidentally none of the linuxes have consistent success at all, and I failed miserably on debian and fedora. Although it did work somewhat with fedora 8- strange huh? And its not the only area, drivers, kernel, software all seems deeply flawed now: seems the project is starting to crumble! I'm struggling to keep my tv server up and running on fedora 10 - there appears I may have a light at the end of my tunnel in that I may be able to get drivers working for freebsd! ---End Message--- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [Fwd: iwn driver on 7.1]
-- Forwarded message -- From: Da Rock rock_on_the_...@comcen.com.au To: freebsd-questions@freebsd.org Date: Fri, 16 Jan 2009 12:32:04 +1000 Subject: iwn driver on 7.1 I've tried the driver on 7.0- 8.0 current is out of the question as it still doesn't fully function either- but I'm trying to sort out 7.1 (might as well, I have many other issues to work out so I might as well fix them on this :) ). The driver patches compiles (iwn-7 from gavin), but when I load it goes through the channels and errors and finally dies with a full page fault. SO, firstly what info is needed here to help resolve this issue? Second, the full functionality of the card is not there- no encryption in transmission (no wep, wpa, etc), a channels not working, etc. Again is there someone who I could work with to help get this card working? For reference (Wojciech will be happy to know his suspicions are indeed correct :) ) linux has gone to the crapper and even debian can barely hold its own with the intel 4965. Incidentally none of the linuxes have consistent success at all, and I failed miserably on debian and fedora. Although it did work somewhat with fedora 8- strange huh? And its not the only area, drivers, kernel, software all seems deeply flawed now: seems the project is starting to crumble! I'm struggling to keep my tv server up and running on fedora 10 - there appears I may have a light at the end of my tunnel in that I may be able to get drivers working for freebsd! for what it is worth I too would very much like iwn working on freebsd 7.1, it works ok on 8-current but I did run in a issue where all I had available to me were wep based AP's (linksys wrt54G) and I could not connect. Sam Fourman Jr. Fourman Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
