Bug 75199 - [NVD7] unsupported GT620M in Samsung All-in-One PC DP500A2D
Summary: [NVD7] unsupported GT620M in Samsung All-in-One PC DP500A2D
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-19 11:24 UTC by slappinjohn
Modified: 2014-02-19 18:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kernel log (84.90 KB, text/plain)
2014-02-19 11:24 UTC, slappinjohn
no flags Details

Description slappinjohn 2014-02-19 11:24:53 UTC
Created attachment 94345 [details]
kernel log

I thought normally the Optimus Card in the Samsung All-in-One-PC should work, but neither the nvidia-331 or the latest nouveau-driver in ubuntu 13.10 seems to recognize the device correctly.
 
here some information (kernel-log attached):
 
lspci -vvxxx:
 
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev a1)
    Subsystem: Samsung Electronics Co Ltd GeForce GT 620M
    Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 16
    Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
    Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
    Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M]
    Region 5: I/O ports at e000 [size=128]
    Expansion ROM at f7000000 [disabled] [size=512K]
    Capabilities: <access denied>
00: de 10 40 11 03 00 10 00 a1 00 02 03 10 00 00 00
10: 00 00 00 01 0c 00 00 f0 00 00 00 00 0c 00 00 4c
20: 00 00 00 00 01 ff 4d 14 00 00 00 00 4d 14 92 b0
30: 00 00 00 f7 60 00 00 00 00 00 00 00 ff 01 00 00
 
 
bumblebee:
 
optirun -vv glxheads
[20512.200644] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[20512.201004] [INFO]Configured driver: nouveau
[20512.201181] [DEBUG]optirun version 3.2.1 starting...
[20512.201194] [DEBUG]Active configuration:
[20512.201200] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[20512.201205] [DEBUG] X display: :8
[20512.201210] [DEBUG] LD_LIBRARY_PATH:
[20512.201215] [DEBUG] Socket path: /var/run/bumblebee.socket
[20512.201220] [DEBUG] Accel/display bridge: auto
[20512.201224] [DEBUG] VGL Compression: proxy
[20512.201229] [DEBUG] VGLrun extra options:
[20512.201234] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
[20512.201267] [DEBUG]Using auto-detected bridge virtualgl
[20512.435068] [INFO]Response: No - error: [XORG] (EE) [drm] KMS not enabled
[20512.435091] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] KMS not enabled
[20512.435098] [DEBUG]Socket closed.
[20512.435121] [ERROR]Aborting because fallback start is disabled.
[20512.435131] [DEBUG]Killing all remaining processes.


Versions:

xserver-xorg-video-nouveau 1:1.0.9+git2
xorg 7.7+1ubuntu6
libdrm-nouveau2 2.4.52+git2014
libmesa 10.2.0~git2014
kernel 3.11.0.17.18
Comment 1 Emil Velikov 2014-02-19 15:01:05 UTC
Seems like bbswitch is not powering the card properly.

I would recommend removing bbswitch and using the kernel's dynamic power management (iirc it landed in 3.12). The latter should power off the nvidia card when not in use and bring it back up if you run DRI_PRIME=1 glxgears
Comment 2 slappinjohn 2014-02-19 18:38:04 UTC
this seems to fix it, even so it still shows only the intel card in glxheads, but the framerate shows the working 3d capabilities. Thanks.
Comment 3 Ilia Mirkin 2014-02-19 18:41:12 UTC
Running stuff with DRI_PRIME=1 should cause it to use the nvidia card (e.g. DRI_PRIME=1 glxinfo). However that will only work once you've set up offloading. Take a look at http://nouveau.freedesktop.org/wiki/Optimus/. (Not sure what glxheads is... glxinfo is pretty authoritative though.)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.