Lost DVB-C TV-card since 3.6* kernel[SOLVED]

[EasterParade]

This may have been mentioned here somewhere already but could not find
a posting that might help.

Since the advent of the 3.6 kernel there are no dvb frontends to be found
under device drivers - multimedia - DVB/ATSC adapters.
Also the driver for the tv-card won´t get loaded. Kaffeine cannot find
a device - so TV on PC is off.

Code: Select all

06:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

Doesn´t make a difference whether it´s a module or built in: the KNC-One TV-card
just won´t work any more.


Does anyone know this issue and/or a method to solve it?

[jamatik]

same problem with DVB-T, stick with 3.5* for now - they moved the DVB Framework, reactivated the modules and all options as before, but the modules for my card didn't even get build

[EasterParade]

It all started with the 3.6 kernel series. In older kernels it worked
probably because v4l which was removed in 3.6 kernels and the subsection for the
frontends which is empty in 3.6 series.

Code: Select all

--- DVB/ATSC adapters                                                              │ │  
  │ │                   *** Supported SAA7146 based PCI Adapters ***                                 │ │  
  │ │             <M>   SAA7146 DVB cards (aka Budget, Nova-PCI)                                     │ │  
  │ │             <M>     Budget cards                                                               │ │  
  │ │                   *** Supported USB Adapters ***                                               │ │  
  │ │             < >   Technotrend/Hauppauge Nova-USB devices                                       │ │  
  │ │             < >   Technotrend/Hauppauge USB DEC devices                                        │ │  
  │ │                   *** Supported FlexCopII (B2C2) Adapters ***                                  │ │  
  │ │             < >   Technisat/B2C2 FlexCopII(b) and FlexCopIII adapters                          │ │  
  │ │                   *** Supported BT878 Adapters ***                                             │ │  
  │ │                   *** Supported Pluto2 Adapters ***                                            │ │  
  │ │             < >   Pluto2 cards                                                                 │ │  
  │ │                   *** Supported SDMC DM1105 Adapters ***                                       │ │  
  │ │                   *** Supported FireWire (IEEE 1394) Adapters ***                              │ │  
  │ │             < >   FireDTV and FloppyDTV                                                        │ │  
  │ │                   *** Supported Earthsoft PT1 Adapters ***                                     │ │  
  │ │             < >   PT1 cards                                                                    │ │  
  │ │                   *** Supported Mantis Adapters ***                                            │ │  
  │ │                   *** Supported nGene Adapters ***                                             │ │  
  │ │             < >   Micronas nGene support                                                       │ │  
  │ │                   *** Supported ddbridge ('Octopus') Adapters ***                              │ │  
  │ │             < >   Digital Devices bridge support                                               │ │  
  │ │                   *** Supported DVB Frontends ***

That´s what it looks like in 3.6* kernels.
Whether the driver for the chip is built in or module doesn´t matter:
it just doesn´t work.
The module doesn´t get loaded

Code: Select all

lsmod
Module                  Size  Used by
vboxnetflt             14893  0 
vboxnetadp             17670  0 
vboxdrv              1808915  2 vboxnetflt,vboxnetadp
hid_apple               5362  0 
snd_virtuoso           31431  4 
snd_oxygen_lib         28933  1 snd_virtuoso
snd_pcm                71911  2 snd_oxygen_lib
snd_timer              18304  2 snd_pcm
snd_page_alloc          6745  1 snd_pcm
skge                   30301  0 
nvidia               9336916  38 
snd_mpu401_uart         5699  1 snd_oxygen_lib
snd_rawmidi            18082  1 snd_mpu401_uart
snd_seq_device          4924  1 snd_rawmidi
sky2                   47742  0 
snd                    52486  13 snd_virtuoso,snd_oxygen_lib,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
usbhid                 34997  0 
asus_atk0110            9755  0 
coretemp                5866  0 
soundcore               4994  1 snd
i2c_i801                9195  0 

Starting kaffeine from the console doesn´t give any more information to go with.

I´d REALLY appreciate it if any useful information would be disseminated here
by the kernel specialists or any user with the same problem who has more knowledge about
this.

[jamatik]

I just compiled kernel 3.6.8, and the modules getting build for me again aka my DVB-Card works again.

Also check if the modules actually got build:

Code: Select all

ls -l /lib/modules/3.6.8-gentoo/kernel/drivers/media/dvb/frontends/

In 3.6* kernels <3.6.8/3.6.7 they wasn't build even if checked.

If u still have problems with new kernel 3.6.8, say it, I will look over it again.

Edit: V4L Adapters are still there:

Code: Select all

--- Multimedia support
    --- Video capture adapters
       --- V4L PCI(e) devices

[EasterParade]

I apologize for not responding so long.
V4l for pci devices is not in the kernel.

[jamatik]

The code of my last post shows u where to find v4l pci(e) devices. I'm using gentoo-sources.

Or just skip to gentoo-sources-3.7*. The kernel-developers reordered the multimedia configs again. For the better imho.
Open 2 terminal windows. 1 for a <=3.5 kernel and 1 for a 3.7 kernel.
use make menuconfig/make oldconfig. And then just copy every config option under "multimedia support" from ur 3.5*-kernel to kernel 3.7. Different places, but all options u need are still there. Compile and test. What u still missing?

[Nreal]

So VDR 1.7.25 doesnt work with 3.7.0/1 - it starts without a problem but doesnt work though.

Is it because the dvb frontends have moved or what

ls -l /lib/modules/3.7.1-gentoo/kernel/drivers/media/dvb-frontends/

s5h1420.ko stb6100.ko stv6110x.ko tda10086.ko tua6100.ko
stb0899.ko stv0288.ko tda10021.ko tda8261.ko
stb6000.ko stv090x.ko tda1004x.ko tda826x.ko

ls -l /lib/modules/3.6.8-gentoo/kernel/drivers/media/dvb/frontends/
l64781.ko stb0899.ko stv0297.ko tda10021.ko tda8261.ko ves1x93.ko
lnbp21.ko stb6000.ko stv0299.ko tda1004x.ko tda826x.ko
s5h1420.ko stb6100.ko stv090x.ko tda10086.ko tua6100.ko
sp8870.ko stv0288.ko stv6110x.ko tda8083.ko ves1820.ko

[jamatik]

I think wrong topic for ur post! It's no kernel problem!
What does it matter for an application where the modules of the kernel are in?

Code: Select all

ls -l /lib/modules/3.7.1-gentoo/kernel/drivers/media/

Devices are still in

Code: Select all

ls -l /dev/dvb/

!

[Nreal]

06:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

It works well with 3.6 kernels, allthough have to remove ca0 on every reboot - it doesnt even have a cam..

cd /dev/dvb/adapter2 && rm ca0 && /etc/init.d/vdr start &


CONFIG_DVB_CAPTURE_DRIVERS=y
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=y
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
CONFIG_DVB_USB=y
CONFIG_DVB_USB_ANYSEE=y
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=m
CONFIG_DVB_STV6110x=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=y
CONFIG_DVB_STV0900=y
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=y
CONFIG_DVB_SP8870=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_MT352=y
CONFIG_DVB_ZL10353=y
CONFIG_DVB_CXD2820R=y
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=y
CONFIG_DVB_STV0297=m
CONFIG_DVB_PLL=y
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6423=y

[DarkSpir]

Hi guys,

I also have problems with my dvb setup since I changed to 3.6 and I think I have a good idea what's going wrong. When I took a closer look at the configuration I was happy. No more searching for the right frontend module for your dvb driver. It's selected automatically. I was happy until the first boot when nothing worked and dmesg told me stuff like this:

Code: Select all

[    9.366342] DVB: Unable to find symbol tda10023_attach()

Problem is: When I select the driver module for my dvb card, it also selects the needed frontends, but not the right ones. I googled a little bit, discovered the magic of the Kconfig files in the kernel sources (I found mine in /usr/src/linux/drivers/media/dvb/dvb-usb/ together with the source file of my driver module) and took a look at what it does with my driver module:

Code: Select all

config DVB_USB_TTUSB2
        tristate "Pinnacle 400e DVB-S USB2.0 support"
        depends on DVB_USB
        select DVB_TDA10086 if !DVB_FE_CUSTOMISE
        select DVB_LNBP21 if !DVB_FE_CUSTOMISE
        select DVB_TDA826X if !DVB_FE_CUSTOMISE
        help
          Say Y here to support the Pinnacle 400e DVB-S USB2.0 receiver. The
          firmware protocol used by this module is similar to the one used by the
          old ttusb-driver - that's why the module is called dvb-usb-ttusb2.

The select-parts will also configure the frontends needed by that driver if you select it. As you can see, there is no line for the tda10023 frontend module. Long story short: I added it, tried that, checked dmesg, noticed more missing frontends, and added them, too:

Code: Select all

config DVB_USB_TTUSB2
        tristate "Pinnacle 400e DVB-S USB2.0 support"
        depends on DVB_USB
        select DVB_TDA10023 if !DVB_FE_CUSTOMISE
        select DVB_TDA10048 if !DVB_FE_CUSTOMISE
        select DVB_TDA10086 if !DVB_FE_CUSTOMISE
        select DVB_LNBP21 if !DVB_FE_CUSTOMISE
        select DVB_TDA826X if !DVB_FE_CUSTOMISE
        help
          Say Y here to support the Pinnacle 400e DVB-S USB2.0 receiver. The
          firmware protocol used by this module is similar to the one used by the
          old ttusb-driver - that's why the module is called dvb-usb-ttusb2.

Funny part is: If I load the dvb_usb_ttusb2-module, it doesn't load tda10086 or lnbp21 or tda826x. I don't need those frontends but Kconfig selects them for me. Also: dmesg is crying about one last frontend it can't load:

Code: Select all

[    9.546346] DVB: Unable to find symbol tda827x_attach()

And that frontend, ladies and gentlemen, is missing. If you check your /usr/src/linux/drivers/media/dvb/frontends folder, you'll find all the frontends above configured by Kconfig... but not tda827x. So I guess that is what you call a kernel bug, isn't it?

I think, transsib is facing similar frontend selecting problems with his card. I will now check the 3.7 sources as jamatik suggested, hopefully it will contain my missing frontend and a better Kconfig file.

Edit:
Ah, forget to tell you, I also use gentoo-sources.

Edit2:
Same problem in the 3.7 sources. Oh and I also checked 3.4 which are also missing those files. Guys, it is officially now: I have no idea why it worked in the first place. I checked the source of the driver module itself (ttusb2.c):

Code: Select all

#include "dvb-usb.h"

#include "ttusb2.h"

#include "tda826x.h"
#include "tda10086.h"
#include "tda1002x.h"
#include "tda10048.h"
#include "tda827x.h"
#include "lnbp21.h"
/* CA */
#include "dvb_ca_en50221.h"

It seems that tda10021.c and tda10023.c uses the tda1002x.h file so this seems legit. But tda827x.h? Then I did a locate on that file and guess what? It's not in the frontend folder but somewhere else (/drivers/media/common/tuners/ on my other machine which uses the tuxonice-sources, I currently have no access to my htpc because my wife uses it now. But I think it will be in the gentoo-sources somewhere there, too). So it seems that the ttusb2 driver (and maybe some other dvb drivers) are a total mess with their Kconfig setup selecting necessary frontends...

[EasterParade]

I´d rather revive a quasi-dead thread than creating a new one with the same subject - so bear with me please.

DarkSpir already pointed out what bugs me most about the newer kernels: the missing frontends although I am not certain whether or not this
causes our issues.
First of all with "make menuconfig" I dont´ get any frontends for dvb cards on pci bus. With "make xconfig" I do: what´s wrong here?

The card is fine as lspci -v tells:

Code: Select all

06:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
        Subsystem: KNC One Device 0022
        Flags: bus master, medium devsel, latency 64, IRQ 10
        Memory at febffc00 (32-bit, non-prefetchable) [size=512]

and on Windows it works perfecly.

No devices are being created although the modules are being loaded and used:

Code: Select all

lsmod
Module                  Size  Used by
budget                 13851  0 
budget_core             7133  1 budget
saa7146                11191  2 budget,budget_core
ttpci_eeprom            1918  1 budget_core
dvb_core               86547  2 budget,budget_core

At least I´ve solved the frontend issue now but still kaffeine finds no device cause ther is no device.

But kaffeine just does not find any device. If I start kaffeine on console I get this error message:

Code: Select all

kaffeine
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

And when I start dvb I only get "no device found" and nothing on console and dmesg doesn´t help at all.

I suspect dbus and kde again here but I´ve never learned how to troubleshoot that.

My impression is that a lot of people have jumped the gentoo-ship lately and that nobody cares anymore ...

However I´ll give it another try now and I´ll do so until I´ve found a solution --- I´ll be damned if I don´t find one

[chomber]

I have a same problem and looking for a solution :(

[EasterParade]

Welcome chomper
Either the kernel or udev simply does not create the device. There is no device, really.
With the 3.6.* and 3.7.* kernel the system does not create the device.
I try to get it working for weeks now without success and it DRIVES - ME - CRAZY
and I do not understand why those specialists for kernel and system ( udev, dbus etc )
don´t know about this.
It may be a minimal, trivial issue....

[Jaglover]

My 2c. Try starting from scratch, make mrpoper; make nconfig. Weird things can happen when stuff is moved in kernel tree.

[EasterParade]

@Jaglover I´ll take your 2c but didn´t you mean "config"
mrporper is a rather radical tool but may be better than make clean.

[chomber]

Well, I don't think it helps as modules are build and even loaded
dvr ~ # lsmod
Module Size Used by
budget 12955 0
budget_core 6253 1 budget
ttpci_eeprom 1710 1 budget_core
saa7146 9431 2 budget,budget_core
dvb_core 74934 2 budget,budget_core

dvr ~ # lspci
...
04:03.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
04:04.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

but no devices
dvr ~ # ls -lrt /dev/dvb*
ls: cannot access /dev/dvb*: No such file or directory

well it could be udev as trassib mentioned? becomes out of my knowledge area...

[Jaglover]

Look, I had similar issue with my WinTV HVR-2250. It took a while to figure out all the options I had to enable after kernel upgrade. You are missing something, that's why device nodes are not created.

@transsib: I meant nconfig, but if you like config more be my guest.

This is the config from my MythTV backend server: http://bpaste.net/show/71614/

[chomber]

well, honestly i don't know what was the fix as I made some kernel config changes and also recompiled the kernel with clean and mrproper but now I have one of the devices appearing. Still the second one is missing...

dvr ~ # dmesg |grep DVB
[ 27.207605] DVB: registering new adapter (Terratec Cinergy 1200 DVB-C)
[ 27.576522] budget_av 0000:04:04.0: DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)...
dvr ~ #
dvr ~ #
dvr ~ #
dvr ~ # ls -lrt /dev/dvb/
total 0
drwxr-xr-x 2 root root 140 Jan 21 22:15 adapter0

[EasterParade]

Right - there is some little thingy that´s missing for udev to create the devices.

The box that has the issue is not mine but my hubbys´ - he has the KNC One DVB-C
PCI card that worked effortlessly until the kernels 3.6.* hit the market.
I need to discuss it with him whether he allows me to make a mrproper make nconfig in his /usr/src/linux directory.
I need to get him to go through with it first but I also think that it´s the only straw left to kling on.

I´ll post if and when I succeed here

[EasterParade]

I was partially successful with mrproper. There is a directory dvb in dev and there is a adapter0 in
there now.
But kaffeine still does not find a device: back to the drawing board

[chomber]

I have similar experience. I got it once or few times to showed up in dev but only one of the adapters and it still didn't worked in tvheadend. I've been playing with different kernels up to latest and vanilla, build in kernel and modules, tried to disable kernel feature to autoselect frontend modules to build but no difference. This far I have been using genkernel but mayby I try one more time building from scratch.

[EasterParade]

I´ve got it now
Yippie
After some more kernel tweaking and a recompile of world
kaffeine finally used adapter0; my hubby is glad and I am both
proud and relieved that I haven´t promised too much when I told him I could fix it.

Thanks Jaglover

@chomper
What does lspci -v say about your two devices?

[chomber]

04:03.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH DVB C-1500
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at ff5ff400 (32-bit, non-prefetchable) [size=512]

04:04.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: TERRATEC Electronic GmbH Terratec Cynergy 1200C
Flags: bus master, medium devsel, latency 64, IRQ 10
Memory at ff5ff000 (32-bit, non-prefetchable) [size=512]

[EasterParade]

@chomber
You have 2 cards and each has the same Phillips chip?
What about the module? Is it the same too?

I´m not certain if this link might help as it is a german portal:
http://www.vdr-portal.de/board60-linux/ ... 930f45ce4e

[chomber]

well I don't know exactly what was the fix but today I upgrade to latest vanilla kernel 3.7.6 and emerge latest updates and udev-scripts and both devices are working again!