[08:35] <BenC> yeah, quad 1.65Ghz G5 cpu's is a bit faster at building kernels than my old 500Mhz G4
[08:35] <BenC> just a bit
[08:35] <ajmitch> nice
[08:36] <crimsun> thanks for the merges, BenC.
[08:36] <BenC> crimsun: thank you
[08:40] <BenC> platform        : pSeries
[08:40] <BenC> machine         : CHRP IBM,9123-710
[08:40] <BenC> pretty sure this is the first time we've had ubuntu on a pSeries
[08:41] <BenC> still need to figure out why I can run a fully installed system without problems, but the installer freezes
[02:33] <zul> heylo
[02:35] <ajmitch> hi zul
[03:27] <Petaris> hello
[03:28] <Petaris> I have installed a new kernel via apt but it is complaining that the modules.dep file has problems
[03:28] <Petaris> It also complains it cannot run depmod
[03:29] <Petaris> Is there a way to either bypass this or fix it?
[03:44] <Petaris> Hello ajmitch
[03:44] <zul> what kernel?
[03:45] <Petaris> zul: 2.6.15-26-amd64-k8
[03:45] <zul> hmm...
[03:46] <Petaris> just for kicks I tried the amd64-server kernel and it did it aswell
[03:50] <zul> did you compile your own kernel at some point?
[03:50] <Petaris> nope
[03:50] <Petaris> fresh install
[03:50] <zul> not sure...you might want to open a bug in launchpad
[03:51] <Petaris> hrm
[03:51] <Petaris> I should maybe note that the system has not completed its first reboot
[03:52] <Petaris> that is the reboot after initial install
[03:52] <Petaris> as it hangs
[03:52] <Petaris> so I used the install disk rescue mode
[03:52] <Petaris> mounted my drives and chrooted in to apt-get these kernels
[03:53] <Petaris> would that cause the issue?
[03:54] <Petaris> brb
[04:02] <Petaris> back
[04:55] <makx> Keybuk: around?
[08:43] <rodarvus> @now
[08:43] <rodarvus> argh. sorry
[09:02] <lamont> has anyone tried an edgy kernel on ia64 with ACPI_DEBUG=n?
[09:09] <zul> not me...but if you want to send me on my way i can ;)
[10:17] <zul> later


[11:22] <alan_g> greyback: I see you looked at this a few months back, maybe you recall? Do we still care enough to keep the bug around? https://bugs.launchpad.net/mir/+bug/1553328
[11:46] <greyback> alan_g: I actually have a fix up for that, was due to Qt renderer using threaded GL by default
[11:46] <greyback> alan_g: what I don't know is if Mir's default renderer would also exhibit the same issue
[11:47] <greyback> Mir's does use a renderer thread per display, and thus do threaded GL of some form.
[11:47] <alan_g> Oh, right. Well the default renderer runs a thread per display buffer, so that could indeed be a problem.
[11:48] <greyback> but it's hard to know how Qt hit that nouveau bug. Perhaps Mir's simpler renderer wouldn't hit it
[11:50] <alan_g> Maybe "incomplete" in Mir until we know.
[11:51] <greyback> *nod*