[00:47] <trimeta> soren: Thanks.
[05:55] <Sydero> Anyone know the minimum version of gcc required to compile kernel 2.6.28?
[06:00] <dtchen> Documentation/Changes lists 3.2
[06:00] <Sydero> thanks
[13:10] <Kano> hi rtg , there are several issues with your 2.6.30 kernel
[13:11] <Kano> first
[13:12] <Kano> drivers/staging/Kconfig b/drivers/staging/Kconfig
[13:12] <Kano> why on earth did you disable 3 drivers?
[13:12] <Kano> funnyly you even patched one of those disabled drivers
[13:13] <Kano> rt2870 got an added id
[13:13] <Kano> but it never was compiled
[13:13] <Kano> that added id conflicts merging with 
[13:14] <Kano> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a9ed12e5c149b05adf13bea5f1e96d68c2127faf
[13:14] <Kano> thats after rc5,but add it, then you could add the added it you have in your tree
[13:15] <Kano> i hate to resolve it everytime
[13:15] <Kano> next
[13:15] <Kano> i found the issue why the kernel did not boot on my systems with saa7136 tv card
[13:16] <Kano> the error was s626 module
[13:17] <Kano> can be solved when you do disable CONFIG_COMEDI, which is useless for me anyway
[13:18] <Kano> last thing is
[13:18] <Kano> if you want to be able to use fglrx with all tricks then you need
[13:18] <Kano> http://kanotix.com/files/excalibur/linux-2.6.30-generic/source/2.6.30-export-flush_tlb_page.patch
[13:18] <Kano> and if you do not want to use a very huge patch then use
[13:18] <Kano> http://kanotix.com/files/excalibur/linux-2.6.30-generic/source/2.6.29-ubuntu-copy-headers-for-fglrx.patch
[13:19] <Kano> Host/Kernel/OS  "Kanotix" running Linux 2.6.30-4-generic i686 [ Kanotix Excalibur 20090506-17:27 ]
[13:19] <Kano> CPU Info        (1) Intel Core2 Duo E8400 @ clocked at [ 2999.000 MHz ]
[13:19] <Kano>                 (2) Intel Core2 Duo E8400 @ clocked at [ 1999.000 MHz ]
[13:19] <Kano> Videocard       ATI Mobility Radeon HD 3450  X.Org 1.4.2  [ 1680x1050 ]
[13:19] <Kano> Processes 140 | Uptime 1:03 | Memory 438.3/1977.9MB | HDD Size 1000GB (6%used) | GLX Renderer ATI Radeon HD 3450 | GLX Version 2.1.8591 | Client Konversation 1.1 | Infobash v2.67.1
[13:19] <Kano> with those patches it is possible to run fglrx
[13:19] <Kano> the export is absolutely required
[13:20] <soren> Kano: Why exactly is it that you don't report this on Launchpad? IRC is a horrible, horrible bug tracker.
[13:21] <soren> Horrible.
[13:21] <Kano> soren: there is no 2.6.30 in launchpad
[13:21] <Kano> as it is only git
[13:21] <Kano> or where are the packages
[13:21] <soren> a) yes, there is.
[13:21] <soren> b) that does not make IRC a better bug tracker.
[13:21] <apw> Kano, you are reporting issues with karmics kernel... as you say 'your 2.6.30'
[13:22] <Kano> soren: not my problem, i fixed the issues, fix em or leave it
[13:22] <apw> therefore there is a package to report it against
[13:22] <Kano> apw: i use git
[13:22] <Kano> as i require changes
[13:22] <Kano> which are not that important for u
[13:22] <apw> i use keyboards that doesn't mean that there isn't a bug tracker
[13:22] <Kano> fix it or not
[13:23] <ogra> fun
[13:23] <soren> Aw.
[13:25] <apw> there really are packages of the karmic kernel in the karmic release pocket
[13:27]  * TheMuso reads the above exchange, and finds himself thinking that if were on the kernel team, he'd ignore kano's "bug reports" out of spite. :)(
[13:38] <apw> heh, no we just tend to lose things that are only in irc
[13:40] <TheMuso> apw: I know that. kano refuses to use a bug tracker period. I've seen some things fixed that he's brought up in here, but I am sure there are many that aren'
[13:40] <TheMuso> apw: I know that. kano refuses to use a bug tracker period. I've seen some things fixed that he's brought up in here, but I am sure there are many that aren't.
[14:54] <apw> smb, can you remind me what was triggered when libusual was enabled
[14:55] <smb> apw, With libusual enabled this would try to handle registration of usb storage devices, which would try to load usb-storage rather early as it was built in
[14:56] <apw> ahh yes, usb storange, thanks
[14:56] <smb> no worries :)
[15:02] <apw> cking, your machine which is showing the bad sound ... what kernel is it running?
[15:05] <cking> 2.6.28-12.43
[15:10] <cking> apw: I don't think it's a kernel issue. The error I get is a pulseaudio big. "The CPU load limiter only becomes active as result of PA entering an
[15:10] <cking> endless loop of some kind. It's only symptom of a bug somewhere, but
[15:10] <cking> gives no hint where it actually is."
[15:10] <apw> i think that means you have the appropriate 'fixes' for the pointers stuff as i understand it, which might be triggering confused pulse
[15:11] <cking> I suppose I can roll back to an earlier kernel and test
[15:12] <cking> I've just spotted: hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[16:53] <apw> rtg this FIRMWARE_IN_KERNEL config change, do we know how much other firmware this may bring into the kernel other than the keyspan stuff?
[16:54] <rtg> apw: I think you have to selectively pick the drivers that get firmware. I think the option just enables those selections
[16:57] <apw> there appears to be a few other things which use fw-shipped-* in the Makefiles, which would be changed by it, as as soon as this option is turned on we longer put any firmware for any device which is =y into the firmware module from the kernel
[16:57] <apw> s/module/result blob/
[16:57] <apw> so i assume all of that firmware must go into the kernel image as well
[16:57] <apw> it doesn't look like _that_ much, just making sure its what you expect
[16:58] <apw> mod-fw := $(fw-shipped-m)
[16:58] <apw> # If CONFIG_FIRMWARE_IN_KERNEL isn't set, then install the 
[16:58] <apw> # firmware for in-kernel drivers too.
[16:58] <apw> ifndef CONFIG_FIRMWARE_IN_KERNEL
[16:58] <apw> mod-fw += $(fw-shipped-y)
[16:58] <apw> endif
[16:58] <apw> installed-mod-fw := $(addprefix $(INSTALL_FW_PATH)/,$(mod-fw))
[16:59] <rtg> apw: shit. I would not have expected that enabling the option would adversely affect other drivers. 
[16:59] <rtg> apw: so, should we put it in the linux-firmware package instead?
[17:01] <apw> rtg, risk wise perhaps so for sru ... a difficult call.  what happens to the firmware blob that the kernel builds during build of the kernel
[17:01] <apw> i wonder if that should be making its way wholesale into the firmware package
[17:01] <Kano> rtg: when do you merge aufs2?
[17:01] <Kano> rtg: http://aufs.sourceforge.net/README.aufs2
[17:02] <rtg> apw: dunno, lemme look at it again.
[17:02] <Kano> in the test live image is even squashfs 3.1 used, that will never work
[17:02] <Kano> you need a cvs snapshot
[17:02] <Kano> user space of course
[17:03] <Kano> as squashfs 4 is in the kernel since .29
[17:04] <Kano> hmm you are lucky,there is even a final 4.0
[17:04] <Kano> in sid
[17:05] <Kano> when i build my .29 test image i had to use cvs
[17:06] <Kano> well merge aufs2 (it is already .30 compatible) + update squashfs-tools in karmic, then you can hope ;)
[17:08] <Kano> rtg: do you want to update jaunty to 2.6.28.10 today?
[17:08] <apw> jaunty is released now so anything like that would be an sru
[17:08] <apw> that said i thought .28 was already in git
[17:08] <Kano> apw: i mean the jaunty branch
[17:08] <Kano> i do not use precompiled kernels
[17:09] <apw> the jaunty git tree has .10 in it
[17:09] <apw> commit 8bdd945b77faa2d7c63ad669d2d8b1a623c57e67
[17:09] <apw> Author: Greg Kroah-Hartman <gregkh@suse.de>
[17:09] <apw> Date:   Sat May 2 11:54:43 2009 -0700
[17:09] <apw>     Linux 2.6.28.10
[17:09] <Kano> ok
[17:09] <Kano> will compile it now
[17:11] <Kano> or do you want to add some more fixes soon?
[17:12] <apw> there are always commits in the pipeline
[17:13] <apw> as for aufs, that pending a decision on how live cd's will be done for karmic
[17:14] <Kano> you can have it the kernel even if you dont use it ;)
[17:14] <Kano> as you can use it without a live system too
[17:14] <apw> no point in carrying delta for something we don't use
[17:15] <Kano> so how do you want to create live images? anything new in casper yet
[17:15] <apw> no decision that i am aware of no
[17:15] <Kano> well i create live images, you talk about em ;)
[17:19] <Kano> apw: did you rebase jaunty today? or since when is there .10?
[17:19] <apw> jaunty doesn't rebase its released.  the commits for .10 went in about the 2nd
[17:20] <Kano> ok, then i have it already
[17:22] <Kano> so all i have to try now is aufs2... bbl
[20:06] <cluk> Hi
[20:07] <cluk> I am trying to provide linux-vserver kernel packages based on the ubuntu kernel in my ppa at:
[20:07] <cluk> https://launchpad.net/~christoph-lukas/+archive/ppa
[20:08] <cluk> the vserver kernel image for jaunty is working fine, the vserver functionality is also working fine
[20:08] <cluk> but I get an kernel oops when I try to load the nvidia module 180.44 build via dkms for this kernel.
[20:08] <cluk> could anybody help me debugging this issue?
[20:09] <cluk> the oops is here: http://paste.ubuntu.com/169897/
[22:17] <cluk> my linux-headers package seems to be broken which seems to break the nvidia module.
[22:17] <cluk> sorry for the noise.