Re: Bounty for Intel AC9560 wireless support

[Ben Woods]

On Wed, 20 Nov 2019 at 11:42 pm, ma...@freebsd.org 
wrote:

> Hi Ben,
>
> Since I did that work under Foundation sponsorship I'd prefer to see
> the bounty donated to the FF.  Please do include any notes you have
> about areas of FreeBSD that need improvement, especially related to
> missing laptop support.  One pressing need is support for newer WiFi
> standards in iwm(4), and we're looking at that now.
>
Done!

Evidence: https://pasteboard.co/IHCJyMY5.jpg

Thanks again.

#putyourmoneywhereyourmouthis

Text from the donation:

“
Bounty for Intel AC9560 support - thank you!
https://lists.freebsd.org/pipermail/freebsd-wireless/2019-November/008921.html

Idea: client to flash firmware updates from vendors:
https://fwupd.org/
“

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

New iwm wireless driver stopped working (9560)

[Ben Woods]

Hi everyone,

Since Mark recently committed the new iwm driver discussed at the bug
report below, I had been happily using my built in wireless card.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227044#c24

However, as of today it has stopped working - the card no longer shows up
under "sysctl net.wlan.devices".

Since I am running the exact same code as when it was working, the only
thing I can think of that could have changed it is that I had rebooted this
laptop into Windows, and Intel driver update was waiting - I applied it.
This might have flashed the firmware on the device.

Any ideas what could cause this or how to troubleshoot it? The pciconf
looks the same as when I reported it on the above bug report.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Intel 9560 chip

[Ben Woods]

On Tue, 5 Feb 2019 at 10:57 pm, Li-Wen Hsu  wrote:

> On Tue, Feb 5, 2019 at 10:53 PM Ben Woods  wrote:
> > Just wondering if there is any work underway to add support for the Intel
> > Dual Band Wireless AC 9560 chipset to the iwm(4) driver?
>
> My friend is working on that, but doesn't have a working state yet:
>
>
> https://lists.freebsd.org/pipermail/freebsd-wireless/2019-January/008548.html



Hi Li-Wen,

Awesome - thanks for your efforts, and good luck!

Please feel free to reach out to me once you would like some more testers.

Regards,
Ben

>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2019-January/008548.html>

-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Intel 9560 chip

[Ben Woods]

Hi everyone,

Just wondering if there is any work underway to add support for the Intel
Dual Band Wireless AC 9560 chipset to the iwm(4) driver?

I have this wireless card built into my new Thinkpad P1 laptop, and would
be happy to test if any progress and report back.

It doesn't look like it has made it into DragonFlyBSD or OpenBSD yet either.
https://github.com/DragonFlyBSD/DragonFlyBSD/tree/master/sys/contrib/dev/iwm
https://github.com/openbsd/src/blob/master/sys/dev/pci/if_iwm.c#L7521

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: iwm7265 device no longer working after 7265D firmware added in r314079

[Ben Woods]

On 20 March 2017 at 20:25, Jonathan Anderson  wrote:

> Hi,
>
> Do you have something like `iwm7265fw_load="YES"` in `/boot/loader.conf`?
> I needed to change `iwm7265fw` to `iwm7265Dfw` when the new firmware came
> in, then everything seemed to work...
>


Hi Jon,

Yes, that was the problem. I made the same change to /boot/loader.conf,
rebooted the machine, and my wireless was back and working.

Thanks for that!

Regards,
Ben
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

iwm7265 device no longer working after 7265D firmware added in r314079

[Ben Woods]

Hi everyone,

I have been successfully using the iwm(4) driver with my Intel 7265
wireless card on FreeBSD-current for some time now, but with the recent
update I applied the other day it has stopped working.

I upgraded my FreeBSD 12-current:
From: r313908
To: r315466

I suspect the issue was introduced with the addition of the 7265D firmware
in r314079.

My dmesg output now shows:
iwm0:  mem 0xf720-0xf7201fff at
device 0.0 on pci2
iwm7265Dfw: root not mounted yet, no way to load image
iwm0: could not read firmware iwm7265Dfw (error 0)
iwm0: Failed to start INIT ucode: 35


Note that I do have the file /boot/kernel/iwm7265Dfw.ko (as well as others
for 7260, 7265, 8000C, 3160).

Any ideas what I can do to get my wireless back please?

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Broadcom BCM 43xx wireless chips

[Ben Woods]

On Wed., 16 Nov. 2016 at 8:09 pm, Andy Mender 
wrote:

> Dear Adrian,
>
> I set the mentioned option (BWN_GPL_PHY just below the bwn driver) in the
> kernel config file and recompiled the STABLE kernel.
> Now the additional message about BWN_GPL_PHY is gone, but there is some 2-3
> features listed as unsupported. The driver gets attached to the network
> card as siba_bwn0, but no interface is created by ifconfig.
>
> What should be the name of the interface in /etc/rc.conf - siba_bwn0 or
> bwn0?
>
> Otherwise, paradox added a link to some Broadcom device datasheets from
> Cypress: http://www.cypress.com/search/all?f[0]=meta_type%
> 3Atechnical_documents[1]=resource_meta_type%3A575[2]=
> field_related_products%3A110101
>
> I had a quick look and although bcm4321 and bcm4322 are not on the list,
> bcm4318, bcm4319 and bcm4325 are. Might be relevant to further testing and
> writing drivers in general.
>
> Best regards,
> Andy
> ___
> freebsd-wireless@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
> "
>

Hi Andy,

Since 11.0-RELEASE FreeBSD no longer shows the parent interface for
wireless devices in ifconfig. It will only show the cloned wlan0 device
once it is created.

To determine which wireless devices are available to clone to a wlan0
interface, use the following command:
$ sysctl net.wlan.devices

Once you have found the wireless device, set it up using the normal method:
https://www.freebsd.org/doc/handbook/network-wireless.html

Good luck!

Regards,
Ben
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD 11.0 8026 Support

[Ben Woods]

On Thursday, 8 September 2016, Jim Heald  wrote:

> Hello,
>
> I have FreeBSD 11.0-RC2 installed and my wifi doesn't work. However, I
> noticed this commit 
> and
> also that FreeBSD 11.0 should be released pretty soon (like in the next few
> weeks). Therefore, I'm curious first off if the Intel 8026 chipset will be
> supported in 11.0 and if not how (if possible) I can compile and install
> the updated driver to get wifi working.
>
> Thanks!
>
> Jim
>

Do you mean the Intel 8260 chipset (rather than 8026)?

My understanding is that yes, it is supported by FreeBSD 11. However, the
driver is young; and not without problems. In saying that, you should be
able to use you wifi!

https://www.freebsd.org/cgi/man.cgi?query=iwm=0=0=FreeBSD+11.0-RELEASE=default=html

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: [CFT] iwm driver synced with DragonflyBSD

[Ben Woods]

On Mon, Jun 20, 2016 at 01:22:24PM +0200, Emmanuel Vadot wrote:
> On Mon, 20 Jun 2016 12:02:26 +0200
> Ben Woods <woods...@gmail.com> wrote:
> 
> > Upon reboot I got a kernel panic after it loaded the module. I took photos
> > of my screen at the debug console, which you can find at the link below. If
> > there is a way to get a better output for debugging, please let me know.
> > http://imgur.com/a/TJ7i5
> 
>  It seems that it kernel panic when creating the wlan0 interface.
>  I guess that the modules are loaded by the loader ? (i.e. in 
> /boot/loader.conf)
> 
>  Could you test not loading them by the loader but by manually after login ?
> 
>  kldload iwmfw.ko && kldload if_iwm
> 
>  Then restart the netif service (or create the wlan0 directly).
> 
> -- 
> Emmanuel Vadot <m...@bidouilliste.com>

Hi Emmanuel,

Whilst I agree the screenshot looks like the failure occurs whilst creating the
wlan0 interface, it in fact occurs when loading the if_iwm module. I have
tested by stopping the netif service and then loading the modules manually, and
you can see the screenshot here:
http://i.imgur.com/2ftzhQa.jpg

I never got a chance to restart netif service.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: [CFT] iwm driver synced with DragonflyBSD

[Ben Woods]

On 19 June 2016 at 17:20, Emmanuel Vadot  wrote:

>
>  Hello all,
>
>  I've sync our driver with the DragonflyBSD one.
>  I'm currently happilly running it on three on my laptops :
>  - HP 840 G1 (iwm 7260)
>  - HP 840 G2 (iwm 7265)
>  - HP 840 G3 (iwm 8000C)
>
>  Just so you know :
>  1) I know nothing about wireless
>  2) This was only done in one day
>  3) I started the day sober, I finished it drunk
>  4) There is still locking problem at fw load and scan (probably
> because of 1, 2 and 3)
>  5) I do NOT plan to commit this for 11.0
>  6) I DO plan to commit this for 12 once code freeze is finished (and
> when the last problems would be corrected)
>  7) I will eventually commit this for 11.1
>
>  I you want to test it (especially if you have the 3160 serie) all the
> code is in my github branch : https://github.com/evadot/freebsd/tree/iwm
>  Just recompile the modules from sys/modules/{iwm,iwmfw}.
>  You need the last firmware (version 16.XXX) for the driver to work.
>
>  The main news is that the serie 8000 is supported (found in skylake
> laptop) and that the led works (not on the 8000 serie thought).
>
>  Knowing nothing about wireless I do not plan to maintain this driver
> but I'll try keep it synced with DragonflyBSD/OpenBSD (so yeah I think
> that this is maintening ...)
>
>  Please let me know (here would be better) if you have any problem (or
> not) with this update.
>
>  Cheers,
>
> --
> Emmanuel Vadot
>

Hi Emmanuel,

Thank you for your work on this.

I have just tried building and installing this on FreeBSD 11-current
r302020, and unfortunately it failed.

To be clear, I took the following steps to perform my testing:

   - git clone -b iwm --single-branch https://github.com/evadot/freebsd.git
   - cd freebsd/sys/modules/iwm
   - make
   - sudo cp if_iwm.ko /boot/kernel/
   - cd ../iwmfw
   - make
   - find . -name "*.ko*" -exec sudo cp {} /boot/kernel/ \;
   - reboot

Upon reboot I got a kernel panic after it loaded the module. I took photos
of my screen at the debug console, which you can find at the link below. If
there is a way to get a better output for debugging, please let me know.
http://imgur.com/a/TJ7i5

I am not sure what you meant when you said I need the latest firmware
(16.XXX) for the driver to work.

Regards,
Ben
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: iwm updates from dfbsd; AR9462/QCA9565 bluetooth coex updates

[Ben Woods]

On 2 June 2016 at 07:49, Adrian Chadd  wrote:

> hi!
>
> Firstly - I've just merged in some fixes from dragonflybsd via the
> maintainer there, Imre Vadasz. He's been pushing patches to me against
> -HEAD to commit. Thanks!
>
> I'd like those tested, so if you're using iwm please test them out and
> let me know.
> ...
> Thanks!
>
> -adrian
>

Hi Adrian,

I have just rebuilt my 11-current laptop and am using the newest updates to
the iwm(4) driver. Haven't yet connected to a WPA2 network, but so far, so
good connecting to the open cafe wifi :)

Thanks!
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: iwm7265fw: fatal firmware error

[Ben Woods]

On 25 April 2016 at 07:47, Adrian Chadd  wrote:

> Hi,
>
> ok, I'm testing it out right now, but I had to manually merge it into
> my -HEAD laptop. I'll let you know how it goes.
>
> Thanks!
>
> -a


I am also having issues with iwm7265 wireless driver regularly having
firmware errors and disassociating with the wireless gateway.

Happy to test the patch against head and let you know if it fixes my issues.

Adrian: could you send me the patch that worked for you against head?

Regards,
Ben
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: forwarding didn't work if wlan0 is member of a bridge

[Ben Woods]

On Wednesday, 23 December 2015, Adrian Chadd  wrote:

> Hi,
>
> inet 10.239.142.126 netmask 0xffe0 broadcast 10.239.142.127
>
> This looks like a problem with your addressing. That netmask != that
> broadcast.
>
> Please recheck your networking setup!
>
>
> -a
>

That broadcast looks correct for me for a bet mask of 0xffe0 (/27).

http://jodies.de/ipcalc?host=10.239.142.126=27=

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: CFT: wpa_supplicant/hostapd 2.5

[Ben Woods]

On 14 October 2015 at 13:00, Rui Paulo  wrote:

> Hi,
>
> Please download and test the wpa_supplicant/hostapd import patch:
>
> http://people.freebsd.org/~rpaulo/patches/wpa-2.5.diff
>
>
> Changelog:
>
> http://w1.fi/cgit/hostap/plain/hostapd/ChangeLog
> http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog
>
>
> Please report success/failures.
>
> Thanks,
> --
> Rui Paulo
>


Hi Rui,

I've build FreeBSD head with your patch and have been using it on my home
wireless router for a couple of days now (running on a Netgate RCC-VE 8860
running FreeBSD head amd64 with AR9280 wifi chip).

All working fine for me. Thanks for your work.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Ben Woods]

No worries :)

Got any advice on how to diagnose why it's able to scan and lock onto the
ssid (shows it in ifconfig), but not able to get an IP address with DHCP or
communicate with a manual IP address?

On Tuesday, November 18, 2014, Kevin Lo ke...@freebsd.org wrote:

 Argh! I think I need more coffee.  rsu(4) does support this chipset.
 Sorry for the noise.

 Kevin

 On Tue, Nov 18, 2014 at 03:08:37PM +0800, Kevin Lo wrote:
  I'm pretty sure.  See OpenBSD cvs log:
  http://marc.info/?l=openbsd-cvsm=128897633210060w=2
 
  I'll be fixing rsu(4), thanks.
 
Kevin
 
  On Tue, Nov 18, 2014 at 02:41:18PM +0800, Ben Woods wrote:
  
   Actually, the rsu(4) man page mentions the RTL8191SU chipset:
   https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
  
   And it appears to be in the code:
  
 http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_rsu.c?view=markup
  
   Are you sure it is not supported?
  
   Regards,
   Ben
  
  
   --
   From: Benjamin Woods
   woods...@gmail.com javascript:;
  
   On 18 November 2014 14:21, Ben Woods woods...@gmail.com
 javascript:; wrote:
  
There seems to be some misalignment with the official release notes,
 which
specifically mention the D-Link DWA-131 A1 is supported:
https://www.freebsd.org/releases/10.1R/hardware.html
   
However, according to this page it is the RTL8191SU chipset:
https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
   
Apparently the RTL8191SU chipset is supported by the OpenBSD rsu(4)
 driver:
http://www.undeadly.org/cgi?action=articlesid=20101216231634
   
Regards,
Ben
   
   
   
   
--
From: Benjamin Woods
woods...@gmail.com javascript:;
   
On 18 November 2014 13:56, Kevin Lo ke...@freebsd.org
 javascript:; wrote:
   
The RTL8191SU chipset is not supported.
   
Kevin
On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:

 I should mention I am running FreeBSD 10.1-RELEASE


 --
 From: Benjamin Woods
 woods...@gmail.com javascript:;

 On 18 November 2014 13:23, Ben Woods woods...@gmail.com
 javascript:; wrote:

  Hey guys,
 
  I am trying to get my D-Link DWA-131 A1 working, with some
 success
but no
  network connectivity.
 
  It shows up in my usb list with device id 07d1:3303. The driver
 pages
  suggest this should be working with the rsu(4) driver and
 potentially
  the rsu-rtl8712fw firmware, according to these:
  https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
  http://www.undeadly.org/cgi?action=articlesid=20101216231634
  https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
 
  I have added the following to /boot/loader.conf and rebooted:
  legal.realtek.license_ack=1
  rsu-rtl8712fw_load=YES
 
  It shows up in ifconfig, and even scans and finds wireless
 access
points.
  I have my WPA ssid and psk details for my access point stored in
  /etc/wpa_supplicant.conf. I can see from ifconfig that it is
 trying to
  associate with the correct access point ssid and do DHCP, but
 it never
  obtains an IP address.
 
  Has anyone had this issue before? Anyone know how can I go about
  troubleshooting this further?
 
  Regards,
  Ben
 
  --
  From: Benjamin Woods
  woods...@gmail.com javascript:;
 
 ___
 freebsd-wireless@freebsd.org javascript:; mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to 
freebsd-wireless-unsubscr...@freebsd.org javascript:;

   
   
   
   ___
   freebsd-wireless@freebsd.org javascript:; mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
   To unsubscribe, send any mail to 
 freebsd-wireless-unsubscr...@freebsd.org javascript:;
  
  ___
  freebsd-wireless@freebsd.org javascript:; mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
  To unsubscribe, send any mail to 
 freebsd-wireless-unsubscr...@freebsd.org javascript:;



-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Ben Woods]

Hmm... turns out this is an issue with authentication with wpa_supplicant.
If I turn off security I can connect just fine.

Other devices devices on my network are connecting fine with WPA2 AES PSK.
My wifi router is a TP-Link Archer D9 operating with both 2.4GHz and 5GHz.
I will go and try on another wifi network and report back if that works.

% sudo cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
ap_scan=1
fast_reauth=1
network={
ssid=MYSSIDHERE
key_mgmt=WPA-PSK
psk=MYPSKHERE
}

For the record, details of my wireless adapter:
% sudo usbconfig -d ugen2.3 dump_device_desc
ugen2.3: product 0x3303 vendor 0x07d1 at usbus2, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=ON (500mA)
  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x07d1
  idProduct = 0x3303
  bcdDevice = 0x0200
  iManufacturer = 0x0001  Manufacturer Realtek 
  iProduct = 0x0002  11n Adapter
  iSerialNumber = 0x0003  00e04c01
  bNumConfigurations = 0x0001

Any thoughts?

Regards,
Ben


--
From: Benjamin Woods
woods...@gmail.com

On 18 November 2014 16:32, Ben Woods woods...@gmail.com wrote:

 No worries :)

 Got any advice on how to diagnose why it's able to scan and lock onto the
 ssid (shows it in ifconfig), but not able to get an IP address with DHCP
 or communicate with a manual IP address?

 On Tuesday, November 18, 2014, Kevin Lo ke...@freebsd.org wrote:

 Argh! I think I need more coffee.  rsu(4) does support this chipset.
 Sorry for the noise.

 Kevin

 On Tue, Nov 18, 2014 at 03:08:37PM +0800, Kevin Lo wrote:
  I'm pretty sure.  See OpenBSD cvs log:
  http://marc.info/?l=openbsd-cvsm=128897633210060w=2
 
  I'll be fixing rsu(4), thanks.
 
Kevin
 
  On Tue, Nov 18, 2014 at 02:41:18PM +0800, Ben Woods wrote:
  
   Actually, the rsu(4) man page mentions the RTL8191SU chipset:
   https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
  
   And it appears to be in the code:
  
 http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_rsu.c?view=markup
  
   Are you sure it is not supported?
  
   Regards,
   Ben
  
  
   --
   From: Benjamin Woods
   woods...@gmail.com
  
   On 18 November 2014 14:21, Ben Woods woods...@gmail.com wrote:
  
There seems to be some misalignment with the official release
 notes, which
specifically mention the D-Link DWA-131 A1 is supported:
https://www.freebsd.org/releases/10.1R/hardware.html
   
However, according to this page it is the RTL8191SU chipset:
https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
   
Apparently the RTL8191SU chipset is supported by the OpenBSD rsu(4)
 driver:
http://www.undeadly.org/cgi?action=articlesid=20101216231634
   
Regards,
Ben
   
   
   
   
--
From: Benjamin Woods
woods...@gmail.com
   
On 18 November 2014 13:56, Kevin Lo ke...@freebsd.org wrote:
   
The RTL8191SU chipset is not supported.
   
Kevin
On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:

 I should mention I am running FreeBSD 10.1-RELEASE


 --
 From: Benjamin Woods
 woods...@gmail.com

 On 18 November 2014 13:23, Ben Woods woods...@gmail.com wrote:

  Hey guys,
 
  I am trying to get my D-Link DWA-131 A1 working, with some
 success
but no
  network connectivity.
 
  It shows up in my usb list with device id 07d1:3303. The
 driver pages
  suggest this should be working with the rsu(4) driver and
 potentially
  the rsu-rtl8712fw firmware, according to these:
  https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
  http://www.undeadly.org/cgi?action=articlesid=20101216231634
  https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
 
  I have added the following to /boot/loader.conf and rebooted:
  legal.realtek.license_ack=1
  rsu-rtl8712fw_load=YES
 
  It shows up in ifconfig, and even scans and finds wireless
 access
points.
  I have my WPA ssid and psk details for my access point stored
 in
  /etc/wpa_supplicant.conf. I can see from ifconfig that it is
 trying to
  associate with the correct access point ssid and do DHCP, but
 it never
  obtains an IP address.
 
  Has anyone had this issue before? Anyone know how can I go
 about
  troubleshooting this further?
 
  Regards,
  Ben
 
  --
  From: Benjamin Woods
  woods...@gmail.com
 
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to 
freebsd-wireless-unsubscr...@freebsd.org

   
   
   
   ___
   freebsd-wireless@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
   To unsubscribe, send any mail to 
 freebsd

D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Ben Woods]

Hey guys,

I am trying to get my D-Link DWA-131 A1 working, with some success but no
network connectivity.

It shows up in my usb list with device id 07d1:3303. The driver pages
suggest this should be working with the rsu(4) driver and potentially
the rsu-rtl8712fw firmware, according to these:
https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
http://www.undeadly.org/cgi?action=articlesid=20101216231634
https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1

I have added the following to /boot/loader.conf and rebooted:
legal.realtek.license_ack=1
rsu-rtl8712fw_load=YES

It shows up in ifconfig, and even scans and finds wireless access points. I
have my WPA ssid and psk details for my access point stored in
/etc/wpa_supplicant.conf. I can see from ifconfig that it is trying to
associate with the correct access point ssid and do DHCP, but it never
obtains an IP address.

Has anyone had this issue before? Anyone know how can I go about
troubleshooting this further?

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Ben Woods]

I should mention I am running FreeBSD 10.1-RELEASE


--
From: Benjamin Woods
woods...@gmail.com

On 18 November 2014 13:23, Ben Woods woods...@gmail.com wrote:

 Hey guys,

 I am trying to get my D-Link DWA-131 A1 working, with some success but no
 network connectivity.

 It shows up in my usb list with device id 07d1:3303. The driver pages
 suggest this should be working with the rsu(4) driver and potentially
 the rsu-rtl8712fw firmware, according to these:
 https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
 http://www.undeadly.org/cgi?action=articlesid=20101216231634
 https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1

 I have added the following to /boot/loader.conf and rebooted:
 legal.realtek.license_ack=1
 rsu-rtl8712fw_load=YES

 It shows up in ifconfig, and even scans and finds wireless access points.
 I have my WPA ssid and psk details for my access point stored in
 /etc/wpa_supplicant.conf. I can see from ifconfig that it is trying to
 associate with the correct access point ssid and do DHCP, but it never
 obtains an IP address.

 Has anyone had this issue before? Anyone know how can I go about
 troubleshooting this further?

 Regards,
 Ben

 --
 From: Benjamin Woods
 woods...@gmail.com

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Ben Woods]

There seems to be some misalignment with the official release notes, which
specifically mention the D-Link DWA-131 A1 is supported:
https://www.freebsd.org/releases/10.1R/hardware.html

However, according to this page it is the RTL8191SU chipset:
https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1

Apparently the RTL8191SU chipset is supported by the OpenBSD rsu(4) driver:
http://www.undeadly.org/cgi?action=articlesid=20101216231634

Regards,
Ben




--
From: Benjamin Woods
woods...@gmail.com

On 18 November 2014 13:56, Kevin Lo ke...@freebsd.org wrote:

 The RTL8191SU chipset is not supported.

 Kevin
 On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:
 
  I should mention I am running FreeBSD 10.1-RELEASE
 
 
  --
  From: Benjamin Woods
  woods...@gmail.com
 
  On 18 November 2014 13:23, Ben Woods woods...@gmail.com wrote:
 
   Hey guys,
  
   I am trying to get my D-Link DWA-131 A1 working, with some success but
 no
   network connectivity.
  
   It shows up in my usb list with device id 07d1:3303. The driver pages
   suggest this should be working with the rsu(4) driver and potentially
   the rsu-rtl8712fw firmware, according to these:
   https://www.freebsd.org/cgi/man.cgi?query=rsusektion=4
   http://www.undeadly.org/cgi?action=articlesid=20101216231634
   https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
  
   I have added the following to /boot/loader.conf and rebooted:
   legal.realtek.license_ack=1
   rsu-rtl8712fw_load=YES
  
   It shows up in ifconfig, and even scans and finds wireless access
 points.
   I have my WPA ssid and psk details for my access point stored in
   /etc/wpa_supplicant.conf. I can see from ifconfig that it is trying to
   associate with the correct access point ssid and do DHCP, but it never
   obtains an IP address.
  
   Has anyone had this issue before? Anyone know how can I go about
   troubleshooting this further?
  
   Regards,
   Ben
  
   --
   From: Benjamin Woods
   woods...@gmail.com
  
  ___
  freebsd-wireless@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
  To unsubscribe, send any mail to 
 freebsd-wireless-unsubscr...@freebsd.org
 

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org

Atheros 9285 unable to reset channel

[Ben Woods]

Hi,

I am trialling FreeBSD10-BETA2 in an attempt to find bugs etc. I am having
a problem with my Atheros 9285 wireless driver which I think might have
been around for a while (not new in 10), but I know a lot of work has been
done on these drivers in 10.

The symptom is I lose my wifi connection after the computer has been
running for some time and I get the following errors scrolling on my
terminal:
*ath0: ath_chan_set: unable to reset channel X (24XX MHz, flags 0xXXX), hal
status 14*

It looks similar to these 2 bug reports:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165543
http://www.freebsd.org/cgi/query-pr.cgi?pr=151198

Has anyone seen this before or have any ideas/suggestions of how I can
troubleshoot further? I am using wpa_supplicant and DHCP. If I reboot my
wifi works again for a few hours and then stops.

# pciconf -lv
ath0@pci0:1:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01
hdr=0x00
  vendor = 'Atheros Communications Inc.'
  device = 'AR9285 Wireless Network Adapter (PCI-Express)'
  class = network

# uname -a
FreeBSD sparticus.home.local 10.0-BETA2 FreeBSD 10.0-BETA2 #0 r257166: Sat
Oct 26 19:23:22 UTC 2013   r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
  amd64

# cat /etc/rc.conf
wpa_supplicant_flags=-sd
wlans_ath0=wlan0
ifconfig_wlan0=WPA DHCP

# cat /etc/wpa_supplicant.conf
network={
  ssid=SSID
  psk=PSK
}

# cat /var/log/dmesg.today
ath0: ath_chan_set: unable to reset channel 8 (2447 MHz, flags 0x480), hal
status 14
ath0: ath_chan_set: unable to reset channel 9 (2452 MHz, flags 0x480), hal
status 14
ath0: ath_chan_set: unable to reset channel 10 (2457 MHz, flags 0x480), hal
status 14
ath0: ath_chan_set: unable to reset channel 12 (2467 MHz, flags 0x680), hal
status 14
ath0: ath_chan_set: unable to reset channel 14 (2484 MHz, flags 0x2a0), hal
status 14
ath0: ath_reset: unable to reset hardware; hal status 14
pid 53465 (python), uid 972: exited on signal 6 (core dumped)

# cat /var/log/debug.log
wpa_supplicant[490]: wlan0: Event SCAN_RESULTS (3) received
wpa_supplicant[490]: Received 0 bytes of scan results (0 BSSes)
wpa_supplicant[490]: wlan0: BSS: Start scan result update 5935
wpa_supplicant[490]: BSS: last_scan_res_used=0/32 last_scan_full=0
wpa_supplicant[490]: wlan0: New scan results available
wpa_supplicant[490]: WPS: AP[0] 30:85:a9:e7:e4:10 type=0 tries=0
last_attempt=-1 sec ago blacklist=2
wpa_supplicant[490]: WPS: AP[1] 00:26:44:9a:d5:21 type=0 tries=0
last_attempt=-1 sec ago blacklist=0
wpa_supplicant[490]: WPS: AP[2] a4:b1:e9:9b:de:9e type=0 tries=0
last_attempt=-1 sec ago blacklist=0
wpa_supplicant[490]: wlan0: No suitable network found
wpa_supplicant[490]: wlan0: Setting scan request: 5 sec 0 usec
wpa_supplicant[490]: wlan0: Starting AP scan for wildcard SSID
wpa_supplicant[490]: wpa_driver_bsd_set_wpa: enabled=1
wpa_supplicant[490]: wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1


Thanks in advance!
-Ben
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org