I just finished restoring my mythbox today - I fried a motherboard following a CPU fan failure, and had some pretty radical upgrades as a result:

Duron 1.2 --> Athlon XP+2800
onboard nvidia --> PCI nvidia MX440SE tv-out (s-video)

good news is, I was able to keep the capture card (leadtek 2000) and no damage to HD. I also upgraded from R4V2 to R4V4 (just one day ahead of R4V5 release...)

The "automatic upgrade" worked flawlessly, but now I'm looking at upgrading to .16 via deb install... but I don't know what the "auto upgrade" chose for me. Am I using i586 or i686? Am I using XV? How can I determine this?

This should give you a general template for how to determine this kind of information

Thanks for the tip.

It shows all the different myth modules as version i586 0.16-1 on my box.
I always thought I had installed i686 since I started with R4V4, and a few updates since. This part of the install get me confused all the time.

Anyway, what can I do now to safely install the i686 myth modules?

I use a ATI remote, do I need lirc? xvmc?

Thanks
[/i]

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20

Presumably you meant i586 0.15-1

You can delete all the myth modules ("man apt-get" for details) and then do the install with the i686 modules. However the rest of your box is probably i586 anyway...

no.

I have it right in front of me while I type, they are all showing as myth***-i586 0.16-1installed: No available version in archive

I updated the box to R4V5 yesterday using a verified iso burned to cd, fixed a couple of small problems (why dont I live in California, the timezone bug at install messed a few things again).

I fixed all of them reading the forum, but as I said, since the first day I have problems clearly understanding the sequence and exact procedure to install i686 together with the nvidia drivers.

When you say the rest of my box is i586 you mean Linux itself, the kernel? As I understand, it is not configured the best way to utize all the processing power of my CPU.

How can I change that?

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20

I didn't have the advantage of finding a "howto" on the forums to fix the timezone issues (I'm in central daylight) but I found an easy solution - in both of the tables "recorded" and "program" use a bit of sql:

With "program", I got duplicate key errors, and had to delete the primary key, run the query, then restore the primary key (on chanid, starttime)

This simply subtracts two hours from the specified fields. To add time, use "date_add".

Note that all of this is a lot easier if you install phpmyadmin first

The auto upgrade doesn't choose which package to install for you. The Duron is a i686 class processor, thoe are teh debs you should install. You don't need XvMC for your remote.

_________________
cesman

When the source is open, the possibilities are endless!

thanks for making it clear I need i686 and no xvmc.

should I just do , after closing mythtv-backend, mysql and gdm?

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20

why does everyone have such a hard time with the timezone thing??? I know it won't take the first time around. big deal just complete it the second time and all is well. I really don't get the big todo. it even states in the documentation that it won't work the first time. I've done umpteen installs and never had to do any "fixes" for the timezone other than actually completing the timezone config the second time it is shown after reboot.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

If you have 0.15.1 installed and you want to install the 0.16 debs, then you need to read the instructions on installing the 0.16 debs.

_________________
cesman

When the source is open, the possibilities are endless!

I have i586 0.16-1 version for myth after the auto-upgrade and want to go to i686 0.16-1

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20

I had problems with it the first time because the restore happened before I could fix the TZ. The hard part is knowing/recognizing the right time to stick your fingers into the mechanism.

Ah, that was the missing bit of info. I'd say make another backup, rerun the auto upgrade, and be sure to select i686...

my timezone issue was that I had restored the data before allowing the timezone to correct itself (I think) which resulted in my "recorded" table being populated by entries all two hours off. As a result, mythfrontend couldn't find any nuv files which matched the timestamps in the database.

It's probably a matter of my not reading the all of the directions fully and completely, I know...

tjc said:

but cesman said:

Am I stuck with those i586 debs?

Xsecrects, you said:
The important word here is everyone.

bshroyer, your are not alone. Same thing happened to me. The database restored itself before I had a chance to correct the timezone. I fixed it by manually editing all the filenames to match the database.

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20