OpenWrt Forum Archive

Topic: RT-N66U and OpenWRT

The content of this topic has been archived on 28 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I'm having problems getting wireless working. When I try the brcmsmac driver, I get nothing. No SSID, nothing.

Even when I switch hwmode to '11n', it still does not work.

When I try the brcmsmac driver, I get the following error message:

[  437.030000] wl: module license 'unspecified' taints kernel.
[  437.040000] Disabling lock debugging due to kernel taint
[  437.080000] Unsupported BCMA bus type 0
[  437.090000] wl_glue: probe of bcma2:1 failed with error -22
[  437.090000] SSB/BCMA glue driver successfully attached

"Unsupported bus type..." and error -22. And yes, I've uninstalled b43

What can I do?

I need wireless-n support!

(Last edited by WizKid on 6 Oct 2015, 19:41)

Zajec wrote:

Check your wireless chipset and read a bit about available WiFi drivers:
https://wikidevi.com/wiki/ASUS_RT-N66U
http://wiki.openwrt.org/doc/hardware/so … fi_drivers

I've tried that, I've even installed nas. But it still gives me that error.

I know the RT-N66U uses the BCM4331. I can't use bcmsmac or b43 because I need 5ghz support.

The 'wl' and 'ilc' configuration tools can't even find the device.

But it is being recognized:

[    0.280000] pci 0000:00:01.0: [14e4:4331] type 00 class 0x028000
[    0.280000] bcma: bus1: Found chip with id 0x4331, rev 0x02 and package 0x08
[    0.430000] bcma: bus1: PMU resource config unknown or not needed for device 0x4331
[    0.620000] pci 0000:01:01.0: [14e4:4331] type 00 class 0x028000
[    0.630000] bcma: bus2: Found chip with id 0x4331, rev 0x02 and package 0x08
[    0.770000] bcma: bus2: PMU resource config unknown or not needed for device 0x4331

Per wl_glue.c, seems like the probed bus type does not match what it's expecting:

if (dev->bus->hosttype != BCMA_HOSTTYPE_SOC)
    {
        pr_err("Unsupported BCMA bus type %d\n", dev->bus->hosttype);
        return -EINVAL;
    }

Seems like the pci fixing the kernel is doing during boot is screwing with the bus type and/or PMU config.

Is there a way to disable pci device fixups on a per-device basis?

Any tips?

(Last edited by WizKid on 7 Oct 2015, 23:05)

WizKid wrote:

I know the RT-N66U uses the BCM4331. I can't use bcmsmac or b43 because I need 5ghz support.

So read again OpenWrt wiki page about broadcom-wl & BCM4331.

Zajec wrote:
WizKid wrote:

I know the RT-N66U uses the BCM4331. I can't use bcmsmac or b43 because I need 5ghz support.

So read again OpenWrt wiki page about broadcom-wl & BCM4331.

I have now, and I'm getting closer:

[   11.680000] wl: module license 'unspecified' taints kernel.
[   11.690000] Disabling lock debugging due to kernel taint
[   11.740000] SSB/BCMA glue driver successfully attached
[   11.740000] bcma: PCI: Fixing up device 0000:00:01.0
[   11.790000] wl0: 5.10.56.27 driver failed with code 11
[   11.790000] Memory leak of bytes 4076
[   11.800000] bcma: PCI: Fixing up device 0000:01:01.0
[   11.840000] wl0: 5.10.56.27 driver failed with code 11
[   11.850000] Memory leak of bytes 20

and here is my network config:

config wifi-device 'wl0'
    option type 'broadcom'
    option disabled '1'

config wifi-device 'wl1'
    option type 'broadcom'
    option disabled '0'
    option channel '161'
    option hwmode '11n'
    option txpower '16'

config wifi-iface
    option device 'wl1'
    option network 'lan'
    option ssid 'xyz'
    option key 'blah'
    option mode 'ap'
    option encryption 'psk2'

do I need to specify the pci device id path(s)?

(Last edited by WizKid on 8 Oct 2015, 19:08)

The discussion might have continued from here.