Contribute
Register

No Audio - Firewire (via Thunderbolt) after Sleep - Yosemite

Status
Not open for further replies.
Joined
Jan 6, 2015
Messages
6
Motherboard
GA-Z97X-UD7 TH
CPU
Core i7 4790K
Graphics
MSI GTX 760 (N760 TF 2GD5/OC)
Mac
  1. Mac Pro
Classic Mac
  1. 0
Mobile Phone
  1. 0
I am referring to

  • Yosemite 10.10.1
  • Gigabyte GA-Z97X-UD7 TH
  • MSI GTX 760 (N760 TF 2GD5/OC)
  • i7 Core i7 4790K
  • Memory: Crucial 32 GB
  • HDD: SSD Samsung 500 GB 840 EVO 500 GB
  • Unibeast 5 (downloaded a frew days ago)
  • Multibeast for Yosemite 7 (downloaded a two weeks ago)
  • Audio: RME Fireface 400 (via Adapters: FW400->FW800 ---> FW800->Thunderbolt

Goal

  • New Audioworkstation

Good news is:

  • I got thunderbolt running
  • Fireface 400 running over thunderbolt as intended.
  • Fireface 400 can be switched on and off during runtime audio works.
FYI: System information says:

Firewire
Code:
FireWire Bus:
  Maximum Speed:    Up to 800 Mb/sec
Vendor 0xA35 Device 0x101800:
  Manufacturer:    0xA35
  Model:    0x101800
  GUID:    0xA35010D654122
  Maximum Speed:    Up to 400 Mb/sec
  Connection Speed:    Up to 400 Mb/sec
  Sub-units:
Unknown Unit:
  Unit Software Version:    0x2
  Unit Spec ID:    0xA35
Thunderbolt
Code:
  Thunderbolt:    No drivers are loaded.

Problem
When I wake up from sleep all audio is dead, especially the Fireface 400 but even the internal audio.
Loosing the internal audio after waking up appears to be a common issue. I personally can fix it without reboot by calling
Code:
sudo kextunload /System/Library/Extensions/AppleHDA.kext
sudo kextload /System/Library/Extensions/AppleHDA.kext
.

... but this fix or workaround does not work for my Fireface 400.

Most interestingly: My system information is still listing the same information as show above.
This gives me the impression that FW is not dead.​

Questions
Is there a similar workaround I could apply to tell the system that it should re-initialize the Firewire hardware?
Any other ideas what to do?​

Regards and thx in advance
Christian

For the books:
Code:
MultiBeast Configuration - 2015-01-17 06:54:05
-----------------------------------------------------------------
Quick Start > DSDT Free
Drivers > Audio > Realtek ALCxxx > ALC1150
Drivers > Disk > 3rd Party SATA
Drivers > Disk > Intel Generic AHCI SATA
Drivers > Disk > TRIM Enabler > 10.10.x TRIM Patch
Drivers > Graphics > Intel Graphics Patch for Mixed Configurations
Drivers > Misc > EvOreboot
Drivers > Misc > FakeSMC v6.11.1328
Drivers > Misc > FakeSMC v6.11.1328 Plugins
Drivers > Misc > FakeSMC v6.11.1328 HWMonitor Application
Drivers > Misc > PS/2 Keyboard/Mice and Trackpads
Drivers > Misc > USB 3.0 - Universal
Drivers > Network > Intel > AppleIntelE1000e v3.1.0
Drivers > System > Patched AppleIntelCPUPowerManagement > OS X 10.9.0
Drivers > System > AppleRTC Patch for CMOS Reset
Bootloaders > Chimera v4.0.1
Customize > Boot Options > 1080p Display Mode
Customize > Boot Options > Basic Boot Options
Customize > Boot Options > Hibernate Mode - Desktop
Customize > Boot Options > Kext Dev Mode
Customize > System Definitions > iMac > iMac 14,2
Customize > Themes > tonymacx86 White
 
Same problem after upgrading to
  • Yosemite 10.10.2

Any ideas?

I would appreciate if someone could share his/her experience with firewire+sleep via thunderbolt on Yosemite.

The problem for me is that I neither have any other firewire hardware nor any thunderbolt hardware at all for testing.

By the way: I have just applied the fix described here to speed up booting:
http://www.tonymacx86.com/general-help/128748-fix-slow-boot-thunderbolt-2-0-motherboards.html
The problem is is still present after that, whereas my boot time increased dramatically.
 
Ok my friends.

I got confirmation that the problem I describe does not occur with a MacBook Air from the shelf an a instance of the same audio device.

This indeed gives me a hint that the problem might actually be a problem of my configuration.

It would be glad if you might have the slightest idea what might be causing this.
 
I tried fix it by playing around with some flags without luck.
Any ideas?
 
Status
Not open for further replies.
Back
Top