View Single Post
Old 09-08-2010, 03:06 PM   #42
customelectronic
Member
customelectronic began at the beginning.
 
Posts: 18
Karma: 10
Join Date: Sep 2010
Device: PRS900
Quote:
Originally Posted by porkupan View Post
If you have a diagnostic MS card, you need to take it out of the device in order to be able to install anything. Or you can install packages from the diagnostic MS card. One or the other. I wonder if that's it.
The ms duo card is only a 16Meg, it is no good for installing; all attempts at an actual flash style install used the internal memory of sony with /temp. The MS did work as a diagnostic MS card which triggered the Sony to factory reset earlier, but no evidence that the script actually ran correctly. I tried both with the card in an out during boot, after boot, hard reset, test shutdown -- restart -- and I erased it for this last test, and only did a touch /Sony Reader/software/autorun.xml which does work to get the sony into test mode. I have also tried with all autorun.xml & scripts on memory stick in all combinations of root, Sony Reader subdirectory (I think that's the name... too tired to remember ) and the software subdirectory. 8 combinations tried -- none were good.

Ps. The bash scripts that make the diagnostic card use dd if=/dev/stdin or of=/dev/stdout occasionally. on Slackware 12/13 my version of dd gives an error message and won't run; it is only dd that refuses to use these dev files -- the header code works correctly. Since dd defaults to stdin, and stdout, simply removing the extra parameter made the scripts run correctly.

I tried the diagnostic card recovery, and the serial version, both as untarred/zipped and after running the script on these two versions and checking them. ...again In all combinations... no evidence that it ever changed the OTG usb driver to the serial one. all kernel dmesg/lsusb -(long format) showed only bulk storage device. Timing of plugging in the cable made no difference either.

The sony boots very regularly with the LED flashing about 10 times during startup. It's a champion plain sony reader.... The only quirk is that if the USB is plugged in during the early part of the boot (but after the boot is started), it will sometimes delay the boot for a significant period of time and may never switch to a mounted filesystem over usb. I get a "No media" error when mounting it when that happens, but that is pretty obviously an unplanned for combination of events. Simply unplug and replug restores normal USB bulk storage operation. It doesn't crash anymore...

sigh.
customelectronic is offline   Reply With Quote