Closed gnetwork-git closed 13 years ago
Remove the lines if [
lspci -v -s $NVIDIABUSID |grep ! |wc -l-eq 1 ]; then
and a fi
folowing per https://github.com/MrMEEE/bumblebee/commit/5c48dfd6f1dd04642cdd1bf01e417345a61a6f42.
The next stable release is due the end of the week, the new codebase is on https://github.com/Bumblebee-Project/Bumblebee
sorry, dont understand what to do. if this be in next stable release, i can wait. otherwise, can u give me idea how to do it.
Please wait for the next stable update then, the current implementation contains some flaws.
Please try the new version here : https://github.com/Bumblebee-Project/Bumblebee.
i used the ppa to install before. can u tell me best way to upgrade it, i'm not sure. thankyou.
G
On 24/08/11 04:17, ArchangeGabriel wrote:
Please try the new version here : https://github.com/Bumblebee-Project/Bumblebee.
sudo apt-get install ppa-purge sudo ppa-purge ppa:mj-caslogic/ppa wget https://raw.github.com/Bumblebee-Project/Bumblebee/master/cleanup chmod +x cleanup sudo ./cleanup
sudo add-apt-repository ppa:bumblebee/stable sudo apt-get update sudo apt-get install bumblebee
sudo usermod -a -G bumblebee YOURUSERNAME
@ArchangeGabriel: please add the usermod
part to your next instructions. Updated your post.
thanks for that. it all seems to work ok, even tho i didnt do the enable/disable card files this time (i guess its built-in now). see my results below:
Unplug the power supply, and run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 1770 mA
Then run glxgears, wait ~30s, then close the window, and give the result.
glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 301 frames in 5.0 seconds = 60.194 FPS 301 frames in 5.0 seconds = 60.007 FPS 301 frames in 5.0 seconds = 60.001 FPS 301 frames in 5.0 seconds = 60.003 FPS 300 frames in 5.0 seconds = 59.998 FPS 301 frames in 5.0 seconds = 60.006 FPS
Then optirun glxgears. While it's running, in an other terminal, run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 2737 mA
Close the glxgears window, give the result.
optirun glxgears 2126 frames in 5.0 seconds = 425.029 FPS 2086 frames in 5.0 seconds = 417.100 FPS 2198 frames in 5.0 seconds = 439.582 FPS 2011 frames in 5.0 seconds = 402.059 FPS 2053 frames in 5.0 seconds = 410.413 FPS 2022 frames in 5.0 seconds = 404.234 FPS
what do u reckon, does it look ok? if so, my next task will be to try it on Linux Mint, fingers crossed as its my main working os.
G
On 24/08/11 07:52, ArchangeGabriel wrote:
sudo apt-get install ppa-purge sudo ppa-purge ppa:mj-caslogic/ppa wget https://raw.github.com/Bumblebee-Project/Bumblebee/master/cleanup chmod +x cleanup sudo ./cleanup
sudo add-apt-repository ppa:bumblebee/stable sudo apt-get update sudo apt-get install bumblebee
run again after: sudo usermod -a -G bumblebee YOURUSERNAME
Unplug the power supply, and run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 1854 mA
Then run glxgears, wait ~30s, then close the window, and give the result.
glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 303 frames in 5.0 seconds = 60.462 FPS 301 frames in 5.0 seconds = 60.032 FPS 301 frames in 5.0 seconds = 60.032 FPS 301 frames in 5.0 seconds = 60.031 FPS 301 frames in 5.0 seconds = 60.032 FPS 301 frames in 5.0 seconds = 60.032 FPS
Then optirun glxgears. While it's running, in an other terminal, run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 2944 mA
Close the glxgears window, give the result.
optirun glxgears 2031 frames in 5.0 seconds = 406.121 FPS 2082 frames in 5.0 seconds = 416.372 FPS 2079 frames in 5.0 seconds = 415.708 FPS 2183 frames in 5.0 seconds = 436.541 FPS 2070 frames in 5.0 seconds = 413.968 FPS 2454 frames in 5.0 seconds = 490.541 FPS
On 24/08/11 08:24, Lekensteyn wrote:
@ArchangeGabriel: please add the
usermod
part to your next instructions. Updated your post.
after reading some more on current stage of development, i sent the ACPI info to free.fr email as requested on https://github.com/Bumblebee-Project/Bumblebee/wiki/ACPI
On 24/08/11 08:24, Lekensteyn wrote:
@ArchangeGabriel: please add the
usermod
part to your next instructions. Updated your post.
You're was already in the bumblebee group.
So it works for you. However, please read the https://github.com/Bumblebee-Project/Bumblebee/wiki/ACPI-Removed page.
And for now on, it's better to test using glxspheres that gives a real benchmark tool and also indicates which GPU is running.
run again with glxspheres:
Unplug the power supply, and run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 1955 mA
glxspheres Polygons in scene: 62464 Visual ID of window: 0x93 Context is Direct OpenGL Renderer: Mesa DRI Intel(R) Sandybridge Mobile GEM 20100330 DEVELOPMENT 28.965708 frames/sec - 32.325731 Mpixels/sec 29.746433 frames/sec - 33.197019 Mpixels/sec 29.530164 frames/sec - 32.955663 Mpixels/sec 29.484949 frames/sec - 32.905203 Mpixels/sec 29.527884 frames/sec - 32.953118 Mpixels/sec 29.521209 frames/sec - 32.945669 Mpixels/sec
Then optirun glxspheres. While it's running, in an other terminal, run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 3164 mA
Close the glxspheres window, give the result.
optirun glxspheres Polygons in scene: 62464 Visual ID of window: 0x21 Context is Direct OpenGL Renderer: GeForce GT 525M/PCI/SSE2 65.769291 frames/sec - 73.398529 Mpixels/sec 63.521804 frames/sec - 70.890333 Mpixels/sec 53.863265 frames/sec - 60.111403 Mpixels/sec 57.332314 frames/sec - 63.982863 Mpixels/sec 51.979868 frames/sec - 58.009532 Mpixels/sec 53.137710 frames/sec - 59.301685 Mpixels/sec
i guess this is because the test glxspheres is bigger load, framerate drops.
i also tried:
optirun firefox
(firefox-bin:2293): LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, modifier)' failed
then after closing firefox
* NSPlugin Viewer * WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() * NSPlugin Viewer * WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() NOTE: child process received `Goodbye', closing down
firefox seems to work all ok.
i love the ideas for future directions with Bumblebee. this is first version seems to work in Ubuntu on this machine. i may go from Linux Mint back to Ubuntu as main OS soon. i have never got bumblebee to work successfully on Linux Mint 11, and am cautious to try again, as it may ruin my main working OS. at least until we have a distro-independent version.
thanks for the code.
On 24/08/11 18:29, ArchangeGabriel wrote:
You're was already in the bumblebee group.
So it works for you. However, please read thehttps://github.com/Bumblebee-Project/Bumblebee/wiki/ACPI-Removed page.
And for now on, it's better to test using glxspheres that gives a real benchmark tool and also indicates which GPU is running.
in response to https://github.com/MrMEEE/bumblebee/issues/368#issuecomment-1553300
Dell Inspiron N5110 - using current enable/disable card setings available, on Ubuntu 11.04 clean install.
Unplug the power supply, and run : grep rate /proc/acpi/battery/BAT0/state Give the result.
present rate: 1883 mA
Then run glxgears, wait ~30s, then close the window, and give the result.
303 frames in 5.0 seconds = 60.481 FPS 301 frames in 5.0 seconds = 60.001 FPS 300 frames in 5.0 seconds = 59.999 FPS 301 frames in 5.0 seconds = 60.002 FPS 301 frames in 5.0 seconds = 60.007 FPS 301 frames in 5.0 seconds = 60.003 FPS 300 frames in 5.0 seconds = 59.996 FPS
Then optirun glxgears. While it's running, in an other terminal, run : grep rate /proc/acpi/battery/BAT0/state Give the result.
optirun glxgears