=== bladernr_ is now known as bladernr_afk
=== smb` is now known as smb
[08:58] <zenith> my touchpad is not detected by the kernel during boot, & i need to use the i8042.reset parameter for it to be detected... how should i go about finding out the cause of  the problem ? I'm using Ubuntu 11.10 with all updates including proposed.
[09:04] <smb> zenith, First (if you have not already), you should create a bug report by running "ubuntu-bug linux". Then I think it will help to gather debugging output of the controller. There is a i8042.debug option I believe. If you gather dmesg output in both (with and without i8042.reset in parallel)
[09:05] <smb> I found it helpful to have a second machine to ssh from there because otherwise every keypress or mouse move adds more debugging output
[09:07] <zenith> where/how should the i8042.debug option be used?
[09:07] <smb> Same as the reset on the kernel arguments list
[09:07] <zenith> oh
[09:11] <zenith> actually i have subimitted some reports on the bug LP#190283, but i think i made a mistake coz the original bug report was for Intrepid ! (I'm SiddhantSaraf in the bug comments btw)
[09:12] <smb> bug 190283
[09:12] <ubot2`> Launchpad bug 190283 in linux "my lenovo y500 touchpad and keyboard do not work" [Undecided,Confirmed] https://launchpad.net/bugs/190283
[09:12] <zenith> i even reopened the old bug ... was it a mistake? should i have filed a new bug against Oneiric ?
[09:13] <smb> Hm, is your machine a lenovo y500
[09:13] <zenith> yup
[09:13] <zenith> actually its touch not being detected has been a very old issue, Ubuntu forums are full of the issue
[09:13] <smb> Usually it is better to have a new report if either the hardware or the symptoms are not exactly the same. Its always possible to mark them duplicate later.
[09:13] <zenith> *touchpad
[09:15] <zenith> ok, i think i will file a new bug, after i use the i8042.debug option
[09:15] <smb> Can happen. Also the problem often is that things can change by bios updates...
[09:16] <smb> There is already a section in the driver which potentially adds the reset for certain vendors / machines automatically
[09:16] <smb> But having more debug data will definitely help arguing the case
[09:17] <smb> And at least the subject line of the old report seems to indicate that the keyboard had not worked either
[09:17] <smb> which I assume it does for you...
[09:17] <zenith> oops, forgot to mention... the keyboard is another issue..
[09:18] <zenith> its a bit insteresting...
[09:19] <smb> Ah I see. Its erratic
[09:19] <zenith> on the login screen, where my keyboard and touchpad both don't work, using a USB mouse if i select 'suspend', then i can bring the computer out of suspen using any key on the keyboard !! & after that thekeyboard works (though the touchpad still doesn't)
[09:20] <zenith> *suspend
[09:20] <smb> And with i8042.reset both works?
[09:20] <zenith> yeah
[09:25] <zenith> in the output of 'cat /proc/bus/input/devices' the keyboard appears last (when i use the suspend trick), with 'Handlers=sysrq kbd event8' while with i8042.reset it'Handlers=sysrq kbd event4', so definitely the keyboard is detected on resuming from suspend
[09:25] <smb> Ok, at least that sounds like adding that machine to the exception table would make sense. On the other hand, but I surely have not followed this in any forums, that bug report at least did not seem to attract many other reporters. So when before creating a new bug, I would check on the Lenovo site that you got the latest BIOS (just to be sure). Maybe you have already
[09:26] <zenith> ok, i will check...
[09:26] <zenith> be right back
[09:26] <smb> I would suspect there is a kind of reset when suspending and resuming. But probably not as complete as when using the reset argument
[11:43] <jibel> bjf, could you refresh http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-p-tracking-bugs.html and http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html please ?
[12:17]  * ppisati is hungry...
[12:25]  * smb too
=== bladernr_afk is now known as bladernr_
=== chuck_ is now known as zul
[15:37]  * ogasawara back in 20
=== yofel_ is now known as yofel
[16:00] <bjf> jibel, i'll look into it
=== bladernr_ is now known as bladernr_afk
[16:21]  * ppisati -> disappears for a bit...
[16:43] <bjf> jibel, the reports are fixed up
[16:53] <diwic> What am I doing wrong if I'm getting this error:
[16:54] <diwic> "II: Checking modules for generic...previous or current modules file missing!"
[16:56] <jibel> bjf, thanks
[16:59] <bjf> diwic, where are you doing your build ?
[16:59] <diwic> bjf, from git clone ...ubuntu-precise
[17:00] <diwic> bjf, with a new entry to debian.master/changelog, and some patches on top
[17:01] <bjf> diwic, are you using one of our build resources or your own local system ?
[17:03] <diwic> bjf, local system, just installed precise on a machine here, and building from there
[17:03] <diwic> so both target and host is precise
[17:04] <tgardner> diwic, did you verify you could build _before_ you started hacking ?
[17:04] <diwic> tgardner, nope
[17:06] <bjf> diwic, i was asking if you were using tangerine so that i could look at your sandbox
[17:06] <bjf> diwic, or one of the other build systems
[17:06] <diwic> bjf, I'm building on my laptop right here
[17:06] <bjf> ugh
[17:06] <ogra_> isnt he just missing the ignore files ?
[17:08] <bjf> diwic, how long does it take to do a build on your laptop ?
[17:08] <diwic> bjf, http://paste.ubuntu.com/792869/
[17:08] <tgardner> ogra_, possibly, but unless he's twiddling config options I wouldn't expect to have a module go missing.
[17:09] <ogra_> it says modules "file" missing 
[17:09] <bjf> diwic, our build resources are there for fast building and you should have access
[17:09] <diwic> tgardner, to be fair, one of the patches adds a new config option (and, I assume, turns it on by default)
[17:09] <ogra_> which i ususally get on manual builods if i dont touch the ignore file
[17:09] <tgardner> bjf, I think he's mucked about with the changelog and did not start a new release, e.g., didn't move the ABI files forward
[17:09] <ogra_> but you know your system better, i only build kernels once a year or so :)
[17:10] <bjf> tgardner: yes, that's what i'm guessing as well
[17:10] <tgardner> bjf, don't we have an RTFM in the wiki somewhere  about version bumping ?
[17:11] <bjf> tgardner: looking
[17:11] <diwic> tgardner, I added a version entry 3.2.0-7.14~jackdection, old version was 3.2.0-7.13
[17:11] <bjf> diwic, that's what caused your problem
[17:12] <diwic> bjf, what version number do you suggest
[17:12] <bjf> diwic, if you had not bumped the build number you'd have been ok (probably)
[17:12] <tgardner> diwic, you can likely get by with just adding '~jackdetection' to the existing changelog entry.
[17:12] <diwic> tgardner, or +jackdetection if I want it to supersede? Otherwise the changelog would be in the wrong order...?
[17:12] <tgardner> diwic, right
[17:12] <diwic> which possibly something else will complain about 
[17:13] <bjf> diwic, the other things your could do are to rename the debian.master/abi/3.2.0-7.13 to debian.master/abi/3.2.0-7.14   -or-   add the "ignore" files so the checking is skipped
[17:15] <bjf> tgardner: yes, that's what i'm guessing as well
[17:15] <bjf> diwic, look at https://wiki.ubuntu.com/KernelTeam/KernelMaintenance#Overriding_ABI_check_failures
[17:16] <diwic> bjf, tgardner, ogra_, thanks for helping, I'll start a new build named 3.2.0-7.13+jackdetection, AND add ignore ABI checks, just to be sure :-)
[17:16] <bjf> diwic, and i'd recomend moving your build to a fast build resource
[17:17] <diwic> bjf, btw, the inspiration for using 7.14~jackdetection was taken from https://wiki.ubuntu.com/Kernel/KernelBisection (section "Give this test a version number"). Is there something subtle I'm not seeing, or is that wiki page wrong?
[17:17] <bjf> diwic, looking
[17:19] <bjf> diwic, yes, that assumes some knowledge not explained on that page (but which we just sort of explained to you above)
[17:20] <ppisati> herton: about the M/dove kernel, i erraneously pasted the lucid url
[17:20] <ppisati> herton: now i corrected it, hope you didn't start with the packaging
[17:20] <herton> ppisati, yep, saw that, I used the right one when building the package
[17:20] <herton> I saw you pushed the rebase to the maverick branch
[17:20] <herton> *maverick repo
[17:21] <ppisati> ah ok
[17:25] <diwic> bjf, a stupid question, am I supposed to do "fakeroot debian/rules binary-generic skipabi=true"?
[17:25] <bjf> diwic, one sec, there is another skip that you can put on the command line (skipmodules=true maybe)
[17:26] <apw> it may be singular, need to check
[17:26] <bjf> diwic, apw is correct, it is singular "skipmodule=true"
[17:29] <diwic> bjf, adding both skipabi and skipmodule made the build proceed, thanks
[17:29] <diwic> bjf, for the record, do you have a wiki page for getting started with the tangerine build resources?
[17:30] <diwic> bjf, I tend to use it so seldom (dkms is faster and sufficient for most things) I forget it between times
[17:31] <diwic> bjf, got the link from vanhoof, thanks 
=== BenC__ is now known as BenC
[17:32] <bjf> diwic, np
[17:35] <bjf> jjohansen: be sure and pack ear plugs (you've been warned)
[17:35] <jjohansen> bjf: ?
[17:35]  * smb assumes the roomie list went out
[17:36]  * vanhoof thinks of manjo 
[17:36] <manjo> ?
[17:36] <vanhoof> lulz
[17:36] <bjf> jjohansen: my snoring is bad from what the wife is saying
[17:36] <manjo> vanhoof, you looking for a roomie ? 
[17:37] <vanhoof> manjo: not you! :)
[17:37] <manjo> heh
[17:37] <vanhoof> believe i'm rooming w/ jk
[17:37] <jjohansen> bjf: heh, np. I wasn't planning on sleeping anyways
[17:37] <manjo> wonder who my victim is this time 
[17:37] <bjf> jjohansen: right, should have known
[17:37] <vanhoof> manjo: none listed for you
[17:38] <manjo> wohoo
[17:38] <apw> i don't know if it is good or bad to always be the dogleg
[17:39]  * vanhoof googles dogleg
[17:39] <apw> vanhoof, doubt its in there: when you have 5 people at a table and you are the one without someone opposite you, you are the dogleg
[17:40] <smb> 5th wheel on the car?
[17:40] <vanhoof> apw: ah
[17:40] <apw> heh, the 5th wheel is something else alllll together
[17:40] <vanhoof> apw: third wheel?
[17:41] <diwic> and the new kernel boots! with the new jack detection interface \o/
[17:41] <vanhoof> diwic: nice :)
[17:42] <smb> apw, It is deemed a bit useless, though depending on whether you think of the steering or reserve wheel its probably more useful than the dogleg. :)
[17:42] <apw> yeah a different feeling to teh word, dogleg in this context is "will be a bit left out on the end there"
[17:42] <apw> and 5th wheel is "mostly we can do without them"
[17:43] <apw> now of course it would be common to put your "5th wheel" on the "dogleg" when seating them :)
[17:43] <bjf> woohoo! just found 3500 Forint
[17:43] <apw> 2 beers
[17:43] <smb> maybe
[17:46]  * smb stumbles over some Korunas... Damn, wrong place...
[17:48]  * apw finds 10K forint, can anyone remember how many to the pound there are
[17:48] <herton> only 1260 forint here, I guess I'll be thirsty :)
[17:48] <smb> apw, Mr Google will know
[17:48] <apw> 25 quid
[17:49] <apw> smb, was a large beer 800 ?
[17:49] <smb> hmm... thought 600... but who knows what changes they made
[17:50] <apw> yeah, and how much we annoy them, so about 12 large beers, thats pretty good, i might be able to stand you a drink :)
[17:52] <smb> apw, Seemed to have stashed some 30K of them... Should be enough for the first night... :-P
[17:52] <apw> smb, you are set for the week :)
[17:52] <bjf> apw, my 3500 are work $14
[17:53] <bjf> s/work/worth/
[17:55] <apw> bjf, good job you reminded me, i'd have probabally left them at home
[17:59] <arges> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736226
[17:59] <ubot2`> Launchpad bug 736226 in linux "bonding inside a bridge does not work when using arp monitoring" [Medium,Confirmed]
[19:06]  * tgardner -> lunch
=== bladernr_afk is now known as bladernr_
[20:05]  * herton -> eod
=== jono is now known as Guest4459
[21:39]  * tgardner -> EOD