Re: Intel WiFi Link 130

2012-08-25 Thread David Coppa
diff please

On Sat, Aug 25, 2012 at 3:29 AM, X-user  wrote:
> Add code to enable boot-time configuration of this device:
>
> file: src/sys/dev/pci/if_iwn.c, from line: 93
> [begin code]
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_1 },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_2 }
> };
> [end code]



Re: Intel WiFi Link 130

2012-08-25 Thread X-user
93c93,95
<   { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 }
---
>   { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 },
>   { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_1 },
>   { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_2 }


25.08.2012, 12:16, "David Coppa" :
> diff please
>
> On Sat, Aug 25, 2012 at 3:29 AM, X-user  wrote:
>
>>  Add code to enable boot-time configuration of this device:
>>
>>  file: src/sys/dev/pci/if_iwn.c, from line: 93
>>  [begin code]
>>  { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 },
>>  { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_1 },
>>  { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_2 }
>>  };
>>  [end code]



Re: Intel WiFi Link 130

2012-08-25 Thread Mark Kettenis
> From: X-user 
> Cc: "bugs@openbsd.org" 
> 
> 93c93,95
> < { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 }
> ---
> > { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 },
> > { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_1 },
> > { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_2 }

And does it actually work?



Re: Intel WiFi Link 130

2012-08-25 Thread X-user
Well, kernel sees and configures device successfully creating iwn0 interface.
But dealing with firmware (for example when you try to do "ifconfig iwn0 up 
scan") causes fatal firmware error.

I compile and use OpenBSD 5.2-current (GENERIC.MP) kernel/base/xorg etc.

Here are logs:

Device as seen by kernel compiled with modified "if_iwn.c":
iwn0 at pci1 dev 0 function 0 "Intel WiFi Link 130" rev 0x34: msi, MIMO 1T2R, 
BGN, address XX:XX:XX:XX:XX:XX
(With original "if_iwn.c" it said "device not configured")

"ifconfig iwn0":
iwn0: flags=8802 mtu 1500
lladdr dc:a9:71:0e:de:9a
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid ... etc.

Firmware error from dmesg (when trying to bring interface up/scan for networks):
iwn0: fatal firmware error
firmware error log:
  error type  = "UNKNOWN" (0x1999)
  program counter = 0x00013638
  source line = 0x012F
  error data  = 0x000100A4
  branch link = 0x0001362C0001362C
  interrupt link  = 0xC15E
  time= 28087
driver status:
  tx ring  0: qid=0  cur=0   queued=0  
  tx ring  1: qid=1  cur=0   queued=0  
  tx ring  2: qid=2  cur=0   queued=0  
  tx ring  3: qid=3  cur=0   queued=0  
  tx ring  4: qid=4  cur=2   queued=0  
  tx ring  5: qid=5  cur=0   queued=0  
  tx ring  6: qid=6  cur=0   queued=0  
  tx ring  7: qid=7  cur=0   queued=0  
  tx ring  8: qid=8  cur=0   queued=0  
  tx ring  9: qid=9  cur=0   queued=0  
  tx ring 10: qid=10 cur=0   queued=0  
  tx ring 11: qid=11 cur=0   queued=0  
  tx ring 12: qid=12 cur=0   queued=0  
  tx ring 13: qid=13 cur=0   queued=0  
  tx ring 14: qid=14 cur=0   queued=0  
  tx ring 15: qid=15 cur=0   queued=0  
  tx ring 16: qid=16 cur=0   queued=0  
  tx ring 17: qid=17 cur=0   queued=0  
  tx ring 18: qid=18 cur=0   queued=0  
  tx ring 19: qid=19 cur=0   queued=0  
  rx ring: cur=2
  802.11 state 0
iwn0: crystal calibration failed
iwn0: could not initialize hardware


So it's configured, but does not really work. One interesting thing is that it 
works brilliant on last FreeBSD release with the (same?) iwn driver.
Do you know what's wrong with that on OpenBSD's iwn?

25.08.2012, 19:45, "Mark Kettenis" :

>  And does it actually work?



Re: Intel WiFi Link 130

2012-08-27 Thread X-user
It's me again.

I just want to say that now (after removing firmwares that are downloaded with 
OpenBSD's fw_update
and copying new one from 
http://intellinuxwireless.org/?n=downloads&f=ucodes_6000g2b to 
/etc/firmware/iwn-6005)
dmesg does not show firmware error anymore!

But now it says

iwn0: could not configure bluetooth coexistence
iwn0: could not configure device

when trying to scan for WiFi AP's and I can't see list of available networks.
Now iwn0 is "UP" but status is "no network", so again I cannot see available 
access points to connect.



Re: Intel WiFi Link 130

2012-08-27 Thread Stuart Henderson
On 2012/08/27 22:18, X-user wrote:
> It's me again.
> 
> I just want to say that now (after removing firmwares that are downloaded 
> with OpenBSD's fw_update
> and copying new one from 
> http://intellinuxwireless.org/?n=downloads&f=ucodes_6000g2b to 
> /etc/firmware/iwn-6005)
> dmesg does not show firmware error anymore!
> 
> But now it says
> 
> iwn0: could not configure bluetooth coexistence
> iwn0: could not configure device
> 
> when trying to scan for WiFi AP's and I can't see list of available networks.
> Now iwn0 is "UP" but status is "no network", so again I cannot see available 
> access points to connect.
> 

Scanning doesn't work correctly in some otherwise-working iwn devices,
for example this one:

iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, 
MIMO 2T2R, MoW, address 8c:70:5a:62:b7:f8

Are you able to associate to a network if you already know the ssid
and set it manually ("ifconfig iwn0 nwid ")?



Re: Intel WiFi Link 130

2012-08-27 Thread X-user
No, I'm unable to do this. Still 

iwn0: could not configure bluetooth coexistence
iwn0: could not configure device

and

iwn0: could not configure bluetooth coexistence
iwn0: could not configure device
iwn0: no link ..sleeping

when doing the same at boot.


I tried all versions of ucode but always get the same messages and no 
connection :(

Then, does anybody know why this WiFi card works flawlessly on FreeBSD?



27.08.2012, 23:56, "Stuart Henderson" :

>  Scanning doesn't work correctly in some otherwise-working iwn devices,
>  for example this one:
>
>  iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: 
> msi, MIMO 2T2R, MoW, address 8c:70:5a:62:b7:f8
>
>  Are you able to associate to a network if you already know the ssid
>  and set it manually ("ifconfig iwn0 nwid ")?



Re: Intel WiFi Link 130

2012-08-31 Thread X-user2008
As I see, iwn driver in OpenBSD is very old and misses necessary iwn-6005 code 
(init and advanced bt coexistence especially) which is present in iwn from 
FreeBSD.
Sync of code with proper adaptation to OpenBSD is needed to get it working, 
otherwise it gives kernel panic if we just add send_advanced_btcoex function 
and invoke it in iwn-6005 init code.
Use newest iwn-6005 firmware images in order not to get any firmware-related 
errors.
Also note that device is named  in FreeBSD.

Cheers!