![]() ![]() ![]() ![]() |
|
Bitfiddler: I get this issue on both my units running 3.17 and 3.18 (and 3.21 too, I downgraded).
At power up you can see the signal through the hdmi. Once its booted up it goes off. Sometimes it just turns off randomly. Fiddling with the connector/cable at the back of the unit gets it working again.
On both units, the AV cable always works fine. I don't think its the hdmi cable as I purchased decent ones from computer dynamics but it is possible that both cables are faulty.
More likely, the connector has a bad joint with the motherboard for a pin that the magic box is using to detect if its connected to the TV. If it is not, it turns off the hdmi signal. This is my current working theory.
Any comments anyone ?
JefWright:Bitfiddler: I get this issue on both my units running 3.17 and 3.18 (and 3.21 too, I downgraded).
At power up you can see the signal through the hdmi. Once its booted up it goes off. Sometimes it just turns off randomly. Fiddling with the connector/cable at the back of the unit gets it working again.
On both units, the AV cable always works fine. I don't think its the hdmi cable as I purchased decent ones from computer dynamics but it is possible that both cables are faulty.
More likely, the connector has a bad joint with the motherboard for a pin that the magic box is using to detect if its connected to the TV. If it is not, it turns off the hdmi signal. This is my current working theory.
Any comments anyone ?
Has this been ongoing or has it become worse?
The hardware is very standard and conservatively engineered. Unless you are supporting the whole MagicTV on its HDMI connector you probably won't have the same hardware flaw on 2 units or on 2 HDMI cables.
I initially got sporadic HDMI negotiation problems (mostly on start-up - with a reasonably modern Sony TV) but I never have a problem with component video. Fiddling with the HDMI connector would sometimes fix it but occasionally I would have to start turning boxes (TV or MagicTV) off and on again.
wklie: HDD spinning during standby is a side effect of the reboot fix in firmware 3.21 and 6.08 beta and beta2.
If one can live with the reboot issue, firmware 3.20 should not cause the HDD to spin during standby.
Bitfiddler: I get this issue on both my units running 3.17 and 3.18 (and 3.21 too, I downgraded).
At power up you can see the signal through the hdmi. Once its booted up it goes off. Sometimes it just turns off randomly. Fiddling with the connector/cable at the back of the unit gets it working again.
On both units, the AV cable always works fine. I don't think its the hdmi cable as I purchased decent ones from computer dynamics but it is possible that both cables are faulty.
More likely, the connector has a bad joint with the motherboard for a pin that the magic box is using to detect if its connected to the TV. If it is not, it turns off the hdmi signal. This is my current working theory.
Any comments anyone ?
PimpMyMagic: I tried updating to 3.21NZ. I wish to retain the modified skip forward/reverse. However the update froze at 45% complete and wouldn't respond to any cancel requests. I had no option but to power cycle it.
It now reports firmware as 3.21NZ but has nothing showing in the Recordings List, won't make any recordings and reports "0" record space available.
Entering rescue mode shows it in the front panel display but it makes no progress from there.
I'm at "Where to next?"
PimpMyMagic: I tried updating to 3.21NZ. I wish to retain the modified skip forward/reverse. However the update froze at 45% complete and wouldn't respond to any cancel requests. I had no option but to power cycle it.
It now reports firmware as 3.21NZ but has nothing showing in the Recordings List, won't make any recordings and reports "0" record space available.
Entering rescue mode shows it in the front panel display but it makes no progress from there.
I'm at "Where to next?"
RingoTB: Go to the MagicTV website and download one of the official firmware version. Then do a Rescue Procedure (from firmware corruption) page 69 in the manual. Once that completes, you can try to update to a patched firmware.
NOTE: When doing the rescue procedure, you MUST have an official firmware version. Trying to do the rescue procedure with a hacked firmware will fail. It will hang with the message "Rescue" displayed but nothing else will happen. You can also find previous firmware versions here
PimpMyMagic: Thanks for that advice Tony. Will 3.21 be accepted as an upgrade from 3.21NZ in rescue mode? I'm not keen to go to the 6.0x Beta range of versions.
I'll give it a go tomorrow morning.
JefWright:
There will be an underlying reason for the upgrade to hang. I had exactly the same thing happen and within a week or two I replaced the HDD (after a whole lot of pain and troubleshooting) and (apart from a small memory leak that makes it slow and laggy and mess up recordings after a couple of weeks without re-booting) my 3600 is going well again. If you don't already have a HDD kicking around you might give some thought now about what disk to buy if you have any further trouble.
|
![]() ![]() ![]() ![]() |