| View previous topic :: View next topic |
| Author |
Message |
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
 Posted: Sun Dec 14, 2014 6:37 am Post subject: Linux optimus support, question for owners. |
 |
|
I am looking at a laptop that has it, just wondering how well it works from those who have it.
I know i have to get used to launching programs a bit differently with it. |
|
| Back to top |
|
 |
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Mon Dec 15, 2014 12:35 am Post subject: |
|
|
Wow really? no one?
I know there are some people who are able to run it. I have looked at all the wiki stuff and the previous forum posts.
But no one wants to tell me their experiences with it? |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Mon Dec 15, 2014 11:54 am Post subject: |
|
|
I've got a dell E6540 with a Radeon HD 8790M. Didn't bother to try and configure it. I just use the built-in Intel graphics. Works like a charm  |
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Mon Dec 15, 2014 1:39 pm Post subject: |
|
|
I use bumblebee on my Asus N56VV laptop. I only use the nvidia card for gaming. I have to edit the game launch options in Steam to "primusrun %command%", or launch the game from a terminal with primusrun. I had no problems setting up bumblebee. Performance is great, I can stream games with Steam from my more powerful optimus laptop to my slower laptop.
There is only one downside: programs launched with nvidia card crash when I return from suspend.
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Tue Dec 16, 2014 3:38 am Post subject: |
|
|
| dweezil-n0xad wrote: | I use bumblebee on my Asus N56VV laptop. I only use the nvidia card for gaming. I have to edit the game launch options in Steam to "primusrun %command%", or launch the game from a terminal with primusrun. I had no problems setting up bumblebee. Performance is great, I can stream games with Steam from my more powerful optimus laptop to my slower laptop.
There is only one downside: programs launched with nvidia card crash when I return from suspend. |
Thats good to hear.
Been kind of finding contradicting information.
So i need to install both the intel and nvidia drivers? |
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Tue Dec 16, 2014 6:07 am Post subject: |
|
|
yes, this is in my /etc/portage/make.conf:
| Code: | | VIDEO_CARDS="nvidia intel i965" |
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
grot
n00b
Joined: 17 Dec 2014
Posts: 33
|
| Posted: Thu Dec 18, 2014 12:18 am Post subject: |
|
|
Bumblebee works great for me on Arch in various wm's. I use the proprietary nvidia drivers. Performance seems to be better on linux for linux-native games than on windows, such as Dead Island - the random windows lag spikes seem to be more of background processing tasks than video lag, although they cause video lag. Also, multiple monitors don't seem to have a staggeringly negative impact like they do on windows, and not having to alt+tab is incredibly convenient.
Overall I'm really incredibly impressed with the project.
My biggest gripe is that switching X servers sometimes crashes my games. I'm curious if this will be the same after I get my -systemd -dbus install fully operational. IIRC, something with systemd is what makes bumblebeed crash during boot.
Bumblebeed has a command that lists how many programs are connected, which is a quick way to know if it's working.
for most programs: optirun or primusrun 'executable'. you might have seen it, but primusrun is generally regarded as faster for nvidia - which is true for me as well
optirun/primusrun vlc
optirun/primusrun wine game.exe
Playonlinux:
There's some random sort of registry setting you have to change... it was really a pain to find.. then you set primusrun/optirun as an argument, and launch as usual
edit: it doesn't crash the game - it freezes the entire system. I suspect I could ssh in to try and fix it, but I haven't tried yet and have just recently obtained a second computer |
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Thu Dec 18, 2014 2:29 pm Post subject: |
|
|
| grot wrote: | | optirun/primusrun vlc |
I don't use the nvidia card for video playback. I use smplayer + mpv to play video with the intel card. I can use xv video output or vaapi video output but I don't notice any difference in cpu usage on my i7. There is screen tearing with the vaapi output unless I use compton as X compositor.
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Sat Dec 20, 2014 7:52 am Post subject: |
|
|
If you use bumblebee you do not need to set up native nvidia optimus support in X. X will be started with the intel drivers.
I do not need a xorg.conf and only have this file in /etc/X11/xorg.conf.d
10-evdev.conf
| Code: | Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "synaptics-all"
Driver "synaptics"
Option "TapButton1" "1"
Option "VertEdgeScroll" "1"
MatchIsTouchpad "on"
EndSection |
The nvidia configuration is in /etc/bumblebe/xorg.conf.nvidia
| Code: | Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
Option "AutoAddGPU" "false"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "ProbeAllGpus" "false"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "UseDisplayDevice" "none"
EndSection |
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Sat Dec 20, 2014 10:17 pm Post subject: |
|
|
| dweezil-n0xad wrote: | If you use bumblebee you do not need to set up native nvidia optimus support in X. X will be started with the intel drivers.
I do not need a xorg.conf and only have this file in /etc/X11/xorg.conf.d
10-evdev.conf
| Code: | Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "synaptics-all"
Driver "synaptics"
Option "TapButton1" "1"
Option "VertEdgeScroll" "1"
MatchIsTouchpad "on"
EndSection |
The nvidia configuration is in /etc/bumblebe/xorg.conf.nvidia
| Code: | Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
Option "AutoAddGPU" "false"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "ProbeAllGpus" "false"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "UseDisplayDevice" "none"
EndSection |
|
i tried it like that and all i get is a blank screen taking over the already loaded xsession. |
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Sun Dec 21, 2014 11:22 am Post subject: |
|
|
Before you try to set up the nvidia card, make sure that the intel driver is working. http://wiki.gentoo.org/wiki/Intel
Please post your /var/log/Xorg.0.log file if you can't start X.
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Sun Dec 21, 2014 5:01 pm Post subject: |
|
|
| dweezil-n0xad wrote: | Before you try to set up the nvidia card, make sure that the intel driver is working. http://wiki.gentoo.org/wiki/Intel
Please post your /var/log/Xorg.0.log file if you can't start X. |
I solved it myself, did not realize bbswitch was a kernel module, lol. loaded it, made sure the nvidia kernel module did not load at boot but was loaded and unloaded by bumblebee and it worked!
the only thing is it spams dmesg with this.
| Code: | [ 123.963127] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1357.117242] i2c /dev entries driver
[ 1365.422642] [drm] GMBUS [i915 gmbus ssc] timed out, falling back to bit banging on pin 1
[ 1368.673265] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
[ 1370.435688] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3
[ 1375.240567] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
[ 2205.652966] nvidia: module license 'NVIDIA' taints kernel.
[ 2205.652969] Disabling lock debugging due to kernel taint
[ 2205.693541] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:03:00.0 on minor 1
[ 2205.693548] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 343.36 Mon Dec 1 16:18:58 PST 2014
[ 2205.694113] ------------[ cut here ]------------
[ 2205.694121] WARNING: CPU: 2 PID: 2373 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190()
[ 2205.694168] No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm_dev_set_unique() to set the
unique name explicitly.
[ 2205.694181] Modules linked in:
[ 2205.694183] nvidia(PO) bbswitch(O) b43 ssb bcma x86_pkg_temp_thermal coretemp xhci_pci xhci_hcd efivarfs [last unloaded: i2c_dev]
[ 2205.694194] CPU: 2 PID: 2373 Comm: X Tainted: P O 3.18.1-gentoo #8
[ 2205.694197] Hardware name: Acer Aspire V3-572G/EA50_HB , BIOS V1.08 06/20/2014
[ 2205.694199] 0000000000000009 ffff880254773cc8 ffffffff81ad82c0 0000000000000001
[ 2205.694204] ffff880254773d18 ffff880254773d08 ffffffff8104c92c ffff880254773d78
[ 2205.694207] ffff880254773df8 ffff88024ba6c000 ffff880098571d80 ffff88024ba6c000
[ 2205.694209] Call Trace:
[ 2205.694215] [<ffffffff81ad82c0>] dump_stack+0x4f/0x7c
[ 2205.694218] [<ffffffff8104c92c>] warn_slowpath_common+0x7c/0xa0
[ 2205.694221] [<ffffffff8104c991>] warn_slowpath_fmt+0x41/0x50
[ 2205.694224] [<ffffffff8163f71e>] drm_setversion+0x17e/0x190
[ 2205.694227] [<ffffffff8117223b>] ? path_openat+0xab/0x600
[ 2205.694230] [<ffffffff8163f15c>] drm_ioctl+0x2dc/0x630
[ 2205.694232] [<ffffffff8163f5a0>] ? drm_noop+0x30/0x30
[ 2205.694235] [<ffffffff81175c30>] do_vfs_ioctl+0x2e0/0x4c0
[ 2205.694238] [<ffffffff8117f9cd>] ? __fget+0x6d/0xa0
[ 2205.694240] [<ffffffff81175e91>] SyS_ioctl+0x81/0xa0
[ 2205.694243] [<ffffffff81ae2345>] ? int_check_syscall_exit_work+0x34/0x3d
[ 2205.694246] [<ffffffff81ae2116>] system_call_fastpath+0x16/0x1b
[ 2205.694248] ---[ end trace bc9b354a9adcc78b ]---
[ 2205.765450] nvidia 0000:03:00.0: irq 49 for MSI/MSI-X
[ 2205.767854] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767888] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767904] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767931] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767947] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767962] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.767997] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2205.768013] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[ 2206.052217] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
|
|
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Mon Dec 22, 2014 9:59 am Post subject: |
|
|
I checked my dmesg and found the same trace! I never noticed that before. I searched the nvidia forums: https://devtalk.nvidia.com/default/topic/796559/kernel-3-18-warning-no-drm_driver-set_busid-implementation-provided-by-nvidia_frontend_exit_modu/
drop this patch in /etc/portage/patches/x11-drivers/nvidia-drivers/ until the next driver update
| Code: | --- kernel/nv-drm.c~ 2014-11-08 00:57:53.000000000 +0100
+++ kernel/nv-drm.c 2014-11-13 21:03:37.589650873 +0100
@@ -128,6 +128,10 @@ static struct drm_driver nv_drm_driver =
.gem_prime_vmap = nv_gem_prime_vmap,
.gem_prime_vunmap = nv_gem_prime_vunmap,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 18, 0)
+ .set_busid = drm_pci_set_busid,
+#endif
+
.name = "nvidia-drm",
.desc = "NVIDIA DRM driver",
.date = "20130102",
diff --git a/nv-frontend.c~ b/nv-frontend.c
index c8c8af1..00f0973 100644
--- kernel/nv-frontend.c~
+++ kernel/nv-frontend.c
@@ -327,7 +327,7 @@ long nvidia_frontend_unlocked_ioctl(
unsigned long i_arg
)
{
- return nvidia_frontend_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_frontend_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
long nvidia_frontend_compat_ioctl(
@@ -336,7 +336,7 @@ long nvidia_frontend_compat_ioctl(
unsigned long i_arg
)
{
- return nvidia_frontend_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_frontend_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
int nvidia_frontend_mmap(
diff --git a/nv.c~ b/nv.c
index 6b31000..3db114e 100644
--- kernel/nv.c~
+++ kernel/nv.c
@@ -1796,7 +1796,7 @@ nvidia_unlocked_ioctl(
unsigned long i_arg
)
{
- return nvidia_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
/* |
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Tue Dec 23, 2014 4:24 am Post subject: |
|
|
| dweezil-n0xad wrote: | I checked my dmesg and found the same trace! I never noticed that before. I searched the nvidia forums: https://devtalk.nvidia.com/default/topic/796559/kernel-3-18-warning-no-drm_driver-set_busid-implementation-provided-by-nvidia_frontend_exit_modu/
drop this patch in /etc/portage/patches/x11-drivers/nvidia-drivers/ until the next driver update
| Code: | --- kernel/nv-drm.c~ 2014-11-08 00:57:53.000000000 +0100
+++ kernel/nv-drm.c 2014-11-13 21:03:37.589650873 +0100
@@ -128,6 +128,10 @@ static struct drm_driver nv_drm_driver =
.gem_prime_vmap = nv_gem_prime_vmap,
.gem_prime_vunmap = nv_gem_prime_vunmap,
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 18, 0)
+ .set_busid = drm_pci_set_busid,
+#endif
+
.name = "nvidia-drm",
.desc = "NVIDIA DRM driver",
.date = "20130102",
diff --git a/nv-frontend.c~ b/nv-frontend.c
index c8c8af1..00f0973 100644
--- kernel/nv-frontend.c~
+++ kernel/nv-frontend.c
@@ -327,7 +327,7 @@ long nvidia_frontend_unlocked_ioctl(
unsigned long i_arg
)
{
- return nvidia_frontend_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_frontend_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
long nvidia_frontend_compat_ioctl(
@@ -336,7 +336,7 @@ long nvidia_frontend_compat_ioctl(
unsigned long i_arg
)
{
- return nvidia_frontend_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_frontend_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
int nvidia_frontend_mmap(
diff --git a/nv.c~ b/nv.c
index 6b31000..3db114e 100644
--- kernel/nv.c~
+++ kernel/nv.c
@@ -1796,7 +1796,7 @@ nvidia_unlocked_ioctl(
unsigned long i_arg
)
{
- return nvidia_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+ return nvidia_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);
}
/* |
|
I will just wait till the next driver update. The ebuild barfs and complains about the patch if I try to apply it by putting it in that dir. |
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Tue Dec 23, 2014 10:54 am Post subject: |
|
|
the posted patch applies cleanly here with nvidia-drivers-346.22
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Tue Dec 23, 2014 12:31 pm Post subject: |
|
|
| dweezil-n0xad wrote: | | the posted patch applies cleanly here with nvidia-drivers-346.22 |
Oh theres the problem. I have 343.36 installed. 
Will fix it tonight, not enough time this morning before work. |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Wed Dec 24, 2014 2:18 am Post subject: |
|
|
nope. no luck. Still doesn't apply.
| Code: |
Calculating dependencies... done!
[ebuild U ~] x11-drivers/nvidia-drivers-346.22 [343.36] USE="X acpi gtk2%* gtk3%* multilib tools -pax_kernel -uvm" 0 KiB
Total: 1 package (1 upgrade), Size of downloads: 0 KiB
>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-drivers/nvidia-drivers-346.22
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/3.18.1-gentoo/build
* Found sources for kernel version:
* 3.18.1-gentoo
* Gentoo supports kernels which are supported by NVIDIA
* which are limited to the following kernels:
* <sys-kernel/gentoo-sources-3.18
* <sys-kernel/vanilla-sources-3.18
*
* You are free to utilize epatch_user to provide whatever
* support you feel is appropriate, but will not receive
* support as a result of those changes.
*
* Do not file a bug report about this.
* Checking for suitable kernel configuration options... [ ok ]
>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-346.22::gentoo
* NVIDIA-Linux-x86_64-346.22.run SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/3.18.1-gentoo/build
* Found sources for kernel version:
* 3.18.1-gentoo
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-346.22.run to /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work
>>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work ...
* Applying user patches from /etc/portage/patches//x11-drivers/nvidia-drivers ...
* kernel-3-18-1-warning.patch ...
* Failed Patch: kernel-3-18-1-warning.patch !
* ( /etc/portage/patches//x11-drivers/nvidia-drivers/kernel-3-18-1-warning.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/kernel-3-18-1-warning.patch.out
* ERROR: x11-drivers/nvidia-drivers-346.22::gentoo failed (prepare phase):
* Failed Patch: kernel-3-18-1-warning.patch!
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 4414: Called epatch_user
* environment, line 1709: Called epatch
* environment, line 1682: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
*
* If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-346.22::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-346.22::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/environment'.
* Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work/'
>>> Failed to emerge x11-drivers/nvidia-drivers-346.22, Log file:
>>> '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/build.log'
* Messages for package x11-drivers/nvidia-drivers-346.22:
* Gentoo supports kernels which are supported by NVIDIA
* which are limited to the following kernels:
* <sys-kernel/gentoo-sources-3.18
* <sys-kernel/vanilla-sources-3.18
*
* You are free to utilize epatch_user to provide whatever
* support you feel is appropriate, but will not receive
* support as a result of those changes.
*
* Do not file a bug report about this.
* Messages for package x11-drivers/nvidia-drivers-346.22:
* Failed Patch: kernel-3-18-1-warning.patch !
* ( /etc/portage/patches//x11-drivers/nvidia-drivers/kernel-3-18-1-warning.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/kernel-3-18-1-warning.patch.out
* ERROR: x11-drivers/nvidia-drivers-346.22::gentoo failed (prepare phase):
* Failed Patch: kernel-3-18-1-warning.patch!
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 4414: Called epatch_user
* environment, line 1709: Called epatch
* environment, line 1682: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
*
* If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-346.22::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-346.22::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/temp/environment'.
* Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work/'
|
|
|
| Back to top |
|
|
dweezil-n0xad
Apprentice
Joined: 30 Oct 2006
Posts: 156
Location: Ostend, Belgium
|
| Posted: Wed Dec 24, 2014 10:27 am Post subject: |
|
|
strange, it works on my machine™
| Code: | # cd /etc/portage/patches/x11-drivers/nvidia-drivers/
# wget https://raw.githubusercontent.com/painless/dweezil/master/x11-drivers/nvidia-drivers/files/kernel-3-18-warning.patch
# ls -l
total 4
-rw-r--r-- 1 root root 1467 Dec 24 10:47 kernel-3-18-warning.patch
# EMERGE_DEFAULT_OPTS="--quiet-build=n" emerge nvidia-drivers::gentoo -av
...
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work ...
* Applying user patches from /etc/portage/patches//x11-drivers/nvidia-drivers ...
* kernel-3-18-warning.patch ... [ ok ]
* Done with patching
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-346.22/work ...
... |
This still comes up in dmesg when I use nvidia card
| Code: | [36317.731690] bbswitch: enabling discrete graphics
[36318.150006] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
[36318.150015] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 346.22 Tue Dec 2 10:50:01 PST 2014
[36318.152273] nvidia 0000:01:00.0: irq 29 for MSI/MSI-X
[36318.154148] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154191] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154243] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154270] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154297] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154323] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154375] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36318.154401] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36319.294755] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36319.528113] vgaarb: this pci device is not a vga device
[36319.530027] vgaarb: this pci device is not a vga device
[36328.143788] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
[36328.150326] [drm] Module unloaded
[36328.151499] bbswitch: disabling discrete graphics |
_________________
i7-4790K | 16GB DDR3 | GTX 970 | 500GB SSD
ASUS N56VV | i7-3630QM | 12GB DDR3 | GT 750M | 256GB SSD |
|
| Back to top |
|
|
Atmmac
Tux's lil' helper
Joined: 17 Oct 2013
Posts: 130
Location: Watertown, MA
|
| Posted: Fri Dec 26, 2014 8:44 pm Post subject: |
|
|
| I have been getting those mismatch errors since I set up my Optimus laptop in August. Never had a problem. Bumblebee works excellent and is a great project. |
|
| Back to top |
|
|
truekaiser
l33t
Joined: 05 Mar 2004
Posts: 810
|
| Posted: Sun Dec 28, 2014 7:48 pm Post subject: |
|
|
| Atmmac wrote: | | I have been getting those mismatch errors since I set up my Optimus laptop in August. Never had a problem. Bumblebee works excellent and is a great project. |
Yea it works well despite the errors. |
|
| Back to top |
|
|
Yamakuzure
Advocate
Joined: 21 Jun 2006
Posts: 2310
Location: Adendorf, Germany
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo Chat
