Thanks Britney ...

Did the upgrade to new core / extra on my LinHES6 machine ... everything works well, but I have to edit /etc/php/php.ini as written here before.

Any chance for a status thread here in announcments for the status of the repos? I'm sometimes little confused about the repos status ... version? Differences of standard and testing repos?

Martin

_________________
-------------------------------------------------
KnoppMyth R6 (release)
* ELITEGROUP 915P-A w P4 3,2 GHz 512MB
* ATI x300PCIe
* HD 200 GB SATA / DVD DL(RW)
- DVB-C / Hauppage PVR-500 (2x analog)
- ATI RemoteWonder, CHERRY /wl keyboard/mouse

If it did, it wasn't on purpose. Started to put together a package for 0.24 but it was being a pain. Probably won't have time to look at it again until next week.

_________________
cesman

When the source is open, the possibilities are endless!

Here is an update to my problem. Turned out only the HDHomeRun tuners were ending the recordings after 4 minutes, my 2 DVB cards were working fine. I deleted the HDHomerun tuners, everything works fine. I let it run for a few days without errors.

I found a post on the Silicon Dust support site,
http://www.silicondust.com/forum/viewtopic.php?t=9440
talking about the same kind of problem.

I configured my HDHR tuners back in, they now work better, but there is still a problem. It now fails in Live TV mode (had not tried this before). Getting the status from the HDHR reports no error however.

I plan on posting my problem to their support site and will see what I get.

Here are the results from the HDHR:

hdhomerun_config FFFFFFFF get /tuner0/debug
tun: ch=8vsb:677000000 lock=8vsb ss=57 snq=72 seq=100 dbg=2048-8581-1403
dev: resync=0 overflow=0
ts: bps=19394080 ut=95 te=0 miss=0 crc=0
flt: bps=12869728
net: pps=1223 err=0 stop=0


I looked to see if the MTU (enet frame sizes) were correct (not Jumbo or such, and they are fine, at 1500.

Might be bad HDHR HW. Funny how us software engineers tend to blame software first.

I do want to take this chance to thank everyone for the effort put into LinHES. The solution is solid and it is great to see the effort to get the quality up.

_________________
Jim Haagen-Smit
Auburn, CA

Jim,

I had a weird problem like that with my HDHomerun... I ended up updating the firmware (used a windows machine to do it) which fixed several problems. That was several months ago and I haven't had a problem since...

_________________
Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1

I just upgraded to the latest R6 also. Everything went smooth until I restarted Mythtv frontend. I see the following message



I was not expecting this, but ran mythtv-setup.

After finishing, I started the backend and frontend again, and was told that MythTV wants to upgrade the database for video schema from 1032 to 1038. I selected "upgrade" and things seem to be OK.

Well, I am having an issue I commonly have after upgrading: digital spdif audio is broken. I had finally got it working with the previous version. It is very annoying that the audio settings seem to get clobbered during upgrades. I know it is off-topic, so I'll check the forum to see if anyone else was successful getting it to work again. BTW, I have a Dragon v. 1.0 with the Chaintech AV710 sound card (aka the KnoppMyth reference platform).

After upgrading to 0.24 i was seeing terrible tearing in the video (VDPAU normal, 1080 output).

Adding the following to xorg.conf made it go away (found on the users list):

Section "Extensions"
Option "Composite" "disable"
EndSection

I have 6.0.3 system and have decided to upgrade to 6.0.4 but when I type "sudo pacman -Syu" I get:

warning: provider package was selected (v4l-utils provides libv4l)
looking for inter-conflicts...
warning: removing 'setuptools' from target list because it conflicts with 'python2-distribute'
warning: removing 'libgl' from target list because it conflicts with 'nvidia-utils'
warning: removing 'python' from target list because it conflicts with 'python2'
:: linux-firmware conflicts with iwlwifi-4965-ucode. Remove iwlwifi-4965-ucode? [Y/n] :: linux-firmware conflicts with rt2x00-rt71w-fw. Remove rt2x00-rt71w-fw? [Y/n]
:: python2-distribute conflicts with setuptools. Remove setuptools? [Y/n]
:: mytharchive conflicts with mythmovies. Remove mythmovies? [Y/n]
:: perl-xml-libxml conflicts with perl-xml-libxml-common. Remove perl-xml-libxml-common? [Y/n]
error: failed to prepare transaction (could not satisfy dependencies)
:: sis-dri: requires libgl=7.9
:: netcfg: requires mktemp
:: rt2500: requires kernel26<2.6.29

I don't think I have done anything weird to my system. I haven't run any updates since Cecil posted about not doing so in August.

Any ideas?

Check your /etc/pacman.conf. From that list it looks like you have the testing repos selected which will not get you to 6.04. You will need to change pacman.conf to point to the stable core and extra repos to get 6.04.

Britney

Thanks Britney,

That was exactly what was wrong.

You're the best!

See http://www.mythtv.org/wiki/Release_Notes_-_0.24 under "Major Changes" and "Special Notices & Instructions"

It seems I can't upgrade:






How (If I can?) can I bypass this package and keep the one I have already installed (0.23-5), or install the one in the extra repo (0.23-7) and upgrade normally.

Help please, Thanks

You could try pulling that package directly:

And then upgrading the rest normally.

That's what I get:


Why is it looking for 0.23-6? Is it safe to force?

It looks like the repository meta-data is corrupt, I'm guessing that the file is actually mythtv-contrib-0.23-7-i686.pkg.tar.gz which is what I have, and somehow the sync data got roached.

You may want to open a redmine ticket for this. http://www.linhes.org/bugs/projects/linhes/issues