Contribute
Register

ACPI Dynamic OEM table load error/Waiting for DSMOS/Horrible performance

Status
Not open for further replies.
Installed the Nvidia WebDrivers. I forgot to put the -c command in Terminal. After reboot, the drivers seemed installed, but they failed to load. Even after setting them and a second reboot. I have reinstalled Sierra, to get it fresh. If I forgot to put that command, would it be relevant for the failure?
 
Vyzantion said:
Installed the Nvidia WebDrivers. I forgot to put the -c command in Terminal. After reboot, the drivers seemed installed, but they failed to load. Even after setting them and a second reboot. I have reinstalled Sierra, to get it fresh. If I forgot to put that command, would it be relevant for the failure?
Click to expand...
nvram -c just clears the nvda_drv=1 boot argument (actually it resets all apple related nvram)

To enable the drivers, in config.plist you at least need
Code: 
<key>SystemParameters</key>
<dict>
...
<key>NvidiaWeb</key>
<true/>
...
</dict>
That is if they will work with your card at all. Think I put FakeID for a supported Quadro card with the same generation chip in that config.plist, along with the NvidiaWeb stuff.
 
So, the -c command was useless in my case, anyway. I mean I needed to edit the plist, then select Nvidia Web Drivers from the MenuBar or SystemPreferences, then reboot.
Graphics performance matter nothing to me anyway, I am not into gaming at all or into video or photo editing. I was satisfied with the minimalistic performance of what I had until now. I was able to run Garageband, that was enough, iMovie did not worked, but I did no cared at all about that. Giving another try with Nvidia WebDrivers would matter only if this made it possible for running High Sierra on this hardware, at the same level Sierra works now. I am asking because, even if I would be able to install WebDrivers and improve performance for graphics successfully now, I would still reinstall clean Sierra without them, to have it as it is now, only with Inject Nvidia, without Web Drivers. If I would be able to run High Sierra ok, I shall keep only InjectNvidia. Reinstalling the OS takes time and effort, so I am asking once again: Is it relevant for running High Sierra installing Web Drivers on my present Sierra installation?
 
Last edited:
Vyzantion said:
So, the -c command was useless in my case, anyway.
Click to expand...
A precaution to avoid a very small chance of un-bootable system
Vyzantion said:
I mean I needed to edit the plist, then select Nvidia Web Drivers from the MenuBar or SystemPreferences, then reboot.
Click to expand...
You only need it set in your Clover config.
Vyzantion said:
Tried to browse the web via Safari, from the booted installation drive and I have got the same error. Many sited do not work, including the Apple website. Some, like Google or Tonymacx86 work, but they bring black elements where they were not suppose to be present.
Click to expand...
Vyzantion said:
Reinstalling the OS takes time and effort, so I am asking once again: Is it relevant for running High Sierra installing Web Drivers on my present Sierra installation?
Click to expand...
Installing the web drivers on your present Sierra doesn't require reinstalling the OS does it? It takes a minute. As High Sierra is a mostly incremental update, a working 10.12 config would be a big step towards a 10.13 one. If the web drivers don't work uninstall them and forget about them.
 
Installed Nvidia WebDrivers, edited the plist, selected them. They appeared as loaded, but the graphics was the same, it appeared in About this Mac as absent, although they appeared loaded in the button on the Menu Bar. It is clear they do not work. Removed them, but, after reboot, they kexts still appeared to be present in System/Library/Extensions . I guess the only hope for this hardware configuration is a FakeSMC update.
 
Finaly, with the latest Clover build, I was able to install High Sierra beta 4. But it went terrible slow. Managed to install the required things via Multibeast, and updated Clover. But it is going horrible, things work really slow, sometimes the Menu Bar takes 10 minutes to load, installer crashes, things like that. Something is wrong, the GPU is too old, the ram too little (2gb), or a combination of both? Or some system definition? Attached some files in here, preboot.log and debug.log. . Perhaps would it be better to start a new thread?
Changing system definitions did not seem to help. If I could get the definitions of Macbook late 2009 (altough I could not find on Multibeast that option and this is not a laptop) I could make it work properly)
 

Attachments

  • preboot.zip
    5.3 KB · Views: 227
  • debug.zip
    89 KB · Views: 265
Last edited:
According to the Information posted already, what hardware upgrade seems more important? The graphics card or the ram (from 2 gb to 4 gb)?
 
Last edited:
Public Beta 5, at first, the same horrible performance of Public Beta 4. Installed all neccesary components (Multibeast, Clover, PS2 kext etc, then reboot for the first internet connection, as usual. Updating via Terminal gave an error message. Shut down the PC and re-open it in the morning. After the 20 minutes of waiting for the automatic morning maintenance, reboot and a real surprise. The OS started to work ok. I was able to update via Terminal. Only MPLAyer OS X failed to load, from the old, average software used. Safari 11 has some glitches on several websites, like Facebook, Weather Channel or the login page on the Google Account. Perhaps the bad performance was caused by processes of gathering setup information and, once it is uploaded, performance improves. Attached PReboot.log . Does it make sense any of this?
 

Attachments

  • preboot.zip
    75.2 KB · Views: 225
The DSMOS error is back in beta 7. It gets stuck on va_page_contigous: zone_pc called... wired count is 46451
Perhaps another Clover and/or FakeSMC update will solve it again.
Update: I have pressed reset after reinstall and the repeat of the error, wanted to get the preboot.log (the attached preboot1.zip) . Then, it booted it up fine, and got to the installation screen. That is really weird. Also attached the preboot for the installed OS (preboot2.zip). When I took preboot2, VooDoo HDA was not loaded at boot, but on reboot it was re-established.
 

Attachments

  • preboot1.zip
    105.7 KB · Views: 236
  • preboot2.zip
    87.6 KB · Views: 209
Last edited:
Another clean install. This time I allowed it about 40 minutes to be stuck in the error (I was caught up with other things). Sometimes during those 40 minutes it managed to go to the login screen, without reset. This gets more and more weird. I can not figure a full pattern of these errors.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top