[05:01] <superm1> kylem, you around possibly?
[05:01] <kylem> yo
[05:02] <kylem> just about to wander off to watch tv,what's up?
[05:02] <superm1> awesome. well i wanted to just ask you quickly if something appears to be unionfs related to you
[05:02] <kylem> ok
[05:02] <superm1> and if so, if there is anything i can do to help debug / fix it, because its holding back our mythbuntu beta disk
[05:03] <superm1> if you look at https://launchpad.net/bugs/144395, we encounter issues at the same time as pitti
[05:03] <ubotu> Launchpad bug 144395 in linux-ubuntu-modules-2.6.22 "unionfs oopses for http processes" [Undecided,New]  
[05:03] <superm1> but we dont get a kernel oops necessarily 
[05:04] <superm1> problem is that its transient, and we'll just get a flat out hang of the process some times, an oops others, and functions others
[05:04] <kylem> hrm.
[05:04] <superm1> in an attempt to make sure it wasnt ubiquity or python-apt, i updated both on an older live cd session from before all the new unionfs stuff
[05:04] <superm1> and things appeared to work
[05:05] <kylem> yeah, it definitely looks like a unionfs bug. :(
[05:05] <kylem> sigh.
[05:06] <superm1> well anything i can do to help, just let me know.  its our last remaining issue for the disk :)
[05:06] <lifeless> is it just me, or is unionfs fragile ?
[05:06] <kylem> clearly it's just you
[05:06] <superm1> haha
[05:07] <kylem> superm1, i'll see if i can puzzle it out in the morning.
[05:07] <superm1> awesome thanks. 
[05:08] <superm1> i'll be on irc throughout the day if there is anything i can do to help
[05:08] <kylem> ok
[05:11] <reya276> I got a quick question? is Gutsy going to have the 2.6.23 kernal upon release
[05:12] <kylem> no.
[05:12] <kylem> 2.6.22
[05:13] <reya276> is it possible someone can help me create a custom kernel, because I need to get a Wacom Bamboo Tablet which will only work on 2.6.23 kernel
[05:13] <reya276> no one in the regular #ubuntu channel knows how to do it
[05:14] <IntuitiveNipple> reya276: https://wiki.ubuntu.com/KernelMaintenance
[05:14] <kylem> no, i don't have time to walk you through that. there's probably a document on the wiki that will help you.
[05:15] <reya276> kylem:maybe you can answer this for me, if I connect a USB device such as the named tablet should it not stay on?
[05:15] <kylem> 'stay on'?
[05:16] <reya276> yes the Tablet has a Circle which lights up when connected to the PC and it should stay on, but for some reason Ubuntu 7.04 disconnects it
[05:17] <mjg59> Should be fixed in gutsy
[05:17] <kylem> mjg59, autosuspend?
[05:17] <mjg59> Yeah
[05:18] <reya276> I have installed and configured the driver and when I check the driver is there but when I do "more /proc/bus/usb/devices" and it list the Wacon device it says "Driver=(none)"
[05:18] <mjg59> Sounds like the driver is broken
[05:19] <reya276> really, how can I remove it and then install it again
[05:19] <reya276> because maybe it was not installed correctly
[05:19] <mjg59> reya276: This isn't really the place to ask. I'd check if the driver provides a support forum.
[05:20] <reya276> ok, thanks
[05:22] <IntuitiveNipple> Building l-r-m and getting "FGLRXExtensions.c:16:35: error: X11/extensions/record.h: No such file or directory" but libxext-dev is installed; what libraries am I missing?
[05:23] <mjg59> x11proto-xext-dev
[05:23] <IntuitiveNipple> thanks :)
[05:23] <mjg59> Oh, no, x11proto-record-dev
[05:23] <IntuitiveNipple> I was thinking I'd got to go and try each one
[05:23] <IntuitiveNipple> hmm, no x11proto-record-dev listed, let me check
[05:25] <IntuitiveNipple> well, apt-get found that one, but synaptics wasn't listing it when I was browsing... now to solve these others
[05:35] <IntuitiveNipple> Hmm, building L-R-M it stops with "Makefile.inc:66: *** /usr/src/linux-headers-2.6.22-12-rt is missing, please set KERNELPATH. Stop." - is there a way to specify just one flavour (tried debian/rules binary generic) ?
[05:36] <IntuitiveNipple> Or, do I need to have all kernel flavours built to build L-R-M ?
[05:45] <IntuitiveNipple> OK... edited L-R-M's debian/rules and altered the flavours definitions for the ARCH (in this case x86_64), from "...,generic rt xen)" to "..,generic)"
[10:18] <Lure> any reason wy usg disk devices would not be detected if pluged during boot (it works if plugged in later)?
[10:18] <Lure> s/wy/why/
[10:28] <fabbione> Lure: events generated after all userland is started vs something discovered before userland is ready to "autodetect" / mount
[10:29] <Lure> fabbione: any way to rescan? currently I need to replug the devices
[10:29] <Lure> fabbione: also some users said it is regression compared to feusty (which I am not sure)
[10:29] <fabbione> dunno
[10:29] <fabbione> no it was in feisty too iirc
[12:37] <defcon_> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Flinville%2Fwireless-dev.git&a=search&h=rt2x00&st=commit&s=rt73 <-- why cant ubuntu use the updated driver because the old ones are flawed?
[12:37] <defcon_> im upset that ubuntu never fixed this problem
[12:37] <defcon_> ubuntu has rt73/ralink drivers that never worked properly for most people
[12:38] <defcon_> https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/34902 https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/146238
[12:38] <ubotu> Launchpad bug 146238 in linux-source-2.6.22 "Ralink Drivers do not work out of the box on Ubuntu Gutsy Beta" [Undecided,New]  
[12:39] <TheMuso> defcon_: Like cjwatson said in -devel, we get the point. He assigned the bug to a more appropriate package, and badgering people about it day after day is not likely to see it fixed any quicker.
[02:23] <zul> morning
[02:26] <amitk> interesting --> http://kerneltrap.org/Linux/CFS_Development_Tree_Backported
[02:26] <zul> amitk: yeah I already opened a bug about that ;)
[02:29] <zul> not
[02:43] <soren> Is there a simple way to see the diff between the ubuntu kernel and the vanilla one on which it's based?
[02:45] <zul> gitweb?
[02:45] <soren> zul: Yes, what about it?
[02:45] <amitk> soren: git log <Linus-tag> <Ubuntu-tag>
[02:46] <amitk> erm, git log <Linus-tag>..<Ubuntu-tag> 
[02:46] <soren> amitk: Ok. Which version are we based on anyway? 
[02:46] <amitk> soren: 2.6.22.9
[02:47] <soren> Oh, really?
[02:47] <amitk> soren: you can see the tags with 'git tag -l'
[02:47] <soren> amitk: Alright, thanks!
[02:54] <soren> amitk: I just cloned git://kernel.ubuntu.com/ubuntu/ubuntu-gutsy.git  and did a 'git tag -l' in the resulting directory.. It lists all the 2.6.22 rc's, but not the 2.6.22.x releases? 
[02:57] <rtg> soren: have you used gitk? It kind of shows the merge relationships.
[03:00] <soren> rtg: Uh, nice. didn't know about that.
[03:01] <rtg> soren: Its not too bad with a simple, almost linear tree. You should look at Linus main tree. Sometimes I get lost in all of the merge branches.
[03:01] <soren> Hm... There doesn't seem to be any delta between the vanilla kernel and ours in the lsilogic driver.. Odd. bug 140761
[03:01] <ubotu> Launchpad bug 140761 in linux-source-2.6.22 "Ubuntu 7.10 Alpha Gust OS does not recognize a lun with non zero target id on Vmware ESX Server" [Undecided,Confirmed]  https://launchpad.net/bugs/140761
[03:02] <rtg> soren: Gutsy is a superset of the vanilla kernel.
[03:04] <soren> rtg: Right. Nevertheless, the mpt* stuff in our kernel seems to be identical to the one in the vanilla kernel, which strikes me as odd considering the last comment on that bug.
[03:05] <rtg> now thats hard to believe :)
[03:07] <soren> I just (wrongly) assumed this was an lsilogic issue. It seems to affect all scsi controllers?
[03:15] <rtg> soren: That could well be. Is it a reasonable workaround to not use non-zero LUN's ?
[03:18] <soren> rtg: In vmware perhaps, but in real life I'm not so sure.
[03:18] <rtg> soren: right, they aren't exactly configurable in real life. 
[03:18] <IntuitiveNipple> I'm debugging some hibernate issues; Is there a kernel-function I can call to flush the buffer-cache late in the hibernate routines to ensure printk()s get captured even when the hibernate fails (the PC freezes prior to swsusp writing any data to disk)
[03:29] <pinskian> for openswan is there any change required at the router ? or just opening a port like openvpn is enough ?
[03:42] <pinskian> solved
[04:05] <pinskian> anyone awake
[04:08] <amitk> probably busy testing Gutsy Beta
[04:09] <pinskian> ah
[08:26] <rtg> mjg59: You around? Can you give me an opinion about the patch in bug #144336 ?
[08:26] <ubotu> Launchpad bug 144336 in linux-source-2.6.22 "ACPI acpi_scan_rsdp() breaks some PCs by not honouring ACPI specification" [High,Confirmed]  https://launchpad.net/bugs/144336
[08:31] <mjg59> rtg: Looks correct
[08:31] <rtg> mjg59: Thanks. I'll suck it in.
[08:40] <rtg> mjg59: I added your SOB to the commit.
[08:42] <mjg59> rtg: Thanks
[08:42] <zul> rtg: sob?
[08:42] <rtg> Signed off by
[08:43] <rtg> Its all in the context of how you use it, huh?
[08:45] <zul> yep
[09:00] <Lutin> hi there
[09:08] <rtg> kylem: Could you review bug #133666 ? I leery of applying this patch at this point in the development cycle.
[09:08] <ubotu> Launchpad bug 133666 in linux "please patch linux-source-2.6.22 to fix ata_piix bug" [Unknown,Fix released]  https://launchpad.net/bugs/133666
[09:08] <Lutin> could someone have a look at bug #129910 please ?
[09:08] <ubotu> Launchpad bug 129910 in initramfs-tools "tty[1-6]  are active but display nothing in Gutsy" [Critical,Triaged]  https://launchpad.net/bugs/129910
[09:09] <kylem> ok
[09:18] <maks_> kylem: can confirm that we load fbcon in scripts/init-top/framebuffer on the debian side
[09:18] <maks_> if fb is used
[09:20] <Lutin> maks_: the issue here is that it's not in the initramfs
[09:20] <maks_> hooks/kernelextras adds it for fbcon=y usage
[09:21] <maks_> (still disclaimer of the debian side ;)
[09:22] <Lutin> maks_: yeah, but here is the point :) in ubuntu the scripts for any *fb) module. which can't be found, as the framebuffer is not a module in gutsy :)
[09:22] <mjg59> Because somebody changed the config for no obvious reason
[09:23] <mjg59> BenC: I thought you were changing that back? :)