<div dir="ltr">Thanks Stephen:<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 31, 2013 at 1:09 PM, Stephen Worthington <span dir="ltr"><<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have a TBS5922 USB DVB-S2 box, and I have never had any problems<br>
with the install, but I have been looking at automating it using dkms,<br>
so I have some idea of how it works. Your install procedure above<br>
looks fine to me, and I presume that you checked the output of the<br>
make and make install commands to see if there were any errors. </blockquote><div><br></div><div>I believe I did: it looked like a non-error exit, though I did not check the exit code.<br></div><div>I'll redo that and check very carefully...<br>
</div><div>...yes, make completed with exit code 0.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I would first suggest checking that the install did actually work.<br>
This should show the *.ko driver files installed in the correct spot:<br>
<br>
ls -al /lib/modules/`uname<br>
-r`/kernel/drivers/media/dvb/frontends/*tbs*<br>
<br>
This is what I get:<br></blockquote><div><br></div><div>Yes, I also get a similar bunch of files in the equivalent place for my kernel and card.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Check the files dates and make sure they match when you did the<br>
install, and that your tbs6981fe.ko is there. </blockquote><div><br></div><div>Yes and yes.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I am not sure if the<br>
TBS6981 needs a firmware file, but check to see if any have been<br>
installed:<br>
<br>
find /lib/firmware -iname "dvb-fe-cx24116.fw"<br>
find /lib/firmware -iname "*tbs*.fw"<br>
find /lib/firmware -iname "v4l-cx23885-avcore-01.fw"<br>
<br>
This is what I get:<br>
<br>
/lib/firmware/dvb-fe-cx24116.fw<br>
/lib/firmware/dvb-usb-tbsqbox-id5926.fw<br>
/lib/firmware/dvb-usb-tbsqbox-id5922.fw<br>
/lib/firmware/v4l-cx23885-avcore-01.fw<br></blockquote><div><br></div><div>Aha: here I only get the last one:<br>/lib/firmware/v4l-cx23885-avcore-01.fw<br><div><br></div>Note that at some point (before posting here) I found a place on the net that suggested copying that particular file (v4l-cx23885-avcore-01.fw) from the drivers package to /lib/firmware. I checked and found I already had a file by that name in /lib/firmware, but with a different md5sum. So I overwrote it with the one from the drivers package, by hand (cp). I don't have any /lib/firmware/tbs*fw and I have wome unrelated /lib/firmware/dvb*fw.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Check that the TBS hardware is actually visible to the system:<br>
<br>
lspci | grep -i tbs<br></blockquote><div><br></div><div>No, I get empty output here. What could I do?<br><br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Next, I would see what happens when you try to load the driver<br>
manually:<br>
<br>
modprobe tbs6981fe.ko<br></blockquote><div><br><br>FATAL: Module tbs6981fe.ko not found.<br> <br></div><div>Further suggestions gratefully received!<br></div></div></div></div>