Optirun broken by nvidia-current update on Asus 1215-n

MrMEEE / bumblebee-Old-and-abbandoned

OUTDATED!!!!! - Replaced by "The Bumblebee Project" and "Ironhide"

http://www.martin-juhl.dk/2011/08/ironhide-reporting-for-duty/

469 stars 50 forks source link

Optirun broken by nvidia-current update on Asus 1215-n #475

Closed DrJohn999 closed 13 years ago

DrJohn999 commented 13 years ago

Installed Bumblebee from PPA sucessfully. All was working fine until yesterday when update manager hit with an update to nvidia-current 275.19-0~nattyubuntu1. I removed (not purged) bumblebee and reinstalled. Enable/disablecard works fine, but optirun fails:

~$ optirun glxgears
 * Starting Bumblebee X server bumblebee                                        Enabled nVidia card
FATAL: Error inserting nvidia_current (/lib/modules/2.6.38-10-generic/updates/dkms/nvidia-current.ko): No such device
                                                                         [ OK ]
 * Stopping Bumblebee X server bumblebee                                        ERROR: Module nvidia does not exist in /proc/modules
Disabled nVidia card
                                                                         [ OK ]

Would you like to see xorg.1.log?

jaybanez commented 13 years ago

I got the same with an Acer Aspire 5750G with a GeForce GT 540M

_PS0 Enabling nVidia Card Succeded. FATAL: Error inserting nvidia_current (/lib/modules/2.6.38-10-generic/updates/dkms/nvidia-current.ko): No such device

. * . * . * . * . * . * . * . * . * . Bumblebee server failed to start
Stopping Bumblebee X server bumblebee Skipping: nVidia Card already disabled

lintah commented 13 years ago

Have you tried to rerun bumblebee-configuration?

alexsantos commented 13 years ago

Same thing happened to me. Removed nvidia-current and bumblebee and reinstalled solved the problem. BTW, I have a Packard Bell that works fine with the Acer 5750G profile (they are basically the same notebook)

lintah commented 13 years ago

@AlexSantos

Have you tried to re-run the bumblebee-configuration before you reinstalled bumblebee?

alexsantos commented 13 years ago

It was late at night... but I think I did it, yes. What I guessed was that it was a linking problem between bumblebee and the nvidia-module, so reinstalling recreated it all again.

2011/7/22 lintah < reply@reply.github.com>

@AlexSantos

Have you tried to re-run the bumblebee-configuration before you reinstalled bumblebee?

Reply to this email directly or view it on GitHub: https://github.com/MrMEEE/bumblebee/issues/475#issuecomment-1630814

alexsantos commented 13 years ago

Well, let me point one thing out: just tried to recreate what I did last night. This error appeared after modifying the acpi_call address. What you must do is try different profiles till you stop getting that error. You do that by running bumblebee-configuration. As I said, my PB TS-11 works fine with the Acer profile. Alex

2011/7/22 Alexandre Santos santosam72@gmail.com

It was late at night... but I think I did it, yes. What I guessed was that it was a linking problem between bumblebee and the nvidia-module, so reinstalling recreated it all again.

2011/7/22 lintah < reply@reply.github.com>

@AlexSantos

Have you tried to re-run the bumblebee-configuration before you reinstalled bumblebee?

Reply to this email directly or view it on GitHub: https://github.com/MrMEEE/bumblebee/issues/475#issuecomment-1630814

DrJohn999 commented 13 years ago

Solved by:

sudo apt-get purge bumblebee
sudo apt-get remove nvidia-current
sudo apt-get install nvidia-current
sudo apt-get install bumblebee

I can choose any of the 1215n bumblebee configurations that create in /etc/X11/xorg.nvidia.conf:

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:04:00:0"
    Option         "IgnoreEDID"
    Option     "ConnectedMonitor" "DFP-0"
EndSection

If this problem is to occur each time nvidia-current or perhaps other updates come down, then isn't this issue a bug? Bumblebee shouldn't have this dependency on nvidia-current that's broken by updates.

arbrandes commented 13 years ago

All I had to do to solve this problem (on an Asus U43JC) was a:

$ sudo dpkg-reconfigure bumblebee

But I agree, this should be done automatically by the update. It's really scary when you reboot and the drivers are all messed up. :)

wilriker commented 13 years ago

I get the same error most of the time any part of bumblebee gets an update (had it yesterday when I guess VirtualGL got an update). My simple but yet working solution is to reboot. After that it usually works again - as I'm coming from Windwos, that's a quite common strategy. Maybe not so much in Linux-environments. ;-)

ArchangeGabriel commented 13 years ago

We have some problems with updates effectively...