I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card - 5700LE or such). I noticed my mistake right away and I immediately disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
Rick B.
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
Rick B.
Unless you have 20 y/o CRT, your LCD/CRT will simply shut down if you try to use an invalid resolution/refresh rate. Some monitors will not display the OSD (E.g. Menu) when connected to invalid display source. Just disconnect the monitor from the machine and/or fix the X.org configuration and the menu will work just fine.
- Gilboa
On Tue, 28 Nov 2006, Gilboa Davara wrote:
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
Rick B.
Unless you have 20 y/o CRT, your LCD/CRT will simply shut down if you try to use an invalid resolution/refresh rate. Some monitors will not display the OSD (E.g. Menu) when connected to invalid display source. Just disconnect the monitor from the machine and/or fix the X.org configuration and the menu will work just fine.
You are off by about 10 years. Those did not come about until about 1995-96. Some flat panels were worse. (I have an NCD flat panel that got damaged by bad frequencies.)
What was the date the displa was made?
On Tuesday 28 November 2006 08:06, Gilboa Davara wrote:
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card - 5700LE or such). I noticed my mistake right away and I immediately disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
Rick B.
Unless you have 20 y/o CRT, your LCD/CRT will simply shut down if you try to use an invalid resolution/refresh rate. Some monitors will not display the OSD (E.g. Menu) when connected to invalid display source. Just disconnect the monitor from the machine and/or fix the X.org configuration and the menu will work just fine.
You hope. Disconnecting things while powered up is never a good idea, ever. See my previous reply.
- Gilboa
On Tue, 2006-11-28 at 10:59 -0500, Gene Heskett wrote:
On Tuesday 28 November 2006 08:06, Gilboa Davara wrote:
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card - 5700LE or such). I noticed my mistake right away and I immediately disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
Rick B.
Unless you have 20 y/o CRT, your LCD/CRT will simply shut down if you try to use an invalid resolution/refresh rate. Some monitors will not display the OSD (E.g. Menu) when connected to invalid display source. Just disconnect the monitor from the machine and/or fix the X.org configuration and the menu will work just fine.
You hope. Disconnecting things while powered up is never a good idea, ever. See my previous reply.
Ouch. Never thought about that.
Thanks. - Gilboa
On Tuesday 28 November 2006 07:06, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
No, I suspect (I'm a C.E.T.) where you made the mistake was in disconnecting it, no doubt while powered up on both ends of the connection. Now go find one of your old grammer school teachers and tell her you've been a bad boy & take the knuckle rapping she will dish out. :-)
I suspect that in the process of unplugging it, a ground connection was the first to be opened. In that case the input electronics in the monitor, and possibly even the output stages of the video card are pretty historical. From your description its plain the monitor needs a trip to the shop, maybe even back to the factory shop, probably for a fresh copy of its video board.
I'd test the video card in the computer with another monitor to see if it survived.
Today Gene Heskett did spake thusly:
On Tuesday 28 November 2006 07:06, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
No, I suspect (I'm a C.E.T.) where you made the mistake was in disconnecting it, no doubt while powered up on both ends of the connection. Now go find one of your old grammer school teachers and tell her you've been a bad boy & take the knuckle rapping she will dish out. :-)
Tsk. "Grammar"
I suspect that in the process of unplugging it, a ground connection was the first to be opened. In that case the input electronics in the monitor, and possibly even the output stages of the video card are pretty historical. From your description its plain the monitor needs a trip to the shop, maybe even back to the factory shop, probably for a fresh copy of its video board.
I'd test the video card in the computer with another monitor to see if it survived.
I'd reboot with it plugged in and see if I got the console...far easier than a trip to the shop... ;)
On Tuesday 28 November 2006 11:18, Scott van Looy wrote:
Today Gene Heskett did spake thusly:
On Tuesday 28 November 2006 07:06, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card - 5700LE or such). I noticed my mistake right away and I immediately disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
No, I suspect (I'm a C.E.T.) where you made the mistake was in disconnecting it, no doubt while powered up on both ends of the connection. Now go find one of your old grammer school teachers and tell her you've been a bad boy & take the knuckle rapping she will dish out. :-)
Tsk. "Grammar"
I never claimed to be the last word in spelling. But you'll have to admit you did get the message anyway. :)
I suspect that in the process of unplugging it, a ground connection was the first to be opened. In that case the input electronics in the monitor, and possibly even the output stages of the video card are pretty historical. From your description its plain the monitor needs a trip to the shop, maybe even back to the factory shop, probably for a fresh copy of its video board.
I'd test the video card in the computer with another monitor to see if it survived.
I'd reboot with it plugged in and see if I got the console...far easier than a trip to the shop... ;)
Humm, good point, but if you don't get the console, then what?
Then you're back to the spare monitor for the test.
I'd reboot with it plugged in and see if I got the console...far easier than a trip to the shop... ;)
--
Although I may have destroyed the monitor, the computer and graphics card continue to work perfectly.
How difficult and expensive would it be to diagnose and fix? Would it be better just to buy a new monitor? This had to happen just at the time I need the monitor most.
Rick B.
Rick Bilonick wrote:
I'd reboot with it plugged in and see if I got the console...far easier than a trip to the shop... ;)
--
Although I may have destroyed the monitor, the computer and graphics card continue to work perfectly.
How difficult and expensive would it be to diagnose and fix? Would it be better just to buy a new monitor? This had to happen just at the time I need the monitor most.
Rick B.
With all the RF shields and fragile wiring harnesses in one display I examined internally and did get working for a bit, I say it depends upon your patience and if you can deal with fragile components fairly well. The surface mounted components need special tool to remove. Also unless you have good schematics and tools, it would be a shot in the dark at best.
Jim
How do,
On Tue, 2006-11-28 at 22:35 -0500, Rick Bilonick wrote:
I'd reboot with it plugged in and see if I got the console...far easier than a trip to the shop... ;)
--
Although I may have destroyed the monitor, the computer and graphics card continue to work perfectly.
How difficult and expensive would it be to diagnose and fix? Would it be better just to buy a new monitor? This had to happen just at the time I need the monitor most.
Probably depends on how comfortable you are working with smt (surface mount technology) & having/access to the proper tools. Most newer electronics use lead free solder & that can be a real PITA :-(
If you have access to newsgroups, there's an electronic repair group & you could run that past them. Most folk there will recommend purchasing a new monitor though :-)
Rick B.
taharka
Lexington, Kentucky U.S.A.
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything. The on light switches quickly from green to a constant yellow and displays "no input signal" on the screen regardless of whether I'm using the analog or digital input. I can no longer bring up the setup menu (e.g., to change from analog to digital) - no menu whatsoever. I called Planar and they said it wouldn't damage the display but it seems like too much of a coincidence.
I blew the crap out of a beautiful 15" MultiSync, back when they cost large dollars. The flyback went "ZINNNGG!" and <poof!> when I over drove it. One of the beauties as well as fallbacks to Linux is that it will dutifully do what you tell it to do. Maybe there is some sort of protective device (like a fuse?) inside? Wave a chicken foot. Smack it! Curse it! "To the last, I will grapple with thee. From hell's heart, I stab at thee. For hate's sake, I spit my last breath at thee."
Something has gotta work... troubleshooting with a shotgun, Ric
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything.
I can't imagine an LCD monitor failing for that sort of reason. CRTs get damaged, that way, because the EHT used to drive the tube is derived from the video signals (directly or indirectly). The voltage changes with the frequency, and can go too far from tolerable.
LCDs don't work that way. Their power isn't related to the incoming video signal. I'd be more inclined to believe three things:
1: You're plugging it into something that's not providing a useable signal, so you're not seeing anything.
2: Damage to the video connectors or cables.
3: Pure chance that a fault developed at the same time. It could well be that if you'd picked up the monitor, and not done anything else but move it, that a fault might have developed.
I can't imagine an LCD monitor failing for that sort of reason. CRTs get damaged, that way, because the EHT used to drive the tube is derived from the video signals (directly or indirectly). The voltage changes with the frequency, and can go too far from tolerable.
LCDs don't work that way. Their power isn't related to the incoming video signal. I'd be more inclined to believe three things:
1: You're plugging it into something that's not providing a useable signal, so you're not seeing anything.
2: Damage to the video connectors or cables.
3: Pure chance that a fault developed at the same time. It could well be that if you'd picked up the monitor, and not done anything else but move it, that a fault might have developed.
-- (Currently testing FC5, but still running FC4, if that's important.)
Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
The monitor doesn't work with either the analog or the digital cable and I've used the cables with other computers and they work. I've tried three computers and there is no display plus I cannot bring up the OSD menu. So I guess I'm stuck with #3. I've checked and the monitor has a 3-year warranty with another year left so I'll try to have it repaired under warranty.
Rick B.
Tim:
3: Pure chance that a fault developed at the same time. It could well be that if you'd picked up the monitor, and not done anything else but move it, that a fault might have developed.
Rick Bilonick:
The monitor doesn't work with either the analog or the digital cable and I've used the cables with other computers and they work. I've tried three computers and there is no display plus I cannot bring up the OSD menu. So I guess I'm stuck with #3. I've checked and the monitor has a 3-year warranty with another year left so I'll try to have it repaired under warranty.
I would. It should survive being asked to show something out of range, and being plugged and unplugged while operating (although that's not such a brilliant thing to do, it's crap design on the product's behalf if its inputs aren't adequately protected). It doesn't sound like you've done anything abnormal to it, so I'd throw it back at them.
On Wed, 2006-11-29 at 07:42 -0500, Rick Bilonick wrote:
I can't imagine an LCD monitor failing for that sort of reason. CRTs get damaged, that way, because the EHT used to drive the tube is derived from the video signals (directly or indirectly). The voltage changes with the frequency, and can go too far from tolerable.
LCDs don't work that way. Their power isn't related to the incoming video signal. I'd be more inclined to believe three things:
1: You're plugging it into something that's not providing a useable signal, so you're not seeing anything.
2: Damage to the video connectors or cables.
3: Pure chance that a fault developed at the same time. It could well be that if you'd picked up the monitor, and not done anything else but move it, that a fault might have developed.
--
The conclusion of this: I called Planar, I gave them the serial number and from that they knew who bought the monitor. Fortunately, it was only about halfway through the 3-year warranty. I did not have to send any documentation to them. They sent me a replacement by 2nd-day FedEx and I shipped the broken monitor back in the same box at no cost. The last tech I spoke with thought it was a dead backlight.
So far, the replacement works fine.
Rick B.
On Wed, 2006-11-29 at 21:07 +1030, Tim wrote:
On Tue, 2006-11-28 at 07:06 -0500, Rick Bilonick wrote:
I have a Planar 20" PL2010M LCD monitor. I attached it to an Athlon 64 system running FC6 and using the nvidia proprietary driver (the latest available). I tried (foolishly) the 1920x1080 interlaced output. The monitor said it was outside the range. I reset to 1600x1200 noninterlaced and everything was fine. Later I connected a similar computer (running FC5) that was displaying 1920x1080i (same nvidia card
- 5700LE or such). I noticed my mistake right away and I immediately
disconnected the monitor. Now, the PL2010M won't display anything.
I can't imagine an LCD monitor failing for that sort of reason. CRTs get damaged, that way, because the EHT used to drive the tube is derived from the video signals (directly or indirectly). The voltage changes with the frequency, and can go too far from tolerable.
LCDs don't work that way. Their power isn't related to the incoming video signal. I'd be more inclined to believe three things:
1: You're plugging it into something that's not providing a useable signal, so you're not seeing anything.
2: Damage to the video connectors or cables.
3: Pure chance that a fault developed at the same time. It could well be that if you'd picked up the monitor, and not done anything else but move it, that a fault might have developed.
Hey, you can always return it... especially if you take some victim stance and wail about it being almost Xmas, taxes are due, your hip is in need of replacement, the family pet has become old and incontinent and must be put to sleep, that kinda thing. Or, you could get aggressive and show consumer teeth over the quality of this dead parrot. Whatever, just see if they will replace it. They did say that what you did shouldn't have blown it up, right? I just wouldn't 'mention' that bit again. Ric
At 15:53 29/11/2006, you wrote:
Hey, you can always return it... especially if you take some victim stance and wail about it being almost Xmas, taxes are due, your hip is in need of replacement, the family pet has become old and incontinent and must be put to sleep, that kinda thing. Or, you could get aggressive and show consumer teeth over the quality of this dead parrot. Whatever, just see if they will replace it. They did say that what you did shouldn't have blown it up, right? I just wouldn't 'mention' that bit again. Ric
And make sure that whoever you return it to isn't on the Fedora Core list ;-)
On Wednesday 29 November 2006 10:18, David Fletcher wrote:
At 15:53 29/11/2006, you wrote:
Hey, you can always return it... especially if you take some victim stance and wail about it being almost Xmas, taxes are due, your hip is in need of replacement, the family pet has become old and incontinent and must be put to sleep, that kinda thing. Or, you could get aggressive and show consumer teeth over the quality of this dead parrot. Whatever, just see if they will replace it. They did say that what you did shouldn't have blown it up, right? I just wouldn't 'mention' that bit again. Ric
And make sure that whoever you return it to isn't on the Fedora Core list
Don't worry about it they are mostly all WW's [Windows Weenies} ;-)
;-)
-
Alan -
David Fletcher -
Gene Heskett -
Gilboa Davara -
Grumpy -
Hadders -
Jim Cornette -
Ric Moore -
Rick Bilonick -
Scott van Looy -
taharka -
Tim