September 24, 20178 yr If it's a driver issue then it's an upstream problem I'm afraid, nothing LT or LimeTech can do about it.
September 24, 20178 yr 1 minute ago, CHBMB said: cx23885 present in the release? I'm afk at the moment so can't check. @CHBMB Yeah the driver is there: root@USS-Enterprise:~# find /lib/modules/4.12.14-unRAID | grep cx23885 /lib/modules/4.12.14-unRAID/kernel/drivers/media/pci/cx23885 /lib/modules/4.12.14-unRAID/kernel/drivers/media/pci/cx23885/altera-ci.ko.xz /lib/modules/4.12.14-unRAID/kernel/drivers/media/pci/cx23885/cx23885.ko.xz Just throws a dirty error when trying to load it
September 24, 20178 yr Problem is Hauppage only explicitly support Ubuntu, not even sure where to report an error.
September 24, 20178 yr 4 minutes ago, CHBMB said: Problem is Hauppage only explicitly support Ubuntu, not even sure where to report an error. @CHBMB I did find this: https://patchwork.kernel.org/patch/9717037/ Unsure if it is related, the videobuf2_memops errors are exactly the same, So I wonder if the solution they suggest would work (Enable VB2). Am happy to test if you want to provide me a test build Edited September 24, 20178 yr by ProGEEK
September 24, 20178 yr @CHBMB Its my primary operating system (Manjaro - The complete manual process of Arch gives me a headache) (I use windows for gaming, about it) Im a Server/Network/Database admin for work managing a fleet of 16 CentOS servers, so you tell me I'd say pretty familiar
September 24, 20178 yr Any chance I can get you on board with this then? I'm pretty time poor at the moment, and debugging cards that I don't own is a major pain in the ass. Compiling the kernel for the LibreELEC build involves two scripts. 1. https://github.com/CHBMB/Unraid-DVB/blob/master/build_scripts/kernel-compile-module.sh 2. https://github.com/CHBMB/Unraid-DVB/blob/master/build_scripts/libreelec-module.sh Now when you look at them please bear in mind I don't actually work with Linux/computers at all. So go easy on me!
September 24, 20178 yr @CHBMB My only question is where do I run these scripts from (From UnRaid or can it be from any linux machine? If so, which OS do you build them from (Might be best if I replicate how you're building them)) and in any particular order? Edited September 24, 20178 yr by ProGEEK
September 24, 20178 yr You run them on your Unraid machine, with a stock install of rc9f, would recommend running them on the cache drive. Run kernel compile first then libreelec.
September 24, 20178 yr Had some issues with the script (Some packages out of date, have manually updated them and so far build is progressing. So must be doing SOMETHING right
September 24, 20178 yr 6 minutes ago, CHBMB said: Packages are pulled from Slackware current, so shouldn't be out of date. the FILE_LIST my build seems to be pulling is out of date (Must be a mirror out of sync) I managed to get a build done, but it caused my server to hose itself - Parity drive went nuts - Do you having this running in a test env for your builds? e.g. a test/dev version of unraid or do you build these on your live server ? Edited September 24, 20178 yr by ProGEEK
September 24, 20178 yr I wonder is LimeTech will give us a test license (1 disk in array) for developing - Since a trial license only lives for so long. REALLY not comfortable doing this on my live machine (I already have a failed drive im trying to replace, dont want my parity to disappear )
September 24, 20178 yr If it's just a matter of enabling vb2 in the kernel I can give it a go when my wife isn't watching TV. Just realised kernel_compile.sh won't work for you without hashing out line 44, otherwise it'll pull the .config I used to make the build from the linuxserver file server. Got no idea where to find vb2 in the setup though.
September 24, 20178 yr Just tried the script here without issues, pulled required dependencies and running it on my cache drive without problems. Dunno why it wouldn't work for you.
September 24, 20178 yr @ProGEEK & @Zan Try replacing bzmodules and bzfirmware of the current LibreELEC rc9f release with the ones in this zip file and reboot. See if that fixes the Hauppage issue. Edited September 24, 20178 yr by CHBMB
September 24, 20178 yr 6 hours ago, CHBMB said: @ProGEEK & @Zan Try replacing bzmodules and bzfirmware of the current LibreELEC rc9f release with the ones in this zip file and reboot. See if that fixes the Hauppage issue. No luck, Still getting the modprobe cx23885 errors from before. I'll try to build it as well, using your script @CHBMB, and just step through the media_build part to see what Mauro and Matthias are referring to in this https://patchwork.kernel.org/patch/9717037/ Might take me a few days, so I'll let you know how I go then.
September 27, 20178 yr On 9/25/2017 at 9:09 AM, Zan said: No luck, Still getting the modprobe cx23885 errors from before. I'll try to build it as well, using your script @CHBMB, and just step through the media_build part to see what Mauro and Matthias are referring to in this https://patchwork.kernel.org/patch/9717037/ Might take me a few days, so I'll let you know how I go then. I just can't figure it out. Have tried a few things including deleting of the compressed modules from the original kernel compile of kernel-compile-module.sh, as per https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers and still no luck. @ProGEEK, my process was to create a stock 6-4-0-rc9f USB stick using the unraid USB creator tool (https://forums.lime-technology.com/topic/59025-unraid-usb-creator-tool-version-01-beta/), then just ran the following steps: mkdir /unraid-dvb cd /unraid-dvb wget https://raw.githubusercontent.com/CHBMB/Unraid-DVB/master/user.scripts/scripts/unraid-dvb/script . sed -i -e 's/mnt\/disk1\//unraid-/g' script chmod +x script ./script sed '/libre/d' /unraid-dvb/build.sh | sed '/tbs-os/d' | sed '/dd-module/d' | sed '/upload/d' | sed '$ s/&& \//' > /unraid-dvb/build-new.sh chmod +x /unraid-dvb/build-new.sh #Remove compressed modules as per https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers for file in `find /lib/modules -name "*.ko"`; do if [[ -e $file.xz ]]; then rm $file.xz; fi; done /unraid-dvb/media-build-2017-09-20/make reload /unraid-dvb/media-build-2017-09-20/depmod -a rm /unraid-dvb/6-4-0-rc9f/tbs-crazy-dvbst/bzmodules mksquashfs /lib/modules/4.12.14-unRAID/ /unraid-dvb/6-4-0-rc9f/tbs-crazy-dvbst/bzmodules -keep-as-directory -noappend
September 27, 20178 yr Im working on a theory, but I have to wait for another build to complete (Im compiling on a trial dual core machine). I'll let you know if I come up with anything
September 27, 20178 yr Ok guys, keep at it, I'm also chatting to cvh over at libreelec about this and he's been helpful, and there's something else we can try, but I'm struggling a bit with free time at the moment but give me a week or so and hopefully I'll get a chance.
September 27, 20178 yr 38 minutes ago, CHBMB said: Ok guys, keep at it, I'm also chatting to cvh over at libreelec about this and he's been helpful, and there's something else we can try, but I'm struggling a bit with free time at the moment but give me a week or so and hopefully I'll get a chance. My Theory is that the compiled modules cannot find the symbols needed that are compiled into the kernel. These USUALLY live at /boot/System.map-$(uname -r)https://en.wikipedia.org/wiki/System.map#Filesystem_location I am testing a build by building the kernel, trying to load the module (With the System.map file missing) then im gonna move this file into position and see if there is a difference. I'm near the end of the build so will report back in an hour or so EDIT: Nope, No-go. As far as I can tell, FRAME_VECTOR isnt being included in the kernel, and im unsure why. root@Tower:/mnt/user/UnRAID/kernel# cat /proc/kallsyms | grep frame_vector_create root@Tower:/mnt/user/UnRAID/kernel# Run the same on my laptop: [rdavies@USS-Stargazer build]$ cat /proc/kallsyms | grep frame_vector_create ffffffff86223780 T frame_vector_create [rdavies@USS-Stargazer build]$ So need to work out why this isnt being included in the build when it is specified in the config Edited September 27, 20178 yr by ProGEEK
Archived
This topic is now archived and is closed to further replies.