[14:44] <ara> cr3 morning :-)
[14:45] <cr3> ara: morning, where's the heno man?
[14:46] <ara> cr3: ping him at #canonical, he should be there
[14:46] <ara> cr3: did you get the chance to fix the checkbox package bugs and reupload?
[14:54] <cr3> ara: I haven't done bug #257746 because it hasn't been affecting me but it will be necessary for intrepid, I'll do it today
[14:55] <ara> cr3: ok, thanks
[14:55] <ara> cr3: did you 'find' heno?
[14:57] <cr3> ara: yep, I wanted to show him all the test results since the dpkg fix. very cool!
[15:33] <onewhirled> Can you tell me what kernel options need to be set in order for wubi to boot?  I have loop and cryptoloop, ntfs and so forth.  The current Intrepid amd64 (for my intel core 2 duo) 2.6.27 based kernel doesn't boot, so I am trying to build my own.
[15:33] <onewhirled> I have already commented on a bug in launchpad on this issue, but would like to determine the possible problem with the current Intrepid kernel.
[15:33] <onewhirled> I have been building my own kernels for years, so I think my basic build configuration is sane.  I can boot the older 2.6.24 based kernels, but when I run lsmod and read the dmesg output, I don't immediately spot any significant difference between the 2.6.24 kernel and my build.
[15:34] <onewhirled> I have tried booting my own 2.6.27-rc6 kernel, but it is failing with the same error as the Intrepid kernel.
[15:34] <onewhirled> I have asked all this on in the ubuntu-kernel room, but gotten no responses.
[15:35] <davmor2> onewhirled: Wubi isn't working in intrepid at the moment bug https://bugs.edge.launchpad.net/wubi/+bug/268123
[15:36] <onewhirled> Okay.
[15:36] <onewhirled> Is this a Wubi issue or a kernel issue?
[15:36] <onewhirled> Thanks.
[15:37] <onewhirled> Will read up.
[15:37] <davmor2> bit of both we think.
[15:37] <davmor2> It seems to linked to how it mounts the drive and then virtual loop drive
[15:39] <onewhirled> Currently, I am seeing an error locating my kernel modules, and then I get the mount error.
[15:40] <onewhirled> I never see the particular message you put into the bug report.
[15:41] <onewhirled> The error I see says that (some long path to a UUID or somesuch) cannot be mounted.  I don't see the isodevice mentioned, afaicr.
[15:41] <davmor2> onewhirled: those are what happen if you try to mount the device once the kernel has failed so we could track down what was causing the issue
[15:41] <onewhirled> Ah, interesting.
[15:42] <onewhirled> Is there anything I can do to help with the debugging process?
[15:42] <onewhirled> has LKML been notified?
[15:42] <onewhirled> Or is the Wubi team working on it alone?
[15:43] <davmor2> Pass not sure who has been notified I think it is being worked on though by the guy the bug is assigned to
[15:43] <onewhirled> Okay.  Thanks for the info.  I will follow up with him.
[15:44] <davmor2> you can try xuvilon on #ubuntu-installer when he is available too
[15:44] <davmor2> he's the main wubi guy
[15:47] <onewhirled> Cool.  Do you know how I can capture the text on the screen, other that writing it down by hand or taking a photo of it?  I would like to add the output from my 2.6.27-rc6 kernel to the bug report.
[15:49] <davmor2> you can check out casper.log and also dmesg just mount a usb device and add the files to the usb device
[15:51] <onewhirled> Great.  I seem to be dropping to a initrd command line interface when the boot fails.  Is that right?  Or is it busybox?  I can run the mount commands from there?
[15:51] <onewhirled> I will poke around and try to figure it out.
[15:51] <onewhirled> I don't have much experience with Busybox.
[15:53] <davmor2> onewhirled: yes it's ash shell on the whole most of the commands you use in normal shell work like cat, ls, cd, cp, mv, mount etc
[15:55] <onewhirled> Great.
[20:03] <smb> ll