-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
saa716xx_budget not created #156
Comments
Ignore the above, it needs a newer kernel. 4.2 fails but 4.8 is ok. |
Hi, I have the same problem but on Debian Jessie kernel 3.16.43-2. What is the resolution, when I don't want to upgrade kernel? I'v followed the install instructions, but the result is always same the driver is not build. Thanks |
6280 require cxd2820r driver, so need at least 4.4 kernel. |
Ok, I've upgraded the kernel to 4.9 and the build was successful. I can see a lot of continuity errors for one multiplex (others are ok). When I tune the multiplex directly on TV, there are no artifacts or visible problems. Do you have any hint what to check? Can it be problem of DVB API? Thanks |
What muxes you lock ? DVB-T, T2 or C ? |
DVB-T Current parameters: |
Try drivers from my media_build This forked from this repo |
I think, I used it ... according to install guide: git clone https://github.com/ljalves/media_build.git |
I am getting much better results when using your driver than proprietary TBS drivers, but this is only problem that bothers me :-(. |
I get this continuity errors at times on 2/4 tuners on a 6985, slightly crappy hardware I think. TBS claim it is a motherboard compatibility issue, have tried 2 completely different motherboards and still get the problem. If it is a compatibility issues it seems common and other cards don't suffer the problem so no prizes for guessing where the blame is. |
I think, you are right. Before reinstall, I had similar problem as now, sometimes could not tune two channels from one multiplex. The problem is gone, but continuity error appeared. Do you know how to use verbose parameter for the driver? |
is it the same problem (saa716x_budget not built) for TBS 6922 on a 4.4.0 kernel (ubuntu trusty) ? i did see the cxd2820r 4.6 kernel limitation during make but the 6922 does not use that one so i was hoping it would work.. i'm trying to build again from scratch, as i had a perl error when executing : the second build also "skipped" saa716x_budget, let me know if there's a way to use it on a 4.4 kernel -- solved -- the tuner seems to work fine with my tbs6922 card, also seems much faster than tbs Also my tvheadend 4.0.9-16~g63c1034 doesn't seem to report the SNR (0%) and signal strength correctly (99%), not a real problem i believe. and i yet have to test rmmod / suspend / modprobe |
Using Ubuntu 15.10 on the the newest 4.2 Kernel I don't seem to get the driver I need. Make output looks quite clean (Below is second run):
rob@TVHeadend:
/media_build/v4l$ ls /lib/modules/4.2.0-42-generic//kernel/drivers/media/pci/saa716x//media_build/v4l$ cd ..saa716x_core.ko saa716x_ff.ko saa716x_hybrid.ko
rob@TVHeadend:
rob@TVHeadend:~/media_build$ make
make -C /home/rob/media_build/v4l
make[1]: Entering directory '/home/rob/media_build/v4l'
creating symbolic links...
make -C firmware prep
make[2]: Entering directory '/home/rob/media_build/v4l/firmware'
make[2]: Leaving directory '/home/rob/media_build/v4l/firmware'
make -C firmware
make[2]: Entering directory '/home/rob/media_build/v4l/firmware'
make[2]: Nothing to be done for 'default'.
make[2]: Leaving directory '/home/rob/media_build/v4l/firmware'
Kernel build directory is /lib/modules/4.2.0-42-generic/build
make -C ../linux apply_patches
make[2]: Entering directory '/home/rob/media_build/linux'
Syncing with dir ../../media
Patches for 4.2.0-42-generic already applied.
make[2]: Leaving directory '/home/rob/media_build/linux'
make -C /lib/modules/4.2.0-42-generic/build SUBDIRS=/home/rob/media_build/v4l modules
make[2]: Entering directory '/usr/src/linux-headers-4.2.0-42-generic'
Building modules, stage 2.
MODPOST 656 modules
WARNING: "frame_vector_to_pages" [/home/rob/media_build/v4l/videobuf2-vmalloc.ko] undefined!
WARNING: "frame_vector_to_pfns" [/home/rob/media_build/v4l/videobuf2-vmalloc.ko] undefined!
WARNING: "frame_vector_create" [/home/rob/media_build/v4l/videobuf2-memops.ko] undefined!
WARNING: "frame_vector_destroy" [/home/rob/media_build/v4l/videobuf2-memops.ko] undefined!
WARNING: "get_vaddr_frames" [/home/rob/media_build/v4l/videobuf2-memops.ko] undefined!
WARNING: "put_vaddr_frames" [/home/rob/media_build/v4l/videobuf2-memops.ko] undefined!
WARNING: "frame_vector_to_pages" [/home/rob/media_build/v4l/videobuf2-dma-sg.ko] undefined!
WARNING: "frame_vector_to_pages" [/home/rob/media_build/v4l/videobuf2-dma-contig.ko] undefined!
WARNING: "frame_vector_to_pfns" [/home/rob/media_build/v4l/videobuf2-dma-contig.ko] undefined!
make[2]: Leaving directory '/usr/src/linux-headers-4.2.0-42-generic'
./scripts/rmmod.pl check
found 656 modules
make[1]: Leaving directory '/home/rob/media_build/v4l'
Try to use this with a TBS6985, it compiled on the same system with code from May2015 a few years ago. Since upgraded the kernel (With headers) and now cant seem to get it to detect the card. Any help appreciated.
The text was updated successfully, but these errors were encountered: