[02:46] <Kano> hi, is the linux-meta 7 package already done
[07:40] <fairuz> HI, morning
[08:24] <apw> loic yes, we should be using orig from now, i didn't bother for the last upload for expediency
[08:57] <fairuz> Hi, I do #include <plat/omap44xx.h> in kernel space and it recognizes it, but it did't recognizes it in user space. Is it normal ? 
[09:06] <apw> fairuz, yep, those are kernel headers, only a select few are exported to userspace in the linux-libc-dev package and they are primarily for libc use
[09:06] <fairuz> apw: ok thanks
[09:36] <ppisati> ericm|ubuntu: ping
[09:45] <ericm|ubuntu> ppisati, pong
[09:45] <ericm|ubuntu> ppisati, what's up dude?
[09:46] <ppisati> ericm|ubuntu: i can't get any audio out of mvl-dove, did you?
[09:46] <ericm|ubuntu> ppisati, I used to - but not really sure if that's still the case
[09:46] <ppisati> ericm|ubuntu: uhmmm...
[09:47] <ppisati> ericm|ubuntu: i mean, a vanilla 10.04 installation was enopugh to get sound? or do i have to tweak anything?
[09:47] <ericm|ubuntu> ppisati, I don't think so
[09:47] <ericm|ubuntu> ppisati, wait
[09:48] <ericm|ubuntu> ppisati, I seem to remember a alsamixer thing to get it work but I'm not really sure
[09:48] <ericm|ubuntu> ppisati, did you check the gnome-volume-control?
[09:49] <ppisati> ericm|ubuntu: volemu control seems ok
[09:53] <ericm|ubuntu> ppisati, hrm.... did you do a search on LP?
[09:53] <ppisati> ericm|ubuntu: i'm hoovering all the mvl-dove bugs
[09:53] <ppisati> ericm|ubuntu: there are 2 audio-related bugs for mvl-dove
[09:53] <ppisati> ericm|ubuntu: the first is about the headphone not recognized (while in a LSP update there was specific mention about it)
[09:54] <ppisati> ericm|ubuntu: the second is about an alsa config
[09:54] <ppisati> wait...
[09:54] <ppisati> ericm|ubuntu: headphones: https://bugs.launchpad.net/ubuntu/+source/linux-mvl-dove/+bug/551249
[09:54] <ubot2> Launchpad bug 551249 in linux-mvl-dove "Audio driver fails to detect Headphone insertion/removal." [Wishlist,Confirmed]
[09:55] <ppisati> ericm|ubuntu: alsa config: https://bugs.launchpad.net/ubuntu/+source/linux-mvl-dove/+bug/651281
[09:55] <ubot2> Launchpad bug 651281 in linux-mvl-dove "Need alsa configuration files for Dove A0 SOC platform" [Undecided,New]
[09:55] <ericm|ubuntu> ppisati, the 2nd one is suspicious
[09:55] <ppisati> the second one, looks like you need a specific config file to get any audio out of this board
[09:55] <ppisati> yep
[09:55] <ericm|ubuntu> ppisati, I didn't really ever check the audio difference between X0 and A0
[09:55] <ppisati> but since i _guess_ you (i mean the mvl-dove team) tested the audio
[09:55] <ppisati> ahhh
[09:56] <ppisati> so you did all the stuff on X0?
[09:56] <ppisati> and i got an A0, right?
[10:09] <Kano> hi, how to disable the modules check globally
[10:43] <apw> Kano, add the ignore.modules file
[10:44] <apw> to the abi for the flavour, see the check-modules script
[10:58] <Kano> and globally?
[10:59] <Kano> the funny thing is, i only increased the version and changed the hz value
[10:59] <Kano> but it failed with modules
[11:00] <Kano> also it still builds too much
[11:00] <Kano> http://paste.debian.net/110848
[11:00] <Kano> it builds tools and i dont want tools
[11:01] <Kano> i already added a skip abi check
[11:02] <Kano> did i forget something after increasing the version with dch -lxxx
[11:03] <Kano> as there are no modules for 7.35 only 6.34
[11:05] <Kano> how to increase version correctly?
[11:07] <Kano> hmm there is a skipmodule too
[11:08] <apw> when you start a new release you need to provide abi information for the previous version
[11:08] <Kano> how to do that?
[11:08] <apw> this is all documented in how to bump the abi information
[11:09] <apw> the getabis script handles the body of the work
[11:11] <Kano> you call that manually?
[11:11] <apw> after the builds complete yes, you run that and it sucks down the abi info from the archive
[11:12] <apw> then that gets commited to allow checking of following builds
[11:12] <apw> but you have been building kernels for years, so not sure why this is a new problem for you
[11:12] <Kano> but that means you have to build it before you can put it into pbuilder
[11:12] <Kano> well the last year i just used your mainline kernels
[11:13] <Kano> i just began with .38rc6 again recompiling your kernels because i needed aufs
[11:13] <apw> no cause you are always using the previous builds stuff
[11:13] <apw> the abi is never for the new kernel, its for the one before, which by definition is already built
[11:15] <Kano> your getabis script tries to dl from a server
[11:17] <Kano> i think i just try skipmodule in arch.mk
[11:21] <Kano> the last kernel with heavy mods i which i compiled using pbuilder was 3 years ago. using the custom flavour options
[11:26] <apw> Kano, yep but it shows you how the abi stuff is meant to extract the info if you care.  otherwise you can skip it
[11:41] <Kano> is there a linux-meta 38-7?
[11:42] <lool> apw: Oy
[11:42] <lool> apw: Re: armhf
[11:43] <lool> apw: Essentially, this is the future for ARM support; this effort started perhaps about 6 months ago from a Genesi initiative using first Ubuntu armel and then introducing a real Debian armhf port, which is not an official Debian port yet but will eventually be one
[11:44] <lool> apw: On the Ubuntu / Linaro side, we want to eventually switch to this port instead of armel as it provides strictly better performance, but it has to be bootstrapped as it changes ABI
[11:44] <lool> apw: We had a good UDS session on this port but we were lacking buildds for very long
[11:44] <apw> lool, ok so when are we going to need this support, natty or O ?
[11:44] <lool> Now, I think we might have buildds, but it's clear that we wont have time to bootstrap armhf for Ubuntu before 11.04, still we're trying to merge as many support patches now rather than later
[11:44] <apw> oneiric (sp?)
[11:45] <lool> apw: I've just asked a couple of days ago for a FFE to merge sourceful fixes in the relevant packages
[11:45] <lool> apw: IOW, we're trying to have the packages be buildable with -aarmhf, but we don't expect Ubuntu to carry binaries this cycle
[11:46] <apw> lool, ok so i should wait for the FFE to be approved before merging them?  otherwise they ahve no operational effect in theory at least
[11:46] <lool> Most of the time, it's a matter of either fixing rules/control to check for both armel and armhf rather than just armhf, or to fix upstream configures which might not support the new triplet (arm-linux-gnueabihf instead of just arm-linux-gnueabi for armel)
[11:48] <lool> apw: You could opt to wait for the FFE, or decide that they are unintrusive  :-)  if you find there is a chance for breakage, then maybe wait for the FFE
[11:48] <apw> lool ok, will have a look see if they work ok in my cross env here
[11:49] <lool> apw: What's the best to rev one patch?  I'd like to update armhf.mk to also skipabi=true and skipmodules=true, but it feels heavy to resend the series just for that
[11:50] <apw> lool do you need to do that, can't you just include the ignore/ignore.modules in the abi directory
[11:50] <apw> when you inject the configs etc
[11:50] <lool> apw: I decided to not add any config or ABI data as to not pollute the kernel tree with armhf churn
[11:51] <lool> that is, I figured you wouldn't want to see a lot of armhf in the diff, when you are not actually building these packages
[11:51] <apw> right, but you must be injecting the configs etc when you build, you could just inject those at the same time?
[11:51] <apw> yeah you are spot on there
[11:51] <lool> I'm not building any kernel ATM; I'm bootstrapping so I just need libc-dev
[11:51] <apw> ok then just send the skip stuf as anohter patch, make make it a reply to the one it need squishing into
[11:51] <apw> and i'll squish it when applying
[11:51] <lool> apw: Ah one important thing I should also mention: the different is only userspace ABI; it's the same kernel ABI, so that armel kernels can run an armhf userspace and vice-versa
[11:52] <lool> *difference
[11:52] <apw> right, as there is no fp in the kernel (in theory at least)
[11:54] <Kano> apw: you tagged the linux-meta but the package is not created?
[11:57] <apw> Kano, not created ?
[11:57] <Kano> or not uploaded or whatever
[11:58] <apw> right, you cannot upload the meta until all the builds are completed and accepted by an AA
[11:58] <apw> else the architecture becomes uninstallable, and cd builds fail, and kernels get de-installed from systems
[11:59] <apw> but you run a debian based distro, you must have the same problem
[11:59] <Kano> sure,but i upload all the same time
[11:59] <Kano> i upload prebuild packages
[12:00] <Kano> usually i fetch the packages from ubuntu which are not critical
[12:01] <apw> that leave dist-upgraders at risk of partial installs, and most resoltions are fatal for meta packages
[12:01] <Kano> i decide when i update the index
[12:01] <apw> you have an advantage i don't have then, hense its 
[12:01] <apw> not uploaded in ubuntu
[12:02] <Kano> well you only need to upload source
[12:02] <apw> i can't upload the source, as that will build and upload the binaries, and they are not held for AA review
[12:02] <Kano> http://kanotix.com/files/hellfire/ubuntu/ubuntu-kernel-build-only-generic.txt
[12:02] <apw> so they will swan past the binaries, and leave us in a heap
[12:03] <apw> which is why we don't do it
[12:05] <apw> we don't do our work in this order to make it hard for you, we do it cause it is right for our users
[12:05] <Kano> oh no, i got past the modules error but now: http://paste.debian.net/110856
[12:06] <Kano> dpkg-gencontrol: error: install new files list file: No such file or directory
[12:06] <Kano> what is that
[12:06] <apw> no idea, never seen that phase forget in all the builds i've done, and its a lot
[12:07] <Kano> i use kernel-wedge from ubuntu but rest is debian
[12:07] <Kano> but it has got an error, maybe it is related
[12:08] <Kano> http://paste.debian.net/110857
[12:09] <apw> the error is a rename failure, renaming a file it made from foo.new to foo 
[12:09] <apw> not something i'd expect we'd trigger really
[12:09] <Kano> do you get this error too?
[12:09] <apw> Kano, those are normal, they are related to empty lines IIRC
[12:09] <apw> and yes we get them
[12:09] <apw> i'd check you arn't out of inodes or something
[12:10] <apw> rename("$fileslistfile.new", $fileslistfile) || syserr(_g("install new files list file"));
[12:10] <apw> is what barfed on you
[12:12] <Kano> 17 gb free just for generic+generic-pae
[12:18] <Kano> http://kanotix.com/files/hellfire/ubuntu/kanotix-kernel-changes.txt
[12:18] <Kano> is there something major missing?
[12:18] <Kano> those are changes against your package
[12:18] <Kano> first i use the other script to disable parts of the build
[13:15] <fairuz> I do request_irq in kernel space, but is it possible to have the handler code in user space?
[13:16] <mjg59> fairuz: No
[13:16] <fairuz> mjg59: ok
[13:16] <mjg59> fairuz: I mean, you could generate a netlink event or something on interrupt and have userspace do something as a result
[13:17] <mjg59> But that's going to end up racy
[13:17] <fairuz> mjg59: yup, I will stick on kernel space then
[14:13] <fairuz> whats writel or readl equivalent in user space?
[14:13] <apw> lool, this nls_cp437 patch seems to have an incorrect bug number in it
[14:13] <lool> apw: indeed, should be 732046
[14:14] <lool> I'll blame it on Chromium's paste buffer handling  :-P
[14:14] <lool> I wonder where I picked the other bug id from, it's private
[14:15] <lool> apw: Do you want me to resend?
[14:16] <soren> lool: * (drop after 2.6.38) ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller - LP: #735240
[14:17] <soren> lool: From an older changelog entry.
[14:17] <lool> Ah, right, I probably forgot to update it after pasting then, thanks
[14:18] <soren> np
[14:20] <smoser> lool, thank you for pushing on bug 735240
[14:20] <ubot2> smoser: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/735240)
[14:20] <lool> smoser: np
[14:21] <apw> lool, nope i can correct it now i know, thanks
[14:21] <smoser> i think it would be quite generally useful if kernel build process created a -extra-modules with the non-whitelisted files whenever the inclusion-list was used
[14:21] <apw> bug #732046
[14:21] <ubot2> Launchpad bug 732046 in linux "Missing filesystem modules in -virtual package" [Undecided,Won't fix] https://launchpad.net/bugs/732046
[14:21] <lool> smoser: I agree with Stefan that the packaging changes aren't trivial, but this would also be my preference
[14:22] <apw> lool and how did you set linux back to new, without natty going back to new ... you've unconjoined the pair somehow
[14:23] <lool> ?
[14:23] <lool> Oh
[14:23] <lool> I think you can do that as soon as the development task is closed
[14:24] <smoser> and generally, that list culd use some attention (i am probably at least partially responsible for doing so)... it has net/wireless/* in it.
[14:24] <lool> For some value of the bug field
[14:26] <apw> lool well you learn something new and odd about launchpad every day
[14:27]  * ogasawara back in 20min
[14:27]  * apw giggles at ogasawara 
[14:34] <apw> smoser, so it does ... hrm ... probabally something for O now
[14:35] <smoser> yeah, i dont really care, but the mac80211 is also there... porobably not that important :)
[14:35] <smoser> i suppose we could do a session on it in uds-o or at least you and smb and i and jj-afk could discuss
[14:36] <fairuz> Hi, all variables in a kernel module will stay until rmmod is made?
[14:36] <apw> fairuz, a module can rely on its memory existing until the end of its destructor
[14:37] <fairuz> apw: destructor == module_exit?
[14:37] <apw> fairuz, believe so yes
[14:37] <fairuz> apw: thanks
[14:38] <smb> smoser, apw sounds reasonable... hopefully we will have again any sensible layout for sessions
[14:44]  * apw overlaps with tgardner :)
[14:44]  * smb tries to picture that...
[14:44] <tgardner> apw, uh, sorry. I was just grinding through the list
[14:45] <apw> tgardner, nope no problem, you carry on
[14:47] <apw> tgardner, i am only seeing the fat change, not the others, yet email says its pushed?
[14:48] <tgardner> apw, which changes are missing?
[14:48] <apw> tgardner, oh ignore that, they moved, and i confused two threads
[14:49] <apw> tgardner, i'll handle updating ubuntu-debian, if thats ok, i want to resync them anyhow
[14:49] <tgardner> apw, I figured you would.
[14:55] <apw> tgardner, i think lool wants this stuff in natty so they can do early testing, much as we have already elsewhere
[15:01] <lool> apw: Should I have sent a series against ubuntu-debian instead?
[15:01] <lool> I vaguely remembered the existence of this repo, but wasn't quite sure which one to send against
[15:09] <apw> lool, nope, its half and half for your use case
[15:09] <apw> i'm sorting it out now
[15:21] <tgardner> ppisati, I was just chatting with ikepanhc about OEM mvl-dove kernels. He's still consuming CVEs and stable updates from the distro kernel. could add 'rebase to master' to your todo list for mvl-dove and send me a pull request?
[15:24] <ikepanhc> tgardner: IIRC the mvl-dove lucid branch is maintained for 18mo?
[15:24] <ppisati> tgardner: isn't the -proposed kernel already rebased against the lastest-ish?
[15:25] <tgardner> ppisati, hang on a sec. otp.
[15:32] <tgardner> ppisati, I can't remember, but I think its a ways behind. I'm sure you can figure it out.
[15:33] <tgardner> ikepanhc, the mvl-dove branch only gets 18mo worth of love
[15:33] <ppisati> tgardner: anyway, ok, i'll do that
[15:33] <ikepanhc> tgardner: ok, I need to inform PM this
[15:50]  * apw_ is off the sir, internet in a heap
[15:52] <tgardner> apw: did you mean "off the air" ?
[15:52] <apw_> indeed, touch screns 
[15:53] <apw_> make lousy keyboards
[15:57] <bjf> ogasawara, you got a sec ? 
[15:57] <ogasawara> bjf: yep
[15:58] <bjf> ogasawara, i just uploaded a linux-ubuntu-modules-2.6.24 to the canonical-kernel-team ppa
[15:59] <bjf> ogasawara, the builds for it all failed: Missing build dependencies: linux-headers-2.6.24-29-generic
[15:59] <bjf> ogasawara, however -29 is in proposed
[16:01] <bjf> ogasawara, i'm don't get it
[16:01]  * ogasawara tries to remember if it'll pull build deps from -proposed
[16:03] <apw_> no it won't it is security only
[16:03]  * smb thinks only updates/security and ppa itself
[16:03] <apw_> one reason to not delete kernrl till all drps built
[16:04] <apw_> remember that is why wr have the ppa, to build against security only
[16:05]  * tgardner is enjoying apw's gibbers typing
[16:05] <apw_> grrrr
[16:06] <apw_> bjf you may be able to copy kernel back from proposed
[16:06] <bjf> apw_, ogasawara ok, so i'm getting feedback that the hardy kernel in -proposed can't be installed due to ubmet dependencies. 'linux-ubuntu-modules-2.6.24-29'
[16:06] <tgardner> apw, bjf: why don't I just upload LUM to the archive?
[16:06] <bjf> apw_, ogasawara so i uploaded a new LUM to fix this issue
[16:06] <bjf> tgardner, you want my src pkg ?
[16:07] <apw_> but if kernel not still in ppa, it wont build
[16:07] <tgardner> bjf, I'll just build from the repo. I assume its what you want?
[16:07] <apw_> assume someone cleaned itvout
[16:08] <apw_> we needcit built in ppa
[16:08] <tgardner> apw:  2.6.24-29.87 is in -proposed. LUM should build against that OK.
[16:08] <bjf> tgardner, will that work ? I want it for both -security and -updates. that's why we use the ppa
[16:08] <ogasawara> bjf: I'd assume you'd need to also upload the headers package to the ppa to get it to build ok
[16:08] <apw_> sobir can be copied to security  too
[16:09] <ogasawara> bjf: once it builds successfully then you could just delete the headers package from the ppa?
[16:09] <apw_> we should notbe deltingbhr
[16:09] <ogasawara> wha??
[16:09] <bjf> we should not be deleting the ppa packages
[16:09] <ogasawara> ah
[16:09] <smb> I would agree with apw (though he sounds like he ran against a wall with his nose)
[16:09] <tgardner> until all dependencies are built
[16:09] <apw_> the headers come from the kernel source
[16:10] <smb> Everything should be first in the ppa and then copied
[16:10] <bjf> smb, thats all well and good except when you forget something, it sucks being human
[16:10] <apw_> i suspect to fix youll have to do a no changecupload of the kernel
[16:11] <apw_> tovthe ppa, then lum
[16:11] <smb> Then the kernel package need to be uploaded and the cleaning mechanism should only delete packages that are superseded in the ppa itself
[16:11] <apw_> and get ourchecklist sorted so it includes lum etc
[16:12] <tgardner> apw: in this particular case, Is ee no reason why we can't just upload LUM to -proposed.
[16:12] <smb> apw_, Could be that the version needs to be tweaked a bit because the real one had been in the ppa already
[16:13] <apw_> ivf the compiler is the same likely itll work
[16:14] <tgardner> apw: I'm not too worried about that. gcc for Hardy hasn'
[16:14] <bjf> apw, tgardner, smb, i'm tempted to just ignore the one that is currently in -proposed and just upload the kernel for the new cycle, then the matching lum
[16:14] <tgardner> hasn't changes in a bit
[16:14]  * smb wonders how long it would take if we only uploaded to our ppa and requested more disk-space until lp learned to auto-clean ppas...
[16:18] <tgardner> bjf, have you had any complaints about folks not being able to upgrade their LUM packages? I assume the meta package in -proposed is pointing at a LUM that does not yet exist.
[16:20] <bjf> tgardner, bug 725138 comments 2 & 3
[16:20] <ubot2> Launchpad bug 725138 in linux "linux: 2.6.24-29.87 -proposed tracker" [Undecided,Fix committed] https://launchpad.net/bugs/725138
[16:21] <bjf> tgardner, don't know why QA hasn't run into this
[16:21] <tgardner> bjf, 'cause LUM is an elective install
[16:21] <bjf> tgardner, that just occurred to me
[16:22] <bjf> tgardner, it's only an issue if you have installed it and then are trying to update
[16:22] <smb> tgardner, I am not so sure about the electiveness of LUM
[16:22] <smb> (as it has all the sound of hardy)
[16:23] <tgardner> smb, , oh it LBM and LRM that were elective?
[16:23] <smb> I think so. 
[16:23] <tgardner> right, so I think all those packages need to get uploaded to -proposed.
[16:26]  * smb is surprised to see his lucid ec2 branch building after all he has done to it...
[16:27] <tgardner> bjf, so I assume Hardy LBM/LRM/LUM are now all on your dependencies checklist for ABI bumps? Hardy is a significant pain in the ass wrt ABI bumps. LBM/LRM are still currently lagging the ABI update.
[16:27] <bjf> tgardner, yes, i'll work on straightening this out today
[16:38] <apw> damnable broadband is still in a heap, at least i have a keyboard now though
[16:39] <smb> apw, Did you buy one for your phone ?
[16:39] <apw> heh, no but i also have a data stick for emergencies, which i've just activated
[16:40] <smb> apw, Ah :) Actually I guess you could have used the phone for that
[16:40] <apw> i can but it sucks up my allowance pretty quick, this is 'unlimited'
[16:41] <smb> They did not promise unlimited speed... Though its hard to get unlimited data with a speed near to zero
[16:56]  * bjf[afk] heading out to deal with a passport issue
[17:06] <ogasawara> so how are CVE's being handled now?  Does the security team still ping us to process a batch of public CVE's or do we just pick them up when we have time or are there dedicated days to work on CVE's?
[17:07]  * ogasawara just noticed the list of CVE's is growing
[17:08] <tgardner> ogasawara, its been kind of jit and miss. most of us try to get to at least one CVE per week. you can coordinate on https://spreadsheets.google.com/a/canonical.com/ccc?key=0AgFTUDTDyXredE92dFdsVGkxN1FMMWJabS0wZENLRWc&hl=en&ndplr=1#gid=0
[17:48]  * tgardner --> lunch
[18:20] <bjf> tgardner, ogasawara https://wiki.ubuntu.com/Kernel/Dev/FixingCVEs
[18:29] <kristian-aalborg> hi ppl
[18:30] <kristian-aalborg> which is the smallest/fastest ubuntu installation that will let me build a kernel.deb?
[18:54] <apw> kristian-aalborg, i don't think any of them will let you do that without installing additional stuff
[18:54] <kristian-aalborg> yup, I'm aware
[18:54] <apw> apt-get builddep linux or similar will sort you on any
[18:54] <kristian-aalborg> but would Server Edition do?
[18:55] <apw> yeah as long as you have the builddeps you are good, there is not impediment
[19:00] <kristian-aalborg> would this be true for debian as well?
[19:01] <kristian-aalborg> I have an ultra modest machine that I plan to build kernels on - would love as little "fluff" as possible and there's only 2 gigs to spare
[19:04] <jjohansen> kristian-aalborg: uh you are aware that kernel builds suck up lots of space
[19:05] <kristian-aalborg> yes, painfully aware... I'm thinking of doing the building itself on an usb stick
[19:05] <kristian-aalborg> then I can just throw the Eee 2g surf (!!) in a corner and check it every few hours ;)
[19:07] <jjohansen> kristian-aalborg: so a minimal debian would work as long as all the proper build deps are installed, but the build deps are actually pretty weighty
[19:07] <jjohansen> several hundred megs, /me doesn't remeber the exact figures
[19:08] <kristian-aalborg> yes
[19:08] <apw> you do need about 5GB plus 1GB per flavour you build
[19:08] <kristian-aalborg> I have two eight gb sticks
[19:10] <jjohansen> kristian-aalborg: while you can do builds on a stick you will want them to be fast sticks and you can burn them out pretty quick
[19:11] <kristian-aalborg> no need to burn, I'll just move the stick over
[19:11] <kristian-aalborg> the perfect crime ;)
[19:14]  * jjohansen -> lunch
[19:20] <kristian-aalborg> I see that ubuntu NetInst with the debs is 1,2 gig
[19:59]  * kristian-aalborg has settled for Server Install and is about to give it a try
[20:16]  * bjf -> lunch
[20:20] <JFo> stepping away for a bit. call my cell if you should need me  
[20:20] <JFo> (not that I expect you will need me)
[20:34]  * vanhoof calls JFo for fun
[20:35] <ogasawara> heh
[20:38] <kristian-aalborg> by the way, is there somewhere you can get a pre-built kernel with APM support (i.e for old hardware)?
[20:39] <tgardner> kristian-aalborg, every release since Dapper has CONFIG_APM=m
[20:40] <kristian-aalborg> tgardner: I was thinking of something app-gettable?
[20:40] <kristian-aalborg> a project somewhere for freaks like me running old machines ;)
[20:44] <tgardner> kristian-aalborg, I'm not really sure what you're asking then. Every _kernel_ we've released supports APM to some extent. Have you tried 'sudo modprobe apm' ?
[20:45] <kristian-aalborg> yes
[20:45]  * kristian-aalborg needs to boot up another machine to do it live (like O'Reilly puts it)
[20:50] <kristian-aalborg> FATAL: error inserting apm, no such device
[20:51] <kristian-aalborg> however, the file is very much there
[20:53] <mjg59> kristian-aalborg: apm will fail if acpi is running
[20:55] <kristian-aalborg> so, the vanilla ubuntu kernel supports apm?
[20:56]  * kristian-aalborg has to shop for cigs, brb
[20:59] <njin> hello to all, in a system with a pae kernel installed, can i suggest to install the ppa kernel?
[21:01] <apw> njin, depends on the PPA ... but normally there are generic and generic-pae flavours in a ppa
[21:02] <kristian-aalborg> mjg59: which flags in grub? apci=off and apm=on ?
[21:02] <mjg59> kristian-aalborg: That would probably be a start
[21:03] <njin> apw: i know only http://kernel.ubuntu.com/~kernel-ppa/mainline/, there's another ppa?
[21:03] <kristian-aalborg> I'd swear I tried any and possible flags...
[21:04] <apw> the mainline builds, we don't build just -generic ones
[21:04] <apw> i mean we do just build -generic there
[21:05] <njin> and where i can find the pae then?
[21:05] <apw> of mainline kernels, we don't make those i am afraid
[21:05] <apw> they are not designed for running regularly, they are for testing only
[21:06] <njin> ah, i understantand, so better not suggest to try the mainline in a machine with a pae kernel?
[21:06] <kristian-aalborg> hurm, same error with those flags
[21:07] <kristian-aalborg> to clarify, this is the kernel that came with the install
[21:08] <kristian-aalborg> 2.6.32-27-generic
[21:09] <mjg59> You're sure that the machine has an APM BIOS?
[21:09] <kristian-aalborg> pretty much
[21:10] <kristian-aalborg> http://www.thinkwiki.org/wiki/Category:770
[21:10] <mjg59> Yeah, ought to work
[21:11] <mjg59> What does dmesg say after modprobe apm ?
[21:15] <njin> Kernel driver in use: i915 and intel ips 0000:00:1f.6: CPU power or thermal limit exceeded is a linux issue ?
[21:15] <kristian-aalborg> aha
[21:16] <njin> bug 728579
[21:16] <ubot2> Launchpad bug 728579 in linux "Imagen in external VGA monitor trembles" [Undecided,New] https://launchpad.net/bugs/728579
[21:16] <kristian-aalborg> http://pastebin.com/V5Wrtxzf
[21:17] <mjg59> kristian-aalborg: Ok, I blame the code that's meant to set up the APM data
[21:18] <mjg59> Should probably just file a bug
[21:19] <kristian-aalborg> hurm
[21:19] <kristian-aalborg> as I understood it, apm has to be compiled into the kernel to work now?
[21:20] <mjg59> Shouldn't
[21:21] <kristian-aalborg> ok, that's good
[22:56] <lool> Does someone have a recipe for doing a PPA upload of an Ubuntu kernel?
[22:56] <lool> basically I'd like to apt-get source linux, do some changes, push to my PPA, but I keep running into issues; I did rename the ABI dir last time around, but now I'm getting module hashes mismatches
[22:58] <lool> sorry symbol hashes
[23:00]  * lool is going to try with a custom ABI name
[23:02] <kamal> lool: hi, I publish kernel PPA's quite regularly -- maybe I can help.  took me several iterations to finally whip the ABI and module check issues into submission also :-)
[23:03] <lool> kamal: Happy to hear your tricks  :)
[23:03] <lool> I could obviously set skipabi and skipmodules on all arches, or touch the ignore files, but if I could keep the changes to a minimum and keep the safety nets, that'd be nice
[23:04] <kamal> lool: the secret is to disable the ABI check *and* the module check
[23:04] <kamal> lool: ah, so you know about the ignore files already -- that's the big "trick" :-)   always works for me, 100%
[23:05] <lool> kamal: Ever tried uploading your own ABI?
[23:05] <kamal> I used to worry about the "safety net" also, but have found that none of my PPA "customers" ever have any trouble with my published kernels -- I don't worry about it any more, I just shut those ABI and module checks right off and don't think twice about it.
[23:05] <lool> kamal: Also, what version number do you use, and do you update both debian.master/changelog and debian/changelog?
[23:06] <kamal> lool: no, I've never tried uploading my own ABI
[23:06] <jjohansen> lool: generally debian.master
[23:06] <jjohansen> debian/changelog should be copied from debian.mast/changelog
[23:06] <lool> But when you prepare the source, tools usually poke debian/changelog e.g. dpkg-source -b
[23:07] <kamal> lool, jjohansen: yes, I always edit *both* as jjohansen describes
[23:07] <lool> so I end up editing both -- if I edit only debian/changelog it gets replaced during build, and that doesn't end happily
[23:07] <jjohansen> lool: fdr clean, setups up debian/changelog
[23:07] <kamal> lool: yes, correct -- you must keep them in sync for any sort of sanity to occur.
[23:07] <jjohansen> yep
[23:07] <kamal> jjohansen: but beware!...   fdr clean only gets run *after* you've produced the source package!...
[23:08] <kamal> jjohansen: so if you don't *manually* copy debian.master/changelog to debian/changelog before you produce that source package, it will get produced with a bogus version number.
[23:08] <kamal> (doesn't matter for git-push-and-build, but does matter very much for PPA uploads).
[23:09] <jjohansen> kamal: ah, yeah that is a problem, /me has always done fdr clean before making the source package
[23:09] <kamal> jjohansen: ah, I don't do that -- I *just* "cp debian.master/changelog changelog"
[23:09] <jjohansen> kamal: well I wasn't sure what other bits might be needed, so I figured it was safest
[23:10] <kamal> jjohansen: that's the only one needed.   I've thought about trying to fix up our packaging system to resolve that issue also (since I built an awful lot of mis-versioned packages before I figured out the reason).
[23:10] <jjohansen> lool: as for the abi stuff its an absolute pain, I suggest you just follow kamal's suggestion of disabling
[23:12] <jjohansen> kamal: its the abi stuff that killed me originally, I was preparing the package from a tree where I had done test builds, but the test builds had generated the abi files I needed incrementally, so they were available locally but didn't become part of the upload, and hence the ppa builds would fail
[23:15] <kamal> jjohansen, lool: yes, I used to tear my hair out over build failures due to ABI ... but having never experienced any problem with just disabling the check.
[23:16] <lool> Thanks all
[23:18] <kamal> lool: you also asked about version numbers...  I've settled on a "+kamal~suchandsuch" scheme so if I'm publishing a build of "the foobar fixes" on top of say 2.6.38-7.35, then I'll use a version number of "2.6.38-7.35+kamal~foobar~fixes".  ...
[23:20] <kamal> IMHO, its good to have my name there for easy blame^Widentification by uname -a.   The "+" sorts correctly and conveys some useful meaning and is a legal character.  The "~" is also a legal character (which does have another special meaning, not relevant here).   Note that neither "-" nor "_" are acceptable characters for you to add on to the string.
[23:33] <kristian-aalborg> mjg59: might you be interested in helping me file a bug report later?
[23:34] <kristian-aalborg> I'd want to do it properly, if I should do it