[01:11] <cwillu> lamont, probably missing firmware
[01:12] <cwillu> lamont, you should have relevant files in /lib/firmware
[01:12] <lamont> cwillu: it works with the lucid kernel, just not with the maverick one
[01:12] <cwillu> lamont, check the folder :p
[01:12] <lamont> OTOH, the gobi chip dislikes the lucid kernel
[01:12] <lamont> will do
[01:12] <cwillu> lamont, iirc, firmware is placed in a kernel-version specific folder
[01:13] <cwillu> although it doesn't have to be
[01:14] <lamont> now if I only knew what file I was looking for
[01:28] <cwillu> lamont, is there a firmware folder for the maverick kernel?
[01:28] <cwillu> actually, I might expect a message in dmesg about not being able to find it if that's the issue;  should probably check for that
[01:33] <lamont> it didn't look like it even found the device
[01:33] <lamont> but bigger fish to fry this evening, I'll worry more about it in a few days
[03:37] <miked595>  I'm running the i7-980x cpu. It should have 12 threads but cpuinfo only shows 8. http://pastebin.org/403849 not sure where to start. Running kernel 2.6.32-23-generic-pae #37-Ubuntu SMP Fri Jun 11 09:26:55 UTC 2010 i686 GNU/Linux
[04:40] <cwillu> do we have a silly compile-time constant limit set I wonder?
[05:01] <lamont> grep -c ^proc /proc/cpuinfo
[05:01] <lamont> 16
[05:01] <lamont> to be fair, that's a hardy machine
[05:01] <lamont> but I can't see lucid _reducing_ such a limit
[06:20] <cwillu> lamont, CONFIG_NR_CPUS=8
[06:20] <cwillu> so, yes, the limit was reduced :p
[06:21] <cwillu> lamont, looks like the 64 bit kernels use a higher limit
[06:22] <cwillu> config-2.6.32-22-generic:CONFIG_NR_CPUS=64 vs 8
[06:22] <cwillu> server kernel may or may not have a higher limit as well
[08:22] <zykes-> cwillu: yes opposed to being a module.
[08:23]  * cwillu_at_work scrolls up
[08:23] <cwillu_at_work> oh, the loop module
[08:23] <zykes-> yes, it makes using loop-aes a nightmare
[08:23] <cwillu_at_work> having it built-in?
[08:23] <cwillu_at_work> why?
[08:23] <cwillu_at_work> I'm pretty sure that sort of thing is the reason it's built in
[08:24] <cwillu_at_work> is loop-aes a replacement for loop?
[08:26] <zykes-> yes
[08:26] <zykes-> you replace the loop module with it
[08:26] <cwillu_at_work> if so, you should consider the wisdom of using a module which overrides standard functionality in order to provide some specific (and incompatible) behaviour
[08:27] <cwillu_at_work> having the module built-in means one doesn't have to do various insane things to allow the system to boot from an encrypted rootfs
[08:28] <cwillu_at_work> (i.e., you can't load the module if it's on the rootfs, unless you put in it initramfs, which is fragile, and unrecoverable without alternate boot media if it breaks)
[09:27] <TeTeT> when I place a custom kernel in a repo, e.g. linux-image-2.6.32-24-generic-pae, do I need to also add linux-image-generic-pae?
[09:38] <abogani> TeTeT, It isn't mandatory but it is more simpler to type when a user install it.
[09:40] <TeTeT> abogani: thanks
[10:51] <ogasawara> RAOF: a while ago you sent us an email about discussing common bug tags for X and the kernel
[10:51] <ogasawara> RAOF: is that something you'd still like to discuss?  And if so, we should all get together this week face to face.
[10:53] <RAOF> Yeah, I would still like that.  When's good?
[10:54] <ogasawara> RAOF: say 3pm-ish today?
[10:54] <RAOF> I think that'll be good.
[10:54] <RAOF> I'm booked with arm after lunch, but that shouldn't take too long.
[10:55] <ogasawara> RAOF: what room will you be in?
[10:55] <ogasawara> RAOF: or just come down to the kernel room
[10:55] <RAOF> Yeah, that'll work.
[10:55] <RAOF> I'll join you in the kernel room.
[10:55] <RAOF> I know where that is :)
[10:55] <ogasawara> RAOF: ack
[10:56] <ogasawara> JFo, apw: ^^ just fyi
[11:04] <JFo> sweet!
[11:04]  * JFo slaps lag_ around
[11:04] <JFo> :)
[11:05]  * lag_ beats JFo with his rhythm stick!
[11:05] <JFo> :-(
[11:05]  * JFo does not feel the love
[11:05] <lag_> JFo: <[11:06] <JFo> hahahahaha
[11:06] <JFo> lag_ == nsfw
[11:06] <JFo> ;)
[11:06] <lag_> We're at work?
[11:06] <JFo> hmmm. kind of
[12:41] <lamont> cwillu: I just needed a 2.6.35-compatible bcmwl.  Now I have wireless and cell-connected-happiness, too.
[12:50] <cwillu> \o/
[15:17] <amitk> apw: Could you send Mathieu to the Linaro room to debug a IGEPv2 problem?
[15:17] <cooloney> amitk: Mathieu is not in our kernel room now
[15:18] <cooloney> amitk: if i see him, i will ask him come
[15:20] <amitk> cooloney: thanks
[16:41] <hyperair> does anyone know why there's this annoying "+" appearing at the end of my packages all the time?
[16:41] <hyperair> and what's include/config/kernel.release? grep doesn't seem to show anything touching it, but that keeps getting created, with the + in the version
[17:11] <ogasawara> akgraner: do you know how to lock down a wiki page so it can't be modified?
[18:50] <komputes> I'm havin a problem with testing the mainline kernel. I have read https://wiki.ubuntu.com/KernelTeam/MainlineBuilds  and still have an issue.
[18:51] <komputes> I need linux >2.6.33 for TRIM support, so I added ppa:kernel-ppa/ppa and tried to install linux-maverick, yet that package is not found.
[18:56] <komputes> Separate issue - This bugs last comment http://launchpad.net/bugs/532451 suggests that there is a linux-backports-modules-2.6.32 package in lucid-proposed which corrects this issue. I am unable to find this package.
[18:56] <ubot2> Launchpad bug 532451 in linux-firmware (Ubuntu Maverick) (and 5 other projects) "Intel WiMAX/WiFi Link 6050 series wireless does not work (affects: 18) (dups: 1) (heat: 120)" [High,Fix released]
[20:23]  * abogani waves
[20:40] <abogani> apw, Please don't forget me! ;-)