Hello,
I'm having serious problems with my 19" CRT, a Sony CPD-G400, running off a Radeon 9700 Pro. It was working well until today, seemingly because of damage caused to the EDID of the monitor by the ATI Linux drivers. Upon rebooting into Windows from Linux today, the monitor was detected as "Default Monitor" by Windows, in spite of it having been properly set up with the CPD-G400 driver many moons ago. Although one can still change the resolution of the monitor to any that is supported, the refresh rate is locked to 60 Hz. Changing the refresh rate to any higher, supported rate using the Control Panels' Display applet will not actually change the refresh rate of the monitor; it remains locked at 60 Hz no matter what it is set to in the Control Panel. Manually updating the "Default Monitor" driver so it is replaced by the proper CPD-G400 driver is possible, but changing the refresh rate still has no effect. If all monitors are deleted in Device Manager, any residual entries are cleared from the Registry under CurrentControlSet and the system is rebooted, the "Default Monitor" is redetected and the problems continue just as before. Additionally, the game of Battlefield Vietnam runs in 60 Hz, even though it is locked to 1024x768 at 100 Hz in its options panel. Using PowerStrip or Viewsonic's EDID.exe utility to query the monitor for EDID/DDC information fails, with a message stating that no such information can be retreived. Powering off and unplugging both the system and monitor for ninety minutes failed to change anything.
I believe that these problems were caused by revision 3.11.1 of the ATI Linux driver. There are reports on the Rage3D forums of v3.11.1 of the ATI Linux driver causing the same problem I describe above by damaging the monitor EDID/DDC. I had been running v3.11.1 on my Gentoo Linux install since the day it was released. Today, after the problem reared its ugly head, I upgraded to 3.14.1, but they have not had any effect (which would be expected, as the damage has seemingly already been done). The monitor was working fine last night in both Windows and Linux. I rebooted to Linux to do some stuff, and midway through the session, X crashed. It restarted, I logged back in, and everything was fine. This afternoon, I rebooted back into Windows, and the problem began. Now, whenever I start X in Linux, the monitor runs in 640x480 at 60 Hz, rather than 1280x960 at 100 Hz as X is configured. Although the thread linked above lists several possible solutions, none have worked.
To summarize:
Any help you can provide will be greatly appreciated, as I'm desperate to restore this monitor to working operation. If the monitor is indeed doomed to eternal operation at 60 Hz, it's about as useful to me as a 55-pound block of wood. Although my 9700 Pro has given me excellent service over the last two years, it will be the last ATI card I buy if I have to worry about their drivers frying monitors. Thanks in advance!
I'm having serious problems with my 19" CRT, a Sony CPD-G400, running off a Radeon 9700 Pro. It was working well until today, seemingly because of damage caused to the EDID of the monitor by the ATI Linux drivers. Upon rebooting into Windows from Linux today, the monitor was detected as "Default Monitor" by Windows, in spite of it having been properly set up with the CPD-G400 driver many moons ago. Although one can still change the resolution of the monitor to any that is supported, the refresh rate is locked to 60 Hz. Changing the refresh rate to any higher, supported rate using the Control Panels' Display applet will not actually change the refresh rate of the monitor; it remains locked at 60 Hz no matter what it is set to in the Control Panel. Manually updating the "Default Monitor" driver so it is replaced by the proper CPD-G400 driver is possible, but changing the refresh rate still has no effect. If all monitors are deleted in Device Manager, any residual entries are cleared from the Registry under CurrentControlSet and the system is rebooted, the "Default Monitor" is redetected and the problems continue just as before. Additionally, the game of Battlefield Vietnam runs in 60 Hz, even though it is locked to 1024x768 at 100 Hz in its options panel. Using PowerStrip or Viewsonic's EDID.exe utility to query the monitor for EDID/DDC information fails, with a message stating that no such information can be retreived. Powering off and unplugging both the system and monitor for ninety minutes failed to change anything.
I believe that these problems were caused by revision 3.11.1 of the ATI Linux driver. There are reports on the Rage3D forums of v3.11.1 of the ATI Linux driver causing the same problem I describe above by damaging the monitor EDID/DDC. I had been running v3.11.1 on my Gentoo Linux install since the day it was released. Today, after the problem reared its ugly head, I upgraded to 3.14.1, but they have not had any effect (which would be expected, as the damage has seemingly already been done). The monitor was working fine last night in both Windows and Linux. I rebooted to Linux to do some stuff, and midway through the session, X crashed. It restarted, I logged back in, and everything was fine. This afternoon, I rebooted back into Windows, and the problem began. Now, whenever I start X in Linux, the monitor runs in 640x480 at 60 Hz, rather than 1280x960 at 100 Hz as X is configured. Although the thread linked above lists several possible solutions, none have worked.
To summarize:
- The EDID/DDC of my monitor, a Sony CPD-G400, seems to have been corrupted. Although it will run in different resolutions, nothing will get it to run above 60 Hz.
- Windows detects the monitor as "Default Monitor", rather than as a Sony CPD-G400 as it always has in the past.
- It's possible to change the resolution through the Control Panel, but adjusting the refresh rate has no effect, even if the proper driver for the monitor has been forcibly installed.
- Deleting all monitor profiles through Device Manager, clearing any leftover values left in the registry under CurrentControlSet, and rebooting does nothing.
- Utilities designed to query EDID/DDC information fail to communicate with the monitor.
- Powering off and unplugging both the monitor and system for ninety minutes did nothing.
Any help you can provide will be greatly appreciated, as I'm desperate to restore this monitor to working operation. If the monitor is indeed doomed to eternal operation at 60 Hz, it's about as useful to me as a 55-pound block of wood. Although my 9700 Pro has given me excellent service over the last two years, it will be the last ATI card I buy if I have to worry about their drivers frying monitors. Thanks in advance!