Announcement

Collapse
No announcement yet.

Here Are Your Vulkan Download Links

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

  • Tomin
    replied
    Originally posted by tomtomme View Post
    amd is opensourcing big parts of catalyst
    Really? I remember only seeing some new code that wasn't part of Catalyst, but anyway it's great that they released it.

    I'm not that worried about AMD not having Vulkan driver yet, because there aren't really any games that could use it.

    I actually don't have much hardware that can run Vulkan yet: My Fermi card may get drivers later, my TURKS card will not get drivers (unless community makes them, which is not that likely) and my Haswell has only experimental support at the moment. Anything else that I have is too old for Vulkan anyway. Maybe its time to go shopping some hardware and AMD is a strong choice because of their new driver strategy.

    Leave a comment:


  • baka0815
    replied
    Well, IP rights, NDA stuff, ... tricky situation.

    The NVIDIA blob(!) is, as someone noted, an old version which has Vulkan enabled - probably their testing driver.

    I'm sure AMD could also deliver some sort of (testing) driver with Vulkan support - but what's the benefit?

    Having something that's kind of working in some cases or having something reliably working in most cases? I'm going with the latter and am buying AMD cards to support their open strategy!

    Leave a comment:


  • tomtomme
    replied
    Originally posted by andre30correia View Post
    again amd nothing care about linux, so much fan boys and defenders and haters against nvidia, always the same sh*t amd
    amd donated mantle to khronos. khronos backs open standards and is a crucial part for linux/android ecosystem
    amd opened up its gpus with gpuopen
    amd is opensourcing big parts of catalyst
    amd hires opensource devs

    compare this to nvidias efforts

    all this while amd is in financial trouble and laying off staff since years. you could interpret this as a desperate move to attract devs but the outcome stays the same. It benefits linux and the foss community a big deal.
    if you care for linux you care for opensource. If not you are using linux just like windows. I do not say everything has to be open source. All the entertainment stuff can stay closed. But stuff at the OS level should be open for various reasons (privacy, security, not-reinventing-the-wheel, collaboration)

    Leave a comment:


  • theriddick
    replied
    I'm willing to cut AMD some slack for a couple months, but NVIDIA seems to get more actually useful results in Linux except for those few show stopping driver bugs they keep releasing...

    Leave a comment:


  • bridgman
    replied
    Originally posted by andre30correia View Post
    again amd nothing care about linux, so much fan boys and defenders and haters against nvidia, always the same sh*t amd
    Right, mean old uncaring AMD moving to an open-stack-based Linux driver architecture right when Vulkan is being introduced. If they cared about Linux they would have stayed with Catalyst forever so they could ship Vulkan Linux support on day one.

    I can't even type that with a straight face, let alone say it.

    Leave a comment:


  • triangle
    replied
    Originally posted by triangle View Post
    ... No Intel driver?
    Than whats this? https://01.org/linuxgraphics/blogs/j...intel-hardware
    (note: I have a sandy bridge cpu so I could not test it yet, so take this with a grain of salt if I am being stupid)
    *should have looked at more recent articles*
    https://phoronix.com/scan.php?page=n...lkan-Published
    Any way, maybe this article should be updated to include that.

    Leave a comment:


  • triangle
    replied
    ... No Intel driver?
    Than whats this? https://01.org/linuxgraphics/blogs/j...intel-hardware
    (note: I have a sandy bridge cpu so I could not test it yet, so take this with a grain of salt if I am being stupid)

    Leave a comment:


  • ileonte
    replied
    Originally posted by blackout23 View Post

    Code:
    [LIST][*][COLOR=#666600]@@[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_registry[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]=[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600](([/COLOR][COLOR=#000000]nvl [/COLOR][COLOR=#666600]!=[/COLOR][COLOR=#000000] NULL[/COLOR][COLOR=#666600])[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]?[/COLOR][*][COLOR=#000000]nvl[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]:[/COLOR][COLOR=#000000] nv_registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][*][COLOR=#666600]-[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] [/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] [/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] [/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][*][*][COLOR=#000088]static[/COLOR][COLOR=#000000] [/COLOR][COLOR=#660066]ssize_t[/COLOR][*][COLOR=#666600]@@[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]560[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]561[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_text_file[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000088]void[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]*[/COLOR][COLOR=#000000]v[/COLOR][*][COLOR=#666600])[/COLOR][*][COLOR=#666600]{[/COLOR][*][COLOR=#666600]-[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] [/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][/LIST]
    Voila. 2 lines changed fixes it. Keep in mind that you have to tell the driver to ignore the X ABI if you're on newer than 1.17.
    I mean sure, you can work around it. The fact remains that as driver releases go this is a pretty crappy one. Funnily enough the situation isn't any better on Windows either - their own GeForce Experience app isn't showing this driver as available even on the beta channel, probably because it's old. So all around this seems to me like a half-assed release from NVIDIA.

    Leave a comment:


  • mezo
    replied
    Originally posted by blackout23 View Post

    Code:
    [LIST][*][COLOR=#666600]@@[/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_registry[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]=[/COLOR][COLOR=#666600](([/COLOR][COLOR=#000000]nvl [/COLOR][COLOR=#666600]!=[/COLOR][COLOR=#000000] NULL[/COLOR][COLOR=#666600])[/COLOR][COLOR=#666600]?[/COLOR][*][COLOR=#000000]nvl[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]:[/COLOR][COLOR=#000000] nv_registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]-[/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000088]return[/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][*][COLOR=#000088]static[/COLOR][COLOR=#660066]ssize_t[/COLOR][*][COLOR=#666600]@@[/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]560[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]561[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_text_file[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000088]void[/COLOR][COLOR=#666600]*[/COLOR][COLOR=#000000]v[/COLOR][*][COLOR=#666600])[/COLOR][*][COLOR=#666600]{[/COLOR][*][COLOR=#666600]-[/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000088]return[/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][/LIST]
    Voila. 2 lines changed fixes it. Keep in mind that you have to tell the driver to ignore the X ABI if you're on newer than 1.17.
    even with this workaround my xserver keeps crashing after few seconds. (debian stretch)

    this is the way i used: https://devtalk.nvidia.com/default/t...1-build-error/

    Leave a comment:


  • blackout23
    replied
    Originally posted by ileonte View Post
    I wouldn't be too quick to praise NVIDIA for this beta driver. It's based off of version 355 which is old (I currently have 361.something installed from their stable releases) and doesn't even compile on newer kernels (I tried on 4.3.0 and it fails to build).
    Code:
    [LIST][*][COLOR=#666600]@@[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]360[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_registry[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]=[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600](([/COLOR][COLOR=#000000]nvl [/COLOR][COLOR=#666600]!=[/COLOR][COLOR=#000000] NULL[/COLOR][COLOR=#666600])[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]?[/COLOR][*][COLOR=#000000]nvl[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000000]registry_keys [/COLOR][COLOR=#666600]:[/COLOR][COLOR=#000000] nv_registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][*][COLOR=#666600]-[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] [/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_printf[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] [/COLOR][COLOR=#008800]"Binary: \"%s\"\n"[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] registry_keys[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] [/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][*][*][COLOR=#000088]static[/COLOR][COLOR=#000000] [/COLOR][COLOR=#660066]ssize_t[/COLOR][*][COLOR=#666600]@@[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]-[/COLOR][COLOR=#006666]560[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]7[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]+[/COLOR][COLOR=#006666]561[/COLOR][COLOR=#666600],[/COLOR][COLOR=#006666]8[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]@@[/COLOR][COLOR=#000000] nv_procfs_read_text_file[/COLOR][COLOR=#666600]([/COLOR][*][COLOR=#000088]void[/COLOR][COLOR=#000000] [/COLOR][COLOR=#666600]*[/COLOR][COLOR=#000000]v[/COLOR][*][COLOR=#666600])[/COLOR][*][COLOR=#666600]{[/COLOR][*][COLOR=#666600]-[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] seq_puts[/COLOR][COLOR=#666600]([/COLOR][COLOR=#000000]s[/COLOR][COLOR=#666600],[/COLOR][COLOR=#000000] s[/COLOR][COLOR=#666600]->[/COLOR][COLOR=#000088]private[/COLOR][COLOR=#666600]);[/COLOR][*][COLOR=#666600]+[/COLOR][COLOR=#000000] [/COLOR][COLOR=#000088]return[/COLOR][COLOR=#000000] [/COLOR][COLOR=#006666]0[/COLOR][COLOR=#666600];[/COLOR][*][COLOR=#666600]}[/COLOR][/LIST]
    Voila. 2 lines changed fixes it. Keep in mind that you have to tell the driver to ignore the X ABI if you're on newer than 1.17.

    Leave a comment:

Working...
X