Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - noggin72

1
Raspberry PI / RPI 2
« on: March 10, 2015, 12:40:12 »
Hi

the firmware is now included and the new dvb package shold be online in ~1 hour.

Cheers - will check it out this evening.

2
Raspberry PI / RPI 2
« on: March 10, 2015, 12:34:32 »
Just tried the new RPi 2 4.0.1 build (separate to the R Pi build)

The August T210 (also sold as a Geniatech) lsusb -v output is here : http://pastebin.com/9T5ENDdq (I only pasted the specific for that USB this time)
The results of dmesg when I plugged it in are here : http://pastebin.com/MqBp8yRq


Hi noggin72,

there seem to be some issues with this stick: https://tvheadend.org/boards/5/topics/10864?r=11372#message-11372

Regards, Paul

I'm in that thread Paul - the original T210, which I have, had Crazy Cat's patch to enable T2 (not just T as previously) support added to the Media Build stuff quite a while ago.  Prior to that you had to compile with a patch - which is what OE did from about 4.0.5 (but that is probably because TV Headend is quite popular in the UK where we have T2 support - one of the main TVH devs is in the UK)

Code: [Select]
RE: August DVB-T210 - Added by Olli Salonen 8 months ago

It seems CrazyCat's patch has just gone into the media tree, which means it's likely included in 3.17 kernel, not the soon to be ready 3.16.

3
Raspberry PI / RPI 2
« on: March 08, 2015, 13:42:36 »
If you find some instructions about how to successfully make your DVB-Sticks work under Linux please let us know. I'm sure that MLD can incorporate these.
Will do.  All of these three tuners, and DVB-T2 work OK in OpenElec and TV Headend on the Pi/Pi2, and recent Media_Build has supported them (the August T210 needed a small patch for a while)

But TV Headend and Kodi aren't VDR...  (I used to use VDR on a  DVB-S Full card 10 or so years ago and loved it)

Quote
Are the DVB-T2 channels encrypted in the UK?

No - we have almost no encrypted broadcasts on DVB-T/T2 in the UK.

However all the services on DVB-T2 muxes are encoded in H264 not MPEG2, whether SD or HD.  (DVB-T2 was introduced in the UK when we launched HD OTA in 2009ish, but some SD services are now being broadcast in H264 on the T2 muxes as well)

4
Raspberry PI / RPI 2
« on: March 08, 2015, 13:17:58 »
For info - here is the output of the tuning process via the web interface : http://pastebin.com/VBSP1GL2
(You can see it fail to tune 545.8MHz - 546MHz at the end, but succeed and find 570MHz but those channels aren't added to channels.conf)

Here's the channels.conf file that is created : http://pastebin.com/DmSJFWfr

I receive the London Crystal Palace tranmsitter which carries the following 7 muxes :

PSB1 490MHz (C23) DVB-T  64QAM 8k 8MHz  (BBC SD services and BBC Radio)
PSB2 514MHz (C26) DVB-T  64QAM 8k 8MHz  (ITV, C4 and C5 SD main services)
PSB3 545.8MHz (C30-) DVB-T2 256QAM 32k 8MHz (BBC, ITV, C4 HD services and additional SD)
COM4 506MHz (C25) DVB-T 64QAM 8k 8MHz
COM5 482MHz (C22) DVB-T 64QAM 8k 8MHz
COM6 529.8MHz (C28-) DVB-T 64QAM 8k 8MHz
COM7 570MHz (C33) DVB-T2 256QAM 32k 8MHz (BBC, C4, Al Jazeera HD and additional SD)
LW 538MHz (C29) DVB-T QPSK 8k 8MHz (Local TV)

5
Raspberry PI / RPI 2
« on: March 08, 2015, 13:03:38 »
Just tried the new RPi 2 4.0.1 build (separate to the R Pi build)

With my Hauppauge Nova-T DT Dual DVB-T tuners I don't get a frontend for my /dev/dvb/adapter0.  If I look at dmesg it appears that there is a crash during the set-up of the USB Tuner.  http://pastebin.com/EJKER8DD (Line 293 ?)

I have run opkg install tools but now whenever I run lsusb or lsusb -v with the Hauppauge tuner plugged in my SSH session hangs.  I have to login via a separate SSH session to trigger a reboot.  However when I do the Pi doesn't properly power down... All is not well.

The PCTV 290e DVB-T/T2 USB stick isn't recognised as a DVB device it appear : http://pastebin.com/Vzp4tYHk
lsusb -v results : http://pastebin.com/0TJdharU (Have pasted entire result but PCTV appears at line 409)

The August T210 (also sold as a Geniatech) lsusb -v output is here : http://pastebin.com/9T5ENDdq (I only pasted the specific for that USB this time)
The results of dmesg when I plugged it in are here : http://pastebin.com/MqBp8yRq

This is more hopeful - it is successfully initialised and I get a frontend0 in /dev/dvb/adapter0

It scanned the UK DVB-T/T2 channels, found all 7 UK DVB-T/T2 muxes, but something still went wrong when it added the DVB-T2 muxes. One mux was channel scanned (i.e. you could see the service names being broadcast) but they don't appear as channels in the VDR OSD.  The other mux failed to add the channels (though it was found during the initial scan)

So good news and bad news.  Two popular DVB-T/T2 tuners don't work, but one, not as widespread, model works, but the DVB-T2 implementation doesn't quite work?



6
Raspberry PI / RPI 2
« on: March 07, 2015, 15:14:10 »
I was a bit confused by that too...

My installation path has been :

Download mld 4.0.1 Standard Raspberry Pi.  Copy the contents of this zip file to an empty FAT32 formatted SD/MicroSD card. Boot the Pi 2 or Pi with this. 

Select the installation to SD card option, and install to the booted SD Card (this is OK?)

Reboot.

SSH in with login root/pwd root.

I get to BusyBox and type lsusb -v and only get the non-verbose output.


7
Raspberry PI / RPI 2
« on: March 07, 2015, 13:44:59 »
Because I really want to trial VDR on a Pi / Pi 2 I tried the same 4.0.1 install on a Pi B (512MB) I also have.

The Dibcom-based Nova-T DT Diversity was recognised - but I don't think all is well.

dmesg : http://pastebin.com/EgJL2Y4K

ls /dev/dvb shows adapter0 as you would expect, but ls /dev/dvb/adapter0 only shows demux0,dvr0 and demux0 with no frontend0 - so there is something wrong there?

lsusb -v :
Code: [Select]
Bus 001 Device 002: ID 0424:9512
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2040:9580
Bus 001 Device 007: ID 147a:e03e

So even on a Pi there are issues at the moment with the current 4.0.1 build? 

My PCTV 290e is recognised as a USB device, but not as a DVB-T/T2 tuner (the drivers for the 290e have been in the kernel since 3.0?). 

8
Raspberry PI / RPI 2
« on: March 07, 2015, 02:06:00 »
Would that be related to the i2c errors I posted in my earlier post?

Totally understand that it's early days though - good luck with the bug hunting!

9
Raspberry PI / RPI 2
« on: March 06, 2015, 23:57:19 »
OK :
DVB-T Dual Tuner Diversity : http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick
dmesg : http://pastebin.com/aiRfx21n
lsusb -v :
Code: [Select]
Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2040:9580
Bus 001 Device 007: ID 147a:e03e

PCTV 290e DVB-T/T2 http://www.linuxtv.org/wiki/index.php/PCTV_Systems_nanoStick_T2_290e
dmesg : http://pastebin.com/j05NdXBt
lsusb -v :
Code: [Select]
Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2013:024f
Bus 001 Device 007: ID 147a:e03e

August T210 DVB-T/T2
dmesg : http://pastebin.com/z64JUZPx
lsusb -v :
Code: [Select]
Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 1f4d:d220
Bus 001 Device 007: ID 147a:e03e

Hope this helps.

Think the DVB devices are Bus 001 Device 006 as they are the only devices that change?  I have a USB powered hub and a Windows Media Center IR receiver plugged in, as well as a small keyboard.

10
Raspberry PI / RPI 2
« on: March 06, 2015, 23:37:43 »
Apologies for writing in English. You wouldn't want to read my dreadful German.

I flashed the MLD Pi image to a 16GB MicroSD card and then installed that within MLD to the same card.  I can't seem to get any of my DVB-T/T2 tuners - 2 x Dibcom (Hauppauge dual/diversity USB stick), PCTV 290e or August T210 - recognised to do a channel scan.  Every time I get
Code: [Select]
Stopping VDR
done
w_scan version 20120605 (compiled for DVB API 5.4)
using settings for UNITED KINGDOM
DVB aerial
DVB-T GB
scan type TERRESTRIAL, channellist 6
output format vdr-1.6
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
main:3220: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.
Starting VDR

Any advice - do I need to install a DVB driver paket ?

Thought I'd Telnet in to see and "opkg install dvb" returns the following :
Code: [Select]
opkg install dvb
Package dvb (1:2015.03.03-114_3.19.0.147) installed in root is up to date.
Configuring i2c.
modprobe: can't load module i2c-dev (kernel/drivers/i2c/i2c-dev.ko): invalid module format
Collected errors:
 * pkg_run_script: package "i2c" postinst script returned status 1.
 * opkg_configure: i2c.postinst returned 1.

11
Raspberry PI / Test MLD-4 RPI tgz
« on: February 27, 2015, 00:23:27 »
Hi noggin72,

here is a download link for MLD-4.0.1-rpi_rpi_2015.02.19-106.tar

https://www.dropbox.com/s/39152ewaeqrgcb1/MLD-4.0.1-rpi_rpi_2015.02.19-106.tar?dl=0

I hope it will be useful for you. RPI 2 is not supported, yet.

Kind regards,

Paul

Thank you - very kind of you to help.

12
Raspberry PI / Test MLD-4 RPI tgz
« on: February 26, 2015, 18:58:16 »
Und ich bin sehr traurig, wenn es schlechte Manieren, um auf Englisch zu formulieren.

Sorry for my English answer. I too cannot boot the MLD-4.0.1-rpi_rpi_2015.02.22-108.tgz current download on a Pi B or B+ I've also tried the net install version.

I get a red square (rotes quadrat) at the top of the screen.

Can someone provide a link to the 02.21 or 02.19 builds ?

Vielen dank.