Welcome to the MacNN Forums.

LavalampCrtv · 09:55 AM

Well all, after updating to the newest upgrade (10.2.6), suddenly my firewire ports dont work. I ran FSCK, and nothing was wrong. repaired permissions. didn't help. rebooted. shutdown, waited 1/2 hour, rebooted, still no firewire recognition. I tested the cables, and they are kosher. I tested both an external firewire HD and my external 52x buslink burner, no go to either. Tried it on a buddies comp running 10.2 and all is fine with the cables and the drives. what is up with this stuff? I downloaded both the combo update and the regular update, and installed both repeatedly. nothing has worked so far. I have a PB G3 400 and 10.2.5 was running like a champ before the upgrade hit. so....if anyone can help debunk this one, I would greatly appreciate the help!

thanks
--jdf

Please post only productive comments.

Severed Hand of Skywalker · Jun 2, 2003, 11:51 PM

Aren't you polluting the timeline by talking about things that haven't happened yet?

Tisk tisk

wreks · Jun 3, 2003, 12:13 AM

are you talking about 10.2.6?

Try unplugging your computer and letting it sit for awhile. I hosed my firewire once when trying target disk mode and the unplug thing fixed it.

Powaqqatsi · Jun 3, 2003, 06:08 AM

Why do you people even ask if he's talking about 10.2.6 or 10.6, isn't that obvious ?

Maybe your firewire port is fried ?

CheesePuff · Jun 3, 2003, 07:56 AM

Originally posted by Powaqqatsi:
Why do you people even ask if he's talking about 10.2.6 or 10.6, isn't that obvious ?

Maybe your firewire port is fried ?

The only reason I clicked on this thread to see if any idiots replied like that.

[APi]TheMan · Jun 3, 2003, 09:13 AM

Originally posted by Powaqqatsi:
Why do you people even ask if he's talking about 10.2.6 or 10.6, isn't that obvious ?

Maybe your firewire port is fried ?

No, it's not obvious. Imagine someone reading this post 6 months from now.

It's always nice to be specific in not using silly acronyms or shady terms like ".6" that mean "10.2.6" just for those that might not know, or to be considerate to people in the future that could be looking at this thread as part of some research. Pretend that some time in the future you're having trouble with your FireWire port, so you launch up google and search a few terms. Then google hands you this as a link... Or maybe it doesn't because your search terms didn't include ".6". Get my drift?

Powaqqatsi · Jun 3, 2003, 10:38 AM

Originally posted by [APi]TheMan:
No, it's not obvious. Imagine someone reading this post 6 months from now.

It's always nice to be specific in not using silly acronyms or shady terms like ".6" that mean "10.2.6" just for those that might not know, or to be considerate to people in the future that could be looking at this thread as part of some research. Pretend that some time in the future you're having trouble with your FireWire port, so you launch up google and search a few terms. Then google hands you this as a link... Or maybe it doesn't because your search terms didn't include ".6". Get my drift?

Yeah, I get your drift.

But I don't look THAT far in the future

I mean 10.6, that's when ? 2006 ?? my bad, sorry.

]Originally posted by CheesePuff:

The only reason I clicked on this thread to see if any idiots replied like that.

Thankyou

Good reason btw.

+ spiral + · Jun 3, 2003, 01:16 PM

I did have a problem related to firewire starting with the 10.2.5 update. Lots of kernel panics. I read that the B+W towers have crappy firewire cards so i got a Maxtor firewire PCI card and i think that made things worse (the console was spitting up lots of firewire errors). 10.2.6 seemed to clear some of those issues up, but i still have a kernel panic 2 times a week, DVDs freeze often and all my web browsers crash often.

So to answer the question, yes i have had problems with firewire starting with 10.2.5 but it isn't totally dead. I have a Maxtor firewire PCI card you can try if you want. I took it out because i don't think my old tower likes it.

LavalampCrtv · Jun 3, 2003, 03:57 PM

Thanks for the help from the last post. I would think that a 3rd party card might be a culprit, but, this is just the standard issue card in a PB G3 400 firewire.

Good news though, There is a fix apparently. After calling some Mac guru buddies, they suggested that I boot into 9, then run diskwarrior from the disk. I borrowed their copy and did it. DiskWarrior cleared it up somehow. Just in case, I ran all of the tests from TechTool Pro, and then reset the PRAM. This seemed to fix the Firewire port issue., but it took a good 2 hours to run all the stuff.

good luck.

--jdf

[APi]TheMan · Jun 4, 2003, 04:38 PM

Originally posted by LavalampCrtv:
Good news though, There is a fix apparently. After calling some Mac guru buddies, they suggested that I boot into 9, then run diskwarrior from the disk. I borrowed their copy and did it. DiskWarrior cleared it up somehow. Just in case, I ran all of the tests from TechTool Pro, and then reset the PRAM. This seemed to fix the Firewire port issue., but it took a good 2 hours to run all the stuff.

DiskWarrior is amazing software. It's saved my data a few times enough that I'd swear by it.

To Powaqqatsi: OOh, I didn't mean to sound rude or condescending. Eeek! But I'm glad you see what I mean.

EnVoy · Jun 4, 2003, 07:17 PM

Unplug your machine!

I had the same thing happen. An Apple support article (can't remember which) said: disconnect all periferals (sp?) except keyboard/mouse/monitor. Shutdown, and unplug the machine. Let sit for 3-5 minutes.

Worked for me