Announcement

Collapse
No announcement yet.

AMDGPU-PRO 16.50 Rolls Out With GCN 1.0 Support, FreeSync

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    bridgman Do you know if the new libdrm that supports SI cards is called "libdrm-amdgpu-pro-radeon1"?

    Comment


    • #32
      Originally posted by mick3 View Post
      Tried to install amdgpu-pro 16.50 in Ubuntu 16.04 using the default 4.4.x kernel. DKMS module building and installation went fine, same with reboot & startup. As soon I wanted to login amdgpu gave me kernel panic. I have a GCN 1.2 Iceland/Topaz chip in my laptop. Does amdgpu-pro not support everything VI?
      Actually, if you look at supported products by amdgpu-pro driver, they don't actually advertise APUs as supported at all... i guess that is because some other company sell those

      edit: ah sorry you are asking about PX there, maybe depend on combo if it is intel or amd cpu... but AMD is known to not writing documantation So maybe you should use modesetting ddx and not amdgpu when PX setup is there or something.
      Last edited by dungeon; 08 December 2016, 06:52 PM.

      Comment


      • #33
        Originally posted by clintar View Post
        Yeah, not seeing it on their site. I see some info if you click on the 400 series, but not download link. Nothing for the GCN 1.0 older series.
        Use the link I posted further up or follow directions below. No matter what you click on you end up at that link anyways.

        I see a lot of GCN 1.0 parts. Title of the page should be "Linux Download Center" unless something is going wacky in the "route to a different server depending on where you are" site logic.

        Failing that, go to amd.com, click on "Get Drivers", then click on any of the first four "Linux" links. If you go down too far you'll end up getting legacy drivers.

        Comment


        • #34
          Originally posted by dungeon View Post
          edit: ah sorry you are asking about PX there, maybe depend on combo if it is intel or amd cpu... but AMD is known to not writing documantation So maybe you should use modesetting ddx and not amdgpu when PX setup is there or something.
          Modesetting works fine with the previous amdgpu.

          But you're right, my model (R7 M360) is not listed in the release notes at http://support.amd.com/en-us/kb-arti...ase-Notes.aspx .

          R7 M350/M380 are now supported although they're only GCN 1.0/1.1 .

          Also the complete R7 M400 series is supported which should contain at least some Iceland chips (M440/460?).

          What hell of AMD marketing department came up with this highly confusing naming scheme with different GCN generations in the same series?
          Last edited by mick3; 08 December 2016, 08:44 PM.

          Comment


          • #35
            They just don't write proper docs, what is advertised and what you get in reality greatly differ. Whatever marketing names are used and they write there, people with any of the following GPU names can try it (basically all GCNs)

            BONAIRE, CARRIZO, FIJI, HAINAN, HAWAII, KABINI, KAVERI, MULLINS, OLAND, PITCAIRN, POLARIS10, POLARIS11, STONEY, TAHITI, TONGA, TOPAZ and VERDE
            Of course depending on the setup, on many it should just work or some might just not by default... or even at all, in case of some bug

            Comment


            • #36
              Originally posted by mick3 View Post
              Tried to install amdgpu-pro 16.50 in Ubuntu 16.04 using the default 4.4.x kernel. DKMS module building and installation went fine, same with reboot & startup. As soon I wanted to login amdgpu gave me kernel panic. I have a GCN 1.2 Iceland/Topaz chip in my laptop. Does amdgpu-pro not support everything VI?
              Currently, the open stack offers a better user experience for hybrid graphics because APU and dGPU share the same GL implementation (Mesa). PX support in the pro stack requires you to logout when switching between power saving and performance modes whereas the open stack supports DRI PRIME GPU offloading so you can use the dGPU only when you need it. Recently, we've pushed a lot of fixes upstream for hybrid graphics. An easy way to get these is to use only the dkms package from the pro stack, with all other graphics components from Ubuntu. Some laptops also require an upgraded DDX (xserver-xorg-video-amdgpu, 1.2.0 recommended). Having said that, PX systems tend to have a lot of quirks so unless we've tested your specific model, YMMV.

              Comment


              • #37
                dungeon Where did you get this information? I was wanting to try this driver in Ubuntu, and I have a pitcairn card but it's not listed (R9 270X).

                Comment


                • #38
                  Crashes on my Kaveri:
                  Code:
                  Dec  9 12:45:56 ubuntu kernel: [    3.362218] [drm] amdgpu kernel modesetting enabled.
                  Dec  9 12:45:56 ubuntu kernel: [    3.371681] AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
                  Dec  9 12:45:56 ubuntu kernel: [    3.374828] AMD IOMMUv2 functionality not available on this system
                  Dec  9 12:45:56 ubuntu kernel: [    3.386300] CRAT table not found
                  Dec  9 12:45:56 ubuntu kernel: [    3.389294] Finished initializing topology ret=0
                  Dec  9 12:45:56 ubuntu kernel: [    3.392369] kfd kfd: Initialized module
                  Dec  9 12:45:56 ubuntu kernel: [    3.395984] checking generic (e0000000 7f0000) vs hw (e0000000 10000000)
                  Dec  9 12:45:56 ubuntu kernel: [    3.395994] fb: switching to amdgpudrmfb from EFI VGA
                  Dec  9 12:45:56 ubuntu kernel: [    3.399012] Console: switching to colour dummy device 80x25
                  Dec  9 12:45:56 ubuntu kernel: [    3.400891] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x5111 0x00).
                  Dec  9 12:45:56 ubuntu kernel: [    3.400946] [drm] register mmio base: 0xF0B00000
                  Dec  9 12:45:56 ubuntu kernel: [    3.400957] [drm] register mmio size: 262144
                  Dec  9 12:45:56 ubuntu kernel: [    3.400977] [drm] doorbell mmio base: 0xF0000000
                  Dec  9 12:45:56 ubuntu kernel: [    3.400986] [drm] doorbell mmio size: 8388608
                  Dec  9 12:45:56 ubuntu kernel: [    3.401025] [drm] ACPI VFCT contains a BIOS for 00:01.0 1002:130a, size 62976
                  Dec  9 12:45:56 ubuntu kernel: [    3.401077] ATOM BIOS: 113
                  Dec  9 12:45:56 ubuntu kernel: [    3.401106] [drm] GPU post is not needed
                  Dec  9 12:45:56 ubuntu kernel: [    3.401116] [drm] Changing default dispclk from 514Mhz to 600Mhz
                  Dec  9 12:45:56 ubuntu kernel: [    3.402266] amdgpu 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
                  Dec  9 12:45:56 ubuntu kernel: [    3.402285] amdgpu 0000:00:01.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
                  Dec  9 12:45:56 ubuntu kernel: [    3.402301] [drm] Detected VRAM RAM=1024M, BAR=256M
                  Dec  9 12:45:56 ubuntu kernel: [    3.402310] [drm] RAM width 128bits UNKNOWN
                  Dec  9 12:45:56 ubuntu kernel: [    3.402503] [TTM] Zone  kernel: Available graphics memory: 3546914 kiB
                  Dec  9 12:45:56 ubuntu kernel: [    3.402514] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
                  Dec  9 12:45:56 ubuntu kernel: [    3.402524] [TTM] Initializing pool allocator
                  Dec  9 12:45:56 ubuntu kernel: [    3.402542] [TTM] Initializing DMA pool allocator
                  Dec  9 12:45:56 ubuntu kernel: [    3.402602] [drm] amdgpu: 1024M of VRAM memory ready
                  Dec  9 12:45:56 ubuntu kernel: [    3.402615] [drm] amdgpu: 1024M of GTT memory ready.
                  Dec  9 12:45:56 ubuntu kernel: [    3.402657] [drm] GART: num cpu pages 262144, num gpu pages 262144
                  Dec  9 12:45:56 ubuntu kernel: [    3.503153] [drm] PCIE GART of 1024M enabled (table at 0x0000000000040000).
                  Dec  9 12:45:56 ubuntu kernel: [    3.503365] amdgpu 0000:00:01.0: amdgpu: using MSI.
                  Dec  9 12:45:56 ubuntu kernel: [    3.503379] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
                  Dec  9 12:45:56 ubuntu kernel: [    3.503389] [drm] Driver supports precise vblank timestamp query.
                  Dec  9 12:45:56 ubuntu kernel: [    3.503446] [drm] amdgpu: irq initialized.
                  Dec  9 12:45:56 ubuntu kernel: [    3.503469] [drm] Internal thermal controller without fan control
                  Dec  9 12:45:56 ubuntu kernel: [    3.503480] [drm] amdgpu: dpm initialized
                  Dec  9 12:45:56 ubuntu kernel: [    3.507894] [drm] amdgpu atom DIG backlight initialized
                  Dec  9 12:45:56 ubuntu kernel: [    3.507913] [drm] AMDGPU Display Connectors
                  Dec  9 12:45:56 ubuntu kernel: [    3.507922] [drm] Connector 0:
                  Dec  9 12:45:56 ubuntu kernel: [    3.507930] [drm]   VGA-1
                  Dec  9 12:45:56 ubuntu kernel: [    3.507939] [drm]   HPD2
                  Dec  9 12:45:56 ubuntu kernel: [    3.507948] [drm]   DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953
                  Dec  9 12:45:56 ubuntu kernel: [    3.507962] [drm]   Encoders:
                  Dec  9 12:45:56 ubuntu kernel: [    3.507970] [drm]     CRT1: INTERNAL_UNIPHY2
                  Dec  9 12:45:56 ubuntu kernel: [    3.507978] [drm]     CRT1: NUTMEG
                  Dec  9 12:45:56 ubuntu kernel: [    3.507985] [drm] Connector 1:
                  Dec  9 12:45:56 ubuntu kernel: [    3.507993] [drm]   HDMI-A-1
                  Dec  9 12:45:56 ubuntu kernel: [    3.508000] [drm]   HPD3
                  Dec  9 12:45:56 ubuntu kernel: [    3.508028] [drm]   DDC: 0x1954 0x1954 0x1955 0x1955 0x1956 0x1956 0x1957 0x1957
                  Dec  9 12:45:56 ubuntu kernel: [    3.508042] [drm]   Encoders:
                  Dec  9 12:45:56 ubuntu kernel: [    3.508051] [drm]     DFP1: INTERNAL_UNIPHY2
                  Dec  9 12:45:56 ubuntu kernel: [    3.508059] [drm] Connector 2:
                  Dec  9 12:45:56 ubuntu kernel: [    3.508067] [drm]   eDP-1
                  Dec  9 12:45:56 ubuntu kernel: [    3.508075] [drm]   HPD1
                  Dec  9 12:45:56 ubuntu kernel: [    3.508084] [drm]   DDC: 0x194c 0x194c 0x194d 0x194d 0x194e 0x194e 0x194f 0x194f
                  Dec  9 12:45:56 ubuntu kernel: [    3.508097] [drm]   Encoders:
                  Dec  9 12:45:56 ubuntu kernel: [    3.508104] [drm]     LCD1: INTERNAL_UNIPHY
                  Dec  9 12:45:56 ubuntu kernel: [    3.508112] [drm] Connector 3:
                  Dec  9 12:45:56 ubuntu kernel: [    3.508120] [drm]   DP-1
                  Dec  9 12:45:56 ubuntu kernel: [    3.508127] [drm]   HPD4
                  Dec  9 12:45:56 ubuntu kernel: [    3.508135] [drm]   DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195b 0x195b
                  Dec  9 12:45:56 ubuntu kernel: [    3.508148] [drm]   Encoders:
                  Dec  9 12:45:56 ubuntu kernel: [    3.508155] [drm]     DFP2: INTERNAL_UNIPHY3
                  Dec  9 12:45:56 ubuntu kernel: [    3.508771] amdgpu 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000010, cpu addr 0xffff88003571c010
                  Dec  9 12:45:56 ubuntu kernel: [    3.508887] amdgpu 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000020, cpu addr 0xffff88003571c020
                  Dec  9 12:45:56 ubuntu kernel: [    3.508987] amdgpu 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000030, cpu addr 0xffff88003571c030
                  Dec  9 12:45:56 ubuntu kernel: [    3.509087] amdgpu 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000040, cpu addr 0xffff88003571c040
                  Dec  9 12:45:56 ubuntu kernel: [    3.509216] amdgpu 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000050, cpu addr 0xffff88003571c050
                  Dec  9 12:45:56 ubuntu kernel: [    3.509391] amdgpu 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000040000060, cpu addr 0xffff88003571c060
                  Dec  9 12:45:56 ubuntu kernel: [    3.509491] amdgpu 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000070, cpu addr 0xffff88003571c070
                  Dec  9 12:45:56 ubuntu kernel: [    3.509592] amdgpu 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000080, cpu addr 0xffff88003571c080
                  Dec  9 12:45:56 ubuntu kernel: [    3.509727] amdgpu 0000:00:01.0: fence driver on ring 8 use gpu addr 0x0000000040000090, cpu addr 0xffff88003571c090
                  Dec  9 12:45:56 ubuntu kernel: [    3.509958] amdgpu 0000:00:01.0: fence driver on ring 9 use gpu addr 0x00000000400000a0, cpu addr 0xffff88003571c0a0
                  Dec  9 12:45:56 ubuntu kernel: [    3.510057] amdgpu 0000:00:01.0: fence driver on ring 10 use gpu addr 0x00000000400000b0, cpu addr 0xffff88003571c0b0
                  Dec  9 12:45:56 ubuntu kernel: [    3.510335] [drm] Found UVD firmware Version: 1.64 Family ID: 9
                  Dec  9 12:45:56 ubuntu kernel: [    3.511028] amdgpu 0000:00:01.0: fence driver on ring 11 use gpu addr 0x000000000028cd30, cpu addr 0xffffc90001438d30
                  Dec  9 12:45:56 ubuntu kernel: [    3.511249] [drm] Found VCE firmware Version: 50.10 Binary ID: 2
                  Dec  9 12:45:56 ubuntu kernel: [    3.511475] amdgpu 0000:00:01.0: fence driver on ring 12 use gpu addr 0x00000000400000d0, cpu addr 0xffff88003571c0d0
                  Dec  9 12:45:56 ubuntu kernel: [    3.511602] amdgpu 0000:00:01.0: fence driver on ring 13 use gpu addr 0x00000000400000e0, cpu addr 0xffff88003571c0e0
                  Dec  9 12:45:56 ubuntu kernel: [    3.521233] [drm] ring test on 0 succeeded in 12 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521385] [drm] ring test on 1 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521422] [drm] ring test on 2 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521457] [drm] ring test on 3 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521507] [drm] ring test on 4 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521540] [drm] ring test on 5 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521573] [drm] ring test on 6 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521608] [drm] ring test on 7 succeeded in 3 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521640] [drm] ring test on 8 succeeded in 2 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521859] [drm] ring test on 9 succeeded in 5 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.521877] [drm] ring test on 10 succeeded in 5 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.567589] [drm] ring test on 11 succeeded in 1 usecs
                  Dec  9 12:45:56 ubuntu kernel: [    3.587471] [drm] UVD initialized successfully.
                  Dec  9 12:45:56 ubuntu kernel: [    3.702527] BUG: unable to handle kernel NULL pointer dereference at           (null)
                  Dec  9 12:45:56 ubuntu kernel: [    3.702546] IP: [<          (null)>]           (null)
                  Dec  9 12:45:56 ubuntu kernel: [    3.702558] PGD 0
                  Dec  9 12:45:56 ubuntu kernel: [    3.702567] Oops: 0010 [#1] SMP
                  Dec  9 12:45:56 ubuntu kernel: [    3.702580] Modules linked in: amdkfd amd_iommu_v2 rtsx_pci_sdmmc amdgpu(OE+) i2c_algo_bit ttm drm_kms_helper psmouse syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm r8169 rtsx_pci mii wmi video fjes
                  Dec  9 12:45:56 ubuntu kernel: [    3.702635] CPU: 3 PID: 144 Comm: systemd-udevd Tainted: G           OE   4.4.0-47-generic #68-Ubuntu
                  Dec  9 12:45:56 ubuntu kernel: [    3.702650] Hardware name: LENOVO 20DECTO1WW/20DECTO1WW, BIOS HTET47WW (1.19 ) 03/08/2016
                  Dec  9 12:45:56 ubuntu kernel: [    3.702666] task: ffff880211748000 ti: ffff880211750000 task.ti: ffff880211750000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702681] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
                  Dec  9 12:45:56 ubuntu kernel: [    3.702697] RSP: 0018:ffff880211753870  EFLAGS: 00010246
                  Dec  9 12:45:56 ubuntu kernel: [    3.702706] RAX: ffffffffc02c6780 RBX: ffff880210ee3928 RCX: ffff88021175387f
                  Dec  9 12:45:56 ubuntu kernel: [    3.702716] RDX: ffff880210c899f0 RSI: ffff880210c89a20 RDI: ffff880210ee0000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702726] RBP: ffff8802117538a8 R08: 0000000000000000 R09: 0000000000000005
                  Dec  9 12:45:56 ubuntu kernel: [    3.702736] R10: ffff880210ee3a58 R11: 0000000000000000 R12: ffff880210ee0000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702746] R13: 0000000000000004 R14: ffff880210c899f0 R15: 0000000000000018
                  Dec  9 12:45:56 ubuntu kernel: [    3.702757] FS:  00007f9c21f158c0(0000) GS:ffff88021ed80000(0000) knlGS:0000000000000000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702772] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
                  Dec  9 12:45:56 ubuntu kernel: [    3.702781] CR2: 0000000000000000 CR3: 0000000211723000 CR4: 00000000000406e0
                  Dec  9 12:45:56 ubuntu kernel: [    3.702791] Stack:
                  Dec  9 12:45:56 ubuntu kernel: [    3.702799]  ffffffffc01b4367 ffff880210ee0000 00000000f84bf3cb ffff880210ee0000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702817]  ffff880210ee3928 ffff880210ee0000 0000000000000000 ffff8802117538d0
                  Dec  9 12:45:56 ubuntu kernel: [    3.702834]  ffffffffc01b496f ffff880210ee0000 ffff880210ee6340 ffff880210ee0000
                  Dec  9 12:45:56 ubuntu kernel: [    3.702851] Call Trace:
                  Dec  9 12:45:56 ubuntu kernel: [    3.703033]  [<ffffffffc01b4367>] ? amdgpu_pm_compute_clocks+0x267/0x620 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703145]  [<ffffffffc01b496f>] amdgpu_dpm_enable_vce+0xaf/0xd0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703268]  [<ffffffffc0224cf5>] amdgpu_vce_ring_begin_use+0x65/0x80 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703378]  [<ffffffffc01ae1f7>] amdgpu_ring_alloc+0x47/0x80 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703500]  [<ffffffffc0225dae>] amdgpu_vce_ring_test_ring+0x2e/0x130 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703619]  [<ffffffffc01e737a>] vce_v2_0_hw_init+0x7a/0xa0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703717]  [<ffffffffc01950d1>] amdgpu_device_init+0xbf1/0x13f0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703734]  [<ffffffff811b364e>] ? kmalloc_order_trace+0x2e/0xe0
                  Dec  9 12:45:56 ubuntu kernel: [    3.703834]  [<ffffffffc0197c7b>] amdgpu_driver_load_kms+0x5b/0x1f0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703891]  [<ffffffffc00643d7>] drm_dev_register+0xa7/0xb0 [drm]
                  Dec  9 12:45:56 ubuntu kernel: [    3.703929]  [<ffffffffc0066a0d>] drm_get_pci_dev+0x8d/0x1e0 [drm]
                  Dec  9 12:45:56 ubuntu kernel: [    3.704034]  [<ffffffffc01924c6>] amdgpu_pci_probe+0xc6/0xf0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.704050]  [<ffffffff81445d55>] local_pci_probe+0x45/0xa0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704062]  [<ffffffff81447193>] pci_device_probe+0x103/0x150
                  Dec  9 12:45:56 ubuntu kernel: [    3.704078]  [<ffffffff81558c62>] driver_probe_device+0x222/0x4a0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704092]  [<ffffffff81558f64>] __driver_attach+0x84/0x90
                  Dec  9 12:45:56 ubuntu kernel: [    3.704104]  [<ffffffff81558ee0>] ? driver_probe_device+0x4a0/0x4a0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704117]  [<ffffffff8155688c>] bus_for_each_dev+0x6c/0xc0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704129]  [<ffffffff8155841e>] driver_attach+0x1e/0x20
                  Dec  9 12:45:56 ubuntu kernel: [    3.704141]  [<ffffffff81557f5b>] bus_add_driver+0x1eb/0x280
                  Dec  9 12:45:56 ubuntu kernel: [    3.704154]  [<ffffffff81559870>] driver_register+0x60/0xe0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704166]  [<ffffffff8144567c>] __pci_register_driver+0x4c/0x50
                  Dec  9 12:45:56 ubuntu kernel: [    3.704204]  [<ffffffffc0066c40>] drm_pci_init+0xe0/0x110 [drm]
                  Dec  9 12:45:56 ubuntu kernel: [    3.704215]  [<ffffffffc03a0000>] ? 0xffffffffc03a0000
                  Dec  9 12:45:56 ubuntu kernel: [    3.704314]  [<ffffffffc03a008f>] amdgpu_init+0x8f/0xa0 [amdgpu]
                  Dec  9 12:45:56 ubuntu kernel: [    3.704329]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
                  Dec  9 12:45:56 ubuntu kernel: [    3.704343]  [<ffffffff811cfd71>] ? __vunmap+0x91/0xe0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704357]  [<ffffffff811ebf23>] ? kmem_cache_alloc_trace+0x183/0x1f0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704370]  [<ffffffff811ecd1a>] ? kfree+0x13a/0x150
                  Dec  9 12:45:56 ubuntu kernel: [    3.704385]  [<ffffffff8118cdd3>] do_init_module+0x5f/0x1cf
                  Dec  9 12:45:56 ubuntu kernel: [    3.704399]  [<ffffffff8110a3ef>] load_module+0x166f/0x1c10
                  Dec  9 12:45:56 ubuntu kernel: [    3.704411]  [<ffffffff81106990>] ? __symbol_put+0x60/0x60
                  Dec  9 12:45:56 ubuntu kernel: [    3.704425]  [<ffffffff81213a80>] ? kernel_read+0x50/0x80
                  Dec  9 12:45:56 ubuntu kernel: [    3.704439]  [<ffffffff8110abd4>] SYSC_finit_module+0xb4/0xe0
                  Dec  9 12:45:56 ubuntu kernel: [    3.704451]  [<ffffffff8110ac1e>] SyS_finit_module+0xe/0x10
                  Dec  9 12:45:56 ubuntu kernel: [    3.704466]  [<ffffffff81834ff2>] entry_SYSCALL_64_fastpath+0x16/0x71
                  Dec  9 12:45:56 ubuntu kernel: [    3.704476] Code:  Bad RIP value.
                  Dec  9 12:45:56 ubuntu kernel: [    3.704491] RIP  [<          (null)>]           (null)
                  Dec  9 12:45:56 ubuntu kernel: [    3.704501]  RSP <ffff880211753870>
                  Dec  9 12:45:56 ubuntu kernel: [    3.704509] CR2: 0000000000000000
                  Dec  9 12:45:56 ubuntu kernel: [    3.704603] ---[ end trace 301e2b87bff62358 ]---
                  Lame. 16.40 at least didnt crash... I don't see DAL/DL being activated either. :|

                  Comment


                  • #39
                    Originally posted by twriter View Post
                    Currently, the open stack offers a better user experience for hybrid graphics because APU and dGPU share the same GL implementation (Mesa).
                    I know OpenCL support in Mesa is very incomplete that's one reason why I'd like to try out out the pro stack. At the moment I use the opencl pro libs with upstream amdgpu as a hack.

                    Originally posted by twriter View Post
                    PX support in the pro stack requires you to logout when switching between power saving and performance modes whereas the open stack supports DRI PRIME GPU offloading so you can use the dGPU only when you need it.
                    Yes, the DRI PRIME GPU offloading works now well in general. No need for "xrand --setprovideroffloadsink" manually etc. ...
                    Still usually I get an empty OpenGL application window what has to get minimized/resized once before the content is shown.

                    Originally posted by twriter View Post
                    Recently, we've pushed a lot of fixes upstream for hybrid graphics.
                    Sure I know, I follow those changes quite closely. Actually I have to, to make the dGPU somehow useful. Until kernel 4.9 there was no pp so the chip was stuck at the lowest clock. I know this is great for the laptop battery but really bad for 3d performance.

                    At the moment I still wonder about PCIe transfer rate to the dGPU. 16x is supported but only 1x is used afais.

                    Originally posted by twriter View Post
                    An easy way to get these is to use only the dkms package from the pro stack, with all other graphics components from Ubuntu.
                    So the dkms packages should compile now on newer kernels than 4.4.x for Ubuntu? For 16.40 before I tried some manual patches for 4.7. unsuccessfully.
                    Yes, I saw that 16.50 was trying to install the dkms packages for 4.9rcx on my system but failed.

                    Originally posted by twriter View Post
                    Some laptops also require an upgraded DDX (xserver-xorg-video-amdgpu, 1.2.0 recommended).
                    Yes, this may fix some x11 server and switching problems but not the amdgpu kernel module crash?

                    Originally posted by twriter View Post
                    Having said that, PX systems tend to have a lot of quirks so unless we've tested your specific model, YMMV.
                    Yes, there are thousands of laptops with AMD hybrid graphics out there now. Don't expect to test them all (leave it to the Windows driver devs) .

                    Just wonder why upstream amdgpu works and amdgpu-pro not?

                    Comment


                    • #40
                      Is this supposed to work with a FirePro m4150 (aka Radeon R7 m260x, Opal Pro)? bridgman ?

                      Comment

                      Working...
                      X