[07:41] <bullgard4> I found PM1a_STS and PM1b_STS in the ACPI 3.0b Spec but not in Ubuntu kernel 2.6.20-16generic. How does PM1a_STS map to Ubuntu?
[09:24] <mjg59> bullgard4: I don't understand the question
[09:36] <bullgard4> mjg59: In http://advogato.org/article/913.html you have written: ""The user presses the power button. The system switches on, jumps to the BIOS start address, does a certain amount of setup (programming the memory controller and so on) and then looks at the ACPI status register. This tells it that the machine was previously suspended to RAM." I asked: "Where can I find the ACPI status register in Ubuntu 7.04 using the 2.6.20-16gener
[09:37] <mjg59> bullgard4: Yes, and I don't understand the question
[09:37] <mjg59> The register is part of your hardware, not the software
[09:50] <bullgard4> ACPI 3.0b Specification gives an 'Intel Architecture SetSleepingState example' where it clears the wake status by aserting a bit in the PM1a_STS status register. Where is the equivalent code to be found in Ubuntu 7.04? 
[09:51] <bullgard4> asserting
[10:11] <mjg59> bullgard4: acpi_hw_clear_acpi_status
[01:01] <bullgard4> Thank you very much. I was able to find it in hwsleep.c, hwregs.c, achware.h and elsewhere.
[02:17] <zul> morning
[02:50] <rtg> amitk: " rtg: Why did you change the -xen config to use MSS stack instead of MMC stack - commit 99b3465fe77281eeb12073e362cb4c7fc332095a?" - blind ignorance. I was satisfying a missing config parameter, but didn't think it through.
[04:40] <iwj> Can I talk to someone about DKMS ?
[04:41] <kousotu> !ask
[04:41] <kousotu> of coursethe damn bot ain't here...
[04:41] <kousotu> iwj: just start your question, someone wil most likely answer you
[04:41] <iwj> I know what you mean but I really don't know anything about DKMS.  I need to know what the kernel guys think of it ...
[04:43] <iwj> In particular, apropos of bug 121676.
[04:45] <rtg> iwj: bug BenC. I'm sure he has some comments.
[04:48] <BenC> iwj: the kernel guys are pushing it :)
[04:48] <iwj> BenC: ^
[04:48] <iwj> Ah, hello.
[04:48] <BenC> iwj: we need it to help support third-party modules
[04:48] <BenC> from OEMs and such
[04:49] <zul> its still sitting the revu right now
[04:49] <iwj> So what's the state of this package ?  Is there a package ?
[04:49] <iwj> Ah.
[04:49] <BenC> it's in universe revu
[04:49] <zul> no one on the motu team has looked afaik i can take a look at it hopefully tonight
[04:50] <zul> or get someone to review it
[04:50] <BenC> yeah, we'd like it to be in universe for gutsy
[04:50] <kousotu> I'm glad the Ubuntu kernal is so forgiving lol
[04:50] <BenC> would be nice if debian would take it so we can just sync it
[04:50] <rtg> BenC: actually we'd like it to be in main for Gutsy (if that is possible)
[04:51] <BenC> rtg: at the very least in universe, so it's installable
[04:51] <BenC> since it wont be in by default, there's not much point in having it in main right now
[04:52] <zul> im getting someone the motu team to do a quick review and ill try to ram it in
[04:55] <kousotu> isthere any wat to have transparency autoset?
[04:55] <zul> iwj: its getting reviewed shortly
[04:56] <iwj> Excellent, thanks.
[04:58] <xhaker> BenC, next ATi driver with AIGLX support, did you know about it already?
[05:01] <rtg> zul: Whom specifically is reviewing the DKMS package? I want to keep track of this issue.
[05:02] <zul> rtg: bddebian
[05:02] <zul> rtg: comments will appear at http://revu.tauware.de/details.py?upid=189
[05:02] <rtg> zul: thanks.
[05:03] <zul> rtg: you can bug him if you want :)
[05:18] <zul> rtg: first review done http://revu.tauware.de/details.py?upid=189
[05:21] <rtg> zul: that was quick. Thanks for the heads up.
[05:22] <zul> no probs
[05:34] <eagles0513875> hey guys what do i have to do to get some wifi drivers added to gutsy
[05:34] <eagles0513875> http://bcm43xx.berlios.de/?go=devices that is the link right now it seems that there r only 2 supported broadcom cards but hopefully they will release more card support
[05:35] <zul> open a bug in launchpad
[05:36] <eagles0513875> ?
[05:36] <eagles0513875> u mean like a wish list kind of thing
[05:36] <zul> yes
[05:36] <eagles0513875> ok am doing it now
[05:38] <eagles0513875> zul: would u like me to link u to the bug then
[05:38] <zul> yes the url in the bug report would be nice
[05:40] <eagles0513875> https://bugs.launchpad.net/ubuntu/+bug/137549
[05:40] <zul> thanks
[05:42] <eagles0513875> no prob
[05:43] <eagles0513875> zul: if those drivers r included in gutsy this distro and pc linux os u will be the only 2 with out of box support
[05:44] <eagles0513875> j/w what is the programming language used by the kernel is it c++ or something else
[05:44] <mjg59> eagles0513875: Erm. We ship bcm43xx.
[05:44] <mjg59> We have done for two years
[05:44] <mjg59> We can't ship the firmware, so you won't get out of the box support
[05:45] <eagles0513875> what u mean
[05:46] <mjg59> I mean, the driver you're asking us to include has been in Ubuntu for two years
[05:47] <eagles0513875> really what repository
[05:47] <mjg59> It's part of our kernel image
[05:47] <eagles0513875> ok for some reason my doesnt work out of the box
[05:47] <eagles0513875> do i download the firmware thats in the repository
[05:48] <mjg59> We can't supply the firmware
[05:48] <eagles0513875> ok
[05:48] <eagles0513875> what do i have to do to get my wifi to work 
[05:49] <mjg59> Search for bcm43xx on the wiki
[05:49] <eagles0513875> ok
[05:49] <mjg59> There are instructions there
[05:49] <eagles0513875> ur kernel wiki or general kubuntu one
[05:49] <mjg59> General one
[05:50] <eagles0513875> ok
[05:54] <kousotu> um.. how many workspaces does gutsy-5 have default?
[05:54] <kousotu> and how might I go about changing them?
[05:54] <eagles0513875> u go into system settings not sure bout how many though
[05:55] <eagles0513875> then desktop
[05:55] <kousotu> there wsn't a manager on 4 or 5
[05:55] <kousotu> and for some reason I only have 1 now
[05:56] <kousotu> 2 would be good, 4 would be awesome
[05:56] <kousotu> lol
[05:57] <eagles0513875> lol
[05:58] <eagles0513875> r u on gnome or kubuntu
[05:58] <kousotu> gnome
[05:58] <eagles0513875> then i dont know lol
[05:58] <eagles0513875> im on kde
[05:58] <kousotu> damn..
[05:58] <kousotu> lol
[05:58] <eagles0513875> sry
[05:58] <kousotu> lol
[05:58] <kousotu> np
[05:58] <kousotu> it's a preference
[05:58] <eagles0513875> kousotu: try #ubuntu-kernel
[05:59] <kousotu> lol
[05:59] <eagles0513875> not that channel
[05:59] <eagles0513875> try #ubuntu+1
[05:59] <eagles0513875> that is the gutsy channel
[05:59] <kousotu> I'm in +1
[05:59] <kousotu> I'm also trying to instal beryl, but that isn't in gutsy :(
[05:59] <eagles0513875> lol still no answer in there
[06:00] <eagles0513875> i think its compiz or compizfusion not sure
[06:00] <kousotu> compiz-fusion
[06:00] <kousotu> but I don't want compiz, I want beryl
[06:00] <kousotu> lol
[06:00] <eagles0513875> !compiz-fusion
[06:00] <kousotu> it's installedlol
[06:01] <kousotu> but like I said, I want brryl and not compiz
[06:01] <kousotu> lol
[06:01] <eagles0513875> i think beryl was merged into compiz-fusion
[06:01] <zul> guys this is offtopic here 
[06:01] <eagles0513875> kousotu: bring the convo to +1
[07:38] <kousotu> ...
[07:38] <kousotu> brb
[07:38] <kousotu> oops...
[07:45] <zul> hah i dont think kvm-intel is meant to be able to suspend
[08:34] <bdmurray> zul: I ran across bug 135760 and was wondering what happens next with a bug like that
[08:35] <zul> which one is that?
[08:36] <bdmurray> one where you recommend that they boot with "pci=assign-busses" and it fixed their issue
[08:36] <zul> maybe there is a blacklist i have to check
[08:37] <zul> bdmurray: ask for the output of sudo dmidecode and we can black list it
[08:37] <bdmurray> zul: okay, how does that work?
[08:38] <zul> bdmurray: basically the kernel checks a table for a hardware vendor and takes approiate action
[08:39] <bdmurray> some kernel options can have negative side effects though like acpi=off - right?
[08:40] <zul> yep
[08:42] <zul> bdmurray: basically ask the output of dmidecode and I can get it blacklisted for him
[08:45] <bdmurray> zul: Right, I've asked
[08:45] <zul> great dont forget to assign the bug to me ;)
[08:54] <Kano> hi, did you notice that
[08:55] <Kano> rt2500usb            0x0003      0x148f   0x2573
[08:55] <Kano> rt73usb              0x0003      0x148f   0x2671
[08:55] <Kano> are both for the same usb id
[08:55] <Kano> rt73usb              0x0003      0x148f   0x2573 
[08:55] <Kano> i mean
[08:55] <Kano> that does not work
[08:56] <Kano> maybe disable it in rt2500usb
[09:11] <BenC> Kano: which one doesn't work?
[09:15] <Kano> well you can not use both the same time
[09:15] <Kano> my tester should come back soon
[09:19] <Kano> how about adding http://sourceforge.net/projects/et131x
[11:20] <Kano> it seems both drivers fail
[11:20] <Kano> only the original ralink rt73 works