[02:52] <maco> in which ubuntu git tree would i find drivers/char/drm/i915_drv.h?  I checked ubuntu/ubuntu-intrepid.git but it's not there
[02:54] <nigel_c> Feisty, Gutsy and Hardy all have it.
[02:54] <nigel_c> (Haven't checked earlier ones)
[02:55] <maco> it's gone in intrepid?
[02:56] <nigel_c> Not there in my git trees.
[02:56] <maco> :-/ i wonder where those macros moved in 2.6.27
[02:56] <maco> ok ill look through lxr
[02:56] <nigel_c> drivers/gpu/drm/i915
[02:56] <nigel_c> maco: ^^
[02:57] <maco> nigel_c: thanks
[03:04] <nigel_c> You're welcome
[05:24] <NCommander> lamont, I'd like to have my ubuntu-jaunty-ports branch blessed as the offical jaunty ports branch since there is no existing jaunty ports branch, and I'd like to be able to upload it (with the kernel teams blessing)
[06:34] <lamont> and I'd like a installable 2.6.27 for ia64
[06:34] <lamont> and iwl4965.ko for intrepid/i386
[06:37] <lamont> interestingly, iwl4965=y in config
[06:55] <NCommander> hey lamont 
[06:56] <NCommander> lamont, well, it compiles on ia64, but the box I have access to I don't own thus I can't even smoke test the kernels
[06:56] <lamont> the final intrepid kernel was ftbfs
[06:56] <lamont> so my ia64 box here running intrepid has 2.6.24 :(
[06:56] <NCommander> lamont, I'm talking jaunty
[06:57]  * NCommander has a 2.6.27.4 ports branch w/ apparmour and Ubuntu drivers added
[06:57] <NCommander> Even AuFS, though it needs some porting on ia64
[06:57] <NCommander> It builds on all port architectures (I just got sparc building tonight)
[06:57] <lamont> and for total amusement, my laptop works just fine with a livecd, not so fine with the hardy system upgraded to intrepid
[06:59] <NCommander> What architecture is your laptop ;-)
[06:59] <lamont> dell inspiron 1520 == iwl4965, running i386 kernel
[06:59] <NCommander> lamont, if you could smoke test my ia64 2.6.27.4 ports kernel, I'd apperiate it
[06:59] <NCommander> lamont, try blacklisting iwl4965, and using iwlagn
[06:59] <lamont> that'll happen at some point after I get a working laptop
[07:00] <lamont> iwlagn is what loads
[07:00]  * NCommander notes someone needs to go through the config for ia64 and sanity checking
[07:00] <NCommander> Most of the things that should be built as modules aren't, the upshot that virtually no udebs are being built
[07:01] <NCommander> I dunno what hardware is present or not on most ia64s, so all I did was blacklist every udeb that didn't have a module compiled for it (i.e., ppp/slip/etc.)
[07:01] <NCommander> THe upshot is I bet the installer is going to be completely hosed until someone can look at it
[07:02]  * lamont notes that he is totally ignoring ia64 tonight
[07:02] <NCommander> lamont, HPPA w/ 2.6.27.4 also builds and gets udebs
[07:02] <lamont> ditto
[07:02] <NCommander> :-)
[07:03] <NCommander> sparc?
[07:03] <lamont> tonight is: 1) fix laptop.  2) sleep
[07:03]  * NCommander runs for cover
[07:04] <NCommander> Ah
[07:04]  * NCommander needs to simply find what the kernel team wants before I find a sponsor for the ports kernel upload I want to do
[07:17] <NCommander> morning abogani 
[07:18] <abogani> NCommander: Good morning to you.
[07:19] <NCommander> abogani, how goes your morning
[07:19] <abogani> Just started ;)
[07:19] <NCommander> cool
[11:25] <Kano> hi, how about adding a 2.6.28 based git tree?
[12:02] <sebner> hi folks! is there any progress in getting the proposed fixes uploaded/What's needed for it?  bug #283316
[12:03] <sebner> no bot? :\
[12:57]  * lamont cries a little.  sleep made things different... now I have no ethernet:  eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:... is missing
[13:05] <rtg> lamont: forcedeth?
[13:05] <lamont> module version missmatch for the win
[13:06] <rtg> lamont: uh, are you off in the weeds?
[13:06] <lamont> ssb_dma_set_mask etc, etc.
[13:06] <lamont> 2.6.27-7.14 and .15
[13:07] <lamont> and it was me sleeping for a while, not the laptop. :(
[13:07] <rtg> oh, b44 which is dependent on SSB
[13:08] <lamont> and linux-b-m-g installed a new ssb.ko
[13:09] <lamont> but not a new b44.ko
[13:09] <rtg> lamont: do you mean lbm-intrepid?
[13:09] <lamont> well, yeah
[13:09] <lamont> once you dig through to l-b-m-2.6.27-7-generic :-)
[13:09] <lamont> could I maybe have a working wireless _AND_ b44?
[13:10] <rtg> lamont: ok, I remember this from Hardy. Can you start a LP report?
[13:10] <lamont> s/wireless/iwlagn/
[13:10] <lamont> sure
[13:10] <rtg> lamont: yes, as long as the wireless isn't b43.
[13:10] <lamont> against l-b-m-intrepid?
[13:10] <lamont> the wireless is iwl4965
[13:10] <rtg> lamont: I was gonna upload a new LBM today anyway. your timing is good.
[13:11] <rtg> yes - against LBM -intrepid
[13:11] <lamont> https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-intrepid <--- 404
[13:11] <lamont> so... against what source package?
[13:11] <rtg> just linux-backports-modules
[13:12] <rtg> lamont: be sure to assign me to it
[13:12] <lamont> sure
[13:12] <rtg> coffee, back in a few
[13:13] <lamont> https://edge.launchpad.net/ubuntu/+source/linux-backports-modules <-- also 404
[13:13] <lamont> ah, lbm-2.6.27
[13:16] <lamont> rtg: already reported as 287450, now assigned to y
[13:16] <lamont> ou
[13:16] <lamont> rtg: scream if you need more
[13:19] <lamont> meanwhile, working wireless is actually more important than working wired.  so I guess that's a win
[13:27] <rtg> lamont: well, I ought to be able to get both working. 
[13:28] <lamont> heh. ok.  if you need a tester, happy to help with that once I make the transition to town in a bit
[13:29] <rtg> lamont: I think I have a b44 in my quiver of laptops
[13:29] <lamont> inspiron 1520, fwiw 
[13:31] <rtg> lamont: cool. I'll bug you later this morning once I've got it uploaded (assuming wireless testing goes ok)
[13:55] <apw> rtg, hiya
[13:56] <apw> you remember that sound thing, the crackling on alsa oss working one ... well i redid all my testing against the updated intrepid kernel and the problem is still there and again my home build module is working fine whereas the 'standard' one is not
[13:56] <apw> you mentioned you had some issues with previously working laptops and i was wondering which ones they were
[13:57] <rtg> apw: you talked to me about this? If so, I don't remember. Is there a bug number?
[13:58] <apw> it was around the release so i can understand forgetting :)  bug #273578
[14:03] <rtg> apw: if OSS works, how does that make it a kernel issue? Seems more like ALSA library problems, perhaps pulseaudio?
[14:04] <rtg> apw: the other thing to look at is if there were quirks for your codec that went missing between Hardy and Intrepid
[14:22] <apw> rtg i agree the oss thing is confusing, but literally recompiling the module seems to make it work
[14:22] <apw> no other change, to userspace ... so something odd is going on for sure
[14:23] <apw> i can't see any quirks going away since 2.6.24 mainline
[14:25] <rtg> apw: can you get the same result by restarting pulseaudio ?
[14:26] <apw> nothing i did to pulse audio seemed to help at all
[14:28] <rtg> apw: 'killall pulseaudio; /usr/bin/pulseaudio -D --log-target=syslog' ?
[14:29] <apw> yep, that had no effect iirc, i can go reinstall the bad module and re-test if thats helpful
[14:30] <rtg> apw: the fact that you are getting any sound output at all indicates its probably not a kernel issue, especially if you are getting interrupts. run the sound test and watch /proc/interrupts for steady increases in IRQ count.
[14:31] <rtg> apw: also, describe in the bug report _exactly_ what you are doing wrt recompiling and insmod'ing etc.
[14:32] <apw> will add that info to the bug, but litterally just built it using fakeroot debian/rules binary-generic
[14:32] <apw> and copied the built version out of the debian directory into /lib/modules
[14:32] <rtg> apw: thats the part that doesn't make sense to me. why would a recompile have any effect?
[14:33] <apw> indeed, its completely illogical as i recall you went to try rebuilding a kernel youself
[14:33] <apw> as i was compiling on a 64 bit install
[14:33] <apw> with a different compiler from you, something like that
[14:34] <apw> will go redo that test with pulse audio and write up what i have done here
[14:34] <rtg> apw: thanks
[16:35] <jcastro> ogasawara: ~25 minutes until your session!
[16:36] <ogasawara> jcastro: thanks :)  I totally forgot about daylight savings being a factor so I would have been late!
[16:36] <jcastro> ogasawara: yeah that's been going around, I'm just doublechecking people just in case. :D
[16:39] <didrocks> rtg: apprently your advice correct the "too hot wifi card bug". I put a commentary. Thanks a lot and keep me in touch if you need more advanced tests
[16:40] <rtg> didrocks: I'll be updating LBM again later this morning, so watch for regressions.
[16:42] <didrocks> rtg: ok, I will
[16:43] <didrocks> rtg: basically, what was the cause of the issue? Too many calls to the Wi-Fi card?
[16:43] <rtg> didrocks: dunno. I didn't have time to drill that deep.
[16:44] <didrocks> rtg: ok. the most important is that it is corrected :)
[17:22] <drunkenkilla> hello
[17:23] <drunkenkilla> i can't regulate the screen brightness... is this a problem, which can be solved with the next kernel-version?
[17:54] <didrocks> rtg: I think that finally, it didn't fixed it
[17:54] <didrocks> it froozes
[17:55] <didrocks> then, I tried to switch back in a wired connexion
[17:55] <didrocks> but I just have now a red light (no green one) :/
[18:45] <didrocks> I am afraid that my network card is broken now :/
[21:51] <TomJaeger> So about bug #276990...
[21:52] <TomJaeger> Can this patch please be applied to the intrepid kernel? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=55d6a3cd0cc85ed90c39cf32e16f622bd003117b
[21:54] <rtg> TomJaeger: try linux-backports-modules
[21:54] <TomJaeger> The patch is clearly 100% safe and in any case has gotten some testing in linux-backports-modules
[21:55] <TomJaeger> rtg: Not everybody knows about linux-backports-modules
[21:55] <TomJaeger> plus, the iwlagn module in linux-backports-modules generates all kinds of additional kernel oopses
[22:00] <TomJaeger> I'm completely dumbfounded by this.  Why exactly are we exposing users to a module that is known to cause kernel panics when there is a one-line patch upstream working around the problem?
[22:01] <TomJaeger> And if we care about stability, why on earth would we recommend anyone to install a random daily snapshot of compat-wireless?
[22:03] <TomJaeger> And is it really to much to ask to set the importance of this bug to High?
[22:09] <rtg> TomJaeger: how about posting a request to kernel-team@lists.ubuntu.com lest I lose track of all the damn wireless bugs?
[22:22] <trv> does anybody know why linux-image-debug in intrepid is for 2.6.25 kernel and not 2.6.27? i want to find the vmlinux file for the current kernel
[22:32] <TomJaeger> rtg: done
[22:34] <TomJaeger> It's kind of sad that I have to spend my time arguing for something so obvious but here you go