search

jmeier64 / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

ATI's Dual Cores labeling issue #180

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Videocards like ATI's HD x4870 X2 has two GPUs on a single card.  Which results 
in having same hardware name. Won't able to get input from its second GPU, only 
from the first one on the OMH's list.

Original issue reported on code.google.com by nana...@gmail.com on 4 Mar 2011 at 12:54

Attachments:

GoogleCodeExporter commented 9 years ago 
What do you mean by "Won't able to get input"? Does it not display any sensor 
information for the second card in the Open Hardware Monitor? Or do you have a 
problem reading the information from other applications.

Original comment by moel.mich on 4 Mar 2011 at 7:53

GoogleCodeExporter commented 9 years ago 
To get an input value of both videocard's cores, it only return the first core 
because they both have the same name.  No way of getting the second core.

(Mind you, they are treated like having two videocards instead of one card with 
two cores.)

Original comment by nana...@gmail.com on 4 Mar 2011 at 4:37

GoogleCodeExporter commented 9 years ago 
The name is not a problem, that is just for the user interface. The cards are 
not identified by name. In general there is not much I can do to improve the 
reading for HD 4870 X2 cards, because the current data is what the graphics 
card driver provides. For example when idling on the desktop, usually the 
second core of the X2 gets powered down and no information is exposed by the 
driver. 

Stressing both cores and then starting the Open Hardware Monitor should get you 
readings from both cores.

Can you attach two reports created with the Open Hardware Monitor (File -> Save 
Report...), one after starting OHM with an idle GPU, and one after starting OHM 
with a complete busy GPU (use some stress test for this).

Original comment by moel.mich on 4 Mar 2011 at 5:43

GoogleCodeExporter commented 9 years ago 
Well that's not the case. The problem is the first core is the idle one while 
second is the main GPU for my use. It's reporting back the first one.  So, it 
does report back normally.  Just can't get report result from the second 
because it's kept reading the first one when both have same name.

Original comment by nana...@gmail.com on 4 Mar 2011 at 7:39

Attachments:

GoogleCodeExporter commented 9 years ago 
From your reports I do not see any problem with the Open Hardware Monitor. Are 
you trying to use values from the Open Hardware Monitor in another software 
like Rainmeter?

Original comment by moel.mich on 4 Mar 2011 at 8:13

GoogleCodeExporter commented 9 years ago 
Yes?   (Was assumming that's what OMH was built for.)

Original comment by nana...@gmail.com on 4 Mar 2011 at 8:27

GoogleCodeExporter commented 9 years ago 
The Open Hardware Monitor is built and developed as a standalone application. 
Exporting the values into Rainmeter is just one possible usage scenario of the 
software. 

Now I understand where you get a problem. The hardware names displayed in the 
Open Hardware Monitor user interface are not for identification of the 
hardware. The problem should be fixed in the Rainmeter plugin by using the 
identifiers provided by the Open Hardware Monitor on each hardware instead of 
the names. 

With the fix of Issue 164 all the identifiers should now be visible in the 
report. 

Discussion continues in the corresponding Rainmeter plugin thread: 
http://rainmeter.net/forum/viewtopic.php?f=18&t=6874&start=30

Original comment by moel.mich on 4 Mar 2011 at 8:48