| Summary: | KWin crashed after nvidia driver installed | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | progopis |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
progopis
2011-06-30 21:46:32 UTC
This is a crash in the intel driver. The nvidia driver is NOT in use here. The intel bug is not related to the nvidia GPU and can be worked around by omitting fullscreen window unredirection (see dupe). To enforce the nvidia driver consult "man xorg.conf" or use the nvidia shellscript to generate a valid X11 configuration. Afaik "Optimus" is NOT supported on Linux. *** This bug has been marked as a duplicate of bug 252817 *** >Afaik "Optimus" is NOT supported on Linux.
Ok, sir. But where did you seen in my message, that "Optimus" is turned on? NVIDIA has no own engine for output. NVIDIA chip works with Intel together, because NVIDIA is just works as accelerator for Intel (special mobile version with 'M' letter in the name of model). My current configuration is not Optimus, because it is based on a dynamic switching video cores, depending on conditions, while I have both cores are working all the time. I tried run desktop effects on Intel hardware without NVIDIA and it ended in failure. I installed 'bumblebee' special package and desktop effects will turn on automatically.
Also, it's not possible for xorg switch video device by configuring xorg.conf. X server can not switch between graphics cards with Optimus scheme. Just look here:
xorg.conf:
...
Section "Device"
Identifier "Device0"
Driver "intel"
VendorName "Intel GMA 3150"
BusID "PCI:0:2:0"
EndSection
...
This is the only section 'Device' in my xorg.conf. Nothing about NVIDIA (but you can not just replace the parameters BusID and Driver, as well as set IsolateDevice to enable NVIDIA). Now look here:
lsmod | grep -i -P "nv|i915"
nvidia 10718100 0
i915 514985 5
drm_kms_helper 42136 1 i915
drm 227495 6 i915,drm_kms_helper
i2c_algo_bit 13400 1 i915
video 19438 1 i915
Both drivers loaded and works. Unfortunately this is a "hack", so that even the nvidia-config "thinks" that the NVIDIA driver is not used. Also I will try '/usr/local/bin/bumblebee-disablecard' script and report if it becomes known anything else.
(In reply to comment #2) > Ok, sir. But where did you seen in my message, that "Optimus" is turned on? Nowhere, was just a general comment that such attempts likely won't work (the naive way). I'm not exactly sure how the bumblebee thing will work (pipe the nvidia output through the intel framebuffer *shrug*) but it ships a script to run applications accelerated which will likely preload the proper GL libraby. So you must use "optirun kwin --replace &" in order to use the nvidia gpu in this context at all. However, if you intend to use the window manager on top of the nvidia GPU, there's really no point in keeping the intel chip in use (in case the nvidia chip has access to some video out adapter) so you'd likely just want to configure a device for the nvidia chip, connect it to one or the screen for your server and you're done. Some misconceptions: ---------- > Both drivers loaded and works. No, both kernel modules are loaded, that's not the same, nor a big deal (since they operate on different HW - show me an lsmod with nouveau and nvidia and i'm impressed ;-) It has NO implications on the X11 server nor on the used (default) OpenGL librabry. The kernel module resides in /lib/modules/2.6.39-ARCH/kernel/drivers/video/ and the xorg "driver" in /usr/lib/xorg/modules/drivers/ Despite the nvidia kernel module is merely a wrapper around the prop. driver, they are NOT THE SAME. > nvidia-config "thinks" that the NVIDIA driver is not used. Because it is not. That is no misassumption on the SW side. Your GL lib probably links to the mesa variant which would not work with the nvidia driver even if that was configured to be used. Just the fact that the kernel module is loaded means absolutely nothing in this regard. |