Welcome to the MacNN Forums.

ligux · 12:10 AM

Hope this is the right forum.
My computer doesn't recognize my firewire units (2 Firewire HD) and it used to.
Any clue? Thanks in advance
I have tried in both OSs(9and X)

zigzag · Oct 5, 2003, 10:23 AM

I haven't had this problem but I think I've read that resetting the PRAM sometimes helps.

ligux · Oct 5, 2003, 10:29 AM

Thanks for this answer, but how do I reset the PRAM? is that safe?

ligux · Oct 5, 2003, 10:40 AM

Ok I have found it out,
Command+opt+p+r
Hope it works, meanwhile any other idea-help is appreciated.

ligux · Oct 5, 2003, 11:06 AM

It didn't work, still not Firewire recognised.

ligux · Oct 5, 2003, 12:32 PM

I have just restarted my computer after switching it off for a couple of minutes, and now it recognise what is plugged into Firewire sockets, but it only happens in OSX because still having the annoying bus error message when I try to start OS9.

zigzag · Oct 5, 2003, 01:24 PM

Originally posted by ligux:
I have just restarted my computer after switching it off for a couple of minutes, and now it recognise what is plugged into Firewire sockets, but it only happens in OSX because still having the annoying bus error message when I try to start OS9.

Good to hear. Sorry I didn't tell you how to reset the PRAM - I didn't know how myself, but I should've mentioned that.

Yeah, sometimes all it takes is a restart.

Angus_D · Oct 5, 2003, 01:46 PM

Try booting into OpenFirmware (cmd-opt-o-f at boot), typing

Code:
reset-nvram
reset-all
continue

That fixed it for me. A simple PRAM reset might be all it takes, I have a vague recollection I needed my entire NVRAM to be reset.

SSharon · Oct 5, 2003, 02:21 PM

just a little aside note . . . what does reseting the pram actually do and what does the nvram do? I mean how does it effect me the user as in what preferences are lost, reset time, other options, etc.
thanks

ligux · Oct 5, 2003, 02:39 PM

[QUOTE]Originally posted by Angus_D:
[B]Try booting into OpenFirmware (cmd-opt-o-f at boot), typing

Code:
reset-nvram
reset-all
continue

Thanks Angus, I will do it right now, and I will be back to tell you if it worked for this case.

ligux · Oct 5, 2003, 02:49 PM

You did it Agnus, congratulations. I am writing from my OS9 and Firewire connections working.

Cadaver · Oct 5, 2003, 03:37 PM

Originally posted by SSharon:
just a little aside note . . . what does reseting the pram actually do and what does the nvram do? I mean how does it effect me the user as in what preferences are lost, reset time, other options, etc.
thanks

Things that might be "lost" are date/time, startup disk preference, startup (default) screen resolution, and Open Firmware password (I think; check me on that one). Nothing critical at all, but occasionally a glitch in the PRAM can prevent a machine from starting properly (or failing to recognize a processor upgrade, RAM upgrade, etc).

rlmorel · Oct 5, 2003, 09:55 PM

Someone once told me that some 3rd party software vendors used the PRAM to store certain settings (against Apples guidelines), ones you would not suspect. This could make your computer act very strange. I found that resetting the PRAM (when I used OS9) could fix a variety of seemingly unrelated issues. This does not seem to be an issue in OSX.

Also, I have heard resetting your CUDA switch on your motherboard can also fix the Firewire problems...

ligux · Oct 5, 2003, 11:58 PM

Also, I have heard resetting your CUDA switch on your motherboard can also fix the Firewire problems..

I am back again, and I confirm that to reset theNVRAM works for that start up. But the problem remains.
This morning when I have started up my comp. I have had the old message again :

System error
�???1125F�
bus error

So I think I will have a go on resetting the CUDA switch, how do I find it. and how do I reset it.

Nivag · Oct 6, 2003, 06:38 AM

ligux, i noticed from your Signature your using 9.2.1 - You may want to update that to 9.2.2 it may solve a few firewire problems.

ligux · Oct 6, 2003, 06:46 AM

Updating might be an option , but I have been using this version until now with no problem.
Anyway, not at home now , but I will check it because I am not sure but maybe I forgot to update my signature. Anyway thanks for the advice.

ligux · Oct 6, 2003, 09:57 AM

Updating my profile right now. I am using 9.2.2
The only way to get into oS9 is reseting PRAM or Booting into Firmware, avoiding the error, any clue how to solve this error?

Nivag · Oct 6, 2003, 10:50 AM

Which Firewire driver are you using?

Apple says OS 9.2.2 should be using 2.8.5, but i just checked mine and it's version 2.8.6. I'm guessing this might have something to do with OS X.

Check the Extensions in your System Folder.

You could try deleting any Prefs in the OS 9 folder relating to Firewire.

Also what make are your FW drives?

ligux · Oct 6, 2003, 11:49 AM

Thank you for your post, but I solved the Firewire failure when I reseted the NVRAM (see above).
The Problem I have right now is with a bus error, maybe my fault for keeping in this topic (Firewire fails) and now the problem is different, though one took me to another.
Anyway I am gonna check the extensions, I haven�t thought about them, thanks
By the way Fwire driver 2.8.5.

ligux · Oct 6, 2003, 02:13 PM

Great Nivag.
The problem was in the extension files, I reconfigured them back again selecting �full� and now is smooth.
I mainly checked the Video-Audio and ethernet extensions which seem to be the ones to give problems.
Thanks to everyone.