[11:18] <pd_> Hello, I've got a kernel packaging problem. I created a new  kernel source package and tried to compile it, but I'm getting a "Checking ABI for [arch]...previous or current ABI file missing!" error. I think that this occures 'cause I changed the ubuntu version, but I'm not sure how to fix the problem properly.
[11:19] <pd_> I hope this question fits in the topic of this channel ;-)
[11:21] <amitk> pd_: you can use 'skipabi=1' in the fakeroot command to bypass the abi check
[11:22] <amitk> pd_: https://wiki.ubuntu.com/KernelMaintenance for details
[11:25] <pd_> amitk: okay... thanks for the hint to the wiki page! I'll try to use the "Development cycle" section of the page to create own packages because I'd like to publish them in my launchpad ppa-
[13:11] <xivulon> cking
[13:11] <cking> xivulon: hi
[13:11] <xivulon> hi there 
[13:12] <xivulon> on 204133, I did ask slangasek and pitti
[13:12] <xivulon> pitti agreed to update it, but steve decided to wait after .1
[13:12] <cking> xivulon: OK. 
[13:13] <xivulon> so we after the 3rd I will chase up steve and pitti again for an SRU
[13:13] <cking> my concern was that it would not get into Intrepid
[13:14] <xivulon> I wouldn't think that should be a major issue, also becase it is an important fix
[13:14] <xivulon> On the other hand, I sent an email to szaka to move the patch upstream, but had no reply so far
[13:15] <xivulon> I will nag him as well
[13:15] <cking> xivulon: OK. Thanks for this. It will be interesting to see if szaka takes the patch into his code
[13:15] <xivulon> as mentioned, I was planning to resume all that after point release
[13:16] <cking> xivulon: if it's not too much to ask, can you keep me informed of the progress of the patch?
[13:16] <xivulon> I will certainly do so!
[13:16] <cking> xivulon: Many thanks!
[13:18] <cking> xivulon: there was one more issue - that was the ntfs mount on with a dirty flag set  - was there a launch pad bug for this?
[13:19] <xivulon> sort-of... there is 226622, it ended up being mostly an ex-post sweetener rather than a fix
[13:20] <xivulon> the bug should probably be split into problem and solutions: 1 give a better error message 2 fix the problem at the root
[13:25] <cking> xivulon: I suspect the dirty flag and ntfs mount can only be addressed by someone with deep knowledge of ntfs
[13:26] <xivulon> cking I would guess so.
[13:27] <xivulon> But it would be nice to be able to address/fix common cases. I assume that in many circumstances it is just the flag, while the underlying filesystem is in fact ok. So a consistency check might be enough.
[13:28] <cking> xivulon: Interesting this as it's a userspace filesystem issue, so it's kind of a kernel bug but also an ntfs tools issue
[15:29] <Monkey77> Hello, I hope my question is not off topic, I am looking to test a new driver which I asked GregKH to include in the kernel, he has put it in his staging kernel ( its the mimio whiteboard driver: http://git.kernel.org/?p=linux/kernel/git/gregkh/staging.git;a=summary). To test that I really need a guide on how to do that in ubuntu.  Are there any walkthroughs so I can test it with the hardware?  I have only done custom 
[15:32] <amitk> Monkey77: you could add the driver in linux-ubuntu-modules, compile it and install the .deb package to test it
[15:33] <amitk> Our git trees are at http://kernel.ubuntu.com/git
[15:33] <amitk> you want hardy-lum.git
[15:34] <amitk> Monkey77: https://wiki.ubuntu.com/KernelMaintenanceStarter should get you started on building LUM
[15:35] <BenC> I wish makedumpfile would get MIRd so the new kernel would build :/
[15:35] <Monkey77> I assume that he has made the patch 2.6.26 or 2.6.27 ready.  Would you expect the patch to work on hardy kernels?
[15:37] <amitk> Monkey77: if the driver is already in 2.6.26 we will get it when we do periodic syncs with Linus' tree. But if it isn't going to make 2.6.26, then we need to add it separtately to the Intrepid tree.
[15:38] <amitk> Monkey77: Hardy is not compulsory, a patch against 2.6.26/27 will do fine.
[15:38] <Monkey77> Its not in 2.6.26, its waiting for me to test it before it gets accepted further.  Thanks for your support
[15:39] <amitk> Monkey77: do you run Ubuntu?
[15:39] <Monkey77> amitk: yes
[15:40] <amitk> Monkey77: Hardy? If so, you could consider installing the Intrepid kernel and providing a patch against it.
[15:41] <Monkey77> The PC I have attached to the whiteboard is purely for getting this driver to work.  I will switch it to Intrepid (from hardy) and do as you suggest.
[15:42] <amitk> Monkey77: You don't have to switch completely, just installing the intrepid kernel ought to be enough.
[15:43] <Monkey77> Ok
[16:09] <Monkey77> One further question, I also need to get a udev rule for the device (once the driver is working), where would I submit a patch for that?
[16:47] <BenC> cking: emailed you the grub+last-good-boot description
[16:47] <cking> BenC: Many thanks
[16:57] <cking> BenC: There must be something screwy with the Email - I haven't received it yet.
[16:58] <BenC> cking: Ooops, I sent it to your .co.uk
[16:59] <cking> BenC: Ah.. and I don't pop the old account anymore.
[17:05] <cking> probably went to /dev/null
[17:40]  * lamont wonders wth "wlan0: RX deauthentication from 00:09:5b:67:48:e6 (reason=6)" is all about, and why he sees it several times an hour
[17:43] <rtg> lamont: reason 6 - Class 2 frame received from nonauthenticated station. probably means the AP has deauthenticated your station for lack of activity.
[17:43] <lamont> rtg: sadly, that makes all too much sense
[17:43]  * lamont will consider adding a keepalive or some such
[17:44] <rtg> lamont: it can hardly be a perceptible pause while it reauthenticates.
[17:44] <lamont> it's clutter in my logfiles
[17:44] <rtg> though I supose NM goes through DHCP again.
[17:44] <lamont> OTOH, the heart of the issue is that, uh, it's plugged into the wired LAN
[17:44] <lamont> NM doesn't do squat in this situation
[17:44] <lamont> and so we play bouncy-bounce
[17:45] <rtg> lamont: rf-kill switch?
[17:45] <lamont> rtg: spoilsport. :-)
[17:45] <lamont> how about an NM that'll DTRT (and let me teach it what that is) when both wired and wireless are available? :-)
[17:46] <rtg> lamont: I think there is an outstanding bug wherein NM does not down the interface if its not in use.
[17:46] <lamont> ah
[17:47]  * lamont downs wlan0
[17:47] <lamont> and then in a bit, we'll see if NM auto-ups it when the wired is gone on unsuspend
[17:47] <rtg> it likely will.
[20:00] <mkrufky> is lpia 32bit?
[20:32] <amitk> mkrufky: yes it is
[20:33] <mkrufky> thanks, amitk
[23:44] <lamont> BenC: (or rtg? or...) does intrepid want to merge git-core 1.5.6-1 ish?  or are we happier with 1.5.4.3-1ubuntu2?
[23:45] <lamont> 'cause I think that requires paperwork now