[12:51] <gnomefreak> what is the package i can use to report kernel bugs? tried using ubuntu-bug linux and after i answer the questions i get a dialog saying its not a genuine ubuntu package
[12:52] <apw> gnomefreak, which kernel do you have installed
[12:52] <apw> as ubuntu-bug linux is the correct incantation
[12:53] <gnomefreak> i have problems with 2.6.32-14-generic #20 so im using -13
[12:54] <apw> what does dpkg -l | grep linux-image | grep -- -13 
[12:54] <apw> say
[12:54] <apw> sorry -14
[12:55] <apw> gnomefreak, ^^
[12:57] <gnomefreak> apw: ii  linux-image-2.6.31-14-generic 2.6.31-14.48 and ii  linux-image-2.6.32-14-generic 2.6.32-14.20
[12:57] <apw> hmm ... that seems completely sane
[12:58] <gnomefreak> apw: i get frequency out of range
[12:58] <gnomefreak> -13 works fine
[12:58] <apw> out of range on your monitor?
[12:59] <apw> what graphics h/w
[13:00] <gnomefreak> apw: yes and nvidia 
[13:00] <apw> probabally related to a switch to nouveau
[13:01] <apw> so yes we would want a bug ...
[13:01] <gnomefreak> apw: that makes sense
[13:01] <apw> you could try reporting the bug manually
[13:01] <apw> and apport-collect bug# against it
[13:02] <gnomefreak> apw: ok on nouveau or kernel
[13:03] <apw> kernel as its doing KMS
[13:03] <apw> you could try booting nomodeset and see how that looks
[13:04] <gnomefreak> not sure how to boot with nomodeset
[13:05] <apw> adding nomodeset in grub to the kernel command line
[13:06] <gnomefreak> ok ill try that after i report the bug 
[13:16] <gnomefreak> apport-collect is crashing after giving access so i will just try nomodeset for now. 
[13:22] <gnomefreak> apw: for some reason it happen just that time. it worked this time normally
[13:22] <apw> hrm
[13:23] <gnomefreak> i havent done updates yet 
[13:40] <tgardner> cnd, did you ever bottom out on the non-free firmware issues?
[13:51] <cnd> tgardner: what do you mean?
[13:51] <cnd> (I haven't read my inbox yet, if that's part of it)
[13:51] <tgardner> the prism54 BS
[13:52] <cnd> tgardner: it sounds like we just need to ship all the prism firmwares
[13:52] <cnd> I'll get that in my tree today for you to pull
[13:53] <tgardner> cnd, the non-free package isn't in git. just lemme know where you have it staged on zinc
[13:53] <cnd> yeah, forgot about that
[13:53] <cnd> I'll get it to you one way or another :)
[13:54] <cnd> tgardner: you didn't uploade the 1.6 version I posted right?
[13:54] <cnd> so I don't need to dch -i again?
[13:54] <tgardner> cnd, nope
[13:54] <cnd> k
[13:55] <tgardner> cnd, you can always tell the current version of a package by looking in Launchpad, e.g., http://launchpad.net/ubuntu/+source/linux
[13:55] <cnd> k
[14:01] <Laibsch> Hi
[14:02] <Laibsch> Would you guys please be so kind to cherry-pick wifi support for Asus netbooks as I wrote in bug 521967?
[14:02] <ubot3> Malone bug 521967 in linux "support for new atheros wifi chipset" [Unknown,Fix released] https://launchpad.net/bugs/521967
[14:03] <Laibsch> I guess it's quite important for lucid (and maybe even karmic, it's still two more months befor lucid is out), I tested it all the way back to .31 and it works fine
[14:05] <tgardner> Laibsch, is that set for the .34 merge window?
[14:05] <Laibsch> sorry, dunno
[14:05] <Laibsch> it's slowly making way to mainline
[14:05] <Laibsch> but I don't think it's already hit it
[14:06] <tgardner> Laibsch, it'll show up in compat-wireless-stable then.
[14:07] <Laibsch> OK
[14:07] <Laibsch> IOW, no need to specifically backport it, it will automatically be there before the final release is made?
[14:08] <tgardner> Laibsch, depends on when .34 closes, but yeah, its quite likely.
[14:08] <Laibsch> OK
[14:08] <Laibsch> good
[14:09] <Laibsch> the ticket is open and targeted, so in any case, it shouldn't be forgotten
[14:09] <Laibsch> would of course be nice to have it available in testing sooner rather than later ;-)
[14:11] <Laibsch> tgardner: what about karmic, will it automatically show up there as well ?
[14:13] <tgardner> Laibsch, that is less likely.
[14:16] <Laibsch> Those are very popular netbooks
[14:16] <Laibsch> I think it's quite important to have support for them in karmic
=== maco2_ is now known as maco2
=== gnomefreak76 is now known as gnomefreak
[15:27] <lool> smb: Heya; is there a karmic-proposed update planned for the LXC stuff?
[15:27] <lool> I think I saw the patch go through, and get an ack, but I didn't see the kernel in proposed
[15:28] <lool> perhaps you have set some specific upload dates for these?
[15:28] <smb> lool, Its only in the repo and I want to get the current proposed to updates and likely some other upload in between
[15:28] <smb> So I cannot give a hard date
[15:29] <smb> lool, You can get kernels from the kernel-ppa PPA if you want to test things
[15:30] <lool> smb: Ok; thanks
[18:27] <LuserN800> anyone know how to handle usb external harddrives that sometimes go into powersave mode? My debian does not like this and can't even remount it. I have to powercycle the disk. Any option I have to set?
[18:34] <johanbr> LuserN800, if you've already turned off power management with hdparm, it's probably the drive's firmware doing that on its own
[18:35] <johanbr> if so, any tool to change that would have to be vendor-specific
[18:35] <LuserN800> johanbr, no I haven't switched it off
[18:35] <LuserN800> in hdparm
[18:35] <johanbr> try doing that
[18:35] <johanbr> it may or may not work... power management on usb drives is a bit iffy
[18:36] <LuserN800> But.. does linux handle this for some drive (correct firmware, documented..). The best would be if I could keep it.
[18:36] <LuserN800> I will try right now hdparm. thanks a lot.
[18:39] <LuserN800> Well, I'll have to wait 6h or something to see if it works. now the disk just floods me with "device descriptor read/8, error -110"
[19:12] <AnAnt> Hello is linux kernel 2.6.32.9 packaged yet ?
=== nick_ is now known as Guest35451
[19:19] <apw> nope the repo is frozen for a-3
[19:34] <AnAnt> apw: not even the vanilla kernel ?
[19:35] <apw> its in the mainline archive
[19:35] <AnAnt> apw: URL please
[19:35] <apw> https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
[19:35] <AnAnt> thanks
[19:41] <apw> cking, what was that block tracer called?
[19:42] <cking> blktrace
[19:42] <cking> http://smackerelofopinion.blogspot.com/2009/10/block-io-layer-tracing-using-blktrace.html
[19:42] <apw> heh thanks
[19:44] <AnAnt> sl-modem kernel modules don't work correctly since kernel 2.6.31 (even against vanilla kernel)
[19:44] <AnAnt> can someone help with that ?
[19:49] <bjf> AnAnt, do you have a bug number?
[19:50] <Laibsch> bjf: https://bugs.launchpad.net/ubuntu/+source/sl-modem/+bug/375148
[19:50] <ubot3> Malone bug 375148 in sl-modem "no more /dev/ttySL0 device node" [High,Confirmed] 
[19:50] <Laibsch> ;)
[19:51] <Laibsch> bjf: skim through the many comments and fast-forward to comment 70
[19:51] <Laibsch> skim, not skip ;-)
[19:53] <AnAnt> Laibsch: this bug is not related
[19:54] <AnAnt> not related to >= 2.6.31 kernel issue
[19:54] <Laibsch> not? I thought this was the main problem we were talking about
[19:54] <Laibsch> but you're right
[19:54] <Laibsch> it occured before .31
[19:54] <Laibsch> so, you shouldn't say they don't work correctly since 2.6.31
[19:55] <AnAnt> LP #375148 is not related to kernel, it's related to udev
[19:57] <Laibsch> which is closely related and if you don't think that bug has anything to do with the kernel, then why are you asking me to try with today's mainline kernel to see if that problem is fixed?
[19:57] <Laibsch> you're comment is pretty scary
[19:58] <Laibsch> udev IS kernel
[19:58] <AnAnt> I didn't say that the request to test with today's mainline kernel has to do with #375148
[19:59] <AnAnt> ok, let me put it another way, 375148 is about sl-modem not supporting creating device nodes through udev, but rather static device nodes
[20:11] <Laibsch> AnAnt: "doesn't work correctly" is about the worst problem description you can give.  We've yet to hear anything else.
[20:36] <tgardner> apw, what would cause an drm:intelfb_panic ? (when modeset=1)
[20:47] <apw> tgardner, not sure i've seen any specific ones
[20:47] <apw> pastebin the panic stack perhasp?
[20:47] <tgardner> yeah, right (snort!)
[20:48] <tgardner> apw, I think it has to do with interrupts. not sure yet, but I have the HW
[20:48] <apw> is this with the franken-kenrnel?
[20:50] <tgardner> apw, no, chromeos right now
[20:50] <tgardner> which is essentially Karmic with diff config options
[20:51] <apw> there was some interrupt patches recenting in stable i think
[20:51] <tgardner> apw, I'm gonna try booting stock Lucid
[20:51] <apw> good test me thinks
[21:29] <manjo> anyone know the diff between broadcom-sta-source and bcmwl-kernel-source in lucid ? 
[21:29] <manjo> they both claim to be broadcom wireless souce 
[21:30] <manjo> jjohansen, ^^ ? 
[21:30] <jjohansen> manjo: nope?
[21:31] <manjo> apw, ? ^^
[21:31] <apw> nope
[21:31] <jjohansen> my wild guess would be a drivers for a different series of wireless
[21:32] <manjo> apt cache search broadcom list both... after I enabled multiverse & partners ... 
[21:35] <manjo> jjohansen, do you know if there is a gui to enable multiverse ? or vi /etc/apt/sources.list is the only way ? 
[21:35] <manjo> jjohansen, I think I found the ans
[21:36] <manjo> system->software sourecs
[21:36] <jjohansen> manjo: got into System>Adminstration>software sources
[21:36] <jjohansen> yep
[21:36] <manjo> yep... I should have looked closely before asking :)
[21:55] <cbmuser> hoi, 2.6.33 is out; anyone has installable debs already?
[23:04] <apw> cbmuser, the mainline builds system will spot it 'shortly' and make some
[23:37]  * jk- high-fives the mainline build system