Re: bwn updates - now BCM4321, BCM4322
hi, I'll go add some more debugging to the attach side of things. It does that when it doesn't recognise the phy, and that's silly. -adrian On 28 May 2016 at 06:34, Björn Jonarewrote: > Hi, > > First let me say that I very much appreciate your work on bwn. Broadcom > devices are, alas all too common :( Anyway I dug an old iMac out of storage > and installed a recent CURRENT (r300836) since I knew the wifi chip in it to > be some variant of the BCM4322. > > After uncommenting all needed lines (?) in the Makefile regarding GNU PHY > support I loaded bwn_v4_ucode, bwn_v4_n_ucode and if_bwn. Upon checking > dmesg I got this: > > siba_bwn0: mem > 0xd020-0xd0203fff,0xd000-0xd00f irq 17 at device 0.0 on pci3 > siba_bwn0: warn: multiple PCI(E) cores > siba_bwn0: unsupported coreid (USB 1.1 Host) > bwn0 on siba_bwn0 > bwn0: failed > device_attach: bwn0 attach returned 6 > > > > So, the driver doesn’t attach :( > > Since my understanding of drivers is well, lacking, is there anything I could > do to get this specific version of BCM4322 to work[1]? I would be glad to > provide any information needed. > > > [1] That is to get the driver to attach. I have no illusions regarding > functionality, this is after all a Broadcom chipset! > > > -- > /Hälsningar Björn > > > > On Thursday 19 May 2016 at 09:01, Adrian Chadd wrote: > >> Hiya, >> >> I managed to get the BCM4321 and BCM4322 working. You need to load >> bwn_v4_n_ucode for BCM4322 and then it should "just work". >> >> BCM4321 also works on bwn_v4_n_ucode - it uses the same newer ucode API. >> >> You can't load bwn_v4_n_ucode and bwn_v4_lp_ucode just yet - I need to >> address that. >> >> Let me know if you can test out either of these chips! >> >> >> -adrian >> ___ >> freebsd-wireless@freebsd.org (mailto: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 >> (mailto:freebsd-wireless-unsubscr...@freebsd.org)" > > > > ___ > 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" ___ 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"
[Bug 193628] Marvell 88W8335 wireless NIC not enabled by malo(4) or ndis(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193628 --- Comment #12 from Juan Ramón Molina Menor--- Oh Adrian, sorry, you were right: I've been building from sources on a faster computer and installing on different ones via NFS mounts for months without issues, but somehow this is not compatible with building directly the malofw kernel module in the target computer. As soon as I downloaded source and built the kernel in this computer the malofw loaded and the Wi-Fi is working. I didn't even need to rebuild the module itself! Well, now it works but I cannot say I understand why... -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ 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: bwn updates - now BCM4321, BCM4322
Hi, First let me say that I very much appreciate your work on bwn. Broadcom devices are, alas all too common :( Anyway I dug an old iMac out of storage and installed a recent CURRENT (r300836) since I knew the wifi chip in it to be some variant of the BCM4322. After uncommenting all needed lines (?) in the Makefile regarding GNU PHY support I loaded bwn_v4_ucode, bwn_v4_n_ucode and if_bwn. Upon checking dmesg I got this: siba_bwn0: mem 0xd020-0xd0203fff,0xd000-0xd00f irq 17 at device 0.0 on pci3 siba_bwn0: warn: multiple PCI(E) cores siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: failed device_attach: bwn0 attach returned 6 So, the driver doesn’t attach :( Since my understanding of drivers is well, lacking, is there anything I could do to get this specific version of BCM4322 to work[1]? I would be glad to provide any information needed. [1] That is to get the driver to attach. I have no illusions regarding functionality, this is after all a Broadcom chipset! -- /Hälsningar Björn On Thursday 19 May 2016 at 09:01, Adrian Chadd wrote: > Hiya, > > I managed to get the BCM4321 and BCM4322 working. You need to load > bwn_v4_n_ucode for BCM4322 and then it should "just work". > > BCM4321 also works on bwn_v4_n_ucode - it uses the same newer ucode API. > > You can't load bwn_v4_n_ucode and bwn_v4_lp_ucode just yet - I need to > address that. > > Let me know if you can test out either of these chips! > > > -adrian > ___ > freebsd-wireless@freebsd.org (mailto: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 > (mailto:freebsd-wireless-unsubscr...@freebsd.org)" ___ 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"
[Bug 193628] Marvell 88W8335 wireless NIC not enabled by malo(4) or ndis(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193628 --- Comment #11 from Juan Ramón Molina Menor--- Thanks Adrian, but this is exactly what I’ve done: set up the new system from CURRENT sources then build the firmware module. I have rebuilt it again for good measure with the same result. Even moved the card to another PCI slot. Do you happen to know how to obtain more detailed info than the following dmesg output after kldload malofw.ko? KLD malofw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type I don’t know if it’s relevant, but I have also built the NVIDIA kernel module, which also depends on kernel sources, and it loads and work as expected. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ 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"