Tvheadend

1. Do you have the firmware installed - it's one thing to see the tuner, it's another to initialise it

2. What happens if you restart tvheadend - it's possibly a timing issue, in that the card could still be initialising as tvheadend gets going

Hi,

when i restart the tvheadend i cannot see the Card.

What you mean with Firmware? Wich driver should i use? There is no information in the dmesg log, that the driver was not found.

Must i copy a driver in /lib/firmware ??

My card work with the Kernel 3.2...

Regards
Hermann

The pi USB alim is not respecting USB standard and you probably need to use an USB powered switch like I was forced to do.

The Device has an external Powersupply.

But - wich Firmware i must use?

You'd normally get it from the right v4l installation... I don't know if there are separate firmware packages available for the pi.

Google suggests that you're looking for dvb-usb-pctv-452e-01.fw

Try this:

https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-usb-pctv-452e-01.fw

Thanks, but this didn't help.....

I copied the file to /lib/firmware.

In the log from dmesg there was no other Information.

Hmmm... I'd put money on it being a card initialisation problem... the lack of "found... in a warm state" stuff in dmesg leads me to that (unless I've badly misunderstood somwthing). Maybe that's not the right firmware...

Can you load the modules manually using modprobe? I'm not sure what modules it's using, that said... is it stb6100? Anything in dmesg that looks even vaguely like this string?

I've had to rebuild v4l to get things to work before, so that's another option if you've got a spare couple of hours...

Is it possible that this is a problem with the kernel 3.2??

When ein use an older Kernel, then i see that a firmware loaded, but under this Kernel my DVB Card was not supported.

I don't have a /dev/deb Directory......

I think i have v4l installed an configure a new Media_Tree.

Regards
Hermann

Not sure - the linuxtv page says that drivers are included in 3.2+, so I presume that earlier kernels have custom .ko. That's really what I'd aim to test with modprobe: do you have, do you need, can you load the relevant kernel modules for this tuner. If they don't exist then something's gone astray - if they're meant to be part of that kernel then they've been left out (perhaps it's a pi-specific build?) and you might need to build them back in - in other words, ignore the 3.2 bit and rebuild as if you had 3.1.

hello-
I have been using tvheadend on raspberry pi with arch linux for a while now and every time there is a kernel update, the dvb drivers need to be rebuilt against the new kernel. Only then will the dvb adaptor be recognised. With what you describe, this may be what you are experiencing.
In order to rebuild the drivers, I have figured out by many hours of pain what exact steps to follow and as Prof Yaffle points out, the process itself does take many hours to complete. If it is of use to you, later this evening I can post the steps I have found successful (I'm at work at present).
cheers
Rob

Hi,

it will be great, if you can descripe the steps to compile the new Modules for the DVB Card.

Regards
Hermann

Hi Hermann, the following is specific to arch linux and it assumes that the DVB device drivers have been previously installed. Have a good read of the linuxtv.org page linked below, if you haven't already.

My setup:¶

Raspberry pi running Arch linux, current kernel 3.10.32-1-ARCH
Kaiser Baas USB TVStick KBA01008- http://www.kaiserbaas.com/tv-radio-category/usb-hd-tvstick-tuner
Installed DVB device drivers via instructions here: http://linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers
When TV stick is connected - loads module dvb_usb_rtl28xxu and mounts at /dev/dvb/adapter0
(note other arch-specific dependencies were required, such as linuxtv-dvb-apps, libavcodec...)

The Problem:¶

With any kernel update, the TV USB stick is no longer recognised. That is:
- module dvb_usb_rtl28xxu not found via `lsmod` and
- /dev/dvb/adapter0 does not exist

The resolution:¶

Rebuild the DVB Device Drivers against the updated kernel. Source: http://linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers

1. Via terminal, enter the directory where the DVB device drivers are installed, in my case:
   

   $ cd ~/.config/media_build
   

2. Issue commands to clean up the build configuration environment and then build/compile the modules from the source code. This ensures that the following "make" build process will be against the new kernel source ("/usr/src/[uname -r]”). As this takes approx 3 hours they are concatenated as:
   

   $ make distclean && make
   

3. Install the kernel driver modules, with:
   

   $ sudo make install
   

4. Check if there is mixture of new modules (*.ko) and their older compressed version (*.ko.gz) installed, as usually occurs with me; using
   

   $ for file in `find /lib/modules -name "*.ko"`; do if [[ -e $file.gz ]]; then echo "$file.gz should be removed"; fi; done
   

   
   This will usually result in many lines ouputted of conflicting module files that need to be moved. If nothing is listed then skip the next step.
5. Move the conflicting module files. First create a directory to move them into:
   

   $ sudo mkdir /etc/v4l-dvb_old_driver$(date -I)
   

   
   Then move them with:
   

   $ for file in `find /lib/modules -name "*.ko"`; do if [[ -e $file.gz ]]; then sudo mv $file.gz /etc/v4l-dvb_old_driver$(date -I); fi; done
   

6. use the v4l-dvb reload command and "depmod" step to rebuild modules dependencies
   

   $ sudo make reload
   $ sudo depmod -a
   

7. Reboot
8. Plug TV stick back in and check for success with:
   

   $ lsmod | grep dvb
   

   
   => should have some sort of output listing modules specific to your TV tuner card, like
   

   dvb_usb_rtl28xxu       14180  0 
   rtl2830                 7258  1 dvb_usb_rtl28xxu
   dvb_usb_v2             15064  1 dvb_usb_rtl28xxu
   dvb_core               92200  3 rtl2830,rtl2832,dvb_usb_v2
   rc_core                16810  3 dvb_usb_rtl28xxu,dvb_usb_v2
   

   
   and check the usual mount point, in my case:
   

   $ ls /dev/dvb/
   adapter0
   

9. Result
   If the 2 commands immediately above don't have any output, then it didn't work

I hope all of that helps. But it will likely be difficult if you are running a different OS other than arch, particularly if the drivers are preinstalled by the OS in some way that is not obvious. If that's the case, you may be better off asking on their dedicated forums.

Hi.

Thanks for your help.

Now my card found and all works fine.

Thank you very much.

Regards Hermann

no problems; glad it helped