Hello,

 

it's great work you make there!

 

But I have a problem getting my USB DVB Card mounted to /dev/dvb/

 

I installed unRAID DVB Edition, rebooted my unRAID system. And looked for /dev/dvb/, but nothing.. What do I need to do?

 

dmesg: https://pastebin.com/6i5wvQcY

system devices: https://pastebin.com/BN3vLQz2 (see line 46)

 

I am using "Terratec cinergy hybrid T USB SX".

 

Thanks for any help!

Did you actually download a build? and then reboot?

@ProGEEK What laptop OS and uname?

@CHBMB I actually just installed the plugin and then rebooted. What build do you mean?

Sorry, I'm new to unRAID DVB Edition.

Have a read of the first post.

Ahh, I didn't know i can click the icon for the settings! Thank you.

 

But I have another problem now: my triple tv stick gets recognized for DVB-T, but I want to use DVB-C.. Can I change this?

 

Edit: I will try "TBS OpenSource", now I am using "LibreELEC"..

 

 

Edited September 27, 20178 yr by 3dee
lemme try something..

Not entirely sure exactly what stick you have but here's some info, can't see any of those that support dvb-c

https://www.linuxtv.org/wiki/index.php/TerraTec

@ProGEEK@Zan Can you try the CrazyCat build for RC9F amd see if that works?

31 minutes ago, CHBMB said:

Not entirely sure exactly what stick you have but here's some info, can't see any of those that support dvb-c

https://www.linuxtv.org/wiki/index.php/TerraTec

Damn, you're right.. That's the problem.. Thanks tho 

Ha! yeah, that would be an issue.

7 hours ago, CHBMB said:

@ProGEEK What laptop OS and uname?

Acer Predator 17 (2015 edition) Running Manjaro - Kernel: 4.12.14-1-MANJARO

Hmmm, same kernel version as Unraid....4.12.14-unRAID

5 hours ago, CHBMB said:

@ProGEEK@Zan Can you try the CrazyCat build for RC9F amd see if that works?

 

As near as I can tell, the only differences between the builds are the firmware files included, is this correct ?

The problem doesnt lie with the cx23885 module, but actually videobuf2.

Try loading the videobuf2_memops module, and thats what gives you the error. There are symbols missing from the kernel, and as far as I can tell, all the builds you have on the server all have an identical bzimage file

Edited September 27, 20178 yr by ProGEEK

No, the drivers are taken from a different media_build tree.

Testing a build using Manjaro's .config file. see what that yeilds

@ProGEEK I've just uploaded a test build with the media_build from linuxtv.org.  Can download it from the Unraid DVB plugin (right at the bottom of the list) 

1 hour ago, ProGEEK said:

Testing a build using Manjaro's .config file. see what that yeilds

 

Only issue with that is that .config will be specific to Manjaro's setup and may not include the other non-DVB drivers that Unraid requires.  I would be a little cautious with this approach tbh.

Just now, CHBMB said:

 

Only issue with that is that .config will be specific to Manjaro's setup and may not include the other non-DVB drivers that Unraid requires.  I would be a little cautious with this approach tbh.

I dont really care what drivers it includes, its the kernel itself im more interested in. To see what it has statically built in or not

Fair enough, I get where you're coming from now.

1 minute ago, CHBMB said:

Fair enough, I get where you're coming from now.

As far as I can tell, all the bzimage files generated by all the builds are identical (Size wise anyway) and none of them seem to include FRAME_VECTOR support, which is what videobuf2_memops requires to load. So im trying various ways of building the kernel to get these static functions compiled in (Cause they're configured to be compiled, but being seem to be getting ignored)

The only files that differ between any of the builds now is bzmodules and bzfirmware.  I have in the past (v6.3.5) generated bzimage, bzroot individually for each DVB build.  

Yup, The linuxTV build has the exact same problem, which brings me back to my previous post

Is maybe those methods compiled out into a module that hasn't been loaded, or does that not matter as all functions should be part of the symbol map?

Just now, BRiT said:

Is maybe those methods compiled out into a module that hasn't been loaded, or does that not matter as all functions should be part of the symbol map?

They're part of the symbol map, but not in the kernel itself which is weird. Im trying to compile as a standalone module, see what milage that produces

@CHBMB @Zan Its exactly as I suspected. Have confirmed frame_vector is not part of the kernel.

I compiled frame_vector as a kernel module, loaded it manually and now i have videobuf2_memops and cx23885 loading correctly.

So next step is, figure out why the he-double-hockysticks frame_vector isnt being compiled into the module statically as its supposed to be