dvb devices not created, and wrong module loaded?
 

Have pretty much got my new gentoo box up and running, however, am having trouble with the dvb.

using kernel 2.6.11 from recent gentoo sources (on amd64), and using udev

Firstly, the device nodes were not being created, (first noticed by fact that kaffeine did not bring up the dvb tab). there is no /dev/dvb/
have checked google, and found reference to udev rules and a dvb.sh script. These rules, and the script are both already in place.

checked that modules were being loaded, and got

Module Size Used by
fglrx 262144 7
budget 8896 0
l64781 7300 1 budget
ves1820 5892 1 budget
budget_core 8068 1 budget
saa7146 16000 2 budget,budget_core
ttpci_eeprom 2432 1 budget_core
stv0299 10180 1 budget
tda8083 5572 1 budget
ves1x93 6404 1 budget
dvb_core 79100 2 budget,budget_core
tda1004x 13572 0

Now, I think the issue here is that the tda8083 module is being used, when my hardware should be using the tda1004x (I know, because this is the same card as I used in my old 32bit athlon system - beside which tda8083 is dvb-s, and I have a dvb-t (winTV nova-T from easter 2004)). I never selected to compile the 8083 module, make menuconfig seemed to automatically do this when I selected the budget modules.

suggestions?

Does this script create the /dev/dvb stuff you need? http://dl.bytesex.org/misc/dvb-devices

It certainly creates the device nodes, but still leaves the problem of the wrong modules being loaded.
(the scan utility says that /dev/dvb/adaptor0/frontend0 there is no such device. Doesn't complain about the demux though).

am going to try 2.6.12 kernel with fingers crossed, but have seen atleast one site that has it working with 2.6.11, so don't see why that should be an issue.

well, kernel upgrade doesn't help.

Why would the kernel load the module for the wrong frontend in preference to the tda1004x?

okay, it seems that loading budget_ci rather than budget loads the appropriate modules.