[00:21] <bgamari> how does one update a single module without repackaging the entire kernel
[00:22] <bgamari> I'm currently getting errors along the lines of: [    8.967377] dell_laptop: no symbol version for dcdbas_smi_request
[00:22] <bgamari> [    8.967380] dell_laptop: Unknown symbol dcdbas_smi_request
[10:20] <Kano> hi, could you disable commedi? the s626 module always locks up on my systems with saa7146 dvd card
[10:22] <Kano> 05:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7146 [1131:7146]
[10:22] <Kano> alias:          pci:v00001131d00007146sv*sd*bc*sc*i*
[10:22] <Kano> is in s626
[10:22] <Kano> and that locks up the system
[10:29] <Kano> usally controlled by budget-av
[10:30] <apw> sounds bad, that sounds like it needs a bug to remind me!
[10:31] <Kano> as all my systems have got dvb cards none will boot ubuntu
[10:32] <Kano> i prefer # CONFIG_COMEDI is not set
[10:33] <apw> may well be something a lot of people hit
[10:33] <apw> let me know the bug number and i'll have a look
[10:35] <Kano> maybe there is another solution, like a complete alias with 4 ids
[10:35] <Kano> just mailed the author
[10:35] <apw> cool
[10:35] <Kano> this is definitely too generic
[10:36] <Kano> all i can do is to disable it
[10:37] <Kano> sv*sd* is generic
[10:38] <apw> yeah it does seem rather overarching
[10:52] <Kano> CONFIG_HAVE_KERNEL_LZMA=y
[10:53] <Kano> how about using that? would not hurt at all
[10:55] <Kano> so rebooting to try without comedi
[11:21] <Kano> it of course boots without s626. but how about updateing ndiswrapper to 1.54
[11:21] <Kano> still 1.53 in there
[11:23] <apw> ndiswrapper is on the list for review
[11:24] <apw> kernel LZMA would potentially affect slow machines
[11:24] <apw> a
[11:24] <apw> and would need testing on those platforms to check for regressions
[11:24] <Kano> nobody mentioned that
[11:24] <Kano> i used that for -9 kernel for kanotix and really nobody metioned that it would be slower
[11:28] <amitk> Kano: how many users does Kanotix have?
[11:28] <Kano> not that many than ubuntu, but enough for me
[11:29] <amitk> Kano: I was just curious. The larger the test base, the better.
[11:33] <Kano> 118 kernel updates in logfile
[11:35] <amitk> I bet the majority of your users are very technical.
[11:35] <Kano> no
[11:35] <Kano> they just like better support
[11:37] <Kano> i provide support for fglrx for every kernel for example
[11:38] <Kano> nvidia of course too
[11:42] <Kano> also there are test image downloads with -9 kernel: 114 - 32 bit, 20 - 64 bit, 873 - combined, nobody mentioned slow loading speed
[11:43] <Kano> it is interesting that these images are not officially announced ;)
[11:46] <Kano> but rt2500usb seems to be really problematic
[11:46] <Kano> any launchpad entries for that yet?
[11:47] <Kano> i could fix one issue with removing ids from rt2500usb to use rt73usb for some cards, but those which are only in rt2500usb are still broken it seems
[11:48] <Kano> thats the only reason that somebody would downgrade currently
[11:48] <TheMuso> /c/c
[11:52] <Kano> http://bugzilla.kernel.org/show_bug.cgi?id=12309
[11:53] <ubot3> bugzilla.kernel.org bug 12309 in Block Layer "Large I/O operations result in slow performance and high iowait times" [High,Resolved: insufficient_data] 
[11:53] <Kano> what do you think about this bug
[12:07] <Kano> so added the cfq-ioshedul patch
[12:07] <Kano> http://kanotix.com/files/excalibur/linux-2.6.30-generic/source/
[12:07] <Kano> you find all used patches there
[12:12] <Kano> one patch seems to miss there
[12:12] <Kano> to cp ieee headers
[12:14] <Kano> so now it is there...
[13:00] <apw> can anyone tell me which key the sysrq tag is on on a standard keyboard?  none of mine have it marked ... BAH
[13:00] <lifeless> apw: laptop?
[13:00] <Kano> print
[13:00] <lifeless> apw: printscreen button probably
[13:00] <apw> lifeless, all and every one of my keybaords oddly
[13:00] <apw> thanks both
[13:00] <lifeless> fn-f11 for my dell laptop that is in front of me
[13:01] <apw> very odd isn't it, having no label on the keyboard, and its not something you can play with once yo uneed it
[13:06] <apw> bugger, found it ... shame i chose 'b'
[13:07] <smb> lol, yeah s might be better :)
[13:34] <ncopa> could someone please help me find the build script source for linux-headers-*-generic package?
[13:34] <ncopa> want to look how they make that nice symvers, .config and symlinks to header dirs
[13:38] <rtg> ncopa: debian/rules.d/2-binary-arch.mk in the kernel git repo
[13:48] <ncopa> thanks
[16:14] <nixternal> anyone having issues with 2.6.30-10? black screen of death here...anything I can do to help triaging let me know..haven't found a bug yet concerning what I am seeing
[16:22] <amitk> nixternal: KMS enabled?
[16:23] <amitk> what graphics card, etc."
[16:23] <amitk> ?
[16:23] <nixternal> you are on the right track :)   intel
[16:23] <nixternal> and yes it is a kms problem
[16:23] <nixternal> I just did i915.modeline=0 and it works
[16:24] <rtg_> nixternal: KMS doesn't work with PAE
[16:25] <rtg_> (yet)
[16:25] <nixternal> gotcha
[16:25] <nixternal> hopefully that is planned
[16:25] <rtg_> its in 2.6.31
[16:26] <nixternal> groovy
[16:26] <nixternal> maybe a blog post should go out to prevent frustration from people who will be upgrading in karmic in the next day or so?
[16:27] <rtg_> nixternal:  upgrades should not encounter the issue, unless you're running -server with desktop installed.
[16:28] <nixternal> I am not running -server, it is -generic
[16:28] <amitk> curious
[16:28] <rtg_> nixternal: 2.6.30-10.11 ?
[16:28] <amitk> nixternal: cat /proc/version_signature
[16:29] <nixternal> 2.6.30-10.12
[16:30] <nixternal> Ubuntu 2.6.30-10.12-generic
[16:30] <amitk> nixternal: so PAE isn't enabled
[16:31] <rtg_> amitk: but KMS _is_ now enabled by default.
[16:31] <amitk> rtg_: true, but this particular case isn't because of a PAE/KMS conflict
[16:31] <amitk> nixternal: ubuntu-bug xorg
[16:31] <rtg_> nixternal: I wonder if your Xorg package is not up to date?
[16:32] <nixternal> very well could be
[16:32] <rtg_> nixternal: they have to be in sync
[16:34] <nixternal> xorg is 7.4~5ubuntu21 from the beginning of June
[16:35] <nixternal> this issue happened right before it came time to enter my 3rd encryption password
[16:35] <nixternal> after entering the 2nd password, the screen went black
[16:35] <Unggnu> hi all
[16:36] <Unggnu> Is there a reason why the sound driver power management is enabled per default in Karmic?
[16:36] <amitk> nixternal: you are running karmic kernel and xorg on jaunty?
[16:36] <nixternal> no, this is all karmic
[16:36] <amitk> Unggnu: to save power? :)
[16:36] <Unggnu> If you use headphones you really getting deaf through the clicking noise when it is enabled again
[16:37] <amitk> nixternal: please upgrade your entire system and if it still persists, file a bug using 'ubuntu-bug xorg'
[16:37] <Unggnu> Please don't do this automatically.
[16:37] <amitk> Unggnu: please file a bug to help us fix it.
[16:38] <Unggnu> ok
[16:39] <amitk> Unggnu: you can disable it in your /etc/modprobe.d options
[16:39] <Unggnu> I have disabled it through proc
[16:39] <Unggnu> or sys
[16:41] <amitk> Unggnu: You can also disable it /etc/modprobe.d/alsa-base.conf (line saying options snd-hda-intel power_save=10)
[16:41] <nixternal> amitk: I did a dist-upgrade already, got everything that is available right now
[16:41] <Unggnu> ok
[16:41] <nixternal> I will yell at Bryce and see what he is up to
[16:41] <amitk> hehe... ok
[16:45] <amitk> bjf_afk: having trouble compiling your kernel...
[16:47] <Unggnu> amitk: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391182
[16:47] <ubot3> Malone bug 391182 in linux "Please disable Kernel sound power saving per default [Karmic]" [Undecided,New] 
[16:48] <amitk> Unggnu: do you use a laptop?
[16:48] <Unggnu> Sure
[16:48] <nixternal> hahaha, amitk and rtg_: I didn't get the new initramfs-tools
[16:48] <Unggnu> I have also tested it in the past but disabled it because of this clicking
[16:49] <amitk> Unggnu: if so, the power savings can be quite substantial. In some cases almost 30-40mins of extra battery life.
[16:49] <nixternal> I just updated and got them and everything is working, though usplash is really small :)
[16:49] <Unggnu> amitk: Because of the sound card?
[16:49] <amitk> Unggnu: yes, the amplifiers, codec, etc.
[16:49] <Unggnu> amitk: My system uses not much power but the only important parts are cpu und display.
[16:50] <Unggnu> which really have an measurable impact if I remember correctly
[16:50] <Unggnu> and wlan of course
[16:50] <nixternal> I spoke to soon, at least I can hit all 3 encryption passwords now, but x is still dead
[16:50] <Unggnu> amitk: You can test it with powertop I guess
[16:51] <amitk> Unggnu: true. But try running your battery flat with and without the sound power savings.
[16:51] <Unggnu> I give it a shot :)
[16:52] <amitk> Unggnu: please post the battery life numbers to the bug, to allow us to judge how much the impact is
[16:57] <Unggnu> amitk: Anyway my ears would be more important for me than 1 W but I am testing :)
[17:00] <Unggnu> 7.6 W with sound power saving
[17:03] <Unggnu> amitk: 7.6W with sound power saving and ~8 W without but the higher cpu usage might be also a reason
[17:04] <Unggnu> or 7.9W something around
[17:04] <amitk> cool
[17:04] <Unggnu> Everyone who needs this little difference can enabled it on his own. A gui entry would be the best of course :)
[17:05] <amitk> Unggnu: I'll leave it to dtchen to decide that. But in general if we can simply blacklist the ones that don't work that would be nice.
[17:06] <bjf> amitk, I'm trying to clear up the last of the config differences between Jaunty and Karmic w.r.t. imx51
[17:06] <Unggnu> They work but there is  a reaction coupling if it gets enabled again which is very loud with head phones
[17:06] <bjf> amitk, I have not tried building for a bit, not surprised there are problems right now
[17:09] <amitk> bjf: ack
[17:10] <amitk> bjf: what I meant was it doesn't even start building. Asks me to run 'make mrproper'. Need to figure out what got hosed.
[17:11] <bjf> amitk, have not had that problem... however
[17:11] <bjf> amitk, I wonder if this is part of the config changes that were recently implemented
[17:12] <rtg_> amitk: isn't that 'cause you have cruft in your build root ?
[17:12] <bjf> amitk, in my working tree git says that I have made changes to other arch / flavour config files (I have not commited them)
[17:12] <amitk> rtg_: right. And I hard reset my tree. But no go
[17:13] <nixternal> amitk and rtg_: if I set 'nomodeset' by editing grub on bootup, everything works fine...fyi
[17:14] <rtg_> nixternal: I thought you said all worked fine after updating initramfs-tools?
[17:14] <nixternal> it started to work fine, but died when firing up X
[17:14] <nixternal> KDM
[17:27] <amitk> bjf: could you try 'debian/rules binary-generic' on your tree
[17:27] <bjf> amitk, i am having the same problem
[17:28] <jaro> Hi there. Is there any suitable channel to ask questions related to quite old (2.4) kernel? I'm fighting with waitpid() not working correctly in a multithreaded process
[17:28] <jaro> and would like to find out if there is any known solution for this
[17:28] <bjf> amitk, the way I got pat it is I did 'debian/rules editconfigs' and just answered 'yes' when exiting to saving the config
[17:28] <amitk> jaro: google would be your friend for such an old kernel
[17:29] <bjf> amitk, I could build after that
[17:29] <bjf> amitk, should I run updateconfigs?
[17:29] <jaro> amitk: i did use it and found out one discussion thread that proposes that there is no way how to fix it
[17:29] <bjf> just did that, let me commit those configs
[17:29] <jaro> amitk: I'd like to make sure that it is that way
[17:30] <bjf> amitk, ^^
[17:31] <amitk> bjf: yes, running updateconfigs is a good idea
[17:31] <bjf> amitk, ok, updates pushed
[17:31] <amitk> jaro: no one here will be able to help with a 2.4 kernel
[17:32] <bjf> amitk, wasn't expecting imx51 changes to ripple into the other config files
[17:33] <amitk> bjf: it should only touch the common arch files and common ubuntu files if it find the same options set in other arches
[17:34] <jaro> amitk: ok I thought so :-/
[17:36] <rtg_> amitk: 'missing' is also a matcvh
[17:36] <amitk> rtg_: aah, right. With apw's new patches
[17:37] <apw> whats up?
[17:37] <apw> bjf yeah if you make changes to any arch config it could trigger changes in other arch common files
[17:38] <apw> if they now collapse to the same value or the inverse
[17:39] <apw> bjf if you are worried about what its doing shove the diff into a pastebin and i can see if i think its mental
[17:39] <bjf> apw, no worries, just unexpected
[17:39] <rtg_> apw: it shouldn't make changes in other arch common configs. armel should only affect config.common.ubuntu, right?
[17:40] <apw> rtg_, no it can affect other commons, if it stops something being common to all arches
[17:41] <apw> or if something becomes common to other arches
[17:41] <apw> like turning on staging or something
[17:41] <apw> then they will drop from the commons and move up to the ubuntu, or visa versa
[17:41] <apw> all depends on the actual value
[17:41] <rtg_> apw: ah, right. I was thinking more about missing features.
[17:43] <apw> yeah its likely something more generci he has changed, rather than something imx specific, which yes should just gently slide up to ubuntu level without affecting the other arches.  if its not then its bust
[17:48] <bjf> apw, rtg_, I've emailed you both the patch just so you can see what changed
[17:49] <rtg_> bjf: I was just looking at the commit in your git repo
[17:50] <bjf> rtg_, you could do that also :-)
[17:52] <rtg_> apw: its interesting what happened to some of the configs. for example, CONFIG_CHARGER_PCF50633 was removed from config.common.ubuntu and was added to the various x86 configs. If it was missing in armel, why didn't it stay in the common config?
[17:53]  * apw waits for the email ... grrr
[17:54] <apw> it should have stayed ... which kernel is he based on?
[17:54] <apw> bjf, whats your current baseline?
[17:54] <apw> sha1 is fine
[17:55] <bjf> apw, it's off of karmic but probably a week old
[17:55] <apw> ok then you have amitk's changes and not mine so the effect will be different
[17:56] <apw> you may have trouble if you are not at the tip
[17:56] <apw> as the config split has changed
[17:56] <bjf> apw, so I'll need to rebase at some point and the another "updateconfigs"?
[17:56] <rtg_> bjf: ah, you definitely need a rebase.
[17:57] <apw> hopefully you have nice clean mods and only one updateconfigs in thee
[17:57] <apw> there
[17:57] <rtg_> yeah, drop the updateconfigs commit
[17:57] <bjf> rtg_, right
[17:57] <rtg_> before rebasing. 'rebase -i' is your friend
[17:57] <apw> if you find the rebase is a nightmare for the configs we may be able to do something clever using the generated configs
[17:58] <apw> as the configs are in the standard format in the middle of a split and we can compare those with some little mods
[18:01] <dupondje> the new kernel in Karmic is broken (2.6.30-10) ?
 dupondje: intel graphics and no /etc/X11/xorg.conf file by any chance? :D
[18:07] <dupondje> nvidia
[18:07] <dupondje> and a xorg.conf :p
[18:08] <Sarvatt> sorry, real common problem in the past hour :D whats wrong? no problems with it here
[18:09] <dupondje> well after grub2 loads
[18:09] <dupondje> it starts the kernel, and then I only get a "_" :p
[18:09] <dupondje> a blinking underscore :p
[18:11] <dupondje> brb, going to eat now :)
[18:15] <Sarvatt> i'm seeing the short flood of sleep: invalid number '0.1' on boot too
[18:16] <Sarvatt> oops wrong channel
[18:51] <bullgard4> I would like to make a proposal to improve the apport program somewhat. Where to dircet such a proposal?
[18:51] <bullgard4> s/dircet/direct/
[18:52] <amitk> bullgard4: get hold of pitti on #ubuntu-devel
[18:52] <amitk> bullgard4: I suspect you will be asked to create a blueprint on launchpad
[18:53] <bullgard4> amitk: I am not afraid of creating such a blueprint. --  Thank you.
[18:54] <amitk> bullgard4: i didn't mean to imply you were afraid, just that I am not completely sure. pitti is the person to talk to.
[18:54] <amitk> :)
[18:55] <bullgard4> amitk: I understood it just like this at the outset.  --  No worries.
[19:25] <dupondje> guys, initramfs-tools is broken
[19:30] <dupondje> nobody awake here ?
[19:38] <dupondje> cjwatson:  ?
[19:42] <dupondje> need him badly
[19:51] <MellowDude> hi i got a question about kernels 
[19:52] <dupondje> shoot
[19:53] <MellowDude> i have a amd Athlon 64  cpu and i have ubuntu 32 bit os installed i was wondering what Kernel should i use the k7 or the k7-smp
[19:53] <ubot3> MellowDude: Error: Could not parse XML returned by Ubuntu: not well-formed (invalid token): line 378, column 84
[19:53] <dupondje> lol :)
[20:35] <maco> pdflush is going bonkers on my cpu. i hear that when this happens on ext4 it means "brace yourself for data loss" ...that true?
[21:39] <dtchen> maco: no.
[22:11] <freinhard> hi!
[22:12] <dtchen> freinhard: your best bet is to file a bug and e-mail the list
[22:13] <freinhard> dtchen: hey, didn't say anything concerning that yet ;)
[22:14] <freinhard> bug 384268, if desirable, i can take some time and do a debdiff
[22:14] <ubot3> Malone bug 384268 in linux-firmware "Firmware update for p54 and kernel >= 2.6.28 suggested" [Undecided,New] https://launchpad.net/bugs/384268
[22:15] <Nafallo> oh hai! I think KMS got the resolution for my eeepc wrong. I guess the kernel is to blame more than X? :-)
[22:16] <dtchen> freinhard: debdiff wouldn't be as helpful as a git changeset reference; see http://kernel.ubuntu.com/git?p=ubuntu/linux-firmware-karmic.git;a=summary and http://kernel.ubuntu.com/git?p=ubuntu/linux-firmware-jaunty.git;a=summary
[22:58] <freinhard> dtchen: any suggestion where i should host the repo so you can pull from?