Posts by thecrane

SUCCESS!!!!

Some of the final mistakes were at my end and some (super-noobish-)mistakes.

A couple of notes for anyone else as dumb as me:

• Make sure you're using a Raspbian (not LibreELEC) build on your SD card. I think my errors were due to the compiled kernel not having support for squashfs
• Make sure you're clear what version your Raspberry Pi is. I thought I was using an old Raspberry Pi 2 and was, therefore, compiling in 64-bit. But it is actually a RPi original, model B, so I should have been compiling in 32-bit.

Other than that, everything looks promising, so thank you very much, Puffin Chunks, for your help!

Okay, so I've managed to get past the rainbow screen...but not that much past it!

I used a LibreELEC build, managed to follow all the instructions (I think) to cross-compile on an Ubuntu machine, and get it all installed on my Raspberry Pi (B+ - not a Raspberry Pi 2 that I originally thought).

But now I get a kernel panic saying "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" with another note a two lines down saying "Hardware name: BCM2835" and then a stack trace.

The last line is "random: fast init done".

So close and yet so far. If anyone can help, I'll be super appreciative!

Quote from Puffin Chunks

If you run in to any issues, let me know, but I can't promise anything as I am by no means an expert!

Cheers

Just a quick question - what were you using as the base build OS? Was it Raspbian? Or Libreelec? I've tried on both, and after patching and compiling the custom kernel, all I get is the rainbow screen when the RPi boots.

Quote from Puffin Chunks

Ok, I have created a patch for version 4.9.y for Rasperry Pi. Some notes for anyone looking to use this.

• This patch was created for my use only, anyone is free to use it, change it and amend it for reposting, but I will not troubleshoot or fix any issues anyone has. It has just been created from my amends to the 4.9 kernel to get dual tuner support working on an rPi Model B+
• Whilst I have tested that the patch compiles (it does) I have not tested it on my Pi. I finally have a working system and I don't want to jeopardise that. That being said, I see no reason why it shouldn't work as it has been created from my working sources, so the compiled kernel should be identical to what I have running.
• Whilst this patch was compiled for a Model B+, I see no reason why it would not work on other models of Pi as the sources are the same.
• This adds support for DVB only! I am in the UK so do not have a need for ATSC nor have any means for testing it. The amended code for ATSC is in my patch, but it has been commented out and has not been tested. The source for lgdt3306a would need to be amended to get ATSC working and I have not touched this. So to reiterate ATSC will NOT work with this patch. Do not try it.

With that said, follow the instructions for compiling your own kernel as detailed in the Raspberry Pi documentation here: Kernel building - Raspberry Pi Documentation but make the following changes:

• When instructed to get the sources, use the following command instead to ensure that you grab the sources for the 4.9 kernel:
  
  Code

  git clone --depth 1 -b rpi-4.9.y https://github.com/raspberrypi/linux

• Once you have retrieved the sources, but before running any other commands, grab my patch from here: hauppage_winTV_dualHD_DVB_PuffinChunks_4.9.y.diff - Google Drive and copy it one folder up from where you have downloaded the rpi kernel source (eg: if your source downloaded to /home/user/linux then copy the patch to /home/user)
• Enter the kernel source directory and apply the patch
  
  Code

  cd linux
  patch -p1 < ../hauppage_winTV_dualHD_DVB_PuffinChunks_4.9.y.diff

  
  The following output should tell you whether you've successfully applied the patch:

  Code

  patching file drivers/media/usb/em28xx/em28xx-cards.c
  patching file drivers/media/usb/em28xx/em28xx-core.c
  patching file drivers/media/usb/em28xx/em28xx-dvb.c
  patching file drivers/media/usb/em28xx/em28xx.h

• With the patch successfully applied to the source you can now continue to follow the instructions on the Raspberry Pi documentation. It is up to you whether you compile locally on the Pi or on a different machine. My advice is the latter as it takes just minutes, but can take many hours to compile on a Pi.
• Once compiled and installed on the Pi, don't forget to grab the firmware for the card from here: dvb-demod-si2168-b40-01.fw and copy it to your /lib/firmware folder on your Pi. You may still be missing some firmware. If this is the case, then I recommend getting CrazyCat's firmware tarball and just installing the whole lot, so you have all bases covered (dvb-firmwares.tar.bz2)

As to your other questions, I believe that the system knows that you have a custom kernel installed, so will not update it (assuming that you are using apt to update your system), although I am happy to be corrected on this.

The Raspberry Pi documentation will tell you how to either compile on your pi or on another system and transfer it over. As I stated above, I recommend cross-compiling on a different machine, but do whatever you feel most comfortable with, just be prepared for a long wait if compiling on the Pi.

If you run in to any issues, let me know, but I can't promise anything as I am by no means an expert!

Cheers

Display More

Thanks so much for all that detail and help!!! I'll give it a go when I get home from work tonight, but I really appreciate you taking the time! Thanks again!

Quote from Puffin Chunks

Hi

I never actually tried using the LibreElec build as my LibreElec install runs on a different device, so I can't say whether this works out of the box with it, but I would try that first, because if it does, then life will be a lot easier.

If not, then post back and I'll see if I can create a patch for the 4.9.11 kernel. Based off my experience, you will need to compile your own kernel to get this working on a Raspbian based Pi (not as daunting as it sounds).

It didn't work out of the box on a new LibreELEC install on my RPi3. Not even detecting the dualHD at all now?

Any help you can provide with how to compile my own kernel, or the idiot's guide to getting this working on an RPi3 (any distro) would be amazing!

Also - and forgive my ignorance - but if I custom compile and patch a kernel, what happens when the system updates?

And (last dumb question): am I compiling all of these on a separate build machine? If so, how am I transferring the right files to the RPi?

Quote from Puffin Chunks

Ugggh, 3 posts on the roll... sorry!

Finally got this working on kernel 4.9.11.

In the end I had to apply the patch to 4.2 (as posted earlier in the thread). Whilst this showed both adapters, they wouldn't tune.

I took the patched files and looked to apply the relevant amends to the source files in kernel 4.9.11. My c knowledge is next to non-existent so this was fun. I compiled kernel 4.9.11 with my amended sources (for DVB only, I don't have ATSC).

Compiled, recognised both tuners and both tune.

I'm sure there was an easier way to do this, but I'm just happy I got there in the end.

Display More

Hi everybody,

I've just purchased a WinTV-dualHD here in New Zealand, and I'm trying to get it running on a Raspberry Pi 3 running OSMC (based off Raspbian) and I'm wondering if there is anything I can do with the great work already outlined in this thread to get a similar result on this setup? Or should I wipe it and run LibreELEC?

I'd really appreciate any help you could provide.

Cheers!