=== smb_tp__ is now known as smb_tp [02:59] ello [03:00] is there any eta on including the driver for elantech touchpads? [03:33] I needs to shut this craptastic tap-to-click off! [03:33] * solarion goes crazy [06:27] 5~/c === wgrant_ is now known as wgrant [11:01] hi I know this might be off topic but I4ve been trying to figure out a way to solve my sound problem and I finally saw that there was a kernel fix for it : http://lkml.org/lkml/2008/8/4/110 [11:02] only I don't know how to apply a kernel fix [11:02] can anyone help me with that ? [11:12] zafy_: It is in the latest Intrepid git: commit 320dcc30f498e0 [11:12] so how do I apply it ? do I have to wait until intrepid comes out ? or is there a way to apply a patch in the mean time ? [11:12] IntuitiveNipple, ^ [11:13] patch to what? [11:13] hang on, don't reply! the windows here have gone funny [11:13] right... let's try again :) [11:15] IntuitiveNipple, I was wondering if there was a way to fix that problem without having to wait for Intrepid [11:15] lik patchin the kernel code and recomiling it i guess [11:15] only I don't know how to do that [11:15] *which* kernel code? [11:16] http://lkml.org/lkml/2008/8/4/110 -> isn't that a patch for the kernel ? [11:16] No, *which* kernel version do you want to patch? [11:16] Hardy? [11:16] Intrepid alpha? [11:16] I have Hardy [11:17] So, you want to know if commit 320dcc30f498e0 can be applied to Hardy? [11:17] yeah [11:17] OK... let me check [11:17] thanks === zafy_ is now known as zafy [11:35] zafy: The patch applies cleanly to the Hardy kernel, but as to whether it *works*, you'd have to test it of course [11:35] IntuitiveNipple, so i do i apply it ? [11:35] do you know a tutorial or a page that'll show me how ? [11:36] I suspect that might be a bit too advanced, but you can take a look at https://wiki.ubuntu.com/KernelMaintenance and the related Git guide. [11:44] IntuitiveNipple, Intrepid is coming out next month right ? [11:44] That's the plan [11:45] and it should be in there then ? [11:45] IntuitiveNipple, what happens if I patch the kernel ? Can I still upgrade to intrepid as normal ? [11:46] Kernel freeze is 16th October, so yes, it should be in [11:47] If you install a custom kernel (with the patch) it exists alongside the other kernel versions, it won't prevent any updates if you use the regular Ubuntu packaging system to install the custom kernel [11:54] cool [11:55] IntuitiveNipple, I'm not sure I see what I'm lookgin for on that page [11:55] I'm a pretty big n00b when it comes to that kind of things [12:08] IntuitiveNipple, ? [14:19] rtg: your changelog entry says that bug 263555 is fixed, but for some reason the bug in LP is still open. is that intentional or shall I close it? [14:19] rtg: (the e1000e thing) [14:21] mdz: lemme check. I've been watching upstream, but I'm not convinced they are converging on the correct solution. [14:31] mdz: I updated the status and comment for 263555. [14:35] rtg: thanks. I'm confused as to why Launchpad didn't automatically update it based on your changelog entry which referenced the bug number [14:35] mdz braindead ubuntoid? [16:37] laga: pushed aufs to git. Should be in next upload (after beta). Thanks for you work. [16:38] amitk: great. thanks for taking care of that :) [16:39] laga: in the end I decided not to 'clean up' the Makefile. It is ugly now, but makes it easier to update aufs. [16:39] yes, that's what i was thought [16:40] that and laziness. [16:41] is there any plan to "update" ath9k more? [16:41] I still find it pretty quirky and upstream always poitns to various wireless-testing commits to answer my concerns [16:42] in fact, it is quite unuseable when I am more than 20 feet from an AP [16:43] jdong: we'll likely end up doing a wireless-testing backport soon after Intrepid is released. [16:45] rtg: gotcha === asac_ is now known as asac [18:24] hi, how about using [18:24] http://thread.gmane.org/gmane.linux.kernel/738629 [18:24] instaed of external e1000? [18:24] e [18:26] those patches aren't in any main kernel branches yet, and some are purely for debugging purpoess [18:26] they are also largely untested outside of intel, so putting them in our kernel before the intel guys have even figured out where the bug is, seems pretty stupid [18:33] well the code to access the device with bad nvram would be really good to have.. [18:45] thats missing in the external module