The 20B-xp-raw2-hp.txt file will work AFTER you replaced all,withSPACE. So 00,FF,FF,FF, becomes 00 FF FF FF .
Another important part is to make sure the file is owned by root and can be accessed during boot.
I honestly do not know. But given the fact that the raw output from MonInfo as ASCII was in an incompatible format, I guess the binary format is also not compatible. After you used the txtversion of the EDID you should be able to extract it again as a valid bin file through nvidia-settings or nvidia-xconfig.
Most likely because the Xorg and NVIDIA driver were not able to receive a valid EDID from the monitor when querying during startup.
Usually if an EDID appears in Windows, it is sent from the monitor itself. If the naming is incorrect that should not influence the timings.
Unfortunately I don’t know any other free tools to read the EDID. But on Linux if you run the X server with lvl 6 verbose logging, you might receive EDID details that you can read out with nvidia-xconfig
-E FILE, --extract-edids-from-file=FILE
Extract any raw EDID byte blocks contained in the specified X log file LOG ; raw EDID bytes are
printed by the NVIDIA X driver to the X log as hexidecimal when verbose logging is enabled with
the "-logverbose 6" X server commandline option. Any extracted EDIDs are then written as binary
data to individual files. These files can later be used by the NVIDIA X driver through the
"CustomEDID" X configuration option.
Thank you for further suggestions.
But I haven’t any correct data file relevant to the CRT monitor, and that’s why I’m looking to get its EDID data.
I know there are softwares that can read directly from the monitor memory, but I can’t find any of them.