Hello
Because Kernel 2.4 is not very well supported any more with DVB(-T), i thought it would be a good idea to update from debian.woody to sarge and then to the 2.6.x kernel.
debain apt makes that so easy...: I added the "sarge" resources to sources.list did #apt-get update #aptiude upgrade # #130MB downloads later(the box is more than only a VDR): #lilo(*) #reboot
I see the "DVB-RAM-test" on the TV but VDR does not find an mpeg decoder anymore!
What am i missing? Any hints why VDR is not fiinding the DVB cards any more? The kernel is unchanged 2.4.28. I just wondered why "deffs" was installed by the upgrade...
In VDR and DVB i made "make clean" and makevdr resp. make ; make install but it does not really help. Rebooted again. Result see below.
i tried to go back to 1.3.18 but that failed because of the new timer format
00:03:21 vdr[2346]: loading /video0/sources.conf 00:03:21 vdr[2346]: loading /video0/diseqc.conf 00:03:21 vdr[2346]: loading /video0/channels.conf 00:03:21 vdr[2346]: loading /video0/timers.conf 00:03:21 vdr[2346]: ERROR: error in /video0/timers.conf, line 109 00:03:21 vdr[2346]: saved setup to /video0/setup.conf 00:03:21 vdr[2346]: stopping plugin: femon 00:03:21 vdr[2346]: stopping plugin: undelete 00:03:21 vdr[2346]: undelete: cPluginUndelete::~cPluginUndelete 00:03:21 vdr[2346]: stopping plugin: osdteletext 00:03:21 vdr[2346]: max. latency time 0 seconds 00:03:21 vdr[2346]: exiting
Ok, using backup an vdr 1.3.18
00:13:15 vdr[3860]: timer 130 (13 1100-1132 'Mega') set to event Mon 30.05.2005 11:00-11:30 (VPS: 30.05 11:00) 'nano' ./dvb-ttpci-budget.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-ttpci-budget-ci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-ttpci-budget-av.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./skystar2.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Using /lib/modules/2.4.29/misc/dvb-core.o insmod: a module named dvb-core already exists
dmesg does not contain not result...
1.3.18 is now not working anymore too ;-( 00:19:08 vdr[2114]: starting plugin: femon 00:19:08 vdr[2114]: loading /video0/themes/sttng-default.theme 00:19:08 lircd 0.7.0[2051]: accepted new client on /dev/lircd 00:19:08 vdr[2119]: LIRC remote control thread started (pid=2119, tid=49156) 00:19:08 vdr[2114]: remote control LIRC - keys known 00:19:23 vdr[2114]: setting watchdog timer to 60 seconds 00:19:23 vdr[2114]: ERROR: no OSD provider available - using dummy OSD!
I did not "aptitude dist-upgrade" as this would require further 190MB of down load (i' try to get a CD...)
----------------------------------------------------------------------
((*)honestly i did not "lilo" so reboot ends in "LI" and have to boot Knoppy and did the lilo there in chroot ..debian apt is not that perfect ;-) lilo now aways says: msi:~# lilo Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/ide/host0/bus1/target0/lun0/disc' -> '/dev/hdc' ) but i don't have devfs installed. Maybe just a new feature of sarg lilo. But the box i sboot)
dmesg ... LVM version 1.0.8(17/11/2003) module loaded kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,4), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,7), internal journal EXT3-fs: mounted filesystem with ordered data mode. bttv: driver version 0.9.15 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at 00:0a.0, irq: 10, latency: 64, mmio: 0xcfcfe000 bttv0: detected: AVermedia DVB-T 771 [card=121], PCI subsystem ID is 1461:0771 bttv0: using: AVerMedia AVerTV DVB-T 771 [card=121,autodetected] bttv0: gpio: en=00000000, out=00000000 in=0090000f [init] i2c-dev.o: Registered 'bt878 #0 [hw]' as minor 0 i2c-core.o: adapter bt878 #0 [hw] registered as adapter 0. bttv0: using tuner=-1 bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 => 35468950 .. ok i2c-core.o: driver i2c TV tuner driver registered. bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 10, latency: 64, memory: 0xcfcff000 btaudio: driver version 0.7 loaded [digital+analog] saa7146: register extension 'dvb'. saa7146_core: found saa7146 @ mem e1960e00 (revision 1, irq 5) (0x13c2,0x0003). DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1). Technotrend/Hauppauge PCI rev2.1 adapter 0 has MAC addr = 00:d0:5c:20:30:9b DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d DVB: AV7111(0) - firmware supports CI link layer interface av7110(0): adac type set to 0 saa7146_fops: saa7146 (0): registered device video1 [v4l2] av7110: found av7110-0. saa7146_core: found saa7146 @ mem e1a0ac00 (revision 1, irq 5) (0x13c2,0x0003). DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1). Technotrend/Hauppauge PCI rev2.1 adapter 1 has MAC addr = 00:d0:5c:20:78:9e DVB: AV7111(1) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d DVB: AV7111(1) - firmware supports CI link layer interface av7110(1): Crystal audio DAC detected saa7146_fops: saa7146 (1): registered device video2 [v4l2] av7110: found av7110-1. saa7146_core: found saa7146 @ mem e1ab4a00 (revision 1, irq 5) (0x13c2,0x0000). DVB: registering new adapter (Siemens/Technotrend/Hauppauge PCI rev1.3). Siemens/Technotrend/Hauppauge PCI rev1.3 adapter 2 has MAC addr = 00:d0:5c:02:16:cc DVB: AV7111(2) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d DVB: AV7111(2) - firmware supports CI link layer interface av7110(2): Crystal audio DAC detected saa7146_fops: saa7146 (2): registered device video3 [v4l2] av7110: found av7110-2. ehci_hcd 00:03.3: Silicon Integrated Systems [SiS] USB 2.0 Controller ehci_hcd 00:03.3: irq 5, pci mem e1b64000 usb.c: new USB bus registered, assigned bus number 4 PCI: cache line size of 64 is not supported by device 00:03.3 ehci_hcd 00:03.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 8 ports detected usb.c: USB disconnect on device 00:03.2-1 address 2 Intel 810 + AC97 Audio, version 1.01, 00:46:52 Jan 23 2005 i810: SiS 7012 found at IO 0xd800 and 0xdc00, MEM 0x0000 and 0x0000, IRQ 10 i810_audio: Audio Controller supports 6 channels. i810_audio: Defaulting to base 2 channel mode. i810_audio: Resetting connection 0 ac97_codec: AC97 codec, id: CMI97 (CMedia) AC97 codec does not have proper volume support. i810_audio: only 48Khz playback available. i810_audio: AC'97 codec 0, new EID value = 0x05c6 i810_audio: AC'97 codec 0, DAC map configured, total channels = 6 hub.c: new USB device 00:03.2-1, assigned address 3 input: USB HID v1.10 Keyboard [Twinhan Tech Remote Control] on usb1:3.0 input: USB HID v1.10 Mouse [Twinhan Tech Remote Control] on usb1:3.1 eth0: Media Link On 100mbps full-duplex ip_tables: (C) 2000-2002 Netfilter core team ip_conntrack version 2.1 (4095 buckets, 32760 max) - 288 bytes per conntrack lirc_dev: IR Remote Control driver registered, at major 61 lirc_serial: auto-detected active low receiver lirc_dev: lirc_register_plugin:sample_rate: 0 bt878(0): unloading bt878_mem: 0xe18fd000. i2c-core.o: driver unregistered: i2c TV tuner driver bttv0: unloading i2c-core.o: adapter unregistered: bt878 #0 [hw] saa7146: unregister extension 'dvb'. bttv: driver version 0.9.15 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at 00:0a.0, irq: 10, latency: 64, mmio: 0xcfcfe000 bttv0: detected: AVermedia DVB-T 771 [card=121], PCI subsystem ID is 1461:0771 bttv0: using: AVerMedia AVerTV DVB-T 771 [card=121,autodetected] bttv0: gpio: en=00000000, out=00000000 in=0090000f [init] i2c-dev.o: Registered 'bt878 #0 [hw]' as minor 0 i2c-core.o: adapter bt878 #0 [hw] registered as adapter 0. bttv0: using tuner=-1 bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 => 35468950 . ok i2c-core.o: driver i2c TV tuner driver registered. bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 10, latency: 64, memory: 0xcfcff000 DVB: registering new adapter (Ave). DVB: registering frontend 0:0 (DVB-T Zarlink MT352 demodulator driver)...
23:34:32 logger[2068]: /root/video/VDR/runvdr restarting VDR 23:34:42 kernel: bt878(0): unloading 23:34:42 kernel: bt878_mem: 0xe18fd000. 23:34:42 kernel: i2c-core.o: driver unregistered: i2c TV tuner driver 23:34:42 kernel: bttv0: unloading 23:34:42 kernel: i2c-core.o: adapter unregistered: bt878 #0 [hw] 23:34:42 kernel: saa7146: unregister extension 'dvb'. 23:34:48 kernel: bttv: driver version 0.9.15 loaded 23:34:48 kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture 23:34:48 kernel: bttv: Bt8xx card found (0). 23:34:48 kernel: bttv0: Bt878 (rev 17) at 00:0a.0, irq: 10, latency: 64, mmio: 0xcfcfe000 23:34:48 kernel: bttv0: detected: AVermedia DVB-T 771 [card=121], PCI subsystem ID is 1461:0771 23:34:48 kernel: bttv0: using: AVerMedia AVerTV DVB-T 771 [card=121,autodetected] 23:34:48 kernel: bttv0: gpio: en=00000000, out=00000000 in=0090000f [init] 23:34:48 kernel: i2c-dev.o: Registered 'bt878 #0 [hw]' as minor 0 23:34:48 kernel: i2c-core.o: adapter bt878 #0 [hw] registered as adapter 0. 23:34:48 kernel: bttv0: using tuner=-1 23:34:48 kernel: bttv0: registered device video0 23:34:48 kernel: bttv0: registered device vbi0 23:34:48 kernel: bttv0: PLL: 28636363 => 35468950 . ok 23:34:48 kernel: i2c-core.o: driver i2c TV tuner driver registered. 23:34:48 kernel: bt878: AUDIO driver version 0.0.0 loaded 23:34:48 kernel: bt878: Bt878 AUDIO function found (0). 23:34:48 kernel: bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 10, latency: 64, memory: 0xcfcff000 23:34:48 kernel: DVB: registering new adapter (Ave). 23:34:48 kernel: DVB: registering frontend 0:0 (DVB-T Zarlink MT352 demodulator driver)... 23:34:49 vdr[2104]: VDR version 1.3.24 started 23:34:49 vdr[2104]: loading plugin: ./PLUGINS/lib/libvdr-osdteletext.so.1.3.24 23:34:49 vdr[2104]: loading plugin: ./PLUGINS/lib/libvdr-undelete.so.1.3.24 23:34:49 vdr[2104]: Undelete: cPluginUndelete::cPluginUndelete 23:34:49 vdr[2104]: loading plugin: ./PLUGINS/lib/libvdr-femon.so.1.3.24 23:34:49 vdr[2104]: loading /video0/setup.conf 23:34:49 vdr[2104]: ERROR: unknown config parameter: AC3dynrng = 1 23:34:49 vdr[2104]: ERROR: unknown config parameter: AC3overDVB = 0 ... lot of unknow parameter 23:34:49 vdr[2104]: ERROR: unknown config parameter: Streaming = 4 1 23:34:49 vdr[2104]: ERROR: unknown config parameter: StreamTTL = 2 23:34:49 vdr[2104]: ERROR: unknown config parameter: Symbol = 1 23:34:49 vdr[2104]: undelete: Setupparameter verbose=1 23:34:49 vdr[2104]: undelete: Setupparameter visible=1 23:34:49 vdr[2104]: loading /video0/sources.conf 23:34:49 vdr[2104]: loading /video0/diseqc.conf 23:34:49 vdr[2104]: loading /video0/channels.conf 23:34:49 vdr[2104]: loading /video0/timers.conf 23:34:49 vdr[2104]: loading /video0/commands.conf 23:34:49 vdr[2104]: loading /video0/reccmds.conf 23:34:49 vdr[2104]: loading /video0/svdrphosts.conf 23:34:49 vdr[2104]: loading /video0/ca.conf 23:34:49 vdr[2104]: loading /video0/remote.conf 23:34:49 vdr[2104]: loading /video0/keymacros.conf 23:34:49 vdr[2104]: reading EPG data from /video0/epg.data 23:34:49 vdr[2104]: probing /dev/dvb/adapter0/frontend0 23:34:49 vdr[2107]: tuner on device 1 thread started (pid=2107, tid=16386) 23:34:49 vdr[2104]: probing /dev/dvb/adapter1/frontend0 23:34:49 vdr[2104]: found 1 video device 23:34:49 vdr[2104]: initializing plugin: osdteletext (0.5): Displays teletext on the OSD 23:34:49 vdr[2104]: initializing plugin: undelete (0.0.2): undelete for recordings 23:34:49 vdr[2104]: initializing plugin: femon (0.8.9): DVB Signal Information Monitor (OSD) 23:34:49 vdr[2104]: setting primary device to 1 23:34:49 vdr[2104]: device 1 has no MPEG decoder 23:34:49 vdr[2104]: SVDRP listening on port 2001 23:34:49 vdr[2108]: Section handler thread started (pid=2108, tid=32771) 23:34:49 vdr[2104]: loading /video0/themes/sttng-default.theme 23:34:49 vdr[2104]: starting plugin: osdteletext 23:34:49 vdr[2104]: starting plugin: undelete 23:34:49 vdr[2104]: undelete: cPluginUndelete::Start undeleteconfigfile=undelete.conf 23:34:49 vdr[2104]: undelete: INFO: config file not found: [/video0/plugins/]undelete.conf 23:34:49 vdr[2104]: undelete: Start 23:34:50 vdr[2104]: starting plugin: femon 23:34:50 vdr[2104]: loading /video0/themes/sttng-default.theme 23:34:50 lircd 0.7.0[2051]: accepted new client on /dev/lircd 23:34:50 vdr[2109]: LIRC remote control thread started (pid=2109, tid=49156) 23:34:50 vdr[2104]: remote control LIRC - keys known 23:34:55 vdr[2104]: setting watchdog timer to 60 seconds 23:34:55 vdr[2104]: ERROR: no OSD provider available - using dummy OSD! 23:34:55 vdr[2104]: timer 49 (80 0100-0200 'Domian') set to event Wed 25.05.2005 01:00-02:00 (VPS: 25.05 01:00) 'Domian' 23:34:55 vdr[2104]: timer 68 (15 2300-2345 'Prisma-Magazin') set to event Tue 24.05.2005 23:00-23:45 (VPS: 24.05 23:00) 'Prisma' 23:34:55 vdr[2104]: no free DVB device to record channel 15!
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
UseNet-Posting-Nospam-74308-@zocki.toppoint.de(Rainer Zocholl) 25.05.05 00:39
Hello
Because Kernel 2.4 is not very well supported any more with DVB(-T), i thought it would be a good idea to update from debian.woody to sarge and then to the 2.6.x kernel.
debain apt makes that so easy...: I added the "sarge" resources to sources.list did #apt-get update #aptiude upgrade # #130MB downloads later(the box is more than only a VDR): #lilo(*) #reboot
I see the "DVB-RAM-test" on the TV but VDR does not find an mpeg decoder anymore!
What am i missing? Any hints why VDR is not finding the DVB cards any more? The kernel is unchanged 2.4.28. I just wondered why "deffs" was installed by the upgrade...
In VDR and DVB i made "make clean" and makevdr resp. make ; make install but it does not really help. Rebooted again. Result see below.
If i use the linux-dvb.2004-12-26 driver VDR 1.3.18 can find the DVB-S cards. The DVB-T is dead of course... If VDR 1.3.24 starts it shows the same error as before.
If 1.3.24 is run after the VDR 1.3.18, 24. can find the cards too!
Why does this happen only because i updated the linux distribution? (OK, the memory allocation might be other....) What's different between 1.3.18 1.3.24 ? If VDR expects a specia DVB driver version/API, why can't it complain? I would find it very mice if, when VDR needs to convert a .conf, it would make a backup copy of the privious version. It's a delveloper version, so i have backups, but it would be nicer if VDR would do the backup too.
Is there meanwhile a driverpackage including then working AverMedia 771 DVB-T driver?
Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl a écrit :
What am i missing? Any hints why VDR is not finding the DVB cards any more? The kernel is unchanged 2.4.28. I just wondered why "deffs" was installed by the upgrade...
Go back to the root : modutils, /etc/modules.conf, szap, etc. There are many little differences between woody and sarge, and also between kernel 2.4 and 2.6 Your conf files should benefit from a dist-upgrade... For sure devfs will hurt things, and I do not have it on my sarge VDR (when I upgraded woody to sarge on that box a long time ago, I first did a complete backup of the disks, and used them at least once)
nhuillard@e-dition.fr(Nicolas Huillard) 25.05.05 10:46
Once upon a time "Nicolas Huillard " shaped the electrons to say...
Rainer Zocholl a écrit :
What am i missing? Any hints why VDR is not finding the DVB cards any more? The kernel is unchanged 2.4.28. I just wondered why "deffs" was installed by the upgrade...
Go back to the root : modutils, /etc/modules.conf, szap, etc. There are many little differences between woody and sarge,
Yes. but i am wondering why VDR says: "device 1 has no MPEG decoder" while it may actually should read: "Found DVB driver API interface Version 1.1 while requiring 1.2". or so.
and also between kernel 2.4 and 2.6
Meanwhile i found a nice "step-by-step" "howto kernel 2.6.x and VDR" in the vdr-wiki.de.
Your conf files should benefit from a dist-upgrade...
Ah thanks. I'll do. I found a CD with debian-testing-i386 so the further 190MB for the "aptitude dist-upgrade" would not hurt so much (the box only has ISDN!).
For sure devfs will hurt things,
I don't think i would like to be forced to use it.
and I do not have it on my sarge VDR (when I upgraded woody to sarge on that box a long time ago, I first did a complete backup of the disks, and used them at least once)
But i'm right that VDR with 2.4.x is no so good anymore, especially with DVB-T and USB and 2.6x would be much better (=stable, relyable). Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------
Rainer Zocholl wrote:
... Yes. but i am wondering why VDR says: "device 1 has no MPEG decoder" while it may actually should read: "Found DVB driver API interface Version 1.1 while requiring 1.2". or so. ...
Well, this might have to do with the fact that the driver doesn't provide that kind of information ;-)
At least not to my knowledge - please corret me if I'm wrong.
Klaus
Rainer Zocholl a écrit : ...
But i'm right that VDR with 2.4.x is no so good anymore, especially with DVB-T and USB and 2.6x would be much better (=stable, relyable).
I came to the same conclusion (even for DVB-S only). Number of patches, additional kernel modudle et al. required for 2.4 are now fully integrated in 2.6.
-
Klaus Schmidinger -
Nicolas Huillard -
Rainer Zocholl