Device Power Consumption Review

• Research Results
• Introduction for testing Power Consumption
• Machines
  • ASUS M2400N
    • Graphs
    • Results
    • lspci
    • Additional tests
      • External VGA Interface
      • WLAN modules
  • Compaq Aramada e500
    • Graphs
    • Results
    • lspci
  • Dialogue Flybook
    • Graphs
    • Results
    • lspci
  • HP nx5000
    • Graphs
    • Results
    • lspci
    • Additional tests
      • USB Mouse/Mice
  • IBM T40P
    • Graphs
    • Results
    • lspci
    • Additional tests
      • External VGA Interface
  • Medion MIM2080
    • Graphs
    • Results
    • lspci
  • Packard Bell MIT-COU-A-X86-64
    • Graphs
    • Results
    • lspci
• Scripts
  • devicedown.sh
  • consumption3.sh
  • average2.sh

Research Results

	***********************************************************
	*                                                         *
	*            Device Power Management (DPM)                *
	*                                                         *
	***********************************************************


1) Introduction
---------------

When talking about "Device Power Management" in general, the main purpose
is to put unused devices into a powersaving mode to reduce overall power
consumption of a system. This is particularly important in respect of
mobile devices to increase battery life time when running without an ac
adapter. But it could even be interesting on workstations. However, the
hardware on desktop systems often does not support power saving.

Having in mind that other operating systems are still often one step ahead
regarding drivers and laptop support, working on Device Power Management
within linux is just a logical consequence.

Therefore we invite everybody to start a discussion about everything
mentioned in this text and to provide proposals or criticism. We are still
designing/planning further steps, so this is the right time for helpful
suggestions and/or hints.


2) Device examination - measurements
------------------------------------

Every pci device has a builtin powersave mode which should be supported by
default:

  short facts about the modes:
        
        quote from linux/Documentation/power/pci.txt:
        
        1. Overview
        ~~~~~~~~~~~
        [...]
        The PCI PM spec defines 4 operating states for devices (D0 - D3)
        and for buses (B0 - B3). The higher the number, the less power the
        device consumes. However, the higher the number, the longer the
        latency is for the device to return to an operational state (D0).
        [...]


For putting devices into powersave mode, the easiest way is to use sysfs:

  echo -n <mode> > /sys/bus/pci/devices/<pci-id>/power/state
       
  <mode> is one of
         3 - D3 powersave mode
         0 - powersaving off (default)

Within the scope of our tests, we only took D3 mode into respect because
it should be supported by default on all devices and/or drivers.

Daniel Gollub (dgollub@suse.de) set up a whole test environment (scripts &
graphs, ampere-meter, etc.) and tested a lot of devices on our
available hardware for their powersave capabilities and made interesting
recognitions. The following test environment came into operation:

  - OS: SUSE Linux 10.0
  - AC-Adapters: 18.5V 
  - laptop model(s):
        * ASUS M2400N
                # with different WLAN modules: ipw2100, ipw2200,
                                               Atheros AR5212
        * HP nx5000
        * Packard Bell MIT-COU-A
        * Medion MIM280
  - booting first with runlevel 5 and switch to runlevel 1 (e.g. no
    cronjobs, no X)
  - battery removed, so the real power consumption (no loading of battery)
    is measured
  - ampere-meter directly connected between AC adapter and laptop
  - data collected via rs232 interface on another machine with QtDMM [1]
  - ntp time sync on measuring-machine and test-laptop
  - unplugging Ethernet cable on test-laptop and stopping network service

  - check current power consumption, push device by device into D3 mode
    for 60 seconds and compare the two values:
            D0: average consumption before suspend
            D3: average consumption while suspended

Here is a list of obvious devices which were tested in detail. Don't
consider this list as finished, it is still work in progress or even under
construction. All values state the average power consumption and are as
precise as possible. This list is a summary of all test information. For
more detailed information, you may want to have a look at our prepared
graphs.

* WLAN cards

  There is a huge potential for saving power for such
  devices. Additionally, some wlan drivers (e.g. ipw2*00, orinoco, ...)
  have another builtin powersave mode which is disabled by default. This
  mode allows the wlan card to reduce its transmission power if the radio
  signal is strong enough without preventing it from working. This is only
  a small hint and will not be covered in this review.

  The network system was stopped and so the WLAN was _inactive_ while
  collecting this data!

  Model               chipset                   module      D0(A)  D3(A)  profit(A)
  ---------------  ---------------------------  ----------  -----  -----  ---------
  HP nx5000        Intel PRO/Wireless LAN 2100  ipw2100     0.806  0.729  0.077
  ASUS M2400N      Intel PRO/Wireless LAN 2100  ipw2100     0.757  0.661  0.096
  ASUS M2400N      Intel PRO/Wireless LAN 2200  ipw2200     0.759  0.654  0.105
  ASUS M2400N      Atheros AR5212 802.11abg     ath_pci     0.723  0.657  0.066
  Packard Bell     RaLink RT2500 802.11         rt2500      1.173  1.133  0.040

* Soundcard

  Despite not playing any sound, the soundcard every time consumes some
  power which could be saved.

  Model                     chipset                      module     D0(A)  D3(A)  profit(A)
  --------------  ----------------------------------  ------------  -----  -----  ---------
  HP nx5000       Intel 82801DB/DBL/DBM (ICH4) AC'97  snd_intel8x0  0.806  0.765  0.041
  ASUS M2400N     Intel 82801DB/DBL/DBM (ICH4) AC'97  snd_intel8x0  0.757  0.727  0.030
  Medion MIM280   VIA VT8233/A/8235/8237 AC97         snd_via82xx   0.742  0.719  0.023
  Packard Bell    VIA VT8233/A/8235/8237 AC97         snd_via82xx   1.173  1.141  0.032


* LAN cards

  Powering down usual network cards only saves power when used. But we
  assume that a usual user needs his network interface when it is used
  atm.

* USB devices / hotpluggable devices

  Usual usb devices like mice or keyboards do not consume a noteworthy
  amount of power. What is more important are external usb harddisks or
  cardbus interfaces. For the moment we assume that if a user wants to
  save power, he is able to remove the device. For instance, we could give
  the user a hint when powering down devices the first time that there are
  other possibilities to save power. But this needs further discussion I
  think.

  (Hint: On most USB (mainly Input) the power consumption is printed on
  the back.)

* Display Brightness

  Reducing the brightness of the display helps a lot. Fortunately,
  this feature is already present within the powersave daemon.

* Internal modems

  Disabling internal modems if not used does not save much power. But due
  to the fact that many (win-)modems are unsupported anyway, we could also
  disable them.

For having more close to reality values, we also tested WLAN, LAN, Sound
and Modem in combination on the HP nx5000 and checked power consumption
for 60 seconds in runlevel 5. Summarizing these devices we could save
theoretical about 115mA on the HP nx5000 which could mean about 23
additional minutes of battery (capacity 2200mAh) life time. Only with
sending four common devices in D3 mode without changing the brightness of
the display.

Additionally, we tested the ASUS M2400N (battery capacity: 4400mAh) with
active WLAN&LAN. While doing this test, the "Performance scheme" from the
powersave daemon[2] came into operation(=highest power consumption with
idle cpu). The results of this test were compared with WLAN, LAN, Modem,
Cardbus, USB Hosts, IEEE1394 and Sound put into D3 mode and the "powersave
scheme" from the powersave daemon (fix 600MHz instead of fix 1400MHz,
medium brightness). We got astonishing results! We could theoretically
save about 295mA which could mean about two houres and 10 minutes of
additionally battery life time!

For getting such good results, of course, it depends on the
hardware. While looking into a MEDION mim280, there were nearly no power
savings with all components.

We would love to get other ideas, criticism or any feedback on all
this. Please ask if something should be not clear or needs more detailed
explanations.


Regards,
	Holger, Daniel


[1] http://mtoussaint.de/qtdmm.html
[2] http://powersave.sourceforge.net

Instruction for testing power consumption

Step by step:

1. unplug your ac-adapter from mains!
2. unplug everything else! no power, no hurt, no destruction
3. remove battery from laptop!
4. check the polarity of the DC connector
5. plug in your ac-adapter to the test-PCB (printed circuit board)
6. check the connection between:
   • laptop - test-PCB
   • test-PCB - multimeter
   • multimeter - pc
7. set your multimeter to DC A, measurement-scale of 20 A
8. plug in the ac-adapter
9. turn on your laptop
10. boot runlevel 5 (don't boot runlevel 1 directly ...)
11. copy devicedown.sh on the test machine
12. switch back to runlevel 1
13. take a deep breath
14. run devicedown.sh with testing-duration per devices in seconds as parameter ( recommend: ./devicedown.sh 60 )
15. follow the instruction of devicedown.sh:
    1. restart network
    2. sync time of test-machine and measurement-system
    3. unplug the Ethernet cable
    4. run QtDMM (or equal) on measurement-system
    5. start measurement in QtDMM
    6. select devices which should be tested
    7. start testing
    8. ...wait...and...press..a..key..to..prevent..DPM..(display power management = blank screen)....
    9. ... wait - when test is finished stop QtDMM/measurement
    10. plug-in your ethernet cable and restart network
16. copy the consumption-report file to the measurement-system
17. export the log file in QtDMM - name it "consumption report file".log
18. run consumption3.sh [info] >> ./consumption3.sh consumption-report-file TEST_MACHINE 6000
19. now you can find a graph with detailed information in $(pwd)
20. finish :)

Machines

ASUS M2400N

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:03.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a9)
01:03.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a9)
01:03.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 01)
01:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:05.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)

Additional tests

External VGA Interface

#1 Diagram:
On the first 60 seconds the external VGA interface was activated by X, then inactive (by X)

#2 Diagram:
System was booted with plugged in CRT display and was active. But the external VGA interface was not activated by the X module. The measurement was while system was in runlevel 5 idle. After 60 seconds the CRT connection was unplugged. No screen on CRT, no changes of consumption. (After replugging no signal on CRT (normal issue) no changes on consumption.)

#3 Diagram:
Green graph shows system in Suspend to RAM mode with active external VGA interface. Red graph shows system in Suspend to RAM mode with inactive external VGA interface.

WLAN Modules

#1 Diagram
Graph shows WLAN module ipw2200 changing to D3 and back. With active (idle) connection.

#2 Diagram
Graph shows WLAN module Atheros changing to D3 and back. IMPORTANT: Atheros seems to have good power management and throttle power consumption itself when no connection is available. When there is no active connection there are immeasurable consumption differences when changing to D3.

Compaq Armada e500

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:04.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 09)
00:09.1 Serial controller: Agere Systems LT WinModem
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)

Dialogue Flybook

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 03)
00:00.1 RAM memory: Transmeta Corporation SDRAM controller
00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad
00:03.0 Modem: ALi Corporation M5457 AC'97 Modem Controller
00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02)
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
00:09.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0b.0 USB Controller: NEC Corporation USB (rev 43)
00:0b.1 USB Controller: NEC Corporation USB (rev 43)
00:0b.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
00:0c.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus Controller (rev 02)
00:0c.1 FireWire (IEEE 1394): Texas Instruments PCI4510 IEEE-1394 Controller
00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]

HP nx5000

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
01:06.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
01:06.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
01:06.3 Unknown mass storage controller: Texas Instruments PCI7420/PCI7620 Dual Socket CardBus and Smart Card Cont. w/ 1394a-2000 OHCI Two-Port  PHY/Link-Layer Cont. an
01:0d.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
01:0e.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)

Additional tests

USB Mouse/Mice

Voltage: 18.5 V

IBM T40P

Voltage: 18.5 V

Graphs

not available at the moment :(

Results

not available at the moment :(

lspci

00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 02)
02:00.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) (rev 03)
02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab NIC (rev 01)

Additional tests

External VGA Interface

ATI Technologies Inc Radeon R250 Lf [FireGL 9000]

Medion MIM2080

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:06.0 Ethernet controller: Winbond Electronics Corp: Unknown device 0033
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 02)

Packard Bell MIT-COU-A-X86-64

Voltage: 18.5 V

Graphs

Results

lspci

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0204
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0a.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

Scripts

devicedown.sh

Power Consumption test script, which brings selected devices in D3 and back to D0, for a specific duration. The script creates a log file named:

> consumption_report.UNIX_TIME_STAMP

The log file contains date of test, lspci output of test machine, and point of time of D0 D3 transition.

usage: devicedown.sh <seconds>

devicedown.sh [bash]

consumption3.sh

consumption3.sh evaluate the measure-logfile and testing-logfile of the test machine and draws an graph (like above). This script requires gnuplot - http://www.gnuplot.org

usage: consumption3.sh <logfile> <machine name> <graph width (px)>

<logfile> - use devicedown.sh log file for this and name QtDMM with append .log

        devicedown.sh log: consumption_report.112912790
        QtDMM log should be named: consumption_report.112912790.log
        in this case -> consumption3.sh consumption_report.112912790 ASUS_M2400N 6000

<machine name> - as a single string. for example:

        IBM T40P -> consumption3.sh consumption_report.112912790 IBM_T40P 6000
        Compaq Armada e500 -> consumption3.sh consumption_report.11291790 Compaq_Armada_e500 6000

consumption3.sh [bash]

average2.sh

average2.sh - calculate the average of power consumption and return a HTML table.

usage: average2.sh <log file>

average2.sh [bash]