Author Topic: Pretty sure I broke my Phatbox - rapidly flashing greed LED - Not Broken!  (Read 10928 times)

0 Members and 1 Guest are viewing this topic.

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Well, I tried the hack.  Things didn't go right, right from the start.  The dmsutils batch files wouldn't run under Win XP, I had to boot into safe mode to get them to run.  I did successfully get to the dmshack to run, and put the dms into the PB.  The first mistake was that I turned on the radio, and pushed the CD button to activate the PB, but it defaulted to it, so I managed to switch to the radio, and then immediately back to the PB.  Within seconds the "Welcome to PB..." message came on.  I tried removing DMS and trying again, but always the same.  So I pulled the DMS and checked the patch.log file.  All was unverified except the first one.  Since its a VW I thought maybe I needed to cycle power.  I did that and then it seemed to be working, but No Magazine came up several times.  Each time it switched back to radio, and I switched back to Phatbox. Then NO CD came on. I pulled the DMS and checked the patch.log.  Only the first four were verified.  I tried the power cycle thing again, and now the box just rapidly flashes the green led.  I restored the DMS by deleting all files, and copying back the full back-ups I had taken of both partitions (the DMS was empty, so files were not too big).  No change.  Then I thought maybe I should try applying a new firmware - an act of desperation.  No change on that either.

So is it unrecoverable?

I was too stupid to keep a copy of the patch.log file...

Jeff
« Last Edit: June 07, 2007, 10:41:09 am by jheyerman »

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #1 on: June 06, 2007, 09:59:31 am »
corrupt ramdisk.sig

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #2 on: June 06, 2007, 11:33:13 am »
Thanks for the reply,

This morning I reran DMShack, corrupted the ramdisk.sig file and put the DMS in the PD, applied power, and no change. Just rapidly flashing greed LED.  No files were written in the log folder.

Jeff




Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #3 on: June 06, 2007, 01:43:26 pm »
check phtsys, do you see the file forceupdate or forcesettings?  if you do, remove them

if you've reapplied the firmware then that could be part of the problem as it overwrites files used in the hack process with phatnoise versions.

I'd suggest reformat phtsys, apply firmware to the drive but check again and remove the forceupdate / forcesettings files before ejecting and then see if you can get the box to play.

Also, bootload.log is always a good tool if your system isn't starting up right. 

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #4 on: June 06, 2007, 02:03:40 pm »
It's back!!!  I left it for half an hour or so, and the leds had gone out on the PB.  I turned on the radio, and got "Check magazine", and a few seconds later it gave me the "Welcome to Phatnoise...".  I let it play for a while, and checked the patch.log file, and it had gotten further - maybe only four items left "Unverified".  I had to go to work; I'll post the patch.log file when I get home. 

On a seperate note, I am not clear on the >120gb drive status.  Is there more risk with using a >120 gig drive in terms of a) getting the DMS to work with the PB - does the 1.2.1 hack method do all that's required, or is another file needed and b) having the DMS not work with PMM 3.92.   Are there certain brand drives that are more likely to give a problem with 3.92 than others?

Thanks again - I appreciate the support.

Jeff

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #5 on: June 06, 2007, 09:16:15 pm »
you only have to download the newer kernel for LBA48 support for greater than 120 gig drives to work properly.

(well thats mostly all you have to do.  PMM can be picky about working with 160's but I got mine working last night after doing the initial DMS setup and sync using 1.87 PMM and then switching back to 3.95)

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #6 on: June 07, 2007, 12:07:14 am »
Wow!  Looks like it is all patched up - here is the patch.log file.  I didn't get a patchverify.log, though...

Code: [Select]
: No such file or directory
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
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!
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 0000 eb00
Verified!
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 0000 eb00
Verified!
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0001, device id=22bf
offsets 0x555 and 0x2aa verified
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
Detected patch 1 already applied
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Detected patch 2 already applied
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Detected patch 3 already applied
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Detected patch 4 already applied
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Detected patch 5 already applied
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Detected patch 6 already applied
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0000 03a0
Detected patch 7 already applied
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 02db eb00    Actual: 0000 eb00
Detected patch 8 already applied
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 02f7 eb00    Actual: 0000 eb00
Detected patch 9 already applied

Now to run patchclean, and then to try out my new 160gb drive!  Driving with flac paradise, here I come!

Jeff

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #7 on: June 07, 2007, 01:00:21 am »
Just to confirm for the 160gb drive, I replace the file named "linux" in the phtsys partition with the file "linux-lba48-nolog" (renaming it to linux) from the dmsutils dir.  Do I need to do anything with the linux.sig file?

Thanks again,
Jeff

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #8 on: June 07, 2007, 01:33:36 am »
yes, and no.  You could even delete/rename the .sig file if you felt like it...

Offline jheyerman

  • Getting the hang of things.
  • **
  • Posts: 56
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #9 on: June 07, 2007, 03:11:34 am »
Happy to report that 160gb drive is working in PB, and in PMM 3.92  ;D ;D ;D

Only problem I had was the newdms.bat script had an error during formatting of the PHTSYS partition.  I did it manually, and copied over the backup of that drive from the original DMS.  I took judb's advice and did original S/U in PMM 1.87, and then PMM 3.92 gave me no issues.  Now to copy over all the .flac files!

In case anyone is interested, the drive I used is a Seagate Momentus (ST9160821A) 160GB 5400.3 Ultra ATA/100 5400RPM 8MB Cache 2.5"

Thanks sbingner and judb for all your hard work and support.  I am a very happy PB owner.

Jeff

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Pretty sure I broke my Phatbox - rapidly flashing greed LED
« Reply #10 on: June 07, 2007, 03:14:08 am »
Gratz!