[mythtvnz] Storage drive won't mount
Stephen Worthington
stephen_agent at jsw.gen.nz
Tue Apr 23 06:13:50 BST 2013
On Tue, 23 Apr 2013 06:16:40 +1200, you wrote:
>> And what sort of TV? Some TVs have updated firmware available to fix
>> problems like that.
>
>Panasonic Viera
The first digital TV I used with MythTV was a Panasonic Viera with the
lower "HD Ready" resolution. It was not a good experience, as its
EDID data was actually incorrect in places and I never found any way
to turn off the silly overscan it did. So when I wanted to upgrade to
a "Full HD" 1920x1080 TV, I did some research and found that Sony TVs
at the time had a reputation of being much more well behaved. I got a
Sony Bravia KDL-32V5500, which I have been pretty happy with. When
connected to a PC, it does not do overscan, and I was able to remove
all my xorg.conf tricks and just let the EDID data do its job. The
only real complaint I have about the Sony is that when it turns on its
screen, or when it changes screen mode, it displays overlayed data for
quite some time that interferes with seeing the picture. I have not
found any way to turn off the overlays, but I can get rid of them
manually with the remote by pushing the "Options" button twice.
As to Panasonics, I have just checked the old boot partition I was
running on when I had mine, and I still seem to have various xorg.conf
files there that I used with it. Everything has moved on since then
(TVs, Nvidia video cards, Nvidia drivers and X itself), but they might
be of some help to you.
I did some experiments with my mother's MythTV box. This has an
identical TV to mine, and a builtin Nvidia 8200. I tried booting with
the TV off, unplugged from the power, and unplugged from the HDMI at
the PC. It rebooted just fine with the TV's mains switch off, and
with the TV completely unplugged from the power. It rebooted without
any display when I unplugged the HDMI at the PC. From that I think
the PC must be remembering the EDID data even when it is unable to
read it from the TV. But when the HDMI cable is unplugged, it assumes
that it might be getting a different device to talk to and then
forgets the existing EDID data.
After booting with the HDMI unplugged, I plugged in the HDMI again,
and still got no display. So I logged in as root via ssh and found
that the display manager (lightdm) was not running. I did a "start
lightdm" command, and the display started properly. So in your case,
instead of doing a "poweroff" or "reboot" command, you might like to
try "start lightdm" and see what happens. First check which display
manager you have configured - there is a choice between installing
lightdm and gdm as part of the Mythbuntu installer, so run a "ps -e |
grep dm" command while the display is working and see which one is
running. If you are running gdm, then the command is "start gdm".
More information about the mythtvnz
mailing list