On Fri, 2010-02-26 at 12:38 +1100, Gerry Butler wrote: [...] > > you seem to confuse firmware and drivers. > > and rtl8168d can not be related to booting unless you are > netbooting, > > which i kind of doubt. > > I know that rtl8168d is the Realtek firmware, but nevertheless the apt > log used the terminology "driver not available". > > The freeze that occurs early in the boot process for 2.6.32, even > before syslog is open, clearly has nothing to do with the Realtek; (as > you say, I'm not booting from a network), and probably nothing to do > with hpet.c; so that's an entirely different problem. There is a known bug in firmware loading that can lead to a 1 minute delay in the boot process. Did you wait that long? Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett
Attachment:
signature.asc
Description: This is a digitally signed message part