#linuxtv 2020-10-14,Wed

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***swegener has quit IRC (Quit: leaving) [05:55]
PriamXHiya. I'm new to digital TV, I just received my Hauppauge tuner today. I'm trying to set it up under Linux and running into some issue. Is there a forum where I may post questions? [06:06]
................................................................... (idle for 5h30mn)
***raidghost has quit IRC (Ping timeout: 246 seconds) [11:36]
............................................... (idle for 3h50mn)
b-radno forum, what's your issue PriamX? [15:26]
.............. (idle for 1h7mn)
PriamXOh, hey, hi b-rad. I'm doing the backport tree, I compiled it under kernel 3.10. Following the directions in a wiki article called "How to Obtain, Build and Install V4L-DVB Device Drivers", but I'm getting a lot of unknown symbols.
I tried the "make unload", and the "make load". The goal is to get the cx23885 driver working for Hauppauge WinTV-quadHD. I think it's ID "57".
This is on...CentOS 7.8 which does have the cx23885 driver, but only up to card id 39, so it fails to card id 0. So that's why I started down the route of compiling the backport tree.
I'm new to TV cards, but I do have some Linux skills. I've compiled the odd kernel module here and there for RAID cards, but this backport tree is pretty...extensive. ;)
[16:33]
b-radpaste the missing symbols somewhere, media_builld *should* work on 3.10--at least the parts you require [16:47]
PriamXLike the dmesg output when I do a make unload; make load?
That's where I'm seeing the error.
[16:48]
b-radyou used the standard "build" script? [16:51]
PriamXHowever, when I do a make unload; modprobe cx23885 I get a slightly different error. about v4l2_common disagreements.
Yes, just the straight build script.
[16:52]
b-radyeh i don't use that, i do the steps manually so I have control
you should have seen output about any missing symbols during the build process
[16:52]
PriamXI followed the Basic User's approach from this wiki article: https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers [16:53]
b-raddisagreements mean it's probably loading your original modules and not the new ones [16:53]
PriamXThat same page had a recommended 'find' command for looking for those conflicts. It didn't find any.
Let me poke around on that drivers/media directory and look with my own eyes.
[16:55]
Yeah, I found some interesting stuff. sec. Give me a moment to grok what I'm looking at.
A few things hanging around in there with .xz extensions. two duplicates: videobuf2-memops.ko(.xz) and videobuf2-vmalloc.ko(.xz)
There is also a videobuf2-core.ko.xz, but no updated replacement equivalent. Should there be a videobuf2-core.ko module?
Oh, same with v4l2-common.ko.xz
[17:02]
With the backport tree, should there be any original CentOS-provided modules in the drivers/media folders? Because I have 17 in there that came from the CentOS distro. Should I clean all of those out? [17:13]
b-radmedia_build is a complete replacement
compressed modules should be removed
[17:15]
PriamXIt looks like the 'make install' script cleans out any duplicate names with or without the .xz extension. But if it's not the same name, it doesn't touch them. [17:15]
b-radalong with all original modules [17:15]
PriamXOkay. Thanks.
It looks like I got 17 peices of CentOS junk in there that needs to come out.
[17:16]
...... (idle for 25mn)
I'm struggling a bit here. I've discovered I've never permanently removed a kernel module from Linux before. I'm assuming I can't just 'rm' the module file. And my Google-foo is failing me, I'm getting results explaining how to use 'rmmod', which just removes it from memory. How do I properly remove a kernel module from the filesystem? Or what search terms can I use to land me on the right
solution?
[17:41]
b-radrm and reboot?
or rmmod then rm
[17:42]
PriamXIs it that simple? I ask because poking around I found entries in modules.dep, entries like these:
"kernel/drivers/media/i2c/noon010pc30.ko: kernel/drivers/media/v4l2-core/v4l2-common.ko.xz kernel/drivers/media/v4l2-core/videodev.ko kernel/drivers/media/mc/mc.ko"
[17:43]
b-radwell you'll have to rerun depmod after putting all the new modules in place and cleaning out the old duff [17:44]
PriamXOkay.
ls
oops.
[17:45]
..... (idle for 22mn)
Well, that certainly fixed a lot. This aside from a few warnings about uninitialized variables, this is the only error I get:
[46851.641527] videobuf2_vmalloc: Unknown symbol dma_buf_export_named (err 0)
[18:07]
b-radthats unfortunate because the symbol exists in 3.10.108 [18:10]
PriamXWell, I did just take out all the remaining *.xz files under drivers/media...I wonder if it was in one of those. [18:11]
b-raddma-buf is in drivers/base i think [18:13]
PriamXDang, I didn't touch that section. [18:13]
b-radi think dma-buf is usually built-in anyways [18:14]
PriamXcrap... [18:14]
I could be wrong, but a couple days ago I thought I found some regression test output of media_build passing in 3.10.0...or perhaps it was just passing compile. I can't remember what I was looking at. [18:19]
......... (idle for 43mn)
Not that I expected any different, but the dma_buf_export_named symbol is NOT in any of the original CentOS 7.8 drivers/media modules I removed.
With CentOS 7.x being entirely based on the 3.10.0 kernel, it is true to say the media backport tree is not compatible with CentOS 7.x, however, likely compatible with CentOS 8.x (based on the 4.18 kernel)?
[19:02]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)