Tim Bates wrote: > >> $ makelinks kernel-sorce directory.. >> After this i manually compile my kernel and install the standard kernel >> way of doing things .. >> To load the modules it would be just the same... To have a list of >> modules i have them at the wiki .. > > > Done that now... And still getting the exact same problem. > Everything looks fine until this: > "dvb-bt8xx: A frontend driver was not found for device 109e/0878 > subsystem 0000/0000" > have you compiled the dst module as described in linux/Documentation/dvb/bt8xx.txt ? This module is in fact responsible for interfacing your hardware to the dvb api. Does it happen everytime after a reset ? If you have compiled the modules ie from the latest dv-kernel CVS, dst and dst_ca both modules takes in 2 parameters for spewing out more info.. If you have compiled the module in, can you load the module with the debug and verbose module parameters to see what's going on ? verbose, takes in the level of verbosity you need, with a maximum of 5 debug, shows all the debugging related information with verbose=5 and debug=1, you would be seeing quite a lot of information what is going on.. if you are using an earlier version, dst_verbose, dst_debug, dst_ca_verbose, dst_ca_debug are the module parameters. The driver is currently under rapid development, and hence the newer additions might not reflect in the document at present.. But trying to keep up with the same to a very big extent. >> I don't see the confusing part.. > > > Confusing part was lack of instruction on how to actually do anything > with what you get from the CVS. I followed the supplied instructions and > didnt get anywhere. > You mean README-2.6 and README.bt8xx were insufficient in your case ? If you think that is insufficient, maybe we can add more details into it. > > > On another topic.... Why does this mailing list not set the reply > address to the list? > That's a good question .. Maybe this should be started off as a separate thread. So that others too can exchange their views.. Manu
