Hallo,
ich habe den Kernel 2.6.28.1 mal mit der HDe [hdshm.ko] und dem NetCeiver [dvbloop.ko] für S2API [VDR 1.7.0] getestet und habe das Problem. daß nach dem ersten VDR-Start noch keine Tuner vom NetCeiver geladen werden.
Zitatcreated new virtual DVB adapter: dvblo_adap0
Erst wenn ich noch einmal ein "stopvdr" und "startvdr" hinlege sind die Tuner vom NetCeiver geladen?
Wie ist eure Reihenfolge für den Start bzw. habet Ihre ein Beispielfür den Start?
1.) HDe
2.) DVB
3.) NetCeiver mit
30_netceiver.module
Habe auch schon ein dickes "sleep" zwischen den dvbloop und dem mcli gesetzt, aber keine Änderung - leider hilft nur einer zusätzlicher "startvdr" Aufruf.
kern.log
Jan 24 22:07:07 (none) kernel: [ 9.261375] tun: Universal TUN/TAP device driver, 1.6
Jan 24 22:07:07 (none) kernel: [ 9.261382] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 24 22:07:07 (none) kernel: [ 9.374396] hdshm_init_struct: Phys start f3000000, start f0680000, nc-start f0a00000
Jan 24 22:07:07 (none) kernel: [ 9.606808] hde_fb: init 1
Jan 24 22:07:07 (none) kernel: [ 9.606813] hde_fb: init_fb_info
Jan 24 22:07:07 (none) kernel: [ 25.046129] Linux video capture interface: v2.00
Jan 24 22:07:07 (none) kernel: [ 25.058644] saa7146: register extension 'budget_av'.
Jan 24 22:07:07 (none) kernel: [ 25.058782] budget_av 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jan 24 22:07:07 (none) kernel: [ 25.058896] saa7146: found saa7146 @ mem f067ec00 (revision 1, irq 22) (0x1894,0x001e).
Jan 24 22:07:07 (none) kernel: [ 25.058905] saa7146 (0): dma buffer size 192512
Jan 24 22:07:07 (none) kernel: [ 25.058909] DVB: registering new adapter (Satelco EasyWatch DVB-S light)
Jan 24 22:07:07 (none) kernel: [ 25.076965] adapter failed MAC signature check
Jan 24 22:07:07 (none) kernel: [ 25.076971] 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
Jan 24 22:07:07 (none) kernel: [ 25.308354] KNC1-0: MAC addr = 00:09:d6:65:8e:de
Jan 24 22:07:07 (none) kernel: [ 25.651077] DVB: registering adapter 0 frontend 845429219 (ST STV0299 DVB-S)...
Jan 24 22:07:07 (none) kernel: [ 25.652099] budget-av: ci interface initialised.
Jan 24 22:07:07 (none) kernel: [ 35.690281] dvblo: dvblo_chardev_init(): initializing char device with minor device number 0
Jan 24 22:07:07 (none) kernel: [ 35.690526] dvblo: dvblo_chardev_init(): added character device dvblo0
Jan 24 22:07:07 (none) kernel: [ 35.690531] dvblo: dvblo_chardev_init(): initializing char device with minor device number 1
Jan 24 22:07:07 (none) kernel: [ 35.690632] dvblo: dvblo_chardev_init(): added character device dvblo1
Jan 24 22:07:07 (none) kernel: [ 35.690637] dvblo: dvblo_chardev_init(): initializing char device with minor device number 2
Jan 24 22:07:07 (none) kernel: [ 35.690723] dvblo: dvblo_chardev_init(): added character device dvblo2
Jan 24 22:07:07 (none) kernel: [ 35.690728] dvblo: dvblo_chardev_init(): initializing char device with minor device number 3
Jan 24 22:07:07 (none) kernel: [ 35.690818] dvblo: dvblo_chardev_init(): added character device dvblo3
Jan 24 22:07:07 (none) kernel: [ 35.690823] dvblo: dvblo_chardev_init(): initializing char device with minor device number 4
Jan 24 22:07:07 (none) kernel: [ 35.690898] dvblo: dvblo_chardev_init(): added character device dvblo4
Jan 24 22:07:07 (none) kernel: [ 35.690901] dvblo: dvblo_chardev_init(): initializing char device with minor device number 5
Jan 24 22:07:07 (none) kernel: [ 35.690971] dvblo: dvblo_chardev_init(): added character device dvblo5
Jan 24 22:07:07 (none) kernel: [ 35.690975] dvblo: dvblo_chardev_init(): initializing char device with minor device number 6
Jan 24 22:07:07 (none) kernel: [ 35.691056] dvblo: dvblo_chardev_init(): added character device dvblo6
Jan 24 22:07:07 (none) kernel: [ 35.691061] dvblo: dvblo_chardev_init(): initializing char device with minor device number 7
Jan 24 22:07:07 (none) kernel: [ 35.691188] dvblo: dvblo_chardev_init(): added character device dvblo7
Jan 24 22:07:07 (none) kernel: [ 35.691196] dvblo: dvblo_init(): successfully initialized DVB Loopback Adapter Version 0.9.4-s2api
Jan 24 22:07:07 (none) kernel: [ 35.885852] EXT3 FS on sda3, internal journal
Jan 24 22:07:07 (none) kernel: [ 36.517305] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
Jan 24 22:07:07 (none) kernel: [ 36.786102] r8169: eth0: link up
Jan 24 22:07:07 (none) kernel: [ 37.116580] w83627ehf: Found W83627EHG chip at 0x290
Jan 24 22:07:07 (none) kernel: [ 37.138615] coretemp coretemp.0: Using relative temperature scale!
Jan 24 22:07:07 (none) kernel: [ 37.138676] coretemp coretemp.1: Using relative temperature scale!
Jan 24 22:07:08 (none) kernel: [ 37.179230] kjournald starting. Commit interval 5 seconds
Jan 24 22:07:08 (none) kernel: [ 37.180782] EXT3 FS on sda4, internal journal
Jan 24 22:07:08 (none) kernel: [ 37.180792] EXT3-fs: mounted filesystem with ordered data mode.
Jan 24 22:07:09 (none) kernel: [ 38.413320] lirc_dev: IR Remote Control driver registered, major 61
Jan 24 22:07:09 (none) kernel: [ 38.431436] lirc_imon: Driver for Soundgraph iMON MultiMedia IR/VFD, v0.3
Jan 24 22:07:09 (none) kernel: [ 38.431440] lirc_imon: Venky Raju <dev@venky.ws>
Jan 24 22:07:09 (none) kernel: [ 38.431470] lirc_imon: imon_probe: found IMON device
Jan 24 22:07:09 (none) kernel: [ 38.431476] lirc_dev: lirc_register_plugin: sample_rate: 0
Jan 24 22:07:09 (none) kernel: [ 38.431658] lirc_imon: imon_probe: Registered iMON plugin(minor:0)
Jan 24 22:07:09 (none) kernel: [ 38.431753] lirc_imon: imon_probe: iMON device on usb<5:2> initialized
Jan 24 22:07:09 (none) kernel: [ 38.431776] usbcore: registered new interface driver lirc_imon
Jan 24 22:07:09 (none) kernel: [ 39.067738] lirc_imon: VFD port opened
Jan 24 22:07:11 (none) kernel: [ 40.592870] lirc_imon: VFD port closed
Jan 24 22:07:12 (none) kernel: [ 41.554574] lirc_imon: VFD port opened
Jan 24 22:07:12 (none) kernel: [ 41.600566] lirc_imon: VFD port closed
Jan 24 22:07:12 (none) kernel: [ 41.940020] saa7146: unregister extension 'budget_av'.
Jan 24 22:07:12 (none) kernel: [ 41.945110] budget_av 0000:01:01.0: PCI INT A disabled
Jan 24 22:07:24 (none) kernel: [ 54.117233] NET: Registered protocol family 10
Jan 24 22:07:24 (none) kernel: [ 54.117679] lo: Disabled Privacy Extensions
Jan 24 22:07:24 (none) kernel: [ 54.117913] tun0: Disabled Privacy Extensions
Jan 24 22:07:25 (none) kernel: [ 54.392417] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
Jan 24 22:07:29 (none) kernel: [ 58.835861] vdr[6411]: segfault at 70616e73 ip b2d1a629 sp bfc42340 error 4 in libvdr-sndctl.so.1.7.0[b2d12000+1e000]
Jan 24 22:07:33 (none) kernel: [ 62.686402] Linux video capture interface: v2.00
Jan 24 22:07:33 (none) kernel: [ 62.702105] saa7146: register extension 'budget_av'.
Jan 24 22:07:33 (none) kernel: [ 62.702263] budget_av 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jan 24 22:07:33 (none) kernel: [ 62.702373] saa7146: found saa7146 @ mem f0d30c00 (revision 1, irq 22) (0x1894,0x001e).
Jan 24 22:07:33 (none) kernel: [ 62.702383] saa7146 (0): dma buffer size 192512
Jan 24 22:07:33 (none) kernel: [ 62.702387] DVB: registering new adapter (Satelco EasyWatch DVB-S light)
Jan 24 22:07:33 (none) kernel: [ 62.704088] adapter failed MAC signature check
Jan 24 22:07:33 (none) kernel: [ 62.704096] 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
Jan 24 22:07:33 (none) kernel: [ 62.936360] KNC1-0: MAC addr = 00:09:d6:65:8e:de
Jan 24 22:07:34 (none) kernel: [ 63.238648] DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)...
Jan 24 22:07:34 (none) kernel: [ 63.240127] budget-av: ci interface initialised.
Jan 24 22:07:35 (none) kernel: [ 64.654010] eth0: no IPv6 routers present
Jan 24 22:07:44 (none) kernel: [ 73.259388] dvblo: dvblo_chardev_init(): initializing char device with minor device number 0
Jan 24 22:07:44 (none) kernel: [ 73.260416] dvblo: dvblo_chardev_init(): added character device dvblo0
Jan 24 22:07:44 (none) kernel: [ 73.260427] dvblo: dvblo_chardev_init(): initializing char device with minor device number 1
Jan 24 22:07:44 (none) kernel: [ 73.261769] dvblo: dvblo_chardev_init(): added character device dvblo1
Jan 24 22:07:44 (none) kernel: [ 73.261782] dvblo: dvblo_chardev_init(): initializing char device with minor device number 2
Jan 24 22:07:44 (none) kernel: [ 73.263794] dvblo: dvblo_chardev_init(): added character device dvblo2
Jan 24 22:07:44 (none) kernel: [ 73.263805] dvblo: dvblo_chardev_init(): initializing char device with minor device number 3
Jan 24 22:07:44 (none) kernel: [ 73.264497] dvblo: dvblo_chardev_init(): added character device dvblo3
Jan 24 22:07:44 (none) kernel: [ 73.264507] dvblo: dvblo_chardev_init(): initializing char device with minor device number 4
Jan 24 22:07:44 (none) kernel: [ 73.264694] dvblo: dvblo_chardev_init(): added character device dvblo4
Jan 24 22:07:44 (none) kernel: [ 73.264698] dvblo: dvblo_chardev_init(): initializing char device with minor device number 5
Jan 24 22:07:44 (none) kernel: [ 73.264799] dvblo: dvblo_chardev_init(): added character device dvblo5
Jan 24 22:07:44 (none) kernel: [ 73.264803] dvblo: dvblo_chardev_init(): initializing char device with minor device number 6
Jan 24 22:07:44 (none) kernel: [ 73.264902] dvblo: dvblo_chardev_init(): added character device dvblo6
Jan 24 22:07:44 (none) kernel: [ 73.264907] dvblo: dvblo_chardev_init(): initializing char device with minor device number 7
Jan 24 22:07:44 (none) kernel: [ 73.265039] dvblo: dvblo_chardev_init(): added character device dvblo7
Jan 24 22:07:44 (none) kernel: [ 73.265045] dvblo: dvblo_init(): successfully initialized DVB Loopback Adapter Version 0.9.4-s2api
Jan 24 22:07:44 (none) kernel: [ 73.754596] lirc_imon: VFD port opened
Jan 24 22:07:45 (none) kernel: [ 74.273277] DVB: registering new adapter (dvblo_adap0)
Jan 24 22:07:45 (none) kernel: [ 74.273290] DVB: registering adapter 1 frontend 0 (Virtual DVB Frontend)...
Jan 24 22:07:45 (none) kernel: [ 74.274745] dvblo: dvblo_adap_create(): created new virtual DVB adapter: dvblo_adap0
Jan 24 22:07:50 (none) kernel: [ 79.570946] lirc_imon: IR port opened
Alles anzeigen
Vielleicht hat jemand eine Idee dieses dumme Problem zu lösen?
Der Betrieb mit der HDe läuft eigentlich "stable" - keine Ton oder Wackler unter dem HD TV.
Grüße
cinfo