> On Tue, Jun 25, 2013 at 08:18:48PM +0200, Philipp Marek wrote: > > I guess I found the reason: this device is not support by the > > default kernel, but needs the broadcom-sta module built. > > > > Trying with m-a a-i now, but I guess this bug can be closed. > > Right, the device listing in your report shows you had the 'wl' driver > loaded on 3.2. Although this doesn't seem to be a regression, it is a > bug (of a sort) that the free b43 driver doesn't support this WLAN > controller. On second thought, the bug might be that installing/booting a new kernel doesn't immediately causes m-a to run.
The problem is that _after_ booting the new kernel there might be no network connection (eg., if the wifi driver is dkms), and then there's no easy way to get the linux-kbuild, -headers, and/or (newer) source packages. Perhaps m-a should have an install trigger for _every_ kernel package, and at least ask whether to get current packages? (As a side note, I had to get the experimental broadcom-sta-modules-3.9-1-amd64:all 5.100.82.112-11+3.9.6-1 because of #711227.) Well, thanks all the same, I hope to get that working on the next reboot ;) Regards, Phil -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1090260129.5737.1372224327512.JavaMail.root@zimbra
