Bitcoin Forum
July 25, 2021, 12:18:46 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 463 »
  Print  
Author Topic: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 669496 times)
Ursul0
Sr. Member
****
Offline Offline

Activity: 843
Merit: 262


View Profile
November 23, 2019, 03:55:46 PM
 #3941

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"
that's interesting. make sure you have like 70GB of virtual memory(swap file) and maybe try two instances of the miner with -amd  and  -nvidia options  (or -di option if it supports such a large enum...) and please report back  Smiley
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1627172326
Hero Member
*
Offline Offline

Posts: 1627172326

View Profile Personal Message (Offline)

Ignore
1627172326
Reply with quote  #2

1627172326
Report to moderator
1627172326
Hero Member
*
Offline Offline

Posts: 1627172326

View Profile Personal Message (Offline)

Ignore
1627172326
Reply with quote  #2

1627172326
Report to moderator
Bigdrago
Newbie
*
Offline Offline

Activity: 312
Merit: 0


View Profile
November 23, 2019, 04:04:00 PM
 #3942

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"

Not 17+...but working great with 13
joeykolb
Newbie
*
Offline Offline

Activity: 81
Merit: 0


View Profile
November 23, 2019, 07:22:25 PM
 #3943

after some modes on my rx s(with phoenix miner) , some of the rx 580 doesnt even start on the risers

any help?
ditec
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 23, 2019, 08:18:20 PM
 #3944

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"

Not 17+...but working great with 13
even with 16
ditec
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 23, 2019, 10:14:13 PM
 #3945

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"
that's interesting. make sure you have like 70GB of virtual memory(swap file) and maybe try two instances of the miner with -amd  and  -nvidia options  (or -di option if it supports such a large enum...) and please report back  Smiley
i'm using Linux
i've tried 2 instances of the same miner, i've tried 2 instances of different miners, i've tried to mine with 16 cards while there were 18 in the rig.... always the same thing
Ursul0
Sr. Member
****
Offline Offline

Activity: 843
Merit: 262


View Profile
November 24, 2019, 08:00:33 AM
 #3946

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"
that's interesting. make sure you have like 70GB of virtual memory(swap file) and maybe try two instances of the miner with -amd  and  -nvidia options  (or -di option if it supports such a large enum...) and please report back  Smiley
i'm using Linux
i've tried 2 instances of the same miner, i've tried 2 instances of different miners, i've tried to mine with 16 cards while there were 18 in the rig.... always the same thing

I'm not sure what segmentation fault there is, but it very well could be that the OS cannot map all the memory of the GPUs properly. try to play with the drivers and reduce number of cards and see where it dies on you. also mb bios could be an issue. (I'm running 12GPU rigs since the very first AMD driver version that started to support more than 8...)
ditec
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 25, 2019, 02:55:48 AM
 #3947

Does anybody made this miner work on large rigs (17+ cards)?
i've tried 12x588+7p106-100 on HiveOS, but i've got only "segmentation fault  waiting to cooldown"
that's interesting. make sure you have like 70GB of virtual memory(swap file) and maybe try two instances of the miner with -amd  and  -nvidia options  (or -di option if it supports such a large enum...) and please report back  Smiley
i'm using Linux
i've tried 2 instances of the same miner, i've tried 2 instances of different miners, i've tried to mine with 16 cards while there were 18 in the rig.... always the same thing

I'm not sure what segmentation fault there is, but it very well could be that the OS cannot map all the memory of the GPUs properly. try to play with the drivers and reduce number of cards and see where it dies on you. also mb bios could be an issue. (I'm running 12GPU rigs since the very first AMD driver version that started to support more than 8...)
everything works great with 16 cards or less. and there is "segmentation fault" in the miner log
PhoenixMiner
Member
**
Offline Offline

Activity: 338
Merit: 79


View Profile
November 25, 2019, 09:05:36 AM
 #3948

    PhoenixMiner 4.8c is officially released. You can find the download link and the checksums in the first post of this thread.

    The new features in this release are:

    • Added command-line option -gbase to set 0-base or 1-based GPU indexes (the default is 1). With -gbase 1 (the default), the first GPU is GPU1, then GPU2, etc. With -gbase 0 the first GPU is GPU0, second - GPU1, etc. Note that this also changes the indexes that are used with all command line options that accept GPU indexes (e.g. -gpus) as well as these used with the interactive commands on the miner shell window

    Here are the other features from 4.8b:

    • Added support for the latest AMD drivers under Linux 19.30-934563 and for mining with RX5700 cards under Linux. Note that drivers are quite buggy and most of the overclocking options don't work, as well as most of the hardware monitoring options.
    • Added a new flexible way for setting GPU-specific options with selectors. Example: -cclock 1-3:1090,4:1300 -mclock nvidia:+450,amd:2000,*:1900,gtx*1070*ti:+200 See bellow for more information
    • Validated support for the latest AMD Windows drivers 19.11.3 (but they already work with 4.7c because there were no significant changes in the OpenCL driver)

    About the AMD Linux drivers 19.30-934563:

    These drivers finally fix the RX5700 TLB problem but they are not perfect:
    - Most of the hardware monitoring options don't work for RX5700 cards - even the temperature is not reported correctly. Only the power usage, fan speed, and core voltage are reported.
    - Almost all hardware control options don't work for RX5700 cards either with the notable exception of power limit, so the only way to avoid wasting power is to use -powlim -45 or something like this. The fan control options doesn't work either so you will be relying on auto-fan.

    About the new selectors for the GPU-specific options:

    This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clock to 1100 MHz
    for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz.

    The part before the colon : is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be:
      - single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU
      - range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5
      - asterisk, which sets the value for all GPUs
      - label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards
      - arbitrary string that starts with letter and can contain letters, numbers and asterisks, which is matched against the GPU name as listed by PhoenixMiner.
        Example: gtx*1070:+500 will set value +500 for all cards which contain 'gtx' and '1070' in their names with anything
        between them. This will match 'Nvidia GeForce GTX 1070' but not 'Nvidia GeForce 1070'.
       
    Note that if more than one selector matches given card, than only the last one counts.
    Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090;
    and the rest of the cards to 1100 MHz core clock.
    VasilyS
    Member
    **
    Offline Offline

    Activity: 586
    Merit: 18


    View Profile WWW
    November 25, 2019, 11:19:15 AM
     #3949

    4.8c is not working on RX cards on Windows 10 with 18.6.1 drivers (constant crashes). Nvidia cards work perfectly. I switched my AMD rigs back to 4.8b.

                                 ❱  CRYPTOPROFI  ❱
    UnclWish
    Sr. Member
    ****
    Offline Offline

    Activity: 1442
    Merit: 253


    View Profile
    November 25, 2019, 01:35:01 PM
     #3950

    4.8c is not working on RX cards on Windows 10 with 18.6.1 drivers (constant crashes). Nvidia cards work perfectly. I switched my AMD rigs back to 4.8b.
    4.8c works perfectly on RX cards on Windows 10 with latest 19.11.3 drivers (no crashes). Just update your drivers, stop to use more than year old drivers.
    VasilyS
    Member
    **
    Offline Offline

    Activity: 586
    Merit: 18


    View Profile WWW
    November 25, 2019, 01:38:30 PM
     #3951

    4.8c is not working on RX cards on Windows 10 with 18.6.1 drivers (constant crashes). Nvidia cards work perfectly. I switched my AMD rigs back to 4.8b.
    4.8c works perfectly on RX cards on Windows 10 with latest 19.11.3 drivers (no crashes). Just update your drivers, stop to use more than year old drivers.
    18.6.1 driver is the best for mining for RX cards if you compare hashrate and stability with latest ones. 4.8c is buggy and there is nothing significant for mining.

                                 ❱  CRYPTOPROFI  ❱
    UnclWish
    Sr. Member
    ****
    Offline Offline

    Activity: 1442
    Merit: 253


    View Profile
    November 25, 2019, 01:48:35 PM
     #3952

    4.8c is not working on RX cards on Windows 10 with 18.6.1 drivers (constant crashes). Nvidia cards work perfectly. I switched my AMD rigs back to 4.8b.
    4.8c works perfectly on RX cards on Windows 10 with latest 19.11.3 drivers (no crashes). Just update your drivers, stop to use more than year old drivers.
    18.6.1 driver is the best for mining for RX cards if you compare hashrate and stability with latest ones. 4.8c is buggy and there is nothing significant for mining.
    19.11.3 has no difference on speed and stability if compare hashrate and stability with any previous ones. 4.8c has no bugs and works fine.
    I personally install all drivers allready several years, and check them. No changes in speed and stability. You just didn't try.
    VasilyS
    Member
    **
    Offline Offline

    Activity: 586
    Merit: 18


    View Profile WWW
    November 25, 2019, 01:55:45 PM
     #3953

    4.8c is not working on RX cards on Windows 10 with 18.6.1 drivers (constant crashes). Nvidia cards work perfectly. I switched my AMD rigs back to 4.8b.
    4.8c works perfectly on RX cards on Windows 10 with latest 19.11.3 drivers (no crashes). Just update your drivers, stop to use more than year old drivers.
    18.6.1 driver is the best for mining for RX cards if you compare hashrate and stability with latest ones. 4.8c is buggy and there is nothing significant for mining.
    19.11.3 has no difference on speed and stability if compare hashrate and stability with any previous ones. 4.8c has no bugs and works fine.
    I personally install all drivers allready several years, and check them. No changes in speed and stability. You just didn't try.
    OK, thank you! I gonna try 19.11.3.

                                 ❱  CRYPTOPROFI  ❱
    Trehjulingsleffe
    Newbie
    *
    Offline Offline

    Activity: 17
    Merit: 0


    View Profile
    November 25, 2019, 08:12:21 PM
     #3954

    I've seen that some of you guys have problem with allocating DAG on 4GB cards. What mobos and configs do you use?

    Never once i had encounter that problem and some of you have even switched to Linux because of this. I have a really huge virtual memory config and the HDMI to monitor is on the motherboard iGPU-port (and of course activated in BIOS). Maybe that is the reason that some experience an issue and some not. Windows doesnt allocate any memory to my gpus at all what i can see.
    It is even possible to mine ETC at DAG #308 with total GPU memory usage at 3,56GB per GPU.

    Can you who have problems with allocating DAG size please share your configs?

    I have a rig with:

    Windows 10 pro
    Newest AMD drivers (19.11.3)
    64GB virtual memory
    Asus B250 Mining Expert
    Intel core i5 6500

    GPUs:
    6x Sapphire Nitro RX470 4GB Mining Edition
    2x Sapphire Nitro+ RX580 4GB
    1x Sapphire Nitro+ RX580 8GB
    1x MSI Radeon Vii 16gb

    2h4u
    Newbie
    *
    Offline Offline

    Activity: 55
    Merit: 0


    View Profile
    November 26, 2019, 06:05:20 AM
     #3955

    • Added command-line option -gbase to set 0-base or 1-based GPU indexes (the default is 1). With -gbase 1 (the default), the first GPU is GPU1, then GPU2, etc. With -gbase 0 the first GPU is GPU0, second - GPU1, etc. Note that this also changes the indexes that are used with all command line options that accept GPU indexes (e.g. -gpus) as well as these used with the interactive commands on the miner shell window

    Glory, glory, hallelujah!
    krinjah
    Sr. Member
    ****
    Offline Offline

    Activity: 784
    Merit: 256


    View Profile
    November 26, 2019, 12:54:00 PM
     #3956

    Hi,

    my Windows defender found a Trojan:Win32/Wacatac.B!ml in the folder of PhoenixMiner_4.8c (referring to PhoenixMiner.exe). Has anyone had the same? This trojan appears to be a severe one, I'm a bit nervous. Miner downloaded from the link in OP

    Thanks
    MATHReX
    Sr. Member
    ****
    Offline Offline

    Activity: 880
    Merit: 281


    View Profile
    November 26, 2019, 02:54:16 PM
     #3957

    Hi,

    my Windows defender found a Trojan:Win32/Wacatac.B!ml in the folder of PhoenixMiner_4.8c (referring to PhoenixMiner.exe). Has anyone had the same? This trojan appears to be a severe one, I'm a bit nervous. Miner downloaded from the link in OP

    Thanks

    I just ran a custom scan for the miner folder and Windows Defender didn't detect anything.
    Can you check the SHA-256 checksum of the zip file that you downloaded?
    Ursul0
    Sr. Member
    ****
    Offline Offline

    Activity: 843
    Merit: 262


    View Profile
    November 26, 2019, 05:41:22 PM
     #3958

    • Added command-line option -gbase to set 0-base or 1-based GPU indexes (the default is 1). With -gbase 1 (the default), the first GPU is GPU1, then GPU2, etc. With -gbase 0 the first GPU is GPU0, second - GPU1, etc. Note that this also changes the indexes that are used with all command line options that accept GPU indexes (e.g. -gpus) as well as these used with the interactive commands on the miner shell window

    Glory, glory, hallelujah!

    Lol yeah. indeed that's a welcome addition.
    I'm just a bit worried about earlier post regarding the 18.6.1 driver issues, as this is the driver that I use on all my polaris rigs.
    Bael
    Jr. Member
    *
    Offline Offline

    Activity: 87
    Merit: 2


    View Profile
    November 26, 2019, 10:12:17 PM
     #3959

    Hi

    I have a problem with version 4.8c, for some reason I do not detect the -gt option well and it always returns to autotunning.

    I've tried it in two rigs, with win 1903, in some 19.10.2 drivers and in another 19.11.1, I tried to put -gbase 1 and -gbase 0 in case it had to do with that, but nothing changed.

    I have put back the 4.7c version that works without problems.

    Any suggestions on what it could be?

    Apologies for writing bad english

    Greetings guys !! : )
    krinjah
    Sr. Member
    ****
    Offline Offline

    Activity: 784
    Merit: 256


    View Profile
    November 27, 2019, 07:48:21 AM
     #3960

    Hi,

    my Windows defender found a Trojan:Win32/Wacatac.B!ml in the folder of PhoenixMiner_4.8c (referring to PhoenixMiner.exe). Has anyone had the same? This trojan appears to be a severe one, I'm a bit nervous. Miner downloaded from the link in OP

    Thanks

    I just ran a custom scan for the miner folder and Windows Defender didn't detect anything.
    Can you check the SHA-256 checksum of the zip file that you downloaded?
    I don't know how to check the SHA-256 checksum, could you please help?

    Thank you!
    Pages: « 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 463 »
      Print  
     
    Jump to:  

    Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!