Huh, I was thinking that blacklisting forbid to modprobe anyway.

People with a non-Optimus laptop will face an huge issue (anyway I dunno what is the result of a bumblebee installation on a non-Optimus system). However, that's not really a problem because it should lead them to discover they're not having an Optimus system.

Can you remind me how bumblebee detects which driver to use ? (Just to verify something).

I will test to blacklist both and see the result.

Bruno

Le 29/04/2012 20:01, Lekensteyn a écrit :
Hi Bruno,

What do you think of blacklisting nvidia and nouveau by default? The driver is unloaded
anyway when starting bumblebee. This change will also solve race conditions with
nvidia being loaded in the middle of bumblebee's startup. There is a little regression
chance since the driver cannot be used anyway on boot time. If it turns out to be
an issue, the user can remove the blacklist and/ or manually modprobe it.

Peter

On Sun, Apr 29, 2012 at 5:28 PM, Lekensteyn <lekenst...@gmail.com> wrote:
Hi Bruno,

Some feature/bugfix patches (that 2k trunk-....patch file) may be added to lucid and natty too,
but I the ...-ia32 changes do not make sense as the lucid and natty do not support multiarch
and those virtualgl packages do already contain both the 32-bit and 64-bit libraries.

We provide libjpeg-turbo 1.1.1 for lucid+natty in the testing repository (which is our
sandbox for building) indeed.

It just occurred to me that Ubuntu ships updated drivers with nvidia-current-updates.
The FAQ in the Ubuntu wiki probably needs to be updated that if you use that
package, KernelDriver=nvidia-current-updates must be set. LibraryPath and
ModulePath have to be adjusted in a similar way.

Now, I'll prepare a change for the preinst script to copy users from adm, admin and
sudo to the group "bumblebee" and test it.

You can just copy the acpi-call package from testing to stable.

Regards,
Peter


On Sun, Apr 29, 2012 at 5:19 PM, Bruno Pagani <bruno.n.pag...@gmail.com> wrote:
Hi Peter,

Ok for the uninstall behavior, that's correct.

How would you update virtualgl for lucid and natty then ? Providing libjpeg-turbo is done by our repo, isn't it ?

Copying adm, sudo(ers) and admin to bumblebee looks fine.

I will update acpi-call too for people who needs it.

Bruno

Le 29/04/2012 19:03, Lekensteyn a écrit :
Hi Bruno,

I've just booted a fresh Live session of Kubuntu 12.04 AMD64 and can confirm that the new packages are
working properly. I'll do another test with Ubuntu 12.04 I think.

The "little problem with uninstall" is actually the expected behavior. If you install Bumblebee accidentally
on a system with no Optimus, the configuration should not be forced to use the Mesa libs. Purging
nvidia-current is the correct behavior.

virtualgl depends on libturbojpeg because the static library could not be linked into the shared
librrfaker.so library from virtualgl. Note: this change is **not** directly backportable to versions older
than Oneiric because natty and older do not have libjpeg-turbo in the official repositories nor
support for Multi-Arch.

A workaround for the adduser stuff is by setting the default group to "adm" or "sudo" thus
avoiding adding the default user to a group. This is really bad practise though as these
groups have little relevance with bumblebee. What about copying the adm ("may read
system logs"), sudo (sudoers users in 12.04 and later), admin (sudoers in 11.10 and before)
members to bumblebee? That works in a default installation.

Summarizing the packages that needs to be copied to stable (letters indicate ubuntu versions):

- virtualgl: o,p (oneiric,precise)
- bumblebee: l, n, o, p (no maverick, support is dropped)
- bbswitch: lnop (copy from precise) (aside, I just copied p -> lno in testing)

libjpeg-turbo is dropped from precise and later since the repositories already contain this
package. We may drop it from oneiric too for the same reason, but let's keep it as it.

acpi-call is useful for testing and I know that some are still using it to trigger a
switch of the card for certain hardware. Let's copy 1.1.1 from testing to stable, lnop?

Peter

PS. I'm cc'ing this to the bumblebee ml as the public may be interested in this conversation

On Sun, Apr 29, 2012 at 3:47 PM, Bruno Pagani <bruno.n.pag...@gmail.com> wrote:
Hi Peter,

Did saw that you've updated the packages. I did some test, all worked fine. Update is OK, new installation on amd64 does also install i386 appropriate libs, so, looks perfect for me. Just faced a little problem with uninstall, I lost 3D acceleration on Intel chip, but uninstalling nvidia-current solved that.

I've noticed that virtualgl now depends on libjpeg-turbo. I suppose this is necessary ? Else, I find still clumsy this need to adduser. Don't we have any alternatives for that ?

If everything is OK for you too, I'm going to create missing packages for other distributions, update all logs and script and upload those.

Bruno






-- 
Mailing list: https://launchpad.net/~bumblebee
Post to     : bumblebee@lists.launchpad.net
Unsubscribe : https://launchpad.net/~bumblebee
More help   : https://help.launchpad.net/ListHelp

Reply via email to