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:
xauth merge /home/user/.Xauthority
Thanks for this! Definitely handy to know the command now, I'll save it in my notes! It does just give me the same error again, but at least I can call the error now.
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.
Here is what happens at boot..
1 - normal linux stuff
2 - x windows config blown away
3 - ati device detection -> generate new x win config
4a - x starts in one thread
4b - mine_start starts in another thread, sleeps for start_delay
5 - X finally gets going
6 - default user logs in automatically to x session
7 - mine_start script runs xauth + to make the X server allow connections
now, in root's .bashrc there is a command: xauth merge /home/user/.Xauthority
this runs when you log in as root. it gives root the ability to talk to the X server.
however, if you log in via ssh before step 6 completes, the .Xauthority file isn't there yet and you get no joy.
or if step 7 happens before step 5, you'll get no joy.
some USB keys are much, much slower than others. same with cpu, etc. having more GPUs means step 3 can take much longer. some GPUs seem to make step 4a/5 take a really long time if no monitor is attached. there are many variables here. since the process splits in step 4, there isn't a strong tie between them and things can get out of order, or you can just be in a rush and logging in via ssh too soon.
the default timing works in most situations, but if it doesnt your best bet is to connect a monitor and change the root password using the console, after you can see that everything is started up. open a root terminal and do passwd. once you've done that, it will probably work fine. if not, you may need to increase the startup delay, its the setting "start_mining_init_delay:" in the main section, see
http://bamter.org/redmine/projects/bamt/wiki/ExamplesYeah I put the start_mining_init_delay on all the boxes, it just seems like a good idea to put that there.
Interestingly, I can't connect a monitor to change the root password using the console. When I have 5 cards on there, I can, but if I put the 6th on, there is absolutely *no* video, not even a post... But the LED blinks, and the system boots, and I can log in via SSH but it can't merge the Xauthority. Clearly if the thing can't light the screen up at all, that tells us something is wrong, and I'm positive it's hardware... We're asking too much of these GD70's. Having two identical boards, identical BIOS's, and identical settings and one will run 6 cards and the other will not? Last night I came up with a theory: the box that can run 6 cards is running 6x 6870s, where 6x 5830s or 5850s is a no go, but 5 is. Now that this has been brought to my brain's attention, they are not as identical as I was thinking. Now I want to experiment with other BIOS versions, I figured if v1.6 can run 6 cards, it is the one to go with, but maybe another version can run 6x 5830s? To be continued!
Thanks for your troubleshooting!
Show Posts
