KNC DVB-s

Also ich wollte jetzt mal meine KNC DVB-s unter Linux in gang setzen, dafür hab ich den 1.1.1er Treiber installiert, folgdendes steht im log, wenn ich die Treiber lade, unter CI werden nur meine beiden FF DVB-s erkannt, also nur 2 karten.

Jun 27 15:13:07 linux kernel: Linux video capture interface: v1.00
Jun 27 15:13:07 linux kernel: saa7146: register extension 'dvb'.
Jun 27 15:13:07 linux kernel: PCI: Found IRQ 9 for device 02:01.0
Jun 27 15:13:07 linux kernel: saa7146_core: found saa7146 @ mem d080c000 (revision 1, irq 9) (0x13c2,0x0000).
Jun 27 15:13:07 linux kernel: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3).
Jun 27 15:13:07 linux kernel: DVB: registering frontend 0:0 (VES1893)...
Jun 27 15:13:07 linux kernel: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 0 has MAC addr = 00:d0:5c:01:ce:d5
Jun 27 15:13:09 linux kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261c
Jun 27 15:13:09 linux kernel: DVB: AV7111(0) - firmware supports CI link layer interface
Jun 27 15:13:09 linux kernel: av7110(0): adac type set to 0
Jun 27 15:13:09 linux kernel: saa7146_fops: saa7146 (0): registered device video0 [v4l2]
Jun 27 15:13:09 linux kernel: av7110: found av7110-0.
Jun 27 15:13:09 linux kernel: PCI: Found IRQ 11 for device 02:03.0
Jun 27 15:13:09 linux kernel: saa7146_core: found saa7146 @ mem d0820800 (revision 1, irq 11) (0x13c2,0x0000).
Jun 27 15:13:09 linux kernel: DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3).
Jun 27 15:13:09 linux kernel: DVB: registering frontend 1:0 (VES1893)...
Jun 27 15:13:10 linux kernel: Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 1 has MAC addr = 00:d0:5c:1e:97:64
Jun 27 15:13:12 linux kernel: DVB: AV7111(1) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261c
Jun 27 15:13:12 linux kernel: DVB: AV7111(1) - firmware supports CI link layer interface
Jun 27 15:13:12 linux kernel: av7110(1): adac type set to 0
Jun 27 15:13:12 linux kernel: saa7146_fops: saa7146 (1): registered device video1 [v4l2]
Jun 27 15:13:12 linux kernel: av7110: found av7110-1.
Jun 27 15:13:12 linux kernel: saa7146: register extension 'budget dvb'.
Jun 27 15:13:12 linux kernel: saa7146: register extension 'budget_ci dvb'.
Jun 27 15:13:12 linux kernel: saa7146: register extension 'budget dvb /w video in'.
Jun 27 15:13:12 linux kernel: PCI: Found IRQ 9 for device 02:02.0
Jun 27 15:13:12 linux kernel: saa7146_core: found saa7146 @ mem d0845400 (revision 1, irq 9) (0x1131,0x4f56).
Jun 27 15:13:12 linux kernel: DVB: registering new adapter (KNC1 DVB-S).
Jun 27 15:13:13 linux kernel: KNC1 DVB-S adapter 2 failed MAC signature check
Jun 27 15:13:13 linux kernel: encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
Jun 27 15:13:13 linux kernel: budget_av: budget_av_attach(): cannot init saa7113.
Jun 27 15:13:13 linux kernel: usb.c: registered new driver Technotrend/Hauppauge USB-Nova
Jun 27 15:13:13 linux kernel: usb.c: registered new driver ttusb-dec

ok, imzw. läuf sie mit den treibern, allerdings beim start vom vdr kommt folgendes:

Jun 27 17:02:02 linux vdr[1289]: probing /dev/dvb/adapter0/frontend0
Jun 27 17:02:02 linux vdr[1292]: tuner on device 1 thread started (pid=1292, tid=16386)
Jun 27 17:02:02 linux vdr[1293]: Section handler thread started (pid=1293, tid=32771)
Jun 27 17:02:02 linux vdr[1289]: probing /dev/dvb/adapter1/frontend0
Jun 27 17:02:02 linux kernel: Unable to handle kernel paging request at virtual address 1501006f
Jun 27 17:02:02 linux kernel: printing eip:
Jun 27 17:02:02 linux kernel: c3c2c5b9
Jun 27 17:02:02 linux kernel: *pde = 00000000
Jun 27 17:02:02 linux kernel: Oops: 0000 2.4.21-226-default #1 Tue Jun 15 10:44:28 UTC 2004
Jun 27 17:02:02 linux kernel: CPU: 0
Jun 27 17:02:02 linux kernel: EIP: 0010:[usb-uhci:uhci_device_operations+17985345/31064644] Not tainted
Jun 27 17:02:02 linux kernel: EIP: 0010:[<c3c2c5b9>] Not tainted
Jun 27 17:02:02 linux kernel: EFLAGS: 00010282
Jun 27 17:02:02 linux kernel: eax: c5ad1f1e ebx: 15010000 ecx: 00000002 edx: 00000068
Jun 27 17:02:02 linux kernel: esi: c41df280 edi: c43dc0a4 ebp: c5ad1f20 esp: c5ad1f28
Jun 27 17:02:02 linux kernel: ds: 0018 es: 0018 ss: 0018
Jun 27 17:02:02 linux kernel: Process kdvb-fe-1:0 (pid: 1294, stackpage=c5ad1000)
Jun 27 17:02:02 linux kernel: Stack: c5ad1f1e 00000000 00000000 00000000 00000020 c2914a60 00000001 c43dcb77
Jun 27 17:02:02 linux kernel: c41df280 00000001 00000015 c34b4c04 00000000 00007651 c43c51c5 c41df280
Jun 27 17:02:02 linux kernel: 00000001 00000000 c34b4c04 00000001 c34b4db0 c43c576f c34b4c04 00007651
Jun 27 17:02:02 linux kernel: Call Trace: [usb-uhci:uhci_device_operations+26047743/23002246] (28) [usb-uhci:uhci_device_operations+25951053/23098936] (28) [usb-uhci:uhci_device_operations+25952503/23097486] (20)
Jun 27 17:02:02 linux kernel: Call Trace: [<c43dcb77>] (28) [<c43c51c5>] (28) [<c43c576f>] (20)
Jun 27 17:02:02 linux kernel: [usb-uhci:uhci_device_operations+25953752/23096237] (44) [ret_from_fork+6/32] (12) [usb-uhci:uhci_device_operations+25953640/23096349] (40) [arch_kernel_thread+35/48] (08)
Jun 27 17:02:02 linux kernel: [<c43c5c50>] (44) [<c0108dc6>] (12) [<c43c5be0>] (40) [<c0107333>] (08)
Jun 27 17:02:02 linux kernel: [usb-uhci:uhci_device_operations+25953640/23096349] (04)
Jun 27 17:02:02 linux kernel: [<c43c5be0>] (04)
Jun 27 17:02:02 linux kernel: Modules: [(stv0299:<c43dc060>:<c43de56c>)] [(dvb-core:<c43c0060>:<c43c9a38>)]
Jun 27 17:02:02 linux kernel: Code: 33 53 6f 75 72 63 65 73 00 5f 5a 4e 31 35 63 50 6c 61 79 6c

lange rede, kurzer sinn, jetzt läuft es

Für alle anderen, die evtl. auch mal dieses Problem haben sollten:

in der insmod.sh die USB Devices auskommentieren