You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. So it looks like the board is probed then module init reports no boards found. Is it possible the driver is being loaded twice? We are configuring a system here to try this.
Hi. So it looks like the board is probed then module init reports no boards found. Is it possible the driver is being loaded twice? We are configuring a system here to try this.
Hello, have you review the problem in your system? or has any way to fix the problem?
Hi. Yes, I can load the ntv2-v4l2 driver. I took another look at your log and should have noticed right away that the first driver loaded is the NTV2 SDK ajantv2 driver. This is not the v4l2 driver and is not required to use the v4l2 driver. Do a "sudo rmmod ajantv2" and then try "sudo make load" to load the v4l2 ntv2video driver. Hopefully this will fix the problem.
I use centos 7.6 (x64) and update kernel to 4.4.196-1.el7.elrepo.x86_64
I build the driver successfully, and run ./load with root
but failed for load my card corvid88 for v4l2.
dmesg show following message, how to fix the problem?
... ...
[ 2.232842] ntv2dev0: detected device CORVID88
[ 2.232944] ntv2dev0: serial number not programmed
[ 2.233038] ntv2dev0: firmware version 2019/05/17 10:42:10
[ 2.233133] ntv2dma0: dmaInit begin
[ 2.233481] ntv2dma0:nwl0: dmaInit configure max vid 67108864 aud 4194304 anc 262144
[ 2.234087] ntv2dma0:nwl0: dmaHardwareInit present
[ 2.234448] ntv2dma0:nwl0: dmaInit configure hardware
[ 2.234795] ntv2dma0:nwl0:h2c0: dmaInit configure dma context
[ 2.235297] ntv2dma0:nwl0:h2c1: dmaInit configure dma context
[ 2.236017] ntv2dma0:nwl0: dmaInit initialization succeeded
[ 2.236362] ntv2dma0:nwl1: dmaInit configure max vid 67108864 aud 4194304 anc 262144
[ 2.236965] ntv2dma0:nwl1: dmaHardwareInit present
[ 2.237319] ntv2dma0:nwl1: dmaInit configure hardware
[ 2.237660] ntv2dma0:nwl1:c2h0: dmaInit configure dma context
[ 2.238150] ntv2dma0:nwl1:c2h1: dmaInit configure dma context
[ 2.238866] ntv2dma0:nwl1: dmaInit initialization succeeded
[ 2.239206] ntv2dma0:nwl2: dmaInit configure max vid 67108864 aud 4194304 anc 262144
[ 2.239814] ntv2dma0:nwl2: dmaHardwareInit present
[ 2.240167] ntv2dma0:nwl2: dmaInit configure hardware
[ 2.240509] ntv2dma0:nwl2:h2c0: dmaInit configure dma context
[ 2.240997] ntv2dma0:nwl2:h2c1: dmaInit configure dma context
[ 2.241720] ntv2dma0:nwl2: dmaInit initialization succeeded
[ 2.242077] ntv2dma0:nwl3: dmaInit configure max vid 67108864 aud 4194304 anc 262144
[ 2.242671] ntv2dma0:nwl3: dmaHardwareInit present
[ 2.243018] ntv2dma0:nwl3: dmaInit configure hardware
[ 2.243371] ntv2dma0:nwl3:c2h0: dmaInit configure dma context
[ 2.243851] ntv2dma0:nwl3:c2h1: dmaInit configure dma context
[ 2.244556] ntv2dma0:nwl3: dmaInit initialization succeeded
[ 2.244914] ntv2dma0: dmaInit end
[ 2.245281] ntv2dev0: enable video interrupts
[ 2.245631] ntv2dev0: enable nwl dma interrupts
[ 2.245979] ntv2dev0: probe end
[ 2.246367] ntv2mod: register chrdev ajantv2
... ...
... ...
[54355.772023] ntv2video: module init version 1.2.2
[54355.772099] ntv2video: no ntv2 boards found
[54355.772100] ntv2video: module init complete
The text was updated successfully, but these errors were encountered: