[00:32] BenC: toshiboa.ko doesn't depend on ACPI, so in principle it provides functionality that isn't implemented elsewhere [00:33] In reality, I suspect Ubuntu doesn't cope with anything that old now [00:40] mjg59: do you have such machines? [00:42] BenC: Nope [00:43] They'd have to be <2000 [00:43] mjg59: would we be better off just using the stock toshiba_acpi module and getting rid of the acpi_hotkey argument in /etc/modprobe.d/? [00:43] Eh. Probably not yet. [00:44] It needs porting to input_polldev [00:44] Now there's something I'd be willing to do [00:44] You might want to get in touch with Daniel Silverstone [00:44] He was looking at a complete rewrite [00:45] last Daniel touched it was years ago [00:45] well, a little over a year at least [00:46] I just wish I had hardware to test, but I guess emailing a few lists with a patch would do [00:48] mjg59: Ok, if I were to write a drivers/input/misc/toshiba_btns.c driver, then we wouldn't need the patch to toshiba_acpi.c, right? [00:48] Yeah, he's been working on it again lately [00:49] I'll email Daniel first, but that seems like a suitable way to do it [00:51] Actually, we just wouldn't need the hotkey part...the rest of it for fan/lcd/video would still be usable [00:57] mjg59: I hate how toshiba_acpi's flagrant use of AE_* status codes in paths that have nothing to do with acpi :/ [00:57] Yeah, bonghits [00:57] In fact, it had module_init() returning AE_* status [00:58] Quality [03:44] mjg59: well that was easy...driver is written, but I don't have a table of the keys returned...so I'll shoot it over to daniel and hope he can fill it in [04:09] hi BenC , 2.6.26.2 is out [04:10] Kano, did you get a chance to look over the stuff I put in git? [04:10] Kano, is it sane to resolve the errors you were seeing? [04:10] superm1: nope,did try things with splashtop ;) [04:11] i can change the first menu also i added java 1.6 [04:13] btw. i used one acpi patch with seemed to help at least for one of the kanotix users [04:14] Kano: please stop doing that [04:14] http://lkml.org/lkml/2008/7/24/286 [04:14] Kano: I have a script that tells me that info, and I didn't name it Kano [04:14] patching kernels? [04:14] Kano: stop telling me when updates are out [04:14] BenC: well you take really much time usually to update... [04:15] Kano: there's good reason [04:15] Kano: but it's not because I don't know it's there [04:16] what do you think about that acpi thermal mini patch [04:18] do you know a solution for some xpress 1200 users which can not boot without acpi=off? === rikai_ is now known as rikai === superm1 is now known as superm1|away [10:11] Should I make a meta-package, for obtain linux-rt and linux-image-rt, on my own for -rt kernel? Or UKT can provide it via linux-meta ? [10:18] abogani: you'll have to do your own. But you can copy intrepid meta or port meta. [10:19] amitk: Ok. Thanks. === emgent is now known as pint === pint is now known as emgent [12:53] if anyone can answer this..... [12:53] what is going on with the realtime kernel in Intrepid? [12:56] AlmightyCthulhu: Under test through PPA. [12:57] ahhh, thanks, the repo still has 2.6.24 [12:57] that startled me [13:36] smb_tp: May i disturb you with one stupid question? [13:36] abogani, sure. though I don't think there are any stupid ones. [13:37] What is the best way to build test kernel for both i386 and amd64 archs? [13:37] As like you usually do for your test kernels (http://people.ubuntu.com/~smb/)? [13:37] A couple of pc? KVM on 64bit host? [13:37] Or what? [13:38] abogani, I normally use a 64bit host with -386 build chroot (well actually -am64 build chroot as well) [13:39] smb_tp: Thus without boot test. [13:39] ? [13:40] abogani, two machines would be faster but I am lacking hardware... Boot test depends sometimes on the changes. If I change drivers to hardware I don't have I sometimes skip it. [13:41] Right. [13:41] abogani, Otherwise I test the 64bit version on the build host and the 32bit one on a vm (can't use kvm since my machines are too old) [13:42] abogani, Or 32bit on the laptop but I normally try to preserve that [13:43] smb_tp: I hope that you never incur in a fs data lossbug [13:43] :-) [13:43] smb_tp: Last thing: What i should set to test kernel package to avoid conflicts? Seems to me that you set EXTRAVERSION, isn't it? [13:44] abogani, Guess if I change stuff on filesystems I would have to be extra careful. :) [13:44] :) [13:45] abogani, No not exactly. I use the debian method and only change the version number in the debian/changelog, recreate debian/control (if necessary) and run debian/rules [13:46] abogani, The EXTRAVERSION remains unchanged. [13:47] abogani, Numberwise i take the last released version and add some suffix [13:47] as like smb4? [13:47] abogani, yes exactly [13:48] abogani, like -19.37 -> -19.37smb1 [13:48] I understand. [13:48] Thanks a lot! :-) [13:48] abogani, No problem. :) [14:12] BenC: how about backporting ath5k from 2.6.27-rc2 as it support ar2007 like eee pc + adding ath9k [14:13] then madwifi is not needed -only if you would like to use it as ap [14:14] your madwifi is the wrong code anyway as only the hal branch would give additional device support === superm1|away is now known as superm1 === superm1 is now known as superm1|away === superm1|away is now known as superm1 [16:14] I incur in this error "EE: Missing modules (start begging for mercy)" during building ... How can resolve it? How can regenerate module list to avoid this type of error? [16:16] Obviously i have added two new modules. [16:20] abogani: actually, it sounds like you've removed some modules. [16:22] Yes you are right. [16:22] I have removed two modules also. [16:22] abogani: look in debian/scripts/modules-check. there are a couple of ways to work around missing modules. [16:23] s/modules-check/module-check/ [16:26] rtg: Thanks fro suggestion! I'll look at in. [16:27] s/fro/for [16:27] abogani: np === macd_ is now known as macd === asac_ is now known as asac [23:32] hi there. I have been struggling to get sound working with ubuntu, it works occasionally then disappears again. I filed a bug about six weeks ago but haven't had any triage on it. Is there someone I could contact to try and progress the bug? [23:33] it's bug 240628