Firewire bei Imac G5 defekt.

C

Catilina

Mitglied
Thread Starter
Dabei seit
06.12.2005
Beiträge
24
Reaktionspunkte
0
Hallo, ich hab einen IMAC G5 20", und Firewire funktioniert nicht, wird auch vom Systemprofiler nicht erkannt. Laut Hardwaretest ist alles in Ordnung. Keine Garantie mehr. Was kann man da machen?
Man hatt mir folgende Tipps gegeben:
PRAM-Reset: hatt nicht geklappt.
Mit gedrückter Shift-Taste starten: hatt auch nicht geklappt

NVRAM-Reset: kann mir jemand erklären wie man diese beidenResets macht?
PMU-Reset :

Oder was kann man sonst noch machen.. hatt das schonmal jemand gehabt?
Grüsse
Catilina
 
öhm... Threadnachobeschieb... weiss da wirklich keiner was:confused:
 
Scheint einfach kaputt zu sein. Bei sowas wird nach meinen Erkenntnissen im Rahmen einer, nach Deiner Beschreibung in deinem Fall nicht mehr vorhandenen Garantie, das Board ausgetauscht. Ich würde mal zu meinem Appledealer gehen und da fragen, ansonsten tippe ich auf einen Hardwaredefekt.

dasich
 
Hallo Catilina,

willkommen im Forum! :)

Also beim Einschalten [APFEL]+[ALT/WAHL]+[o]+[f] gedrückt halten bis die OpenFirmware kommt und dann loslassen. Jetzt erscheint ein Prompt und Du gibst ein
reset-nvram [ENTER] (Achtung, amerikanische Tastatur - über 8)
reset-all [ENTER]

Da geht auch nichts kaputt. :)

Falls das noch immer nicht hilft, ein SRAM-Reset:
- Mac ausschalten, Stecker von der Netzsteckdose und Mac ziehen
- 1 Minute warten
- Stecker wieder einstecken

Und da auch net :)

Viele Grüße
Michael
 
broken FireWire interface
Tue, Nov 29 '05 at 07:46AM • from: robg


Sorry for the delay in getting today's hints online -- at some point this morning, my Mac decided to stop recognizing any FireWire devices that were connected. It didn't matter if I used the front-panel port, the back-panel port, or the FireWire2 port -- nothing worked. Scary, to say the least. So I took some time to troubleshoot and (thankfully) fix the problem, and thought I'd document it here, in case this happens to someone else.

I didn't do anything odd to cause the problem, as far as I can tell. I just plugged in my iPod, noticed it didn't show up in iTunes, and then quickly discovered that nothing at all that used FireWire was functional.

I tried shutting down and booting, restarting, logging in as another user, even resetting PRAM and NVRAM. Nothing worked; my devices were simply gone. I knew the ports were generally OK, though, as my iPod dock was charging the iPod, and my iSight's green light would flash when it was plugged in. It's just that the machine didn't want to admit that it knew anything at all about FireWire.

I then opened Console, in Applications -> Utilities, and opened to the system log. There I found tons and tons of these entries (line breaks added for narrower display):
Nov 29 05:17:21 gargantua5 kernel[0]: FireWire (OHCI) Apple ID 42 built-in:
no valid selfIDs for more than 2 minutes after bus reset.
Nov 29 05:20:33 gargantua5 kernel[0]: FireWire (OHCI) Apple ID 42 built-in:
no valid selfIDs for more than 2 minutes after bus reset.
Nov 29 05:23:45 gargantua5 kernel[0]: FireWire (OHCI) Apple ID 42 built-in:
no valid selfIDs for more than 2 minutes after bus reset.
etc...
These repeat about every three minutes for as long as the machine was powered up. Not encouraging, to say the least. But this at least gave me something to Google on, which in turn led me to this Knowledge Base document. There they describe the standard FireWire troubleshooting tips (most of which I had already tried). Down at the bottom, though, they provided a solution that did work:
Shut down the computer.
Disconnect all FireWire devices and all other cables, except the keyboard and mouse cable(s).
Disconnect the computer from the power outlet and wait for 3 to 5 minutes.
Plug the computer back in and turn it on.
Reconnect the FireWire device(s) (one at a time if there is more than one) and test. Test with each FireWire port if you have more than one.
Being the lazy sort, I shortcutted it just a bit, and only pulled the FireWire and power cables. I let it sit for about 10 minutes, rebooted, and all was once again fine in FireWire land.
 
Zurück
Oben Unten