| 1 |
Version 3.2.1 - 26 April 2013 |
| 2 |
|
| 3 |
Highlights: |
| 4 |
- [hotfix] Fixed Bumblebee 3.2 not working on a lot of setups. |
| 5 |
This happened because of "Device" section splitting in xorg conf files. |
| 6 |
- [fix] Fixed an issue where an empty XorgModulePath lead to -isolateDecide |
| 7 |
being removed from Xorg start command line instead of -modulepath. |
| 8 |
|
| 9 |
Important notes for packagers: |
| 10 |
- In 3.2.1 release, we removed the bumblebee/xorg.conf.d/busid.conf file, |
| 11 |
because it was avoiding X to start in cases widely common. If your packaging |
| 12 |
system does not automatically remove it on upgrade to 3.2.1, then you will |
| 13 |
still have a broken optirun. You either need to remove this file on package |
| 14 |
upgrade or tell your distro users to do so, depending on your distro policy. |
| 15 |
- In 3.2 release, we have extended our nvidia-specific udev rule file to add |
| 16 |
device files (/dev/nvidia*) when the module is loaded (previously it would |
| 17 |
only remove those files when the module is unloaded). Consequently, we also |
| 18 |
changed its name. Some distributions, for example Gentoo, do not need to |
| 19 |
install this rule file because they already have a similar mechanism in |
| 20 |
place. Please also note that the rule file sets file permissions to 0666; you |
| 21 |
may want to adjust it to set permissions/owner/group more strictly according |
| 22 |
to your distribution's practice before installing. If you already use the |
| 23 |
kernel module options to declare permissions, simply running nvidia-smi on |
| 24 |
module load will do the job. |
| 25 |
|
| 26 |
Notes: |
| 27 |
- bbswitch is independent of the driver; vga_switcheroo works for nouveau only. |
| 28 |
See also the Known Issues section above and |
| 29 |
https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods |
| 30 |
- the video drivers must be unloadable. This means that it should not be |
| 31 |
compiled into the kernel. When using dynamically built modules like nvidia, |
| 32 |
be sure that the toolchain used for building the kernel matches the one that |
| 33 |
is used for building the module. This means that Ubuntu mainline kernels do |
| 34 |
not work and will cause crashes. |
| 35 |
- VirtualGL performance is very dependent on the Transport method set. The |
| 36 |
default "proxy" setting appears to perform bad in some situations. Try other |
| 37 |
available settings like "rgb" or "yuv". |
| 38 |
- in many cases, primus offers better performance; please try it and report |
| 39 |
compatibility issues in primus tracker, if you find any; for now VirtualGL is |
| 40 |
still preferred as the default autodetected render bridge, while primus is |
| 41 |
being tested at larger scales before being released as default. Try it and |
| 42 |
ensure everything you use works to help us build the best backend. |
| 43 |
|
| 44 |
Known issues: |
| 45 |
- vga-switcheroo won't survive suspension/hibernation (patch for newer Optimus |
| 46 |
machines for OFF to work has been published in Kernel 3.3; a good patch for |
| 47 |
suspend is still being prepared). |
| 48 |
- bbswitch cannot disable the discrete nvidia card for the Dell Vostro 360 |
| 49 |
desktop with Synergy. If you have a machine using that technology, please |
| 50 |
submit your machine information on: https://bugs.launchpad.net/bugs/752542 |
| 51 |
- Some laptops (mainly Lenovo) are neither supported by bbswitch nor the video |
| 52 |
drivers. See https://github.com/Bumblebee-Project/bbswitch/issues/2. This is |
| 53 |
fixed in Linux Kernel 3.9. |