Oh vgaswitcharoo is how I tried doing the GPU switch and check the current setting (on/off) of each GPU.
On Thu, Mar 12, 2015 at 12:47 AM, Evan Foss <evanf...@gmail.com> wrote: > Hi Pierre, > > No worries about the response time. I remember when the features > matrix was mostly todo's. Clearly you folks have put in a ton of work. > I would feel bad about trying to shove a developer into my problem and > I do not have the time right now to join the development team. Besides > my day job I am currently writing a library to interpret BSDL files > (JTAG). > > I am having a bit of trouble with acpidump which is telling me there > is no -n option. The acpidump I am running is from a package called > pmtools. Is that the correct thing? I am in gentoo and used the > following ebuild to do the install. > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-power/pmtools/pmtools-20110323-r1.ebuild?view=markup > which pulls this source > https://github.com/anyc/pmtools/ > > I see your point about using the intel instead of the nVidia GPU. > > Many thanks for your help, > -Evan > > On Wed, Mar 11, 2015 at 3:52 PM, Pierre Moreau <pierre.mor...@free.fr> wrote: >> Hi Evan! >> >> Sorry for taking so long before answering... >> Thanks for the greps! It appears you have a newer version of apple_gmux than >> I have, so let's see if something also changed in the _DSM method. Could you >> please run - as root - `acpidump -b -n DSDT` which will create a file named >> dsdt.dat containing the DSDT table, and then run `iasl -d dsdt.dat` and send >> me the resulting dsdt.dsl file? >> That way I will have the uuid, the available functions and their version for >> your _DSM method. >> >> Regarding bringing the clocks down, you could add a fake performance level >> in the vbios but I'm not sure if it would be a good move. You should rather >> power off the NVidia card and only use the Intel one - using vgaswitcheroo, >> see [1]; once I have that dsdt.dsl file, I should be able to add support for >> auto-powering down the NVidia card. Or you could try to motivate some >> developers - or if you want to give it a try - to investigate / add support >> for power and/or clock gating. >> >> Regards, >> >> Pierre >> >> [1]: >> http://nouveau.freedesktop.org/wiki/Optimus/#checkingthecurrentpowerstate >> >> >> ----- Mail original ----- >>> The first grep of dmesg is for the apple info so you know exactly >>> what >>> box I have. The second is to show that I am booting in EFI mode and >>> not some bogus bios compatibility thing. The third is to show the >>> gmux >>> version. The fourth is to answer the question you actually asked. >>> >>> $ cat /proc/version >>> Linux version 3.19.0 (root@turingatlarge) (gcc version 4.7.3 (Gentoo >>> 4.7.3-r1 p1.4, pie-0.5.5) ) #3 SMP Sun Feb 15 01:09:59 EST 2015 >>> >>> ------ $ dmesg|grep Apple >>> [ 0.000000] efi: EFI v1.10 by Apple >>> [ 0.000000] DMI: Apple Inc. MacBookPro9,1/Mac-4B7AC7E43945597E, >>> BIOS MBP91.88Z.00D3.B08.1208081132 08/08/2012 >>> [ 0.000000] ACPI: XSDT 0x000000008CD8E1C0 0000B4 (v01 APPLE >>> Apple00 00000000 01000013) >>> [ 0.000000] ACPI: FACP 0x000000008CD8C000 0000F4 (v04 APPLE >>> Apple00 00000000 Loki 0000005F) >>> [ 0.000000] ACPI: HPET 0x000000008CD8B000 000038 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: APIC 0x000000008CD8A000 0000BC (v02 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: SBST 0x000000008CD88000 000030 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: ECDT 0x000000008CD87000 000053 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: MCFG 0x000000008CD89000 00003C (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 3.091740] usb 3-1.1: Manufacturer: Apple Inc. >>> [ 3.410516] usb 4-1.8.1: Manufacturer: Apple Inc. >>> [ 3.581141] usb 4-1.8.2: Manufacturer: Apple Computer, Inc. >>> [ 3.777265] usb 4-1.8.3: Product: Apple Internal Keyboard / >>> Trackpad >>> [ 3.777267] usb 4-1.8.3: Manufacturer: Apple Inc. >>> [ 3.782615] input: Apple Inc. Apple Internal Keyboard / Trackpad >>> as >>> /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8.3/4-1.8.3:1.0/0003:05AC:0252.0002/input/input13 >>> [ 3.833440] apple 0003:05AC:0252.0002: input,hidraw0: USB HID >>> v1.11 >>> Keyboard [Apple Inc. Apple Internal Keyboard / Trackpad] on >>> usb-0000:00:1d.0-1.8.3/input0 >>> [ 4.091248] apple 0003:05AC:0252.0003: hidraw2: USB HID v1.11 >>> Device [Apple Inc. Apple Internal Keyboard / Trackpad] on >>> usb-0000:00:1d.0-1.8.3/input1 >>> [ 4.319509] usb 4-1.8.1.3: Manufacturer: Apple Inc. >>> [ 4.457798] input: Apple Computer, Inc. IR Receiver as >>> /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8.2/4-1.8.2:1.0/0003:05AC:8242.0001/input/input18 >>> [ 4.509982] appleir 0003:05AC:8242.0001: input,hiddev0,hidraw4: >>> USB >>> HID v1.11 Device [Apple Computer, Inc. IR Receiver] on >>> usb-0000:00:1d.0-1.8.2/input0 >>> >>> ------ $ dmesg|grep EFI >>> [ 0.000000] efi: EFI v1.10 by Apple >>> [ 1.220269] fb0: EFI VGA frame buffer device >>> [ 2.619144] EFI Variables Facility v0.08 2004-May-17 >>> [ 4.205767] fb: switching to nouveaufb from EFI VGA >>> >>> ------ $ dmesg|grep gmux >>> [ 2.739845] apple_gmux: Found gmux version 1.9.35 [classic] >>> [ 4299.386843] apple-gmux 00:03: System wakeup disabled by ACPI >>> >>> ------ ~/Documents $ dmesg|grep DSM >>> [ 4.205710] ACPI Warning: \_SB_.PCI0.IGPU._DSM: Argument #4 type >>> mismatch - Found [Buffer], ACPI requires [Package] >>> (20141107/nsarguments-95) >>> [ 4.205724] ACPI: \_SB_.PCI0.IGPU: failed to evaluate _DSM >>> [ 4.205739] ACPI Warning: \_SB_.PCI0.P0P2.GFX0._DSM: Argument #4 >>> type mismatch - Found [Buffer], ACPI requires [Package] >>> (20141107/nsarguments-95) >>> [ 4.205749] ACPI: \_SB_.PCI0.P0P2.GFX0: failed to evaluate _DSM >>> >>> On Sun, Feb 15, 2015 at 5:13 AM, Pierre Moreau >>> <pierre.mor...@free.fr> wrote: >>> > Does the Nvidia card auto-suspends or do you have to force it? If >>> > not, does >>> > it report some “failed to parse _DSM” message? >>> > I have a mid 2009 MBP who uses a different _DSM handles than the >>> > ones >>> > Nouveau currently supports, and I wondered if they were related to >>> > the Apple >>> > Gmux or not. So, as you have a different model with a different >>> > Nvidia card >>> > but still with an Apple Gmux, I’d be interested to know if you have >>> > the same >>> > _DSM handles as I have. >>> > >>> > Pierre >>> > >>> > On 15 Feb 2015, at 06:44, Evan Foss <evanf...@gmail.com> wrote: >>> > >>> > Thanks again. >>> > >>> > This works and the heat has dropped substantially. It is still not >>> > as >>> > cool as I would like but this will do for now. I still need to file >>> > a >>> > bug report with the intel / apple gmux people. >>> > >>> > -Evan >>> > >>> > On Sat, Feb 14, 2015 at 10:42 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > On the older kernel >>> > >>> > [ 6.494956] nouveau [ CLK][0000:01:00.0] 07: core 270-405 >>> > MHz >>> > memory 838 MHz >>> > [ 6.494989] nouveau [ CLK][0000:01:00.0] 0a: core 270-774 >>> > MHz >>> > memory 1560 MHz >>> > [ 6.495015] nouveau [ CLK][0000:01:00.0] 0e: core 270-774 >>> > MHz >>> > memory 4000 MHz >>> > [ 6.495182] nouveau [ CLK][0000:01:00.0] --: core 405 MHz >>> > memory 680 >>> > MHz >>> > >>> > On Sat, Feb 14, 2015 at 10:35 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > Because I am on a macbook the VBIOS might be wonky. >>> > >>> > I tried turning off nVidia and using intel. The result was a blank >>> > screen. I know other people had the same bug which was something to >>> > do >>> > with reprobing lvds?! I saw patches go by and every time I tried >>> > one >>> > the results were the same. fail. I was actually about to post a bug >>> > report to the intel (i915) people about it. >>> > >>> > I tried to work out how to get optimus to work. After trying >>> > several >>> > different sets of instructions I never found a working >>> > configuration >>> > and put it aside. I never used to use opengl but lately my pcb >>> > software has adopted it so my needs changed. >>> > >>> > I will get back to you with more results on this matter after I get >>> > the newer kernel up. >>> > >>> > >>> > On Sat, Feb 14, 2015 at 10:09 PM, Ilia Mirkin >>> > <imir...@alum.mit.edu> wrote: >>> > >>> > On Sat, Feb 14, 2015 at 9:56 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > I have a side question which may be the subject of a future second >>> > bug >>> > report. I have been lurking on the nouveau mailing list for some >>> > time. >>> > I understand from various posts that the nvidia gpu clock speed >>> > right >>> > now is set to the lowest possible setting. Why does my machine run >>> > so >>> > >>> > >>> > Often but not always the case -- the clock speed is whatever the >>> > VBIOS >>> > leaves it in. For kepler, that is usually the lowest setting. >>> > >>> > much hotter in linux than macos? I turned off the intel graphics >>> > and >>> > the cpu clock is set to the lowest available speed. >>> > >>> > >>> > You should instead turn off the nvidia graphics and run off intel >>> > -- >>> > intel is much less power-hungry than nvidia, even at the lowest >>> > clocks. If it's an optimus setup, the nvidia gpu should >>> > automatically >>> > power off until needed (either because some display is connected to >>> > it, or for offloading). >>> > >>> > >>> > How do I get a display of the GPU clocking speeds? >>> > >>> > >>> > You should see it in dmesg... look for CLK lines. The ones with -- >>> > (or >>> > AC/DC) will show the current setting. Or boot with nouveau.pstate=1 >>> > and you should have a /sys/class/drm/card*/device/pstate file. >>> > >>> > -ilia >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > _______________________________________________ >>> > Nouveau mailing list >>> > Nouveau@lists.freedesktop.org >>> > http://lists.freedesktop.org/mailman/listinfo/nouveau >>> > >>> > >>> >>> >>> >>> -- >>> Home >>> http://evanfoss.googlepages.com/ >>> Work >>> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > > > > -- > Home > http://evanfoss.googlepages.com/ > Work > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ > > On Wed, Mar 11, 2015 at 2:52 PM, Pierre Moreau <pierre.mor...@free.fr> wrote: >> Hi Evan! >> >> Sorry for taking so long before answering... >> Thanks for the greps! It appears you have a newer version of apple_gmux than >> I have, so let's see if something also changed in the _DSM method. Could you >> please run - as root - `acpidump -b -n DSDT` which will create a file named >> dsdt.dat containing the DSDT table, and then run `iasl -d dsdt.dat` and send >> me the resulting dsdt.dsl file? >> That way I will have the uuid, the available functions and their version for >> your _DSM method. >> >> Regarding bringing the clocks down, you could add a fake performance level >> in the vbios but I'm not sure if it would be a good move. You should rather >> power off the NVidia card and only use the Intel one - using vgaswitcheroo, >> see [1]; once I have that dsdt.dsl file, I should be able to add support for >> auto-powering down the NVidia card. Or you could try to motivate some >> developers - or if you want to give it a try - to investigate / add support >> for power and/or clock gating. >> >> Regards, >> >> Pierre >> >> [1]: >> http://nouveau.freedesktop.org/wiki/Optimus/#checkingthecurrentpowerstate >> >> >> ----- Mail original ----- >>> The first grep of dmesg is for the apple info so you know exactly >>> what >>> box I have. The second is to show that I am booting in EFI mode and >>> not some bogus bios compatibility thing. The third is to show the >>> gmux >>> version. The fourth is to answer the question you actually asked. >>> >>> $ cat /proc/version >>> Linux version 3.19.0 (root@turingatlarge) (gcc version 4.7.3 (Gentoo >>> 4.7.3-r1 p1.4, pie-0.5.5) ) #3 SMP Sun Feb 15 01:09:59 EST 2015 >>> >>> ------ $ dmesg|grep Apple >>> [ 0.000000] efi: EFI v1.10 by Apple >>> [ 0.000000] DMI: Apple Inc. MacBookPro9,1/Mac-4B7AC7E43945597E, >>> BIOS MBP91.88Z.00D3.B08.1208081132 08/08/2012 >>> [ 0.000000] ACPI: XSDT 0x000000008CD8E1C0 0000B4 (v01 APPLE >>> Apple00 00000000 01000013) >>> [ 0.000000] ACPI: FACP 0x000000008CD8C000 0000F4 (v04 APPLE >>> Apple00 00000000 Loki 0000005F) >>> [ 0.000000] ACPI: HPET 0x000000008CD8B000 000038 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: APIC 0x000000008CD8A000 0000BC (v02 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: SBST 0x000000008CD88000 000030 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: ECDT 0x000000008CD87000 000053 (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 0.000000] ACPI: MCFG 0x000000008CD89000 00003C (v01 APPLE >>> Apple00 00000001 Loki 0000005F) >>> [ 3.091740] usb 3-1.1: Manufacturer: Apple Inc. >>> [ 3.410516] usb 4-1.8.1: Manufacturer: Apple Inc. >>> [ 3.581141] usb 4-1.8.2: Manufacturer: Apple Computer, Inc. >>> [ 3.777265] usb 4-1.8.3: Product: Apple Internal Keyboard / >>> Trackpad >>> [ 3.777267] usb 4-1.8.3: Manufacturer: Apple Inc. >>> [ 3.782615] input: Apple Inc. Apple Internal Keyboard / Trackpad >>> as >>> /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8.3/4-1.8.3:1.0/0003:05AC:0252.0002/input/input13 >>> [ 3.833440] apple 0003:05AC:0252.0002: input,hidraw0: USB HID >>> v1.11 >>> Keyboard [Apple Inc. Apple Internal Keyboard / Trackpad] on >>> usb-0000:00:1d.0-1.8.3/input0 >>> [ 4.091248] apple 0003:05AC:0252.0003: hidraw2: USB HID v1.11 >>> Device [Apple Inc. Apple Internal Keyboard / Trackpad] on >>> usb-0000:00:1d.0-1.8.3/input1 >>> [ 4.319509] usb 4-1.8.1.3: Manufacturer: Apple Inc. >>> [ 4.457798] input: Apple Computer, Inc. IR Receiver as >>> /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8.2/4-1.8.2:1.0/0003:05AC:8242.0001/input/input18 >>> [ 4.509982] appleir 0003:05AC:8242.0001: input,hiddev0,hidraw4: >>> USB >>> HID v1.11 Device [Apple Computer, Inc. IR Receiver] on >>> usb-0000:00:1d.0-1.8.2/input0 >>> >>> ------ $ dmesg|grep EFI >>> [ 0.000000] efi: EFI v1.10 by Apple >>> [ 1.220269] fb0: EFI VGA frame buffer device >>> [ 2.619144] EFI Variables Facility v0.08 2004-May-17 >>> [ 4.205767] fb: switching to nouveaufb from EFI VGA >>> >>> ------ $ dmesg|grep gmux >>> [ 2.739845] apple_gmux: Found gmux version 1.9.35 [classic] >>> [ 4299.386843] apple-gmux 00:03: System wakeup disabled by ACPI >>> >>> ------ ~/Documents $ dmesg|grep DSM >>> [ 4.205710] ACPI Warning: \_SB_.PCI0.IGPU._DSM: Argument #4 type >>> mismatch - Found [Buffer], ACPI requires [Package] >>> (20141107/nsarguments-95) >>> [ 4.205724] ACPI: \_SB_.PCI0.IGPU: failed to evaluate _DSM >>> [ 4.205739] ACPI Warning: \_SB_.PCI0.P0P2.GFX0._DSM: Argument #4 >>> type mismatch - Found [Buffer], ACPI requires [Package] >>> (20141107/nsarguments-95) >>> [ 4.205749] ACPI: \_SB_.PCI0.P0P2.GFX0: failed to evaluate _DSM >>> >>> On Sun, Feb 15, 2015 at 5:13 AM, Pierre Moreau >>> <pierre.mor...@free.fr> wrote: >>> > Does the Nvidia card auto-suspends or do you have to force it? If >>> > not, does >>> > it report some “failed to parse _DSM” message? >>> > I have a mid 2009 MBP who uses a different _DSM handles than the >>> > ones >>> > Nouveau currently supports, and I wondered if they were related to >>> > the Apple >>> > Gmux or not. So, as you have a different model with a different >>> > Nvidia card >>> > but still with an Apple Gmux, I’d be interested to know if you have >>> > the same >>> > _DSM handles as I have. >>> > >>> > Pierre >>> > >>> > On 15 Feb 2015, at 06:44, Evan Foss <evanf...@gmail.com> wrote: >>> > >>> > Thanks again. >>> > >>> > This works and the heat has dropped substantially. It is still not >>> > as >>> > cool as I would like but this will do for now. I still need to file >>> > a >>> > bug report with the intel / apple gmux people. >>> > >>> > -Evan >>> > >>> > On Sat, Feb 14, 2015 at 10:42 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > On the older kernel >>> > >>> > [ 6.494956] nouveau [ CLK][0000:01:00.0] 07: core 270-405 >>> > MHz >>> > memory 838 MHz >>> > [ 6.494989] nouveau [ CLK][0000:01:00.0] 0a: core 270-774 >>> > MHz >>> > memory 1560 MHz >>> > [ 6.495015] nouveau [ CLK][0000:01:00.0] 0e: core 270-774 >>> > MHz >>> > memory 4000 MHz >>> > [ 6.495182] nouveau [ CLK][0000:01:00.0] --: core 405 MHz >>> > memory 680 >>> > MHz >>> > >>> > On Sat, Feb 14, 2015 at 10:35 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > Because I am on a macbook the VBIOS might be wonky. >>> > >>> > I tried turning off nVidia and using intel. The result was a blank >>> > screen. I know other people had the same bug which was something to >>> > do >>> > with reprobing lvds?! I saw patches go by and every time I tried >>> > one >>> > the results were the same. fail. I was actually about to post a bug >>> > report to the intel (i915) people about it. >>> > >>> > I tried to work out how to get optimus to work. After trying >>> > several >>> > different sets of instructions I never found a working >>> > configuration >>> > and put it aside. I never used to use opengl but lately my pcb >>> > software has adopted it so my needs changed. >>> > >>> > I will get back to you with more results on this matter after I get >>> > the newer kernel up. >>> > >>> > >>> > On Sat, Feb 14, 2015 at 10:09 PM, Ilia Mirkin >>> > <imir...@alum.mit.edu> wrote: >>> > >>> > On Sat, Feb 14, 2015 at 9:56 PM, Evan Foss <evanf...@gmail.com> >>> > wrote: >>> > >>> > I have a side question which may be the subject of a future second >>> > bug >>> > report. I have been lurking on the nouveau mailing list for some >>> > time. >>> > I understand from various posts that the nvidia gpu clock speed >>> > right >>> > now is set to the lowest possible setting. Why does my machine run >>> > so >>> > >>> > >>> > Often but not always the case -- the clock speed is whatever the >>> > VBIOS >>> > leaves it in. For kepler, that is usually the lowest setting. >>> > >>> > much hotter in linux than macos? I turned off the intel graphics >>> > and >>> > the cpu clock is set to the lowest available speed. >>> > >>> > >>> > You should instead turn off the nvidia graphics and run off intel >>> > -- >>> > intel is much less power-hungry than nvidia, even at the lowest >>> > clocks. If it's an optimus setup, the nvidia gpu should >>> > automatically >>> > power off until needed (either because some display is connected to >>> > it, or for offloading). >>> > >>> > >>> > How do I get a display of the GPU clocking speeds? >>> > >>> > >>> > You should see it in dmesg... look for CLK lines. The ones with -- >>> > (or >>> > AC/DC) will show the current setting. Or boot with nouveau.pstate=1 >>> > and you should have a /sys/class/drm/card*/device/pstate file. >>> > >>> > -ilia >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > >>> > >>> > >>> > >>> > -- >>> > Home >>> > http://evanfoss.googlepages.com/ >>> > Work >>> > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > _______________________________________________ >>> > Nouveau mailing list >>> > Nouveau@lists.freedesktop.org >>> > http://lists.freedesktop.org/mailman/listinfo/nouveau >>> > >>> > >>> >>> >>> >>> -- >>> Home >>> http://evanfoss.googlepages.com/ >>> Work >>> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >>> > > > > -- > Home > http://evanfoss.googlepages.com/ > Work > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ _______________________________________________ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
