| LinHES Forums http://forums.linhes.org/ |
|
| can't run mythfrontend http://forums.linhes.org/viewtopic.php?f=14&t=9471 |
Page 1 of 1 |
| Author: | DrewCS [ Mon Apr 03, 2006 10:39 pm ] |
| Post subject: | can't run mythfrontend |
I just did an update to R5A30.1, went through all the inital setup just fine. Then when I got to mythtv-setup, I set the ip address and the database stuff (all default) and then it is supposed to go into the rest of the set up but it just quits back to the desktop. I found that it gives an error about not being about to connect to the backend but it is running, and if I log in as root then I can load the frontend and it can connect to the database. I can't use my remote as root, nor is any sound working. Any thoughts on how to fix this? |
|
| Author: | tjc [ Mon Apr 03, 2006 11:16 pm ] |
| Post subject: | |
Any reason you didn't go to R5B7? You probably need to look at the logs to get more specific details about why it's falling over, then fix that symptom, and finally rerun the setup. For details on the part last, look for posts by Cecil or cesman which mention the touch commnad. |
|
| Author: | DrewCS [ Tue Apr 04, 2006 3:42 pm ] |
| Post subject: | |
ok I now tried to upgrade to R5B7 since I was not having any luck before...and it is giving me the same error of not beging able to connect to the database and I know it is running. Code: 2006-04-04 17:33:59.906 Using runtime prefix = /usr
2006-04-04 17:33:59.962 New DB connection, total: 1 2006-04-04 17:33:59.965 Unable to connect to database! 2006-04-04 17:33:59.965 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '127.0.0.1' (111) 2006-04-04 17:34:00.023 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2006-04-04 17:34:00.076 Unable to connect to database! 2006-04-04 17:34:00.077 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '127.0.0.1' (111) and it repeats this over and over, anyone know how to fix this? I don't think that is the correct port number. How do I change it? |
|
| Author: | DrewCS [ Tue Apr 04, 2006 7:06 pm ] |
| Post subject: | |
well I fixed my problem, but now I have another one...now my soudn does not work. Code: root@mythtv:/home/mythtv# cat /proc/asound/pcm
00-00: Intel ICH : SiS SI7012 : playback 1 : capture 1 00-01: Intel ICH - MIC ADC : SiS SI7012 - MIC ADC : capture 1 root@mythtv:/home/mythtv# any ideas? I had sound before I upgraded |
|
| Author: | tjc [ Tue Apr 04, 2006 7:54 pm ] |
| Post subject: | |
Check the setting stuff in the frontend and try using a different device. There have been several "no sound" issues which just need some configuration tweaking. A search for the quoted phrase should turn up the relevant discussions. BTW - More hardware details would be really useful... Type of capture card, type of MoBo, type of sound card, ... |
|
| Author: | ahronzombi [ Sat Apr 22, 2006 1:16 pm ] |
| Post subject: | |
but how did u fix 2006-04-04 17:33:59.906 Using runtime prefix = /usr 2006-04-04 17:33:59.962 New DB connection, total: 1 2006-04-04 17:33:59.965 Unable to connect to database! 2006-04-04 17:33:59.965 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '127.0.0.1' (111) 2006-04-04 17:34:00.023 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2006-04-04 17:34:00.076 Unable to connect to database! 2006-04-04 17:34:00.077 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '127.0.0.1' (111) im having the same prob bob |
|
| Author: | mjl [ Sat Apr 22, 2006 5:54 pm ] |
| Post subject: | |
Hi, Good hint tjc, a few hardware details do help to understand issues. The db error often will occur with an upgrade because of the ip. Go through the mythtv-setup, general I think and put in the 127.0.0.1 default. You may have to /usr/bin/mythbackend restart See if that helps. As for the audio issue, you cac try as root to run alsaconf and the alas mixer. Actually do it in reverse to see if it has discovered the sound card. Some of the SIS stuff acts a bit "funky" so it may be a muted control. Mike |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|