[07:33] <smb> Morning +*
[07:41] <siji> hi All
[07:41] <siji> smb, GooAfterNoon
[07:41] <siji> *good
[07:42] <siji> regd bug:824589
[07:42] <smb> bug 824589
[07:42] <ubot2> Launchpad bug 824589 in ubuntu "improper Touch Screen Driver module(for arm beagleboard) for TSC2046 in the Expansion board,and it connect with DM3730 by SPI port ." [Undecided,Incomplete] https://launchpad.net/bugs/824589
[07:43] <siji> i have compiled the module again , but still TS is not working 
[07:43] <smb> Hm, not necessarily my area
[07:43] <siji> smb, ok
[07:44] <siji> now it's not returning any error messages, but not about find anything at /dev/input/..
[07:44] <siji> I hve tried evtest too 
[07:47] <smb> Well, if "not finding anything" means there is no automatically created dev, it may be a problem registering with the subsystem. 
[07:47] <siji> smb, so wht's the sol for it 
[07:48]  * smb s crystal ball is broken atm
[07:49] <smb> siji, Maybe look whether everything in the init code checks for errors and reports them...?
[07:49]  * apw yawns
[07:49] <siji> ok let me recheck 
[07:50] <smb> Morning apw 
[07:51] <apw> siji, does the driver even load
[07:51] <apw> smb, morning
[07:51]  * smb was assuming that from "not returning any error messages"
[07:52] <siji> apw, i think no, kernel.log is not shwing anything reg.ads 
[07:53] <apw> and if you load it manually ?
[07:53] <siji> lsmod dispalying the specific driver module 
[07:56] <apw> so the driver _is_ loaded in lsmod, but you have no output in dmesg for it, and no /dev/input elements appearing, correect ?
[07:56] <siji> apw, yes
[07:57] <apw> then your next step i guess is to add debug into the init path of the module to tell you why its not enabling the device
[07:58] <siji> ok
[08:39] <ppisati> morning *
[08:41] <smb> Morning ppisati 
[08:46] <cking> yawn
[10:18] <apw> cking, sounding like a lively morning
[10:38] <Daviey> smb: Hello sir!  Do you have a status update on bug 790712?  Is it likely to be resolved pre-release?
[10:38] <ubot2> Launchpad bug 790712 in linux "20110531 i386 server ISO: order 5 allocation failure during install" [High,Confirmed] https://launchpad.net/bugs/790712
[10:44] <apw> Daviey, expect he is away currently
[10:46] <cking> apw,  it's a slow day today - deep diving into daft bugs
[10:46] <Daviey> apw: ta, week vacation?
[10:47] <apw> Daviey, no he should be about later today
[10:47] <Daviey> cking: You could speed up your day by applying for upload access for that damn package.
[10:47] <apw> cking, sounds like fun
[10:47] <Daviey> apw: ta
[10:47] <apw> Daviey, like that'll be any more fun
[10:49] <cking> fun fun fun fun
[10:49] <Daviey> ha
[12:27] <mdeslaur> hey kernel hackers, it would appear something is missing for kernel 12.19 to get pulled in by dist-upgrade
[12:28] <apw> mdeslaur, yep i wouldn't think the meta package is updated yet, that has to wait until all the arches are built and approved
[12:29] <mdeslaur> apw: cool, just wanted to let you know in case
[12:29] <apw> mdeslaur, i would expect leann has that review and upload on her list for this morning
[12:29] <mdeslaur> apw: thanks
[12:29] <apw> mdeslaur, waiting for something specific in it ?
[12:30] <mdeslaur> apw: yeah, I want to test to update bug 858459
[12:30] <ubot2> Launchpad bug 858459 in linux "lock up on boot when network cable is unplugged" [Undecided,Incomplete] https://launchpad.net/bugs/858459
[12:30] <apw> mdeslaur, you could grab the binaries by hand of course
[12:31] <mdeslaur> apw: I will, thanks
[12:32] <apw> mdeslaur, what is interesting about that bug, is i have a 533 with an atl1c and i don't see that behaviour
[12:33] <mdeslaur> apw: how odd :)
[12:33] <mdeslaur> apw: the kernel team definitely needs more buggy hardware :)
[12:34] <apw> mdeslaur, hmm mine does have a 1969:2060 whereas you have 1969:2062 ... must be significant
[12:35] <apw> mdeslaur, and i suspect it won't help, i'd check whats being offered by stable but ... with k.o down there really isn't one
[12:35] <mdeslaur> my issue seems to be common with the 522, I've seen posts about it all over ubuntu/suse/fedora land
[12:37] <apw> mdeslaur, well if its still there in -12, which i suspect it will be then i'd suggest editing your grub entry from the grub menu, and 1) change the "set gfxpayload=" to be =text, then drop quient and splash from the command line and add debug
[12:38] <apw> and see if you get some indication as to why
[12:38] <smb> Daviey, That bug is very unlikely fixed pre-release. Mainly because neither me really looked much into it (I never saw this happen locally, though I certainly did not do that many installations. Also the question is always does it still happen? I will add the questions to the bug, but currently there is no good info to follow.
[12:38] <mdeslaur> apw: ok, thanks
[12:55] <apw> ppisati, did we ever get a response on what to do with rsalveti's patches ??
[12:56] <ppisati> apw: nope
[12:57] <ppisati> apw: uhm wait
[12:57] <ppisati> apw: i saw an email regarding some patches
[12:57] <ppisati> apw: let me check
[12:59] <apw> the patch is still in oneiric, i guess it isn't going anywhere this late anyhow
[13:07] <apw> ppisati, is this item going to happen 'look into generating a trimmed down config for debug purposes'
[13:10] <ppisati> apw: nope, that was more of a request on what i could turn on to ease debugging
[13:16] <ogasawara> mdeslaur: fyi, I just uploaded linux-meta.  it's pending approval in the upload queue and then should be available shortly thereafter.
[13:17] <mdeslaur> ogasawara: thanks!
[13:26] <lamont> http://pastebin.ubuntu.com/697256/ <-- ppisati why does your kernel hate on the panda?  (natty)
[13:53] <smb> That looks a bit like that thing that maybe is caused by that panel driver (some n900 thing)
[13:54]  * smb does a lot of hand waving gestures
[13:56] <ppisati> lamont: the natty kernel that i provided you or latest one?
[14:16] <lamont> latest
[14:16] <lamont> dist-upgraded last week
[14:22]  * ogasawara back in 20
[14:53] <tgardner> tyhicks, are you still getting email at your IBM address ? I see ecryptfs patches addressed to tyhicks@linux.vnet.ibm.com. Perhaps you should send a patch to update the MAINTAINERS file.
[14:53] <tyhicks> tgardner: thanks for the reminder - will update that today
[14:53] <tyhicks> tgardner: The IBM address should be bouncing
[14:54] <tgardner> tyhicks, you're assuming IBM has noticed that you're gone :)
[14:55] <tyhicks> tgardner: that is a big assumption ;)
[15:08] <mthaddon> bjf: howdy - is there any more debugging info I can provide for bug#853085? it's basically rendered by laptop unusable currently 
[15:08] <bjf> mthaddon, hi
[15:11] <bjf> mthaddon, were you running a previous oneiric and then you started having this issue after an update?
[15:12] <mthaddon> bjf: yes - I upgraded at beta, was seeing occasional issues, and then it got worse after an update (when I filed the bug)
[15:13] <bjf> mthaddon, can you go back to booting the kernel that "worked" ? and what version of that kernel is it that worked?
[15:14] <mthaddon> bjf: how do I force it to show me the grub list? normally it's hidden for me
[15:15] <bjf> mthaddon, hold the left shift as it's booting (when coming out of post and just before trying to boot a kernel)
[15:34] <mthaddon> bjf: I can boot (to a text console only) with 3.0.0-10-generic
[15:38] <mthaddon> bjf: actually, I can get to a text console with 3.0.0-11-generic too
[15:42] <mthaddon> so I'm not sure why I can't boot off today's daily build...
[15:47] <mthaddon> and once booted into unity 2d and udpated, and get another general protection fault
[15:47] <mthaddon> guess I could try older kernels and see if I can get into unity 2d
[15:53] <mthaddon> and I spoke too soon - this time it doesn't even boot with 3.0.0-10-generic
[15:59] <mthaddon> bjf: at this stage I can't see any clear pattern for one kernel versus another - all seem to fail in different ways at different attemps to boot (3.0.0-{9,10,11}-generic)
[16:14] <jjohansen> rebooting
[18:01]  * tgardner -> lunch
[20:15]  * jjohansen -> lunch
[22:53] <CanadianPirate> Does anyone know if the compat wireless patch is working in linux 3?