No Signal on Boot with Samsung HDTV over DVI/HDMI

Hey guys,
I have done some searching but to no avail. I have tried everything I can find/think of with absolutely no luck.

I have a brand new Samsung LN46B750 which I have connected to my desktop for use as an HTPC. VGA works fine, but I would much prefer to use a digital connection. SO, I have an HDMI <> DVI adapter and a monoprice HDMI cable connecting my GeForce 6800 to the HDMI/DVI port on the HDTV.

I have tried 182.5 and the latest Nvidia drivers as well as the generic W7 drivers. It's all the same.

Everything works fine in the OS so long as I make it past the Windows splash screen. And unfortunately, that never happens. I believe that the problem lies in the auto adjustment of the screen when 7 starts loading. (If I boot without the TV connected, and then connect after the splash screen has loaded, everything is perfect.) Is there any way to disable the auto detection/adjustment of the TV and just have the OS always boot into 1920x1080 @ 60 Hz. I am really tired of the blank or black screen every time I reboot. This is a terrible bug with W7 or EDID and it needs to be fixed now Microsoft!

Thank you!

I have a Samsung LNT4665F.

The problem actually lies in the Samsung - the I/O board is, well, been replaced a few times. Service warranty even replaced the entire TV after four failed repairs.

The good news - Windows 7.7600.16385 with an ATI HD3850 no longer gets caught by the Samsung oddity.

Perhaps it is a Samsung IO problem, but I have seen similar issues reported regarding other manufacturers as well. Personally, after four replacements and repairs, I would look at the possibility that the issue is not with the TV's hardware. They say that if you are not part of the solution, you are part of the problem. I believe that the way that the display is initialized on startup is a large part of this glitch. As I mentioned, connecting immediately after the splash screen is shown allows the TV to function flawlessly. If there is any way to bypass the automatic configuration of the display I would certainly like to try it. This is a software issue which can be solved on either side of the cable and the PC side seems the most likely side for a fix. Any ideas?

Hi i have a similiar issue...

I worked already with my Win7 System without problems. But today when I started my PC I just saw the win 7 logo during booting. but when the login screen appears my Samsung T220 switched to "No Signal".

Why does it work anymore. I didn't changed anything. Just a win update this week. Any suggestions??

Thanks and regards,
Oliver


EDIT:

I just tried to load the Save mode and the Samsung is working. Furthermore I used another display Fujitsu siemens TFT and it works in the normal mode fine.

So it must be a problem with the Samsung...

I'm lookin' into an LN37B650 myself... For the Network Port of course...

What do you think of the Samsung's in general and any other Connectivity Issues besides what's mentioned here...???

Rayk, if it works in safe mode, it is not a hardware issue. Something is wrong with your software. Anyone have any ideas for a fix, short of unplugging and replugging my TV on boot? I would really like to disable the display auto-detection / auto-configuration feature and just boot with 1920x1080 at startup. I am very frustrated with this issue.

Thanks!



oldewolfe, The TV itself is great. The network port leaves a little to be desired. Using DLNA you con only stream certain video codecs. Otherwise, that feature works fairly well. The 650 is a good series, I purchased the 750 because I didn't care for the bezel of the 650, and the 750 is reported to have better black levels. The only downfall I can find with this particular set is the poor viewing angle. Otherwise it is superb. I do recommend purchasing from Amazon.com because they have had excellent customer service.

Here's the answer: every digital display device has a unique identifier attached to it, called an Electron Device ID (EDID). This number uniquely identifies a specific digital display before announcing its capabilities. So the conversation goes something like this:

Plasma Monitor: "Hi Computer! My EDID is Bob!!!"
Vista: "Hey there, Bob! I'm Vista. How's it hanging?"
PM: "Slightly to the left, Vista!"
Vista & PM: "HaHaHaHa!"
PM: "I kill me!"
Vista: "Yes, that was funny. Tell me Bob, what can you do?"
PM: "Well, I can display 12 resolutions of various color depths, and I have a physical dimension of 1900x1200 pixels!"
Vista: "Let me write that down....ok. Got it. Thanks"
PM: "No problem - well, I'm going to sleep now!"
Vista: "G'night Bob!"

What? Am I anthropomorphizing again? Sorry.

Anyway - certain display devices (especially the earlier implementations, like my Sony plasma screen) incorrectly implemented some of the VESA protocols. In the case of my plasma, the VESA protocol to announce that it is being turned on is probably incorrect. XP was forgiving of that particular error, but Vista - with its overly aggressive power saving features - is not.

So, once Vista instructed the graphics card to power down, it never tells it to power back up again because the plasma screen never issued the correct series of VESA commands when it was turned back on.


VIA Notes From the Rocket: The Big Vista Sweep, Part V

So I want to make vista more forgiving by just setting the output manually. Help!