=== KB1JWQ is now known as PFY === PFY is now known as KB1JWQ === kamalm is now known as kamalm-away [03:55] Keybuk: did you ever have a bug filed about your RS600 problem? [04:00] Sarvatt: RS600 ? [04:00] that sounds like a kind of bike [04:00] latitude XT? [04:01] oh, the Radeon thing? [04:01] yeah [04:01] no, I don't think I ever filed a bug [04:02] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/544590 [04:02] Malone bug 544590 in linux "[RS600] video freeze with KMS (X and plymouth) (upstream patches available)" [High,Triaged] [04:03] was that commit I linked in there the same one that they put together for ya to fix it? [04:03] drm/radeon/kms: initialize set_surface_reg reg for rs600 asic [04:03] not sure, the laptop and my notes are 5000 miles away [04:03] but it sounds familiar [04:03] I don't think I ever actually got around to testing it [04:03] ahh ok [04:04] got distracted by the nvidia which needed more active help from me [04:04] remind me when I'm not in SF [04:04] that GPU is like the rarest of the rare of ATI's, they pulled them from the market during the AMD/ATI merger [04:04] (and it's unusable with lucid without nomodeset at the moment) [04:05] it's ok, got 2 testers to build kernels for to be sure the fixes work :) [04:06] yeah, that's what I was told upstream [04:08] Sarvatt: That's the GPU with GTT issues where it'll eventually corrupt all your ram, isn't it? [04:08] yup [10:18] any chance to include new files into linux-firmware? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/560306 [10:18] Malone bug 560306 in linux "[lucid] ATI hd5xxx cards wrongly doing kms?" [Undecided,Confirmed] [13:53] artnay, whats the issue? [13:56] apw: there are several setups (seems like affected are only i5/i7 and 5xxx users) which don't even boot using live CD. https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/560306 has the details and links. [13:56] Malone bug 560306 in linux-firmware "[lucid] ATI hd5xxx cards wrongly doing kms?" [Undecided,Confirmed] [13:57] if you compare the output of "dpkg -L linux-firmware | grep radeon" and http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=radeon;h=3dc32482fcf179c43e2fcc0b30303f231774820a;hb=HEAD it seems that 5xxx series is missing firmware files (which probably would help with the boot issue) [13:58] I could be totally wrong but that's the only way I see it at the moment. [13:59] the bug was filed against linux but I moved it against linux-firmware (where it belongs AFAIK) [14:00] artnay, ta [14:02] apw, I synced with dwmw2/linux-firmware before I left. Seems that he's added a few new files. [14:03] apw, here it is: 'radeon: add evergreen family microcode.' [14:04] yeah looks like a rebase may be in order before release [14:04] _if_ we can confirm it doesn't change any files at least [14:04] otherwise selective picks at least [14:04] apw, I'm thinking I'll on;y add the evergreen stuff. there are lots of other changfes, but we should SRU them after the fact [14:05] fair enough === kamalm-away is now known as kamalm [18:38] Is Jerone around? [18:38] I've just sent a patch for the Lenovo USB resume problem [18:38] Thinko in the PCI resume code === yofel_ is now known as yofel [19:45] mjg59, to kernel-team@ ?? [19:45] or upstream, or :) [19:47] apw: Upstream [19:47] Should be on -acpi and -pci [19:47] cool ... thanks for the heads up [20:29] kamalm, your patch was miss categorised cause i missed removing the SRU: prefix [20:30] i'll fix that up and repush it [20:31] apw: thank you sir. I must admit that I was^Wam confused about which [TAGS] and TAGS: to add or not add, and what purpose they all serve [20:32] kamalm, yet another thing which is not well documented. we tried to clean up the templates, and they are a hell of a lot better but they are not right still [20:34] apw: well, we have in debian/commit-templates: sauce-patch and upstream-patch (but no just "patch" as the wiki claims). I think I added [Lucid] and SRU: manually, following examples I'd seen, but I felt like I was mostly just guessing (and hoped some kindly human would fix it before a script got its mitts on it). [20:35] putting things in [] are good as they get stripped automatically on applicaiton and [SRU Lucid] is probabally an appropriate prefix [20:35] but yes its all a bit broken and i've added it to our next sprint agenda for review [20:49] tgardner, do i remember correctly that you were looking at the radeon firmware issue? [20:51] apw, yep, I uploaded a PPA linux-firmware this morning for the Evergreen series and asked for test results. [20:51] bug 560306 [20:51] Malone bug 560306 in linux-firmware "[lucid] ATI hd5xxx cards wrongly doing kms?" [High,Confirmed] https://launchpad.net/bugs/560306 [20:52] excellent, then i can forget about it :) [21:50] cking: around? I still get no joy from the acpi_osi workaround for bug 539477 [21:50] Malone bug 539477 in gnome-settings-daemon "Video out hot key sends super + p + return on many upcoming Dell & HP systems" [Undecided,Confirmed] https://launchpad.net/bugs/539477 [22:01] kamalm, care to send me your DSDT again and I will see why it fails [22:02] cking: again? I never sent it to you before (but will be happy to do so) -- lets make sure I'm even using the workaround correctly. I've tried booting with acpi_osi="Windows 2006" and acpi_osi="!Windows 2009" but neither helps -- is that syntax proper (i.e. the quotes and the !) ? [22:05] kamalm, my fail, try this acpi_osi=\"!Windows 2009\" [22:06] kamalm, if that fails, send me your dmesg output [22:07] cking: okay, that *does* work (yay!) [22:08] cking: perhaps you would like to post a comment to the bug with this new and improved workaround? The last post on the matter suggest using "Windows 2006". [22:14] kamalm, well !Windows 2009 will work until a new version appears and the kernel picks it up, then it will fail again [22:18] cking: it'll do for now anyway -- I note that jerone's comment #20 in that bug recommends acpi_osi="Windows 2006" (with no backslashes) so it would not get processed correctly -- but I find that \"Windows 2006\" isn't helpful anyway. [22:27] kamalm, the Windows 2006 method may/may not work depending on the order and how the OSI probes are handled in ACPI. It's ugly and broken [22:27] I've update the bug [22:28] cking: thank you (for the update, and for the workaround!) [22:28] kamalm, thank ppetraki for this one [22:29] I like comment [22:29] oops, I like the penultimate comment on the bug report [22:29] thank you ppetraki :-) [22:31] cking: yup. I call first swing with the bat! [22:31] I'm scared of them getting back to me [22:31] ;-) [22:45] xrandr [22:45] oops [22:45] wrong kb