[04:09] <jml> At the moment, 2.6.20-11.18 isn't booting on my macbook.
[04:09] <jml> answered my own question. never mind.
[04:37] <jml> out of curiosity, how do you get dmesg output out of a kernel that doesn't boot?
[04:38] <crimsun> digital photos, handscrawls, whatever it takes
[04:41] <jml> right. I can imagine that makes responding to bug reports kind of tricky :)
[04:45] <jml> I'm being bitten by bug 84964. Is the fix supposed to be in 2.6.20-11?
[04:45] <jml> (rather, I _think_ I'm being bitten by #84964)
[04:48] <crimsun> wait for 2.6.20-12.19
[04:55] <jml> will do.
[11:28] <Mithrandir> BenC: -12.19 FTBFS on ia64, fyi.
[12:14] <fabbione> hmmm annoying failure
[06:35] <BenC> Mithrandir: saw that, I'll fix it for post beta
[06:35] <BenC> might try pre-beta
[10:54] <frey> During boot, when fsck is running, I see some messages from udev, e.g. "specified group "nvram" unknown". Is this the right channel to ask or where else should I ask?
[10:55] <kylem> #ubuntu
[10:55] <frey> (I'm using feisty, so #ubuntu+1?)
[10:56] <kylem> sure.
[10:56] <frey> h
[10:56] <frey> thx
[10:56] <kylem> /etc/udev/rules.d/40-permissions.rules:89:KERNEL=="nvram",                      GROUP="nvram"
[10:56] <kylem> hmm
[10:56] <kylem> although i guess udev is our responsibility now.