Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Uh... reread the date. I posted 3 days AFTER the release date. It is now 5 days after.

I'll use big letters: Again, IT'S BEEN VERIFIED OVER AND OVER AND OVER AND OVER AND OVER AND OVER AND...

FireWire no longer works over macOS Tahoe. Apple said it wouldn't and they are right!!!!


Many of us have tried to engineer a workaround. No one has been successful.


So, how many more ways are you going to ask this?
time to look away and take a deep breath.
 
I kind of figured this day would eventually come, especially since Apple pretty much replaced FireWire with Thunderbolt by 2012, complete with Thunderbolt now being able to support Target Disk Mode (rather than limit it to FireWire), not to mention virtually all digital audio and video devices no longer using it (when it comes to video, in addition to tape-based DV having also become obsolete in the early 2010s, some higher-end hard drive or flash memory camcorders would even include a built-in Thunderbolt port in addition to some form of USB for an even faster file transfer!). Additionally, Adobe Premiere Pro and Elements dropped support for FireWire-based DV capture for a few years now.
Besides, I almost never used FireWire with my M1 MacBook Air anyway except for digitizing some analog videotapes via my Sony Digital8 camcorder, especially since most of my videos are shot either on my Canon VIXIA HF-R600 camcorder (records onto SD card) or my iPhone 14, and importing the video from them into iMovie or Final Cut Pro or Premiere Pro or whatever is a lot easier (especially when using an SD card reader with footage from the Canon camcorder), compared to the real-time shuttling and capture of MiniDV/HDV and Digital8 cassettes. But sometimes I do use some of those camcorders for throwback-style videos, and if I do, I would generally import and edit them on an older FireWire-enabled Mac anyways as part of the throwback.
F6A4DAF1-A562-4471-B10D-EA2E188845EB_1_105_c.jpeg


Heck, I even did so in a recent vlog talking about the 30th anniversary of MiniDV...
Complete with being shot on the MiniDV format, but for even more of a fun throwback I edited it on the Windows XP version of Adobe Premiere 6.5, on my early 2008 15" MacBook Pro's Windows XP Boot Camp partition!
So yeah, I'm all covered when it comes to legacy FireWire devices. But if I want to digitize any analog footage into my M1 MacBook Air (like a YTP sourced from one of my VHS tapes), I may then look into getting a decent USB-based analog-to-video capture device for the Mac, such as Elgato's.
 
I kept my MOTU 828mkII FW audio interface around long past the time I pulled it out of my rack. It made a great test unit and I was able to help a number of people with installation issues etc.

Once I verified that FW was gone for good in Tahoe, I sold it on eBay with the clear caveat that Sequoia was the end of the line for that beast and the various issues facing Windows users (best with Texas Instruments FW card etc.). It sold faster than I expected for more than my opening price.
 
I kept my MOTU 828mkII FW audio interface around long past the time I pulled it out of my rack. It made a great test unit and I was able to help a number of people with installation issues etc.

Once I verified that FW was gone for good in Tahoe, I sold it on eBay with the clear caveat that Sequoia was the end of the line for that beast and the various issues facing Windows users (best with Texas Instruments FW card etc.). It sold faster than I expected for more than my opening price.
not surprised. for someone looking for a working replacement unit on an offline system used only for production workflow, they would pay anything versus lose time and go through discovery of new hardware and a revised workflow.
 
A little update: I have discovered a good way to enjoy Tahoe while retaining Sequoia for my Firewire needs.

I installed Sequoia onto an NVME drive utilizing a TB4 enclosure, and installed Tahoe onto my internal drive.

Whenever I need to utilize Firewire I will boot from the external drive. Everything else will be done on my internal disk.

I have a time machine backup of my Sequoia install cloned onto multiple external drives and my NAS so I don’t lose it.
 
  • Like
Reactions: toke lahti
A little update: I have discovered a good way to enjoy Tahoe while retaining Sequoia for my Firewire needs.

I installed Sequoia onto an NVME drive utilizing a TB4 enclosure, and installed Tahoe onto my internal drive.

Whenever I need to utilize Firewire I will boot from the external drive. Everything else will be done on my internal disk.

I have a time machine backup of my Sequoia install cloned onto multiple external drives and my NAS so I don’t lose it.
That's one way to do it. I'm reminded of back in 2020-21 when I set up an external 1 TB hard drive with Mac OS 10.11 El Capitan to use with my 2012 quad-core i7 Mac Mini for if I needed to use any older 32-bit applications while the main drive in said Mini had Mac OS 10.15 Catalina. But now I have a collection of older Macs spanning the 2000s and 2010s, and most of them have FireWire. I do not use any FireWire audio interfaces or regularly use FireWire external hard drives; I just sometimes use FireWire-enabled camcorders (two Canon HDV models and a Sony Digital8) for throwback purposes, including importing and editing the footage on one of the older Macs.
FF21E725-DDCE-46ED-804E-EB06AE502E2C_1_105_c.jpeg

The point is, when I do this, it's just FUN.
 
That's one way to do it. I'm reminded of back in 2020-21 when I set up an external 1 TB hard drive with Mac OS 10.11 El Capitan to use with my 2012 quad-core i7 Mac Mini for if I needed to use any older 32-bit applications while the main drive in said Mini had Mac OS 10.15 Catalina. But now I have a collection of older Macs spanning the 2000s and 2010s, and most of them have FireWire. I do not use any FireWire audio interfaces or regularly use FireWire external hard drives; I just sometimes use FireWire-enabled camcorders (two Canon HDV models and a Sony Digital8) for throwback purposes, including importing and editing the footage on one of the older Macs.
View attachment 2561483
The point is, when I do this, it's just FUN.
Yeah, that looks like a sweet getup! I use FireWire for Target Disk mode to easily load stuff onto my G4 Emac. I don’t have any other vintage devices but I plan on procuring more.
 
  • Like
Reactions: dandeco
I have a time machine backup of my Sequoia install cloned onto multiple external drives and my NAS so I don’t lose it.
That's about the only way you can do it. Because you have Tahoe on the System drive, you will not be able to reinstall Sequoia from Time Machine — only the Data Volume.

Apple no longer allows external drives to have a Recovery partition, They made that change with Ventura.
 
Get your facts right:"Over and over again", but before launch.

Then once after the launch, by you and not stating that you have tried with official version.

So, thankyouverymuch (with Kaufman's voice).
Reread the thread. Please pay attention to the actual dates and times of the posts and you will see that you are incorrect. Everyone else can read them.
 
That's about the only way you can do it. Because you have Tahoe on the System drive, you will not be able to reinstall Sequoia from Time Machine — only the Data Volume.

Apple no longer allows external drives to have a Recovery partition, They made that change with Ventura.
Drats, good to know. I will keep that in mind, thanks!
 
That's about the only way you can do it. Because you have Tahoe on the System drive, you will not be able to reinstall Sequoia from Time Machine — only the Data Volume.

Apple no longer allows external drives to have a Recovery partition, They made that change with Ventura.
I have used my mini2018 with externally booted Ventura for 30 months now.
It has always had a recovery partition.

But now, I'm thinking if there are cases when it does not work, since it is on a "synthesized" disk?
Code:
/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                 Apple_APFS Container disk5         1000.0 GB  disk4s2

/dev/disk5 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1000.0 GB  disk5
                                 Physical Store disk4s2
   1:                APFS Volume macOS 12 - Data         750.9 GB   disk5s1
   2:                APFS Volume Preboot                 2.2 GB     disk5s2
   3:                APFS Volume Recovery                1.2 GB     disk5s3
   4:                APFS Volume VM                      17.2 GB    disk5s4
   5:                APFS Volume macOS 12                9.4 GB     disk5s5
   6:              APFS Snapshot com.apple.os.update-... 9.4 GB     disk5s5s1


My next plan is to "glue" internal ssd and newer nVME tb3-drive to a Fusion Drive and install Sequia to that.
 
Last edited:
Reread the thread. Please pay attention to the actual dates and times of the posts and you will see that you are incorrect. Everyone else can read them.
I asked about official release in "911", 11st of Sep.
It was released 15th of Sep.

How could anybody had answered my question before the official version was released?

Do you understand what I mean by "official release"?
That is the release version that is released in that day that official release is released.
And you can't be sure what build version that is before it's out?

Maybe you think I asked that later or again?
I didn't.
 
I
How could anybody had answered my question before the official version was released?
For crying out loud, I answered it on September 16 and you complained that I hadn't on the 20th.

I know that reading, calendars and dates are not your strong suit but will you please let this drop?

Screenshot 2025-10-01 at 11.24.56 AM.png
 

Attachments

  • Screenshot 2025-10-01 at 11.24.56 AM.png
    Screenshot 2025-10-01 at 11.24.56 AM.png
    77.4 KB · Views: 12
I

For crying out loud, I answered it on September 16 and you complained that I hadn't on the 20th.

I know that reading, calendars and dates are not your strong suit but will you please let this drop?

View attachment 2562256

Okay, now I get it.

I thought at 20th that you complained me asking it on 11th.
Because you quoted that.

But what you tried to tell me, that my question was answered 15th and by you 16th.

Just a misunderstanding.
Thank you for your insults.
Peace, out.
 
Last edited:
  • Like
Reactions: mikehalloran
While I agree with you on principle, it’s also very true that legacy drivers still take up system resources and time.
The “Snow Leopard” update people wax poetic about in every other comment section, the one that was famous for shrinking the storage size of Mac OS X… was pretty much only possible because Apple spent that entire update cycle dumping old legacy drivers and bundles from the power PC and classic Mac OS 9 days.

You can’t really have it both ways.
If you just keep supporting every legacy device, you end up with a mess like Windows, where compatibility is great, but actually using the operating system you’ll quickly run into bits that feel like they’ve barely been touched since Windows 95.
Meanwhile macOS is basically the opposite, and within the next two years, them leaving both Intel and Rosetta in the past is both going to be very sad and annoying for consumers, but also very great for the operating system.
The fw kext is a few ko, it basically hasn't been updated in years. This is purely another dick move by apple.
 
  • Like
Reactions: toke lahti
I wonder how many people this will really affect as anyone who's been around Macs long enough and still regularly uses Firewire devices likely has an old Mac more than capable of doing what they need with that device (or is using odd workarounds with the Firewire device more as a satisfying challenge than out of necessity).
Me, it will affect me, and it's not a 'challenge' to use a perfectly fine motu interface, I use it with a modern M1 computer and it works perfectly fine with adapters.
I hate this, and apple is really the worst offender compared to windows when it comes to planned obsolescence. Still I will now try to stay on Sonoma then Sequoia for as long as possible (out of spite if anything lol, watch me use a firewire interface for my gigs in 2030. And I'm serious).
 
Nobody is FORCING you to upgrade to the latest version of MacOS, nor should upgrading be done blindly and without due diligence. With each new version take an objective look at what features you get and what you lose and decide if upgrading will fit your workflow. If connecting to a FireWire device is essential to your business then don't upgrade. Or keep a different Mac around just to keep it connected. Or find a replacement device that connects via a supported interface. It's not the end of the world, there's always a reasonable solution.
Try keeping the same system for a few years and see what happens. Granted it can go on a while but at some point you won't be able to update your software (avoid anything apple as they are the first to drop), or install anything new. Then your browser will stop updating (firefox keeps support for a long time but it runs out at some point). Then the internet is unusable. And I haven't even mentionned the security risks. So yeah at some point you are forced to upgrade somehow. I think five years is about the limit you can go on. In the end my interface is still gonna be a brick for no good reason and I'll be down the price of a laptop to replace it.
 
It's a little bit different, you're comparing two different things. One is the physical connection, the other is a media type. You can have a floppy that connects through USB, still a fully supported physical connection. Same with a ZIP disk.

If they remove the support for physical FireWire connections, that doesn't change anything for anyone using adapters to connect their FireWire devices to a Mac. And since no Mac has had a physical FireWire port in almost 15 years, that would be pretty much everyone.

Think about it... No Mac with a FireWire port comes even close to running Tahoe. So if you are using a new Mac, and you're using an adapter, by the time Tahoe "sees" the device, it is seeing a USB or Thunderbolt device because of the adapter, it isn't seeing a FireWire device.

And if you've hung onto an old Mac to use a FireWire device, well, you won't be installing Tahoe on that ancient computer ANYway.

So everyone going crazy about Apple removing FireWire support for no reason really needs to just calm down. Find a cause more worthwhile for your outrage.
That's not how it works, even with an adapter, which is seen by the mac as a pcie card through thunderbolt btw, the firewire connexion won't work without system support for it. That's like if you plugged a pcie card in a tower and the card doesn't work because **** you. FW support is basically a few ko .kext in the system.
 
Well, there’s one reason why I will continue to use Windows PCs. I was able to install a FireWire card in a $4000+ build and it works. Now FireWire devices won’t work on Mac no matter how many dollars you throw at their system (and their professional PCs can cost well above this amount multiple times over)

I really don’t think they were rewriting the FireWire code with every OS update. Maintaining and periodically testing its functionality is one thing (more than Apple does for some of their other software; see “Apple Devices”) but this seems like the deliberate removal of a protocol they really didn’t have to touch.
The kext that make firewire work had litteraly one update in ten years, it's been the same. It cost them nothing to maintain.
 
All the older FW 400 & 800 devices, scanners, digital tape, audio interfaces have always been able to connect to the latest Thunderbolt ports via two Apple adapters. Why remove the drivers when the adapters allow connecting to the latest port?
Now I can see why Apple discontinued the Thunderbolt 2 to FireWire 800 Adapter A1463. Prices starting to rise on eBay.
My god mine is randomly not recognized, and now I have to pay 100 euros to replace it?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.