On 6 May 2015 at 21:55, David du Colombier <0in...@gmail.com> wrote: > However, now I'm sure the issue was caused by a kernel > change in 2013. > > There is no problem when running a kernel from early 2013. >
Welly, welly, welly, well. That is interesting.
