Try again please with the updated git now. (only diablo kernel has been changed this time).
Correction: it is on average 190 MH/s.Therefore: Thanks! It works!
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 611. (Read 5805746 times)
March 28, 2012, 04:35:55 AM
Therefore: Thanks! It works!
March 28, 2012, 04:19:17 AM
yes... know, but I prefer the default kernel (is it diabolo?) since I tested all of them a while ago and diabolo was the fastest. Therefore I prefer to work with the older git version... but why did the hashrate drop?
The kernels have radically changed and I need to choose the right ones. I'm asking you because I need your feedback, i'm not telling you a workaround. You are running very experimental code by trying the git tree.Current Git:
diablo: 175 MH/s
poclbm: 157 MH/s
phatk: 168 MH/s
poclbm: 160 MH/s
Git from 3/3/2012:
default/diablo: 190 MH/s
Everything on Ubuntu 11.10 64bit, with HD5770 , Intensity 9, no overclocking/underclocking ,
ADL SDK 3.0
APP SDK 2.6 RC3
Cataclyst 12.2
Should I test all the kernels with the older git, too?
March 28, 2012, 04:03:57 AM
Con,
Restarting cgminer always fixes it, no need to restart the whole box.
Is this still something you consider adding to cgminer?
Yes. ckvolias:using latest cgminer 2.3.1-2 win7 64x
after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Windows driver ATI Display Library fsckage. I can't do anything about it. Does restarting cgminer fix it or rebooting the machine fix it? I could probably try working around the former by detecting "losing adl support" and re-initialising it.after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Is this still something you consider adding to cgminer?
March 28, 2012, 03:30:44 AM
Con,
Restarting cgminer always fixes it, no need to restart the whole box.
Is this still something you consider adding to cgminer?
ckvolias:using latest cgminer 2.3.1-2 win7 64x
after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Windows driver ATI Display Library fsckage. I can't do anything about it. Does restarting cgminer fix it or rebooting the machine fix it? I could probably try working around the former by detecting "losing adl support" and re-initialising it.after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Is this still something you consider adding to cgminer?
March 28, 2012, 03:30:23 AM
yes... know, but I prefer the default kernel (is it diabolo?) since I tested all of them a while ago and diabolo was the fastest. Therefore I prefer to work with the older git version... but why did the hashrate drop?
The kernels have radically changed and I need to choose the right ones. I'm asking you because I need your feedback, i'm not telling you a workaround. You are running very experimental code by trying the git tree.Current Git:
diablo: 175 MH/s
poclbm: 157 MH/s
phatk: 168 MH/s
poclbm: 160 MH/s
Git from 3/3/2012:
default/diablo: 190 MH/s
Everything on Ubuntu 11.10 64bit, with HD5770 , Intensity 9, no overclocking/underclocking ,
ADL SDK 3.0
APP SDK 2.6 RC3
Cataclyst 12.2
Should I test all the kernels with the older git, too?
March 28, 2012, 02:43:07 AM
yes... know, but I prefer the default kernel (is it diabolo?) since I tested all of them a while ago and diabolo was the fastest. Therefore I prefer to work with the older git version... but why did the hashrate drop?
The kernels have radically changed and I need to choose the right ones. I'm asking you because I need your feedback, i'm not telling you a workaround. You are running very experimental code by trying the git tree.Current Git:
diablo: 175 MH/s
poclbm: 157 MH/s
phatk: 168 MH/s
poclbm: 160 MH/s
Git from 3/3/2012:
default/diablo: 190 MH/s
Everything on Ubuntu 11.10 64bit, with HD5770 , Intensity 9, no overclocking/underclocking ,
ADL SDK 3.0
APP SDK 2.6 RC3
Cataclyst 12.2
Should I test all the kernels with the older git, too?
March 28, 2012, 02:25:27 AM
yes... know, but I prefer the default kernel (is it diabolo?) since I tested all of them a while ago and diabolo was the fastest. Therefore I prefer to work with the older git version... but why did the hashrate drop?
The kernels have radically changed and I need to choose the right ones. I'm asking you because I need your feedback, i'm not telling you a workaround. You are running very experimental code by trying the git tree. March 28, 2012, 02:23:21 AM
yes... know, but I prefer the default kernel (is it diabolo?) since I tested all of them a while ago and diabolo was the fastest. Therefore I prefer to work with the older git version... but why did the hashrate drop?
March 28, 2012, 02:16:02 AM
Hi, I just wanted to report that with the latest git My Hashrate drops from 190 MH/s to 170 MH/s. When I check the git repository out from the date 3/3/2012 then I get again 190MH/s.
I use the default kernel and I use ubuntu 11.10 with a HD5770. What changes made the hashrate drop so drastically?
I'm experimenting. It looks like you are on SDK 2.6. Try -k diablo and see what that does to your hashrate.I use the default kernel and I use ubuntu 11.10 with a HD5770. What changes made the hashrate drop so drastically?
March 28, 2012, 01:19:42 AM
Hi, I just wanted to report that with the latest git My Hashrate drops from 190 MH/s to 170 MH/s. When I check the git repository out from the date 3/3/2012 then I get again 190MH/s.
I use the default kernel and I use ubuntu 11.10 with a HD5770. What changes made the hashrate drop so drastically?
I use the default kernel and I use ubuntu 11.10 with a HD5770. What changes made the hashrate drop so drastically?
March 27, 2012, 02:53:03 PM
On Windows, can I use a driver version which does NOT officialy support the 7970 as long as the newest SDK is installed?
no 
March 27, 2012, 09:15:00 AM
On Windows, can I use a driver version which does NOT officialy support the 7970 as long as the newest SDK is installed?
March 27, 2012, 06:43:15 AM
I'm back online. So time to start rounding up a few pending patches and bring out a new version in the next few days.
Interestingly, I finally got to try the official 12.2 driver for linux with my 7970 and it actually makes my GPU go sick and then dead at clocks that were fine with that early GCN only driver release amd-driver-installer-8.921-x86.x86_64.run . Downgrading to that fixed the problem. Worth considering a different driver version if you're having apparent hardware instability it seems.
Interestingly, I finally got to try the official 12.2 driver for linux with my 7970 and it actually makes my GPU go sick and then dead at clocks that were fine with that early GCN only driver release amd-driver-installer-8.921-x86.x86_64.run . Downgrading to that fixed the problem. Worth considering a different driver version if you're having apparent hardware instability it seems.
March 26, 2012, 03:19:27 PM
It's more of a miner hardware status and 'debug' style info - so better to show it all on some extended status or 'debug' style page.
Basically, you already have Alive, Sick, Dead, NoStart, Disabled.
When things are Sick or Dead, then on that rare occasion someone may want to see some info about what's going on.
If it's one device, that's fine, but if it's more than one ... having to go to N different device pages would be a PITA in my opinion - but that's just my opinion
I'm thinking more along the lines of: there is something wrong and this overview of where things are going wrong is the best use of it
i.e. "I see a problem", is it only one card, or multiple cards or even 2 GPU's on the same card or 2 GPU's on different cards - so an across the board rundown of the status of everything is way more useful as that is the point of what boozer was looking at and since he gave me some BTC for helping I thought best to also write the code to help some more - i.e. an overview of what's going wrong: where it's happening and why
Basically, you already have Alive, Sick, Dead, NoStart, Disabled.
When things are Sick or Dead, then on that rare occasion someone may want to see some info about what's going on.
If it's one device, that's fine, but if it's more than one ... having to go to N different device pages would be a PITA in my opinion - but that's just my opinion
I'm thinking more along the lines of: there is something wrong and this overview of where things are going wrong is the best use of it
i.e. "I see a problem", is it only one card, or multiple cards or even 2 GPU's on the same card or 2 GPU's on different cards - so an across the board rundown of the status of everything is way more useful as that is the point of what boozer was looking at and since he gave me some BTC for helping I thought best to also write the code to help some more - i.e. an overview of what's going wrong: where it's happening and why
OK, that makes sense. My other thought was to add a new page to display this.
March 26, 2012, 05:52:35 AM
I was asked to set it to 10 seconds (because of a high stale rate).
If you mean P2Pool, then that's not the getwork delay.I they did mean P2Pool then that would probably be some noob who didn't read the README that tells you what to do on P2Pool.
Of course, yes read the README if you are referring to P2Pool
README:
Q: How do I tune for p2pool?
A: p2pool has very rapid expiration of work and new blocks, it is suggested you decrease intensity by 1 from your optimal value, and decrease GPU threads to 1 with -g 1.
If on the other hand it has nothing to do with P2Pool, then ask whoever told you what on earth they mean
March 26, 2012, 05:37:33 AM
I was asked to set it to 10 seconds (because of a high stale rate).
March 26, 2012, 05:13:24 AM
How can I set the getwork delay (if such a setting exists)?
You can't - you can set the Queue size with -Q though ...The code decides what its best
(which of course makes perfect since)
If you are talking Icarus - then set it to at least 4
Otherwise ... what for?
March 26, 2012, 04:07:41 AM
How can I set the getwork delay (if such a setting exists)?
March 25, 2012, 06:59:40 PM
I've put a few commits in my git:
https://github.com/kanoi/cgminer/
that add a simple device history that is accessible via the new API command 'notify'
Compiling my git reports itself as 2.3.1k
You can see it with
Code:
echo -n notify | nc 127.0.0.1 4028 ; echo
The base code change adds a few extra fields and counters to the device structure (that are all reported by the API)
Including: per device: last well time, last not well time, last not well reason, and counters for each of the reasons meaning how many times they have happened (e.g. Device Over Heat count, Device Thermal Cutoff count among others)
Wondering if you can make it retrievable per device?
I don't think this is info that needs to go on anubis' host page (where the devices are listed). Seems to be more detailed then necessary for that page, so I would put it on the individual device page, but then I'd have to get the whole list and find the relevant entry.
Thoughts?
Basically, you already have Alive, Sick, Dead, NoStart, Disabled.
When things are Sick or Dead, then on that rare occasion someone may want to see some info about what's going on.
If it's one device, that's fine, but if it's more than one ... having to go to N different device pages would be a PITA in my opinion - but that's just my opinion
I'm thinking more along the lines of: there is something wrong and this overview of where things are going wrong is the best use of it
i.e. "I see a problem", is it only one card, or multiple cards or even 2 GPU's on the same card or 2 GPU's on different cards - so an across the board rundown of the status of everything is way more useful as that is the point of what boozer was looking at and since he gave me some BTC for helping I thought best to also write the code to help some more - i.e. an overview of what's going wrong: where it's happening and why
March 25, 2012, 12:38:52 PM
I had the problem witch boozer has.
GPU0 crasches and i get 50/50% of usage by Xorg/cgminer or any other combination with xorg.
only reboot helps.
configuration: 5870 VaporX+2x5970 with acceleroX, Xubuntu 11.04, CAT 12.2(SDK 2.6), cgminer 2.3.1, kernel diablonow i`m testing phatk).
For last lew days, i was using 2.0.6 with cheat(few pages ago), but my hdd was dying, it was matter of time....
All new install. 2.0.6 wont work
2.3.1 crasches my GPO0 :/
EDIT:
phatk and diablo do this same...after prox 20 minutes, crash of xorg.
now i`m trying: -g 1
5870 works on 940/150, where i know i can pull 970 .... max temp 62 *C
system was totally 13minutes uptime, and xorg failed :/
Edit#2
Now i think it`s just broken xorg. I was ipgrading al, and xorg dieded. I`ll end it tomorow - i hope.
Edit#3
rule No.69 - always tourn off your screen sever.
GPU0 crasches and i get 50/50% of usage by Xorg/cgminer or any other combination with xorg.
only reboot helps.
configuration: 5870 VaporX+2x5970 with acceleroX, Xubuntu 11.04, CAT 12.2(SDK 2.6), cgminer 2.3.1, kernel diablonow i`m testing phatk).
For last lew days, i was using 2.0.6 with cheat(few pages ago), but my hdd was dying, it was matter of time....
All new install. 2.0.6 wont work
2.3.1 crasches my GPO0 :/
EDIT:
phatk and diablo do this same...after prox 20 minutes, crash of xorg.
now i`m trying: -g 1
5870 works on 940/150, where i know i can pull 970 .... max temp 62 *C
system was totally 13minutes uptime, and xorg failed :/
Edit#2
Now i think it`s just broken xorg. I was ipgrading al, and xorg dieded. I`ll end it tomorow - i hope.
Edit#3
rule No.69 - always tourn off your screen sever.
Jump to: