Failure to find DMS with bootable hack disk

[seaofvapours]

Hi,

I have a known good DMS, but when I boot from the Hack and Repair CD, after Linux boots, and after I then insert the DMS cartridge, I get endless 'USB device 1-3......etc. ' messages and never get to the screen where I can search for a DMS. From searching this forum, I think maybe the boot disk USB drivers have some incompatibility with my machine (Thinkpad T40)?

So, is this correct, or am I just being stupid? If it's correct, anything I can do about it with this machine (I only have access to Thinkpads).

Thanks,

[seaofvapours]

To clarify the above slightly. Once I boot to the "Phathack Flash/DMS Building Disk" main screen, I then insert the 'known good' DMS cartridge and this produces an endless set of the following messages in green:
"USB 1-4: new high speed USB device using ehci_hcd and address n" (where n is a series of numbers from 1 to 1xx).

[Firefox]

I can't add much other than to say i have successfully used a T40 Thinkpad with the Phathack CD in the past. So it's not necessarily that.

Is it a USB 2 cradle?

Make sure nothing else is USB connected at all. Just the cradle. No USB mouse, nothing. Also unplug any PC Cards from the slots - keep it bare minimum. Then boot with the Cradle connected but DMS out.

If you've already done that, I'd probably suggest going to another PC and trying there....

[seaofvapours]

Thanks for the info.

I've given up with the disk and tried to to it manually. Problem now is that I don't think the hack is working on the Phatbox. I couldn't find a bootlog anywhere, and when I tried the newly built DMS cartridge in it it eventually came up with No CD, which I take to mean that the firmware didn't get updated? (I did remove forceupdate when I built the new DMS cartridge, but could not find forcesettings anywhere to delete).

Also, I'm not seeing a bootload.log - is this supposed to appear of PHTSYS after the hack has been applied?

[Firefox]

Search is your friend on this site -   - but change the search period to all messages (not default of one week)

You need to create a bootload.log file yourself in root of PHTSYS before you boot to see results of the boot checks. Just copy any text file there and rename it to bootload.log

After a boot you will see the contents have changed.

Post that here and someone will comment...

[seaofvapours]

Thanks!

Right. I've restored the DMS back to the working drive, checked that it still works, put the phathac back on it again then left it running for about 15 minutes, just to make sure.

I've got some logs - though not a bootload.log as I failed to notice that the file had to have non-zero bytes prior to doing this :-(

However, the phatpatch.log is 495 bytes, and can't be opened. The patch.log contains the following:

[code]
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
[code]

....and that carries on, presumably until I stop it by turning off the car/HU.

Ummm......so what does that mean please anyone?!

Thanks.

[seaofvapours]

Hmm.... finally got the following, which I take to mean it's worked, based on other posts ?

 -------------------------------------------------------------
patch.log:
--------------------------begin----------------------------
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
----------------------------end----------------------------
 
 
 
-------------------------------------------------------------
phatpatch.log:
--------------------------begin----------------------------
PhatPatch v0.2 -bushing
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, device id=22ba
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!
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
----------------------------end----------------------------

So, looks like my manual attempt to create the new disk isn't working then. Can anyone confirm whether this SHOULD be possible using Windows XP diskmgmt.msc?

What I did was create:
A 64MB Primary partition, FAT32, labelled it PHTSYS
Then created an extended partition on the rest of the 80GB drive
Then created a drive which I labelled PHTDTA in the extended partition - I had no options but to make this NTFS (is that correct?)
Then I ran the dd.exe command, which worked and created a DMS I could manipulate in PMM.
Then I used the firmware update to install the 7.02 Audi level on the DMS.
Finally removed the 'forceupdate from PHTSYS - I could not find a 'forcesettings' file to delete.

Is anything wrong in the above?

The odd thing is, that looking at the DMS whilst in the cradle and after it had been in the car, the PHTSYS partition showed as 260MB, not 64MB..... I don't understand that, and hence the question about exactly how to create the partitions under XP (errr......sort of not something I do a lot of, this - as if it wasn't entirely obvious - so apologies for the dumb questions :-(  ) Oh- and I've done the build of the new drive at least twice now, with similar lack of success - I get 'No magazine' or 'No CD', and endlessly blinking green light on the Phatbox.

Any pointers gratefully received as I've been at this for 8 hours now and don't seem to be getting very far!

[seaofvapours]

Further to the above:

I just checked the original, working DMS in MickeySoft XP disk manager and IT shows up as having a 260MB PHTSYS partition. Even more confused now :-(

Also, the PHTDTA partition is showing as FAT32, so I presume my problem could, at least in part, be that my new one was formatted as NTFS - yet, I had no option in the disk manager window to do anything OTHER than format it to NTFS.... Hmmm... Definitely need pointers as to how to format this properly please!

[seaofvapours]

Sorted! (Partially at least).

The DMS is now working with the new drive, albeit with only a 32GB PHTDTA. Now to find someone with a machine that will boot and see it under the Linux boot disk.

Last question remaining is: are they any alternatives for getting the PHTDTA drive formatted at > 32GB?

Thanks,

Mike

[sbingner]

use the phatnoise rescue cd

[seaofvapours]

Thanks. I tried that and I get:

usb.c: USB device not accepting new address=n (error=-71)

where 'n' starts at 2 and goes upwards on each successive error.

Is it possible that there is a problem with my Phatnoise USB 2.0 cradle which could explain it?

[judb]

It would be something with your USB controler I'd guess, not the cradle if it works in windows but not on the boot cd's...

With windows XP you cannot format fat32 greater than 32 gigs due to Microsoft being smarter than everyone else and programming it that way.

you could use a tool like partition magic to redo that partition as fat32 or use another computer with your cradle and the boot CD to fix it. (find a PC that the boot CD will work correctly with.)

Lastly, you could try using VMWare and put the USB device into the VMWare session and try using the boot CD in the VMWare session.  I am not going to do a full write up on how but if it works in windows (the cradle) it SHOULD work via VMWare using the boot CD iso / burned disc put into the VMWare session.

Best of luck.

[sbingner]

http://www.mager.org/mkdosfs/

[seaofvapours]

Hoorah! Sorted and working at last - that was traumtic :-)

Thanks to everyone for all the assistance.

I finally found that my Thinkpad motherboard has a (common) problem where the USB ports have been over-loaded, hence a) Linux can't use the ports properly and b) I need a new motherboard. Anyway, eventually sorted it using mkdosfs - fine utility :-)

Mike