I can not get working my new Gigabyte GA-970A-DS3P motherboard with two PCI cards (Hauppauge PVR-150, Skystar 2). During boot I get these error messages (part of dmesg):
0.227977] pci 0000:04:07.0: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227981] pci 0000:04:07.1: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227984] pci 0000:04:07.2: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227988] pci 0000:04:07.3: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227991] pci 0000:04:07.4: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227995] pci 0000:04:07.5: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.227998] pci 0000:04:07.6: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
0.228001] pci 0000:04:07.7: can’t claim BAR 0 [mem 0x00800000-0x00ffffff pref]: no compatible bridge window
(These are for the Hauppauge TV card. Skystar2 is present but can not tune to any channel.)
It seems to me like a kernel problem, some conflict between the memory management of the motherboard and the linux kernel.
OpenSUSE 13.2 x64,
Linux 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
It’s actually most likely broken BIOS implementation that the kernel exposes. Do you have the latest BIOS / firmware for your motherboard installed?
The Hauppauge card can tune? Did you remember to manually download and insert the Skystar firmware into /lib/firmware, especially if it’s the S2 model.
Hauppauge:
The ivtv module is not loaded on boot, and if I do “modprobe ivtv”, I get this at the end of dmesg:
300.181611] Linux video capture interface: v2.00
300.367060] ivtv: Start initialization, version 1.4.3
300.367153] ivtv: End initialization
But no video or vbi device. The Hauppauge firmware files are in /lib/firmware.
SkyStar 2:
This is the dmesg output after removing and then modprobing the modules:
1733.270945] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
1733.273294] flexcop-pci: will use the HW PID filter.
1733.273300] flexcop-pci: card revision 2
1733.276980] DVB: registering new adapter (FlexCop Digital TV device)
1733.280965] b2c2-flexcop: MAC address = 00:d0:d7:02:ce:2c
1733.281477] CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
1733.281480] CX24123: wrong demod revision: 87
1733.482336] b2c2-flexcop: found ‘ST STV0299 DVB-S’ .
1733.482354] b2c2_flexcop_pci 0000:04:06.0: DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)…
1733.485205] b2c2-flexcop: initialization of ‘Sky2PC/SkyStar 2 DVB-S rev 2.6’ at the ‘PCI’ bus controlled by a ‘FlexCopIIb’ complete
I have downloaded a firmware file (dvb-fe-cx24120-1.20.58.2.fw), but this card worked in an other motherboard without it. And I see the “wrong demod revision”, but I can not recall if it was a problem before. It was a working configuration in an other motherboard.
You might get it working with pci=nocrs as a linux kernel parameter (you can try it by adding it via YAST -> System -> Boot Loader -> Kernel Parameters -> and add it to the end of Optional Kernel Command Line Parameters, OK and Reboot). It’s a really old failsafe trick from Days of Old when ACPI was a real pain in the ass.
However nocrs comes with some other issues, it’s worth a shot though.
Flashed it, but for the PVR-150 board nothing changed. The Skystar2 board now works, I do not know if because of the flashing of the BIOS or because of any other fiddling.
Anyhow, the problem is narrowed down to the PVR-150 card.
Swapping the two cards had some result: the SkyStar 2 still works, and the PVR-150 recognized. (Appears in the lspci list.)
However, the PVR-150 still did not work and I decided to replace the motherboard with an older one in this box, and this seems to solve my problem for now.