[12:23] <neuralis> zul: still getting an error unpacking xen-utils-3.0 on x86_64. 
[12:29] <zul> neuralis: what error?
[12:30] <neuralis> zul: it can't find module blkbk which causes xend to fail starting
[12:31] <zul> hmm...ok ill take a look
[12:31] <zul> can you do modprobe blkbk
[12:32] <neuralis> nope, don't have that module
[12:33] <zul> ok ill take a look soon
[12:33] <neuralis> no rush, thanks
[12:54] <BenC> mjg59: got it, thanks
[01:38] <_sah_> sorry if this is the wrong place to ask, but nobody else seems to be able to answer. Are there plans to add MPT Fusion SAS RAID support to the ubuntu-server kernel? If so, when? Thanks.
[01:40] <infinity> _sah_: modinfo mptsas
[01:40] <infinity> _sah_: What's wrong with that one?
[01:41] <_sah_> the kernel that ships with the ubuntu-server install CD does not support RAID on these devices. AFAIK the driver was updated somewhere between 2.6.15 and 2.6.16 and ubuntu ships with 2.6.15
[01:42] <infinity> Oh, you're talking dapper.  Check.  I did the above on an edgy machine. :)
[01:42] <infinity> Not sure how updating the fusion stack in dapper would/could destabilise OTHER fusion drivers, for the sake of new hardware support.
[01:43] <infinity> But that's not my call.
[01:43] <_sah_> yes, dapper
[01:44] <_sah_> who is the one to talk to about this? As dapper is being used as base for the LTS version, it would be nice to use that one.
[01:45] <infinity> BenC would be the man to discuss this with.  The Fusion stack is generally pretty stable, but doing large driver updates on a stable kernel is always risky.
[01:45] <infinity> Oh, he's only been idle 50 mins..
[01:45] <infinity> BenC: Ping.  Still around?
[01:47] <_sah_> Is there an email address I could use or a particular good time to contact BenC on this channel?
[01:51] <zul> you might want to start by opening a bug in launchpad
[01:55] <_sah_> it has already been filed as Bug #37452
[01:57] <_sah_> apparently no solution could be found back then. we are in exactly the same situation as described in the bugreport.
[01:58] <_sah_> I have no idea of how git, etc. works but if someone would give me some pointers on how to create a server install cd with a custom kernel I would be more than happy to give it a try.
[02:06] <_sah_> Have to go now. Thanks for your help so far.
[09:17] <zul> morning
[09:18] <fabbione> zul: didn't you go to sleep today?
[09:18] <zul> fabbione: yep i did..
[09:19] <fabbione> so what are you doing up at 3am?
[09:19] <zul> for the meeting
[09:19] <zul> besides katie is talking in her asleep again
[09:20] <fabbione> dude.. the only reason why you wake up at 3am is to either get laid or get a beer or watch porn while your wife talks in her sleep
[09:20] <zul> heh..or i cant sleep
[09:20] <fabbione> that's solvable with beer
[09:20] <zul> im beerless though
[09:33] <rodarvus> are you wineless too?
[09:35] <zul> i dont like wine
[09:36] <fabbione> he is also dickless^Wbrainless
[09:36] <fabbione> :P
[09:36] <zul> hah hah
[09:42] <zul> and xen is still stuck on 2.6.16
[09:42] <Mithrandir> you did some work on getting it up to .18, didn't you?
[09:42] <zul> yeah 
[09:42] <fabbione> xen sucks.. it will never get merged upstream
[09:43] <zul> heh i was playing with esx today
[09:43] <Mithrandir> fabbione: there appears to be a small bit of movement around it upstream.
[09:44] <fabbione> Mithrandir: yeah but most core kernel guys don't like it
[10:23] <zul> bbl
[04:10] <zul> BenC: i guess you dont have a 2.6.18 git lying around for edgy+1 do you?
[04:12] <makx> edgy is not based on 2.6.18 dooh
[04:22] <BenC> zul: I think edgy+1 will be 2.6.19
[04:23] <BenC> but to answer your question, no
[04:23] <zul> ok..
[06:24] <fabbione> BenC: fixed glibc have been uploaded.. just waiting knot-3 to be out for acceptance
[06:24] <fabbione> it also reduces the size of the initramfs of about 2.5MB on sparc
[06:24] <BenC> col
[06:24] <BenC> err, cool
[06:24] <fabbione> and that should make Niagara boot again
[06:24] <fabbione> (testint it right now)
[06:26] <fabbione> Loading initial ramdisk (6290368 bytes at 0x1FF800000 phys, 0x40C00000 virt)...
[06:26] <fabbione> old PHYS address
[06:26] <fabbione> we will still need to understand why it corrupts
[06:26] <fabbione> but this will give us a bit of time to do it
[06:27] <fabbione> [    5.145560]  checking if image is initramfs... it is                               
[06:27] <fabbione> score
[06:27] <BenC> I already know why, remember :)
[06:27] <fabbione> right, but we still need:
[06:27] <fabbione> a) understand why .15 can boot using the same PHYS
[06:27] <fabbione> b) get a fix ;)
[06:28] <fabbione> oh crap we also need to get infinity to kick silo back
[06:28] <fabbione> now the headers should be available for it to build
[06:28] <fabbione> but that's not really important
[06:28] <fabbione> .10 we have is basically .12
[06:28] <fabbione> and the rebuild didn't even boot
[06:55] <BenC> mjg59: ping
[06:56] <BenC> mjg59: Can you look at https://launchpad.net/bugs/53381, follow the linux bug, and tell me if we should be defaulting ec_intr to 0?
[06:59] <mjg59> I don't think so
[07:00] <mjg59> It breaks all sorts of other things
[07:01] <mjg59> Get him to retry with the new acpi code after the next upload
[07:28] <zul> BenC: ping another question for you
[07:29] <BenC> zul: shoot
[07:32] <BenC> mjg59: ok, thanks
[07:32] <zul> im going to be doing a xen-restricted modules which consist of the nvidia kernel module, and i was going to call the .ko file nvidia-xen does that sound reasonable?
[07:32] <Mithrandir> why not just let it still be named nvidia.ko?
[07:32] <BenC> zul: I suspect you don't need to do that, since the modules will be in a separate module directory anyway
[07:33] <zul> ah true...i didnt think of that
[07:33] <BenC> zul: why not just build it all out of the same lrm?
[07:33] <BenC> we can just add new flavours
[07:33] <Mithrandir> BenC: because lrm is restricted, xen is universe
[07:33] <BenC> add depends for the xen header packages
[07:33] <BenC> Mithrandir: so?
[07:33] <Mithrandir> BenC: restricted can't build dep on universe, afaik?
[07:33] <BenC> we can't have lrm build-dep on universe?
[07:33] <Mithrandir> ttbomk, no
[07:33] <BenC> that sucks :/
[07:33] <Mithrandir> not without putting it in multiverse
[07:34] <BenC> would xen make sense in multiverse?
[07:34] <Mithrandir> multiverse can build-dep on universe.
[07:34] <zul> i thought multiverse was for non-gpl stuff
[07:34] <Mithrandir> just not the other way around.
[07:34] <Mithrandir> zul: non-free, not non-gpl
[07:34] <zul> ah
[07:35] <Mithrandir> zul: else, we'd have to punt X and other stuff to multiverse, which would be a shame. :-)
[07:35] <zul> meh..
[07:36] <zul> you know what i meant :)
[07:36] <Mithrandir> yeah, I do
[07:50] <fabbione> BenC: up to room up for UDS?
[07:51] <BenC> fabbione: hell yeah
[07:51] <fabbione> done :)
[07:51] <fabbione> BenC: i will invite also David since it's close to where he lives
[07:59] <BenC> cool
[09:19] <zul> sparc is not being built on hoary is it?
[09:19] <Mithrandir> correct.
[09:19] <zul> ok..
[10:02] <Mithrandir> zul: you're working on xrm now?
[10:02] <zul> Mithrandir: im at work right now, but will fit some time into it tonight
[10:02] <Mithrandir> zul: do you want my preliminary stuff or is that useless for you?
[10:03] <zul> Mithrandir: that would be good it would give me a starting point
[10:04] <Mithrandir> I'mm make them work with the current xen from git then
[10:04] <zul> cool
[10:04] <Mithrandir> s/mm/ll
[10:05] <Mithrandir> and then put them somewhere
[10:05] <zul> Mithrandir: ill probably add a domU kernel as well this weekend
[10:06] <Mithrandir> zul: coolie.  I don't know if I'll have time for it, but maybe I'll get around to do the update-initramfs magic and such
[10:06] <zul> that would be super as well, but isnt that handle by kernel-package?
[10:06] <Mithrandir> apparently not
[10:07] <zul> hmm..
[10:30] <zul> right im heading home...later..
[10:31] <Philip5> what is the abi-file in /boot used for? and second... when i make a kernel from vanilla kernel source with make-kpkg i don't get a abi-file
[10:31] <Philip5> how do i make one and do i need one?