Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Tom's Hardware Ask Me Anything – AMD - November 6

  1. #1
    AMDave's Avatar
    AMDave is offline Seeker of the exit clause Moderator
    Site Admin
    Join Date
    Jun 2004
    Location
    Deep in a while loop
    Posts
    9,659

    Tom's Hardware Ask Me Anything – AMD - November 6

    Tom's Hardware Ask Me Anything – AMD - November 6

    Ever wanted to ask one of the big hardware or software giants something directly? Why’d they do that? Where’d the idea come from for that last product? What’s in store next? Well, now you have the chance!
    Tom’s Hardware is proud to announce the next in a series of our brand new community feature – ASK ME ANYTHING.
    On November 6th, we’ll be hosting a Tom’s Hardware “Ask Me Anything”, and our guests will be official representatives from AMD!

    more...
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    ---------------------------------------------

  2. #2
    Join Date
    Sep 2010
    Location
    Leiden, the Netherlands
    Posts
    4,472
    Let's ask whether there's any future in the AM3+ platform. In short: Will Steamroller/Excavator ever appear on AM3+?
    If No, let's ask whether there will be more than just Kaveri on FM2+ -bound to be a 'Yes'-, and when we can expect them.
    If Yes, let's ask when we can see a new chipset to fully support all new features that Steamroller/Excavator have.
    And when can we expect decent drivers for Ubuntu 13.10, aka Saucy Sausage?


  3. #3
    AMDave's Avatar
    AMDave is offline Seeker of the exit clause Moderator
    Site Admin
    Join Date
    Jun 2004
    Location
    Deep in a while loop
    Posts
    9,659
    I think your first 3 lines will be accepted based on the rules on the page.

    The drivers are working fine for me on 13.10 on all hardware that I have.
    You should have noticed an improvement on kernel 3.11 as I did.
    You will soon be getting kernel 3.12 in 13.10, which Phoronix testing has shown makes a big difference.
    But if your issue is with support for the newest hardware, it takes time as per market demand.
    They get the Bugs out first, then expand support on Windows and then on Linux.
    It is still possible that one day that will change, when there are more AMD devices on linux based OSs than on windows. (watch for Steam OS next year)
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    ---------------------------------------------

  4. #4
    Join Date
    Sep 2010
    Location
    Leiden, the Netherlands
    Posts
    4,472
    All was well till last Thursday, when it appeared my Ubuntu box had spontaniously re-booted.
    It would not recognize the GPUs (and that's three of them) in Boinc since, nor would it start up with launch bar or menu bar when run with fglrx drivers (either 13.4 or 13.8)
    The open source drivers have no missing bars, but you can't crunch with them.

    I had my earlier Lubuntu problems solved by re-installing 13.10 with a newly burned DVD, and BOINC 7.2.7 is running fine with Catalyst 13.4 on the Lubuntu box, only a bit sluggish. I even returned valid MilkyWay WUs done on the A10-5700! But what makes people at Canonical decide to use experimental (7.2.7) BOINC versions?

    I just burned a new Ubuntu 13.10 disk to try and repair the installation on the Ubuntu-box and so far, so good. The Ubuntu box is happily crunching on the fglrx drivers that came with 13.10 and started using the HD 6550D and the better (2 GB) HD 6670 without even a cc_config.xml edit!
    Almost like the time I installed my GTX 630 alongside the A8-3820 -under Windows- and got PhysX for the HD 6650D too.
    Looks like the OS-es do not 'see' the AMD IGP of the APU, at least not as being equal to a discrete graphics card. In the case of the HD 7660D a most remarkable feat, as it outperforms a HD 6670.
    Last edited by Dirk Broer; 11-04-2013 at 08:17 PM.


  5. #5
    Join Date
    Sep 2010
    Location
    Leiden, the Netherlands
    Posts
    4,472
    And again! After an upgrade and subsequent reboot the GPUs are no longer detected in BOINC.
    And this while I have a functioning Catalyst Control center....

    dirk@ASUS-F1A75V-EVO:~$ lspci | grep VGA
    00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D]
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]
    02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]
    dirk@ASUS-F1A75V-EVO:~$


    dirk@ASUS-F1A75V-EVO:~$ fglrxinfo
    display: :0 screen: 0
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon HD 6550D
    OpenGL version string: 4.2.12337 Compatibility Profile Context 13.101

    display: :0 screen: 1
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon HD 6670
    OpenGL version string: 4.2.12337 Compatibility Profile Context 13.101

    display: :0 screen: 2
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon HD 6670
    OpenGL version string: 4.2.12337 Compatibility Profile Context 13.101




    # Warning: This xorg.conf file is autogenerated by fglrx-pxpress. All changes to this file will be lost.

    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    Screen "aticonfig-Screen[1]-0" RightOf "aticonfig-Screen[0]-0"
    Screen "aticonfig-Screen[2]-0" RightOf "aticonfig-Screen[1]-0"
    EndSection

    Section "Module"
    EndSection

    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection

    Section "Monitor"
    Identifier "aticonfig-Monitor[1]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection

    Section "Monitor"
    Identifier "aticonfig-Monitor[2]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection

    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:0:1:0"
    EndSection

    Section "Device"
    Identifier "aticonfig-Device[1]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection

    Section "Device"
    Identifier "aticonfig-Device[2]-0"
    Driver "fglrx"
    BusID "PCI:2:0:0"
    EndSection

    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection

    Section "Screen"
    Identifier "aticonfig-Screen[1]-0"
    Device "aticonfig-Device[1]-0"
    Monitor "aticonfig-Monitor[1]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection

    Section "Screen"
    Identifier "aticonfig-Screen[2]-0"
    Device "aticonfig-Device[2]-0"
    Monitor "aticonfig-Monitor[2]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection


    za 09 nov 2013 22:25:40 CET | | Starting BOINC client version 7.2.28 for x86_64-pc-linux-gnu
    za 09 nov 2013 22:25:40 CET | | log flags: file_xfer, sched_ops, task
    za 09 nov 2013 22:25:40 CET | | Libraries: libcurl/7.32.0 OpenSSL/1.0.1e zlib/1.2.8 libidn/1.28 librtmp/2.3
    za 09 nov 2013 22:25:40 CET | | Data directory: /var/lib/boinc-client
    za 09 nov 2013 22:25:40 CET | | GPU detection failed. error code 65280
    za 09 nov 2013 22:25:40 CET | | No usable GPUs found
    za 09 nov 2013 22:25:40 CET | | Host name: ASUS-F1A75V-EVO
    za 09 nov 2013 22:25:40 CET | | Processor: 4 AuthenticAMD AMD A8-3870 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
    za 09 nov 2013 22:25:40 CET | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter
    za 09 nov 2013 22:25:40 CET | | OS: Linux: 3.11.0-13-generic
    za 09 nov 2013 22:25:40 CET | | Memory: 5.81 GB physical, 7.49 GB virtual
    za 09 nov 2013 22:25:40 CET | | Disk: 65.86 GB total, 39.44 GB free
    za 09 nov 2013 22:25:40 CET | | Local time is UTC +1 hours
    za 09 nov 2013 22:25:40 CET | | VirtualBox version: 4.2.16_Ubuntur86992
    za 09 nov 2013 22:25:40 CET | | Config: use all coprocessors
    Last edited by Dirk Broer; 11-09-2013 at 08:33 PM.


  6. #6
    AMDave's Avatar
    AMDave is offline Seeker of the exit clause Moderator
    Site Admin
    Join Date
    Jun 2004
    Location
    Deep in a while loop
    Posts
    9,659
    So you are using the custom install of the AMD proprietary driver.
    The error number indicates to me that a file may be missing.

    See if you can strip all of the custom installed proprietary driver out
    Install the proprietary driver provided by the linux distribution.
    * Software & Updates > Additional Drivers tab > Using video driver for the AMD graphics accelerators from fglrx-updates (proprietary)
    It requires that the custom install is completely removed, which can be very tricky
    If it doesn't work the removal most likely failed - it only takes 25 mins to do a clean OS install & get back to this point.
    Sometimes it is worth it if you don't have time to muck around.

    Mine works fine with HD7xxx now, so I now prefer this instead of doing a custom install of the driver.
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    ---------------------------------------------

  7. #7
    Join Date
    Sep 2010
    Location
    Leiden, the Netherlands
    Posts
    4,472
    Already using the driver you suggested? File wasn't missing till last software updates....
    Screenshot from 2013-11-10 01:56:00.png
    Last edited by Dirk Broer; 11-10-2013 at 12:14 AM.


  8. #8
    AMDave's Avatar
    AMDave is offline Seeker of the exit clause Moderator
    Site Admin
    Join Date
    Jun 2004
    Location
    Deep in a while loop
    Posts
    9,659
    I suspect that your 'updates' are 'dist-upgrade's which means you get the kernel updates
    When you get a kernel update the machine needs to re-compile the kernel modules, which includes your custom install of the AMD driver which is not included in the re-build script.
    If you use the distro version of the proprietary driver the kernel module IS included in the re-build script after the updates are downloaded.

    So if you are getting kernel updates you should always know that you need to re-install your custom driver.
    OR you can turn off the kernel updates in the software updater.
    OR use the distro version of the proprietary driver and watch your worries fade away ;)
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    ---------------------------------------------

  9. #9
    AMDave's Avatar
    AMDave is offline Seeker of the exit clause Moderator
    Site Admin
    Join Date
    Jun 2004
    Location
    Deep in a while loop
    Posts
    9,659
    I have seen that setting get flagged after a custom driver install, which was confusing.
    Did you install from the file downloaded from AMD? or did you install by selecting that setting? Was it a clean install - no custom driver install before that?

    From a clean install, using the distro driver by using that setting, I have had ZERO problems with it.

    If the kernel module needs to be re-built you can use the 'dkms' instructions from the Ubunru AMD drivers page, which also gives you extra diagnostics & will tell you where the problem is.
    Personally I'd cut to the 25 minute version - wipe, re-install & update.
    But that's just me. All my data is on backed up network drives so I made it easier on myself & can wipe & install whenever I feel like I need to.
    Might not be the case for you.

    That said - I haven't had to in a long time now. I think all my machines are upgrades from 12.10, 13.04 to 13.10. All working fine.
    Even the laptop. but that was a clean install after Win7.
    PS Linux install to an SSD from USB2 memory stick is incredibly fast :D
    Last edited by AMDave; 11-10-2013 at 12:49 AM.
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    ---------------------------------------------

  10. #10
    Join Date
    Sep 2010
    Location
    Leiden, the Netherlands
    Posts
    4,472
    No SDD here, and my biggest USB stick is 256 MB. Guess I'll do a clean install from DVD once the BOINC cache is empty -apart from the GPU WUs, I'll have to abort those...

    Can the 'missing file' have to do with ia32-libs, which is no longer available in 64-bit linux?
    Last edited by Dirk Broer; 11-10-2013 at 10:22 AM.


Page 1 of 2 12 LastLast

Posting Permissions

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