Closed ArchangeGabriel closed 13 years ago
Sounds great.. really glad you're doing this work...
When you get the wiki up, I'll see what I can do to pull the info into the bumblebee-installer...
Fedora users should do
sudo yum install pmtools iasl
instead of
sudo apt-get install acpidump iasl
I presume you want people to submit info even if it has been submitted to https://bugs.launchpad.net/lpbugreporter/+bug/752542 (Just thought I would check. Looks like you also have added system-version to the file name.)
Also, I notice some people having issues with models that are 'known' to work. Perhaps this is due to variation in graphics hardware? (For example, I have a Dell Precision M4600 but that could be configured with a Quadro 1000M or 2000M and, for the 2000M, either an RGBLED or WLED screen. My internal display is DFP-5 (for some reason) but another M4600 owner always has it as DFP-0. Clearly some difference.) Perhaps it is worth collecting some info about the graphics processor, e.g. device ID? The model can be looked up using the text file at http://developer.nvidia.com/content/device-id-list
As on http://linux-hybrid-graphics.blogspot.com/2010/07/using-acpicall-module-to-switch-onoff.html the device ID can got from
lspci -vnnn | perl -lne 'print if /^\d+\:.+(\[\S+\:\S+\])/' | grep VGA
I could only find what looks like an incidental reference to my device ID in the ACPI DSL files. If it is actually captured, then please ignore me...
Yes I want to get them in addiation to the Launchpad thread because I don't have the time to match each post to a correct tar.gz file. While in the Launchpad thread the only goal was to found acpi calls to add them to the test_off.sh file, here we want to associate each file his computer.
Thank you for you comments, I'm adding them.
The Wiki is up at http://hybrid.graphics.free.fr/.
I will add content as fast as I can, but I'm really busy right now... If some people can make the base structure, that will be nice.
There is apparently a way to dump all the content from the bug report. Someone at launchpad did it for us for the first bug batch. It should allow you to script the list of device IDs from the tar.gzs. I sometimes use "tar xOzf *.tar.gz | grep something" to study the content of the files. I think it's a great idea to compile the info in a more meaningful way than just files in a launchpad bug. If there is anything I can do to help, please let me know.
Updated the bumblebee wiki ACPI page.
For the wiki @free.fr, I'm waiting for them to support PHP >=5.2
Moved to the new issues tracker.
I'm studying a lot of DSDT and SSDT files, and there is one thing that appears : we're not doing the good calls for most of the computers, because we're just calling the latest function from a serie of instructions, so we're not properly enabling or disabling the card.
I'm manually reversing the DSDT and SSDT tables, and I'm about launching a Wiki to store all the DSDT and SSDT tables together to work easier on them. It will be available at http://hybrid.graphics.free.fr, and the goal is to list all the Optimus machines and to have for each of them the DSDT and SSDT tables. I thinking about adding the commands we use for now for information, and the one we want to use and maybe some people in the community will be able to found the good things in the tables.
In one table I found a reference to Optimus, and it looks like that the method is ever the same...
It seems that WWMX is the thing we need. But I don't know yet enough ACPI to understand exactly how it works. So for now I will stay on the old ones, and choose to add machines before improving existing ones.
I will try to learn ACPI soon, but for now I have a lot of other things to do, and I can't find anything else than the specs to learn ASL...
Also I was thinking that we should get the enable disable scripts first from bumblebee files if available and then from DB.
I've created this issue to keep a trace of the work ongoing.
For people reading this, please see https://github.com/Bumblebee-Project/Bumblebee/wiki/ACPI
Thank you !