=== asac_ is now known as asac === pwnguin is now known as jldugger === jldugger is now known as pwnguin [02:40] Can anyone tell me what this from my dmesg is being caused by? http://dpaste.com/59176/ 2.6.24-19-server === jeff__ is now known as SEJeff_home === pgraner__ is now known as pgraner === dhaval is now known as dhaval_away [13:39] hi BenC , i wanted to compile, but then o gut makedumpfile - command not found. what is that tool and whats the package name? [13:44] i do not even find a makedumpfile package for intrepidß [13:50] ok, found it in launchpad, but not with packages.ubuntu.com === pgraner__ is now known as pgraner [14:00] hi [14:00] i tested 2.6.26-rc8 and i get tty_wakeup errors on connecting through the connect.sh script [14:21] BenC: in lrm you made one space too less in the changelog [14:24] also dont forget -3 [14:29] Kano: -3 isn't going out until alpha 1 is out [14:29] Kano: and I'd appreciate if you didn't bark out orders to me [14:30] Kano: makedumpfile is in universe, and it's used to create a vmcoreinfo file so that we can easily capture crashdumps without have a full linux-debug-image installed [14:31] could you fix lrm [14:34] BenC: dont you think it has to be in main when you use it for the kernel? [14:39] Kano: it has to get moved by an archive admin, which is in-progress [14:39] well i put it in my repository [14:39] now i only want to be able to comple lrm to try it [14:40] what are you talking about in lrm? [14:40] the changelog [14:40] a) you missed one space [14:41] in the ABI Bump line in front of the * [14:41] also i still did not get why you need a tab in front of all? [14:42] last change would be a 2nd abi bump [14:49] well it seems i have to disable that uvesafb, i dont know how to use it... [14:49] CPU[Dual Intel Core2 6600 @ clocked at 1600.000 Mhz] Kernel[Linux 2.6.26-3-generic i686] Up[-11min-] Mem[-115.7/2023.4MB-] HDD[-760GB(13%used)-] Procs[-150-] Client[Konversation 1.0.1] [14:51] make sure that the v86d helper is installed and executable [14:51] hmm [14:53] is there a package with it? [14:53] or how to you use uvesafb? [15:45] gspca still missing [15:59] also how to build only the firmware package from lrm? [16:07] ok, found it myself, binary-indep... [16:18] hmm using the /lib/firmware dir creates bad dependency problems [16:19] conflicts with ivtv-utils, or did you strip the firmware out of it? [16:22] hmm looks like [16:33] why does the package with the firmware depend on binutils-static? [16:41] what IDE do most of you use? [16:41] ..if any.? === Jay-home is now known as Jay-laptop [17:16] BenC: ping [17:16] bdmurray: yo [17:16] BenC: Its not clear to me why my PS3 won't boot 2.6.24. I can't find any bug reports or anything but vague forum posts. [17:18] bdmurray: I know it wont, but I forget why...ps3 guys are working on intrepid (linux-ports) though [17:18] bdmurray: mine is still running gutsy [17:19] I successfully upgraded to Hardy just can't run that kernel. I'm not sure what to do with Ubuntu on it anyway though. [17:46] bdmurray: download the cell enabled distributed.net client and crank out some hashes :) [17:47] ps3 is really only useful as a cell development platform, IMO [17:47] BenC: heh, I'd have to fight with the kids for access to it [17:48] my ps3 mostly just sits on the folding@home client [17:48] and some guitar hero III every now and then [17:48] I use it as a blueray player more than anything else :) [17:48] I haven't gotten the remote yet, do you need it? [17:49] Nope, just use the controller [17:50] Oh, sweet! You think I would have just tested it. [17:51] buying blueray movies means I have the benefit of telling people no when they ask to borrow movies now [17:51] that will only last but so long though [17:51] heh [18:26] hi [18:27] is there a kernel patchset somewhere to better support intel atom processors? (frequency scaling for example) [18:31] lapo: send a note to Oliver Grawert ogra@canonical.com. He has recently been working on an Atom based unit. [18:33] rtg: thanks I'll do it [19:07] doesn't mid better support atom? [19:10] so lemme get this right, is MID gonna be for mobile phones/smartphones someday? almost an alternative to windows mobile? [19:18] Tophat: MID is targeted towards netbook class devices, e.g., those with a somewhat smaller display. [19:18] eeepc type deal? [19:19] right, displays that require reformatting of applications. [19:19] right on. thanks mate [19:19] is there any plans to do an ubuntu for phones? [19:20] Tophat: there is an Ulta-mobile project, but don't think its targeted at phones because of the telco stack required. [19:21] rtf - excellent ty mate [19:24] rtg - you use any IDE for kernel stuff? [19:24] Tophat: other then vi? [19:24] sure [19:25] Tophat: the only other editor I occasionally use is Visual SlickEdit [19:25] but no IDEs per se [19:26] right, i was just hoping to find a GUI editor for working on the wireless b43 [19:27] Tophat: well, vs is pretty good, but it does cost money. [19:27] what are you looking for in an IDE? if all you want is codingstyle enforcement, kwrite, gedit, emacs, anything will do the job given the proper configuration [19:28] mkrufky - something with a side panel that i can have multiple files open and easy to navigate them all. something easier than having a million terminal windows open [19:28] gedit supports tabs [19:32] right on thanks mate. dunno why i haven't tried it before... >< [19:33] :-) [19:34] I been using gedit for this stuff a lot more now that I've basically moved most of my machines to Ubuntu [19:34] On a KDE machine I might use kwrite instead [19:34] and i always use emacs when Im in a text shell over ssh [19:35] kwrite is nice, it lets you expand and collapse functions, prototypes, structures, #defines, etc [19:42] mkrufky: so does vim :) [19:48] yes, i never really used vim much ... [19:48] but i hear its the best [20:13] SciTE can do the expand/collapse stuff too ;) [21:33] hi [21:34] what kernel should I run on my old pentium firewall:) I was running -386 but the hardy one doesn't. [21:34] dapper [21:35] lifeless: what does that mean, the hardy one doesn't? [21:35] uhm, I'm not entirely sure - something about 'cannot read system configuration' or 'no configuration found' [21:36] then it appears to go away into lala land [21:36] I've just plugged a monitor and keyboard in, so I can dig further - but I'll go offline during reboots :) [21:36] lifeless: what is the latest release that works? [21:37] I booted 2.6.15-23-386 #1 PREEMPT Tue May 23 13:49:40 UTC 2006 i586 GNU/Linux [21:37] and it worked [21:37] its the most recent kernel before the one the hardy upgrade installed [21:37] (that is on the machine) [21:37] lifeless: then why wouldn't you stay with dapper? [21:37] rtg: dappers old, hardies shiny [21:38] lifeless: dude, this is a firewall. [21:38] if it works, then don't fix it. [21:38] rtg: yes, which is why it was still on dapper; but isn't dapper about to go out of support? [21:39] lifeless: wasn't released five years ago yet :-) [21:39] lifeless: 2 more years yet. I'm actively maintaining it as we speak. [21:39] anyhow, I figured I may as well be one of the pre '8.4.1 is a candidate upgrade' folk [21:39] hmm. warty wasn't released five years ago :-O [21:40] rtg: I'm not stressed by this, there is no urgency - I've changed the default kernel. But if its not my machine, or if -386 is expected to load on a model name : Pentium 75 - 200 [21:40] then I can potentially save other folk some grief when they do upgrade [21:41] lifeless: I think I have some machines of that vintage. [21:41] lifeless: you leave your firewall alone and I promise to do some -386 testing. After all, we'd miss your shiny presense if it gets trashed :) [21:41] rtg: :) [21:42] rtg: thank you ; if you want any sort of tests run by me just let me know [21:42] lifeless: in the meantime dapper is scheduled for some CVE updates. [21:42] rtg: should I file a bug at this point? (I'm guessing not as I have no real data to give ...) [21:42] rtg: kernel ones? [21:43] lifeless: yeah - unless you can capture a screen or something, the bug report won't be worth much [21:43] rtg: [apt is pointing at hardy now; but I can grab dapper kernels...] [21:43] lifeless: yes - kernel updates. still several days away. [21:43] rtg: I'll keep an eye out. Unless its remote-exploit its low stress for me on this box [21:43] lifeless: are you running hardy userspace with a dapper kernel? [21:44] rtg: I think so [21:44] lifeless: huh, I'm surprised udev works. [21:44] rtg: imagine me chortling [21:44] rtg: it was my 'oh damn it doesn't boot; ok lets try a previous kernel' reaction [21:45] lifeless: seems like a reasonable approach. [21:46] I'll install the dapper upgrade when it comes out, and take a photo of the hardy fail at the same time [21:46] thanks heaps [21:46] lifeless: k === rikai_ is now known as rikai [23:37] rtg: hey [23:50] kirkland: dude [23:51] rtg: you wanna quit sending kernels to your ppa long enough for me to get one installed? :-) [23:51] kirkland: its like a daily event :) [23:51] rtg: :-) [23:51] rtg: it takes FOREVER to build [23:51] I deleted all the kernel packages while this one is building. [23:51] rtg: so I've tested the Intrepid kernel, and it does NOT suffer from the ecryptfs bug [23:52] rtg: yeah, I know ;-) [23:52] rtg: i'm still trying to verify that cherry picked fix [23:52] kirkland: ok, I'll upload the other packages as soon as the kernel build is done. [23:52] rtg: i tried it yesterday, and it didn't look like it solve the problem, but I'm not sure I if I pulled the right package or not [23:52] kirkland: I suspect you did. [23:53] kirkland: I know for sure one has that patch [23:53] rtg: i mean, would that fix have been in the linux-image-generic package, or one of the LUM (and friends)? [23:53] s/one/this one/ [23:53] rtg: ie, ecryptfs is built as a module [23:54] linux-image-generic, its a core kernel patch, wasn't it? yes - i'm sure it was. [23:54] rtg: it was for the ecryptfs filesystem, which is built as a module [23:54] kirkland: built as a module, but part of the kernel package [23:54] rtg: ah [23:54] okay