Page 96 of 143 FirstFirst ... 46869495969798106 ... LastLast
Results 951 to 960 of 1425

Thread: Updated and Optimized Ubuntu Free Graphics Drivers

  1. #951
    Join Date
    Jan 2014
    Posts
    2

    Default

    Quote Originally Posted by mmstick View Post
    Did you properly fully remove all of fglrx? Did you remove the xorg.conf in /etc/X11?
    I did fresh installation of ubuntu. no fglrx used, no other ppa.
    thanks for advise :-/

  2. #952
    Join Date
    Aug 2012
    Posts
    439

    Default

    http://cgit.freedesktop.org/mesa/mes...?qt=grep&q=AMD

    The OpenGL 3.3 RadeonSI patches are now live in mesa upstream. All we need is for Oibaf to upgrade to LLVM 3.5 git and update the rest.

  3. #953
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,286

    Default

    Quote Originally Posted by oibaf View Post
    stats-rebased needs... a rebase.
    Done.

  4. #954
    Join Date
    Aug 2012
    Posts
    70

    Default

    I jknow its not a place to post bugs.
    But just to let everyone know.
    INTEL HD3000 + AMD 6450M
    chrome 100% unusable using acelerated or not.

    constants crashes...
    [ 75.162430] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 597.043197] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 597.043209] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 597.415392] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 597.415403] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 761.283390] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 761.283402] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 761.656967] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 761.656980] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

    LAtest 7 days seems very unstable..

    Not asking for help or otas for nothing.
    Just a small report.

    ;-)

  5. #955
    Join Date
    Aug 2012
    Posts
    70

    Default

    and...
    [ 89.018649] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 89.018654] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 342.070463] [drm] stuck on render ring
    [ 342.070468] [drm] GPU crash dump saved to /sys/class/drm/card0/error
    [ 342.070470] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
    [ 342.070471] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
    [ 342.070473] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
    [ 342.070474] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
    [ 342.074617] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x86b000 ctx 0) at 0x86b5a0
    [ 367.050023] [drm] stuck on render ring
    [ 367.050073] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x85c000 ctx 0) at 0x85c830
    [ 624.002572] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 624.002584] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
    [ 624.373040] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
    [ 624.373053] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

    cat /sys/class/drm/card0/error

    Num Pipes: 2
    Pipe [0]:
    SRC: 077f0437
    Plane [0]:
    CNTR: d8004400
    STRIDE: 00001e00
    ADDR: 00000000
    SURF: 02063000
    TILEOFF: 00000000
    Cursor [0]:
    CNTR: 04000027
    POS: 00b4000f
    BASE: 01073000
    Pipe [1]:
    SRC: 00000000
    Plane [1]:
    CNTR: 00004000
    STRIDE: 00000000
    ADDR: 00000000
    SURF: 00000000
    TILEOFF: 00000000
    Cursor [1]:
    CNTR: 00000000
    POS: 00000000
    BASE: 00000000
    CPU transcoder: A
    CONF: c0000050
    HTOTAL: 0897077f
    HBLANK: 0897077f
    HSYNC: 080307d7
    VTOTAL: 04640437
    VBLANK: 04640437
    VSYNC: 0440043b
    CPU transcoder: B
    CONF: 00000000
    HTOTAL: 00000000
    HBLANK: 00000000
    HSYNC: 00000000
    VTOTAL: 00000000
    VBLANK: 00000000
    VSYNC: 00000000

  6. #956
    Join Date
    Dec 2013
    Posts
    57

    Default Chrome issue with intel drivers

    has been fixed. At least in my case (Sandy Bridge). I am not getting the corruptions any more.

  7. #957
    Join Date
    Aug 2012
    Posts
    70

    Default

    nor me.
    Sandybridge to.
    I update 3 hour ago and now is worst i cant be loged for less than one minut. no need to open nothing to crash.
    UXA didnt work to. not even load the x.

  8. #958
    Join Date
    Aug 2012
    Posts
    70

    Default

    Yes.. Seems the last intel update solve the problem..
    But DRI_PRIME/OFFLOAD is 100% broken.
    So way of load using xrandr

  9. #959
    Join Date
    Jan 2014
    Posts
    15

    Default

    I was testing out the mesa AMD OpenCL drivers with pyrit benchmarks, and I was surprised by the performance gains vs the proprietary AMD drivers: 20-30%! Gallium OpenCL has gotten a lot better in the past few months.

    So, I was wondering if the maintainer of the repository wouldn't mind applying this patch I made (adapted from this debian sid patch) to turn on opencl support in mesa? This patch builds out the opencl libraries to seperate deb packages, and it is tested and working on the latest mesa oibaf source package (as of right now). It can be found here: http://pastebin.com/iaaRCtBm

    The only other thing required is the libclc libraries, which can be backported from the trusty working repo here. The llvm and clang packages in the oibaf repository already fulfill the requirements.

    Regardless, thank you so much for this repo, it has saved me a lot of time and anguish in trying to get the latest mesa drivers working.

  10. #960
    Join Date
    Dec 2013
    Posts
    57

    Default

    Quote Originally Posted by fritzls View Post
    Yes.. Seems the last intel update solve the problem..
    But DRI_PRIME/OFFLOAD is 100% broken.
    So way of load using xrandr
    Well yeah, the issue with Chrome has been fixed, but another one (ones?) appeared. This happened on my laptop, and on workstation. After some time X crashes, and I get lightdm login screen appears. Unfortunately I don't have time to report the issue, because I cannot find where the logs are : ). It looks to me that log files structure has changed on Ubuntu. I have just checked again and this is all I have found:

    Jan 29 19:28:31 denis-desktop kernel: [ 3.355118] [drm] Wrong MCH_SSKPD value: 0x16040307
    Jan 29 19:28:31 denis-desktop kernel: [ 3.355120] [drm] This can cause pipe underruns and display issues.
    Jan 29 19:28:31 denis-desktop kernel: [ 3.355121] [drm] Please upgrade your BIOS to fix this.
    Jan 29 19:28:31 denis-desktop kernel: [ 3.700331] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
    Jan 29 19:28:31 denis-desktop kernel: [ 3.700333] i915 0000:00:02.0: registered panic notifier
    Jan 29 19:28:31 denis-desktop kernel: [ 3.700348] i915: No ACPI video bus found
    Jan 29 19:28:31 denis-desktop kernel: [ 3.700375] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    Jan 29 19:28:40 denis-desktop /usr/sbin/gpm[1999]: *** info [daemon/startup.c(131)]:
    Jan 29 19:28:40 denis-desktop /usr/sbin/gpm[1999]: Started gpm successfully. Entered daemon mode.

    Since I have some work to do, I have purged oibaf repo, and will try in couple of days again.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •