Hi Everyone,
Since I moved a year ago to New Zealand I have much less time to keep my AUR packages maintained and keep my system tweaked. Arch Linux is just too bleeding edge to make a comfortable low maintenance multimedia server platform and I now need a server which will continue to run for years in a very boring reliable way without much input from me. Also the frequent surprises that happen when Arch updates to something new are not as fun as they should be. I recently made the switch to CentOS7 on my main server which is running FFdecsawrapper and will stay on a 3.10 kernel probably for the next 8 years.
This is the time for me to bow out as I can not longer test this package. So this package needs a new owner. I will miss the learning fun that ArchLinux has given me. But I'll keep a little fun as my remote frontends will still run Arch.
Search Criteria
Package Details: tbs-unofficial-dvb-drivers-git v150429-1
Package Actions
| Package Base: | tbs-unofficial-dvb-drivers-git |
|---|---|
| Description: | Unofficial TBS DVB drivers from L.J. Alves (forked to bas-t repo) + firmware from official TBS source |
| Upstream URL: | https://github.com/ljalves/linux_media/wiki |
| Category: | multimedia |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | p-we |
| Maintainer: | None |
| Last Packager: | p-we |
| Votes: | 1 |
| First Submitted: | 2014-06-06 14:17 |
| Last Updated: | 2015-04-30 08:12 |
Dependencies (6)
- git (make)
- linux-headers (make)
- patchutils (make)
- perl-proc-processtable (make)
- linuxtv-dvb-apps (optional) – handy DVB tools
- v4l-utils (optional) – hardware support for some cards
Required by (0)
Sources
Latest Comments
Comment by p-we
Comment by p-we
bas-t has asked for a last change in order for him to clean up his collection of GIT forks, repos etc. A small ask for his big contribution to TBS OS drivers (and of course FFdecsawrapper). Now building from arch branch of bas-t/media_tree and bas-t/media_build (replaces linux_media fork)
Important! You must still wipe all previous GIT directories and start fresh
Thanks to @bpbastos for testing 6285/6281.
Comment by bpbastos
Thank you @bas-t and @p-we for your help! It was much appreciated :)
Sorry for the off-topic
Bests
Comment by bas-t
@bpbastos
"It seems like my motherboard doesn't support msi interrupts."
Not true, it gives that for atleast 2 hours.
"irq 16: nobody cared (try booting with the "irqpoll" option)"
indicates that you are suffering from a badly designed chip and/or a badly designed driver.
In case a chip is bad (like some asmedia pci bridge chips) blacklisting the driver should solve your problem.
In case a driver is bad (like the r8169 driver) you should patch it, or try to get a non-offending version to compile into your kernel.
Luis Alves just reacted, make sure he knows about the "irq 16: nobody cared (try booting with the "irqpoll" option)" issue
This of course is way off topic here.
Comment by bpbastos
@bas-t
I've tried to blacklist he r8168 module and use instead r8169 and have also tried to disable my onboard lan and use an Intel 82574L but none of them solved the problem.
It seems like my motherboard doesn't support msi interrupts.
Comment by bpbastos
@bas-t
Thank you again for help me out!
Comment by bas-t
Your mobo has a RealtekĀ® 8111F-VL. If r8169 driver module is loaded for your lan chip it's p[robably the one that causes conflicts.
If so, use google to solve your issue.
Comment by bpbastos
@bas-t
I have a Gigabyte GA-B85M-D3PH and couldn't find any bios option to enable MSI.
I already tried int_type=2 but seem like it isn't supported, the interruptions map stay the same as using the default interruption type.
If I use int_type=2 or default for about 2 ~ 3 hours it gives me the infamous irq error in dmesg:
irq 16: nobody cared (try booting with the "irqpoll" option)
The only solution is to restart the tv server..
Comment by bas-t
Or maybe your mobo supports msi-x
What happens when you set 'int_type=2'?
Comment by bas-t
@bpbastos
Usually it's a BIOS thing. Some of them are not msi interrupt capable.
If you are in luck, you can find an option in the BIOS to set something like msi=enabled