MacBook Pro to Toshiba LCD Television Problem

Question

Level 1

0 points

MacBook Pro to Toshiba LCD Television Problem

Finally got hold of a DVi to HDMi Cable to connect my MacBook Pro to my new Toshiba 32" Regza XV Series LCD Television 32XV555D.

Everything worked initially fine, plugged the MacBook into the back of the TV HDMi port with the cable, switched on the TV and booted the mac, desktop was extended perfectly.

After clicking on the Displays icon in system preferences the TV screen turned Blue. Toshiba TV shows up in the displays preferences dialog box and in the display icon bar in the top menu and lists the resolutions but will not do anything other than show a blue screen on the television.

I have tried resetting both PRAM and PMU settings, tried using both DisplayConfigX and SwichRes X but can't get anything bar the Blue screen to show.

Any ideas please ? This was a test to see what the TV was like before getting a Mac MIni to use with it, but after tonight's issues I am in no rush to order one !

Regards

Rich

Macbook Pro, Mac OS X (10.5.5)

Posted on Dec 11, 2008 2:57 PM

Reply

Answer 1

iVmichael

Level 6

13,740 points

Dec 11, 2008 3:13 PM in response to richt1

In the Display options do you have Overscan checked ? (do it if not)
And, make sure the Refresh Rate is set to 60 Hertz NTSC

Reply

Answer 2

richt1 Author

Level 1

0 points

Dec 11, 2008 3:20 PM in response to iVmichael

Hi Michael - box checked and set to that ?

Cheers

Reply

Answer 3

Dec 11, 2008 4:44 PM in response to richt1

Hi I have the same problem too, on the same TV. it works sometimes and not others, as far as I can find from reading other posts it's a problem with the MacBook Pro and the software. People with other makes of LCD TV find it not displaying, even though in the display setting it see the TV. I know people with iMacs and MacMini's using Toshibas with no probs. It's really annoying as I've just bought that exact same TV. People using Boot Camp and Windows found that the Display worked fine, so it's a Software thing on the MacBook Pro, I wish Apple would sort this out!!!

One question though, why would you set it to NTSC you live in the UK and we use PAL, so does Australia?

cheers

Phil

Reply

Answer 4

richt1 Author

Level 1

0 points

Dec 12, 2008 2:01 AM in response to philhowes

Not good news then Phil - Hopefully there is a fix soon, I will try again later but I only managed to make mine work once so far.

I think the NTSC was tied into the 60HZ option. Think there was only a option for 50HZ in PAL.

Going to try and borrow one or buy the mini from the local Apple Store on the prevision it works with the TV as I don't fancy wasting 400 quid.

Reply

Answer 5

richt1 Author

Level 1

0 points

Dec 12, 2008 10:37 AM in response to richt1

*Slight update* - wired it all back in again tonight and like last night worked first time. Worked fine for while even worked when I clicked into the Displays Control Panel.

Eventually stopped working when the MacBook Pro went to sleep while I was on the phone, Pro display woke up, the TV screen however just remained Blue, I could move the Mouse cursor off the screen still on to extended desktop display on the TV but of course not see it as the TV screen was blue - the mystery continues.

Cheers

Rich

Reply

Answer 6

Dr. Mark

Level 1

9 points

Dec 12, 2008 12:41 PM in response to richt1

Hi, Guys
I'm using a MacBook Pro with a Samsung 610 52" color monitor for studio video production.
I'm using an adapter to hook up the TV to the Mac via VGA. There are times when I can get the image on the screen, but any time I either start cold or have to change a cable, I get the message "check signal cable." I originally thought the problem was the cable, but changing out three different "known to be good" cables did not resolve. When select system preferences=>displays=>gather windows, the Samsung window with resolution options opens. Nothing as of yet immediately resolves the problem, but if I **** around with it long enough (plug and unplug cables, turn both computer or LCD off and on), eventually I get a picture. And yes, I never had this problem when we were using a Dell Inspiron. Any suggestions or resolutions, please let me know.

Reply