lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Sep 2009 09:10:24 +0200
From:	Michal Witkowski <neuro@...pl>
To:	linux-kernel@...r.kernel.org
Subject: Explicitly putting a PCI device to ACPI D0

Hi,

I've been searching for my answer for a while now, and since I haven't found it anywhere, 
I've decided to post to LKML, hoping that someone here can help me.

First, I'll explain the background of my problem. My grief is the switchable GPU in my 
Lenovo Ideapad U330. The BIOS supports two options "Discrete only" (only the ATI card is 
visible on the BUS) and "Switchable" (both ATI and Intel card visible on the bus). The 
problem is the lack of a third option "Integrated", in which only the Intel card would be 
powered off. Lenovo refused to introduce such an option into the BIOS, stating that it's a 
feature request and not a bug.

To save battery power I'd like to be able to run on the Intel card. However, with the 
"Switchable" option, powertop indicates huge power usage (24W), which can only be 
explained by the fact that both cards draw power.

Thus, my question is the following:
Is there a way to explicitly put a device into ACPI D0? I would like to do that to the ATI 
card on boot.

I've tried the following code:
http://ftp.chg.ru/pub/parallel/scyld/diag/pci-config.c
But it didn't work (the ATI card was still on).

Cheers,
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ