/srv/irclogs.ubuntu.com/2008/09/10/#ubuntu-testing.txt

=== persia_ is now known as persia
=== persia_ is now known as persia
aracr3 morning :-)14:44
cr3ara: morning, where's the heno man?14:45
aracr3: ping him at #canonical, he should be there14:46
aracr3: did you get the chance to fix the checkbox package bugs and reupload?14:46
cr3ara: I haven't done bug #257746 because it hasn't been affecting me but it will be necessary for intrepid, I'll do it today14:54
aracr3: ok, thanks14:55
aracr3: did you 'find' heno?14:55
cr3ara: yep, I wanted to show him all the test results since the dpkg fix. very cool!14:57
onewhirledCan 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
onewhirledI 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
onewhirledI 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:33
onewhirledI have tried booting my own 2.6.27-rc6 kernel, but it is failing with the same error as the Intrepid kernel.15:34
onewhirledI have asked all this on in the ubuntu-kernel room, but gotten no responses.15:34
davmor2onewhirled: Wubi isn't working in intrepid at the moment bug https://bugs.edge.launchpad.net/wubi/+bug/26812315:35
ubot5Launchpad bug 268123 in wubi "Intrepid: Wubi fails to mount sda1" [High,Confirmed]15:35
onewhirledOkay.15:36
onewhirledIs this a Wubi issue or a kernel issue?15:36
onewhirledThanks.15:36
onewhirledWill read up.15:37
davmor2bit of both we think.15:37
davmor2It seems to linked to how it mounts the drive and then virtual loop drive15:37
onewhirledCurrently, I am seeing an error locating my kernel modules, and then I get the mount error.15:39
onewhirledI never see the particular message you put into the bug report.15:40
onewhirledThe 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
davmor2onewhirled: 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 issue15:41
onewhirledAh, interesting.15:41
onewhirledIs there anything I can do to help with the debugging process?15:42
onewhirledhas LKML been notified?15:42
onewhirledOr is the Wubi team working on it alone?15:42
davmor2Pass not sure who has been notified I think it is being worked on though by the guy the bug is assigned to15:43
onewhirledOkay.  Thanks for the info.  I will follow up with him.15:43
davmor2you can try xuvilon on #ubuntu-installer when he is available too15:44
davmor2he's the main wubi guy15:44
onewhirledCool.  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:47
davmor2you can check out casper.log and also dmesg just mount a usb device and add the files to the usb device15:49
onewhirledGreat.  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
onewhirledI will poke around and try to figure it out.15:51
onewhirledI don't have much experience with Busybox.15:51
davmor2onewhirled: 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 etc15:53
onewhirledGreat.15:55
smbll20:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!