Michael, Thanks for that pointer on VDR, I'll check it out.
I have built the drivers separately from the kernel, but I'm having some problems loading them. It's a bt878 card, so with the original kernel modules, my modules.autoload.d/kernel-2.6 looks like this:- # # Note that this file is for 2.6 kernels. # videodev bttv card=0x68 i2c_hw=1 dvb-core v4l1-compat dst #bt878 dvb-bt8xx However, if I try to load the new drivers, I get this:- teleputer build-2.6 # modprobe videodev teleputer build-2.6 # modprobe bttv card=0x68 i2c_hw=1 teleputer build-2.6 # insmod dvb-core.o teleputer build-2.6 # modprobe v4l1-compat teleputer build-2.6 # insmod dst.o insmod: error inserting 'dst.o': -1 Unknown symbol in module I don't know if I'm loading them right! Any hints? Cheers, Jon > Hello Jon, > > On 16.03.2004 12:24, Jon Whitear wrote: >> I'm trying to compile the 1.1.1 drivers against a 2.6.1 kernel, becuase >> I'm getting the following error when compiling VDR (which I assume is >> because of old drivers) >> >> #error VDR requires Linux DVB driver API version 3! > > V3 is out for over 1,5 years. It's unlikely that you have such an old > driver... > > It's more likely that VDR simply doesn't find the required header files > or that it finds the wrong files. > > Grep through the source of VDR and find the place and the reason for the > error message. > >> I can compile the kernel with the built-in dvb drivers just fine, but >> when >> I use makelinks to link the newer drivers to the kernel and then >> compile, >> I get: > > I don't recommend to use "makelinks" anymore, because it messes with > your kernel source tree. Instead, build the driver outside of the kernel > with "build-2.6" directory. > > While you're at it, you can update to 2.6.4, too... 8-) > >> Thanks, >> Jon > > CU > Michael. > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
