hybrid-graphics-linux team mailing list archive

[Albert Vilella <avilella@xxxxxxxxx>]

fwd to the mailing list.

On Mon, Apr 4, 2011 at 4:10 PM, Hans Persson <perssonhans78@xxxxxxxxx> wrote:
> Hi Albert,
>
> Yes loading and running it works, as seen in attatched file. My power
> consumption is down by apporx. 4 W.
>
> But my computer will not shut down after switching of the NVidia chip.
> I guess it's because my computer still loads the nv driver?!
> I still don't know how to stop this driver from loading.
>
> There are some error messages while trying to shut down, which I can not
> find in dmesg, so I'm afraid I can not send them to you.
>
>
> Cheers
> Hans
>
>
> 2011/4/3 Albert Vilella <avilella@xxxxxxxxx>
>>
>> Hi Hans,
>>
>> Can you check if this works for your ASUS 1215N?
>>
>> https://lists.launchpad.net/hybrid-graphics-linux/msg00254.html
>>
>> On Fri, Apr 1, 2011 at 4:03 PM, Hans Persson <perssonhans78@xxxxxxxxx>
>> wrote:
>> > Hi all,
>> >
>> > I have a ASUS 1215N as follows:
>> >
>> > 1215N
>> > x.x
>> > 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family
>> > Integrated Graphics Controller [8086:a001] (rev 02) (prog-if 00 [VGA
>> > controller])
>> > 05:00.0 VGA compatible controller [0300]: nVidia Corporation Device
>> > [10de:0a76] (rev a2) (prog-if 00 [VGA controller])
>> >
>> > I hope I will be able to help with testing and debugging.
>> >
>> > Regards
>> > Hans Persson
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~hybrid-graphics-linux
>> > Post to     : hybrid-graphics-linux@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~hybrid-graphics-linux
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>
>

Message log relating acpi_call

Loading kernel module and running ASUS 1215N script
Apr  4 16:15:35 hans-1215N kernel: [   90.586870] acpi_call: Module loaded successfully
Apr  4 16:16:12 hans-1215N kernel: [  127.661677] acpi_call: Calling \_SB.PCI0.P0P4.GFX0.P3MO
Apr  4 16:16:12 hans-1215N kernel: [  127.661710] acpi_call: Call successful: 0x0
Apr  4 16:16:12 hans-1215N kernel: [  127.663703] acpi_call: Calling \_SB.PCI0.P0P4.GFX0.DGPS
Apr  4 16:16:12 hans-1215N kernel: [  127.663736] acpi_call: Call successful: 0x0
Apr  4 16:16:12 hans-1215N kernel: [  127.665875] acpi_call: Calling \_SB.PCI0.P0P4.GFX0._PSC
Apr  4 16:16:12 hans-1215N kernel: [  127.665910] acpi_call: Call successful: 0x0
Apr  4 16:16:17 hans-1215N kernel: [  132.229323] acpi_call: Calling \_SB.PCI0.P0P4.GFX0._DSM
Apr  4 16:16:17 hans-1215N kernel: [  132.229879] acpi_call: Call successful: {0x59, 0x00, 0x00, 0x11}
Apr  4 16:16:17 hans-1215N kernel: [  132.231897] acpi_call: Calling \_SB.PCI0.P0P4.GFX0._PS3
Apr  4 16:16:17 hans-1215N kernel: [  132.388101] acpi_call: Call successful: 0x0
Apr  4 16:16:17 hans-1215N kernel: [  132.390202] acpi_call: Calling \_SB.PCI0.P0P4.GFX0.P3MO
Apr  4 16:16:17 hans-1215N kernel: [  132.390234] acpi_call: Call successful: 0x0
Apr  4 16:16:17 hans-1215N kernel: [  132.392206] acpi_call: Calling \_SB.PCI0.P0P4.GFX0.DGPS
Apr  4 16:16:17 hans-1215N kernel: [  132.392239] acpi_call: Call successful: 0x1
Apr  4 16:16:17 hans-1215N kernel: [  132.394323] acpi_call: Calling \_SB.PCI0.P0P4.GFX0._PSC
Apr  4 16:16:17 hans-1215N kernel: [  132.394357] acpi_call: Call successful: 0x3