Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 23. (Read 324176 times)
August 14, 2012, 04:27:56 PM
No, I do not have "new" ... using old hard disk again.
August 14, 2012, 04:25:32 PM
So problems continues after new unexpected power down : xauth: error in locking authority file /root/.Xauthority
message : read-only file system
Starting mining processes...: minestart_mining: starting mining processes
..muninrm: cannot remove `/etc/munin/plugins/gpuhash_all': Read-only file system
rm: cannot remove `/etc/munin/plugins/gputemp_all': Read-only file system
rm: cannot remove `/var/lib/munin/plugin-state': Read-only file system
ln: creating symbolic link `/var/lib/munin/plugin-state/run': File exists
..GPU 0..fan 0..OC 0..GPU 1..fan 1..OC 1..GPU 2..fan 2..OC 2.
I cant reboot machine, or start mining
message : read-only file system
Starting mining processes...: minestart_mining: starting mining processes
..muninrm: cannot remove `/etc/munin/plugins/gpuhash_all': Read-only file system
rm: cannot remove `/etc/munin/plugins/gputemp_all': Read-only file system
rm: cannot remove `/var/lib/munin/plugin-state': Read-only file system
ln: creating symbolic link `/var/lib/munin/plugin-state/run': File exists
..GPU 0..fan 0..OC 0..GPU 1..fan 1..OC 1..GPU 2..fan 2..OC 2.
I cant reboot machine, or start mining
usb key has died. might work if you reflash, might not, or might work for a day or two and die again.
http://anonymouse.org/cgi-bin/anon-www.cgi/http://img600.imageshack.us/img600/4928/adata.jpg
Have you tried a "new" USB flash drive?
August 14, 2012, 02:36:52 PM
So problems continues after new unexpected power down : xauth: error in locking authority file /root/.Xauthority
message : read-only file system
Starting mining processes...: minestart_mining: starting mining processes
..muninrm: cannot remove `/etc/munin/plugins/gpuhash_all': Read-only file system
rm: cannot remove `/etc/munin/plugins/gputemp_all': Read-only file system
rm: cannot remove `/var/lib/munin/plugin-state': Read-only file system
ln: creating symbolic link `/var/lib/munin/plugin-state/run': File exists
..GPU 0..fan 0..OC 0..GPU 1..fan 1..OC 1..GPU 2..fan 2..OC 2.
I cant reboot machine, or start mining
message : read-only file system
Starting mining processes...: minestart_mining: starting mining processes
..muninrm: cannot remove `/etc/munin/plugins/gpuhash_all': Read-only file system
rm: cannot remove `/etc/munin/plugins/gputemp_all': Read-only file system
rm: cannot remove `/var/lib/munin/plugin-state': Read-only file system
ln: creating symbolic link `/var/lib/munin/plugin-state/run': File exists
..GPU 0..fan 0..OC 0..GPU 1..fan 1..OC 1..GPU 2..fan 2..OC 2.
I cant reboot machine, or start mining
usb key has died. might work if you reflash, might not, or might work for a day or two and die again.
http://img600.imageshack.us/img600/4928/adata.jpg
August 13, 2012, 07:39:53 PM
Code:
root@bamt-miner:~# rm /home/user/.Xauthority
rm: cannot remove `/home/user/.Xauthority': No such file or directory
doesn't seem to be there.. but if we can figure out how to reset Xauthority manually like this, I'll be psyched!
As root:
Code:
xauth merge /home/user/.Xauthority
August 13, 2012, 05:53:02 PM
Code:
root@bamt-miner:~# rm /home/user/.Xauthority
rm: cannot remove `/home/user/.Xauthority': No such file or directory
doesn't seem to be there.. but if we can figure out how to reset Xauthority manually like this, I'll be psyched!
August 13, 2012, 05:49:34 PM
Try then to delete the /home/user/.Xauthority file and let it be recreated.
Code:
rm /home/user/.Xauthority
August 13, 2012, 05:41:03 PM
What if you exit SSH and SSH again directly as root?
That's a damn good suggestion. Tried it on both, one worked the other didn't. But we need more than 4 cards on these boards, so i'll try 5 on the one that succeeded SSH as root.edit: same thing..
August 13, 2012, 05:38:47 PM
Two identical boxes, both MSI 890FXA-GD70 motherboards, both 4x 5850s, I cannot set the password without it spitting the Xauthority error.
We need 6 cards running on each box. It's like effin' impossible to do but there is a 6-card 890FXA-GD70 with 6x 6870s on it running no problem.
These two, again identical, all same bios (1.6) and it errors on 4 cards. WTF.
We need 6 cards running on each box. It's like effin' impossible to do but there is a 6-card 890FXA-GD70 with 6x 6870s on it running no problem.
These two, again identical, all same bios (1.6) and it errors on 4 cards. WTF.
August 13, 2012, 05:36:37 PM
What if you exit SSH and SSH again directly as root?
August 13, 2012, 05:33:47 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Found this:
https://bitcointalksearch.org/topic/m.885677
Exactly. Reduce overclocking. But the system hasn't been configured yet, all that has been done is the password is set. It's not doing ANYTHING yet.
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Have you applied all the updates? IIRC there was a fix that addressed this, I may be wrong through, it's been a while.
Fresh image to USB flash drive.
Booted with a monitor attached.
Logged in as root via the gui.
Minimal mods to the bamt.conf to get the cards enabled and on a pool. (tweak/oc/tune later)
Ran cgminer via the gui, hit F for fixer, applied all.
As root via the gui, changed PW.
Then SSH'd to it from PuTTY.
I just remember getting an error like that before, and I think logging in on the rig first before hitting it via SSH made that go away. Or I'm way off base, and I'm thinking of something completely different. Either way, hope it helps.
I don't know if that's the case.. It would be annoying to have to configure each box this way... I'll try it though.
August 13, 2012, 05:17:24 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Have you applied all the updates? IIRC there was a fix that addressed this, I may be wrong through, it's been a while.
Fresh image to USB flash drive.
Booted with a monitor attached.
Logged in as root via the gui.
Minimal mods to the bamt.conf to get the cards enabled and on a pool. (tweak/oc/tune later)
Ran cgminer via the gui, hit F for fixer, applied all.
As root via the gui, changed PW.
Then SSH'd to it from PuTTY.
I just remember getting an error like that before, and I think logging in on the rig first before hitting it via SSH made that go away. Or I'm way off base, and I'm thinking of something completely different. Either way, hope it helps.
August 13, 2012, 04:57:39 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Found this:
https://bitcointalksearch.org/topic/m.885677
August 13, 2012, 04:57:31 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Have you applied all the updates? IIRC there was a fix that addressed this, I may be wrong through, it's been a while.
August 13, 2012, 04:38:16 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
Have you applied all the updates? IIRC there was a fix that addressed this, I may be wrong through, it's been a while.
August 13, 2012, 04:15:42 PM
This error is currently the bane of my existence.
Why does this happen, on a fresh BAMT, immediately after setting the root password? Once that error happens, if you reboot, there's a chance it might work on next boot, but sometimes reformatting the USB helps.
I've had to format BAMT so many times now that the USB sticks are dying, and it's mostly because of this stupid Xauthority error.
Any tips? I've asked in the past but no real solutions to this.
August 13, 2012, 01:48:15 PM
A bit later, gigavps found that 2.3f would sometimes just exit with no clear indication of why. He was desperate for a fix, and I believe contacted you guys, posted on the cgminer forum, etc. When no solution was forthcoming, he asked me if I could hack mother to detect that it had exited and start it back up. So I did.
Anyway I instrumented the newer cgminer restart problem in bamt and it is indeed in the /opt/bamt/mother monitoring file. The perl parsing of ps axu output fails to detect cgminer is there and it then calls /etc/init.d/mine restart . So it is in fact bamt that is restarting cgminer, and if I edit the mother script to parse the output of ps axu differently, it does NOT continually restart cgminer. Alas I don't really know perl, but it does seem to need fixing.
If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash):
http://ck.kolivas.org/apps/cgminer/temp/mother
If you copy this file on top of mother in /opt/bamt it shouldn't restart on you (note this is not the correct fix and will probably not restart cgminer should it actually really crash):
http://ck.kolivas.org/apps/cgminer/temp/mother
So what would be best thing to do then, use ckolivas's fix OR don't apply BAMT fix 20 in the first place?
August 13, 2012, 11:12:42 AM
I am seeding it right now. Try to add those trackers I mentioned above to your torrent client.
Oh there we go, I had to read between the lines. I mean put an empty line between trackers. W00t! August 13, 2012, 11:11:38 AM
I am seeding it right now. Try to add those trackers I mentioned above to your torrent client.
August 13, 2012, 11:03:22 AM
I see people keep asking for a BAMT able to run with 7970 cards so I am thinking to share mine.
It may work for you or it may not...give it a try. It worked for me two months already so is not gonna blow your PC.
It is a BAMT updated to SDK 2.6 and 8.921 AMD driver using cgminer 2.5.0.
SDK 2.6 was recommended by ckolivas for 7970 and the 8.921 driver was (I tried all recent drivers) the only one that did not gave me hardware errors with cgminer.
Other (more recent) SDK/driver combinations could work also but this one worked perfectly for me.
All you need to do is edit bamt.conf at the cgminer_opts line and enable cgminer in each GPU section for how many cards you have.
If you want to use a separate cgminer config be my guest, I personally enter all the options I need in that cgminer_opts line.
I give no guarantees that it will work for you, it does for me with three 7970 cards.
root password = root
user password = live
Download:
https://ca.isohunt.com/torrent_details/402809617/BAMT+for+7970?tab=summary
Hope this damn torrent will work, eventually add these trackers to your bit-torrent client:
http://announce.opensharing.org:2710/announce
http://exodus.desync.com:6969/announce
Sweet! But I'm getting no seeds. Can someone seed this please? It may work for you or it may not...give it a try. It worked for me two months already so is not gonna blow your PC.
It is a BAMT updated to SDK 2.6 and 8.921 AMD driver using cgminer 2.5.0.
SDK 2.6 was recommended by ckolivas for 7970 and the 8.921 driver was (I tried all recent drivers) the only one that did not gave me hardware errors with cgminer.
Other (more recent) SDK/driver combinations could work also but this one worked perfectly for me.
All you need to do is edit bamt.conf at the cgminer_opts line and enable cgminer in each GPU section for how many cards you have.
If you want to use a separate cgminer config be my guest, I personally enter all the options I need in that cgminer_opts line.
I give no guarantees that it will work for you, it does for me with three 7970 cards.
root password = root
user password = live
Download:
https://ca.isohunt.com/torrent_details/402809617/BAMT+for+7970?tab=summary
Hope this damn torrent will work, eventually add these trackers to your bit-torrent client:
http://announce.opensharing.org:2710/announce
http://exodus.desync.com:6969/announce
August 13, 2012, 10:17:11 AM
I see people keep asking for a BAMT able to run with 7970 cards so I am thinking to share mine.
It may work for you or it may not...give it a try. It worked for me two months already so is not gonna blow your PC.
It is a BAMT updated to SDK 2.6 and 8.921 AMD driver using cgminer 2.5.0.
...
...
It may work for you or it may not...give it a try. It worked for me two months already so is not gonna blow your PC.
It is a BAMT updated to SDK 2.6 and 8.921 AMD driver using cgminer 2.5.0.
...
...
It work for my, Thanks a lot
Ah, many thanks for the feedback, so far at least 6 persons downloaded the image (from me) but no one said at least fuck you, it doesn't work...
I am glad to know that it is working for you
Jump to: