Went to get torsmo and noticed it has been removed, so I thought I'd try conky. As far as I can tell conky 1.3.5 seems to work great on my alpha (ev56). All I did was edit the keywords on the ebuild, it compiled, installed and works perfectly, didn't even have to do any work. I would love it if someone could just add the ~alpha keyword to the ebuild so it won't get clobbered on my end every time I run a sync.
This is supported by me and Brenden (upstream maintainer).
I've confirmed that app-admin/conky-1.4.0 works as well, however the Frequency in MHz and Frequency in GHz both display as 0.
Created attachment 81467 [details, diff] Corrects CPU Frequency for Alpha (In reply to comment #2) > I've confirmed that app-admin/conky-1.4.0 works as well, however the Frequency > in MHz and Frequency in GHz both display as 0. I tested conky-1.4.0-r1 and ran into the same problem as Mike, the "Frequency in MHz" and "Frequency in GHz" both display as 0. The problem is CPU frequency in /proc/cpuinfo is different on alpha. For example, my 500MHz Alpha has "cycle frequency [Hz] : 499695364 est." while a 500MHz x86 system would have something like "cpu MHz : 499.695" This patch adds support for the cycle frequency used by /proc/cpuinfo on alpha. I've tested it on alpha, and it works as expected. However, I haven't tested this patch on non-alpha systems, so it should be tested on other arches before it gets added.
(In reply to comment #3) > Created an attachment (id=81467) [edit] > Corrects CPU Frequency for Alpha > > (In reply to comment #2) > > I've confirmed that app-admin/conky-1.4.0 works as well, however the Frequency > > in MHz and Frequency in GHz both display as 0. > > I tested conky-1.4.0-r1 and ran into the same problem as Mike, the "Frequency > in MHz" and "Frequency in GHz" both display as 0. The problem is CPU frequency > in /proc/cpuinfo is different on alpha. For example, my 500MHz Alpha has > "cycle frequency [Hz] : 499695364 est." > while a 500MHz x86 system would have something like > "cpu MHz : 499.695" > > This patch adds support for the cycle frequency used by /proc/cpuinfo on alpha. > I've tested it on alpha, and it works as expected. However, I haven't tested > this patch on non-alpha systems, so it should be tested on other arches before > it gets added. > Thanks a plenty. Committed to CVS.
How do we get the keyword ~alpha added then? This bug has been here for a while and I've since updated to the latest version, it still works fine. Is there a reason the keyword still doesn't show up when I do a sync? Do I need to post this someplace else?
(In reply to comment #5) > How do we get the keyword ~alpha added then? This bug has been here for a > while and I've since updated to the latest version, it still works fine. Is > there a reason the keyword still doesn't show up when I do a sync? Do I need > to post this someplace else? conky 1.4.1 includes the patch attached to this bug (Attachment #81467 [details, diff])[1]. The patch fixes CPU frequency detection on Alpha. Once conky 1.4.1 hits portage[2], I'll test it, add the ~alpha keyword if there are no problems, and close this bug. In Comment #4, the phrase "Committed to CVS" meant that the patch was added to the upstream cvs, not portage. [1] http://conky.sourceforge.net/changelog.html [2] http://bugs.gentoo.org/126008
conky 1.4.1 is in portage now, but it doesn't compile for me, see Bug #129639. I'll test and keyword conky once that bug is fixed. Thanks for being patient!
Added ~alpha keyword. Thanks to everyone who tested and helped get this program working on alpha.
