 Show Posts
|
|
Pages: [1]
|
I've never seen that behaviour before. atitweak is just printing information returned by the driver dso. Is it possible that your xorg.conf is incomplete? Mine looks like this: Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
<snip>
There should be one ServerLayout section and one Device/Screen/Monitor sections for each card. You can get the PCI addresses with lspci. I just wanted to say thanks for posting your config. I have two 5850's and it was only seeing one. A simple X configuration problem, nothing to do with atitweak (damn awesome by the way), but having your config to model it on was most helpful in getting a system which sees both cards. Regards... Todd |
|
|
|
it seems i get more and more of these Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python miner while already using latest m0mchil's python miner. I see that you are sending more stale shares than expected (but less than 1%, anyway). Trying to find the cause of this. I've got two machines mining, both at fairly low bitrates, 6M and 73M. Both of them are running the latest poclbm. My status page (for accounts tlyons@ive.*) show my two accounts at 1.91% and 1.49% stale, respectively. Is that statistic over the life of the account? Because I just started using the new poclbm about 24 hours ago, but was using it for a couple weeks before that. In addition, I see log entries such as this occasionally (times are UTC -0700) : 15/03/2011 06:40:30, 5ab08224, accepted
15/03/2011 06:41:38, long poll: Deepbit is temporarily unavailable
15/03/2011 06:42:13, ea0227f4, accepted
15/03/2011 06:42:57, d260477e, accepted
15/03/2011 06:43:45, long poll: new block I suspect the last line is long polling working as suspected, where the server pushes out an update request to me when it receives a new block. I also suspect the second line is just you doing work on the system and restarting things, but that's a guess. I also see this occasionally: 15/03/2011 08:41:16, long poll: backend error Is there anything I might want to tweak on this? Regards... Todd |
|
|
|
Yep, OSX is known broken at this time. Waiting for someone to fix it, in a way that doesn't break everyone else's build...
There was a guy on IRC last week building your miner who made a quick change per some post he found via google that got byteswap to work. I'll dig and see if I can find it. Regards... Todd Some asshat came into the channel and trolled the entire freakin channel on Thu and wiped out all my scrollback (gotta remember to increase that on Monday). But was able to find the post he was talking about. From http://www.mail-archive.com/barry-devel@lists.sourceforge.net/msg00113.html , there is a link to this commit that defines it inline if OSX is detected: http://lists.freedesktop.org/archives/xorg-commit/2007-January/010041.htmlRegards... Todd |
|
|
|
Yep, OSX is known broken at this time. Waiting for someone to fix it, in a way that doesn't break everyone else's build...
There was a guy on IRC last week building your miner who made a quick change per some post he found via google that got byteswap to work. I'll dig and see if I can find it. Regards... Todd |
|
|
|
|
Web interface feature request:
Purely for aesthetics, on the statistics page would it possible to identify which blocks were submitted by your pool? An asterisk would be sufficient IMHO, but you could just as easily add a "Pool Hit" column with a checkmark if your pool submitted that block. If the "claiming" of that block goes against the Anonymous nature of the currency, I understand a "no I won't do that" answer.
|
|
|
|
Maintaining the faucet isn't a big drain on my time-- most days I don't think about it.
Given the number of newbies who wander into #bitcoin-dev and mention they got 0.05 BTC from the faucet, I think it is still valuable as a nice introduction to using bitcoin.
And Jim: thanks! Without donations the Faucet would have run out of coins long ago...
Gavin, you should make it much more obvious about how to give back to the Faucet. In the end I had to click to (try to) get another .05 BTC, at which point it said I had already gotten some, but if I wanted to I could give back to a specific address, which I assume is the Faucet. Is it ok to post it here for confirmation? |
|
|
|
71mhash with downclocked memory and stream SDK 2.2.
72 Mhash/sec, linux, poclbm.py, SDK 2.1, no OC'ing. |
|
|
|
I suggest to change it so that when you're logged in (and it shows it on the top right side), don't display the user/pass login boxes. Thanks for your suggestion, i'll fix it. Holy crap that was fast. Awesome, thanks! |
|
|
|
|
Hi Tycho, your site is nice, and seems to be reliable. Great job! I have a small website change suggestion: The user/pass login always shows in a box on top of the left pane, even when you're logged in. I suggest to change it so that when you're logged in (and it shows it on the top right side), don't display the user/pass login boxes. Instead, display "Welcome $USER" and/or a Logout link, or just nothing at all. It _works_ properly, I'm not complaining about how well it works in the least :-) Just that it from a UI perspective, it shouldn't continue to prompt you for login credentials if you've already logged in.
Great product! Thanks!
|
|
|
|
- Add support for JSON-format configuration file. See example
file example-cfg.json. Any long argument on the command line
may be stored in the config file. Curious, how come a json format was chosen over something like yaml? JSON is extremely unforgiving when it comes to syntax, compared to yaml which is much more forgiving. Personally I also find YAML to be more readable, but that's just a personal preference not based on capabilities nor function. Are there plans to centralize configs or something (since json is so web friendly)? Or was it just a convenient way to save/retrieve configuration? Regards... Todd |
|
|
|
|
