On Mon, Feb 12, 2018 at 03:22:32PM +, James Hogan wrote:
> On Mon, Feb 12, 2018 at 05:08:10PM +0200, Kalle Valo wrote:
> > James Hogan writes:
> > > On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote:
> > >> I bisected to this "first bad commit:"
> > >>
> > >>
On Mon, Feb 12, 2018 at 05:08:10PM +0200, Kalle Valo wrote:
> James Hogan writes:
> > On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote:
> >> I bisected to this "first bad commit:"
> >>
> >> commit 58eae1416b804d900014d84feadda7195007cc30
> >> Author: James Hogan
James Hogan writes:
> Hi Adric,
>
> On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote:
>> In the time between Linux 4.15-rc8 and -rc9, my wireless driver, b43,
>> would no longer load automatically. When I modprobe the b43 (and ssb)
>> modules, the device still
On Mon, 5 Feb 2018 13:14:28 -0500
Adric Blake wrote:
> In the time between Linux 4.15-rc8 and -rc9, my wireless driver, b43, would
> no longer load automatically. When I modprobe the b43 (and ssb) modules,
> the device still didn't appear in NetworkManager. Comparing the
Hi Adric,
On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote:
> In the time between Linux 4.15-rc8 and -rc9, my wireless driver, b43,
> would no longer load automatically. When I modprobe the b43 (and ssb)
> modules, the device still didn't appear in NetworkManager. Comparing
> the
In the time between Linux 4.15-rc8 and -rc9, my wireless driver, b43,
would no longer load automatically. When I modprobe the b43 (and ssb)
modules, the device still didn't appear in NetworkManager. Comparing
the kernel logs between working (4.14.16-lts) and nonworking (4.15)
kernels reveals that