If you were starting with a clean slate.... What OS for Myth box?

For discussion related to MythTV which doesn't belong in another forum.

Moderator: Forum Moderators

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Fri Jan 19, 2018 4:49 pm

What a long, strange trip it's been! And it ain't over yet.

I tried three times to get an Ubuntu install to work with Myth and my Hauppauge WinTV QuadHD tuner card. After finding out that my Gigabyte AM4 motherboard is known the world over for giving problems with new versions of Ubuntu, I tore the system down and rebuilt it on an ASRock board with the Ryzen 3 processor.

The Hauppauge website says their PPA supports kernel 4.4 and 4.10, which led me to installing Zesty 17.04. Is this a good choice? Right after the install, it's barking at me saying the OS is no longer supported.

I am familiar with Ubuntu and would prefer to stick with them, but is there a better choice? I am a long ways from being a Linux whiz, but I poke around on the command line when I need to.

So, what OS works best with the Hauppauge tuners and MythTV?

mythbuntubox
Senior
Posts: 128
Joined: Tue Apr 28, 2015 1:17 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by mythbuntubox » Fri Jan 19, 2018 8:37 pm

If you want to stick with Ubuntu, it's probably best to stick with the last LTS at the moment (16.04). The Mythbuntu team suggested starting with a basic server installation and then adding a slim desktop, e.g. XFCE, and then installing the Mythbuntu repos and configuring MythTV from there when they called time on Mythbuntu as a distribution.

MikeB2013
Senior
Posts: 305
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by MikeB2013 » Fri Jan 19, 2018 8:37 pm

If you need Hauppauge patches, you have to use their ppa on 17.10 Artful (I suggest Xubuntu or Lubuntu) which is now the only supported operating system, all the others are End of Life.

Zesty has just gone End of Life, but you can do an in-place upgrade to Artful 17.10, which Hauppauge do support (despite what is on the web site). After the in-place upgrade (I think this disables the ppa) you will need to re-add the Hauppauge ppa and reinstall the two packages.

I have the DVB-T/T2 version of the QuadHD card and tried it on a clean install of Xubuntu 17.10, with the Hauppauge ppa and mythtv 29 and it works ok.

Note the Hauppauge ppa installs a new kernel as well, personally I don't like this as it means you are now reliant on Hauppauge for kernel security fixes (rather than Ubuntu maintainers).

This is the kernel installed from Hauppauge ppa:
Linux xubutu17 4.13.0-19201712311231-generic #0+mediatree+hauppauge-Ubuntu SMP Sun Dec 31 21:14:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This is the kernel installed on a fully updated Artful installation:
Linux xubutu17 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

As you can see the Artful kernel is later, certainly by date, I have no idea about content.

It is a shame that Hauppauge made the decision not to support Ubuntu 16.04 LTS, using just a V4L (media stack) update. Even better would have been to get the required changes into the mainline V4L and hence into the kernel.

Mike

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Fri Jan 19, 2018 9:06 pm

Thank you so much for the replies, Gentlemen! I have upgraded to 17.10, and will proceed from there. I'll keep you all posted. I too am miffed that they didn't see fit to accommodate 16.04 LTS.

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Sat Jan 20, 2018 1:20 pm

Well, here I am. Installed myth 29 and set it up last night. Scan went as before, no lock, no channels. I've checked the output from dmesg and I'm getting an error like "fix frontend error" or something like that. I guess I could start another topic and post up dmesg output?

MikeB2013
Senior
Posts: 305
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by MikeB2013 » Sat Jan 20, 2018 2:15 pm

New post with dmesg output would be good.


Just for reference, they may assist, here is my dmesg output for my QuadHD DVB-T/T2 card showing tuner card detection

Code: Select all

dmesg|grep -i hauppauge
[    0.000000] Linux version 4.13.0-19201712311231-generic (buildd@lgw01-amd64-010) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #0+mediatree+hauppauge-Ubuntu SMP Sun Dec 31 21:14:27 UTC 2017 (Ubuntu 4.13.0-19201712311231.0+mediatree+hauppauge-generic 4.13.13)
[    3.505838] cx23885: CORE cx23885[0]: subsystem: 0070:6a28, board: Hauppauge WinTV-QuadHD-DVB(885) [card=60,autodetected]
[    3.847543] tveeprom: Hauppauge model 166200, rev B4I6, serial# 4035973424
[    3.847549] cx23885: cx23885[0]: hauppauge eeprom: model=166200
[    3.865862] cx23885: CORE cx23885[1]: subsystem: 0070:6b28, board: Hauppauge WinTV-QuadHD-DVB(885) [card=60,autodetected]
[    4.207585] tveeprom: Hauppauge model 166201, rev B4I6, serial# 4035973424
[    4.207590] cx23885: cx23885[1]: hauppauge eeprom: model=166201
and this dmesg output showing the initialization:

Code: Select all

mike@xubutu17:~$ dmesg|grep -i si2
               	5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
               	5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
               	5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
[    3.847546] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[    3.855692] si2168 5-0064: Silicon Labs Si2168-B40 successfully identified
[    3.855693] si2168 5-0064: firmware version: B 4.0.2
[    3.858583] si2157_probe: probing si2157 tuner fe=ffff8f46cfdba828 cfg=ffffa363813bfbc8 addr=0X60
[    3.858584] si2157_attach (6-0060)
[    3.858585] si2157 6-0060: creating new instance
[    3.858585] si2157_attach: instance=1
[    3.858586] si2157_attach(): new instance for tuner @0x60
[    3.858586] si2157_setup_configuration: client=ffff8f46d03ddc00
[    3.858587] si2157_setup_configuration: dev=ffff8f46cc10f600
[    3.858587] si2157_setup_configuration(0x60): dvb driver submitted configuration; port=1 invert=0
[    3.858828] si2157 6-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    3.858834] cx23885 0000:04:00.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[    3.864642] si2168 5-0066: Silicon Labs Si2168-B40 successfully identified
[    3.864643] si2168 5-0066: firmware version: B 4.0.2
[    3.865341] si2157_probe: probing si2157 tuner fe=ffff8f46cfdbd828 cfg=ffffa363813bfbc8 addr=0X62
[    3.865342] si2157_attach (6-0062)
[    3.865343] si2157 6-0062: creating new instance
[    3.865343] si2157_attach: instance=1
[    3.865344] si2157_attach(): new instance for tuner @0x62
[    3.865345] si2157_setup_configuration: client=ffff8f46cc288800
[    3.865345] si2157_setup_configuration: dev=ffff8f46cc10ec00
[    3.865346] si2157_setup_configuration(0x62): dvb driver submitted configuration; port=1 invert=0
[    3.865586] si2157 6-0062: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    3.865590] cx23885 0000:04:00.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
[    4.207587] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[    4.215711] si2168 10-0064: Silicon Labs Si2168-B40 successfully identified
[    4.215712] si2168 10-0064: firmware version: B 4.0.2
[    4.216805] si2157_probe: probing si2157 tuner fe=ffff8f46cfdb9828 cfg=ffffa363813bfbc8 addr=0X60
[    4.216807] si2157_attach (11-0060)
[    4.216808] si2157 11-0060: creating new instance
[    4.216808] si2157_attach: instance=1
[    4.216809] si2157_attach(): new instance for tuner @0x60
[    4.216810] si2157_setup_configuration: client=ffff8f46d562b800
[    4.216810] si2157_setup_configuration: dev=ffff8f46cc3b1c00
[    4.216811] si2157_setup_configuration(0x60): dvb driver submitted configuration; port=1 invert=0
[    4.217052] si2157 11-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    4.217059] cx23885 0000:05:00.0: DVB: registering adapter 2 frontend 0 (Silicon Labs Si2168)...
[    4.238373] si2168 10-0066: Silicon Labs Si2168-B40 successfully identified
[    4.238374] si2168 10-0066: firmware version: B 4.0.2
[    4.239338] si2157_probe: probing si2157 tuner fe=ffff8f46cfdb9028 cfg=ffffa363813bfbc8 addr=0X62
[    4.239339] si2157_attach (11-0062)
[    4.239341] si2157 11-0062: creating new instance
[    4.239342] si2157_attach: instance=1
[    4.239342] si2157_attach(): new instance for tuner @0x62
[    4.239343] si2157_setup_configuration: client=ffff8f46cde93800
[    4.239343] si2157_setup_configuration: dev=ffff8f46cffe2200
[    4.239344] si2157_setup_configuration(0x62): dvb driver submitted configuration; port=1 invert=0
[    4.239585] si2157 11-0062: Silicon Labs Si2147/2148/2157/2158 successfully attached
[    4.239591] cx23885 0000:05:00.0: DVB: registering adapter 3 frontend 0 (Silicon Labs Si2168)...
[   26.924705] si2168 5-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   27.528985] si2168 5-0064: firmware version: B 4.0.11
[   27.555920] si2157 6-0060: found a 'Silicon Labs Si2157-A30'
[   27.578508] si2157 6-0060: firmware version: 3.0.5
[   27.611725] si2157 6-0060: found a 'Silicon Labs Si2157-A30'
[   27.634308] si2157 6-0060: firmware version: 3.0.5
[   27.705223] si2157 6-0060: found a 'Silicon Labs Si2157-A30'
[   27.734059] si2157 6-0060: firmware version: 3.0.5
[   29.505965] si2168 5-0066: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   30.115375] si2168 5-0066: firmware version: B 4.0.11
[   30.142278] si2157 6-0062: found a 'Silicon Labs Si2157-A30'
[   30.164860] si2157 6-0062: firmware version: 3.0.5
[   30.198067] si2157 6-0062: found a 'Silicon Labs Si2157-A30'
[   30.220671] si2157 6-0062: firmware version: 3.0.5
[   30.289397] si2157 6-0062: found a 'Silicon Labs Si2157-A30'
[   30.319028] si2157 6-0062: firmware version: 3.0.5
[   31.087858] si2168 10-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   31.692838] si2168 10-0064: firmware version: B 4.0.11
[   31.719753] si2157 11-0060: found a 'Silicon Labs Si2157-A30'
[   31.742342] si2157 11-0060: firmware version: 3.0.5
[   31.772382] si2157 11-0060: found a 'Silicon Labs Si2157-A30'
[   31.804601] si2157 11-0060: firmware version: 3.0.5
[   31.876825] si2157 11-0060: found a 'Silicon Labs Si2157-A30'
[   31.906288] si2157 11-0060: firmware version: 3.0.5
[   32.663136] si2168 10-0066: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   33.274494] si2168 10-0066: firmware version: B 4.0.11
[   33.296391] si2157 11-0062: found a 'Silicon Labs Si2157-A30'
[   33.319296] si2157 11-0062: firmware version: 3.0.5
[   33.352489] si2157 11-0062: found a 'Silicon Labs Si2157-A30'
[   33.378884] si2157 11-0062: firmware version: 3.0.5
[   33.448757] si2157 11-0062: found a 'Silicon Labs Si2157-A30'
[   33.479794] si2157 11-0062: firmware version: 3.0.5

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Sat Jan 20, 2018 8:22 pm

Sorry this is ugly. I think I'm missing a driver, si 2165. Is that something I can just pick up from github and put in a folder, or do I need to install it somehow?

[ 9.701848] media: Linux media interface: v0.10
[ 9.734692] Linux video capture interface: v2.00
[ 9.734694] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
330dada5957e3ca0c8811b14c45e3ac42c694651 media: dvb_frontend: fix return error code
5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
7c4f4d1d7e5e3a5efc0a75410c7dad1c6c0be838 media: cx23885: Use semicolon after assignment instead of comma
[ 9.747988] kvm: disabled by bios
[ 9.780904] kvm: disabled by bios
[ 9.816896] kvm: disabled by bios
[ 10.006828] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
330dada5957e3ca0c8811b14c45e3ac42c694651 media: dvb_frontend: fix return error code
5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
7c4f4d1d7e5e3a5efc0a75410c7dad1c6c0be838 media: cx23885: Use semicolon after assignment instead of comma
[ 10.031825] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
330dada5957e3ca0c8811b14c45e3ac42c694651 media: dvb_frontend: fix return error code
5e0d3c3a2c67c060e65e152558fa3cbdabdafe6c media: MAINTAINERS: add si2165 driver
7c4f4d1d7e5e3a5efc0a75410c7dad1c6c0be838 media: cx23885: Use semicolon after assignment instead of comma
[ 10.209903] usb 1-7: reset high-speed USB device number 3 using xhci_hcd
[ 10.303385] cx23885: cx23885 driver version 0.0.4 loaded
[ 10.303519] cx23885: CORE cx23885[0]: subsystem: 0070:6a18, board: Hauppauge WinTV-QuadHD-ATSC [card=57,autodetected]
[ 10.404575] MCE: In-kernel MCE decoding enabled.
[ 10.405789] EDAC amd64: Node 0: DRAM ECC disabled.
[ 10.405790] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 10.436281] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3071, rev 021c detected

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Sat Jan 20, 2018 8:26 pm

dmesg|grep -i hauppauge
[ 0.000000] Linux version 4.13.0-19201712311231-generic (buildd@lgw01-amd64-010) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #0+mediatree+hauppauge-Ubuntu SMP Sun Dec 31 21:14:27 UTC 2017 (Ubuntu 4.13.0-19201712311231.0+mediatree+hauppauge-generic 4.13.13)
[ 10.303519] cx23885: CORE cx23885[0]: subsystem: 0070:6a18, board: Hauppauge WinTV-QuadHD-ATSC [card=57,autodetected]
[ 10.645002] tveeprom: Hauppauge model 165100, rev B4I6, serial# 4036005754
[ 10.645008] cx23885: cx23885[0]: hauppauge eeprom: model=165100
[ 12.119266] cx23885: CORE cx23885[1]: subsystem: 0070:6b18, board: Hauppauge WinTV-QuadHD-ATSC [card=57,autodetected]
[ 12.461075] tveeprom: Hauppauge model 165101, rev B4I6, serial# 4036005754
[ 12.461080] cx23885: cx23885[1]: hauppauge eeprom: model=165101

MikeB2013
Senior
Posts: 305
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by MikeB2013 » Sun Jan 21, 2018 4:29 pm

Not sure about the driver 2165, those messages seem to indicate the driver was included.

Can you attach, as a file attachment to a post, the complete output from the dmesg command (dmesg >dmesg.log) following a reboot.

Mike

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Sun Jan 21, 2018 6:18 pm

dmesg output attached.
Attachments
dmesg.txt
(89.79 KiB) Downloaded 18 times

MikeB2013
Senior
Posts: 305
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by MikeB2013 » Mon Jan 22, 2018 4:33 pm

Thanks for the dmesg.txt file.

The only thing that stands out is the risc errors for each of the tuners, I don't know if they are fatal or just a warning (the actual code indicates warning):

Code: Select all

[   38.770915] cx23885: cx23885[0]/1: Audio risc op code error
[   38.770920] cx23885: cx23885[0]: TV Audio - dma channel status dump
[   38.770925] cx23885: cx23885[0]:   cmds: init risc lo   : 0xf8ef9000
[   38.770929] cx23885: cx23885[0]:   cmds: init risc hi   : 0x00000000
[   38.770933] cx23885: cx23885[0]:   cmds: cdt base       : 0x00010930
[   38.770936] cx23885: cx23885[0]:   cmds: cdt size       : 0x00000008
[   38.770940] cx23885: cx23885[0]:   cmds: iq base        : 0x000106b0
[   38.770943] cx23885: cx23885[0]:   cmds: iq size        : 0x00000010
[   38.770947] cx23885: cx23885[0]:   cmds: risc pc lo     : 0xf8ef9018
[   38.770950] cx23885: cx23885[0]:   cmds: risc pc hi     : 0x00000000
[   38.770954] cx23885: cx23885[0]:   cmds: iq wr ptr      : 0x000041b2
[   38.770957] cx23885: cx23885[0]:   cmds: iq rd ptr      : 0x000041ac
[   38.770960] cx23885: cx23885[0]:   cmds: cdt current    : 0x00000000
[   38.770963] cx23885: cx23885[0]:   cmds: pci target lo  : 0x00000000
[   38.770967] cx23885: cx23885[0]:   cmds: pci target hi  : 0x00000000
[   38.770970] cx23885: cx23885[0]:   cmds: line / byte    : 0x00000000
[   38.770974] cx23885: cx23885[0]:   risc0: 
[   38.770975] 0x00000000 [ INVALID count=0 ]
[   38.770979] cx23885: cx23885[0]:   risc1: 
[   38.770980] 0x00000000 [ INVALID count=0 ]
[   38.770984] cx23885: cx23885[0]:   risc2: 
[   38.770985] 0x00000000 [ INVALID count=0 ]
[   38.770988] cx23885: cx23885[0]:   risc3: 
[   38.770989] 0x00000000 [ INVALID count=0 ]
[   38.770993] cx23885: cx23885[0]:   (0x000106b0) iq 0: 
[   38.770994] 0x81621dc8 [ sync irq1 22 21 cnt1 12 count=3528 ]
[   38.771001] cx23885: cx23885[0]:   (0x000106b4) iq 1: 
[   38.771002] 0xb8ac46c0 [ writerm sol 23 21 19 18 14 count=1728 ]
[   38.771008] cx23885: cx23885[0]:   iq 2: 0x81669635 [ arg #1 ]
[   38.771012] cx23885: cx23885[0]:   iq 3: 0xaa1bf77c [ arg #2 ]
[   38.771015] cx23885: cx23885[0]:   (0x000106c0) iq 4: 
[   38.771016] 0x4e4e4822 [ INVALID sol eol irq2 22 19 18 cnt1 14 count=2082 ]
[   38.771023] cx23885: cx23885[0]:   (0x000106c4) iq 5: 
[   38.771024] 0x6fc922ff [ INVALID sol eol irq2 irq1 23 22 19 cnt0 13 count=767 ]
[   38.771031] cx23885: cx23885[0]:   (0x000106c8) iq 6: 
[   38.771031] 0x7a0690e6 [ jump sol irq2 18 cnt1 resync 12 count=230 ]
[   38.771038] cx23885: cx23885[0]:   iq 7: 0xd99123ba [ arg #1 ]
[   38.771041] cx23885: cx23885[0]:   iq 8: 0xcc3465c6 [ arg #2 ]
[   38.771045] cx23885: cx23885[0]:   (0x000106d4) iq 9: 
[   38.771045] 0x043c0e53 [ INVALID eol 21 20 19 18 count=3667 ]
[   38.771051] cx23885: cx23885[0]:   (0x000106d8) iq a: 
[   38.771052] 0xc328847c [ writecm irq2 irq1 21 19 resync count=1148 ]
[   38.771058] cx23885: cx23885[0]:   iq b: 0x07170398 [ arg #1 ]
[   38.771062] cx23885: cx23885[0]:   iq c: 0x0f80ccaf [ arg #2 ]
[   38.771065] cx23885: cx23885[0]:   (0x000106e4) iq d: 
[   38.771066] 0xbd52175b [ writerm sol eol irq1 22 20 cnt1 12 count=1883 ]
[   38.771072] cx23885: cx23885[0]:   iq e: 0xc8e9c85d [ arg #1 ]
[   38.771076] cx23885: cx23885[0]:   iq f: 0xbe881f0f [ arg #2 ]
[   38.771077] cx23885: cx23885[0]: fifo: 0x00007000 -> 0x8000
[   38.771078] cx23885: cx23885[0]: ctrl: 0x000106b0 -> 0x10710
[   38.771081] cx23885: cx23885[0]:   ptr1_reg: 0x000073a8
[   38.771084] cx23885: cx23885[0]:   ptr2_reg: 0x00010938
[   38.771088] cx23885: cx23885[0]:   cnt1_reg: 0x00000075
[   38.771091] cx23885: cx23885[0]:   cnt2_reg: 0x00000007

It could be worthwhile checking if your card actually works outside of mythtv, to do this:

In a terminal make sure mythbacked is not running :
sudo systemctl stop mythtv-backend.service

Install w_scan :
sudo apt install w-scan

Run w_scan for ATSC VSB (United States, Over-the-Air) - info taken from https://github.com/b-rad-NDi/Ubuntu-med ... /issues/31 :

w_scan -fa -A1 -c US -X

Mike

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Mon Jan 22, 2018 7:19 pm

Thanks Mike! I will do that.

The card was working briefly with Kaffeine, but I can't even recall what Ubuntu version I was running at the time. I want to say it was 16.04.1 with kernel 4.4, but that might be wrong. I was able to pull several channels though. That much I do remember.

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Mon Jan 22, 2018 10:32 pm

installed and ran w-scan. It seems happy, reports no errors, but finds no channels.

Also, this dmesg output is different. Only change I made was putting RAM in proper slots on motherboard.
Attachments
dmesg2.log
(88.85 KiB) Downloaded 9 times

MikeB2013
Senior
Posts: 305
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by MikeB2013 » Wed Jan 24, 2018 7:32 pm

I just hit a similar problem risc errors on my new motherboard, Gigabyte AB350 Gaming 3, with Ryzen CPU and QuadHD DVB card.

I have reported the issue to Hauppauge see :
https://github.com/b-rad-NDi/Ubuntu-med ... -360244131

Mike

Marcus Aurelius
Junior
Posts: 33
Joined: Sat Dec 16, 2017 2:12 pm
United States of America

Re: If you were starting with a clean slate.... What OS for Myth box?

Post by Marcus Aurelius » Thu Jan 25, 2018 3:01 pm

Funny, I had that same motherboard and a Ryzen 3 1200. Not much better with the ASRock board, but at least 17.10 installed on it okay, or so it seems. In the end, it doesn't seem to work either. I'm thinking it's something Ryzen specific (what is the processor microcode that gets flagged in "system info"? I should have stayed "old school". I may try this exercise one more time with an AM3 board and an FX-series processor. I've been beating my head on this for far too long!

Post Reply