On Fri, 2010-11-05 at 10:23 +0100, Didier 'OdyX' Raboud wrote: > tags 602444 -patch > thanks > > Hi Ben, and thanks for your answer, > > Le jeudi 4 novembre 2010 23:37:48 Ben Hutchings, vous avez écrit : > > On Thu, 2010-11-04 at 22:52 +0100, Didier Raboud wrote: > > > Package: firmware-brcm80211 > > > > What has this got to do with the firmware? > > The observable facts I could get is that: > > * the boot completes when the package is not installed True, but only because the driver fails to initialise. [...] > So my guess is that Network-Manager uses the driver, eventually triggering a > scan and then kernel oopses at that moment, leading to a non-completed boot. > Would you need more information ? Of what sort ? [...] Please use a serial console or netconsole to provide the 'oops' message. There have been a huge number of cleanups and other fixes to this driver since the initial release into staging, which I'll apply to our package. I hope these will fix this bug. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part