Isight firewire issue

This is just FYI:
I purchased a new isight (12/06) and had a terrible time getting it to work on my dual processor G5. Finally, after fussing around with everything, I realized that, at least on my system, this is one of those firewire devices that is sensitive to anything but being plugged directly into the computer. So if you are having trouble with an isight, and it is plugged into another firewire device for convenience, you might try plugging it in direct. For me, it solved all the problems I was having, such as the green light being on, but the program not finding it.
Have fun!
Elsee
G5 Mac OS X (10.4.7)
G5 Mac OS X (10.4.7)

As Tony said above, "Known problem."
A bit more detail for those of you with the external iSight.
It has been detailed in a number of threads, but the external FW iSight may have a problem working with any other external FW device.
My suggestion is to only have the iSight plugged in to your Mac when you intend to use it. If there are other ext. FW HD's plugged in at the same time (or scanners or...) there is a chance that you may lose the device mounting, or if in the middle of a data transfer, data.
I personally have not had a problem, so it's hit and miss, but there have been enough reports to post this reminder.
Respectfully,
Bill Gallagher

Similar Messages

Isight firewire cam not working in iChat on Leopard.

After installing Leopard on my Powerbook G4 867 dvi, my Isight Firewire Cam is not working anymore
in Ichat on Leopard.
Any solutions, it worked fine under Tiger.
Isight firewire cam works fine wirh Skype, Amsn , Photobooth and Quicktime.

Alright. I've done quite a bit of testing now.
My system is (as stated below,) a 12" PowerBook G4, 867 MHz, 640 MB RAM, 40 GB hard drive, Combo drive, AirPort Extreme. It was purchased in Summer 2003, and while the OS has been reloaded, it hasn't been for a long time, and at present, the OS was an install of Jaguar that was upgraded to Panther to Tigard, finally to Leopard.
I was experiencing the issue mentioned. In my case, I use a FireWire miniDV camcorder for video in iChat. It has worked fine in the iChat AV beta in Jaguar, and iChat AV in Panther and Tiger.
Upon upgrading to Leopard, I get the "Slow Network" explanation for why I cannot use video (or hosting multiperson audio, or screen sharing.)
My research shows the following:
This occurs both on the upgraded install, and a fresh install. (To an external hard drive.)
Using Ecamm's PowerBoost allows me to use every option that isn't barred outright by lack of hardware (video effects.) This includes both "Slow Network" issues and "Insufficient CPU" issues (essentially just multiperson video.)
So my guess is that the "Slow Network" is indeed a "bug", and will be fixed by an update from Apple.

ISight (firewire external) and Adobe Onlocation software

Adobe requires a firewire to work with onlocation.
Is the external ISight firewire camera compatible with onlocation?
Has anyone tried to work with this on a Mac?
Specifically, I want to use the wave generator and vectorscope feature within the Adobe software.

Hi,
I have no information on this.
Having said that I have not heard of an App that could not see an External iSight.
I did find this http://kb2.adobe.com/cps/405/kb405857.html that lists known issues and some problems with some sample rates and Audio Card abilities.
7:05 PM Friday; September 16, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Firewire Issues: External Hard Drives & DV Deck Sony DSR 11 not recognized

So, I have this brand new $6000 Mac Pro that will not recognize a simple DV deck, nor the external HD's.
Thus, after spending seven hours searchig around last night, trying every configuration possible from updates, unplug power source, and everything else, I began making calls as of 4 am this morning.
I was referred to FCP Europe where I was informed that I needed FCS friver updates. (unavailable for 1.0.1) or perhaps it was a Sony issue. The deck & drives work fine with my G4 & Powerbook G4. With six fire wire ports on the Mac Pro, and nothing being recognized via a single fire wire port, does anyone have a simple, expedient solution? Thank you.

Ahhhh. Firewire issues. I'm convinced that these Macpros have some serious problems here. I am running a sony dsr11 also with a digi002. MY issues is bootup. . I have a mac pro with Tiger installed. My issue is I intermittently get a prohibitted error on bootup. The error looks like a no smoking sign without the cigerett. I have to re boot and sometimes the os boots right up othertimes not. I have sfound that I have to boot my sytem with noting hooked up first. It seems when you have high end firewire devices that the Bus just can't handle it. Real ****** for thos who bought the system for A/V work. Everything woks fine on my powerbook and my G5. Problem is with MACPRO! Do you also have other firewire devices hooked up? Are they daisychained together?
Vito

Isight firewire extension cable

I need a 10 foot (or 3 meter) firewire cable that will fit the isight holder. Apple refers to this as a thin firewire and it must be able to snap in the transistion piece between the camera and the stand. Most aftermarket cables are too thick due to rubber caldding around plug. Has anybody found such a cable that fits??? Or maybe cut down the rubber to make it fit ? I am familiar with hubs and repeaters and it appears that firewire depot sells a male/female extension, but i'm looking for just the simple solution of a single cable.

OK, so I've found a solution that, while not as simple and elegant as a single cable, solves my problem. After looking at male/ female cables at venders like L-COM.COM( which also sells a nifty shielded panel connector that also can act as a connector between the apple cable and an after market cable), I decided that this would work best with the short apple isight firewire cable so as not to go beyond the recommended distance for firewire without a repeater. Well, these short cables aren't cheap(20.00 to 30.00 bucks). Then add the male/ female aftermarket cable($ 30.00) and it's starting to add up. I also looked at doing a little grinding to the apple mount or adapter(depending on which you use) and shaving down the rubber overmolding on a aftermarket cable, and this looked like it might work. But the final solution was to buy a Griffin sightlight($20.00 through Amazon) that has a real short female receptical that allows me to use any 10 foot cable I wish. This way I spent the least amount of money and got a useful accessory to boot !!

External ISight Firewire with Onlocation

Should an external Apple ISight firewire camera work with CS5 Onlocation's real time field monitor (ie vector scope and waveform)?
Also, are there any other specifications for the type of camera that are compatible?
I understand that there are also caveats as non-support of avchd format.
I know this horse has been beat to death...
Thanks

To the best of my knowledge, any FireWire camera should work fine.

ISight FireWire with 2010 Mac Pro

I just picked up an iSight FireWire Camera off Craigslist. Since my Mac Pro does not have a FireWire 400 port I picked up a Belkin FireWire 800/400 9-pin to 6-pin cable.
When I plug the iSight into the rear FireWire 800 port iChat starts and the green light on top of the iSight camera is illuminated. I can see video clearly, but there is no audio. I check System Profiler and System Preferences and everything is listed and selected as they should be.
Does anyone have any ideas why I would not be getting any audio?

You have marked Malcom's response Helpful
Does that mean your question is "Answered"?
If you still have a problem, post back and we will try to offer suggestions based on your new details.
Mac Pro Quad Core (Early 2009) 2.93Ghz Mac OS X (10.6.4); MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.4)
LED Cinema Display; G4 PowerBook 1.67GHz (10.4.11); iBookSE 366MHz (10.3.9); External iSight; iPod touch 4.1

CS5 support is falling down - the famous firewire issue

As a loyal user of Adobe professioanl editing solutions for the last 10 years this past month has been a nightmare. When I inquired about upgrading to CS5 from CS3 I was advised during an online chat with an Adobe person here on the site to upgrade to CS4 and because of the timing I would get a complimentary CS5 upgrade. I purchased CS4 on April 14th and had so many issues it was never even used in the edit suite. When CS5 became available I decided to cut my losses and decided if I was going to have to go through all the hoops I might as well only go through them once with CS5. I have had numerous long discussions with Adobe "support" regarding various problems and now I am at the end of my rope. Even though they say the are taking notes during our conversations each subsequent "support" person claims to not know most of the pariculars discussed in previous phone calls. I didn't think I had to follow up each phone call with a note here but evidently that is the case. Today I have a deadline to deliver content on TAPE to a national cable network and the series contract could be in jeapordy if I can't deliver the first of 26 episodes. I CANNOT PREVIEW ON AN EXTERNAL TELEVISION MONITOR OR EXPORT THROUGH FIREWIRE TO MY MAIN DV DECK. It is a deck I have used for YEARS with Premiere CS2 and CS3 and i NEVER had an issue like this. I have been told repeatedly that the issue would be resolved and most recently on Tuesday of this week I was promised a callback between "1PM and 2PM" Central Standard time on Wednesday, THAT CALL NEVER CAME. When I followed up with another call MOST of the days previous discussion was NOT in my case notes. I was told my main Sony VTR and secondary JVC VTR were not HDV decks even though I have been using BOTH for many years for just that purpose and even though that didn't address the most pressing of all my issues which was just getting output through firewire to tape. After a very frustrating call I was promised another callback "in an hour" by a "supervisor". That call NEVER came. Both Adobe "support" and PNY Quadro "support" claim that they have "never" heard of the firewire issue even though it is all over the forums at Adobe. I will be posting this and every subsequent communication between me and Adobe on the forums, at Yelp and any other web sites that take reviews of professional video products. For the record just some of my other issues include the inability to capture HDV from the Sony HDV deck I have been capturing from for years, Alpha Glow not working and no split screen when doing color correction in a number of effects where it is offered. Also for the record I have tried turning off the MPE GPU acceleration to export to tape and that doesn't work either. System is a Supermicro dual processor motherboard with lots of ram and a Quadro FX 3800 operating with 64 bit Windows 7.

Read here:
http://kc.flex-radio.com/KnowledgebaseArticle50433.aspx
It may get firewire working again on your older deck with Windows 7. If the solution on that page works, then the problem is down to Microsoft, not Adobe.
FWIW, it's getting to be pretty well known around these parts that the current implementation of Adobe Customer Service is awful. That said, several Adobe employees, including some Premiere Pro engineers, have been hanging out in the forums recently. This is a big change from earlier releases of Pr, where an Adobe presence was rarely seen at all.
These same folks have also said that Adobe is working to improve their Customer Service. Like the inertia of a large ship forcing it to take a long time to change course, I suspect that it will take a bit longer for Adobe to make that improvement than it would for a smaller company. Don't give up on 'em just yet.
-Jeff

10.8.4 update firewire issues

10.8.4 update is not fixing the firewire issues that 10.8.3 caused with my macpro. my printer (professional Epson)
hard crashes when accessed. I'm reporting this because there are many people having firewire issues with firewire
printers and 10.8.3.

Use the workaround until the FW issue is resolved: use a USB cable.
OT

FireWire Issues - anyone else?

Have a PB G4, 1.67, with an Apple-repaired logic board [from Nov 08]. After latest Security updates, I have had trouble connecting either 800 or 400 FW drives. I've tried them on an iMac and iBook; both work. Tried different cables, three different drives [2 OCW, one Verbatim]. Nothing works. Wiggled cables. Used both bus and external power.
HELP please. I don't want to spend another $350 [plus postage from UK via APO] to fix this a third time [was a refurb, used from PowerMax, they looked at logicboard once, and then I used Apple's fix it service]. The Apple repair warranty expired in Feb 09.
I might try an $80 cardbus FW800/400 if I can find one still.
Thanks in advance.

Frustrating trying to get it to work .... You can zap the PRAM as well as reset the PMU anytime. At this point, if you haven't go ahead and do the PRAM and might as well do the PMU again. Reset PRAM. Note the effects are immediate, there's no advantage to waiting overnight:
1. Shut down the computer.
2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
3. Turn on the computer.
4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
6. Release the keys.
It sounds like you may have had hard drive issues that Drive Genius fixed for you. For comparison, did you run the Disk Utility disk repair after Drive Genius fixed the hard drive .. just to see if Disk Utility gives the drive a clean bill of health?
When you ran the Apple hardware test, did you run the extended test? Do you have either of the TechTool programs available? They do similar testing to the Apple hardware test, it would be interesting to see if they also say the hardware is OK.
You've reloaded the operating system a couple of times. Did you use the combo update to update to 10.4.11? I prefer that to letting Software Update make the updates, as sometimes it doesn't update correctly. Repair disk permissions before and after the update, too. Then run software update to pick up any other required updates.
You've, by this time, reset PRAM and PMU, I assume the PRAM reset didn't change anything? If so, sorry, but I don't know what else you can do. At this point, I'd take it to a genius at the Apple store, and get their opinion.
I didn't address sleep as I think you need to resolve the Firewire issue first, then see if there is a sleep problem.

Isight firewire mac mini 2011

hi
is it possible to connect a apple isight firewire on a mac mini 2011 with an adaptator firewire 400-800 ?
any one try this ?
thanks (and sorry for my bad english )

Hi,
Yes.
However it is about the type of adapter that you need.
See EZ Jim's Post here
9:29 PM Sunday; September 18, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

HT6065 Does this update fix the Facetime HD iSight Camera issue?

Does this update fix the Facetime HD iSight Camera issue?

Looking at its release notes, it does not specify a fix for that problem. However, you should install this update, as this fixes other bugs and improve performance. Open  > Software Update, and OS X 10.9.1 will show up

Firewire Issues Caused By Apple Isight!

For months, I've been having an intermittent Firewire audio problem, which I initially thought was A) Quad G5 or B) RME Fireface 800!
Testing the RME on another Quad G5 resulted in no errors, though for piece of mind a replacement RME was given! Back home the same intermittent problems occurred, it had to be the Quad G5???
Livid, this time I persisted on Google searching for FW issues, (a few hours later) to my amazement I came across an article on MacFixIt, that pointed the finger to Apple's own iSight FW camera, which I had connected!
The transcript below explains how to resolve this problem, it worked for me!
Mini-Tutorial: Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
As an Apple-invented technology, FireWire (IEEE 1394a and IEEE 1394b) should be (and usually is) one of the most solid and efficient means for interfacing with external peripherals. Indeed Apple's "i"-branded devices -- the iPod and iSight -- have, in large part, been made possible by the quick transfer rates, power sourcing, and hot pluggability offered by FireWire.
Occasionally, however, conflicts between FireWire-connected devices arise and can result in a variety of issues including DV cameras dropping frames, FireWire drives not mounting, and erratic behavior from the iPod (disappearing from iTunes, etc.). In the midst of these issues, you might also experience "buffer underrun" errors when trying to burn CDs or DVDs with FireWire-connected recorders.
The iSight is especially notorious for causing issues of this nature, and exhibiting symptoms.
There exist a number of methods for dealing with FireWire device interference, a few of which are explored here.
Switching Ports The first procedure you should try when experiencing a problem that you believe to be caused by device interference is to simply reconfigure the arrangement in which your FireWire peripherals are connected.
Try switching each device to a different port, or temporarily disconnecting one or more of the devices. In particular, if you are a PowerMac G5 owner, trying switching devices from the front to back ports or vice versa.
Adding an external hub In some cases, it appears that FireWire devices are not drawing enough power from the computer. This can cause a sundry of strange issues, including apparent conflicts between devices and unexpected power-offs during device operation. In these instances, adding an externally powered FireWire hub can clear things up.
One of the reasons an "under-powered" situation can occur is that different Mac models have varying power capacities available through their FireWire ports.
PowerBooks and iBooks have the least, generating around 7 watts. The iMac G5 also generates a relatively low amount of FireWire power, sharing 8 watts between its two FireWire 400 ports.
The Power Mac G5 shares 15 watts between its one FireWire 800 port and two FireWire 400 ports.
Place devices on different FireWire busses/Isolate the iSight Similar to the above procedure, adding another FireWire bridge -- via an extra PCI-based FireWire adapter or another means -- can eliminate conflicts from devices that reside on the same bridge.
Power cycling the system Simply cycling the power on your system may be enough to temporarily eliminate a few FireWire conflict issues.
Shut down your Mac, and disconnect all FireWire devices as well as the computer's power cord. Leave the system off for about 10 minutes, then plug it back in. First turn your Mac back on, then re-attach the FireWire devices one at a time and check for the conflict to resurface.
Disconnect the iSight As noted above, the most common cause of interference is Apple's own iSight. In case after case, simply disconnecting this single device has eliminated problems with other FireWire devices.
Disconnecting the iSight has proved particularly successful for an issue where the iPod disappears from the Desktop and from the iTunes playlist, while the iPod status screen cycles from the Apple logo to a "Do not Disconnect" message over and over.
The exact reasons why the iSight causes more than its fair share conflicts with other FireWire devices are many, and sometimes unclear. One potential source of conflict, however, could be the unit's high bandwidth usage.
The iSight captures video at a 640 x 480 pixel resolution, at 30 frames per second in millions of colors. Such throughput uses a significant chunk of the standard FireWire port's 400 Mbps bandwidth. As such, when other devices are connected, the bandwidth requirements for satisfactory performance may not be met.
Apply the latest updates Make sure that your FireWire drives are using the latest firmware (check the manufacturers' Web site) and the most recent iPod update has also been applied.
Of higher importance, if you have an iSight, is the iSight 1.0.2 updater. In a large number of cases it has resolved conflicts caused by the camera.
Re-apply the most recent Mac OS X combo updater In some cases, re-applying the most recent combo updater can resurrect seemingly defunct FireWire ports and allow devices -- drives included -- to be recognized again.
The most recent combo updater is available from Apple's download page.
Clear caches Try using a tool like Tiger Cache Cleaner or Cocktail to remove potentially corrupt system caches. Restart, then check if your FireWire devices are recognized.
Ps. There was no iSight connected when testing the RME on another Quad!
Power Mac G5 Quad 2.5 GHz Mac OS X (10.4.4) 2x 2.5 GB HD, 2.5 GB RAM, iSight, iPod, RME Fireface 800 Audio Interface

TA

ISight Firewire Hard Drive issues? Anyone?

Hey there, I just picked up a refurbished 1.83 Core 2 Dou Mac Mini, and I've got a weird issue going on.
The single Firewire port is giving me some greif - I've got a MyBook 500 gig FireWire drive plugged into the port. I've also got an iSight (and a bunch of other FireWire devices) but I seem to have issues chaining them.
When I plug the iSight into the second FireWire port of the drive, it isn't happy. I get a really distored picture, interlaced fields, and it runs at about 1 frame every 3 seconds. Then it crashes iChat, or the screen previewing the iSight image goes gray and tells me the "camera is being used by another application".
When I plug the iSight in directly, it works great.
I read some of the other posts and it sounded like it might be a power issue, so I bought a Belkin powered 6 port FireWire hub (I've got a 3G iPod I also need to plug in, and a external dual layer burner, and my FireWire camera, so I needed one anyhow).
Still having the problem! When the iSight is on the same chain as another device, it freaks out. If it's the only device in port, everything is fine.
Anyone else having or had this problem?
Thanks!

Hi RocketChicken-
Greetings and welcome to the Apple boards.
iSight cameras are notorious for being picky about what else is connected to the FW bus. Does it cause problems just being plugged in or only when it is on?
You may find more help in the iSight forum: Forum : iSight
Luck-
-DaddyPaycheck

Can someone help my with my firewire issues?

After searching on the web for a while I've discovered that leopard and firewire are having issues working with each other.
I own a Macbook Pro 10.5.6
I'm having issues running my mac when I have more than 1 firewire device connected to it. I do a lot of video editing and capture all my video footage with Final Cut Pro via FW400. I have a GRaid 1Tb external HDD that is connected via FW800. Never had problems with any of this before but upgraded to Leopard last week and then this issue hit.
•If I have my HDD connected but not my camera, the HDD works fine. However my MAC won't recognize my camera if I hook it up.
•If I have my camera connected but not my HDD the camera will connect just fine. However when I try to hook up my HDD it will not be recognized by my mac.
•If I have neither of them connected and connect them both, my MBPro will recognize whichever device gets hooked up first but will not recognize the second. If I leave them both connected any try to shut down my MAC- it will not shut down. As soon as I disconnect 1 of them, my MAC will shut down just fine.
•If I hook up both devices before my MAC is turned on and then try to boot it up. I will get to the blue screen and it will boot no further. If 1 of the devices is then turned off, the MAC will continue to boot just fine.
I've tried resetting the PRAM by doing the <option> <command> <r> but it had no effect. Not sure I'm doing it propperly. I hold down <option> <command>
<r> and wait until I hear 3 chimes. Anyway, it hasn't fixed anything.
Also, I read something about resetting some of the firmware by holding down <option> <command> <o> <f> after the start up chimes and then typing in
reset-nvram
set-defaults
reset-all
However, whenever I try to do this- I hold down <option> <command> <o> <f> but nothing happens. I never get to any kind of command prompt.
Anyone have any other ideas? Any help is greatly appreciated!!
Thanks!

Thank you all for your replies. I'm trying them all but nothing is working.
I do have a couple of new pieces of information. I figured out that the reason nothing was showing in my System Profiler was because I had both the HDD and the Camera connected if I disconnected one or the other, the remaining device will show in my firewire tree.
Here is a listing of some things. Maybe this will help you all.
Again, thank you for all your suggestions!
//If I only attach my camera (FireWire400) and not my external HDD (firewire 800) I get this in my firewire tree//
FireWireBus
ZR60
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
//Which is weird to me because it's only a FW400 port and cable//
ZR60:
Manufacturer: Canon
Model: 0x0
GUID: 0x850000ACED38
Maximum Speed: Up to 100 Mb/sec
Connection Speed: Up to 100 Mb/sec
Sub-units:
ZR60 Unit:
Unit Software Version: 0x10001
Unit Spec ID: 0xA02D
ZR60:
Manufacturer: Canon
Model: 0x0
GUID: 0x850000ACED38
Maximum Speed: Up to 100 Mb/sec
Connection Speed: Up to 100 Mb/sec
Sub-units:
ZR60 Unit:
Unit Software Version: 0x10001
Unit Spec ID: 0xA02D
(If I only attach my external HDD FW800 and do not attach my camera I get this in my firewire tree)
FireWire Bus
G-Raid Device 00
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
G-RAID Device 00:
Manufacturer: G-TECH
Model: 0x0
GUID: 0x1D27CE0010ABB
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 800 Mb/sec
Sub-units:
G-RAID Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x9102
Product Revision Level: GM4O
Sub-units:
G-RAID Device 00 SBP-LUN:
Capacity: 931.52 GB
Removable Media: Yes
BSD Name: disk1
Mac OS 9 Drivers: No
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
Volumes:
GRaid2:
Capacity: 931.4 GB
Available: 663.31 GB
Writable: Yes
File System: HFS+
BSD Name: disk1s3
Mount Point: /Volumes/GRaid2
(I thought I would attach this information as well maybe it will be useful, I don't really know what to look for here so I though I would just send as much info as possible.)
Battery Information:
Model Information:
Serial Number: Sony-ASMB012-377b-7650
Manufacturer: Sony
Device name: ASMB012
Pack Lot Code: 0001
PCB Lot Code: 0000
Firmware Version: 0110
Hardware Revision: 0500
Cell Revision: 0303
Charge Information:
Charge remaining (mAh): 4693
Fully charged: Yes
Charging: No
Full charge capacity (mAh): 4772
Health Information:
Cycle count: 132
Condition: Good
Battery Installed: Yes
Amperage (mA): 0
Voltage (mV): 12461
System Power Settings:
AC Power:
System Sleep Timer (Minutes): 0
Disk Sleep Timer (Minutes): 0
Display Sleep Timer (Minutes): 0
Automatic Restart On Power Loss: No
Wake On AC Change: No
Wake On Clamshell Open: Yes
Wake On LAN: Yes
Display Sleep Uses Dim: No
Battery Power:
System Sleep Timer (Minutes): 180
Disk Sleep Timer (Minutes): 180
Display Sleep Timer (Minutes): 180
Wake On AC Change: No
Wake On Clamshell Open: Yes
Display Sleep Uses Dim: Yes
Reduce Brightness: No
Hardware Configuration:
UPS Installed: No
AC Charger Information:
Connected: Yes
Charging: No
USB Bus
apple internal keyboard / trackpad
USB Bus
Bluetooth USB Host Controller
USB Bus
IR Receiver
USB BUS
USB High Speed Bus
Built-in-iSight
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x27c8
PCI Revision ID: 0x0002
PCI Vendor ID: 0x8086
Bus Number: 0x1d
Apple Internal Keyboard / Trackpad:
Product ID: 0x021a
Vendor ID: 0x05ac (Apple Inc.)
Version: 0.18
Speed: Up to 12 Mb/sec
Manufacturer: Apple Computer
Location ID: 0x1d200000
Current Available (mA): 500
Current Required (mA): 40
Apple Internal Keyboard / Trackpad:
Product ID: 0x021a
Vendor ID: 0x05ac (Apple Inc.)
Version: 0.18
Speed: Up to 12 Mb/sec
Manufacturer: Apple Computer
Location ID: 0x1d200000
Current Available (mA): 500
Current Required (mA): 40
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x27cb
PCI Revision ID: 0x0002
PCI Vendor ID: 0x8086
Bus Number: 0x7d
Bluetooth USB Host Controller:
Product ID: 0x8205
Vendor ID: 0x05ac (Apple Inc.)
Version: 19.65
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x7d100000
Current Available (mA): 500
Current Required (mA): 0
Bluetooth USB Host Controller:
Product ID: 0x8205
Vendor ID: 0x05ac (Apple Inc.)
Version: 19.65
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x7d100000
Current Available (mA): 500
Current Required (mA): 0
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x27ca
PCI Revision ID: 0x0002
PCI Vendor ID: 0x8086
Bus Number: 0x5d
IR Receiver:
Product ID: 0x8240
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.10
Speed: Up to 12 Mb/sec
Manufacturer: Apple Computer, Inc.
Location ID: 0x5d200000
Current Available (mA): 500
Current Required (mA): 100
IR Receiver:
Product ID: 0x8240
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.10
Speed: Up to 12 Mb/sec
Manufacturer: Apple Computer, Inc.
Location ID: 0x5d200000
Current Available (mA): 500
Current Required (mA): 100
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x27c9
PCI Revision ID: 0x0002
PCI Vendor ID: 0x8086
Bus Number: 0x3d
USB High-Speed Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x27cc
PCI Revision ID: 0x0002
PCI Vendor ID: 0x8086
Bus Number: 0xfd
Built-in iSight:
Product ID: 0x8501
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.84
Speed: Up to 480 Mb/sec
Manufacturer: Micron
Location ID: 0xfd400000
Current Available (mA): 500
Current Required (mA): 100
Built-in iSight:
Product ID: 0x8501
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.84
Speed: Up to 480 Mb/sec
Manufacturer: Micron
Location ID: 0xfd400000
Current Available (mA): 500
Current Required (mA): 100
//As a final note I opened up my system profiler and tired to fine any FireWire info. I narrowed the listings by using the search filter for fire*. Here's what it returned.//
12/22/08 12:43:43 PM SystemStarter[16] /Library/StartupItems/M-Audio FireWire Audio Helper
12/22/08 12:46:24 PM kernel Loading security extension com.apple.nke.applicationfirewall
12/22/08 12:46:28 PM kernel FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe9a6930; max speed s800.
12/22/08 12:52:36 PM kernel FireWire (OHCI) TI ID 8025 built-in: 1039 bus resets in last 3 minute.
12/22/08 9:34:42 PM kernel FireWire (OHCI) TI ID 8025 built-in: 150 bus resets in last 3 minute.
12/23/08 9:02:52 AM SystemStarter[15] /Library/StartupItems/M-Audio FireWire Audio Helper
12/23/08 9:37:37 AM kernel Loading security extension com.apple.nke.applicationfirewall
12/23/08 9:37:37 AM kernel FireWire (OHCI) TI ID 8025 built-in now active, GUID 0019e3fffe9a6930; max speed s800.
12/23/08 9:41:41 AM kernel FireWire (OHCI) TI ID 8025 built-in: 466 bus resets in last 3 minute.
12/23/08 9:44:53 AM kernel FireWire (OHCI) TI ID 8025 built-in: 2538 bus resets in last 3 minute.

Isight firewire issue

Similar Messages

Maybe you are looking for