Precision 7530 & Precision 7730 owner's thread

Did you use GPU-Z or nvflash to dump the VBIOS? From my experience, GPU-Z loses a few bytes when dumping the VBIOS and can potentially cause flashing errors.

 

I've used GPU-Z after taking the screenshot. I will try nvflash this weekend and will compare the two resulting vbios files just in case.

 

The created nvflash VBIOS dump with latest nvflash version 5.670 is completey identical to the GPU-Z extracted version so I guess it's fine or at least the best I can do

 

For some reason, the performance and battery limiter options have disappeared from Dell Power Manager on my notebook, and power-limit throttling is back (the ThrottleStop option used to work, and no longer).

Any ideas?

 

I've dug around in the Dell Power Manager code (when producing the DellSetThermalSetting console app). It basically queries the BIOS for support for these features and then hides them if it gets a bad response. First things first, I'd say try shutting everything down and doing a clean boot, if you haven't already, and see if that takes care of it ... I don't know why this would have changed without a BIOS update.

[Edit] Maybe try running the DellSetThermalSetting app actually and see if it returns an error, I'm curious...

 

Much obliged. I tried a cold boot, no dice, I only see the battery charge level and nothing else.

DellSetThermalSetting and the Linux Dell SMM tools work, though:


This isn't really a problem as I can change the two most fundamental settings in Dell Power Manager elsewhere, but it definitely is very inconvenient.

 

Just checked and there is no issue with Dell Power Management on my system (DPM 3.7.0, BIOS 1.14.4), so no idea what to suggest other than maybe BIOS reset ...?

 

Long time ago, but I have the fix.
(I spent too long fighting with this today...)

* With the latest Precision 7530 Realtek audio driver installed...
* Download the latest audio driver for the Precision 7520... extract (but do not install).
* From the extracted pile of stuff, open up RealtekAudio\WIN64\RtkNGUI64.exe.
* This is a "Dell Audio" application... go to "Advanced", "Jack information", click on the jack (black circle), and select headset with microphone. Wait a few moments and the "jack mic" should be active.

(Source)

Probably could figure out what files this program needs to run, copy those out, and then have it start automatically with the PC. It has an option to run from the system tray, and pop up a dialog whenever you plug something in to the 3.5mm jack to ask what it is.

Not sure why it is so hard to "find" this program. My 7530 actually had it installed under C:\Program Files\Realtek\Audio\HDA, before I started mucking, but after several driver installs/uninstalls/reinstalls (trying different versions), it is not there anymore. When I first tried to use it, it would give me an error message when I tried to switch the jack to headset mode. But after my driver mucking (settling again on the latest version), running the one from the Precision 7520 package seems to work fine.

All this to figure out that my new Surface Headphones 2 don't support mic over 3.5mm (apparently).
[Edit] Nevermind, they do... Just have to use the special cable that came with them, which has three poles on the headphones side and four poles on the jack side... Looks like the mic is actually in the cable (little black thing) and it doesn't pass through the signal from the mic that is embedded in the headphones themselves.

 

Great sleuthing work. For some reason, the RtkNGUI64.exe program doesn't open on my notebook.

I think a reinstall is in order. I've also been seeing weekly blue-screens, too; need to figure out if it's a memory problem.

 

I've determined that the only files that you need to run the app are RtkNGUI64.exe and WhiteJadeSkinImages64.dll.
I'm unable to get the popup box to fire when plugging something into the 3.5mm jack. That was working when I originally started messing around with this (but it would give me an error when I selected "headset with microphone"). Now I don't get the error but I also don't get the popup box at all, I have to manually fire up the app and select it.

Makes me want to switch to just using a USB adapter...