First off thanks (again) to the development team and to brfransen for the great work. My installs went OK on all my machines using both pacman and iso (just to try different methods...). One consistent nvidia problem however (similar in 8.5). I am using older nvidia cards (9400 in master backend, Zotac minis elsewhere) none of which are supported by the current installs. After the reboot, systems in a constant reboot state - ssh in and downgrade driver to 340. All is well...

_________________
nbdwt73

Thanks for the information regarding older nvidia cards. I fall into this category as well.

So it's possible to ssh into the box while it's in this state?

Yep... then just

sudo VGACARDTYPE="nvidia-340xx" xconfig.sh

_________________
nbdwt73

Great!! Thanks for the heads up.

One correction - I said "constant reboot state". I should have said "constant frontend reboot state". The machine is not rebooting...

_________________
nbdwt73

i updated my 8.5.2 box on friday, the upgrade went smoothly. as warned, i needed to delete the /etc/ssl/certs/ca-certificates.crt file, which i did. no warning was received for the ParserDetails.ini file.

i have successfully recorded programs and removed commercials from the recordings.

one item of note that i have started to notice prior to this upgrade is that when running /usr/LH/bin/lh_system_backup_job manually in a shell, this line in the script:



will error out, complaining that /home/vncsvc does not exist. it does not, and i am assuming it does not exist because i do not have tigervnc installed. i removed the reference to /home/vncsvc from the script prior to the upgrade, but the script was replaced as part of the upgrade.

it was very nice to get kodi updated to version 18. i have been reading the issues logs and can see that knappster and brfransen put some effort into working on this package.

the kodi upgrade went smoothly. i did, however need to update the kodi-addon-visualization-waveform from version 1:1 to version 1:2 (available on the archlinux aur)

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6

welner, thanks for mentioning the /home/vncsvc. I will push a fix for that.

nbdwt73, what driver does xconfig.sh install without forcing 340xx? And what is the device ID it finds?

It sounds like the ISO boots on those machines and you do get a GUI. Is that correct?

Sorry for the delay - am on a business trip. From memory I don't remember if I even looked to see what driver was installed - I just saw the rebooting... I do know that there were many errors related to the driver version and I then just installed the version that I know works - 340.

Yes the GUI works fine. No issues noted until the driver issue showed up... I will run xconfig.sh when I return to see what happens...

_________________
nbdwt73

That is very odd that the ISO GUI works but the install doesn't until you force the driver to 340.

When I was at R8.5 I had Kodi installed.

I just noticed that after I upgraded to R8.6 the previous version of Kodi was removed, but the latest version was not installed. Was this by design or an oversight?

Just wondering. I think I would have preferred to leave the earlier version installed or an option to upgrade to the latest Kodi package.

If Kodi was installed by pacman then it should have updated it to 18.1. I just tested in a VM from R8.5.2 to R8.6 and Kodi stayed installed and was upgraded. Can you check the pacman log and see if there is any error around the kodi 18.1 install? The only other thing I can think of is if systemconfig ran and kodi wasn't installed through the Service Menu.

The previous version won't run in R8.6 due to old deps.

I did find an error

So something strange happened there. Your comment


I'm sure that I installed the previous version just using pacman from the command line and not using the service menu. So that was probably the cause. I installed it using the menu today.
Thanks

That error shouldn't matter. But it looks like systemconfig did remove it because it wasn't marked in the db as being installed. You can install it outside the service menu and then the next time you go into the programs sections of the service menu the db would get updated that it was installed.

That's what I figured. I installed it from the menu so it should no longer cause any problems.
Thanks!

i had the opportunity to burn a DVD for a family member, and discovered that the process would immediately fail with an on screen message indicating that there were "no log files to show"

the myth messages log indicated that it could not access archive, log, or work directories.

it appears that the /myth symlink, which i believe was kept for legacy purposes was deleted with this release or possibly an earlier release (i haven't burned a dvd in quite a while).

the fix was to go into service -> mythtv setup -> setup -> media settings -> archive file settings

and change the setting for "myth archive temp directory" from /myth/tmp/ to something that exists

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6