Comments on: Intel firmwares hit the base system http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/ (Mostly) Technical Blog Wed, 07 Jan 2009 04:43:31 +0000 http://wordpress.org/?v=2.7 hourly 1 By: MOBY http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-12315 MOBY Fri, 10 Aug 2007 01:39:08 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-12315 <strong>Bookmarks...</strong> I can't add your post to Digg. How I do this?... Bookmarks…

I can’t add your post to Digg. How I do this?...

]]> By: Ron http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-7982 Ron Mon, 23 Apr 2007 05:33:01 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-7982 Hi, I've had exactly the same result as ka73ka on my new Asus A8JS. In fact thanks ka73ka for posting, I wouldn't have tried that version if I hadn't seen your post. Ron Hi,

I’ve had exactly the same result as ka73ka on my new Asus A8JS. In fact thanks ka73ka for posting, I wouldn’t have tried that version if I hadn’t seen your post.

Ron

]]> By: old http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-7807 old Sun, 15 Apr 2007 10:05:35 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-7807 i've been trying to get it working since yesterday on my hp nc6320 running current with no luck. still can't get past that 'bus_dmamem_alloc' error. kldloads/unloads do not seem to help at all. i'm willing to help with testing etc too if you need it. i’ve been trying to get it working since yesterday on my hp nc6320 running current with no luck.
still can’t get past that ‘bus_dmamem_alloc’ error. kldloads/unloads do not seem to help at all.
i’m willing to help with testing etc too if you need it.

]]> By: ka73ka http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6822 ka73ka Sun, 18 Mar 2007 01:52:57 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6822 I've done some testing and if you are interested in results: I have WPA and WPA2 on my AP Toshiba Tecra m5 106 I made /etc/wpa_supplicant.conf and ssid and psk there. *** wpi-freebsd-20061109.tgz (I used it before) *** #kldload if_wpi # wpa_supplicant -i wpi0 -c /etc/wpa_supplicant.conf Everything works (connecting to AP, key negotiation, dhcpd) exept that on ttyv0 i still gets "rx tail flags error 702" ... but it's "working" *** wpi-perforce-20070315.tgz *** # kldload firmware # kldload if_wpi # wpa_supplicant -i wpi0 -c /etc/wpa_supplicant.conf ioctl[SIOCS80211, op 23, arg 0x0]: Invalid argument Failed to initiate AP scan. and on ttyv0 i have: firmware status=0xffffffff need val=0x40400000 wpi0: timeout waiting for adapter to initialize wpi0: could not lock memory And it can't connect. I’ve done some testing and if you are interested in results:

I have WPA and WPA2 on my AP
Toshiba Tecra m5 106

I made /etc/wpa_supplicant.conf and ssid and psk there.

*** wpi-freebsd-20061109.tgz (I used it before) ***

#kldload if_wpi

  1. wpa_supplicant -i wpi0 -c /etc/wpa_supplicant.conf
    Everything works (connecting to AP, key negotiation, dhcpd) exept that on ttyv0 i still gets “rx tail flags error 702” ... but it’s “working”

*** wpi-perforce-20070315.tgz ***

  1. kldload firmware
  2. kldload if_wpi
  3. wpa_supplicant -i wpi0 -c /etc/wpa_supplicant.conf
    ioctl[SIOCS80211, op 23, arg 0×0]: Invalid argument
    Failed to initiate AP scan.

and on ttyv0 i have:
firmware status=0xffffffff need val=0×40400000
wpi0: timeout waiting for adapter to initialize
wpi0: could not lock memory

And it can’t connect.

]]> By: po http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6742 po Thu, 15 Mar 2007 14:36:42 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6742 Thank you! I'll test on this week-end, and provide you with details if you interested. Thank you! I’ll test on this week-end, and provide you with details if you interested.

]]> By: Florent Thoumie http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6738 Florent Thoumie Thu, 15 Mar 2007 13:49:58 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6738 I've put a snapshot of the development version here: http://people.freebsd.org/~flz/local/wpi/wpi-perforce-20070315.tgz Be sure to load the firmware *before* he driver itself. If you get bus_dmamem_alloc errors, just kldunload if_wpi and kldload if_wpi until it goes away (but don't do that too quickly, I think I got some panics when doing this). I’ve put a snapshot of the development version here:

http://people.freebsd.org/~flz/local/wpi/wpi-perforce-20070315.tgz

Be sure to load the firmware before he driver itself. If you get bus_dmamem_alloc errors, just kldunload if_wpi and kldload if_wpi until it goes away (but don’t do that too quickly, I think I got some panics when doing this).

]]> By: po http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6737 po Thu, 15 Mar 2007 13:44:06 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6737 Thank you for answer. And where i can get this version of wpi(4), that is have "couple of issues to fix"? I can to render assistance on testing. (I'm using HP nx7400 with 3495 in it) on -STABLE and -CURRENT. Thank you for answer. And where i can get this version of wpi(4), that is have “couple of issues to fix”? I can to render assistance on testing. (I’m using HP nx7400 with 3495 in it) on -STABLE and -CURRENT.

]]> By: Florent Thoumie http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6734 Florent Thoumie Thu, 15 Mar 2007 13:09:12 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6734 I'll MFC firmwares for iwi(4) in two weeks. Firmwares for ipw(4) will have to wait until we MFC latest ipw(4) changes to RELENG_6 (firmware(9) support being one of them). The port of OpenBSD wpi(4) driver is still being worked on, there are still a couple of issues left to fix (note: I'm not the one working on it). The firmware will be committed at the same time. I’ll MFC firmwares for iwi(4) in two weeks. Firmwares for ipw(4) will have to wait until we MFC latest ipw(4) changes to RELENG_6 (firmware(9) support being one of them).

The port of OpenBSD wpi(4) driver is still being worked on, there are still a couple of issues left to fix (note: I’m not the one working on it). The firmware will be committed at the same time.

]]> By: po http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6733 po Thu, 15 Mar 2007 12:52:18 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6733 Thats really great news! Much thanks you for this! When you planning to add 3945 support, and when you planning to MFC this to RELENG_6? Thanks in advance for answer/ Thats really great news! Much thanks you for this! When you planning to add 3945 support, and when you planning to MFC this to RELENG_6? Thanks in advance for answer/

]]> By: Florent Thoumie http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/comment-page-1/#comment-6716 Florent Thoumie Wed, 14 Mar 2007 14:37:25 +0000 http://blog.xbsd.org/2007/03/02/intel-firmwares-hit-the-base-system/#comment-6716 I think I'm going to start moderating comments. The previous comment was brought to you by somebody who needed 6 hours to apply a patch. :-) I think I’m going to start moderating comments.

The previous comment was brought to you by somebody who needed 6 hours to apply a patch.

:-)

]]>