1 Jun
2013
1 Jun
'13
4:38 p.m.
On Sat, 01 Jun 2013 23:30:04 +1000, Anthony K wrote:
- sudo lsmod > file-without-s3
Creates a file with headers "Module, size, & used by".
- ensure S3 is locked then connect to PC
OK. Done.
- sudo lsmod > file-with-locked-s3
OK. Done.
- sdiff-s file-with-s3 file-with-locked-s3| egrep '>'
Syntax error, corrected, in addition to file names: $ sdiff -s file-without-s3 file-with-locked-s3 | egrep '>' Reports nothing different. Hmmm... $ sdiff -s file-without-s3 file-with-locked-s3 Also reports nothing different. Same with: $ diff file-without-s3 file-with-locked-s3
- take note of what new modules are loaded by looking to the right of
the '>' sign
None.
- disconnect the S3
OK. Done.
- for each new module noted in step 5 above, do sudo modprobe -r module_name
No new modules popped up.
- unlock the S3 and mount it again
Didn't get to this point.
The phone should mount successfully! If not, then I'd really like to know what else the locked S3 does to the PC that requires a reboot to fix!
Me too! :)