Plus the mb which has connection lights lights for every slot is lighting up slots l am not plugged into.
Tom M
I have traced this behavior to specific riser card bases. Apparently the mb was fine but the bases were not. Will resume riser base screening after resting.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Plus the mb which has connection lights lights for every slot is lighting up slots l am not plugged into.
Tom M
I have traced this behavior to specific riser card bases. Apparently, the mb was fine but the bases were not. Will resume riser base screening after resting.
After sleeping on the problem it turns out that Rx 5700 cards cause the multiple slots to light up/start but not the Rx 570/580 cards.
I have (finally) located what are possibly the slots I can plug Rx 5700 cards into. And am now testing that.
So AFAIK this is a motherboard hardware issue.
Ubuntu is still letting me logon (cross fingers).
Plan B: I have an untested H310-F Pro (used) that is basically a cut-down version of the B360-F Pro motherboard that I will try if my "workarounds" don't fly.
Plan C: I can most likely revert to the original locations for various GPUs if neither mining MB is going to work. Specifically, take the 5 Rx 5700's back to the AMD 2700x MB and add two Rx 580's to it. And replace the Nvidia cards on the AMD 3950x with 2 Rx 570 cards.
Just started a testing cycle for an Rx 5700 in one of the slots that apparently is not broken. Should have an answer later tonight or in the morning.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Plan B: I have an untested H310-F Pro (used) that is basically a cut-down version of the B360-F Pro motherboard that I will try if my "workarounds" don't fly.
I guess it is time for Plan B.
The MB has stopped booting.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Plan B: I have an untested H310-F Pro (used) that is basically a cut-down version of the B360-F Pro motherboard that I will try if my "workarounds" don't fly.
I guess it is time for Plan B.
The MB has stopped booting.
So I cleaned off my work bench for the first time in too long.
Dismounted the MSI B360-F Pro and plugged it into my "test rig" stuff.
I refuse to believe that blowing the dust off the MB and moving it to a "new" environment was all the "fix" I needed.
But there it is.
I still need to re-test the failing PCIe slots but it is quietly munching away on GR gpu tasks and U@H cpu tasks on my work bench.
===edit====
PCIe slots still showing multiple lighting up when plugged into certain single slots.
Its dead :(
====edit====again=======
It's Alive. No it's disabled...
Anyway I have recreated the same issue with the B310-F Pro motherboard.
And have opened two support tickets.
Meanwhile the B310-F Pro MB is driving an Rx 570 with No New Tasks set till it runs dry.
I guess I will be looking at migrating my Rx 5700's back to the "original" box and maybe even adding two Rx 580's while I work through the Mining MB issues.
====edit=== Maybe I need to move these messages to a new thread? =====
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
Well you didn't even specify what file to edit so don't think when everyone thinks is simple is what you think is simple. Your post is very Linux elitist.
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
Well you didn't even specify what file to edit so don't think when everyone thinks is simple is what you think is simple. Your post is very Linux elitist.
The file is "grub" in /etc/default. Tom is not a Linux newbie.
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
Well you didn't even specify what file to edit so don't think when everyone thinks is simple is what you think is simple. Your post is very Linux elitist.
1. CTRL+ALT+F3 to dump out of the GUI and into command line
2. sudo nano /etc/default/grub
3. make the changes to the file, press CTRL+X to save, then 'Y' to confirm
Well you didn't even specify what file to edit so don't think when everyone thinks is simple is what you think is simple. Your post is very Linux elitist.
The file is "grub" in /etc/default. Tom is not a Linux newbie.
Granted I am not a Linux newbie but there are people here who likely could be.
So it is a good point to not assume everyone has full context.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
You have terrible luck with installs I guess. I have no response other than Ubuntu hates you.
And I have had no luck with using Ubuntu with the Repository Boinc Manager.
I have spent hours/days trying to troubleshoot what I thought was a hardware error.
Then I discovered that Ubuntu/Repository Boinc Manager was essentially running my Rx 5700 at idle on a testbed Intel system I had set up.
So I just installed Windows 10 on another HD and that system came right up and started processing E@H Gamma-Ray GPU tasks on an Rx 5700.
So I dug out the 5,000,000 RAC Moonshot hard disk, planted an Rx 5700 in the #1 spot on the mining rack motherboard (which is now an AMD 3900/MSI X570-Pro). And it just came up and started booging on a single Rx 5700.
Tomorrow I will resume trying to troubleshoot my riser card hardware. Had a very busy day cat-proofing some parts of my Sister's basement. And I am all out of energy.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
And I wonder why you were messing with the repository BOINC when you could have been running the team client. That client gives you so much more with regard to the management of projects compared to any repository stock client, I have no clue as to why anyone with the option would want anything else.
Tom M wrote: Plus the mb
)
I have traced this behavior to specific riser card bases. Apparently the mb was fine but the bases were not. Will resume riser base screening after resting.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Tom M wrote:Tom M
)
After sleeping on the problem it turns out that Rx 5700 cards cause the multiple slots to light up/start but not the Rx 570/580 cards.
I have (finally) located what are possibly the slots I can plug Rx 5700 cards into. And am now testing that.
So AFAIK this is a motherboard hardware issue.
Ubuntu is still letting me logon (cross fingers).
Plan B: I have an untested H310-F Pro (used) that is basically a cut-down version of the B360-F Pro motherboard that I will try if my "workarounds" don't fly.
Plan C: I can most likely revert to the original locations for various GPUs if neither mining MB is going to work. Specifically, take the 5 Rx 5700's back to the AMD 2700x MB and add two Rx 580's to it. And replace the Nvidia cards on the AMD 3950x with 2 Rx 570 cards.
Just started a testing cycle for an Rx 5700 in one of the slots that apparently is not broken. Should have an answer later tonight or in the morning.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Quote:Plan B: I have an
)
I guess it is time for Plan B.
The MB has stopped booting.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Tom M wrote:Quote:Plan B: I
)
So I cleaned off my work bench for the first time in too long.
Dismounted the MSI B360-F Pro and plugged it into my "test rig" stuff.
I refuse to believe that blowing the dust off the MB and moving it to a "new" environment was all the "fix" I needed.
But there it is.
I still need to re-test the failing PCIe slots but it is quietly munching away on GR gpu tasks and U@H cpu tasks on my work bench.
===edit====
PCIe slots still showing multiple lighting up when plugged into certain single slots.
Its dead :(
====edit====again=======
It's Alive. No it's disabled...
Anyway I have recreated the same issue with the B310-F Pro motherboard.
And have opened two support tickets.
Meanwhile the B310-F Pro MB is driving an Rx 570 with No New Tasks set till it runs dry.
I guess I will be looking at migrating my Rx 5700's back to the "original" box and maybe even adding two Rx 580's while I work through the Mining MB issues.
====edit=== Maybe I need to move these messages to a new thread? =====
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Keith Myers wrote: OK, one
)
Well you didn't even specify what file to edit so don't think when everyone thinks is simple is what you think is simple. Your post is very Linux elitist.
mmonnin wrote: Keith Myers
)
The file is "grub" in /etc/default. Tom is not a Linux newbie.
mmonnin wrote: Keith Myers
)
1. CTRL+ALT+F3 to dump out of the GUI and into command line
2. sudo nano /etc/default/grub
3. make the changes to the file, press CTRL+X to save, then 'Y' to confirm
4. sudo update-grub
5. reboot
_________________________________________________________________________
Keith Myers wrote: mmonnin
)
Granted I am not a Linux newbie but there are people here who likely could be.
So it is a good point to not assume everyone has full context.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Keith Myers wrote: You have
)
And I have had no luck with using Ubuntu with the Repository Boinc Manager.
I have spent hours/days trying to troubleshoot what I thought was a hardware error.
Then I discovered that Ubuntu/Repository Boinc Manager was essentially running my Rx 5700 at idle on a testbed Intel system I had set up.
So I just installed Windows 10 on another HD and that system came right up and started processing E@H Gamma-Ray GPU tasks on an Rx 5700.
So I dug out the 5,000,000 RAC Moonshot hard disk, planted an Rx 5700 in the #1 spot on the mining rack motherboard (which is now an AMD 3900/MSI X570-Pro). And it just came up and started booging on a single Rx 5700.
Tomorrow I will resume trying to troubleshoot my riser card hardware. Had a very busy day cat-proofing some parts of my Sister's basement. And I am all out of energy.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
And I wonder why you were
)
And I wonder why you were messing with the repository BOINC when you could have been running the team client. That client gives you so much more with regard to the management of projects compared to any repository stock client, I have no clue as to why anyone with the option would want anything else.