Author Topic: DMS working in PC but not in the car  (Read 54606 times)

0 Members and 1 Guest are viewing this topic.

Offline The_Dude

  • Newbie
  • Posts: 9
  • PhatHacker
Re: DMS working in PC but not in the car
« Reply #60 on: May 27, 2006, 12:14:37 pm »
I repartitioned and reformatted the new DMS and it still will not work.  Could someone tell me if the patch actually ever completed?  It looks like it did not.  But, the patchverify.log says everything is verified.

patchwrite.log:
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, device id=22bf
Resetting flash.
Testing patch locations:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0033 1a00    Actual: 0033 1a00
Match! Programming...
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, device id=22bf
Resetting flash.
Testing patch locations:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0033 1a00    Actual: 0000 1a00
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0026 1a00
Match! Programming...
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
firs
<Then some null and garbage here>
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, device id=22bf
Resetting flash.
Testing patch locations:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0033 1a00    Actual: 0000 1a00
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Mismatch!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Mismatch!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Mismatch!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Mismatch!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Mismatch!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0001 03a0
Match! Programming...

End of patch.log:
2048+0 records in
2048+0 records out

hdparm - get/set hard disk parameters - version v3.9

<options omitted to save space in post>

PhatPatch v0.4 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0000 03a0
Verified!
done
: No such file or directory
: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory

Following printed twice in patchverify.log
Starting Patch Process
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0000 03a0
Verified!

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: DMS working in PC but not in the car
« Reply #61 on: May 27, 2006, 03:02:30 pm »
according to this your box is patched just fine.

Does the new dms have a bootload.log file on it?  Does anything get written to it?  sorry if I've already asked these questions.. this thread is getting rather long.

Offline The_Dude

  • Newbie
  • Posts: 9
  • PhatHacker
Re: DMS working in PC but not in the car
« Reply #62 on: May 27, 2006, 09:58:49 pm »
Okay, so it is patched.  The old DMS always says your system has been unlocked when I put it in the Phatbox.  I thought maybe because it is doing this  (constantly running the patch) and some of the mismatch messages in the patchwrite.log could mean the box was not patched.

The new dms does have a bootload.log file, but at first it was empty.  Then I ran a fsck on the new DMS and it found errors and I had to recreate it from the boot cd.  Then, the new DMS had nulls in the bootload.log.  I cleared out the nulls and tried again.  Now it is just empty.  I am starting to think the new DMS hd is bad in some way.  It works fine in the cradle or in a 2.5 inch enclosure, but it just doesn't seem to work in the Phatbox.  

I still get lights with the new DMS.  First the red light, then immediately after the green light comes on.  Both stay on for 30 seconds to a minute.  Then they both go out and sequence repeats.

Maybe I'll try returning the drive for a new one.

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: DMS working in PC but not in the car
« Reply #63 on: May 28, 2006, 03:26:44 pm »
There has to be data in the bootload.log (at least a few Kilobytes in size) in order for it to be written to.

Make a copy of the phatbox.ini as bootload.log again and try booting the drive.  That should put some info into the bootload.log.

Also make sure you are letting the lights turn off the phatbox before pulling out a drive as that can cause filesystem errors.

Offline The_Dude

  • Newbie
  • Posts: 9
  • PhatHacker
Re: DMS working in PC but not in the car
« Reply #64 on: June 14, 2006, 12:31:24 am »
Finally success !!!

I had to use the manual method to write the signature to the hard disk.  But, that fixed the issue.


http://forum.phathack.com/cgi-bin/yabb2/YaBB.pl?num=1123119033


« Last Edit: June 14, 2006, 12:31:50 am by The_Dude »