Hi Chris, I sanity checked this with a clean install, installed fwts from ppa:firmware-testing-team/ppa-fwts-stable and got:
dpkg -l fwts Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii fwts 0.22.10~m FirmWare Test Suite ubuntu@ubuntu-MM061:~$ fwts -v fwts, Version V0.22.10, Thu Mar 24 09:52:06 GMT 2011 Maybe you haven't picked up the latest libfwts.so.1 - this contains the core fwts support library and this maybe an older version. Can you try the following: strings /usr/lib/libfwts.so.1 | grep "^V0.22" You should get: V0.22.10 Maybe removing and re-installing may help. Not sure why you have this problem. Colin On Fri, 2011-03-25 at 13:40 -0400, Chris Townsend wrote: > Colin, > > I updated to the latest stable fwts and I still have the problem. > However, I wonder if the package is incorrect: > > $ dpkg -l fwts > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Description > +++-==============-==============-============================================ > ii fwts 0.22.10~m FirmWare Test Suite > > $ fwts -v > fwts, Version V0.22.07, Sun Mar 6 14:00:29 GMT 2011 > > > I did try pressing 'q' and then Enter when the problem occurred and it > did not break out of the test. I still had to hit Ctrl-C to end the test. > > Thanks, > Chris > > On 03/23/2011 04:53 PM, Colin Ian King wrote: > > On Wed, 2011-03-23 at 15:32 -0400, Chris Townsend wrote: > >> Hello, > >> > >> When running fwts version 0.22.07~m, it hangs at the "Check _CRS > >> (Current Resource Settings)." stage and will not complete. > >> > >> Any ideas of what is going on here? > > It hits an AML breakpoint opcode when evualting \_SB_.PCI0._CRS and the > > ACPICA execution engine requires some input (it goes into debug mode). A > > workaround > > is to press 'q' followed by enter. I will work on a correct fix later. > > > > Colin > >> Thanks, > >> Chris > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~firmware-testing-team > >> Post to : [email protected] > >> Unsubscribe : https://launchpad.net/~firmware-testing-team > >> More help : https://help.launchpad.net/ListHelp > > _______________________________________________ Mailing list: https://launchpad.net/~firmware-testing-team Post to : [email protected] Unsubscribe : https://launchpad.net/~firmware-testing-team More help : https://help.launchpad.net/ListHelp
