[09:18] <AnAnt> Hello, in alpha3 PC beep was working on my laptop, yet in alpha4 it doesn't, is this a kernel or pulseaudio issue ?
[11:00] <apw> cking, this bug seems to have come back with some comments:
[11:00] <apw> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/347623
[11:00] <ubot3> Malone bug 347623 in linux "Samsung q45 does not produce key-release events for Fn-Keys (patch included)" [Low,Fix committed] 
[11:01] <apw> smb, this was the pad thing: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/300143
[11:01] <ubot3> Malone bug 300143 in linux "tablet devices show up as non-functional joysticks" [Undecided,Fix committed] 
[11:01] <cking> apw, hrm.. ok, will pop it on my todo list
[11:02] <apw> cking, they verified it in -proposed and reported something odd like down works fine and up is odd or something (brightness)
[11:05] <cking> 80+ steps to dim the light is a little too much to ask I suppose.
[11:08] <laga> apw: did you see my message about the aufs config option? i'm afraid i killed my irssi session last night :)
[11:09] <apw> laga, best to repeat it now :)
[11:11] <laga> apw: mythbuntu needs CONFIG_AUFS_BR_RAMFS so its diskless clients can boot properly
[11:11]  * ogra wonders why 
[11:11] <ogra> ltsp works fine as is 
[11:12] <ogra> dont you base the mythbuntu diskless mode on ltsp anymore ? 
[11:12] <laga> ogra: the xino lookup table is placed in /tmp. and if there's no ramfs support, that won't work in initramfs
[11:12] <laga> ogra: i can only assume you're placing the xino elsewhere
[11:13] <laga> let me restate that
[11:13] <ogra> stgraber would know i think
[11:13] <laga> you use some kind of temporary in-memory file system which is not ramfs AFAIK. aufs can place the xino table there
[11:14] <laga> for mythbuntu-diskless, our COW branch is on NFS - and the xino table can't go there, so it falls back to /tmp, which is broken in karmic
[11:14] <ogra> oh, NFS
[11:14] <laga> due to that config option lacking
[11:14] <ogra> how evil :P
[11:14] <ogra> yeah, NFS and union mounts were never good friends, thats a good reason indeed
[11:14] <apw> laga, so this is an aufs2 only issue affecting only karmic?
[11:14] <laga> yes
[11:15] <apw> laga, is there a bug filed?
[11:15] <laga> apw: no. :)
[11:15] <laga> i guess i should do that then. :)
[11:15] <apw> can you get one filed for me, i'll go see why that option is off
[11:17] <apw> laga, have you tested that turning this thing on actually works for you?  if so can you record that in the bug
[11:17] <laga> apw: yes, it works for me
[11:19] <laga> apw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414738
[11:19] <ubot3> Malone bug 414738 in linux "Mythbuntu-diskless needs CONFIG_AUFS_BR_RAMFS" [Undecided,New] 
=== saispo_ is now known as saispo
=== bjf-afk is now known as bjf
[16:27] <smb> apw, May I kindly remind you of bug 406419. I believe you wanted to do a correct SRU mail for that. :)
[16:27] <ubot3> Malone bug 406419 in linux "Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly inserted USB device" [Medium,In progress] https://launchpad.net/bugs/406419
[16:27] <apw> *burp*
[16:32] <micahg> do you guys do support in here or should I send people to #ubuntu + 1?
[16:32] <micahg> *people :)
[16:35] <rtg> micahg, depends on what you mean by support. we're willing to discuss kernel bugs, etc.
[16:36] <micahg> rtg: I had a user tell me a broadcom chipset isn't supported, I found an open bug regarding it, I'm just wondering where to send him if he can't solve it
[16:38] <rtg> micahg, well, wl.ko (if thats the driver in question) is a binary blob driver, so there's not a lot we can do to fix Broadcom issues.
[16:38] <micahg> so if broadcom dropped support we're stuck
[16:40] <rtg> micahg, I think thats unlikely, but their support is typically directed towards monetized projects on specific platforms. they don't really seem to care otherwise.
[16:41] <micahg> but the new intel drivers require the karmic kernel, right?
[16:43] <rtg> micahg, the Intel drivers _are_ part of the kernel. I assume you're talking about the Xorg drivers? If so, then yes - you'll need them in order to use the KMS enabled kernel drivers.
[16:44] <micahg> right, so someone trying to use an intrepid kernel with karmic will break stuff?
[16:45] <rtg> micahg, yep - won't work too well with the desktop.
[16:47] <ukev> hi, I've a curios problem with the usb stick subsystem of the kernel with usb pens(?) >= 8GB. Reading works fine but writing crashs after ~100-200MB with IO Error. USB drives (harddisk) works fine and the two usb sticks (8 GB and 16 GB) are working fine with other computers (osx), where can I look to locate the problem?
[16:58] <micahg> ok thanks rtg
[18:00] <ogasawara_> smb: re the ext4 patches, did you happen to save your patched kernels you built somewhere that I might quickly be able to point testers too?
=== ogasawara_ is now known as ogasawara
[18:00] <apw> rtg ok ... i've reconstructed your abstracted debian form against head.  i've scripted the initial split so it can be applied again to any other repo we need.  just test building it now, and then will push it for review
[18:01] <ogasawara> smb: no worries if not, I can rebuild
[18:01] <smb> ogasawara, Let me check. I am not sure... Brain image not complete yet. :)
[18:01] <ogasawara> heh
[18:02] <rtg> apw, cool
[18:03] <apw> i shoved a couple of tweaks on the top the first lets you use all the targets in debian.master/rules
[18:03] <apw> the second fixes the insertchanges target
[18:04] <smb> ogasawara, Hm, no, it seems I got the packages removed. Sorry
[18:04] <ogasawara> smb: no problem, I was just being lazy :)
[18:05] <smb> ogasawara, Understandably, for the amount of time a build takes. :)
[18:16] <ukev> hi, I've got a curios problem with the usb disk subsystem of the kernel with usb pen drives >= 8GB. Reading works fine but writing crashs after ~100-200MB with IO Error. USB drives (harddisk) works fine and the two pen drives (8 GB and 16 GB) are working fine with other computers (osx), where can I look to locate the issue?
[18:41] <apw> rtg ok seems to build ok ... the proposed stack is here: git://kernel.ubuntu.com/apw/ubuntu-karmic.git abstracted-debian
[18:41] <rtg> apw, cool. I'll have a look as soon as I get mvl-dove sorted
[18:41] <apw> good luck with _that_
[18:42] <rtg> apw, oh, its close. there is some mind numbing udeb crap to deal with, but everything else is working.
[18:42] <apw> yay udebs ...
[18:53] <bjf> rtg, sorry, should have asked my question here ...
[18:53] <bjf> rtg, I just updated my karmic tree and the mvl-dove branch doesn't build, is that expected?
[18:57] <rtg> bjf, ok, try the mvl-dove branch again
[19:00] <apw> rtg heard any issues recently (-5/-6) with rfkill after resume?  needing an rfkill unblock
[19:00] <rtg> apw, nope, but its likely wifi driver dependent (unless its the laptop driver)
[19:16] <bjf> rtg, still not building, however this looks different: dpkg-architecture: warning: Specified GNU system type arm-linux-gnueabi does not match gcc system type x86_64-linux-gnu.
[19:18] <rtg> bjf, how are you building?
[19:19] <bjf> rtg, not with debuilld, am reading up on that now
[19:19] <bjf> rtg, export $(dpkg-architecture -aarmel)
[19:19] <rtg> bjf, here is the rune: debuild -eCROSS_COMPILE=arm-none-linux-gnueabi- --prepend-path=$(HOME)/proj/arm-tools/arm-2008q3/bin -b -aarmel -us -uc
[19:19] <bjf> rtg, CROSS_COMPILE=arm-none-linux-gnueabi- fakeroot debian/rules binary-$1
[19:20] <rtg> bjf, the key environment setting is '-aarmel'
[19:21] <bjf> rtg, that is set by: export $(dpkg-architecture -aarmel) right?
[19:22] <rtg> bjf, uh, dunno. 
[19:22] <bjf> rtg, just ignore me
[19:22] <bjf> rtg, operator error
[19:22] <rtg> bjf, thats easy enough :)
[19:55] <bjf> rtg, dove should be producing a uImage but seems to be producing a zImage
[19:55] <rtg> bjf, hmm, you're right.
[19:56] <bjf> rtg, also, I'm getting a bunch of errors/warnings after "Now running lintian..."
[19:56] <rtg> bjf, they're OK, just noise 'cause I'm too lazy right now.
[19:56] <bjf> rtg, np
[19:58] <rtg> ogra, uploading dove right now, but it still produces a zImage.
[20:04] <Nafallo> something in 2.6.31-6-generic turns my eeepc into flickerville. I would assume that has been reported already?
[20:05] <rtg> Nafallo, flickerville is such a technical term :) I assume you refer to your display?
[20:06] <Nafallo> hehe. yeah :-). or graphics rather.
[20:06] <Nafallo> whenever something moves on the screen, the whole UNR desktop flickers
[20:07] <Nafallo> I booted into ABI 5 for now :-P
[20:07] <rtg> Nafallo, Is that intel graphics?
[20:07] <Nafallo> yeah. let's see if I can see what lshw -C VGA says.
[20:08] <Nafallo> nothing. maybe it's graphics :-)
[20:08] <rtg> Nafallo, lspci ?
[20:09] <Nafallo> product: Mobile 915GM/GMS/910GML Express Graphics Controller
[20:09] <Nafallo> lshw -C display
[20:09] <Nafallo> 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
[20:10] <rtg> Nafallo, as I suspected. Please start an LP bug, make sure ogasawara knows that it is a regression.
[20:10] <Nafallo> oki
[20:18] <Nafallo> woha! I found the report bug link for the right package!
[20:18] <Nafallo> woha! I found the report bug link for the right package!
[20:18] <Nafallo> took a bit :-P
=== bjf is now known as bjf-afk
[20:35] <Nafallo> ubuntu-bug -p linux managed to cause OOM conditions.
[20:35] <Nafallo> had to reboot.
[20:35] <Nafallo> so much for following instructions ;-)
[22:14] <lesshaste> hi
=== bjf-afk is now known as bjf