Third party firmware wrt54gs v7

is there third party firmware available for version 7 of the gs router?

Read the wiki of dd-wrt. I find it contains a lot of useful information around these issues, e.g. how to recover from a bad flash etc...
But generally, once the router is really dead there is nothing you can do...

Similar Messages

Would you mind telling us what that third party firmware...

Would you mind telling us what that third party firmware was?

Start with the wikipedia article on "WRT54G" and check some of the links for firmware projects. Have a closer look at the dd-wrt wiki.

WRT54GX4 router third party firmware

I recently replaced my WRT54GX4 with a Linksys E3000. My rationale was to hopefully extend the signal strength and to have two different networks, with the high speed N network reserved for my Internet ready BlueRay Player in one room and an Internet Ready Vizio TV in the far reaches of my bedroom.
Neither of the Internet ready devices see the N network. The only device that sees the Wireless N network is a Dell Latitude D630 with the Intel Chipset OR, to say this different, none of the Atheros Chipset devices see the Wireless N network.
I've updated the drivers on all of the Atheros devices, and they still only see the G network (yes they're configured for G/N and the router is broadcasting the N netowrk.)
Any suggestions on the Atheros not seeing the N network?
Linksys Tech Support says I can't use the WRT54GX4 as an access point. Are there any third party firmwares that will support the WRT54GX4? Checking the compatibility database on most of these third party firmware sites, it appears that the WRT54GX4 is the "ugly duckling," not supported by any of the third parties.
Suggestion please! Any thank you!

RE: Atheros Driver
I downloaded the drivers directly from the Atheros site.
I have the N network at 40mhz only and the G Network at 20mhz only. The channel for both is set to AUTO.
Any suggestions (and thank you for the assistance.)

Third party firmware

I know this might not be wise, but I though I was ask, so I will know. I know there are firmware out there from other third party developers, and some of them say to uses at your own risk. Is there not a recovery if this something bad should happen?
I tinker with everything

Read the wiki of dd-wrt. I find it contains a lot of useful information around these issues, e.g. how to recover from a bad flash etc...
But generally, once the router is really dead there is nothing you can do...

Can I use firmware from third party on my WRT54G v5 router

Hi,
I can see any third party firmware on web for WRT54G routers. Can I used them on WTR54 v5 router, will it work fine? HAve anyone tried....

there's no guarantee that the third party firmware is effective... somehow, they're good too... but the thing is you will not be qualified for linksys support if ever you will upload a third party firmware on your router. make sure that the third party firmware is capable of fixing your problem if you think that the solution for your problem is only that third party firmware then go ahead.

Third party routers that need no firmware update

What are the best third party WiFi routers with LAN ethernet ports that need no firmware update to work with 10.4.8 and Windows XP?

Actually the extra ethernet ports is paramount.
Otherwise you don't know who is being secure to
whom. You end up having two routers to setup for
configuration of security. Simplicity is
important, since I want to be able to help set it up
for the friend, and forget it.
?? That doesn't make any sense - I think you're missing something fundemental here. The extra ethernet ports are on the LAN side of the secure connection. The firewall in the router isolates the internal, LAN network (wireless + ethernet) from the external WAN (aka the big bad internet). Whether or not you have a switch attached to one of the LAN ports makes no difference, security-wise - you are in control of the devices connected to the LAN side of the router. WEP/WPA/WPA2 security controls who is able to connect to the wireless LAN.
From a security standpoint, there is ABSOLUTELY no difference between buying a router with eight lan ports and buying a router with four lan ports plus plugging in a five-port switch to one of the lan ports. It's exactly the same thing.
What you don't control is the WAN side of things - the internet itself. You certainly wouldn't want to connect the switch to the WAN port on the router, at least not unless you wanted to run, say, a web server that is exposed to the internet itself. This wouldn't be a good idea in any case - there are better ways to set this up as well (either by setting up a DMZ, or by setting up port forwards)
There is absolutely no reason why you would want or need two routers for this setup - this is only an issue for extremely large networks.
The WRT54G has 1 WAN port and four LAN ports. You can have four hardwired devices (computers, printers, switches, etc) on these LAN ports - they are protected from the internet by the firewall in the router. You can also have any number of wireless devices on this same router; these, as well, are on the LAN side of the router, and are therefore protected.
Adding a switch to the LAN side of the router has absolutely no impact on security. No additional routers would be required.

Since latest Thunderbolt Firmware update, most of my third party programs no longer work, is there a way I can fix this?

Since the latest update, most of my third party apps no longer work, none of my photo software, torrent programs, open office, NOTHING!! It is most frustrating - is there a way to 'downgrade' and go back to a previous version of the firmware, or am I just stuck with no apps that work?

They just don't open, and i get an error message like this:
Process:
Google Chrome [27305]
Path:
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:
com.google.Chrome
Version:
27.0.1453.93 (1453.93)
Code Type:
X86 (Native)
Parent Process: launchd [166]
User ID:
501
Date/Time:
2013-05-26 08:08:17.911 +0930
OS Version:
Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report:
28298 sec
Crashes Since Last Report:
13993583
Per-App Crashes Since Last Report:   1
Anonymous UUID:
1681FA19-E0EA-448F-4E99-067A50E38854
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
/usr/lib/libz.1.dylib
Dyld Error Message:
Library not loaded: /usr/lib/libz.1.dylib
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: not a dylib
Binary Images:
0xb000 -
0xbff3 +com.google.Chrome (27.0.1453.93 - 1453.93) <7ABACF68-7D3E-30FA-8B03-9A1C0FFFF4F9> /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
0xf000 - 0x408ffaf +com.google.Chrome.framework (27.0.1453.93 - 1453.93) <C691C1FF-CF8A-3CFA-9F0D-10CDAFA2540F> /Applications/Google Chrome.app/Contents/Versions/27.0.1453.93/Google Chrome Framework.framework/Google Chrome Framework
0x43b8000 - 0x4f74ff7 com.apple.AppKit (6.8 - 1187.37) <6FBB3467-04F9-395F-8EA8-C84347C5BE43> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x5491000 - 0x5491fff com.apple.ApplicationServices (45 - 45) <677C4ACC-9D12-366F-8A87-B898AC806DD9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x549c000 - 0x54c1ff7 com.apple.CoreVideo (1.8 - 99.4) <A26DE896-32E0-3D5E-BA89-02AD23FA96B3> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x54dc000 - 0x55a5ff3 com.apple.Bluetooth (4.1.3 - 4.1.3f3) <7909C26F-90FB-359F-84DD-51583A2DC3DA> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x55f8000 - 0x563affb com.apple.RemoteViewServices (2.0 - 80.6) <AE962502-4539-3893-A2EB-9D384652AEAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x5665000 - 0x587cfff com.apple.CoreData (106.1 - 407.7) <17FD06D6-AD7C-345A-8FA4-1F0FBFF4DAE1> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x592a000 - 0x5ae6ffd libicucore.A.dylib (491.11.2) <59A23F06-16AD-35F8-BA58-D17305232402> /usr/lib/libicucore.A.dylib
0x8fe0a000 - 0x8fe3ce57 dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld
0x902fe000 - 0x90362ff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib
0x90ce3000 - 0x90e5bff5 com.apple.QuartzCore (1.8 - 304.2) <FB737C74-C460-32A3-9107-D2112BAE6EBC> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9120e000 - 0x9132affb com.apple.desktopservices (1.7.3 - 1.7.3) <7157C51D-C695-3C9E-B532-F551E7E55B56> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x9132b000 - 0x91488ffb com.apple.QTKit (7.7.1 - 2599.24) <39CC892D-2874-33FE-BE30-87FE07D875BD> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x9148c000 - 0x91599057 libobjc.A.dylib (532.2) <FA455371-7395-3D58-A89B-D1520612D1BC> /usr/lib/libobjc.A.dylib
0x91d3a000 - 0x91d7cff7 libcups.2.dylib (327.3) <C7A4A315-FA15-354B-8BC9-BE824C4EFF6D> /usr/lib/libcups.2.dylib
0x91df4000 - 0x920b4ff3 com.apple.security (7.0 - 55179.11) <165A3105-9ADF-329B-93FC-3C8EFAEDDD13> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x9302b000 - 0x93213ffb com.apple.CoreFoundation (6.8 - 744.18) <68AFEE40-0078-347E-9DEE-32CFE0062A10> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x93573000 - 0x93573fff com.apple.Accelerate (1.8 - Accelerate 1.8) <4EC0548E-3A3F-310D-A366-47B51D5B6398> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x93a62000 - 0x93a62ffd com.apple.audio.units.AudioUnit (1.8 - 1.8) <D35BA73D-1E56-3A1D-9F9F-971F3BF8C136> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x93f64000 - 0x93fccff7 com.apple.framework.IOKit (2.0.1 - 755.22.5) <F9A70D23-1108-3616-9DE3-6C5730CA7AB2> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x94474000 - 0x944a3ff7 com.apple.securityinterface (6.0 - 55024.4) <7C5E28DC-F8BE-3238-883F-E1646A2AF895> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x94760000 - 0x947c4fff com.apple.datadetectorscore (4.1 - 269.2) <B4D53047-C613-32F8-9E08-0154EA81B487> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x94884000 - 0x948defff com.apple.ImageCaptureCore (5.0.2 - 5.0.2) <BB0D85EE-A85D-3E7B-B04E-720886553258> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCo re
0x949b2000 - 0x949f4ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib
0x949f9000 - 0x949f9fff com.apple.Cocoa (6.7 - 19) <354094F0-F36B-36F9-BF5F-FD60590FBEB9> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x95365000 - 0x95365fff libSystem.B.dylib (169.3) <81C58EAB-0E76-3EAB-BDFD-C5A6FE95536F> /usr/lib/libSystem.B.dylib
0x95366000 - 0x953b4ff3 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <6E858B9F-337A-314E-88B7-24A274ACE568> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x95490000 - 0x9549efff com.apple.opengl (1.8.7 - 1.8.7) <0631EC1D-833B-39D2-A907-A9F7617E5504> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x9549f000 - 0x95588ff7 libxml2.2.dylib (22.3) <015A4FA6-5BB9-3F95-AFB8-B9281E22685B> /usr/lib/libxml2.2.dylib
0x95868000 - 0x95b86ff3 com.apple.Foundation (6.8 - 945.16) <C4D95341-B4FF-30AC-815A-A23C019C57A3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x95e49000 - 0x95fa1ffb com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <0D36953C-9897-3E9B-8C70-847E90B203A2> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x97b16000 - 0x97b74ff7 com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <953DD669-8C6E-387D-AB3F-D8C8965347DF> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x97bc5000 - 0x97e5ffff com.apple.AddressBook.framework (7.1 - 1169) <AF50144A-A327-3367-81B1-95B3D46E56F0> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x99699000 - 0x99a7cfff com.apple.HIToolbox (2.0 - 626.1) <ECC3F04F-C4B7-35BF-B10E-183B749DAB92> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x99c23000 - 0x99c2cfff com.apple.DiskArbitration (2.5.2 - 2.5.2) <89822A83-B450-3363-8E9C-9B80CB4450B1> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x99c2d000 - 0x99c37fff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <B855E8B4-2EE3-3BFF-8547-98A0F084F9AF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x99f02000 - 0x99f1fff7 libresolv.9.dylib (51) <B9742A2A-DF15-3F6E-8FCE-778A58214B3A> /usr/lib/libresolv.9.dylib
0x99f20000 - 0x99f20fff com.apple.Carbon (154 - 155) <604ADD9D-5835-3294-842E-3A4AEBCCB548> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x9a08f000 - 0x9a08ffff com.apple.CoreServices (57 - 57) <956C6C6D-A5DD-314F-9C57-4A61D41F30CE> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.69f4
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9500325ASG, 500.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 3
USB Device: My Passport 071A, 0x1058 (Western Digital Technologies, Inc.), 0x071a, 0xfa130000 / 6
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0245, 0xfa120000 / 4
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

WVC54G setup for third party applications and also firmware query.

I have resurrected someone's old WVC54G and installed it to work initially wirelessly to my netwark and then my Windows 7 64-bit laptop. I did an initial reset, then set up the ip address etc. to the system here, and everything seems to work even though the viewer and recorder software installer gave a Windows error message.
I'd like to be able to look at the camera via the VLC viewer application, and I see from another posting here that this should work. Is there a guide anywhere showing how to do this? Ideally I'd like to understand how to interface the camera so that I can test various third party camera applications.
Also, the Linksys setup software says the firmware version is V5.10, Feb 21, 2005, which seems a much higher number than it should be. Is this right?

Try downloading the viewer and recorder utility from the linksys website under the download section which is pretty user friendly.
To view it in VLC player, you can use the option 'open url' in file menu and type in http://your camera's IP
The latest FW for wvc54g is ver. 2.11. The version you have mentioned might be software version.

Updating firmware (third-party memory)

I've just spent a joyous week resurrecting my life's work, after a hideous Norton-hard-drive-erasing incident. Thanks to maclover and others for their help with that.
I've reinstalled everything and upgraded my OS to 10.4. All fine and dandy, except that my Mac will not now go to sleep when told to do so. The screen will go to sleep, but not the computer. Also, when I leave it for an hour or so, the screen will go to sleep but can't wake it up again.
While running a check for software updates, I was given the option to download a firmware update (5.1.5f). From the blurb, I understand that this should fix the sleeping issue.
Before I install it, I just want to check one thing: the instructions say to remove any third party memory before upgrading the firmware, and re-installing the memory afterwards.
Is this really necessary? I don't want to risk buggering anything up, but I'd prefer not to go messing about with the innards of my Mac if it's not necessary.
Thanks in advance!
Mira
1.8 GHz PowerPC G5 Mac OS X (10.2.x) 1.67 GHz PowerBook G4 Mac OS x (10.4.6)

Hi MiraW-
If Apple has taken the time to include that as an instruction then it is probably a very good idea.
Make sure to discharge any static before you reach in and pull out the stick(s).
Luck-
-DaddyPaycheck

Firmware and third party updates

Hi Everyone,
Currently I am running ARD version 3 on tiger server and I have Tiger and Leopard OS X running on my client machines (G5, Intel Mac).
I was wondering if there is a way to send Apple firmware and third party application updates to all of my Mac clients using ARD.
I have used "softwareupdate -i -a" and this command seems to be only working with Apple software but nothing else.
1. Is there a command that I can send (using ARD) to update firmware on all my Mac clients?
2. Is there a command to update third party software such as Adobe, Roxio etc?

1. No
2. Only by repackaging the updates into an Apple standard package installer and pushing them out via ARD. I suggest you use LanREV's InstallEase (Free) to package up the updated files on your master build system and deploy those packages.

How to install third-party SSD as boot disk in MacPro 5,1

I had so much trouble with this that I thought I'd post a recipe that others could follow.
The first thing you should know is that it's not possible to get a non-Apple SSD recognized in a sled slot of a MacPro 5,1. It just doesn't see them at all, even if (as some suggested) previously partitioned as a GUID partition (which works in a MacBook Pro, but not a MacPro 5,1). This is true even with the most up-to-date EFI firmware. You're going to have to use a PCIe adapter card.
The next thing you should know is that not all PCIe SATA3 SSD adapter cards are bootable on a MacPro 5,1. For instance, even though the Sonnet Tempo SSD is advertised as working for a boot drive in a Mac Pro, it actually works in any Mac Pro *except* the 5,1. In a 5,1 drives on the card do not work as boot drives, either with option boot or if you select it as the startup drive after booting from something else. Also, EFI boot is extended by about a minute -- not the end of the world, but an annoyance. The Tempo card does work well for add-on drives, its very fast. I am pretty sure the Tempo Pro variant of the card also does not work, as the Sonnet support guys told me that they have to use use rEFIt for booting 5,1 MacPros in their lab. I imagine if the Pro worked they would have pointed me at that instead. (Note that rEFIt has been superseded by rEFInd, http://www.rodsbooks.com/refind/. I didn't try using rEFIt or rEFInd because I found a better way, but if you want to dual-boot to Linux those utilities are apparently Da Bomb.)
An Apricorn Velocity x2 Duo card *will* boot, and does not have a long EFI boot delay. That card is a little more expensive than the Tempo SSD (but not the Tempo Pro SSD) but it works properly. It's worth the extra money, especially since it's the only card I could find that explicitly claimed to work as a boot drive on a 5,1 MacPro. And it does.
One caveat: With the Tempo SSD the SSD drives were invisible until repartitioned in GUID format, which also happens if you try to use a third-party SSD inside a Macbook Pro. I found that I could repartition one drive, a Crucial MX500 960GB, using a run-of-the-mill USB SATA2 adapter. Unfortunately this solution did not work with a Samsung Evo 1TB drive, I had to use an external USB3 enclosure. Moreover, the enclosure supported both FireWire and USB3 but FireWire did not work. This FireWire issue might be due to the super-cheap enclosure I was using, so YMMV, but keep in mind that it's possible that you'll need either a USB3 expansion card in the MacPro, or a different Mac, to perform the initial repartition to GUID format.
It's possible that SSDs would be visible on the Velocity card even before repartitioning, I don't know as both of my drives had been repartitioned prior to trying the Velocity. So, it might work ... but you might need to partition externally.
I don't know if pre-partitioning is necessary with the Velocity card, as I only ever tried pre-partitioned drives with it. If you try the Velocity and the drive isn't seen, that's the problem and you'll have to use an external SATA adapter of some sort to repartition before installing on the Velocity card.
After partitioning the drive and installing on the Velocity card, it worked fine. Yosemite installed properly and with reboot it blazed.
Next up, TRIM support. For some reason known only to Apple, the Apple AHCI driver refuses to enable TRIM support for anything other than Apple drives. It's possible that there are or were bugs in some of the early SSDs and Apple is just playing it safe, although I would have preferred to have the option to enable TRIM or not if that's the case. Unfortunately there is no such option, you have to use a substitute AHCI driver.
Unfortunately if you're using Yosemite you cannot use a substitute driver without disabling kext extensions, because Apple will not sign anyone else's driver (at least not at the time of this writing). That's unfortunate, I would prefer to have signed extensions if I could, but realistically speaking you're no worse off in terms of security than you were with Mavericks so it's not the end of the world. With a little luck Apple will either start supporting TRIM on third-party drives or starts signing third-party drivers sometime in the future.
So: Before you can start TRIMming drives, you first need to run this command, or something like it:
sudo nvram boot-args=“kext-dev-mode=1”
I rather like seeing the boot process, rather than just the Apple logo, so I use this:
sudo nvram boot-args=“-v kext-dev-mode=1”
I tried both Trim Enabler (http://www.cindori.org/software/trimenabler/) and Chameleon SSD Optimizer (http://chameleon.alessandroboschini.com/). As of this writing the Chameleon driver is more up-to-date, and comes with some additional utilities that are pretty nice. Take your pick, though, both worked fine in my experiments.
With a TRIM-enabled AHCI driver, kext signing disabled, a Velocity card, and your favorite SSD you are in business.
The only weird thing after all of this is that non-boot SSDs on the Velocity card (or on the Tempo) are ejectable. As far as I can determine there’s no way to mark them as non-ejectable. That’s a minor annoyance compared to the performance you get out of the SSD, though.
Because, with this stuff in there, yowza is the MacPro 5,1 a fast machine. You Will Like It. Enjoy!

Then you should read these.
http://forums.macrumors.com/showthread.php?t=1804704&highlight=sonnet+tempo+pro
http://forums.macrumors.com/showthread.php?t=1721573&highlight=sonnet+tempo+pro
This was strange but has to do with how startup disk and nvram interact
http://forums.macrumors.com/showthread.php?t=1795765
I think your problems were solvable and not that the Sonnet card and 5,1 is not bootable, in fact the 5,1 is easier, there are more supported cards.
I have the 1,1 where the Sonnet Pro is recommended but for data only and are not bootable because of the 32-bit EFI firmware. NOT the 4,1 and 5,1. The 2008's are problem child and have a mix of PCIe 1.1 slots, first implementation of EFI64 that also has problems. Also the 4,1 has two PCIe 2.x slots 3 and 4 that share a controller but that simply limits bandwidth.
I would have left the TRIM support and NVRAM changes in Yosemite to a separate thread if you wanted to focus on the Sonnet Tempo Pro support in Mac Pro 2010-12 5,1s.
Also the make of SSD can vary and they also have their own firmware as do bootable controllers along with the EFI of the Mac, all of which have to work together. Meaning it might be that Samsung 840 va 840 EVO vs 840 Pro will all be slightly different but my experience is Samsungs work well (as do others like Crucial with the proper firmware - and there was/is an issue with the firmware of the Samsung 840 but not with booting).
The PCIe card gets seen and treated as external and therefore 'eject' but of course you can't when it is the system boot drive.
One thing I found last week and meant to mention: After installing or changing PCIe cards, RESET SMC made all the difference in the world with the long boot delay. Some PCIe cards will add a few seconds, system has to search the device tree which now shows another controller with multiple devices - and sometimes NVRAM and SMC are what I will call "dirty" and need to be rebuilt and reset.

Third party chip and OSX upgrades

i have an original bondi blue imac (233 mhz) that I upgraded years ago to 500mhz with a newer technologies third-party chip. I also have upgraded it to a 40MB HD and 374 Meg RAM with another 8Meg video RAM. Now it is time to do the firmware update in order to upgrade to OSX.
Has anyone had any experience with that firmware update and those types of third party chips? I am afraid!
The manufacturer has discontinued them and I emailed them but haven't got any joy so far.
thanks
kt
iMac bondi :: dual USB ibook Mac OS 9.2.x

Do you have the original CPU handy? You can always downgrade, then do the firmware upgrade, and then upgrade again.
As far as I know the firmware upgrade affects only the logic board and not the CPU, but I don't want to be responsible for you frying your upgrade chip. As the upgrade chip is technically not supported by Apple, they will not have tested their firmware upgrader on a machine that has a third-party chip. But untested doesn't mean it won't work.

Logic Pro 9.1.1 AU third-party plug-ins ongoing issue for many

Where is the Logic development team on this? Nearly all third-party AU plug-ins produce random pops and clicks at the beginning of playback and on occasion randomly during playback but before audio regions in tracks with these plug-ins installed. These pops and clicks are even visible in the track's meter. http://www.gearslutz.com/board/music-computers/482381-logic-3rd-party-plugs-pop- click-nightmare-how-does-rest-world-do.html How many people need to complain? Is Logic Pro considered production software?

I can't imagine a more textbook and apple-friendly environment than what I have. 32-bit is not the problem. I don't believe logic runs at 64 until you're on os 10.6 and I'm still on 10.5.8. My entire rig is what you'd see in an apple store logic demo. I've tried nearly everything:
1) All standard optimization tips including but not limited to no date/time updates, no airport/wi-fi, no bluetooth
2) I have a ultra high-quality external fw drive by G-drive
3) Standard issue ensemble with updated firmware
4) Moving AU component files from system library to user library
If you look at the number of people commenting on the GS thread as well as other forums – the problem is common and needs to be fixed. I'm not the only logic user plagued by this issue:
http://www.logicprohelp.com/viewtopic.php?t=43306
http://www.logicprohelp.com/viewtopic.php?t=50030
I really believe it has something to do with how many third-party plug-ins handle AU's reset or initialize callbacks; somewhere in between. This bug is clearly affecting many users and I'm coming close to starting a petition and devoting some serious time to making a big dorky stink about it on youtube.
Either the AU spec needs to be updated to clarify some tricks (or hacks) specific to Logic's on-demand DSP usage or the logic team needs to publish a notice to all "Logic" AU developers. Optionally, if Logic had a preference to turn OFF on-demand AU DSP (so that plug-ins are always-on like in every other DAW or...ugh...outboard gear). Logic's on-demand AU DSP handling is outdated considering the processing power available in ANY apple computer made within the last 3 years. My CPU meter in Logic barely even lights up. On-demand DSP is overkill and antiquated and the least Logic can do is provide production or mission-critical users the ability to opt-out if they have the CPU power to do so.
Having said all that; I hope I'm wrong about something and can come back here to eat my words and feel very embarrassed about my rant. I'm going to keep digging for solutions – hopefully, I'll find out the secret to whatever it is the few of you are doing to keep your third-party AU plugs quiet before an audio region starts.
Also; Scott at Stillwell Audio has graciously begun trying to track down this very issue and is one of the few DSPers who has taken interest in helping Logic folk.

Third Party base stations for airport express

Hi, I recently bought an AX, my question was answered earlier so I guess my doubt now is which third party products could act as base stations which can be recognized by the AX, which Linksys products (not too expensive) would you recommend? I thank you in advance for your attention.
John

An Airport Express can act as a client (printing and AirTunes) with ANY wifi-certified 802.11b/g wireless router.
In terms of using an Airport Express to extend an existing wireless network, then I wouldn't recommend ANY third party router, I would use an Airport Extreme Base Station or another Airport Express.
It has been shown to work with
- a Linksys WRT54G or WRT54GS (not latest versions v5)
- a Belkin F5D7230-4 and F5D7231
- one specific model from SMC
- one specific model from Buffalo
- BT Voyager 2100
For wireless routers not on this short list - not possible.
In particular, it will not work with any WiFi routers from D-Link or Netgear.
http://www.dd-wrt.com/wiki/index.php?title=WDSLinked_routernetwork
iFelix

Connecting to third-party router, but unable to browse or e-mail

I am using an Airport Extreme card in my PowerBook G4 running firmware version 405.1 (3.90.34.0.p18). Our office Wi-Fi access is through a third-party router. We used to use MAC address filtering, and I had no problem accessing the network.
Recently, for reasons unclear to me, our IT director ditched the MAC address filtering in favor of the WPA-personal standard. I was able to enter the encryption key and get connected to the network, but I wasn't able to get my browser to access the internet, nor send or receive e-mail traffic.
Our IT folks temporarily disabled all security and restarted the wireless router, but I was still only able to connect to the router, and not use my browser or e-mail, so it doesn't seem to be a problem with the use of WPA per se. I tried temporarily turning off my own firewall, too, but the problem remained.
Oddly, I can open up the Terminal and Ping successfully to an outside address -- only http and e-mail traffic seems to be blocked. The Windows-based PCs seem to be able to connect to the wireless network and use their browsers to access the internet without any problem. Any thoughts as to what else I might try, or have the IT administrators try, to resolve the problem?
Thanks,
Sid

Hello kilgores. Welcome to the Apple Discussions!
Something to ask your IT staff is if they use a proxy server for Internet access. If so, do they require proxy configuration scripts (.pac) to provide access to the Internet through your company's firewall. This information would normally be added to your browser's settings.
For Safari: Preferences... > Advanced > Proxies > Change Settings... > Automatic Proxy Configuration

Third party firmware wrt54gs v7

Similar Messages

Maybe you are looking for