Hello All,
I recently upgraded my Fedora 8 system kernel from 2.6.25.9 to
2.6.26.3. After a reboot, both of my DVB TT S-1401 cards disappeared.
Looking through /var/log/messages, I noticed that with kernel 2.6.25.x
my DVB drivers were loading somehow like this:
Sep 24 22:54:56 mythbackend kernel: saa7146: register extension 'budget dvb'.
Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt 0000:0b:09.0[A] -> GSI 18 (level, low) -> IRQ 18
Sep 24 22:54:56 mythbackend kernel: saa7146: found saa7146 @ mem f8a00000 (revision 1, irq 18) (0x13c2,0x1018).
Sep 24 22:54:56 mythbackend kernel: saa7146 (0): dma buffer size 192512
Sep 24 22:54:56 mythbackend kernel: DVB: registering new adapter (TT-Budget-S-1401 PCI)
Sep 24 22:54:56 mythbackend kernel: adapter has MAC addr = 00:d0:5c:61:4c:67
Sep 24 22:54:56 mythbackend kernel: DVB: registering frontend 0 (Philips TDA10086 DVB-S)...
Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> IRQ 17
Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt 0000:0b:0b.0[A] -> GSI 19 (level, low) -> IRQ 19
Sep 24 22:54:56 mythbackend kernel: saa7146: found saa7146 @ mem f8c36400 (revision 1, irq 19) (0x13c2,0x1018).
Sep 24 22:54:56 mythbackend kernel: saa7146 (1): dma buffer size 192512
Sep 24 22:54:56 mythbackend kernel: DVB: registering new adapter (TT-Budget-S-1401 PCI)
Sep 24 22:54:56 mythbackend kernel: adapter has MAC addr = 00:d0:5c:0b:01:2d
Sep 24 22:54:56 mythbackend kernel: DVB: registering frontend 1 (Philips TDA10086 DVB-S)...
And with kernel 2.6.26.3 I could only see this:
Sep 24 22:48:54 mythbackend kernel: ACPI: PCI Interrupt 0000:0b:09.0[A] -> GSI 18 (level,low) -> IRQ 18
Sep 24 22:48:54 mythbackend kernel: Audiowerk 2 sound card (saa7146 chipset) detected and managed
Sep 24 22:48:54 mythbackend kernel: ACPI: PCI Interrupt 0000:0b:0b.0[A] -> GSI 19 (level, low) -> IRQ 19
Sep 24 22:48:54 mythbackend kernel: Audiowerk 2 sound card (saa7146 chipset) detected and managed
Sep 24 22:48:54 mythbackend kernel: input: PC Speaker as /class/input/input5
Sep 24 22:48:54 mythbackend kernel: saa7146: register extension 'budget dvb'.
And that's it. No more mention of dvb, saa7146 or TDA10086.
I wonder what "Audiowerk 2 sound card" has to do with my DVB card... I
didn't have these messages in previous kernel. So I checked with
'lspci -v' and noticed that the newer kernel loads some "snd-aw2"
module, which interferes with the DVB drivers.
Here's what 'lspci -v' showed about my DVB-S cards in kernel 2.6.25.9:
0b:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH DVB S-1401
Flags: bus master, medium devsel, latency 123, IRQ 18
Memory at f0221000 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: budget dvb
Kernel modules: budget
0b:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH DVB S-1401
Flags: bus master, medium devsel, latency 123, IRQ 19
Memory at f0221400 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: budget dvb
Kernel modules: budget
And this is what 'lspci -v' shows about my DVB-S cards in kernel 2.6.26.3:
0b:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH DVB S-1401
Flags: bus master, medium devsel, latency 123, IRQ 18
Memory at f0221000 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: Emagic Audiowerk 2
Kernel modules: budget, snd-aw2
0b:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH DVB S-1401
Flags: bus master, medium devsel, latency 123, IRQ 19
Memory at f0221400 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: Emagic Audiowerk 2
Kernel modules: budget, snd-aw2
So the problem was easily solved by adding the line:
blacklist snd-aw2
to /etc/modprobe.d/blacklist
After a reboot, my DVB was back and running just fine (although I
didn't test it much yet).
I don't know if there's a problem somewhere, or it's a normal
behavior. But I hope this will help to the ones who faced a similar
issue.
--
Best regards,
Andrew
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
