[mythtv-users] Fonts unreadable in GDM/Xorg with Ubuntu
decepticon at gmail.com
Fri Mar 9 06:59:53 UTC 2007
Ok, so I'm pulling my hair out here. mythtv-setup will not
successfully scan any cable channels no matter what I do. I have an
HDHR, which works perfectly with VLC. When I run mythtv-setup, I'm
seeing lines like:
2007-03-09 ... HDHRChan(ffffffff/0): device found at address 192.168.0.103
so I know it's detected.
When I click the scan button, a progress bar skims thru in about a
second, and disappears, leaving a blank channel listing. I have
followed the setup instructions exactly as shown in the wiki, and on
silicondust's website. I have tried to scan every type of cable, and
bcast setting available in the menu, all to no avail. Please, if you
know the magic spell I need to cast, help me out. I'm ready to watch
some TV now.
On 3/8/07, jason maxwell <decepticon at gmail.com> wrote:
> those lines did the trick. thank you.
> now i just need to get my optical audio to work, and get my HDHR to scan.
> ...almost there...
> On 3/8/07, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> > On 03/08/2007 05:22 PM, Willy Boyd wrote:
> > > On 3/8/07, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> > >
> > >> I wasn't saying your approach is wrong, only that there are more details
> > >> at the link provided.
> > >>
> > >> ...
> > > Understood. And it's a great point -- I should have taken time to
> > > clarify those options would only, potentially, help with an NVIDIA
> > > card and a recent proprietary driver. Someone less patient could come
> > > along and see that and think it's the end-all, be-all way :)
> > >
> > I'm also not saying it's your responsibility to provide the extra info.
> > You did answer the question--which means you've volunteered your time to
> > contribute--so you've done A Good Thing (and, thanks for contributing,
> > BTW). I just wanted the additional info to be there along with yours.
> > > I've never liked the mathematical dance that DisplaySize made me go
> > > through to get right at 100dpi; it always seemed like trial and error.
> > > Had to go through it again when I got a new display and switched
> > > resolutions to 720p. So I was pretty excited to get to specify it
> > Yeah. Funny, though, with Myth 0.21, you'll stop specifying DPI and go
> > back to DisplaySize. :) In 0.21, the DPI is irrelevant, but the aspect
> > ratio remains important, and although you can specify the aspect ratio
> > with DPI, it requires the inverse mathematical dance that you used to do
> > to get DPI with DisplaySize (unless you have square pixels--in which
> > case it's just "pick a number", but determining if you're using square
> > pixels requires some math, so...). With DisplaySize, specifying aspect
> > ratio is as easy as "pick a number and multiply by aspect."
> > (Technically, if you've properly specified a 100DPI pitch with proper
> > aspect ratio, you can continue to use the same DPI setting and--since
> > DPI is irrelevant to Myth 0.21--Myth won't care/notice. However, by
> > changing the pitch to an appropriate value, you can improve the look of
> > things like xterm and Firefox and ...)
> > Mike
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
More information about the mythtv-users