12.1 and sdk 2.5 is the least worst -recent- driver sdk combo. 11.6/2.5 is good but wont install on new linux versions.
Alright, I'll have to look into it. I dunno why it would start messing up after a random system update though. Seems weird to me. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 609. (Read 5806103 times)
March 28, 2012, 03:10:28 PM
March 28, 2012, 03:05:28 PM
AMD fail. Dodgy driver/SDK combo for your hardware. Downgrade your driver to a less bad one.
I would, but I haven't found a decent guide anywhere to downgrade properly. What was the optimal driver/SDK combo for 6000 series cards again anyway? March 28, 2012, 02:52:10 PM
AMD fail. Dodgy driver/SDK combo for your hardware. Downgrade your driver to a less bad one.
I would, but I haven't found a decent guide anywhere to downgrade properly. What was the optimal driver/SDK combo for 6000 series cards again anyway? March 28, 2012, 02:47:52 PM
Just started getting this today after an update told me to restart.
Using cgminer 2.3.1-2 on Ubuntu 11.10.
AMD fail. Dodgy driver/SDK combo for your hardware. Downgrade your driver to a less bad one. Code:
[2012-03-28 12:40:03] Started cgminer 2.3.1X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 136 ()
Minor opcode of failed request: 19
Serial number of failed request: 8
Current serial number in output stream: 8
Using cgminer 2.3.1-2 on Ubuntu 11.10.
March 28, 2012, 11:47:21 AM
Just started getting this today after an update told me to restart.
Using cgminer 2.3.1-2 on Ubuntu 11.10.
Code:
[2012-03-28 12:40:03] Started cgminer 2.3.1X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 136 ()
Minor opcode of failed request: 19
Serial number of failed request: 8
Current serial number in output stream: 8
Using cgminer 2.3.1-2 on Ubuntu 11.10.
March 28, 2012, 04:40:44 AM
Try again please with the updated git now. (only diablo kernel has been changed this time).
no problem:between 188 and 190 MH/s
Thanks! it works!
But in average it seems to be 2 MH/s lower...
March 28, 2012, 04:35:55 AM
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!
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.
Jump to: