I have tried everything possible. The funny part is I'm not new to linux either but this mysql problem has happened with my knoppmyth install and when I tried to use wilson.net's fedora install. It keeps telling me the same thin over and over. Cant connect to master please check your settings. I have used the 127.0.0.1, localhost, 192,168.0.101 ip all of which are valid and pingable. The reason I choose knoppmyth was in the hopes it would install everything for me and get this thing up and running but I have the same error.

I have figured a work around for it and that is to run everything as the root user and then everything connects and records.

I changed the mysql privilages with these commands:
$ mysql -u root mythconverg
mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv";
mysql> flush privileges;

But still nothing. Anyone have any suggestions?

I'm assuming that you're trying to do a frontend-only install. I'm tried for hours tonight to do the same thing and got the same problem. After booting off the CD, I successfully set the timezone and time, it kicks into mythtv-setup, where I pick a language. Then it tells me to check my database settings because it can't contact the master database. The settings are fine, and when I go through two screens verifying settings, it kicks me out to knoppix.

A buddy of mine figured out that mysql isn't running locally on the frontend machine (I'm not entirely certain that it should be), but after getting kicked out to knoppix, I manually started (as root) mysql on my frontend machine with:

/etc/init.d/mysql start

Checking with "ps -ef | grep sql", I saw that half-a-dozen mysql processes were running. Then I started mythtv-setup, and it didn't complain about not being able to contact the master database and it allowed me in the "General" section to set up the IP address of my frontend and backend machines. But the problem now is that it won't save the settings for the new ip addresses. Every time I go back into the "General" pages, the ip addresses are set back to 127.0.0.1. Because I was able to get through mythtv-setup once, it does allow me to kick off mythfrontend, but when I try to watch tv or do anything, it says that it can't contact the backend.

My guess is that for some reason, the cd doesn't kick off mysql on the frontend machine, which doesn't allow you to successfully run mythtv-setup. And I think that manually running mythtv-setup instead of having whatever process in the CD boot run it is causing the manual run to not be able to save the setup to ram disk. Just my newbie speculations.

BTW, andyem, I also did the "grant all ..." commands inside mysql on the master backend server and it didn't help.

Anyone been able to install, configure, and run knoppmyth R5B7 as a CD boot frontend successfully?

Doh! After tossing and turning for 5 hours about this problem, I figured out at 5:00 am that my problem was that when myth complains that it can't connect to the backend and asks me to check my database settings, I just needed to change my "hostname" setting to the ip address of my backend from 127.0.0.1. Didn't need to start up mysql or anything else on my frontend. Now my front end can talk to my backend and I can watch tv and do everything.

The only thing I can't figure out (and I'm not certain if it's even possible when I'm just booting a frontend only off CD) is install a remote. Anyone know if this is possible?

andyem, I'm osrry, but in reading your post again, it sounds like you're installing the frontend on disk and not just trying to get it to run off a CD. Sorry if my post was distracting.

My first crack at Myth19 was on a fedora4 box. I used the knoppmyth frontend just fine; after changing the settings at boot to point to my backend. It worked great.

I changed capture cards and everything fell apart. I then used KnoppMyth autoinstall and started fresh, but the HOWTO guilds were no longer applicable to correct KNoppmyth. I'm going to work on changing backend so that a frontend can connect to it. MythWeb might work then too.

Oh. Do not start mysql on front end as this was pointed out to confuse the recordings, scheduler and everything. It may seem like that works, but it might just take a few days to realize that was not it.

Ive actually just reinstalled yet again and everything seems to be working on the mysql front. WHo knows what happened lol