Wednesday, March 23, 2011

Phctool bug with kernels 2.6.38

Hey guys,

unfortunately another bug in phc and phctool.... with 2.6.38 kernel throttling interface has moved, so you get:



Traceback (most recent call last):
  File "./phctool.py", line 468, in <module>
    app=appgui()
  File "./phctool.py", line 83, in __init__
    self.throttling=throttling.throttlecontrol(self.cpuinfo.data)
  File "inc/libs/throttling.py", line 16, in __init__
    self._cpus_have_interface()            ##check which CPU has a trottling
interface
  File "inc/libs/throttling.py", line 23, in _cpus_have_interface
    if
os.path.exists('/proc/acpi/processor/'+self.cpus[cpu]['acpi']['acpiname']+'/throttling')
&
os.path.exists('/proc/acpi/processor/'+self.cpus[cpu]['acpi']['acpiname']+'/limit'):
KeyError: 'acpiname'

this has already been reported to bugzilla, I wrote a patch but it's just a temporary solution, you can get it from here: https://bugs.gentoo.org/show_bug.cgi?id=360009

The file needs to be placed in

/usr/share/phctool/inc/libs/cpuinfo.py
 If anyone has some python skills and/or a CPU with throttling interface available (I don't), feel free to post a comment so we can solve this!


Cheers

2 comments:

  1. Hi. Old message maybe but you helped me out. I found a workaround. I edited the phctool.py file to comment out all instances of throttling, and also commented out the "T" opts in generic.py and renamed throttling.py to something innocous. Crude I know but phctool loads but I haven't tried it out yet. I'll post later to let you know how it turned out. Thanks again.

    ReplyDelete
  2. You're welcome ^_^

    Actually it's a strange issue, because phctool seems to have lost its developer so I don't know what to do. Anyway AFAIK throttling is no more supported for new CPU or new drivers so it could be removed...

    ReplyDelete

Loading...