Optirun glxgears unable to run (UL30Vt/G210M)

[weiliddat]

I've installed Bumblebee, enablecard and disablecard works, but optirun is not able to run anything.

When running "optirun glxgears", it returns

_PS0 Enabling nVidia Card Succeded.
- .  
- .  
- .  
- .  
- .  
- .  
- .  
- .  
- .  
- .  
  Bumblebee server failed to start
- Stopping Bumblebee X server bumblebee  
  _PS0 Disabling nVidia Card Succeded.```

[MrMEEE]

Is this the PPA version or the script version??? Could you please send me a bugreport, run bumblebee-bugreport

[Hoverbear]

I'm also having this issue.

Edit: I should note this outright fails running anything.

[weiliddat]

I got it using git bumblebee, so I think it's the script version. I'll send you the report asap, since i've no access to my laptop at the moment.

[Hoverbear]

Yeah, it was working fine just 2 days ago or so.

On Fri, Jul 8, 2011 at 8:43 PM, ksat90 < reply@reply.github.com>wrote:

I got it using git bumblebee, so I think it's the script version. I'll send you the report asap, since i've no access to my laptop at the moment.

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

[ArchangeGabriel]

I'm working on a solution, but there is a critical bug to solve first.

[Hoverbear]

Alright, I thought something was the matter, let me know if you need a tester.

[ArchangeGabriel]

Which distro are you on ?

[Hoverbear]

I'm running Kubuntu 11.04.

On Sat, Jul 9, 2011 at 12:51 PM, ArchangeGabriel < reply@reply.github.com>wrote:

Which distro are you on ?

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

[ArchangeGabriel]

Ok, can you upload both enable and disable scripts, the /etc/X11/xorg.conf.nvidia file and the Xorg log file corresponding to an attempt to run something via bumblebee.

An one more thing, which model are you using ? An UL30Vt ? Because I've just realized something for the original posters: the Asus UL30Vt isn't an Optimus laptop, so maybe it has something to do with that...

[Hoverbear]

I'm actually using a Lenovo T420, but I'm having a similar issue.

My enable and disablecard scripts simply call bumblebee-switch, which i've attached.

Xorg..conf,nvidia: Section "DRI" Mode 0666 EndSection

Section "ServerLayout" Identifier "Layout0" Screen "Screen1" Option "AutoAddDevices" "false" EndSection

Section "Module" Load "dbe" Load "extmod" Load "glx" Load "record" Load "freetype" Load "type1" EndSection

Section "Files" EndSection

Section "Device" Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:01:00:0" Option "IgnoreEDID" Option "ConnectedMonitor" "REPLACEWITHCONNECTEDMONITOR" EndSection

Section "Screen" Identifier "Screen1" Device "Device1" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1920x1200" "1920x1080" "1680x1050" "1600x1200" "1440x900" "1280x1024" "1366x768" "1360x768" "1280x800" "1024x768" "800x600" "640x480" EndSubSection EndSection

Section "Extensions" Option "Composite" "Enable" EndSection

Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 73.0 VertRefresh 43.0 - 72.0 Option "DPMS" Modeline "1920x1200" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync Modeline "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync Modeline "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync Modeline "1600x1200" 161.00 1600 1712 1880 2160 1200 1203 1207 1245 -hsync +vsync Modeline "1440x900" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync Modeline "1366x768" 85.25 1368 1440 1576 1784 768 771 781 798 -hsync +vsync Modeline "1280x800" 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync EndSection

bumblebee-switch:

!/bin/sh

Power control for Thinkpad T420 by Erik Andresen

based on Power control for Asus 1215N Optimus by Pete Eberlein

if ! lsmod | grep -q acpi_call; then echo "Error: acpi_call module not loaded" exit fi

acpi_call () { echo "$*" > /proc/acpi/call cat /proc/acpi/call }

case "$1" in off) modprobe -r nvidia-current echo _DSM $(acpi_call "_SB.PCI0.PEG.VID._DSM" \ "{0xF8,0xD8,0x86,0xA4,0xDA,0x0B,0x1B,0x47," \ "0xA7,0x2B,0x60,0x42,0xA6,0xB5,0xBE,0xE0}" \ "0x100 0x1A {0x1,0x0,0x0,0x3}") echo _PS3 $(acpi_call "_SB.PCI0.PEG.VID._PS3") ;; on) echo _PS0 $(acpi_call "_SB.PCI0.PEG.VID._PS0") modprobe nvidia-current ;; *) echo "Usage: $0 [on|off]" esac

On Sat, Jul 9, 2011 at 2:50 PM, ArchangeGabriel < reply@reply.github.com>wrote:

Ok, can you upload both enable and disable scripts, the /etc/X11/xorg.conf.nvidia file and the Xorg log file corresponding to an attempt to run something via bumblebee.

An one more thing, which model are you using ? An UL30Vt ? Because I've just realized something for the original posters: the Asus UL30Vt isn't an Optimus laptop, so maybe it has something to do with that...

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

[ArchangeGabriel]

Ok, you've got a triple problem...

First, you're switch script is a not the good one... We will fix that together, but for now, we have an other problem to solve.

In the /etc/X11/xorg.conf.nvidia, replace REPLACEWITHCONNECTEDMONITOR by CRT-0. If it works, perfect. Else, try DFP-0 instead.

For the script, please do the followings : sudo apt-get install acpidump iasl mkdir ~/acpiinfo ; cd ~/acpiinfo sudo acpidump > acpidump.txt sudo acpixtract acpidump.txt ls *.dat | while read i; do iasl -d "${i}"; done && name=sudo dmidecode -s system-product-name` mkdir "${name}" && cp *.dsl "${name}"/ && tar czf "${name}.tar.gz" "${name}"/ && ls -l "$( pwd )/${name}".tar.gz`

And upload the .tar.gz

[Hoverbear]

Here's the TAR http://ompldr.org/iOWY4YQ

The xorg conf modification worked, seems like the config script never set it.

[ArchangeGabriel]

Yes, this is an actual critical bug, which is responsible of a lots of others.

[Hoverbear]

Makes sense.

On Sat, Jul 9, 2011 at 4:05 PM, ArchangeGabriel < reply@reply.github.com>wrote:

Yes, this is an actual critical bug, which is responsible of a lots of others.

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

[MrMEEE]

ok.. this was a bug introduced by the new configuration script.. this is now fixed in both git and ppa..

Please update...

[Hoverbear]

Thanks so much!

On Sun, Jul 10, 2011 at 9:32 AM, MrMEEE < reply@reply.github.com>wrote:

ok.. this was a bug introduced by the new configuration script.. this is now fixed in both git and ppa..

Please update...

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

[weiliddat]

Hi MrMEEE, I've gotten back my laptop. I think it's not the most suitable for Bumblebee since it's a UL30Vt, and it's switchable graphics, not Optimus. So is it still supported, or should I find another alternative?

[weiliddat]

I've uploaded my bugreport tar file here: http://www.mediafire.com/?33ywt4wnibhwtzu Hopefully it helps. I'm a newbie to linux and stuff so I've no idea what to debug in the scripts. ><

[MrMEEE]

Hi..

Try changing line 29 in /etc/X11/xorg.conf:

Option "ConnectedMonitor" "CRT-0"

to

Option "ConnectedMonitor" "DFP-0"

and try again..

send me /var/log/Xorg.1.log if it doesn't work...

[MrMEEE]

Please also open a new issue...