Mailing List Archive

upgrade from V 31 to V 32
Hi

I'm preparing to upgrade from V 31.0 to V 32.0 (xubuntu 20.04)

Will this require me to reload a backed up database? Or will it do it
all automatically?

I am using MythTV Control Panel which allows me to select the 32.0 repo
and then do an update.

A long time ago I did an upgrade using Mythbuntu Control Panel from 26.0
to 27.0 and if I recall correctly I did not need to do anything else but
I may be wrong about that.

-Paul
Re: upgrade from V 31 to V 32 [ In reply to ]
On Sat, 12 Mar 2022 17:50:54 +1300, you wrote:

>Hi
>
>I'm preparing to upgrade from V 31.0 to V 32.0 (xubuntu 20.04)
>
>Will this require me to reload a backed up database? Or will it do it
>all automatically?
>
>I am using MythTV Control Panel which allows me to select the 32.0 repo
>and then do an update.
>
>A long time ago I did an upgrade using Mythbuntu Control Panel from 26.0
>to 27.0 and if I recall correctly I did not need to do anything else but
>I may be wrong about that.
>
>-Paul

Whenever MythTV updates the database schema, it automatically does a
database backup first. But it uses the default settings for the
backup location, as set in the "DB Backups" storagegroup. So if your
normal backups from /etc/cron.weekly or /etc/cron.daily go somewhere
else, you need to set that storagegroup properly in mythtv-setup
before doing a database schema upgrade.

The usual way to go about doing a v31 to v32 upgrade is just to change
the /etc/apt/sources.list.d/ file that is pointing to v31 to now point
to v32. In my case:

root@mypvr:/etc/apt/sources.list.d# cat mythbuntu-ubuntu-31-focal.list
deb http://ppa.launchpad.net/mythbuntu/31/ubuntu focal main
# deb-src http://ppa.launchpad.net/mythbuntu/31/ubuntu focal main

So I need to rename mythbuntu-ubuntu-31-focal.list to
mythbuntu-ubuntu-32-focal.list (not necessary but a good idea) and
change all references to 31 in that file to 32. Then shut down
mythfrontend and do:

sudo systemctl stop mythtv-backend
sudo apt update
sudo apt full-upgrade
sudo apt autoremove

So now you have all the v32 packages installed and the v31 ones
removed. Next, you need to make sure that the database schema upgrade
happens. It is best to do that by running mythtv-setup. It will ask
for permission to do the schema upgrade and will tell you that it is
doing a backup and where it is storing it. On exit from mythtv-setup,
let it restart mythbackend, or do that yourself:

sudo systemctl start mythtv-backend

Then run mythfrontend. If you are using any plugins that have their
own database tables (such as mythmusic), you will then be asked to
allow the schema update to happen on those tables, and another
database backup will happen before that is done. Once mythfrontend is
running normally, the v32 upgrade is complete.

Hopefully, the above is pretty much what MCC will do if you ask it to
perform the upgrade. But I have not used the new MCC since it was
refreshed by its new maintainers.

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: upgrade from V 31 to V 32 [ In reply to ]
On Sun, 13 Mar 2022 11:10:15 +1300, you wrote:

>I successfully updated to v32 following Stephen's instructions but I
>cannot run mythtv-setup via a VNC session to my headless backend.
>
>I will have to wait until I am fit and mobile enough (after an operation
>on my ankle) to connect it to a screen and keyboard.
>
>Rob

To get VNC to work on a headless machine, you need to configure it
with the dummy video driver. I have been playing with this on my
"lith" PC (Ubuntu 20.04) and have got it to work. You install the
xserver-xorg-video-dummy package, and use an /etc/X11/xorg.conf file
that looks something like this:

Section "ServerLayout"
Identifier "DefaultLayout"
Screen "Screen1"
EndSection

Section "ServerFlags"
Option "DefaultServerLayout" "DefaultLayout"
EndSection

Section "Monitor"
Identifier "Dummy1"
HorizSync 28.0-80.0
VertRefresh 48.0-75.0
# https://arachnoid.com/modelines/
# 1920x1080 @ 60.00 Hz (GTF) hsync: 67.08 kHz; pclk: 172.80 MHz
Modeline "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084
1118 -HSync +Vsync
# 1920x1080 @ 50.00 Hz (GTF) hsync: 55.60 kHz; pclk: 141.45 MHz
#Modeline "1920x1080_50.00" 141.45 1920 2032 2232 2544 1080 1081
1084 1112 -HSync +Vsync
EndSection

Section "Device"
Identifier "Device1"
Driver "dummy"
VideoRam 256000
EndSection

Section "Screen"
DefaultDepth 24
Identifier "Screen1"
Device "Device1"
Monitor "Dummy1"
SubSection "Display"
Depth 24
Modes "1920x1080_60.00"
EndSubSection
EndSection

My email client wraps long lines - the Modeline lines are all on one
line.

You can use the modeline calculator on the URL above to set up a
screen definition that matches your actual monitor if you want that
rather than 1920x1080. My monitor is 1920x1200.

I think it will work also if you set up a "Screen0" definition that
works with your real monitor when that is plugged in, and set
"Screen0" ahead of "Screen1" in the "Serverlayout" section. Then it
should connect to the real monitor if it is present, and will create
the dummy monitor as a second screen. If you do that, when the real
monitor is connected, it will be DISPLAY=:0.0 and the dummy monitor
will be DISPLAY=:0.1. From

In any case, you can keep two xorg.conf.xxx files and just copy the
one you want for the next boot to be xorg.conf via ssh. These are the
xorg.conf sections I use for my real screen, using my Nvidia GT1030
card:

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "DELL 2707WFP"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce GT 1030"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Via SSH, you can see what your screens are using xrandr. I have
several PCs on an HDMI KVM switch, and when the switch is set to a PC
other than lith, lith's video card sees no monitor connected and VNC
will not work on the main screen, but if I start a second VNC server
on the dummy screen, that works. This is what xrandr shows in that
situation:

stephen@lith:~$ DISPLAY=:0.0 xrandr
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected primary (normal left inverted right x axis y axis)
stephen@lith:~$ DISPLAY=:0.1 xrandr
xrandr: Failed to get size of gamma for output default
Screen 1: minimum 320 x 240, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
1920x1080 60.00*
1680x1050 70.00 60.00
1400x1050 70.00 60.00
1600x900 60.00
1280x1024 75.00 60.00
1440x900 60.00
1400x900 60.00
1280x960 60.00
1368x768 60.00
1360x768 60.00
1280x800 60.00
1152x864 75.00 70.00 60.00
1280x720 60.00
1024x768 75.00 70.00 60.00
1024x576 60.00
960x600 60.00
832x624 75.00
960x540 60.00
800x600 75.00 72.00 60.00 56.00
840x525 70.00 60.00
864x486 60.00
700x525 70.00 60.00
800x450 60.00
640x512 75.00 60.00
720x450 60.00
700x450 60.00
640x480 75.00 73.00 60.00
684x384 60.00
680x384 60.00
640x400 60.00
576x432 75.00 70.00 60.00
640x360 60.00
512x384 75.00 70.00 60.00
512x288 60.00
416x312 75.00
480x270 60.00
400x300 75.00 72.00 60.00 56.00
432x243 60.00
320x240 75.00 73.00 60.00

To start a second copy of the x11vnc server via ssh, I do this command
as root:

/usr/bin/x11vnc -auth guess -forever -loop -noxdamage -repeat -rfbauth
/etc/x11vnc.pass -rfbport 5901 -shared -noxrecord -display :0.1 &

(all one line)

The second VNC server will run on port 5901 instead of the default
5900 which is in use by the first x11vnc server on the :0.0 display
that is started automatically at boot time.

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: upgrade from V 31 to V 32 [ In reply to ]
How is everyone finding the update to V32

My backend is still on Ubuntu 18.04 and I'm a bit wary of a major update
due to some of the DVB-S tuner's I'm currently using.

I'll can see there is a V32 build for 18.04 so I might just give it a whirl.

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
Re: upgrade from V 31 to V 32 [ In reply to ]
Mine went very smoothly.
I didn't worry about a backup as I wouldn't have much to sort out if I lost
it.

On Wed, 23 Mar 2022, 5:55 pm OpenMedia Support, <support@openmedia.co.nz>
wrote:

> How is everyone finding the update to V32
>
> My backend is still on Ubuntu 18.04 and I'm a bit wary of a major update
> due to some of the DVB-S tuner's I'm currently using.
>
> I'll can see there is a V32 build for 18.04 so I might just give it a
> whirl.
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz@lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
Re: upgrade from V 31 to V 32 [ In reply to ]
On Wed, 23 Mar 2022 17:54:55 +1300, you wrote:

>How is everyone finding the update to V32
>
>My backend is still on Ubuntu 18.04 and I'm a bit wary of a major update
>due to some of the DVB-S tuner's I'm currently using.
>
>I'll can see there is a V32 build for 18.04 so I might just give it a whirl.

I have found a couple of niggles with the MythCenter-Wide 1.9 theme. I
was using short timestamps in "Wed 23/03" format, but they do not fit
on the programme listings screen now due to the new percentage
watched/percentage recorded field just to the left. So I had to
change to "23/03" format, which works there, but elsewhere (such as
the Guide screen) it is a pain not having the day of the week. And on
my test box, I have some tuner numbers >100, and they do not display
unless I edit the theme to make a wider field for them. I do like the
new percentage fields though - they are quite useful.

I think you will be needing to upgrade from 18.04 within a year anyway
- it goes into ESM status at the end of April 2023, I think, so only
security updates after then and you have to have an Ubuntu Advantage
subscription to get them. And 20.04 is significantly better than
18.04, especially the systemd stuff, so it is well worth upgrading.

So what tuners are you thinking will be a problem? If they are kernel
supported, they should still be kernel supported in all later kernels.
So do you have to compile drivers for them?

_______________________________________________
mythtvnz mailing list
mythtvnz@lists.ourshack.com
https://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/