Posted 09 May 2012 - 09:20 AM

SRSR333

InsanelyMac Geek

Members

123 posts

Gender:Male

Location:Singapore

Hey, thanks for the great guide to change the display name. I'm a little, ahem, *noob*, could I have a little more layman kind of instruction? I understood the part about entering commands in Terminal and changing the hex values to dec, but the next few steps are a complete blank. Please help...

Posted 17 July 2012 - 09:18 AM

philip_petev

InsanelyMac Protégé

Members

94 posts

Gender:Male

Location:Haskovo, Bulgaria

Hey, thanks for the great guide to change the display name. I'm a little, ahem, *noob*, could I have a little more layman kind of instruction? I understood the part about entering commands in Terminal and changing the hex values to dec, but the next few steps are a complete blank. Please help...

I'm working on a shell script, which will generate this information automatically, stay tuned...

Posted 17 July 2012 - 07:25 PM

HackMan85

InsanelyMac Geek

Members

226 posts

Gender:Male

Location:napoli

Interests:Computer e sapere informatico.

Hello everyone, I have a weird problem, when I enter the commands that are used for our data I get this result:
ioreg-l-x-w0 | grep DisplayProductID
"DisplayProductID" = 0x717
ioreg-l-x-w0 | grep DisplayVendorID
"DisplayVendorID" = 0x756e6b6e
but these results are the path to the file located in:
System/library/displays/overrides/DisplayVendorID-756e6b6e
and the file is called: DisplayProductID-717, converting them to decimal results in the file already exists, how can I get the real information of my LG LCD? mine is a notebook asus x54hy.

Posted 17 July 2012 - 08:42 PM

philip_petev

InsanelyMac Protégé

Members

94 posts

Gender:Male

Location:Haskovo, Bulgaria

Hello everyone, I have a weird problem, when I enter the commands that are used for our data I get this result:ioreg-l-x-w0 | grep DisplayProductID"DisplayProductID" = 0x717ioreg-l-x-w0 | grep DisplayVendorID"DisplayVendorID" = 0x756e6b6ebut these results are the path to the file located in:System/library/displays/overrides/DisplayVendorID-756e6b6eand the file is called: DisplayProductID-717, converting them to decimal results in the file already exists, how can I get the real information of my LG LCD? mine is a notebook asus x54hy.

This is happening because you already have the information for your display in the Overrides folder. If you want to get your real information, delete this folder or simply remove it from the Overrides folder, restart your laptop and after this run the following commands:

Posted 18 July 2012 - 12:22 PM

HackMan85

InsanelyMac Geek

Members

226 posts

Gender:Male

Location:napoli

Interests:Computer e sapere informatico.

I deleted the folder displayvendorid-756e6b6e and I emptied the trash, however, the results of the 2 commands that you told me to enter when I wrote them in the end they gave me a result that was already in the 717 files that I deleted the folder 756e6b6e, rusultato of the command is this:

also eliminating the folder of files by starting SwitchResX still indicates that the path of the configuration file is: "DisplayProductID" = 0x717"DisplayVendorID" = 0x756e6b6eit is as if the file still existedAlways missing the vendorid that does not appear in SwitchResX

Posted 18 July 2012 - 11:39 PM

philip_petev

InsanelyMac Protégé

Members

94 posts

Gender:Male

Location:Haskovo, Bulgaria

1815(dec)=0x717(hex) and 1970170734(dec)=0x756e6b6e(hex), so everything seems to be ok. The outputs seems fine (I didn't understand why the -x parameter in the first two commands hasn't worked, but it's not so important). So, it seems these are your real values.

Try this script, it works according to the instructions in the first post. It will generate the data for your laptop display in the folder, where the script is located, but you have to remove all custom override information for your display and restart the laptop, before use it. The usage is:

genEDID.sh <name>

where <name> is the name you want to see in About This Mac/More info. Remember to use quotes, double quotes or "\ " between the words, if you want a name with more than one word. And also remember, the script will generate the EDID information only for the laptop display and not for the external display, if you have such attached.

There's no need to use sudo, the script works fine without it. And I see no reason for such behaviour, the script uses only commands, that are included in OSX - ioreg, grep, sed, plutil. Try to run it like this:

I always go back to this script, however, result from 0 at the beginning of post commands do not go out with 0.I'm sorry you are so giving a huge annoyance, but I should so like to use this operating system since January and I'm trying unsuccessfully to run well this monitor, just earn some money I'll buy one immediately.

I always go back to this script, however, result from 0 at the beginning of post commands do not go out with 0.I'm sorry you are so giving a huge annoyance, but I should so like to use this operating system since January and I'm trying unsuccessfully to run well this monitor, just earn some money I'll buy one immediately.

This script is for use only with laptop diplays, not with external displays. Is your display external or not? I think I said this few posts ago - it will detect only the laptop display and not the external one.

Posted 22 July 2012 - 09:37 AM

I use only the internal monitor, Sometimes I think it could be the video card 'cause some people find problems, but' with the external monitor works fine.

What's your videocard? Actually nevermind, ok, can you do something for me: open the Terminal, run the following command:

ioreg -lxw0 >> ~/dump.txt

You'll find a file called dump.txt in your home folder, zip it and attach it here.

Edit: I suspect what could be the problem: I wrote the script for HP ProBook 4x30s with Intel HD 3000 graphics in mind, it was suppose to be used only with laptops with such graphics. Maybe it will work with other laptops with Intel HD 3000 graphics, but I can't say will it work on laptops with other graphics. I also suspect that the names of the displays on laptops with different graphics are also different (the names in the IO Register). So I think it's my fault if I misguided you. But I think maybe it's a good idea to make the script graphics-independеnt.

Posted 22 July 2012 - 05:22 PM

HackMan85

InsanelyMac Geek

Members

226 posts

Gender:Male

Location:napoli

Interests:Computer e sapere informatico.

I have new information, booting in verbose mode, I noticed that the kext RadeonMonitor.kext I do not recognize the video card even if the kext correctly recognize all Ati6000controller.kext, I must see if not having the monitor configured correctly or if this happens I have to add something to the kext, tonight I will try to create a log file of the boot, about chameleon some settings may prevent proper recognition? I turned PciRoot because if you do not active the screen stays black.