=== asac_ is now known as asac
[03:41] <rtg__> infinity: got it. I'll do it in London on Monday.
=== gnomefre1k is now known as gnomefreak
=== emgent_ is now known as emgent
[14:20] <qense> The Intel chipset drivers are in the normal kernel, aren't they?
[14:30] <mjg59> Yes
[14:35] <qense> ok, thx
[16:27] <hxu> Hi! I need to build a kernel module against the Ubuntu 8.04 kernel. In redhat-like distros, you usually have a kernel-devel package which contains enough kernel source for you to do kernel development.  Is there a kernel devel package in Ubuntu?
[16:30] <Nafallo> linux-headers IIRC
[19:07] <Nxx> hi
[19:08] <Nxx> does anybody know how to make sound work under ubuntuu?
[19:10] <crimsun> what doesn't work on your audio hardware?
[19:12] <rysiek|pl> hi all
[19:12] <rysiek|pl> it's quiet... too quiet
[19:12]  * rysiek|pl feels uncomfortable
[19:13] <crimsun> Nxx: ping me in #ubuntu if you need to troubleshoot.
[19:13] <rysiek|pl> anywhoo... do *anybody* know about any workarounds of i8042 bugs?
[19:13] <rysiek|pl> my laptop's (LG E200) keyboard dies as soon as the kernel kicks in
[19:14] <rysiek|pl> needless to say it's quite a showstopper ;)
[19:28] <rysiek|pl> anybody?
=== pwnguin_ is now known as pwnguin
[20:46] <rysiek|pl> guys, I need some serious help with a laptop keyboard that is not functioning in Linux
[20:46] <pwnguin> are you going to write a kernel patch for it?
[20:47] <rysiek|pl> if need be and it will not be some depp-kernell kick-ass kung-fu, why not
[20:47] <rysiek|pl> pwnguin: why?
[20:47] <pwnguin> because this is #ubuntu-kernel
[20:47] <rysiek|pl> anywhoo: it seems to start working after I pass the kernel an i8042.dumbkbd=1 option - but "caps lock" light does NOT light upon using capslock (though capslock works aok, ie. the letters are big)
[20:47] <pwnguin> from topic: "kernel development ONLY"
[20:47] <rysiek|pl> pwnguin: yes, I know
[20:48] <rysiek|pl> pwnguin: google, launchpad, ##linux, ##kernel, #debian, #ubuntu-pl, #kubuntu, #ubuntu and still nothing
[20:49] <pwnguin> perhaps your laptop vendor will know more about the hardware?
[20:49] <rysiek|pl> pwnguin: through those 6 hrs of fighting and testing, and re-testing I have come to believe it's a problem with the i8042 PS/2 driver in kernel and some quirky chipset of the laptop I have here
[20:49] <rysiek|pl> pwnguin: so I am turning - at the very last - to the only place that seems to have people with enough expertise to help me debug this bugger
[20:49] <pwnguin> just about every laptop chipset is "quirky" :)
[20:50] <rysiek|pl> pwnguin: e.g. look at dmesgs (i8042.debug=1) or tell me what options should I try now
[20:51] <rysiek|pl> pwnguin: I have programmed in C a wee bit (not much, and no kernel stuff, but I will know a pointer from a comment...) and - given only little help - I can try to patch the bugger
[20:52] <pwnguin> irc is a rendevous protocol for debugging something like this; you really want to collect all this information in one place and point experts to that at their leisure
[20:52] <rysiek|pl> pwnguin: I have got everythin https://wiki.ubuntu.com/DebuggingKeyboardDetection said I should
[20:53] <rysiek|pl> pwnguin: plus dmesgs from ~10 different runs of the single mode with different options passed
[20:53] <pwnguin> you mentioned launchpad
[20:54] <pwnguin> does this mean you filed a bug?
[20:55] <rysiek|pl> I'm back
[20:55] <rysiek|pl> pwnguin: not yet. I am not 100% sure it's not a dupe of 2-3 I have found
[20:55] <rysiek|pl> pwnguin: although I do have (apparently) different chipset and a wee bit different problems
[20:56] <rysiek|pl> pwnguin: i.e. in one bug the keyboard stops working AFTER suspend/resume, but besides that it's exactly what I have
[20:57] <rysiek|pl> so, still testing. ;)
[20:57] <pwnguin> i'd say file the bug and dup it as nessecary
[20:57] <rysiek|pl> pwnguin: if you have a bit of time, I could point you the dmesgs, lspci logs, etc.
[20:57] <rysiek|pl> ok, will do
[20:58] <rysiek|pl> darn, gtg for a while, be back in 45mins
[20:58] <rysiek|pl> thanks for your time ;)
[20:58] <pwnguin> well, i don't do much kernel hacking yet
[20:58] <pwnguin> don't expect a lot of real help from me, but filing the bug might trigger something
[21:05] <pwnguin> reminds me i still need to follow up with the SD hci guy =(
[21:24] <emgent> heya
=== reynaldo_ is now known as reynaldo
[21:35] <pwnguin> what's the right way to request a patch be brought into Ubuntu's kernel?
[22:10] <rysiek|pl> pwnguin: I would say "guys, could you bring this-and-that patch into ubuntu's kernel?" ;)
[22:11] <dupondje> somebody awake to help creating a patch ?
[22:12] <dupondje> a fix in fact :)
[22:12] <pwnguin> well i just see over and over again this pattern where people file a bug against ubuntu, it lingers collecting more and more "is anyone listening" until some lone rider outside the kernel team decides to press upstream and writes a patch
[22:14] <dupondje> I found the change that makes it crash ...
[22:14] <dupondje> its 10 lines ...
[22:15] <rysiek|pl> dupondje: what does you patch fix? (and *do* tell me it's either atheros ar242x, or i8042 on ATI chipsets... ;) )
[22:15] <dupondje> its a official ubuntu patch ...
[22:15] <dupondje> for the kernel
[22:15] <dupondje> Areca Raid controller
[22:15] <rysiek|pl> dupondje: *disclaimer* I am a complete n00b and I cannot help with the patch
[22:15] <dupondje> arcmsr
[22:16] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/235889
[22:16] <dupondje> check bottom :)
[22:17] <sectech> Is there a wiki or something that shows what the pci probe error messages mean? I am am triaging a bug that has a PCI probe fail with error -16
[22:59] <dupondje> Who can commit the patch to the Ubuntu Kernel ?
[22:59] <dupondje> would be cool if it was fixxed
[22:59] <dupondje> in next kernel rls