=== NCommander is now known as Guest48610
[02:13] <mozmck> What is the difference between the source from ubuntu-karmic.git and that obtained with apt-get source linux-image* ?
[02:20] <ikepanhc> mozmck: ubuntu-karmic.git is the version control tree of karmic kernel, and what you get from apt-get source is the source code of a signle version
[02:21] <mozmck> I see, so the git will have changes now that haven't gotten into the last released version.
[02:22] <ikepanhc> mozmck: yes
[02:22] <mozmck> thanks.
[02:33] <RAOF> I've sent a couple of messages to the kernel-team@ mailing list about the current state of nouveau & what we can do to incorporate it in Lucid, but they seem to by falling into a black hole, and I'm uncertain about how to respond to this.
[02:34] <RAOF> https://lists.ubuntu.com/archives/kernel-team/2009-December/008095.html is an example.  Has the kernel team come to a consensus as to what to do about nouveau, and so my investigations are useless noise?
[02:35] <RAOF> Or is everyone taken up with other tasks, and no-one's specifically in charge of nouveau so it's just going unremarked?
=== Guest48610 is now known as NCommander
[03:15] <mozmck> how do I change the kernel configuration using the git tree?  can I just run make xconfig?
[03:19] <dtchen> RAOF: priorities, etc.
[03:20] <RAOF> mozmck: Depends on what, precisely, you're trying to do.  There are targets for changing the config in debian/rules, and that'll hook in with the various foo-{generic,server,virtual,etc} flavours.
[03:21] <mozmck> hmm, I'm adding a patch for rtai and I need to enable some new options it will add and change some others.
[03:22] <mozmck> trying to make a basically generic kernel otherwise.
[03:23] <RAOF> If you want to make packages out of it, use the debian/rules targets.
[03:23] <RAOF> If you just want to build from the same tree, go wild!
[03:26] <mozmck> I want to make packages.  so will the debian/rules targets see the new options and put them in?  I'm used to using make menuconfig or xconfig
=== NCommander is now known as Guest88322
[03:28] <RAOF> mozmck: Check out debian.master/rules.d/2-maintainer.mk; that defines targets like "updateconfig" and "docrazystuffwithconfig".  They'll run a configuration interface & then merge the results back into the flavour system.
[03:28] <mozmck> ok, thanks!
=== Guest88322 is now known as NCommander
[06:43] <Vamp898> Hi, with 2.6.32 my Wirelss Card RT2860 does not work anymore http://bugzilla.kernel.org/show_bug.cgi?id=14750 is there a chance to use an older kernel until its fixed?
[06:43] <ubot3> bugzilla.kernel.org bug 14750 in Staging "rt2860 does not work anymore in 2.6.32" [High,New] 
[06:48] <ikepanhc> Vamp898: as I know, rt2860 driver is still in staging, do you enable it?
[06:50] <Vamp898> for sure^^ there wireless card is detected too
[06:50] <Vamp898> its just unable to connect
[06:50] <Vamp898> the same happend with RT2870 after they renamed it from ra0 to wlan0 and now the same with RT2860
[06:51] <Vamp898> http://pastebin.com/d4f1a1634
[06:56] <Vamp898> with kernel 2.6.32 the RT2870 problem was fixed
[06:56] <Vamp898> but now 2860 does not work anymore and i dont want to wait until 2.6.33 without any internet
=== ogra_ is now known as ogra
[17:05] <Sarvatt> hmm,  /sys/class/thermal/thermal_zone0/temp started reporting as 47000 instead of 47 somewhere in the past few kernel releases, kind of scared to adjust acerhdf fanon and fanoff values to work with that because whenever its fixed my fan wont come on anymore
[17:06] <Sarvatt> or does anyone know if that change was intentional?
[17:09] <Keybuk> I would imagine so
[17:09] <Keybuk> temp
[17:09] <Keybuk>         Current temperature as reported by thermal zone (sensor).
[17:09] <Keybuk>         Unit: millidegree Celsius
[17:09] <Keybuk>         RO, Required
[17:09] <Keybuk> it's certainly documented as being in thousandths of a degree
[17:11] <mjg59> Sarvatt: Yes. It was a bug that acerhdf reported in degrees.
[17:11] <Sarvatt> ah thanks, indeed i found the acerhdf commit that made it milidegrees, was worried it would possibly change back to degrees but it looks like its safe to adjust the module parameters
[17:11] <Keybuk> commit 7129b126cc64f530d793bd56eb1709a06ec65a2d
[17:11] <Keybuk> Author: David Fries <david@fries.net>
[17:11] <Keybuk> Date:   Wed Feb 6 01:38:09 2008 -0800
[17:11] <Keybuk>     W1: w1_therm.c standardize units to millidegrees C
[17:12] <Keybuk> commit 5e012760dfd5ec24c41b9eab9e654a88360bb026
[17:12] <Keybuk> Author: Zhang, Rui <rui.zhang@intel.com>
[17:12] <Keybuk> Date:   Thu Feb 28 07:51:30 2008 +0800
[17:12] <Keybuk>     ACPI: thermal: show temperature in millidegree Celsius
[17:12] <Keybuk> etc.
[17:14] <Sarvatt> sorry for the noise and thanks for the help, i should have looked harder :D
[17:16] <Sarvatt> i just have to be careful booting a .31 kernel in that case
[17:55] <Laibsch> How does the Kernel team apply patches?  Patch the source and let it go to diff.gz or does it use a patch system?
[17:56] <Laibsch> Looking at the unpacked source, it seems to be the former
[17:56] <Laibsch> But the kernel package is complicated and I'd like to verify
[17:57] <rtg> Laibsch, start here: https://wiki.ubuntu.com/KernelTeam/KernelMaintenance
[17:57] <Laibsch> I was reading that (and lots of other wiki pages)
[17:57] <Laibsch> yet, I still don't know
[17:57] <Laibsch> it's a simple question
[17:57] <Laibsch> (or isn't it)
[17:57] <Laibsch> (or isn't it?)
[17:58] <rtg> Laibsch, its not, which is why there are multiple wiki pages on the topic
[17:58] <Laibsch> OK
[17:58] <Laibsch> It's about bug 444801
[17:58] <ubot3`> Malone bug 444801 in linux "prism 2.5 broke in 2.6.30.x (fixed upstream in 2.6.32)" [Medium,Fix released] https://launchpad.net/bugs/444801
[17:58] <Laibsch> which I reported
[17:59] <Laibsch> I did not have wifi for a while so could not test the fix that has already landed upstream
[17:59] <Laibsch> I want to test now and ultimately get the fix into karmic
[17:59] <Laibsch> lucid kernel seems to already have it
[17:59] <Laibsch> what do you suggest I do?
[18:00] <rtg> Laibsch, run the lucid kernel with karmic userspace
[18:00] <Laibsch> then I have the fix, nice
[18:00] <rtg> Laibsch, alternately, install linux-backports-modules-karmic-generic
[18:00] <Laibsch> But I'd like to get the fix into karmic for everyone's benefit, too
[18:00] <rtg> which is 2.6.32 based
[18:01] <Laibsch> rtg: thanks for helping me
[18:01] <Laibsch> I'm not looking for support
[18:01] <Laibsch> but for a way to properly backport the fix
[18:01] <Laibsch> for everybody
[18:01] <rtg> Laibsch, understood, but LBM _is_ the fix, not the main kernel.
[18:01] <Laibsch> I see
[18:02] <Laibsch> Maybe it should be installed by default, then?
[18:02] <rtg> Laibsch, nope, LBM is, and will remain, an elective install.
[19:00] <Laibsch> rtg: unfortunately, LBM does not fix the issue, it makes my wifi card completely dysfunctional!  I have to concede, though, that the card won't work with today's mainline kernel, either :-(
[19:01] <rtg> Laibsch, hmm, I thought you said it had been fixed upstream?
[19:01] <Laibsch> there was a patch committed
[19:01] <Laibsch> And indeed, I verified the patch works
[19:01] <Laibsch> -> see discussion in the bug
[19:01] <Laibsch> But it seems there is some other regression
[19:01] <rtg> Laibsch, commited after2.6.32?
[19:02] <Laibsch> not sure when it happened
[19:02] <Laibsch> the patch to fix the original issue made it into 2.6.32, I believe
[19:02] <Laibsch> bug 444801
[19:02] <ubot3`> Malone bug 444801 in linux "prism 2.5 broke in 2.6.30.x (fixed upstream in 2.6.32)" [Medium,Fix released] https://launchpad.net/bugs/444801
[19:03] <Laibsch> I'm currently recompiling the lucid kernel for karmic
[19:04] <Laibsch> I'll see if the lucid kernel has the problem (I suspect it does)
[19:04] <Laibsch> I'll open a new ticket, then
[19:05] <rtg> Laibsch, why not just install the deb? you don't need to rebuild it
[19:05] <Laibsch> I don't?
[19:05] <Laibsch> I wasn't sure
[19:05] <rtg> Laibsch, no, just use dpkg.
[19:05] <Laibsch> I usually always recompile binary packages
[19:05] <Laibsch> OK
[19:05] <Laibsch> Thanks
[19:07] <rtg> Laibsch, the patch in the bug report went in as of 2.6.32-rc1, so Lucid ought to be right. I'm surprised LBM didn't fix it also.
[19:07] <Laibsch> I suspect a separate regression
[19:13] <Laibsch> brb
[20:00] <Laibsch1> rtg: lucid kernel works and is free of the original problem as well
[20:02] <rtg> Laibsch1, cool, glad you're back in business
[20:02] <Laibsch1> I guess outlook is gloomy, though
[20:02] <Laibsch1> I'm glad I caught the error early
[20:02] <Laibsch1> I guess it's time for another kernel bug report upstream
[20:32] <yoasif> hey guys
[20:32] <yoasif> quick question
[20:32] <yoasif> im running lucid and id like to report a bug with my webcam
[20:32] <yoasif> apport recommends that i try with a mainline kernel 
[20:32] <yoasif> should i download the rc8 version on the mainline server or the plain 2.6.32?
[20:33] <rtg> yoasif, use the plain 2.6.32 since its the official. 2.6.32.1 should also be there.
[20:34] <yoasif> rtg, so just grab the kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/ (along with the headers and etc?)
[20:35] <rtg> yoasif, you shouldn't need the headers unless you have a DKMS dependency (like nVidia)
[20:35] <yoasif> yeah, i do have nvidia -- do i need to get the sources too, or no -- it's a large file
[20:35] <rtg> just the headers
[20:35] <yoasif> sounds good, thanks rtg
=== Laibsch1 is now known as Laibsch