On Sun, 21 Aug 2011 07:27:02 -0600 Donovan Lavinder drmario2007@gmail.com wrote:
That's strange. I have tried rewriting the firmware so I COULD provide you the text file... It froze after couple complaints of 4-byte RDID not found (it just ignored that before), and I tried just "flashrom", same thing. Now that's a can of worm. It was 100% successful - verified and signed. Now I am somewhat confused. I may have to wait for a while (thankfully I still have a Windows laptop so I could write up the report on progresses of the firmware ROM.)
the 4 byte RDID warnings should not matter. the chip you have does not need it. it is just printed for other chips that are probed for by flashrom. you can use the -c <chipname> parameter to probe for the correct chip only. regarding the lockup i can't say much without a log, but that it should not happen. :) does it reliably happen while probing for the same chip or is it (seemingly) random? could you also please define "froze" precisely? is it flashrom alone or the whole OS etc?
The flashrom is the only program that froze when looking for the flash chip. I have tried cold reboot - same thing happened. That here, was a head-scratcher since it is not even supposed to happen. Probably it could be because the firmware unmounted itself (shouldn't happen). The whole OS ran fine otherwise (I could close the frozen flashrom program with ease). I am wondering how could SuperIO refuse the handshake between the flashrom - I left it alone for a while, no change in the behavior (as far as the verbose terminal emulator was concerned).
On Sun, Aug 21, 2011 at 8:05 AM, Stefan Tauner < stefan.tauner@student.tuwien.ac.at> wrote:
On Sun, 21 Aug 2011 07:27:02 -0600 Donovan Lavinder drmario2007@gmail.com wrote:
That's strange. I have tried rewriting the firmware so I COULD provide
you
the text file... It froze after couple complaints of 4-byte RDID not
found
(it just ignored that before), and I tried just "flashrom", same thing.
Now
that's a can of worm. It was 100% successful - verified and signed. Now I
am
somewhat confused. I may have to wait for a while (thankfully I still
have a
Windows laptop so I could write up the report on progresses of the
firmware
ROM.)
the 4 byte RDID warnings should not matter. the chip you have does not need it. it is just printed for other chips that are probed for by flashrom. you can use the -c <chipname> parameter to probe for the correct chip only. regarding the lockup i can't say much without a log, but that it should not happen. :) does it reliably happen while probing for the same chip or is it (seemingly) random? could you also please define "froze" precisely? is it flashrom alone or the whole OS etc?
-- Kind regards/Mit freundlichen Grüßen, Stefan Tauner
-
Donovan Lavinder -
Stefan Tauner