[03:30] <ntrfug> Good evening. Anybody home?
[07:30] <]Oscar> does the usb driver send a reset signal to peripherial while shutting down the pc?
[07:33] <alex_joni> :P
[08:11] <tjaalton> any known issues with virtualbox on .31? there are a lot of crash reports being filed against xorg-server, but the problem is somewhere else
[08:21] <tjaalton> bug 402800 is the master bug
[08:21] <ubot3> Malone bug 402800 in virtualbox-ose "Xorg crashed with SIGSEGV in <signal handler called>()" [Medium,Confirmed] https://launchpad.net/bugs/402800
[08:35] <tjaalton> heh, there are a lot of similar crashes, some have 30 dupes
[08:36] <tjaalton> quality
[14:40] <apw> rtg we should probabally ask what the pain point was, my understanding was that the versions being different for the arches was the issue
[14:41] <apw> that i lead to complex hand holding of the version mappings for d-i
[14:41]  * amitk nods
[14:41] <apw> i think if we have to source packages, we should just in the main aim to have them loaded at the same time
[14:41]  * rtg nods
[14:42] <apw> though i am thinking that maybe the amitk idea of mushing a merged tree at build time is interesting
[14:42] <rtg> apw, its worth discussing, but I'm leery...
[14:42] <apw> i will write them all up for next week so we can think on them
[14:43] <apw> yeah interesting but ultimatly a bit scarey
[14:53] <amitk> apw: the rebase script was supposed to be scarey too, but we ship it :-p
[14:54] <apw> heh yeah its a bit scarey but it occurs in my face and i can see the result
[14:54] <apw> the other options we never see the real source as seen by the compiler, whihc is scarier
[14:57] <rtg> amitk, how is 'UBUNTU: ARM: IMX51 ' for a patch subject?
[14:57] <amitk> rtg: you mean 'UBUNTU: ARM: DOVE' ?
[14:58] <rtg> amitk, I thought you wanted IMX51?
[14:58] <rtg> amitk, from your email: 'UBUNTU: ARM: IMX51: <description>'
[14:59] <amitk> rtg: IMX51 for the _Freescale_ patches. DOVE for _Marvell_ patches.
[14:59] <rtg> amitk, got it
[14:59] <amitk> rtg: I was just showing the pattern I used for Freescale
[15:10] <mjg59> Keybuk: The reason thermal and fan are in the initramfs was so that they're loaded before resume from disk is triggered
[15:11] <mjg59> Otherwise you'd overheat while doing that
[15:12] <mjg59> Obviously not a problem with stuff statically built
[15:12] <Keybuk> but they're loaded by udev *anyway*
[15:13] <maks_> not if not present?
[15:13] <mjg59> They weren't when it was originally implemented
[15:13] <mjg59> acpi didn't have modaliases
[15:13] <Keybuk> right
[15:13] <Keybuk> in hindsight, we should have fixed *that* instead
[15:14] <mjg59> Wel, yes
[15:14] <mjg59> Though that's true of many things
[15:14] <mjg59> I mean, rather than usplash I should have written KMS :)
[15:16] <Keybuk> damned straight
[15:16]  * mjg59 goes back to hating on USB
[15:23] <devinheitmueller> Hello all.  I spent the last few months working with Xceive to get their firmware licensed for distribution with Linux distros.  That's been done and it's in dwm2's linux-firmware git tree.  Aside from opening a launchpad ticket, is there anything I can do to facilitate getting this pulled into Karmic?
[15:23] <devinheitmueller> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/403642
[15:23] <ubot3> Malone bug 403642 in linux-firmware "Include xc5000 firmware in Karmic (now properly licensed)" [Undecided,New] 
[15:24] <devinheitmueller> woah, is there an echo in here?  :-)
[15:25] <rtg> pgraner, ^^ re: linux-firmware
[15:25] <pgraner> rtg: it will be ready for you next week. I'm running a bit behind 
[15:26] <rtg> pgraner, just wanted to make sure you noted it.
[15:26] <pgraner> devinheitmueller: no need for a bug, we will be pulling it in 
[15:26] <pgraner> rtg: I did will do it at the sprint
[15:26] <devinheitmueller> Wow, did I happen to walk into the middle of a conversation about my exact bug, or are you guys really that fast?
[15:27] <apw> they are that fast
[15:27] <devinheitmueller> pgraner: great.  Thank you very muhc.
[15:27] <devinheitmueller> s/muhc/much/
[15:27] <rtg> devinheitmueller, licensing has been a topic of some interest of late.
[15:28] <devinheitmueller> rtg: understandable.  It took several months to get this one straightened out, so it will be great to finally get it into the distros since it makes a half dozen Hauppauge/PCTV products work "out of the box".
[15:29] <devinheitmueller> Anyway, thanks for all your help guys.  I will keep my eyes open for the package update.
[15:29] <rtg> devinheitmueller, should be sometime next week.
[15:30] <rtg> certainly before Karmic releases
[15:30] <devinheitmueller> rtg: excellent.
[15:32] <devinheitmueller> On a separate note, is there an #irc archive for this channel?  I looked around and couldn't find one.  If so, could someone paste a link?
[15:34] <rtg> devinheitmueller, dunno. you might have to contact a freenode admin
[15:34] <devinheitmueller> ok, just curious.  thanks.
[15:34] <devinheitmueller> (I wasn't sure if you guys had a loggging bot setup)
[15:35] <rtg> apw, you've somehow acquired logs from #ubuntu-meeting. Are all channels logged?
[15:37] <apw> rtg? you mean i point to them in the meeting notes?
[15:37] <apw> i am not sure all are logged no
[15:37] <rtg> apw, ok, you know as much as I do :)
[15:37] <apw> i think the logger is ubuntulog user
[15:38] <apw> so if thats not on a channel its not logged, if it is is is
[15:39] <devinheitmueller> Ah, here we go:  http://irclogs.ubuntu.com/2009/07/30/
[15:39] <devinheitmueller> Great, thanks for the info.
[15:53] <awe> apw: ping
[15:53] <apw> awe hi
[15:56] <awe> apw: hey, i saw emails between you and stefan recently about wep module name munging in jaunty related to ipw2200
[15:56] <awe> just wondering if this may be a problem on karmic too
[15:56] <awe> ?
[15:57] <awe> just saw a bug report for a user on karmic who's having trouble with ipw2000; repeated disconnects when trying to associate to a wpa-psk AP
[15:57] <apw> awe karmic is ok as the munging is gone as of recently, rtg removed it cause modprobe is now sorted out and does the right thing in the face of the duplicate modules
[15:57] <awe> was it a problem at some point in karmic though?
[16:00] <rtg> awe, not to my knowledge. the last change remember making to ipw2200 was a module parameter default, but I think its upstream now.
[16:00] <apw> awe i don't remeber it being and issue
[16:01] <awe> rtg, apw: ok.  i asked for more information, but it looks to me like there still may be an issue with ipw2200 under karmic
[16:01] <awe> thanks for the 411
[16:02] <rtg> awe, you going to the wireless mini-summit in Sept?
[16:02] <awe> rtg: i plan to, but that depends on whether or not my boss(es) have other plans for me in sept
[16:03] <awe> i responded yes to john's email
[16:03] <rtg> awe, cool. hope to see you there.
[16:04] <awe> rtg: me too
[16:04] <awe> rtg: see you next week!
[17:10] <gnarl> awe, rtg There was a munging problem in Jaunty but that would prevent the wep crypto module from getting loaded at all
[17:11] <gnarl> Karmic should be fine with that as there is no munging done
[17:11] <awe> gnarl: thanks for the info!
[17:34] <rtg> bjf, just pushed some changes for Karmic arm topic branch which remove support for non-arm arches
[17:35] <rtg> bjf, there is likely to be one or 2 more once I figure out all of the packaging issues
[17:35] <bjf> rtg, ack