ProGEEK
-
Posts
52 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ProGEEK
-
-
Still missing the cx23885 module.
And now that the 6.4* images have been removed I can't roll back to a working version
-
hey @CHBMB, Drivers for cx23885 seem to have gone again too, from both 6.5.2-rc2 and 6.5.2 - LibreELEC build
root@Daedalus:~# modprobe cx23885 modprobe: FATAL: Module cx23885 not found in directory /lib/modules/4.14.40-unRAID
-
On 07/11/2017 at 12:57 PM, ProGEEK said:
hey @CHBMB, Where did we get with the frame_vector module?
Does rc10b still have the same issue ?Just upgraded. yep it sure does
-
hey @CHBMB, Where did we get with the frame_vector module?
Does rc10b still have the same issue ? -
3 hours ago, CHBMB said:
sed -i -e 's/CONFIG_FRAME_VECTOR=y/CONFIG_FRAME_VECTOR=m/g' $D/kernel/.config
Would probably be the easiest way to achieve things is my guess. I can chat to LT about it, but this would be easy to implement. I'll run another build tonight which should then "modularise" things and see what happens if @ProGEEK can test
@CHBMB That latest version doesnt work for me.
You'll still need to update mm/Kconfig to allow frame_vector to be compiled as a module. as the Kconfig file defines that the frame_vector component is a boolean (See my patch)
Attached is the patch for just modifying mm/Kconfig -
They probably won't, since it's not required for anything relating to unRAID. As far as I know, it's only used by media modules
-
55 minutes ago, CHBMB said:
Hmmm, kernel changes with every Unraid release, and i generate a new .config each time.
Might be easier to replace CONFIG_FRAME_VECTOR=y with CONFIG_FRAME_VECTOR=m to be honest.
Should be relatively easy to achieve that in bash.
Might be just easier if you rebuild the bzimage every time.
So long as the code in /usr/src/whatever is the source that the unraid dev team use to build their kernel, it should be fine to use and we wont have to bother with the patch. -
New build working for me
-
6 minutes ago, CHBMB said:
Uploaded a new LibreELEC build with bzimage, if someone can confirm it works, we should be good.
root@matrix:~# dmesg | tail -n1 [ 57.174478] cx23885: cx23885 driver version 0.0.4 loaded@ProGEEK I'm up for the idea of the patch, one question, will this remain constant or will it require changing as Unraid changes kernel version?
It will work until either you edit the .config or the kernel changes for file mm/Kconfig
I could split the patch so each file is patched separately. or drop the .config from the patch and you just edit your .config to have CONFIG_FRAME_VECTOR=m
Then the patch would work until mm/Kconfig is updated, as the patch changes frame_vector to be able to be compiled as a module -
I've been doing all my devel in KVM which doesnt have the hardware
-
If you wanna provide a download to the bzimage when you're done (Should be all I need) i'll give it a spin and try to load the module
(You can try loading modules even if you dont have the hardware, the driver will load, it just wont do anything)
-
Just now, CHBMB said:
@ProGEEK I've just gone back through the thread to remind myself of who was having issues and with what card, every single one has been a Hauppage user. You my friend have just become the hero of the thread!
Well i'm not one to toot my own horn.. ( Who are we kidding, Hell yes I am! )
-
@Zan I've attached my frame_vector.ko file.
Can you please download this to your machine and runinsmod frame_vector.ko modprobe videobuf2_memops modprobe cx23885and see if your tuner springs to life ?
I'd do this myself, but my server isnt in a state where it can run the RC of unRAID right now.-
1
-
-
Attached my patch to my previous post (You're too quick at replying!
)
-
1
-
-
3 minutes ago, CHBMB said:
I like that option, but running a compile now, I'll upload it when it's finished and we can check it works.
And to be honest patching is out of my expertise, but you want to work on it, I'm all ears. My only concern with that approach is could there be anything else that's "missing" that others might need for their cards. Wondering if it's safer to just package up bzimage for each build?
I guess thats a call we'd have to make based on feedback from the public, if there is minimal, say 2-3 that are unrelated to frame_vector, then I think patch is the better road, if more, then yeah, complete kernel replacement - Have you had any other reports of cards suddenly not working as a result of the new unraid ?
Im already working on and testing a patch
EDIT: attached is my working patch to generate a frame_vector.ko in mm: mm/frame_vector.ko
As long as the patch exists in the root of the kernel tree before line 38 of you kernel-compile-module.sh script executes, it'll be patched-
1
-
-
Either that, or we include a patch as part of your build process to just compile frame_vector as a loadable kernel module and include it in the bzmodules
-
@CHBMB
Its not in the default unraid .config, but is in your one at https://mirror.linuxserver.io/unraid-dvb-rc/6-4-0-rc9f/stock/.config which looks correct to me.CONFIG_FRAME_VECTOR=y
Accompanying file is mm/KConfig
My best guess is the kernel being generated by the build proces isnt the kernel being included in bzimage -
@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
-
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
-
Yup, The linuxTV build has the exact same problem, which brings me back to my previous post
-
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)
-
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
-
Testing a build using Manjaro's .config file. see what that yeilds
-
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
)
[Plugin] Linuxserver.io - Unraid DVB
in Plugin Support
Posted · Edited by ProGEEK
Upgraded from 6.4.2 to 6.5.2 as all previous 6.5.x releases have given me issues
Im building the modules manually and i see that in your .config, CX23885 is disabled