Problems During Install MD5
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired
query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:c1e490dcfb8334abee398507865c08a0' in /var/www/mythdora/html/includes/cache.inc on line 26.
- user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired
query: UPDATE cache_filter SET data = '<p>First off, I have remedied most of this, so this is mostly informational.<br />\nI have a dedicated FE/BE which I upgraded from MD4 to MD5 by backing up my database and doing a fresh install then restoring the database, and by far the easiest MythTV upgrade I have had for a while. <br />\nI have a Frontend that is connected to my HDTV, and I recently moved from a tower next to the entertainment center to an HTPC case, when I got the case I wired it into the entertainment center to hide the wires the downside, is taking the box back to my office for maintenance is a pain, So when it came time to upgrade that one, I thought I would take over the TV and upgrade right there a frontend only install is fairly quick and painless. And that’s where the problems came in. <br />\nFirst but really a problem on the installers part, The TV is very picky about its resolutions, it doesn’t seem to have the standard crutch resolutions, doesn’t like 640x480, but prefers 720x400, I cant remember all the resolutions it displays, but the 2 that get used for me are 720x400 (console and text screens) and 1920x1080 everything else, so when I do the Gui install option on the DVD, and it tries to load anaconda\'s gui, the X session starts with a mouse curser in the middle of the screen and then a few seconds later a copy of the middle cursor shows up on the upper left hand corner, and X is essentially frozen. I gave up and figured I would install text mode instead, <br />\nI reboot and try again in Text mode install, I successfully select all the options, the files copy, the cd gets ejected I restart, and I expect the nice gui config to meet me on the other side, I get a blue and red setup config in console mode, I attempt to setup the firewall options and the other things, but the setup that shows up is more OS centered then the Mythdora config, when I close it I am dropped back into console, so I log in as root and run init 5. X loads the mythdora config grey box appears, and I am able to connect to my backend and TV shows are working, I restart the machine to test that it starts properly, and I go back to the text blue and white setup program. So I look at my inittab and its set to 3. I change it to 5, and restart again, and run into a similar X freeze as I did when I tried to install in GUI mode. but if I change to init3 to close it and then go back to init5 X starts up at proper resolution and works fine, <br />\nAt this point I just felt maybe installing in text mode caused all the problems, so I give in, and pull my box out of the entertainment center pull it into my office and hook it all back up, and re-install MD5 in gui mode because I have similar hardware in my backend, but none of these problems appeared for that one. Install went normal all screens worked, no freezes, but my lcd monitors, have all the typical resolutions and max res of 1440x900, I get everything to what I consider working using all the defaults from the CD even then nVidia 6 series drivers, I take it back out to the television, it starts up, and as it starts it even loads the gui splash screen as it loads at 1920x1080, but when it comes to the MD desktop to load it freezes again, mouse cursor in the middle and another mouse cursor in the corner inside of a blue box, but I found that if as soon as I see that if I get on the keyboard and switch to ctrl+alt+f1 then back to ctrl+alt+f7 I catch Myth loading still prescaling images at 1920x1080 and everything seems okay from that point. Since I don’t normally restart, it’s more of an annoyance at this point then anything so that is why it’s more for your info.<br />\nSince the X loading problem only seems to happen on my TV, and not duplicatable on regular monitors I am guessing it has more to do with the limited resolutions of my television then anything else.<br />\nTelevision is a Westinghouse TX-42F430S 42inch 1080p connected via the VGA Port<br />\nfront end is, <br />\nAMD 64 3200+ 754<br />\nECS RS482-M754 <br />\n-1GB PC3200 ram (2x512)<br />\n-onboard video disabled<br />\n-onboard sound in use<br />\n-onboard NIC<br />\nEVGA- GeForce 6800XT 256mb card connect with DVI->VGA connector to the monitor<br />\n40 GB 2.5 inch PATA hard drive<br />\nATI Remote Wonder RF</p>\n', created = 1369316656, expire = 1369403056, headers = '', serialized = 0 WHERE cid = '1:c1e490dcfb8334abee398507865c08a0' in /var/www/mythdora/html/includes/cache.inc on line 109.
Submitted by witmore1 on June 3, 2008 - 7:39am
First off, I have remedied most of this, so this is mostly informational.
I have a dedicated FE/BE which I upgraded from MD4 to MD5 by backing up my database and doing a fresh install then restoring the database, and by far the easiest MythTV upgrade I have had for a while.
I have a Frontend that is connected to my HDTV, and I recently moved from a tower next to the entertainment center to an HTPC case, when I got the case I wired it into the entertainment center to hide the wires the downside, is taking the box back to my office for maintenance is a pain, So when it came time to upgrade that one, I thought I would take over the TV and upgrade right there a frontend only install is fairly quick and painless. And that’s where the problems came in.
First but really a problem on the installers part, The TV is very picky about its resolutions, it doesn’t seem to have the standard crutch resolutions, doesn’t like 640x480, but prefers 720x400, I cant remember all the resolutions it displays, but the 2 that get used for me are 720x400 (console and text screens) and 1920x1080 everything else, so when I do the Gui install option on the DVD, and it tries to load anaconda's gui, the X session starts with a mouse curser in the middle of the screen and then a few seconds later a copy of the middle cursor shows up on the upper left hand corner, and X is essentially frozen. I gave up and figured I would install text mode instead,
I reboot and try again in Text mode install, I successfully select all the options, the files copy, the cd gets ejected I restart, and I expect the nice gui config to meet me on the other side, I get a blue and red setup config in console mode, I attempt to setup the firewall options and the other things, but the setup that shows up is more OS centered then the Mythdora config, when I close it I am dropped back into console, so I log in as root and run init 5. X loads the mythdora config grey box appears, and I am able to connect to my backend and TV shows are working, I restart the machine to test that it starts properly, and I go back to the text blue and white setup program. So I look at my inittab and its set to 3. I change it to 5, and restart again, and run into a similar X freeze as I did when I tried to install in GUI mode. but if I change to init3 to close it and then go back to init5 X starts up at proper resolution and works fine,
At this point I just felt maybe installing in text mode caused all the problems, so I give in, and pull my box out of the entertainment center pull it into my office and hook it all back up, and re-install MD5 in gui mode because I have similar hardware in my backend, but none of these problems appeared for that one. Install went normal all screens worked, no freezes, but my lcd monitors, have all the typical resolutions and max res of 1440x900, I get everything to what I consider working using all the defaults from the CD even then nVidia 6 series drivers, I take it back out to the television, it starts up, and as it starts it even loads the gui splash screen as it loads at 1920x1080, but when it comes to the MD desktop to load it freezes again, mouse cursor in the middle and another mouse cursor in the corner inside of a blue box, but I found that if as soon as I see that if I get on the keyboard and switch to ctrl+alt+f1 then back to ctrl+alt+f7 I catch Myth loading still prescaling images at 1920x1080 and everything seems okay from that point. Since I don’t normally restart, it’s more of an annoyance at this point then anything so that is why it’s more for your info.
Since the X loading problem only seems to happen on my TV, and not duplicatable on regular monitors I am guessing it has more to do with the limited resolutions of my television then anything else.
Television is a Westinghouse TX-42F430S 42inch 1080p connected via the VGA Port
front end is,
AMD 64 3200+ 754
ECS RS482-M754
-1GB PC3200 ram (2x512)
-onboard video disabled
-onboard sound in use
-onboard NIC
EVGA- GeForce 6800XT 256mb card connect with DVI->VGA connector to the monitor
40 GB 2.5 inch PATA hard drive
ATI Remote Wonder RF
|
