Opened 10 years ago

Closed 7 years ago

#7773 closed enhancement (fixed)

Intel Wireless-N 6300 drivers

Reported by: jaykruer Owned by: axeld
Priority: normal Milestone: R1
Component: Network & Internet/Wireless Version: R1/alpha3
Keywords: Intel, Wireless, 6300 Cc:
Blocked By: Blocking:
Platform: All


The latest version of the wireless driver: iwn(4)at supports the 6300 card. Haiku's current version of the driver is about 3 years old so I was hoping a contributor could update the latest version and make it compatible with Haiku. The card itself isn't actually listed in the information about the driver but according to this thread, it works fine with the card.

Thanks to anyone who could contribute this. I and surely a lot more of Haiku users would greatly appreciate it!

Change History (3)

comment:1 by korli, 10 years ago

AFAICT we use the 8.2 FreeBSD release for the iwn driver. When a new release includes support for this card, we'll update to it.

see here

comment:2 by tonestone57, 10 years ago

I had a quick look too and what Korli says is true. Haiku has same to BSD 8.2 release but you also are kinda right that there is a newer BSD driver for that card. You just will not see it until 8.3 is released because BSD's stable branch is not used for Haiku network drivers. ie, you will have to wait for BSD to make newer release first.

Haiku's card support:

BSD 8.2 card support:

BSD stable branch card support:

The idea being if you went and downloaded current FreeBSD 8.2 release you would get similar driver to Haiku's but if you download FreeBSD nightly you would get the newer BSD network driver. Whether Haiku should use FreeBSD release branch or switch to stable branch is something to discuss on the mailing list. It is an issue of using an older driver version versus stability of current driver. 8.2's iwn driver is 4 months + 1 week old.

comment:3 by luroh, 7 years ago

Resolution: fixed
Status: newclosed

Likely fixed, as Haiku's drivers are currently based on FreeBSD 9.2. Please reopen the ticket if the problem persists and include the device ID of the adapter in question.

Note: See TracTickets for help on using tickets.