[07:39] <EruditeHermit> hello, if I have a kernel compiled according to https://wiki.ubuntu.com/KernelTeam/GitKernelBuild is there a way to patch it and only rebuild that module and get another package?
[07:39] <EruditeHermit> how do I avoid rebuilding the entire kernel
[07:57] <EruditeHermit> anyone?
[07:58] <RAOF> You might be able to get away with just calling fakeroot debian/rules binary
[07:58] <RAOF> You might be able to get away with just calling fakeroot debian/rules binary-generic
[07:59] <jjohansen> yep, 
[07:59] <jjohansen> what you need to do is patch
[07:59] <amitk> EruditeHermit: try make O=debian/build/build-<flavour>
[08:00] <jjohansen> rm debian/stamps/stamps-build-generic
[08:00] <jjohansen> then you can do fakeroot debian/rules binary-generic
[08:00] <jjohansen> it will only rebuild the module and then do packaging
[08:00] <jjohansen> amitk: way of make will work but won't give you the package
[08:01] <jjohansen> s/amitk/amitk's/
[08:01] <EruditeHermit> ok
[08:01] <EruditeHermit> let me try that
[08:01] <EruditeHermit> this has bugged me for months
[08:04] <EruditeHermit> no rule to make target 'binary-generic'
[08:04] <EruditeHermit> I reran the build command
[08:04] <EruditeHermit> maybe that screwed things up?
[08:05] <jjohansen> what exactly did you run?
[08:05] <EruditeHermit> CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers
[08:06] <amitk> EruditeHermit: eeeeks
[08:06] <amitk> make-kpkg is not supported
[08:06]  * amitk checks the wiki
[08:06] <EruditeHermit> so what do you guys recommend?
[08:06] <EruditeHermit> what tutorial should one use?
[08:07] <EruditeHermit> I was using this
[08:07] <EruditeHermit> https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[08:07] <amitk> wtf, wiki talks about make-kpkg
[08:08] <jjohansen> heh???!!! since when I don't remember it talking about make-kpkg
[08:08] <EruditeHermit> basically I need to git clone a kernel source, patch it, then build it into an installable package
[08:08] <jjohansen> EruditeHermit: I would just run  fakeroor debian/rules binary-generic
[08:08] <EruditeHermit> but the cloned version doesn't have a debian dir
[08:08] <RAOF> jjohansen: That won't work for upstream kernels, though.
[08:09] <jjohansen> ah, I was thinking patching our kernel and rebuilding
[08:09] <EruditeHermit> nah
[08:09] <EruditeHermit> so I am working with a kernel dev on a bug
[08:09] <EruditeHermit> so I need to use his specific kernel
[08:09] <amitk> this one is a user-contributed wiki page, I think. Needs to be scrubbed
[08:10] <EruditeHermit> and then he sents me patches
[08:10] <amitk> Try this instead: https://help.ubuntu.com/community/Kernel/Compile
[08:10] <amitk> hmm.. but Leanne has contributed to the page
[08:11] <EruditeHermit> amitk, which part of that page?
[08:11] <EruditeHermit> amitk, I am not using Ubuntu kernels
[08:11] <EruditeHermit> so I don't have debian dirs
[08:12] <EruditeHermit> most of those instructions assume a debian/ dir
[08:13] <amitk> errm, this is a channel for ubuntu kernels, really.
[08:13] <amitk> you didn't mention that at the beginning
[08:13] <EruditeHermit> right, but I am building kernels the Ubuntu way
[08:13] <EruditeHermit> err I want to build kernels that are created as deb packages
[08:14] <jjohansen> EruditeHermit: I have never done mainline into a package before but one idea would be to grab our kernel and copy over debian and debian.master
[08:14] <EruditeHermit> do you guys have a 2.6.34-rc2 or newer kernel?
[08:14] <amitk> apw: ^^^ mainline building as a .deb question
[08:15] <amitk> EruditeHermit: yes, we build all mainline rc releases these days
[08:15] <EruditeHermit> so I can just copy the debian dir from that?
[08:15] <amitk> https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
[08:15] <EruditeHermit> as jjohansen said?
[08:16] <amitk> that might be easiest
[08:16] <jjohansen> EruditeHermit: I've never tried it, it might need a tweak but it should work
[08:18] <EruditeHermit> err rok
[08:18] <EruditeHermit> i'll try that if no one has any better suggestions
[08:19] <crazybyte> hello! Perhaps somebody could help me to either solve or find the cause of the following problem. I switched from Hardy to Karmic (and Lucid Beta 2 for a short time). Since my switch the kernel is constantly sending out oopses at random times (after boot up). It says that it cannot satisfy a paging request around a certain address that repeats itself. Also always in the traceback I'm getting functions related to file system oper
[08:19] <crazybyte> ations (like getting an inode). I figured iot could be a memory problem so I ran memtest for a long test and also a hard drive test (including badblocks, fsck and smart self test) but without any luck, there is no hardware error (at least that is the impression).  Could somebody enlighten me what could be the possible cause of these errors or how could I debug it and find what is causing them? At this stage my machine (which is 
[08:19] <crazybyte> a laptop) is unusable entirely. Thank you!
[08:20] <amitk> crazybyte: filesystem errors? We'd need a log to say more...
[08:21] <crazybyte> amitk, i would happily send it or put it up somewhere
[08:22] <crazybyte> but only tonight because i'm at work now.
[08:22] <crazybyte> amitk, could a hw be the cause of these kernel oopses?
[08:23] <crazybyte> amitk, also I tried using ext4 and ext3 with the same result
[08:23] <jjohansen> crazybyte: its possible, but it is likely you are hitting something else
[08:23] <jjohansen> we really need to see a traceback to get a better idea
[08:24] <crazybyte> jjohansen, i will get all of them and come back later
[08:24] <crazybyte> ok?
[08:24] <jjohansen> crazybyte: also I would try installing the latest 2.6.32-21 kernel it has several fixes in it
[08:24] <amitk> crazybyte: file a bug using 'ubuntu-bug -p linux' and it will get everything we need
[08:24] <crazybyte> amitk, ok
[08:24] <crazybyte> i will
[08:24] <crazybyte> thanks
[08:24] <crazybyte> :)
[08:25] <EruditeHermit> jjohansen, so how do I obtain the debian dir from an ubuntu kernel source package?
[08:25] <EruditeHermit> I downloaded the source package from the mainline kernel ppa
[08:25] <EruditeHermit> but it doesn't have the debian dir inside
[08:27] <EruditeHermit> they don't make this easy
[08:27] <EruditeHermit> lol
[08:28] <RAOF> EruditeHermit: You could (a) clone the ubuntu kernel git tree, then (b) add Linus' tree as a remote, and git checkout the kernel commit of your choice, then (c) run “git checkout master -- debian debian.master” to do a partial checkout of ubuntu's tree - picking up just the debain directories.
[08:29] <EruditeHermit> err sounds a little intense
[08:29] <EruditeHermit> if ubuntu has a git repo
[08:29] <EruditeHermit> perhaps I can just clone that repo somewhere
[08:29] <EruditeHermit> and copy over the debian dir
[08:30] <EruditeHermit> where does ubuntu keep its repos?
[08:30] <amitk> kernel.ubuntu.com/git
[08:31] <EruditeHermit> so which one is the mainline one?
[08:31] <EruditeHermit> lets say I wanted to clone 2.6.34-rc2 of Ubuntus mainline tree
[08:36] <jjohansen> EruditeHermit: I don't believe the mainline ones are there
[08:36] <jjohansen> sorry I didn't realize the debian dir wasn't in the mainline source package
[08:36] <jjohansen> I would say clone the lucid tree
[08:36] <jjohansen> and just copy over debian and debian/master
[08:37] <jjohansen> I am sure apw will have a better way when he shows up
[08:47] <EruditeHermit> the lucid tree is 2.6.32
[08:48] <amitk> EruditeHermit: today is a very bad time for most of us - we're busy with Lucid freeze
[08:48] <amitk> you'll have to figure out yourself or wait for next week
[08:51] <EruditeHermit> no probs
[08:51] <EruditeHermit> i'll try checking in daily
[08:51] <EruditeHermit> or every few days
[08:51] <apw> EruditeHermit, yep thats how the builds are made, copy the one out of the tip of the lucid tree into the tree you want to build
[08:52] <EruditeHermit> apw, will the 2.6.32 debian dir work with 2.6.34?
[08:52] <EruditeHermit> apw, and do you have a git repo URL for me for the master?
[08:54] <apw> that is literally how we make the mainline builds
[08:54] <apw> so it works as well for .34 as the mainline builds
[08:54] <EruditeHermit> lol
[08:54] <EruditeHermit> ok let me try
[08:54] <apw> the main tree from lucid is the place to get it
[08:54] <EruditeHermit> what is the git URL?
[08:55] <apw> git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[08:55] <EruditeHermit> ah thanks
[08:55] <EruditeHermit> i'll let you know how it goes
[08:55] <EruditeHermit> and its literally the master branch of this tree right?
[08:56] <apw> yep
[08:57] <EruditeHermit> so copy over debian dir, then fakeroot debian/rules binary-generic will build packages
[08:57] <EruditeHermit> then I can patch 1 driver
[08:57] <EruditeHermit> and do fakeroot debian/rules binary-generic again
[08:57] <EruditeHermit> and it will just compile that one changed driver
[08:57] <EruditeHermit> and create a new package
[08:57] <EruditeHermit> correct?
[09:09] <apw> plan is correct, the build will rebuild everything, thats the nature of debian packaging
[09:18] <EruditeHermit> wait thats the whole point
[09:18] <EruditeHermit> to avoid rebuilding every module
[09:19] <EruditeHermit> also it keeps running me through the config script every time I try it
[09:19] <EruditeHermit> and doesn't build anything
[09:22] <EruditeHermit> apw, how do I avoid having to rebuild everything all the time
[09:24] <apw> in the debian/stamps there is a build stamp i think you can remove that and it'll do what you want, but i normally build in full so i can't be more definative
[09:25] <jjohansen> yes, it does
[09:25] <EruditeHermit> will it rebuild just the module I want?
[09:25] <jjohansen> you may need to retouch the prepare stamp
[09:25] <apw> i only recall removing one
[09:25] <jjohansen> EruditeHermit: as long as the patch doesn't touch other parts of the kernel
[09:25] <EruditeHermit> just touches a GPU driver
[09:25] <EruditeHermit> also unrelated
[09:25] <EruditeHermit> what does this mean?
[09:26] <EruditeHermit> check-config: FAIL: value CONFIG_DEFAULT_SECURITY_APPARMOR y
[09:26] <apw> it means that your config does not have app-armour
[09:26] <apw> which is a manditory configuration for ubuntu therefore enforced
[09:27] <apw> you can build skip-modules=1 or modules-skip=1 something like that
[09:27] <EruditeHermit> do I need to install app-armour?
[09:27] <apw> crap, config-skip or skip-config
[09:27] <jjohansen> EruditeHermit: no
[09:27] <apw> grep for it in the debian directory
[09:27] <jjohansen> skip-config=true
[09:27] <apw> you will also want skip-modules=1 and skip-abi=1
[09:27] <jjohansen> yep
[09:27] <apw> else we'll be having conversations on those as well
[09:27] <EruditeHermit> so what would the command I run be
[09:29] <EruditeHermit> skip-modules =1 skip-abi=1 fakeroot debian/rules binary-generic
[09:29] <apw> and skip-config=1
[09:29] <apw> otherwise i think thats right
[09:30] <EruditeHermit> skip-modules=1 command not found
[09:31] <EruditeHermit> how do you guys manage such a build system
[09:31] <EruditeHermit> isn't it hard to work with?
[09:32] <jjohansen> EruditeHermit: not really, the kernel is kept in sync with it
[09:32] <jjohansen> having the extra checks can be a life safer
[09:33] <EruditeHermit> so that skip-modules=1 stuff isn't working
[09:33] <jjohansen> now deviating and doing your own custom builds with it does become harder
[09:33] <amitk> EruditeHermit: your requirements are a bit unusual, mainline kernel, ubuntu configs, no ubuntu patches, own patches, no complete rebuild, *sigh*
[09:33] <EruditeHermit> lol
[09:34] <EruditeHermit> all I want to do is have my mainline kernel or custom kernel sources built the ubuntu way with something like ccache
[09:34] <jjohansen> skipmodules=true skipabi=true fakeroot debian/rules binary-generic
[09:34] <amitk> and now add ccache
[09:35] <EruditeHermit> ccache essentially does what I wanted which is to not rebuild the entire kernel if I patch 1 driver
[09:35] <EruditeHermit> I am trying to debug a problem in one driver
[09:35] <EruditeHermit> I don't really care about most of the kernel, just the graphics stack that I am working with
[09:36] <amitk> so why not just compile it normally using make and use the resulting zImage and modules?
[09:36] <EruditeHermit> its easier to keep track of packages
[09:36] <EruditeHermit> package managers are nice because you don't leave stray files around
[09:39] <EruditeHermit> and it seems that Ubuntu/debian packaging isn't designed to do this easily
[09:39] <EruditeHermit> which I understand is not the goal of it
[09:39] <EruditeHermit> but it still makes things hard for me =p
[09:40] <EruditeHermit> btw thank you all for your help
[09:40] <EruditeHermit> I'm sorry if I am asking too many questions
[09:40] <EruditeHermit> but there really isn't documentation about how to do this
[12:50] <apw>  bug 563679
[12:50] <ubot3> Malone bug 563679 in linux-mvl-dove "CONFIG_BLK_DEV_RAM_SIZE should be 65536 as in other kernels" [Undecided,New] https://launchpad.net/bugs/563679
[18:06] <apw> bug 563893
[18:06] <ubot3> Malone bug 563893 in thunderbird "Thunderbird will not launch do to a recursive symlink" [High,Triaged] https://launchpad.net/bugs/563893