First off a BIG THANK YOU to all the guys, people, devs that keep making this happen!
A couple of questions / remarks:
DISCLAIMER: these questions / remarks are intended to be positive and helpfull (if not to myself then ... )
They have been gathered and verified over multiple installs.
However, if fellow LinuxMCE users find these to be incorrect please do post your findings.MAIN QUESTION: How do fellow LinuxMCE users configure MythTV for first time use? (mythtv-setup)
Today, after many, many, many retrials I finally managed to get 0810 beta2 installed on my M3N78-EM (asus) mobo.
- As each Kubuntu install imperatively creates 'a' first user (I called mine linuxmce :-) )
how does LinuxMCE install treat this user? Or, does LinuxMCE install create a new user to be used in running LinuxMCE? Why I ask this? During the many installs I went through, each and every time I had to adjust membership of users. If not, mythtv-setup would not run properly.
- Running mythtv-setup from a terminal shows "kdesu command not found" [kdesudo is found (?)]
- Running sudo updatedb.conf errors out:
updatedb:/etc/updatedb.conf:4: unknown variable `exit'
A small edit of updatedb.conf solves this.[/li]
- minor issue: after LinuxMCE install ALT-F2 is broken in KDE
On to LinuxMCE related stuff:
- After entering KDE - How can one properly get back to LinuxMCE Orbiter?
- I've recently learned about /usr/pluto/bin/Restart_MythBackend.sh
How is a user supposed to run mythtv-setup if mythtv-backend can't be stopped without Restart_MythBackend doing its thing?
- In my case, in Belgium, using dvb-t and a Hauppauge HVR-4000 we have to use a workaround to get program information into mythconverg (mc2xml)
- With the new myth 0.22 version, multiple frontends are supported (THANK YOU!!)
However, after killing restart_mythbackend, after stopping myth-backend and entering mythtv-setup, I am
100% able to choose the correct /dev/dvb/adapterN/frontendN. Problem is the adapter is not recognized, so scanning channels is impossible.
- When leaving myth-setup there is a warning like:
"Path /home/user_1/data/pvr does not exist" solve?
This path off course does exist, but the initial user has no permission...
For testing purposes I installed dvb-utils and a copy of my local be-Schoten file (scan info file)
Scanning proceeds succesfully:
linuxmce@dcerouter:~$ sudo scan -f 1 ~/be-Schoten > channels.conf
using '/dev/dvb/adapter0/frontend1' and '/dev/dvb/adapter0/demux0'
initial transponder 506000000 0 2 9 3 1 0 0
>>> tune to: 506000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
0x0000 0x1090: pmt_pid 0x0000 VRT -- Klara continuo (running)
0x0000 0x1080: pmt_pid 0x0000 VRT -- MNM (running)
0x0000 0x1070: pmt_pid 0x0000 VRT -- Studio Brussel (running)
0x0000 0x1060: pmt_pid 0x0000 VRT -- Klara (running)
0x0000 0x1040: pmt_pid 0x0000 VRT -- Radio 1 (running)
0x0000 0x1050: pmt_pid 0x0000 VRT -- Radio 2 (running)
0x0000 0x1010: pmt_pid 0x0000 VRT -- EEN (running)
0x0000 0x1020: pmt_pid 0x0000 VRT -- Canvas/Ketnet (running)
0x0000 0x10b0: pmt_pid 0x0000 VRT -- Canvas+/Ketnet+ (running)
0x0000 0x10a0: pmt_pid 0x0000 VRT -- Sporza (running)
0x0000 0x10c0: pmt_pid 0x0000 VRT -- Nieuws+ (running)
0x0000 0x10d0: pmt_pid 0x0000 VRT -- MNM hits (running)
Network Name 'VRTmux1'
>>> tune to: 482000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_1_2:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
0x0001 0x1090: pmt_pid 0x1090 VRT -- Klara continuo (running)
0x0001 0x1080: pmt_pid 0x1080 VRT -- MNM (running)
0x0001 0x1070: pmt_pid 0x1070 VRT -- Studio Brussel (running)
0x0001 0x1060: pmt_pid 0x1060 VRT -- Klara (running)
0x0001 0x1040: pmt_pid 0x1040 VRT -- Radio 1 (running)
0x0001 0x1050: pmt_pid 0x1050 VRT -- Radio 2 (running)
0x0001 0x1010: pmt_pid 0x1010 VRT -- EEN (running)
0x0001 0x1020: pmt_pid 0x1020 VRT -- Canvas/Ketnet (running)
0x0001 0x10b0: pmt_pid 0x10b0 VRT -- Canvas+/Ketnet+ (running)
0x0001 0x10a0: pmt_pid 0x10a0 VRT -- Sporza (running)
0x0001 0x10c0: pmt_pid 0x10c0 VRT -- Nieuws+ (running)
0x0001 0x10d0: pmt_pid 0x10d0 VRT -- MNM hits (running)
Network Name 'VRTmux1'
dumping lists (24 services)
So to me this seems like SOUND PROOF that the HVR-4000 is properly registered and functioning.
I really do hope I (stupid me!) missed something here, as this is REALLY REALLY close to WORKING!
So once more: THANK YOU