Harddisk & Airport conection USB/Firewire - problem with connetion

So I bought the Airport Express and wanted to connect my Lacie Firewire HD with it. But since it is a FireWire - I guess I need a converter to go from firewire to USB2.
Is that possible? ..and where can I get a converter?

There is no such thing as a USB to FireWire converter. You will need a hard drive with a USB connection.

Similar Messages

FireWire (and USB?) problems with 23" Cinema display

Hello.
Whenever my G5 wakes from sleep, I seem to have problems with FireWire devices attached to the Cinema Display (and, possibly, the USB ports also). Somehow, it seems that the "wake" signal is not transmitted to them.
Specifically:
a FireWire hard drive does not spin up (a USB drive connected to the back port does, as does a FW 800 drive also connected to my PowerMac). When I try to access it, then it finally spins up.
An EyeTV 200 device fails to connect (i.e., display TV or record shows) unless the Fi cable is unplugged and reattached.
This happens WHENEVER the Mac sleeps. However, if I attach those two devices directly to my PowerMac, they function just fine, using the same port the Cinema Display is attached to.
I don't have other comparable devices attached to the USB port of the Cinema Display, except (previously) for a Plextor ConvertX DVR (a USB 2 device), which exhibted the same problems as the EyeTV 200, which is why I tried swapping it with the FireWire-based EyeTV (unsuccessfully). So I have some evidence that the USB port has similar problems, but nothing conclusive.

Hey Scott
You are not alone. I'm beginning to think there is an issue with the power supplies of the 23" displays.
In my case, my computer is set to never sleep, while the display is set to sleep atfter 30 mins or so.
It appears that the computer won't wake up in these cases, but in fact what is happening is that the display won't wake up.
Multiple re-starts are sometimes necessary to get the display up and running again.
While your problem seems slightly different, I think that the two are related in that there is not enough power being delivered from the power supply for the monitor to both your USB and Firewire devices connected to your display.
I don't really have a solution as of yet.... aside from purchasing a new power supply from Apple... But, you are not exactly alone in your misery. Should I run across a fix for this aside from the power supply, I'll be glad to let you know.
Generally after HD's spin down, they usually don't spin up unless they are accessed. If you have any open files on your FW800, that may explain why it does spin up when you wake up your system.
One thing you can try, in the System Prefs, under Energy Saver, uncheck "Put HD's to sleep". This may cause all of them to spin up when you wake your system up.

Airport Time Capsule 2TB - Problem with Backups

Hello everybody,
I´m from Germany but I hope you understand my english. I have got a problem with my new Airport Time Capsule 2TB. I want to use it as a data storage, where all my pictures and videos are accessible via WIFI.
Copying the datas was no problem but now I want to make a backup of all the datas. For this purpose i created a RAID 0 out of two 1TB external hard drives. I connected the bay with these two hard drives in it with the Time Capsules USB interface. The problem is that no drives were displayed in the airport-programm ... Also non of my other USB hard drives were found. Only the Time Capsule´s partition "data" got found...
In the time machine program I can´t see the Time Capsule, so I can´t do a backup on the normal way... Even the "hard drive - program" from OS X didn´t show the Time Capsule.
It looks like they don´t want to know anything about each other ...
So, how can I realize to do a backup of the datas saved on my Time Capsule?
Thank you for your answers and sorry if my english is bad in some cases.

Ok.. can understand..
You have two problems.. maybe 3.
1. Time Machine (TM) does not work on network drives which includes Time Capsule.. so you simply cannot backup your pictures from a TC to a backup location using TM. It only works on locally connected drives.. you can use an alternative software like Carbon Copy Cloner .. I did check superduper but in the past it was not able to backup network source drives. You will need to check if the situation has improved.
2. The Time Capsule will not accept raid array disks.. it must be a standard hard disk on a USB drive that it has drivers for.. and that is far from every model out there. So not all plain single USB disk works.. almost no array disks work.
3. Your iphoto library if that is what you mean by pictures should not be on a network drive.. apple says it is going to be corrupted.
YMMV.. it is dangerous and only a matter of time.. if the pictures and videos are raw from camera that is fine.. it is only the iphoto (or aperture) library that is at risk.

Airport Express B/G : problems with manual IP configuration?

I don't know when it started, but I think it has something to do with one of te latest systemupdates or airport firmware updates.
Configuration :
- Airport Express N : only N, bridge mode, IP manual (192.168.1.7), roaming with Extreme N
- Airport Extreme N : only N, bridge mode, IP manual (192.168.1.35), roaming with Express N
- Airport Express B/G (older one) : B/G compatible, bridge mode, IP manual (192.168.1.8), no roaming, just stand alone.
All the airports are wired connected to a 10/100 switch.
No internet configuration on these airports, I'm using a separated router, also connected to the switch.
Problem : The airport Express B/G dissapears from the network : from time to time not visible in the airport utility program, from time to time not visible in iTunes (airtunes). In spite of these problems, he is always visible in the airport network menu. An IP ping works just fine.
When I change the IP configuration of the Airport Extreme B/G from manual to DHCP, there is NO problem anymore.
No problems with the Airport Express N an Airport Extreme N.
Are there other users with the same problem?
Thanks in advance.
Message was edited by: Mario Willen

question: i below what should i do ?
1) put a cable from my cablemodem to the airport extreme bs;
2) put a cable the airport extreme bs to the airport express bs.
Yes on both. Your network configuration would look something like the following:
Modem > (Ethernet) > \[WAN port] AEBSn \[LAN port] > (Ethernet) > AX
do i have to reset the modems and are there any setting i should be aware of ?
Yes, it's always a good idea to both reset both base stations and, after doing so and before configuring them, perform a complete power recycle of your network equipment.
So in this case ...
o Power-down the modem, AEBSn, AX, & computers. (Order is not critical.)
o Reset both the AEBSn & AX. (Again, order is not critical.)
o Power-down each base station after performing a successful reset.
o Power-up the modem; wait at least 15 minutes.
o Power-up the AEBSn; wait at least 10 minutes.
o Plug-in the AX; wait at least 5 minutes.
o Power-up your computer(s).
o Use the AirPort Utility to reconfigure both base stations as required.

[SOLVED!] On USB drives, problems with non-English chars and HAL

Hello,
I am having a problem with non-English caracters (áãàçéẽê...) on files stored on my USB drive.
On Windows they're created with the correct name. But on Linux the files have the non-English characteres replaced by '?' and are not accessible.
If I manuallly mount the drives using 'mount -o iocharset=utf8 /dev/sdb1 /media/usbdisk' the characters are OK, so I think I just need to get HAL to pass the correct parameters to mount. However I don't know how to do that, and haven't found any good solution.
I tried to build a custom kernel setting the default charset as UTF-8 and it didn't work.
Any ideas? I'm using x86-64, HAL 0.5.13-3 and my locale is pt-BR.UTF-8.
Thanks!
EDIT: Actually, this is not a HAL problem, but a problem with 'exo'. For the solution, I edited /etc/xdg/xfce4/mount.rc and added iocharset=utf8 to the [vfat] category.
Last edited by Renan Birck (2009-11-28 20:54:23)

I don't use Thunar presently, but I looked in the Thunar Volume Manager doc and I didn't find anything to change the mount options of removable drives. I am not quite sure if it's possible or not. Maybe someone using it can tell for sure.
But if it is not possible to change the mount options, a possible solution is to disable the Thunar Volume Manager plugin and to use something else more configurable to manage the automount function.
Personally I use the halevt package from AUR which uses configuration files in the xml format.
It's not so easy to use but is highly configurable.
But there exists other tools also.
I can help you with halevt if you choose that way...

10.4.7 update and external firewire problems with HD corrupion

Dear all,
Advised by Jpfresno I started this new topic about Tiger 10.4.7 update.
I will repeat my post and what was happening 2 weeks ago:
“In 5 years 10.4.7 update was a tragedy for my Powerbook Ti 667. When I update from 10.4.6 to 10.4.7 my 300 GB firewire drive gets corrupted, after repairing it with DiskWarrior and after connecting it to my PowerBook my computer freezes and I must shut it down via powerbutton. Safari also crashes after the update.
I just erase my Hard Drive and after that install 10.4 and update with combo to 10.4.7. But I had the same problems: finder freezes with connected firewire devices and also safari when browsing. I spend a week trying to solve the problem but no luck.
Yesterday and with no firewire devices, 10.4.7 freeze and I have big trouble in order to started my powerbook!!! Even when i insert the 10.4 install DVD it did not detected my HD. Finally I get it to work and install 10.4 and combo update to 10.4.6 and everything works. My external firewire drive and safari. I already diagnose my HD with disk utility, TechTool and directories with Diskwarrior and everything is ok.
I clone my 10.4.6 to firewire, boot from it and everything is working. I let my external drive connected and finder does not freeze.
My conclusion is that the problem is 10.4.7 update. It only give me problems and I was getting crazy with it. 10.4.6 is working good and I do not advice anyone to update to 10.4.7.”
Last week after reinstalling 10.4.6 I started to have HD problems with my Powerbook 667. I did a surface scan with TechTool I it reported bad sector. Then I done a zero disk format but after a second surface scan TechTool also reported bad sector. Then I take the decision to replace my internal HD. I bought a Samsung 40GB Hard Drive and installed it on my PowerBook. Then I have done a clean installation of 10.4.6 with all applications that I need and clone it to my hard drive with Intego Personal Backup software. Everything works on 10.4.6. and external firewire drive.
After that everything is ok. But I decided to test if my problem derivates from 10.4.7 update or from previous HD corruption. Then I install 10.4.7 update on my Internal Hard Drive. Everything is working good but after connecting my external Hard Drive the finder started to freeze!!!!!!!!!. After that I tried cloning HD to external firewire with Intego personal Backup. Everything was working good but when it was finishing the backup process started to give errors!! I started panic. I interrupted the backup process but after and after restart I found something strange with 10.4.7. The system started up, I login but I could not started any application!!!??? All my application died!
Then I have done one more clean installation of tiger and 10.4.6 update.
My conclusions are that the 10.4.7 update causes all the problems that I have on my PowerBook, because I used the same methods and same software/hardware on 10.4.6 and did no have any problem.
This last two weeks were very difficult to me. I tough that these problems do not happen with Apple computers but I was wrong!!! It is very hard to me to deal with it. I always said to my friends that I never had problems with Apple computers. I accept that a hard drive died because the use of it but I can not accept that a system update cause me 2 weeks of hard problems and make me loose precious work information! I always love apple computers and Apple OS but now I am disappointed
If anyone can explain what happen or have a solution for those problems?
Thanks for the comprehension and collaboration.
Best Regards
Mac OS X (10.4.6)

Hi, alsvieira.
There are some things you did not check in all of your troubleshooting:
1. Run the Apple Hardware Test (AHT) that came the affected computer. See my "Apple Hardware Test" FAQ for comprehensive advice on using the AHT in troubleshooting.
2. re: FireWire troubleshooting: Here is some general troubleshooting advice that may help if problems return with your FireWire drive:1. Review the AppleCare Knowledge Base document "What to do if your computer won't recognize a FireWire device".
2. If this problem occurred after installing a recent Mac OS X Update, and you are also unable to mount CDs, DVDs, or disk images perform the steps in this Mac OS X Hints article. This worked under Panther and may also work in certain situations under Tiger.
3. Power-on the FireWire drive before starting up (booting) your Mac.
4. Reset PRAM and NVRAM.
5. Resett the power-management chip in your Mac.
6. Try a different FireWire port. James Wiebe, CEO of WiebeTech, has published FireWire Port Failures in Host Computers and Peripheral Devices, a white paper providing backgroud information and technical analysis concerning the causes of failure for FireWire ports. This may provide additional diagnostic information.
7. Micromat TechTool Pro version 4 can test the FireWire bus in your computer: this tests the bus — not the ports — but if the problem is on the FireWire bus on the logic board, it should reveal it.
8. Check with the manufacturer of your FireWire drive or enclosure to see if any firware updates are available for such.
9. Hopefully, the partition map on the FireWire drive is not damaged. This can happen if the FireWire drive was not Ejected before being disconnected or powered off. If it still refuses to mount, you may need to employ data recovery tools or services: see my "Data Recovery" FAQ.Note that some of the information above is from the "FireWire Problems" chapter of my book, Troubleshooting Mac® OS X.
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

MM-1 (Bower&Wilkins) USB speakers problems with OS Mavericks

Hi,
I use USB speakers, rather fine ones. MM-1 (Bower&Wilkins)
With Mountain Lion, everything was good. Ever since I switched to Mavericks, I have all sorts of problem with them.
In lin- in mode, everything is ok, but in USB mode:
I loose all audio sometimes when switching apps, or or for example, starting a video when music is playing from Rdio streaming.
A loud «pop» or "click" sound occurs in the left speaker when a video or a sound «initializes». e.g. opening a web page with a video in it.
Changing the audio out back and forth from USB to "internal speaker" sometimes bring sound back, but most of the time, only a restart will do.
Or to make everything explode:
Play music in Rdio, open Safari, launch a YouTube video, toggle multiple times between full screen and normal mode, then BOOM loose All audio until restarting the Mac.
Thank you!

Hi,
I use USB speakers, rather fine ones. MM-1 (Bower&Wilkins)
With Mountain Lion, everything was good. Ever since I switched to Mavericks, I have all sorts of problem with them.
In lin- in mode, everything is ok, but in USB mode:
I loose all audio sometimes when switching apps, or or for example, starting a video when music is playing from Rdio streaming.
A loud «pop» or "click" sound occurs in the left speaker when a video or a sound «initializes». e.g. opening a web page with a video in it.
Changing the audio out back and forth from USB to "internal speaker" sometimes bring sound back, but most of the time, only a restart will do.
Or to make everything explode:
Play music in Rdio, open Safari, launch a YouTube video, toggle multiple times between full screen and normal mode, then BOOM loose All audio until restarting the Mac.
Thank you!

Audio/Firewire Problems with Mini, Please Help!

I just bought a brand new Mini from Amazon.com and am having some problems. First, when I plug computer speakers into the mini, the sound continues to come from the internal speaker and the mini ignores the speakers. In System Preferences, it doesn't even recognize that something is plugged into the machine.
Second, the Mini does not recognize my external, Firewire iSight camera. In System Profiler, it does not show anything connected to the port when the camera is connected.
The Mini is the latest rev running 10.4.11. Leopard upgrade disks should be in the mail soon.
Any ideas as to what is wrong? Should I just return to Amazon for a replacement? Thanks for your help!

Having just posted in a similar situation, pardon the cut and paste, but these are the first two (and easiest) things to try:
First reset parameter RAM - it's an area of non-volatile memory used for system settings and hardware configuration. It it gets corrupted, it can cause odd problems.
Reset PRAM
-Shut down the computer.
-Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in the next step but one.
-Turn on the computer.
-Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
-Hold the keys down until the computer restarts and you hear the startup sound for the second time.
-Release the keys.
Next, perform an SMC reset. The SMC is the device which controls system hardware and devices, so if there is a problem with hardware components not functioning, it could be that.
To reset the SMC on an Intel mini:
-From the Apple menu, choose Shut Down (or if the computer is not responding, hold the power button until it turns off).
-Unplug all cables from the computer, including the power cord and any display cables.
-Wait at least 15 seconds.
-Plug the power cord back in, making sure the power button is not being pressed at the time.
-Then reconnect your keyboard and mouse to the computer.
-Press the power button on the back to start up your computer.

USB audio problems with 2013 iMac

I'm having a strange audio problem with USB microphones and headsets. The issue with my Logitech H650e is shown in this screencast I recorded. In the first part of the screencast, I am not speaking into the mic—yet you can see the levels fluctuating as if there is static playing (not in a natural pattern that you'd see when someone is speaking). In the next part of the video I demonstrate that selecting the built-in iMac mic for input, and then re-selecting the Logitech headset temporarily solves the problem. You can see the input start to fluctuate normally as it should when I am speaking. But at 0:31 in the screencast, you can see the input levels freeze and stop registering anything. I continued to speak until the end of the screencast, but no input was detected. For this screencast, I was on a Go To Webinar call, but the problem occurs regardless of whether I'm using Skype, Go To Webinar, GarageBand or any other software.
The problem with my Blue Yeti USB microphone is also different. In that case, the input does not freeze as it does with the Logitech headset. The levels appear as you would expect, and it seems to work. However, the person on the other end can hear static in the background, even though I don't hear it in my own headphones. I learned this because I just tried to do a Skype interview with the Blue Yeti, and the interviewer told me they could hear static. We closed Skype and called each other back twice, but the problem persisted. Then, suspecting the problem was related to what I described above with the Logitech, I unplugged the Yeti and then plugged it into my Macbook Air 2013 (also running Mavericks). Lo and behold the static completely disappeared.
My Griffin iMic and Audio Technica lavalier mic (attached to the iMic) behaves similarly to the Yeti, except in this case I can hear the static when I speak with my monitoring headphones. The input works but I get a lot of cracking and static in the background. This was confirmed by calling the Skype Test Call number and recording a message, which is then played back.
Here are the facts:
All 3 of my USB audio microphones/headsets do not work with my 2013 iMac running Mavericks
All 3 of these microphones/headsets worked fine with my 2008 Mac Pro running Mountain Lion
All 3 of these microphones/headsets work fine with my 2013 Macbook Air running Mavericks
In this other thread, several people are reporting similar issues with the iMac 2013 and Mavericks. At least two people did not have the issue when the iMac 2013 was running Mountain Lion. This of course suggests the issue is the combination of the iMac 2013 and Mavericks.

Apple>About This Mac>More Info>Service
Please read the warranty paperwork that came w/your computer.
You have 14 days to return the computer w/no questions asked.
You have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.
Strongly suggest that you take FULL advantage of the above before it runs out. Let Apple deal w/the problems.

Firewire problems with audio interface

Hi, I have a problem with the firewire connection of my Power Mac G4: I have a Tascam FW-1884 audio interface and when I turn it on, the firewire led (that should be always turned on for the correct working of the machine) after a pair of seconds turns off and doesn't work at all..
Here's what my system console says if helps..
===== Thu Jan 12 2006 ===== 09:44:12 Europe/Rome =====
Jan 12 09:44:20 localhost kernel: TASCAM FW1884 Audio Device: init (1 of 1)
Jan 12 09:44:20 localhost kernel: TASCAM FW1884 Audio Device: start 1.2.1 (instances 1)
Jan 12 09:44:21 localhost kernel: TASCAM FW1884 Audio Device: message 0xE00087D2 for 0x12060000
Jan 12 09:44:23 localhost kernel: TASCAM FW1884 Audio Device: HandleWatchdogTimer: prefs daemon relaunched
Jan 12 09:44:24 localhost kernel: TASCAM FW1884 Audio Device: newUserClient
Jan 12 09:44:24 localhost kernel: TASCAM User Client: start
Jan 12 09:44:24 localhost kernel: TASCAM User Client: clientMemoryForType
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: High speed bus detected
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FinishStartup: FW884MacXDevice (216812)
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: Driver Register Version 0x00000014
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884REGISTERVERSION 0x00000014
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884FPGAVERSION 0x00010031
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884ARMVERSION 0x000100B7
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884HARDWAREVERSION 0x00030000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884HARDWARESERIAL 0x00000000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884GUIDMSB 0x00022EFF
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884GUIDLSB 0xFE800000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mRegBaseAddress 0x00000000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mNodeNum 0x00000000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mGenerationNumber 0x0000000E
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mlocalNodeNum 0x00000001
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mMIDIReceiveHi 0x00000002
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: FW1884DeviceHandlePlugIn mMIDIReceiveLo 0x00000000
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: initHardware
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: createAudioEngine
Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: init (1)
Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: start (3)
Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: initHardware (3)
Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: performFormatChange
Jan 12 09:44:29 localhost kernel: TASCAM Audio Engine: performFormatChange
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOCHANNEL 0x00000001
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOSPEED 0x00000002
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: New PLAYBACK_ISOCHANNEL 0x00000002
Jan 12 09:44:29 localhost kernel: TASCAM FW1884 Audio Device: DoStartAudioTransfers w/resync
Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: Input stream stopped (B)
Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:30 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000200
Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000200
Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOCHANNEL 0x00000000
Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:31 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000204
Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000204
Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: New RECORD_ISOSPEED 0x00000000
Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:32 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000020C
Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: * Failed ReadRegisterLong 0xE00002D6
Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000020C
Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: New PLAYBACK_ISOCHANNEL 0x00000000
Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:33 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000022C
Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000214
Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:34 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000218
Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: at 0x0000021C
Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: * Failed WriteRegisterLong 0xE00002D6
Jan 12 09:44:35 localhost kernel: TASCAM FW1884 Audio Device: at 0x00000228
I've tried running the same interface on my i-book (with the same drivers installed on the powermac) and all was good..
Anyone can help me?
Thanks =)
power mac G4 quicksilver 800Mhz Mac OS X (10.3.9) i-book G4 1,25Ghz
power mac G4 quicksilver 800Mhz Mac OS X (10.3.9) i-book G4 1,25Ghz
power mac G4 quicksilver 800Mhz Mac OS X (10.3.9) i-book G4 1,25Ghz
power mac G4 quicksilver 800Mhz Mac OS X (10.3.9) i-book G4 1,25Ghz
power mac G4 quicksilver 800Mhz Mac OS X (10.3.9) i-book G4 1,25Ghz

On both computers I have only one account, the fw cable is always the same..
I have purchased a new cable and I'm testing it..
Another thing to say is that the fw port number 2 is generally working better than 1.. I mean, while port 1 never loads my tascam (the computer firewire connection is always loaded succesfully on both ports) port 2 sometimes works.. well this can't be called stability at all =)
Sometimes reastarting computer, unplugging cables etc can help starting succesfully a new session.. I've already resetted PMU but no progress..
All these things don't last longer than one session..

After upgrade to ios 6 usb connection problems with car stereo

Hi Everyone,
after ios upgrade to ios6 i am not further able to use the iPhone 4s as music device - having usb connection problems ("not readable"). I am sure, that the upgrade ist the culprit; worked fine before. My car stereo is built in a Volvo XC 60; the device is connected via the standard usb cable by apple.
Any Ideas?
Thanks
Ivo

(same problem thread): see also https://discussions.apple.com/message/20185146#20185146 (not fixed)

Firewire problems with MP

Hi
My new 2008 MacPro is doing ok for me at the minute the pnly problem I have had is a Firewire 400 problem.
I had a sound cut out and a hardrive not being recognised by the port already. Then today after connecting my Canon HDV to the front 400 port and successfully importing footage the sound dropped out whilst still importing, the footage also freezed on screen at the sametime.
Any thoughts what this could be? Is there known issues using more than one FW at a time on these machines?
Thanks

Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that didn't work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try.
If that still didn't get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple doc.#88338 on getting FireWire to work.
Here's another
Fw Faq.
DALE

USB Cable problem with HP Photosmart 7960 printer

This may sound like a stupid question but I just bought a new 7960 printer to replace my old 7960 which has two out of the three ink cartridge holders broken and the usb port on the new printer won't accept a usb cable. It appears to be blocked by a cap insert over the connector prongs which will not come out. Any suggestions?

Here is a link with some troubleshooting steps that may help to solve the issue you are having with your printer:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02065582&cc=us&dlc=en&lc=en&product=3940574&tmp...
Paper feed problems are a hardware issue, if none of these steps help I would recommend contacting HP for upgrade options. I have included a link with directions for contacting HP:
http://www8.hp.com/us/en/hp-information/summary/ww-contact-us.html
I am an HP employee.
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"

USB 3 problem with OEL 6.3

Hi,
after connecting an external 2.5" HDD (USB 3 ready!!) to one of my USB 3 interfaces I recognized a lot of xhci_hcd warnings. They all look the same.
xhci_hcd 0000:0e:00.0: WARN: Stalled endpoint.
I tried to connect while the OS was running.
According to the output of my lsmod command it seems to be that the xhci_hcd kernel module is loaded but not used. Here is the output:
xhci_hcd 123859 0
In spite of these warnings the HDD seems to work. May be with a reduced speed??
As I am a Linux newbie I don't know how to investigate further or to get rid of this problem.
Could you please give some advice?
Thanks and regards
Volker
P.S. I am using the following kernel: 2.6.39-200.24.1.el6uek.x86_64

Oracle Linux or any other Linux distribution based on the source of RHEL is designed for enterprise server hardware. However, the USB 3 issue you are experiencing is not an issue with Enterprise Linux only and apparently affects other Linux distributions too. The solution for the problem is usually a device firmware and Linux kernel upgrade. You could try to upgrade to OL 6.4 and use the latest Oracle UEK2 kernel or switch to a Debian based desktop distribution, such as Ubuntu, which deploys the latest versions of available Linux software.

USB Drives - Problem with Recovery Manager

I bought a Kingston DataTraveler 112 16GB thumb drive so I could copy the recovery image as a backup. It recognized the thumb drive and showed that the recovery image was a little over 11GB. But when it started to format the USB, it returned to the previous screen and no longer showed the drive there. At the bottom of the screen it said to contact HP Support but it didn't give me an error message. Now when I try the recovery manager it won't recognize the USB at all.
Prior to that I had purchased another 16GB USB--don't remember which brand. I have 5 other USB drives, but they're all smaller, except a 32GB Kingston DT101 G2 which does not work on this computer, although it worked on my previous computer (Pavilion w/Vista Home Premium) with no problem. All these USBs, including the new Kingston are for USB 2.0.
OS is Windows 8.1 64 bit on HP Pavilion 500-A60 desktop. I've tried the problem USB drives in all 4 ports (2.0 and 3.0). Also in the one I plug into a port to give me 3 USB ports, also used on my prior computer.
Is it possible that this computer doesn't recognize Kingston or certain other brands of USB thumb drives?
This question was solved.
View Solution.

The trick to this is to use a USB 2.0 port and to use a non-Windows 8 certified thumbdrive. If the USB flash drive shows as a "removable device" then there should be no issue in using the media to create recovery media
I have had great success with a Transcend USB 3.0 16-GB flash disk.
I own a couple of DataTraveler flash disks and had the same lack of success creating recovery media that you did. I have also had zero success with Sandisk Extreme usb 3.0 flash disks
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Harddisk & Airport conection USB/Firewire - problem with connetion

Similar Messages

Maybe you are looking for