Results 1 to 44 of 44

Thread: (Guide) Fglrx + AMD APP SDK + Pyrit + Cal++ for AMD Video Cards

  1. #1
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315

    (Guide) Fglrx + AMD APP SDK + Pyrit + Cal++ for AMD Video Cards

    Hi all,

    This is an alternative to my other post where I explained how to install the OpenCL version of GPU support for pyrit / oclhashcat.

    While OpenCL is very easy to install, it is no where near as powerful as Cal++. Below are some statistics for my Radeon HD 6970

    Code:
    Pyrit Benchmark
    OpenCL 50595.56 PMKs/s (graphics card produced 49359.6 PMKs/s)
    
    Cal++ 82695.02 PMKs/s (graphics card produced 81675.5 PMKs/s)
    As can be seen, the Cal++ version is much faster.

    At time of writing, the latest versions of all software is being installed on a 64bit Kali 1.0.9. This includes:
    Code:
    Pyrit v308
    AMD APP SDK 2.9-1
    Fglrx 14.4.2
    Cal++ 0.90
    1. Update and upgrade kali
    Code:
    apt-get clean && apt-get update && apt-get upgrade && apt-get dist-upgrade
    2. Install headers
    Code:
    apt-get install linux-headers-$(uname -r)
    3. Install fglrx
    Code:
    apt-get install fglrx-driver fglrx-atieventsd fglrx-control
    4. Build xorg files
    Code:
    aticonfig --initial
    5. Reboot
    Code:
    shutdown -r now
    6. Install some dependencies needed for later
    Code:
    apt-get install libpcap-dev python-dev libssl-dev
    7. Download AMD APP SDK from the link below (about 120MB). I'm on 64bit so I downloaded 2.9-1 for linux 64bit. Store it in your home folder. Extract it when finished.
    Code:
    http://developer.amd.com/tools-and-sdks/opencl-zone/amd-accelerated-parallel-processing-app-sdk/
    
    cd ~
    
    tar xvf AMD-APP-SDK*.tar.bz2
    8. Install AMD APP SDK and accept defaults
    Code:
    ./AMD-APP-SDK*.sh
    9. Update .bashrc to set the correct paths. Insert the block below somewhere near the top (use the blank space under # for examples on line 3)
    Code:
    cd ~
    nano .bashrc
    Add the following
    Code:
    # AMD APP SDK
    export AMDAPPSDKROOT=/opt/AMDAPPSDK-2.9-1
    export AMDAPPSDKSAMPLESROOT=/opt/AMDAPPSDK-2.9-1/
    export LD_LIBRARY_PATH=${AMDAPPSDKROOT}lib/x86_64:${LD_LIBRARY_PATH}
    export ATISTREAMSDKROOT=$AMDAPPSDKROOT
    10. Reboot again to update paths as its easiest.
    Code:
    shutdown -r now
    11. Some required files are not provided by AMD APP SDK, so this step is to download them and put them where they need to go.
    Code:
    mkdir /opt/AMDAPPSDK-2.9-1/include/CAL
    
    cd /opt/AMDAPPSDK-2.9-1/include/CAL
    
    svn checkout https://github.com/clockfort/amd-app-sdk-fixes/trunk/include/CAL .
    12. Install some more dependencies for cal++
    Code:
    apt-get install cmake libboost-all-dev
    13. Download cal++ from here (about 90kb). Store it in your home folder.
    Code:
    http://sourceforge.net/projects/calpp/files/latest/download
    14. Extract cal++ and go into the folder created.
    Code:
    cd ~
    
    tar xvf cal*.tar.gz
    
    cd calpp-0.90
    15. Nano the CMakeLists.txt file. Change line 18,19 and 20 to match those below. When changes are finished, save and exit.
    Code:
    FIND_LIBRARY( LIB_ATICALCL aticalcl PATHS "$ENV{ATISTREAMSDKROOT}" )
    FIND_LIBRARY( LIB_ATICALRT aticalrt PATHS "$ENV{ATISTREAMSDKROOT}" ) 
    FIND_PATH( LIB_ATICAL_INCLUDE NAMES cal.h calcl.h PATHS "$ENV{ATISTREAMSDKROOT}/include/CAL" )
    16. Time to build and install cal++. Run the following from within the calpp-0.90 folder. Should be ~/calpp-0.90/. Will have warnings but it will finish.
    Code:
    cmake .
    
    make
    
    make install
    17. Checkout and then build pyrit
    Code:
    cd ~
    
    svn checkout http://pyrit.googlecode.com/svn/trunk/ pyrit_svn
    
    cd pyrit_svn/pyrit/
    
    python setup.py build
    python setup.py install
    18. Move into the cpyrit_calpp folder
    Code:
    cd ~/pyrit_svn/cpyrit_calpp/
    19. Edit line 28 and then line 41 to match those shown below. Once changes are made, save and exit.
    Code:
    nano +28 setup.py
    
    Line 28 should read
    VERSION = '0.4.1-dev'
    
    Line 41 should read
    CALPP_INC_DIRS.append(os.path.join(CALPP_INC_DIR, 'include/CAL'))
    20. Build and install cpyrit_calpp
    Code:
    python setup.py build
    python setup.py install
    21. List pyrit cores and benchmark. You should see your cal++ device in pyrit list_cores
    Code:
    pyrit list_cores
    
    pyrit benchmark
    Last edited by staticn0de; 2014-09-20 at 04:34.
    chown -R us ./base

  2. #2
    Join Date
    2013-Mar
    Posts
    57

    Problems during CAL++ build

    Hi,

    sorry for hijacking this HOWTO but I am totally frustrated. Didn't count the fresh installation of my system today (appr. 20) to get pyrit and CAL++ working for my card R9 290X. After I found your guide I hoped that it will work but I failed during CAL++ build. Also tested with SDK 2.7 guided by blackmore but the same error in the end.

    complete output on pastebin: http://pastebin.com/30v5k4mp

    here just some output for faster reading.

    If I would knew that installation is so complicated under linux or kali I would never changed my NVIDIA card to AMD. Since March 2014 I am trying to get my card working with pyrit.
    I really really hope that you could help me with my error.

    Can you tell me if this an driver error or does it come from CAL++? (see dmesg output last line)

    Thanks in advance for reading.

    lspci -nnkv
    Code:
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0] (prog-if 00 [VGA controller])
    	Subsystem: Tul Corporation / PowerColor Device [148c:2342]
    	Flags: bus master, fast devsel, latency 0, IRQ 47
    	Memory at e0000000 (64-bit, prefetchable) [size=256M]
    	Memory at f0000000 (64-bit, prefetchable) [size=8M]
    	I/O ports at e000 [size=256]
    	Memory at f7e00000 (32-bit, non-prefetchable) [size=256K]
    	Expansion ROM at f7e40000 [disabled] [size=128K]
    	Capabilities: [48] Vendor Specific Information: Len=08 <?>
    	Capabilities: [50] Power Management version 3
    	Capabilities: [58] Express Legacy Endpoint, MSI 00
    	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    	Capabilities: [150] Advanced Error Reporting
    	Capabilities: [200] #15
    	Capabilities: [270] #19
    	Capabilities: [2b0] Address Translation Service (ATS)
    	Capabilities: [2c0] #13
    	Capabilities: [2d0] #1b
    	Kernel driver in use: fglrx_pci
    fglrxinfo
    Code:
    display: :0.0  screen: 0
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon R9 200 Series
    OpenGL version string: 4.4.12874 Compatibility Profile Context 14.10.1006.1001
    Code:
    root@b0x:~/pyrit_svn/cpyrit_calpp# python setup.py build
    running build
    running build_ext
    Building modules...
    building 'cpyrit._cpyrit_calpp' extension
    creating build
    creating build/temp.linux-x86_64-2.7
    gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/opt/AMDAPPSDK-2.9-1/include/CAL -I/usr/include/python2.7 -c _cpyrit_calpp.cpp -o build/temp.linux-x86_64-2.7/_cpyrit_calpp.o -Wall -fno-strict-aliasing -DVERSION="0.4.1-dev (svn r308)"
    cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
    gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/opt/AMDAPPSDK-2.9-1/include/CAL -I/usr/include/python2.7 -c _cpyrit_calpp_kernel.cpp -o build/temp.linux-x86_64-2.7/_cpyrit_calpp_kernel.o -Wall -fno-strict-aliasing -DVERSION="0.4.1-dev (svn r308)"
    cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
    _cpyrit_calpp_kernel.cpp: In function ‘void sha1_process(const SHA_DEV_CTX&, SHA_DEV_CTX&)’:
    _cpyrit_calpp_kernel.cpp:429:32: warning: suggest parentheses around arithmetic in operand of ‘^’ [-Wparentheses]
    _cpyrit_calpp_kernel.cpp:431:57: warning: suggest parentheses around arithmetic in operand of ‘^’ [-Wparentheses]
    _cpyrit_calpp_kernel.cpp:434:61: warning: suggest parentheses around arithmetic in operand of ‘^’ [-Wparentheses]
    . OUTPUT OMITTED
    . OUTPUT OMITTED
    cpyrit_calpp_kernel.cpp:685:49: warning: suggest parentheses around arithmetic in operand of ‘|’ [-Wparentheses]
    _cpyrit_calpp_kernel.cpp:689:76: warning: suggest parentheses around arithmetic in operand of ‘|’ [-Wparentheses]
    creating build/lib.linux-x86_64-2.7
    creating build/lib.linux-x86_64-2.7/cpyrit
    g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/_cpyrit_calpp.o build/temp.linux-x86_64-2.7/_cpyrit_calpp_kernel.o -lcrypto -laticalrt -laticalcl -o build/lib.linux-x86_64-2.7/cpyrit/_cpyrit_calpp.so
    
    root@b0x:~/pyrit_svn/cpyrit_calpp# python setup.py install
    running install
    running build
    running build_ext
    Building modules...
    running install_lib
    copying build/lib.linux-x86_64-2.7/cpyrit/_cpyrit_calpp.so -> /usr/local/lib/python2.7/dist-packages/cpyrit
    running install_egg_info
    Writing /usr/local/lib/python2.7/dist-packages/cpyrit_calpp-0.4.1_dev._svn.r308_.egg-info
    
    root@b0x:~/pyrit_svn/cpyrit_calpp# pyrit list_cores
    Segmentation fault
    Checking dmesg gives me
    Code:
    [  510.460402] pyrit[9573]: segfault at e1c ip 00007f2491e67399 sp 00007fff59a5c580 error 4 in libaticaldd.so[7f2491d04000+b47000]
    Last edited by tr00n3r; 2014-09-22 at 22:29.

  3. #3
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Hi tr00n3r,

    Does the command 'pyrit selftest' work?

    I have the same card in my other computer. I'll install Kali tonight and try getting it to work.
    chown -R us ./base

  4. #4
    Join Date
    2013-Mar
    Posts
    57
    Hi staticn0de,
    thanks for your fast reply! no the selftest also not working --> Segmentation fault

    for clarification - this is the card: http://www.tomshardware.com/reviews/...view,3803.html
    CPU: i7 4770k
    MB: Z87-G45 GAMING
    RAM: 16 GB Corsair CMX16GX3M2A1600C11

    thought it would be a good card for gpu cracking
    I also tried also the 32 bit version but with blackmoreops' guide (SDK 2.7) same result. Tomorrow I will test the 32bit again but with your's

    In blackmoreops' guide was the radeon blacklisted. I am not a Linux professional but is it necessary to do this?
    Last edited by tr00n3r; 2014-09-22 at 23:45.

  5. #5
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    I have not been through blackmores guide lately so I don't know why Radeon would be blacklisted.

    It's a reasonably cutting edge card, I'd try the 14.6 drivers in the Debian Sid repo rather than another install of amd app SDK.

    Edit: also, if you didn't change from NVIDIA you would just being having as much fun installing CUDA ☺
    Last edited by staticn0de; 2014-09-23 at 00:05.
    chown -R us ./base

  6. #6
    Join Date
    2013-Mar
    Posts
    57
    ok, will try tomorrow.
    one more thing: can you tell me how do I install the 14.6 drivers from the Debian Sid?
    is that right to add these to /etc/apt/source.list ?
    Code:
    # There is no security, volatile or backports repo for unstable.
    # Unstable Sid
     #deb http://http.us.debian.org/debian/ unstable main contrib non-free 
    # Unstable Sources
     #deb-src http://http.us.debian.org/debian/ unstable main contrib non-free
    or should I directly download the drivers from AMD?

    I thought it would be a good idea to change to AMD because of performance. NVIDIA GTX780 gives me ~64500 PMKs/s and that took too long for me as I saw the AMD benchs (7970+7990) Driver and CUDA were not the problem.
    Last edited by tr00n3r; 2014-09-23 at 00:40.

  7. #7
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Just add this and run apt-get update. After you install the drivers (step 3.) remove the line and run apt-get update again.

    deb http://http.us.debian.org/debian/ unstable main contrib non-free
    Last edited by staticn0de; 2014-09-23 at 01:14.
    chown -R us ./base

  8. #8
    Join Date
    2013-Mar
    Posts
    57

    CAL++ failed with error

    I have tried with the driver from SID and AMDAPPSDK-2.9-1 (fresh 64bit installation) only did upgrade, added sid for driver, installed driver, removed sid and followed your guide
    Code:
    root@b0x:~# fglrxinfo 
    display: :0.0  screen: 0
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon R9 200 Series
    OpenGL version string: 4.4.12968 Compatibility Profile Context 14.201.1006.1002
    fglrx is loaded
    Code:
    root@b0x:~# lsmod | grep -i fglrx
    fglrx                9171703  81 
    button                 12944  1 fglrx

    and in use

    Code:
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0] (prog-if 00 [VGA controller])
    	Subsystem: Tul Corporation / PowerColor Device [148c:2342]
    	Flags: bus master, fast devsel, latency 0, IRQ 47
    	Memory at e0000000 (64-bit, prefetchable) [size=256M]
    	Memory at f0000000 (64-bit, prefetchable) [size=8M]
    	I/O ports at e000 [size=256]
    	Memory at f7e00000 (32-bit, non-prefetchable) [size=256K]
    	Expansion ROM at f7e40000 [disabled] [size=128K]
    	Capabilities: [48] Vendor Specific Information: Len=08 <?>
    	Capabilities: [50] Power Management version 3
    	Capabilities: [58] Express Legacy Endpoint, MSI 00
    	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    	Capabilities: [150] Advanced Error Reporting
    	Capabilities: [200] #15
    	Capabilities: [270] #19
    	Capabilities: [2b0] Address Translation Service (ATS)
    	Capabilities: [2c0] #13
    	Capabilities: [2d0] #1b
    	Kernel driver in use: fglrx_pci

    Code:
    root@b0x:~/calpp-0.90# cmake .
    -- The C compiler identification is GNU 4.7.4
    -- The CXX compiler identification is GNU 4.7.4
    -- Check for working C compiler: /usr/bin/gcc
    -- Check for working C compiler: /usr/bin/gcc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Boost version: 1.49.0
    -- Found the following Boost libraries:
    --   date_time
    -- ===========================================================
    -- ATI CAL include directory /opt/AMDAPPSDK-2.9-1/include/CAL
    -- ATI CAL cl library directory /usr/lib/x86_64-linux-gnu
    -- ATI CAL rt library directory /usr/lib/x86_64-linux-gnu
    -- Boost version 1_49
    -- ===========================================================
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /root/calpp-0.90
    root@b0x:~/calpp-0.90# 
    root@b0x:~/calpp-0.90# make
    Scanning dependencies of target coalescingtest
    [  6%] Building CXX object examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o
    /root/calpp-0.90/examples/coalescingtest.cpp: In function 'void show_result(int, int)':
    /root/calpp-0.90/examples/coalescingtest.cpp:224:5: error: reference to 'int64_t' is ambiguous
    In file included from /usr/include/stdlib.h:314:0,
                     from /usr/include/c++/4.7/cstdlib:66,
                     from /usr/include/boost/config/platform/linux.hpp:15,
                     from /usr/include/boost/config.hpp:53,
                     from /usr/include/boost/detail/workaround.hpp:41,
                     from /usr/include/boost/format.hpp:19,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:25:
    /usr/include/x86_64-linux-gnu/sys/types.h:197:1: error: candidates are: typedef long int int64_t
    In file included from /usr/include/boost/date_time/compiler_config.hpp:54:0,
                     from /usr/include/boost/date_time/posix_time/posix_time.hpp:14,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:26:
    /usr/include/boost/cstdint.hpp:308:50: error:                 typedef boost::long_long_type boost::int64_t
    /root/calpp-0.90/examples/coalescingtest.cpp:224:13: error: expected ';' before 'bytes'
    /root/calpp-0.90/examples/coalescingtest.cpp:225:29: error: 'bytes' was not declared in this scope
    make[2]: *** [examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o] Error 1
    make[1]: *** [examples/CMakeFiles/coalescingtest.dir/all] Error 2
    make: *** [all] Error 2
    root@b0x:~/calpp-0.90# 
    root@b0x:~/calpp-0.90# make install
    [  6%] Building CXX object examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o
    /root/calpp-0.90/examples/coalescingtest.cpp: In function 'void show_result(int, int)':
    /root/calpp-0.90/examples/coalescingtest.cpp:224:5: error: reference to 'int64_t' is ambiguous
    In file included from /usr/include/stdlib.h:314:0,
                     from /usr/include/c++/4.7/cstdlib:66,
                     from /usr/include/boost/config/platform/linux.hpp:15,
                     from /usr/include/boost/config.hpp:53,
                     from /usr/include/boost/detail/workaround.hpp:41,
                     from /usr/include/boost/format.hpp:19,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:25:
    /usr/include/x86_64-linux-gnu/sys/types.h:197:1: error: candidates are: typedef long int int64_t
    In file included from /usr/include/boost/date_time/compiler_config.hpp:54:0,
                     from /usr/include/boost/date_time/posix_time/posix_time.hpp:14,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:26:
    /usr/include/boost/cstdint.hpp:308:50: error:                 typedef boost::long_long_type boost::int64_t
    /root/calpp-0.90/examples/coalescingtest.cpp:224:13: error: expected ';' before 'bytes'
    /root/calpp-0.90/examples/coalescingtest.cpp:225:29: error: 'bytes' was not declared in this scope
    make[2]: *** [examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o] Error 1
    make[1]: *** [examples/CMakeFiles/coalescingtest.dir/all] Error 2
    make: *** [all] Error 2
    Last edited by tr00n3r; 2014-09-23 at 09:45.

  9. #9
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by tr00n3r View Post
    I have tried with the driver from SID and AMDAPPSDK-2.9-1 (fresh 64bit installation) only did upgrade, added sid for driver, installed driver, removed sid and followed your guide
    Code:
    root@b0x:~# fglrxinfo 
    display: :0.0  screen: 0
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: AMD Radeon R9 200 Series
    OpenGL version string: 4.4.12968 Compatibility Profile Context 14.201.1006.1002
    fglrx is loaded
    Code:
    root@b0x:~# lsmod | grep -i fglrx
    fglrx                9171703  81 
    button                 12944  1 fglrx

    and in use

    Code:
    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0] (prog-if 00 [VGA controller])
    	Subsystem: Tul Corporation / PowerColor Device [148c:2342]
    	Flags: bus master, fast devsel, latency 0, IRQ 47
    	Memory at e0000000 (64-bit, prefetchable) [size=256M]
    	Memory at f0000000 (64-bit, prefetchable) [size=8M]
    	I/O ports at e000 [size=256]
    	Memory at f7e00000 (32-bit, non-prefetchable) [size=256K]
    	Expansion ROM at f7e40000 [disabled] [size=128K]
    	Capabilities: [48] Vendor Specific Information: Len=08 <?>
    	Capabilities: [50] Power Management version 3
    	Capabilities: [58] Express Legacy Endpoint, MSI 00
    	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    	Capabilities: [150] Advanced Error Reporting
    	Capabilities: [200] #15
    	Capabilities: [270] #19
    	Capabilities: [2b0] Address Translation Service (ATS)
    	Capabilities: [2c0] #13
    	Capabilities: [2d0] #1b
    	Kernel driver in use: fglrx_pci

    Code:
    root@b0x:~/calpp-0.90# cmake .
    -- The C compiler identification is GNU 4.7.4
    -- The CXX compiler identification is GNU 4.7.4
    -- Check for working C compiler: /usr/bin/gcc
    -- Check for working C compiler: /usr/bin/gcc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Boost version: 1.49.0
    -- Found the following Boost libraries:
    --   date_time
    -- ===========================================================
    -- ATI CAL include directory /opt/AMDAPPSDK-2.9-1/include/CAL
    -- ATI CAL cl library directory /usr/lib/x86_64-linux-gnu
    -- ATI CAL rt library directory /usr/lib/x86_64-linux-gnu
    -- Boost version 1_49
    -- ===========================================================
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /root/calpp-0.90
    root@b0x:~/calpp-0.90# 
    root@b0x:~/calpp-0.90# make
    Scanning dependencies of target coalescingtest
    [  6%] Building CXX object examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o
    /root/calpp-0.90/examples/coalescingtest.cpp: In function 'void show_result(int, int)':
    /root/calpp-0.90/examples/coalescingtest.cpp:224:5: error: reference to 'int64_t' is ambiguous
    In file included from /usr/include/stdlib.h:314:0,
                     from /usr/include/c++/4.7/cstdlib:66,
                     from /usr/include/boost/config/platform/linux.hpp:15,
                     from /usr/include/boost/config.hpp:53,
                     from /usr/include/boost/detail/workaround.hpp:41,
                     from /usr/include/boost/format.hpp:19,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:25:
    /usr/include/x86_64-linux-gnu/sys/types.h:197:1: error: candidates are: typedef long int int64_t
    In file included from /usr/include/boost/date_time/compiler_config.hpp:54:0,
                     from /usr/include/boost/date_time/posix_time/posix_time.hpp:14,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:26:
    /usr/include/boost/cstdint.hpp:308:50: error:                 typedef boost::long_long_type boost::int64_t
    /root/calpp-0.90/examples/coalescingtest.cpp:224:13: error: expected ';' before 'bytes'
    /root/calpp-0.90/examples/coalescingtest.cpp:225:29: error: 'bytes' was not declared in this scope
    make[2]: *** [examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o] Error 1
    make[1]: *** [examples/CMakeFiles/coalescingtest.dir/all] Error 2
    make: *** [all] Error 2
    root@b0x:~/calpp-0.90# 
    root@b0x:~/calpp-0.90# make install
    [  6%] Building CXX object examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o
    /root/calpp-0.90/examples/coalescingtest.cpp: In function 'void show_result(int, int)':
    /root/calpp-0.90/examples/coalescingtest.cpp:224:5: error: reference to 'int64_t' is ambiguous
    In file included from /usr/include/stdlib.h:314:0,
                     from /usr/include/c++/4.7/cstdlib:66,
                     from /usr/include/boost/config/platform/linux.hpp:15,
                     from /usr/include/boost/config.hpp:53,
                     from /usr/include/boost/detail/workaround.hpp:41,
                     from /usr/include/boost/format.hpp:19,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:25:
    /usr/include/x86_64-linux-gnu/sys/types.h:197:1: error: candidates are: typedef long int int64_t
    In file included from /usr/include/boost/date_time/compiler_config.hpp:54:0,
                     from /usr/include/boost/date_time/posix_time/posix_time.hpp:14,
                     from /root/calpp-0.90/examples/coalescingtest.cpp:26:
    /usr/include/boost/cstdint.hpp:308:50: error:                 typedef boost::long_long_type boost::int64_t
    /root/calpp-0.90/examples/coalescingtest.cpp:224:13: error: expected ';' before 'bytes'
    /root/calpp-0.90/examples/coalescingtest.cpp:225:29: error: 'bytes' was not declared in this scope
    make[2]: *** [examples/CMakeFiles/coalescingtest.dir/coalescingtest.cpp.o] Error 1
    make[1]: *** [examples/CMakeFiles/coalescingtest.dir/all] Error 2
    make: *** [all] Error 2
    I just finished installing Kali on my desktop so I'm working on it now. I'll let you know how I go.
    chown -R us ./base

  10. #10
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Good news and bad news.

    You can get past that error by:

    nano /usr/include/boost/cstdint.hpp

    and then find

    Code:
         typedef  ::boost::long_long_type            intmax_t;
         typedef  ::boost::ulong_long_type   uintmax_t;
         typedef  ::boost::long_long_type            int64_t;
         typedef  ::boost::long_long_type            int_least64_t;
         typedef  ::boost::long_long_type            int_fast64_t;
         typedef  ::boost::ulong_long_type   uint64_t;
         typedef  ::boost::ulong_long_type   uint_least64_t;
         typedef  ::boost::ulong_long_type   uint_fast64_t;
    and replace with

    Code:
         typedef  ::boost::long_long_type            intmax_t;
         typedef  ::boost::ulong_long_type   uintmax_t;
         typedef  long int int64_t;
         typedef  ::boost::long_long_type            int_least64_t;
         typedef  ::boost::long_long_type            int_fast64_t;
         typedef  long unsigned int uint64_t;
         typedef  ::boost::ulong_long_type   uint_least64_t;
         typedef  ::boost::ulong_long_type   uint_fast64_t;
    Bad news is there is still a segmentation fault.

    Working on that...
    chown -R us ./base

  11. #11
    Join Date
    2013-Mar
    Posts
    57
    thank you so much for helping me!!!!!!

    yeah, I found this solution 5 min ago in blackmoreops' guide and tested --> segmentation fault
    another question: did you update the gcc version during driver installation in SID from GNU 4.7.2 to GNU 4.7.4 because I did - was this a good idea?

    ****************EDIT****************
    tested without updating libc6 - driver install will fail
    Last edited by tr00n3r; 2014-09-23 at 10:52.

  12. #12
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    I didn't get it to work tonight. I'll keep at it tomorrow. Others have had success without using latest drivers.

    Tomorrow I'll try Kali 1.0.9 with drivers from the normal repo and amd app SDK. The difference is, I'll replace all instances of AMD-APP-SDK-v2.9-1 with AMDAPP from that below from a post on blackmoreops

    OPENCL_INC_DIRS = ['/opt/AMDAPP/include/']
    OPENCL_LIB_DIRS = ['/opt/AMDAPP/lib/x86_64/']
    chown -R us ./base

  13. #13
    Join Date
    2013-Mar
    Posts
    57
    alright, will try this too! Thanks again for your help!

  14. #14
    Join Date
    2014-Jun
    Posts
    5
    hey guys i followed the tutorial exactly but got the following error:

    root@kali:~# pyrit list_cores
    terminate called after throwing an instance of 'cal::Error'
    what(): Operational error
    Aborted


    just to mention that i tried the OPENCL before that and it worked with pyrit!!

    any ideas?

  15. #15
    Join Date
    2013-Mar
    Posts
    57
    what card are you using?

    pleae show lspci --nnkv (for card/vga section)
    and
    dmesg | tail when errors happens.

  16. #16
    Join Date
    2013-Mar
    Posts
    57
    staticn0de,

    did you figure something out about CAL++ and R9 290X ?

    greetz

  17. #17
    Join Date
    2014-Jun
    Posts
    5
    im using kali 1.0.9 32 bits yet my machine is 64 bits on switchable graphics intel hd4000/AMD Radeon HD 8730M



    root@kali:~# lspci -nnkv

    00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, fast devsel, latency 0
    Capabilities: [e0] Vendor Specific Information: Len=0c <?>

    00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=01, subordinate=06, sec-latency=0
    I/O behind bridge: 00003000-00003fff
    Memory behind bridge: c0000000-c0ffffff
    Prefetchable memory behind bridge: 00000000a0000000-00000000afffffff
    Capabilities: [88] Subsystem: Dell Device [1028:05b8]
    Capabilities: [80] Power Management version 3
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [a0] Express Root Port (Slot+), MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [140] Root Complex Link
    Kernel driver in use: pcieport

    00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, fast devsel, latency 0, IRQ 47
    Memory at c1000000 (64-bit, non-prefetchable) [size=4M]
    Memory at b0000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 4000 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [d0] Power Management version 2
    Capabilities: [a4] PCI Advanced Features
    Kernel driver in use: i915

    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Mars [Radeon HD 8500/8700M Series] [1002:6601] (prog-if 00 [VGA controller])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, fast devsel, latency 0, IRQ 48
    Memory at a0000000 (64-bit, prefetchable) [size=256M]
    Memory at c0000000 (64-bit, non-prefetchable) [size=256K]
    I/O ports at 3000 [size=256]
    Expansion ROM at c0040000 [disabled] [size=128K]
    Capabilities: [48] Vendor Specific Information: Len=08 <?>
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    Capabilities: [150] Advanced Error Reporting
    Capabilities: [270] #19
    Kernel driver in use: fglrx_pci



    00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, medium devsel, latency 0, IRQ 42
    Memory at c1600000 (64-bit, non-prefetchable) [size=64K]
    Capabilities: [70] Power Management version 2
    Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
    Kernel driver in use: xhci_hcd

    00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, fast devsel, latency 0, IRQ 44
    Memory at c1614000 (64-bit, non-prefetchable) [size=16]
    Capabilities: [50] Power Management version 3
    Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Kernel driver in use: mei_me

    00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, medium devsel, latency 0, IRQ 16
    Memory at c1619000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci-pci

    00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, fast devsel, latency 0, IRQ 46
    Memory at c1610000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
    Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [130] Root Complex Link
    Kernel driver in use: snd_hda_intel

    00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
    I/O behind bridge: 00002000-00002fff
    Prefetchable memory behind bridge: 00000000c1400000-00000000c14fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: Dell Device [1028:05b8]
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

    00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
    Memory behind bridge: c1500000-c15fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: Dell Device [1028:05b8]
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

    00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, medium devsel, latency 0, IRQ 23
    Memory at c1618000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci-pci

    00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04)
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, medium devsel, latency 0
    Capabilities: [e0] Vendor Specific Information: Len=0c <?>
    Kernel driver in use: lpc_ich

    00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) (prog-if 01 [AHCI 1.0])
    Subsystem: Dell Device [1028:05b8]
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 43
    I/O ports at 4088 [size=8]
    I/O ports at 4094 [size=4]
    I/O ports at 4080 [size=8]
    I/O ports at 4090 [size=4]
    I/O ports at 4060 [size=32]
    Memory at c1617000 (32-bit, non-prefetchable) [size=2K]
    Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [70] Power Management version 3
    Capabilities: [a8] SATA HBA v1.0
    Capabilities: [b0] PCI Advanced Features
    Kernel driver in use: ahci

    00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
    Subsystem: Dell Device [1028:05b8]
    Flags: medium devsel, IRQ 19
    Memory at c1615000 (64-bit, non-prefetchable) [size=256]
    I/O ports at 4040 [size=32]
    Last edited by elios115; 2014-09-29 at 21:31.

  18. #18
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by tr00n3r View Post
    staticn0de,

    did you figure something out about CAL++ and R9 290X ?

    greetz
    Hey mate,

    I could not get it working. I did some looking around and we are not alone with the seg faults on a 290X.

    A lot of users of related software (bionic ect) have the same problems.

    ATI released 14.9 today. I'll give it a go with that.
    chown -R us ./base

  19. #19
    Join Date
    2014-Aug
    Posts
    2
    Quote Originally Posted by staticn0de View Post
    Hey mate,

    I could not get it working. I did some looking around and we are not alone with the seg faults on a 290X.

    A lot of users of related software (bionic ect) have the same problems.

    ATI released 14.9 today. I'll give it a go with that.
    No success for me with new driver.

  20. #20
    Join Date
    2013-Mar
    Posts
    57
    do we have any news for the R9 290x cards?

  21. #21
    Join Date
    2014-Dec
    Posts
    5
    Hi im going to start this tomorrow with my amd radeon hd 7520g graphics card but i was wondering if this setup can work with cgminer 3.7.2 aswell? I was going to try it loosely using this guide:
    http://www.distrogeeks.com/install-c...-3-7-2-ubuntu/

    Replacing the opencl steps with Cal++

  22. #22
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    Huh i made everything like in tutorial... instalation went ok, but after trying to run pyrit ive got error: segmentation fault

  23. #23
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    Ok, I removed old installation and installed pyrit + cpyrit_opencl. It finnaly works with my Radeon R9 290....

    Pyrit 0.4.1-dev (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
    This code is distributed under the GNU General Public License v3+

    Running benchmark (85733.9 PMKs/s)...

  24. #24
    Join Date
    2014-Dec
    Posts
    2
    hi,@ staticn0de
    have you any idea with AMD Radeon (TM) HD 8500M/8700M works?
    i have installed fglrx, amdappsdk2.7, cal++ and reinstalled pyrit many times. and output was always
    root@kali:~# pyrit
    terminate called after throwing an instance of 'cal::Error'
    what(): Operational error
    or
    sometimes i don't konw how i reinstalled pyrit and pyrit works but without cal++ just like the original version.

    can you help me with my best wishes!

  25. #25
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    Are there any news about R9 290/290X ? Im still working on Pyrit OpenCL, cause my Pyrit Calpp crashes.

  26. #26
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    Is there anyone who knows why does CAL++ doesn't work with R290/290X ? Or how make it work ? It would be nice to get 40% more power in cracking wpa2.

    Somebody here got pyrit with r290 ? What benchmark score do You have?

  27. #27
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Bad news,

    http://sourceforge.net/p/calpp/bugs/6/

    Short answer is amd dropped support in newer hardware.

    It is unlikely anyone will ever get it working on the cutting edge cards.
    chown -R us ./base

  28. #28
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    ok thanks for the response... So i guess that its better to use 7970 instead of R9 290/290x cause it gets more PMKs on CAL++, it is cheaper and consumes less electricity.

  29. #29
    Join Date
    2014-Dec
    Location
    Poland
    Posts
    27
    OK, I've tested this today, R9 290 + R7970 in OpenCL = ~150k PMKs

    then i run only R7970 with CAL++ and it was ~130k PMKs.

    R9 is going for sell to setup 3x7970.

  30. #30
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by buggie View Post
    OK, I've tested this today, R9 290 + R7970 in OpenCL = ~150k PMKs

    then i run only R7970 with CAL++ and it was ~130k PMKs.

    R9 is going for sell to setup 3x7970.
    Thanks for posting the comparison, I know I (and I'm sure others) appreciate it.

    The 7970 may be the current best card for cal++
    chown -R us ./base

  31. #31
    Join Date
    2013-Mar
    Posts
    57
    hmmm, **** it!

    @staticn0de
    thanks for your research to get the x290 in working condition.

    Now I have a great graphic card but it's not woring with CAL++

  32. #32
    Join Date
    2013-Mar
    Posts
    57
    another question:
    does the problem also exists with a HD7990 card? or will the card work with cal++? want to know before I will buy one of these

  33. #33
    Join Date
    2015-Apr
    Posts
    5

    Smile Thanks staticn0de

    Thanks staticn0de for great Guide,

    my result with R7970 (1GHz):

    Computed 124947.10 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 123353.2 PMKs/s (RTT 1.1)
    #2: 'CPU-Core (SSE2)': 680.1 PMKs/s (RTT 3.0)
    #3: 'CPU-Core (SSE2)': 672.5 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 678.6 PMKs/s (RTT 3.0)

    unfortunately after activation crossfire in ccc the result was strange

    Computed 114017.44 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 56525.5 PMKs/s (RTT 1.7)
    #2: 'CAL++ Device #2 'AMD GPU DEVICE'': 56776.0 PMKs/s (RTT 1.7)
    #3: 'CPU-Core (SSE2)': 757.2 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 756.1 PMKs/s (RTT 3.0)

    the second card is also R7970
    Must i do something additional to get the full Speed?

    Quote Originally Posted by tr00n3r View Post
    another question:
    does the problem also exists with a HD7990 card? or will the card work with cal++? want to know before I will buy one of these
    Also very interesting question tr00n3r

  34. #34
    Join Date
    2015-Apr
    Posts
    5

    Performance Improvement

    After execution of following Steps:

    1. aticonfig --adapter=all –initial
    2. restarting X-Server
    3. export DISPLAY=:0

    i got

    Computed 200949.09 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 117284.7 PMKs/s (RTT 1.1)
    #2: 'CAL++ Device #2 'AMD GPU DEVICE'': 84111.8 PMKs/s (RTT 1.2)
    #3: 'CPU-Core (SSE2)': 697.1 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 700.9 PMKs/s (RTT 3.0)

    much better

    I tried also to change "ncpus -= 1" to "ncpus -= 2" and "ncpus -= 4" under /usr/lib/pymodules/python2.6/cpyrit.py
    but the result still the same.

    It must be the way to get nearly the same PMKs/s with second HD7970.
    Any ideas?

  35. #35
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Hey guys,

    Sorry I have not replied sooner. Someone was trying to access my account here on the forums and they constantly triggered the incorrect login screen, effectively locking us both out.

    Seems like you sorted it all out without me anyway! I had the same situation with my dual HD6970. One card was noticeably faster than the other. I couldn't find a way around it.

    I went and wrote it off as bus limitations or CPU or some other nonsense (I didn't really know) but others, including those using bionic had the same situation.

    Did you need to put export DISPLAY=:0 in again after a restart? that isn't a persistant setting. If you do, just add it to ~/.bashrc
    chown -R us ./base

  36. #36
    Join Date
    2015-Apr
    Posts
    5

    Hd7990

    Hallo,

    indeed that isn't a persistant setting. My whole system is under construction and raw. But at the end ~/.bashrc will be set.

    By the way, i got a chance to test one HD7990. Here is the result (after DISPLAY=:0):

    Computed 195779.45 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 111024.9 PMKs/s (RTT 1.1)
    #2: 'CAL++ Device #2 'AMD GPU DEVICE'': 84497.1 PMKs/s (RTT 1.1)
    #3: 'CPU-Core (SSE2)': 695.3 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 701.9 PMKs/s (RTT 3.0)

    The same problem.
    Interesting is, how much will produce the third GPU?
    Without DISPLAY=:0 each chip perform 50.000-60.000 PMks/s

    Please let me know staticn0de if you find any way to boost the results on second GPU.

  37. #37
    Join Date
    2015-Apr
    Posts
    1
    Hi staticn0de,

    thanks for the excellent guide. Everything works, and I'm on a fresh install of kali 1.1.0a.

    Only one issue, I can't run pyrit in any of the terminals without first logging into gnome. This also means I can't run pyrit through SSH without first logging into the GUI on the host. Perhaps the drivers haven't loaded yet?
    Any insight would be a great help!

  38. #38
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Grunski View Post
    Hallo,

    indeed that isn't a persistant setting. My whole system is under construction and raw. But at the end ~/.bashrc will be set.

    By the way, i got a chance to test one HD7990. Here is the result (after DISPLAY=:0):

    Computed 195779.45 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 111024.9 PMKs/s (RTT 1.1)
    #2: 'CAL++ Device #2 'AMD GPU DEVICE'': 84497.1 PMKs/s (RTT 1.1)
    #3: 'CPU-Core (SSE2)': 695.3 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 701.9 PMKs/s (RTT 3.0)

    The same problem.
    Interesting is, how much will produce the third GPU?
    Without DISPLAY=:0 each chip perform 50.000-60.000 PMks/s

    Please let me know staticn0de if you find any way to boost the results on second GPU.
    Hi there,

    I've been working on this a bit tonight and have some good news and some bad news.

    The good news is, you can get second card to be just about the same speed as the first! See below for my initial setup as per the guide before I made changes.

    Code:
    #1: 'CAL++ Device #1 'AMD CAYMAN'': 81018.0 PMKs/s (RTT 1.2)
    #2: 'CAL++ Device #2 'AMD CAYMAN'': 47461.8 PMKs/s (RTT 1.5)
    #3: 'CPU-Core (SSE2/AES)': 699.7 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2/AES)': 668.8 PMKs/s (RTT 3.0)
    #5: 'CPU-Core (SSE2/AES)': 680.9 PMKs/s (RTT 2.9)
    #6: 'CPU-Core (SSE2/AES)': 730.4 PMKs/s (RTT 2.9)
    #7: 'CPU-Core (SSE2/AES)': 698.4 PMKs/s (RTT 2.9)
    #8: 'CPU-Core (SSE2/AES)': 655.1 PMKs/s (RTT 3.0)
    My results after changes

    Code:
    Computed 156874.93 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD CAYMAN'': 81071.2 PMKs/s (RTT 1.2)
    #2: 'CAL++ Device #2 'AMD CAYMAN'': 80010.4 PMKs/s (RTT 1.2)
    #3: 'CPU-Core (SSE2/AES)': 1196.1 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2/AES)': 1204.6 PMKs/s (RTT 2.9)
    The bad news is, the settings we are changing are setup specific. What I chose through trial and error may not lead to the same result for you. I'll include a few combinations I tried to give you an idea.

    1. For the fixing, the most important change I made is turning off hyperthreading. This gave me a massive increase. As it turns out, the CPU was the bottleneck after all.

    Second, we have some values we can modify. Each time we chage them, we have to re-build and reinstall that component (not as hard as it sounds)

    2. Changing the buffer size

    If you followed the guide, this should work

    Code:
    nano +52 /root/pyrit_svn/cpyrit_calpp/_cpyrit_calpp.cpp
    
    change the value between 1 and 4. I had the best performance on 2 and the worst on 1.
    3. Rebuilding the cal module for pyrit
    Code:
    You need this step after each buffer size change
    
    root@kali ~/pyrit_svn/cpyrit_calpp$ python setup.py build
    
    root@kali ~/pyrit_svn/cpyrit_calpp$ python setup.py install
    4. Modify CAL itself. This setting is either on, or it's off. I had the best speeds with it on.
    Code:
    nano +45 /root/calpp-0.90/include/cal/cal.hpp
    
    Change the line by removing the leading '//' so it looks like this
    
    #define __CAL_USE_NON_BLOCKING_WAIT 1
    5. Rebuild call++
    Code:
    cd /root/calpp-0.90/
    
    cmake .
    
    make
    
    make install
    Give pyrit benchmark a go and let me know. The result I had after I made this changes. Remember, turning off hyperthreading in the bios was the biggest speed boost.

    Best results for me:
    Buffer set 2
    HT off
    cal.hpp removed slashes

    Same as before, but buffer on 1
    Code:
    buffer set to 1
    Running benchmark (121551.8 PMKs/s)... \ 
    
    Computed 121551.82 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD CAYMAN'': 65645.1 PMKs/s (RTT 1.1)
    #2: 'CAL++ Device #2 'AMD CAYMAN'': 57752.2 PMKs/s (RTT 1.7)
    #3: 'CPU-Core (SSE2/AES)': 1227.4 PMKs/s (RTT 2.9)
    #4: 'CPU-Core (SSE2/AES)': 1227.7 PMKs/s (RTT 3.0)
    root@kali-corsair:~/pyrit_svn/pyrit#
    Last edited by staticn0de; 2015-04-17 at 12:46.
    chown -R us ./base

  39. #39
    Join Date
    2015-Apr
    Posts
    5
    Thanks statikn0de,

    my best result with HD 7990 was:

    Computed 214303.81 PMKs/s total.
    #1: 'CAL++ Device #1 'AMD GPU DEVICE'': 122460.0 PMKs/s (RTT 1.1)
    #2: 'CAL++ Device #2 'AMD GPU DEVICE'': 91421.1 PMKs/s (RTT 1.1)
    #3: 'CPU-Core (SSE2)': 712.9 PMKs/s (RTT 3.0)
    #4: 'CPU-Core (SSE2)': 716.4 PMKs/s (RTT 3.0)

    Buffer set 3
    cal.hpp with slashes
    HT was not necessary to disable with my Intel i5 750. Maybe I upgrade a system later to i7, but not now

    With your best setting:
    Buffer set 2
    cal.hpp removed slashes

    It was only
    111490.0 PMKs/s (first GPU)
    80840.0 kPMKs/s (second GPU)

    It is a significant improvement to the result of my last post. Thanks again.

  40. #40
    Join Date
    2015-Apr
    Posts
    5
    Hi,
    i tried to play with bios settings, especially CPU settings without success.
    I don't think that for the similar boosting i need i7 with Hyperthreading (and this Hyperthreading must be deactivated).
    Maybe my Motherboard ( Asus P7P55D LE ) is to old.
    Which one CPU do you have staticn0de?

  41. #41
    Join Date
    2014-Apr
    Location
    Down Under
    Posts
    315
    Quote Originally Posted by Grunski View Post
    Hi,
    i tried to play with bios settings, especially CPU settings without success.
    I don't think that for the similar boosting i need i7 with Hyperthreading (and this Hyperthreading must be deactivated).
    Maybe my Motherboard ( Asus P7P55D LE ) is to old.
    Which one CPU do you have staticn0de?
    That one is an i7-2600k @4.5Ghz
    chown -R us ./base

  42. #42
    Join Date
    2015-Jun
    Posts
    1
    Hi,
    I got up to the aticonfig --initial. I got a reply: aticonfig: No supported adapters. I have a 280x. Is there way to solve this?
    Thanks.

  43. #43
    Join Date
    2015-Jun
    Posts
    1
    Hi everyone
    Im running kali on acer aspire one 722
    Tried to install proprietary drivers + sdk + cal++ but wasnt succeed
    I was following the manual posted on black more ops
    Is it REALLY possible to instal that all with my configuration?

    00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller])
    Subsystem: Acer Incorporated [ALI] Device [1025:0598]
    Flags: bus master, fast devsel, latency 0, IRQ 25
    Memory at 80000000 (32-bit, prefetchable) [size=256M]
    I/O ports at 4000 [size=256]
    Memory at 90400000 (32-bit, non-prefetchable) [size=256K]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
    Kernel driver in use: radeon


    thanks to all

  44. #44
    Join Date
    2015-Jun
    Posts
    1
    Hello staticn0de,

    Thanks for this tutorial, but I am getting stuck on step 16.

    cmake . command completes with errors

    -- The C compiler identification is GNU 4.7.2
    -- The CXX compiler identification is GNU 4.7.2
    -- Check for working C compiler: /usr/bin/gcc
    -- Check for working C compiler: /usr/bin/gcc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Boost version: 1.49.0
    -- Found the following Boost libraries:
    -- date_time
    -- ================================================== =========
    -- ATI CAL include directory LIB_ATICAL_INCLUDE-NOTFOUND
    -- ATI CAL cl library directory /usr/lib/x86_64-linux-gnu
    -- ATI CAL rt library directory /usr/lib/x86_64-linux-gnu
    -- Boost version 1_49
    -- ================================================== =========
    CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
    Please set them or make sure they are set and tested correctly in the CMake files:
    LIB_ATICAL_INCLUDE
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/examples
    used as include directory in directory /root/calpp-0.90/regression
    used as include directory in directory /root/calpp-0.90/regression

    -- Configuring incomplete, errors occurred!


    and the following make & make install commands error

    make: *** No targets specified and no makefile found. Stop.

    I am sure it is something simple and silly I am missing, but if you could help out that would be great.

    Thanks

Similar Threads

  1. Replies: 10
    Last Post: 2016-03-03, 20:37
  2. Having severe difficulty with FGLRX /pyrit/cowpatty using KALI
    By theoctavist in forum General Archive
    Replies: 0
    Last Post: 2015-08-27, 23:46
  3. (Guide) Installing fglrx 14.12 (omega) on Kali 1.1.0
    By staticn0de in forum How-To Archive
    Replies: 9
    Last Post: 2015-08-21, 05:45
  4. Unable to use pyrit with 2 cards
    By ch3kmate in forum General Archive
    Replies: 0
    Last Post: 2014-10-10, 07:15
  5. nvidia 'optimus' (2 video cards) on kali
    By Quest in forum Installing Archive
    Replies: 1
    Last Post: 2014-07-07, 09:26

Posting Permissions

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