Oh, not your fault at all. You did good. Don't feel guilty!
I pinned @Phipli 's comment with the correction - sorry about that!Other than the fact that I created the patch application, not @Phipli ... it would be nice if people's work was accurately credited in youtube videos, although I know the youtube crowd is not fond of me. A correction would be nice, @omgmonsters
Thank you, Sean! Great to see the TAM back on the channel, and looking forward to the Mac OS X effortI pinned @Phipli 's comment with the correction - sorry about that!
@omgmonsters That will need some care - both OSX and the SATA card need stuff in nvramrc. You will need to combine the two scripts from XPostFacto and for SATA.Mac OS X effort
I pinned @Phipli 's comment with the correction - sorry about that!
Ah, thanks for this pointer!@omgmonsters That will need some care - both OSX and the SATA card need stuff in nvramrc. You will need to combine the two scripts from XPostFacto and for SATA.
Perfectly do-able, but not currently a one click install.
Depending on what format newlines were used, it doesn't show. Apply the patch and restart. Don't worry about the current contents thing.Hi all,
I'm having a bit of trouble getting the nvram patch to "take" - this is on a stock TAM with Tango 2.0 card installed and a fresh install of Mac OS 9.1 with the USB and Firewire drivers installed.
With or without the patch installed, it continues to display 4 port Ethernet card and pci-bridge. I can charge off FW but not detect any devices - this includes a FW iPod and FW hard disk both working on another FW Mac.
See below, when patch is run nothing is displayed in the your current nvramc. I'm assuming something should be displayed here if the patch applied properly.
I've reset the PRAM, reset the CUDA and disconnected the power/battery for some hours.
Note how "your current nvramrc" is 190 bytes? It just doesn't display correctly because of the newlines.I'm assuming something should be displayed here if the patch applied properly.
Note how "your current nvramrc" is 190 bytes? It just doesn't display correctly because of the newlines.
Probably in the stdio lib.oh dear, is this a bug in the patcher?
Well, not a bug, it expects classic mac newlines, and the patch is Unix style.oh dear, is this a bug in the patcher?
Another idea I had was just to get rid of the PCI-PCI bridge altogether... Technically it shouldn't be necessary, as you can in theory just put all 3 devices (in this case SATA, FireWire and USB controller) all on the same PCI bus. That is if you don't end up reaching some sort of PCI device limitation on these machines.
My plan with dingusppc was to figure out how Open Firmware fails with the emulated PCI card (with pci-bridge and multifunction devices) then go from there.
This is all very cool to see developing. One thing I'm curious about is whether or not this sort of patching could be applied to the ROM of the SuperMac S900 ("Storm Surge"?). As far as I know, the issue faced by the S900 is that four of its six PCI slots are behind a PCI-PCI bridge and because of this the ROM does not identify many installed cards correctly. PCI cards that themselves have PCI-PCI bridges do not work at all, AFAIK. Are these similar issues or am I barking up the wrong tree?
Can confirm your patch works with all the combo cards I have here. Good stuff!
Ethernet on the three-way card doesn't work, but it's detected, and I'm apt to put that down to Realtek weirdness rather than Gazelle weirdness.
Do you have RealTek's driver for the 8139 cards? But it might need some kind of modification because of the bridge. IIRC, there's instructions in the 8169 driver regarding editing some parameters in the driver such as Vendor ID, depending on who used RealTek's chip in their product.
I did - and I modified it according to the instructions. Didn't have any luck, than ran out of time to attempt to diagnose. I don't know really very much about this class of machine, alas...
Does the S900 have an ATI chip? If not, then it's probably a different problem.
Are there any posts that describing the S900 issue?