Hello Cedric,

Am 26.10.2013 10:56, schrieb c...@cgross.info:
You must get and build net80211 from -HEAD also. It's why you have this kind of compile error.

Thanks, this was exactly my miss. With net80211 from -HEAD it built.

I first tried IWL (https://github.com/KreizIT/freebsd-iwl) with FreeBSD 9.2-RELEASE.

When I try to load the module with kldload if_iwl the kernel panics:

Unread portion of the kernel message buffer:
iwl0: <Intel Centrino Wireless-N 2230> mem 0xf1500000-0xf1501fff irq 17 at device 0.0 on pci2
iwl0: iwl_read_eeprom_ht40: no entry for channel 1
iwl0: iwl_read_eeprom_ht40: no entry for channel 2
iwl0: iwl_read_eeprom_ht40: no entry for channel 3
iwl0: iwl_read_eeprom_ht40: no entry for channel 4
iwl0: iwl_read_eeprom_ht40: no entry for channel 5
iwl0: iwl_read_eeprom_ht40: no entry for channel 6
iwl0: iwl_read_eeprom_ht40: no entry for channel 7
panic: ieee80211_get_ratetable: no rate table for channel; freq 0 flags 0x0

cpuid = 3
KDB: stack backtrace:
#0 0xffffffff80947986 at kdb_backtrace+0x66
#1 0xffffffff8090d9ae at panic+0x1ce
#2 0xffffffff80a1399e at ieee80211_get_ratetable+0x10e
#3 0xffffffff809eb3a5 at ieee80211_media_init+0x355
#4 0xffffffff809eb69e at ieee80211_ifattach+0xae
#5 0xffffffff81864914 at iwl_attach+0xbd4
#6 0xffffffff8186d360 at iwl_pci_attach+0x2f0
#7 0xffffffff809405dc at device_attach+0xcc
#8 0xffffffff8064a0ca at pci_driver_added+0xda
#9 0xffffffff8093e765 at devclass_driver_added+0x75
#10 0xffffffff8093f2a3 at devclass_add_driver+0x103
#11 0xffffffff808f80c8 at module_register_init+0xa8
#12 0xffffffff808f004e at linker_load_module+0x85e
#13 0xffffffff808f0688 at kern_kldload+0xb8
#14 0xffffffff808f08a4 at sys_kldload+0x84
#15 0xffffffff80cf187a at amd64_syscall+0x5ea
#16 0xffffffff80cdbff7 at Xfast_syscall+0xf7

Any ideas?

Kind regards,
Matthias
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to