[03:05] <lifeless> hi
[03:05] <lifeless> whose around ?
[03:06] <lifeless> CONFIG_BLK_DEV_IO_TRACE is not enabled in Feisty; is it in gutsy, or are there plans to do so? the blktrace program is unusable without it.
[03:06] <lifeless> (at least, to the best of my knowledge)
[08:35] <kraut> moin
[09:36] <kraut> is there no REGPARM support anymore in the feisty-kernel?!
[09:38] <Mithrandir> grr, obexftp or bluetooth reliably hangs my x40 with the feisty kernel.
[09:40] <kraut> ah, REGPARM is default now, nice.
[10:54] <ivoks> is it only me or others are havin problems with git? fatal: unexpected EOF
[10:54] <ivoks> doh.. never mind
[11:20] <abogani> it works for me
[11:20] <ivoks> yeah... my mistake
[01:15] <shawarma> Any objections to adding DAC960 to the "most" list of modules in initramfs ? ( http://launchpad.net/bugs/31035 )
[01:23] <maks_> done since long afair
[01:23] <maks_> initramfs-tools (0.75) unstable; urgency=high
[01:23] <maks_> and feisty adds all the drivers/block subdir
[01:24] <maks_> so you can close the bug as resolved shawarma
[01:24] <maks_> i do wonder why we still hardcode the net drivers list, any reason for that BenC?
[01:25] <maks_> (there might have been size consideration?)
[01:26] <fabbione> maks_: mostlikely because root over nfs is not very common and it doesn't make sense to pull in all possible network driver in the initramfs
[01:26] <fabbione> while you want to be able to boot from any kind of block device.. always
[01:27] <shawarma> maks_: So it does. My bad. Thanks!
[04:12] <pinch150g> I was told to ask here by folks in the #edubuntu if you might be able to help me figure out what is going on with my boot up from a CD
[04:12] <pinch150g> Here is the problem
[04:13] <pinch150g> I get the following error:
[04:13] <pinch150g> end_request: I/O error, dev fd0, sector 0 (Multiple Times)
[04:13] <pinch150g> then
[04:13] <pinch150g> /bin/sh: cant access tty; job control turned off
[04:13] <pinch150g> Then it hangs after
[04:13] <pinch150g> sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
[04:13] <pinch150g> Do I need to load some other controller drivers before I can boot?
[04:14] <pinch150g> If you can't help, can you guide me to someone who can?  I have looked on the ubuntu forums and tried everything--no good!
[04:17] <pinch150g> Anyone?
[04:18] <pinch150g> Is there anyone here?
[04:20] <pinch150g> Hello?
[04:24] <pinch150g> Is anyone available to answer a question?
[04:28] <pinch150g> Anyone there?
[04:35] <pinch150g> Hello?
[04:41] <rtg> pinch150g: Go through the Launchpad process. I suspect your bug is a duplicate. https://bugs.launchpad.net/ubuntu
[04:43] <pinch150g> I already checked there and saw that it was there multiple times.  I can't seem to get any of the work arounds to work for me.
[04:44] <pinch150g> I'm checking for updated Intel 82801BA chipset drivers to see if that fixes the problem
[04:46] <pinch150g> rtg: thanks
[09:53] <lifeless> morning
[09:54] <lifeless> BenC: around perchance?
[09:54] <BenC> lifeless: yeah
[09:54] <lifeless> CONFIG_BLK_DEV_IO_TRACE is not enabled in Feisty; is it in gutsy, or are there plans to do so? the blktrace program is unusable without it.
[09:55] <lifeless> I'd like to use blktrace in bzr performance work, it looks like it would be useful.
[09:56] <BenC> lifeless: it isn't, but if you could file a bug against linux-source-2.6.22 I'll look into it
[09:56] <lifeless> thanks I'll do that
[10:05] <lifeless> BenC:  https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/118303
[10:09] <lfittl> BenC: are the patches for Mobile IPv6 in the gutsy kernel? http://www.linux-ipv6.org/umip-0.3-ann.html.en
[10:17] <BenC> lfittl: if they aren't upstream, then no
[10:17] <BenC> lifeless: thanks
[10:17] <lfittl> BenC: any chance that you could take a look at them (not much code), and merge them?
[10:18] <BenC> lfittl: There's no way I can include a patch that touches that much code
[10:19] <BenC>  21 files changed, 914 insertions(+), 91 deletions(-)
[10:19] <BenC> that's way over my "trivial" threshold :)
[10:21] <lfittl> hm, I see, anything I could do to convince you? (I just want to avoid compiling a custom kernel for multiple machines)
[10:21] <lfittl> e.g. testing
[10:21] <BenC> No, there's a strict don't-muck-with-upstream-where-possible guideline for stock kernel
[10:22] <lfittl> ok, so getting it into mainline is the only way?
[10:23] <BenC> pretty much
[10:23] <BenC> these patches are against 2.6.21-rc5...you sure it isn't in 2.6.22-rc3 yet?
[10:24] <lfittl> not completely, I will check that, thanks