ath0: could not map interrupt (again?)
Tim Chase
freebsd at tim.thechases.com
Thu May 3 02:28:16 UTC 2018
On 2018-05-02 23:21, Adrian Chadd wrote:
> CAn you try booting freebsd-head and see if it's any better?
At your advice, I created a boot image of 12.0-CURRENT r333017 but
see the same "could not map interrupt" in my dmesg that I got on 11.x
-tim
PS: thanks for the boot-from-a-memstick-snapshot suggestion...much
faster than the svn+buildworld+buildkernel I'd been trying.
More information about the freebsd-wireless
mailing list