VDR stürzt täglich nach Neusinstallation auf Ubuntu 14.04 LTS ab

hansp · 27. August 2016

Hallo,
schön langsam werfe ich meine Nerven weg. Ich versuche mal zu beschreiben welche Infos ich über die Abstürze habe,

Vorletzter Absturz:
Syslog:

Code

Aug 23 14:03:10 VDR-Server vdr: [27528] frontend 1/0 timed out while tuning to channel 260 (Nickelodeon OBSOLETE), tp 112515
Aug 23 14:03:24 VDR-Server kernel: [66466.391755] divide error: 0000 [#1] SMP 
Aug 23 14:03:24 VDR-Server kernel: [66466.391779] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_tables x_tables rc_dib0700_rc5 rfcomm bnep bluetooth nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache rc_tevii_nec ts2020 ds3000 xfs libcrc32c mt2060 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_codec_hdmi dvb_usb_dib0700 input_leds serio_raw dib7000m dib0090 dib0070 snd_hda_codec_realtek snd_hda_codec_generic dib3000mc dibx000_common snd_hda_intel dvb_usb_dw2102 dvb_usb snd_hda_codec dvb_core lpc_ich rc_core snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915 snd_seq snd_seq_device snd_timer snd drm_kms_helper 8250_fintek shpchp video soundcore drm mei_me mac_hid ie31200_edac parport_pc mei edac_core i2c_algo_bit ppdev lp parport hid_generic usbhid hid uas usb_storage ahci libahci r8169 mii
Aug 23 14:03:24 VDR-Server kernel: [66466.392198] CPU: 0 PID: 27517 Comm: kdvb-ad-1-fe-0 Not tainted 4.2.0-42-generic #49~14.04.1-Ubuntu
Aug 23 14:03:24 VDR-Server kernel: [66466.392229] Hardware name: MSI MS-7758/Z77A-G43 (MS-7758), BIOS V2.1 02/20/2012
Aug 23 14:03:24 VDR-Server kernel: [66466.392253] task: ffff88021541c4c0 ti: ffff88001f0ac000 task.ti: ffff88001f0ac000
Aug 23 14:03:24 VDR-Server kernel: [66466.392278] RIP: 0010:[<ffffffffc017105b>]  [<ffffffffc017105b>] ds3000_set_frontend+0x1cb/0x570 [ds3000]
Aug 23 14:03:24 VDR-Server kernel: [66466.392314] RSP: 0018:ffff88001f0afdc8  EFLAGS: 00010246
Aug 23 14:03:24 VDR-Server kernel: [66466.392333] RAX: 0000000000007451 RBX: ffffffffc01727a3 RCX: 0000000000000000
Aug 23 14:03:24 VDR-Server kernel: [66466.392356] RDX: 0000000000000000 RSI: ffffffffc0438b50 RDI: ffff880212bc5800
Aug 23 14:03:24 VDR-Server kernel: [66466.392380] RBP: ffff88001f0afdf8 R08: ffff88021f216640 R09: ffff88021541c4c0
Aug 23 14:03:24 VDR-Server kernel: [66466.392403] R10: 0000000000000012 R11: 000000000000000b R12: ffff880212bc5800
Aug 23 14:03:24 VDR-Server kernel: [66466.392426] R13: ffff880212bc5810 R14: ffff880212b095e8 R15: ffff880212b09400
Aug 23 14:03:24 VDR-Server kernel: [66466.392450] FS:  0000000000000000(0000) GS:ffff88021f200000(0000) knlGS:0000000000000000
Aug 23 14:03:24 VDR-Server kernel: [66466.392477] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 23 14:03:24 VDR-Server kernel: [66466.392496] CR2: 00007f6d4af32000 CR3: 0000000001c0e000 CR4: 00000000001406f0
Aug 23 14:03:24 VDR-Server kernel: [66466.392519] Stack:
Aug 23 14:03:24 VDR-Server kernel: [66466.392528]  ffff88001f0afdf8 ffffffff8161c884 0000000000000246 ffff880212bc5810
Aug 23 14:03:24 VDR-Server kernel: [66466.392556]  ffff880212b09620 ffff880212bc5810 ffff88001f0afe28 ffffffffc0171424
Aug 23 14:03:24 VDR-Server kernel: [66466.392585]  0000000100001b00 ffff88001f0afe5c 0000000000000032 0000000000000000
Aug 23 14:03:24 VDR-Server kernel: [66466.392614] Call Trace:
Aug 23 14:03:24 VDR-Server kernel: [66466.392626]  [<ffffffff8161c884>] ? i2c_transfer+0x64/0xc0
Aug 23 14:03:24 VDR-Server kernel: [66466.392647]  [<ffffffffc0171424>] ds3000_tune+0x24/0x50 [ds3000]
Aug 23 14:03:24 VDR-Server kernel: [66466.392671]  [<ffffffffc03e2388>] dvb_frontend_thread+0x3d8/0x700 [dvb_core]
Aug 23 14:03:24 VDR-Server kernel: [66466.392697]  [<ffffffff810b9fd0>] ? prepare_to_wait_event+0xf0/0xf0
Aug 23 14:03:24 VDR-Server kernel: [66466.392720]  [<ffffffffc03e1fb0>] ? dvb_frontend_release+0x100/0x100 [dvb_core]
Aug 23 14:03:24 VDR-Server kernel: [66466.392745]  [<ffffffff81097a99>] kthread+0xc9/0xe0
Aug 23 14:03:24 VDR-Server kernel: [66466.392763]  [<ffffffff810979d0>] ? kthread_create_on_node+0x1c0/0x1c0
Aug 23 14:03:24 VDR-Server kernel: [66466.392787]  [<ffffffff817c3b1f>] ret_from_fork+0x3f/0x70
Aug 23 14:03:24 VDR-Server kernel: [66466.392806]  [<ffffffff810979d0>] ? kthread_create_on_node+0x1c0/0x1c0
Aug 23 14:03:24 VDR-Server kernel: [66466.392827] Code: 85 6c 03 00 00 b9 d3 4d 62 10 3d 27 4f 4c 00 0f 87 f1 01 00 00 f7 e1 b8 51 74 00 00 49 8b 74 24 08 4c 89 e7 89 d1 31 d2 c1 e9 06 <f7> f1 b9 0d 00 00 00 ba c3 00 00 00 8d 58 01 83 c0 02 f6 c3 01 
Aug 23 14:03:24 VDR-Server kernel: [66466.392968] RIP  [<ffffffffc017105b>] ds3000_set_frontend+0x1cb/0x570 [ds3000]
Aug 23 14:03:24 VDR-Server kernel: [66466.392994]  RSP <ffff88001f0afdc8>
Aug 23 14:03:24 VDR-Server kernel: [66466.401400] ---[ end trace 8d29f9ec9c6d75a8 ]---
Aug 23 14:03:42 VDR-Server vdr: [27515] frontend 0/0 timed out while tuning to channel 9 (WIENTV), tp 730
Aug 23 14:04:32 VDR-Server vdr: [27495] PANIC: watchdog timer expired - exiting!
Aug 23 14:04:33 VDR-Server vdr: [27552] VNSI: cxSocket::read(fd=16): eof, connection closed
Aug 23 14:04:33 VDR-Server vdr: [27552] VNSI Client 0->192.168.123.205:46850 thread ended (pid=27495, tid=27552)
Aug 23 14:04:49 VDR-Server kernel: [66551.400093] init: vdr main process (27495) killed by ABRT signal
Aug 23 14:04:49 VDR-Server vdr: [761] VDR version 2.2.0 started
Aug 23 14:04:49 VDR-Server vdr: [761] switched to user 'vdr'
Aug 23 14:04:49 VDR-Server vdr: [761] codeset is 'UTF-8' - known
Aug 23 14:04:49 VDR-Server vdr: [761] found 28 locales in /usr/share/locale
Aug 23 14:04:49 VDR-Server vdr: [761] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.2.0
Aug 23 14:04:49 VDR-Server vdr: [761] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.2.0
Aug 23 14:04:49 VDR-Server vdr: [761] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.2.0
Aug 23 14:04:49 VDR-Server vdr: [761] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.2.0
Aug 23 14:04:49 VDR-Server vdr: [761] loading plugin: /usr/lib/vdr/plugins/libvdr-vompserver.so.2.2.0
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/setup.conf
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: DumpNaluFill = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: HardLinkCutter = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: JumpPlay = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: JumpSeconds = 60
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: JumpSecondsSlow = 10
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: MaxRecordingSize = 100
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: PauseLastMark = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: PlayJump = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: SupportTeletext = 0
Aug 23 14:04:49 VDR-Server vdr: [761] ERROR: unknown config parameter: WarEagleIcons = 1
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/sources.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/diseqc.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/scr.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/channels.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/timers.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/commands.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/reccmds.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/svdrphosts.conf
Aug 23 14:04:49 VDR-Server vdr: [761] loading /var/lib/vdr/keymacros.conf
Aug 23 14:04:49 VDR-Server vdr: [761] registered source parameters for 'A - ATSC'
Aug 23 14:04:49 VDR-Server vdr: [761] registered source parameters for 'C - DVB-C'
Aug 23 14:04:49 VDR-Server vdr: [761] registered source parameters for 'S - DVB-S'
Aug 23 14:04:49 VDR-Server vdr: [787] video directory scanner thread started (pid=761, tid=787, prio=high)
Aug 23 14:04:49 VDR-Server vdr: [788] video directory scanner thread started (pid=761, tid=788, prio=high)
Aug 23 14:04:49 VDR-Server vdr: [761] registered source parameters for 'T - DVB-T'
Aug 23 14:04:49 VDR-Server vdr: [761] probing /dev/dvb/adapter0/frontend0
Aug 23 14:04:49 VDR-Server vdr: [761] creating cDvbDevice
Aug 23 14:04:49 VDR-Server vdr: [761] new device number 1
Aug 23 14:04:49 VDR-Server vdr: [789] epg data reader thread started (pid=761, tid=789, prio=high)
Aug 23 14:04:49 VDR-Server vdr: [789] reading EPG data from /var/cache/vdr/epg.data
Aug 23 14:04:49 VDR-Server vdr: [788] video directory scanner thread ended (pid=761, tid=788)
Aug 23 14:04:49 VDR-Server vdr: [761] DVB API version is 0x050A (VDR was built with 0x050A)
Aug 23 14:04:49 VDR-Server vdr: [761] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("DiBcom 3000MC/P")
Aug 23 14:04:49 VDR-Server vdr: [761] cTimeMs: using monotonic clock (resolution is 1 ns)
Aug 23 14:04:49 VDR-Server vdr: [761] probing /dev/dvb/adapter1/frontend0
Aug 23 14:04:49 VDR-Server vdr: [761] creating cDvbDevice
Aug 23 14:04:49 VDR-Server vdr: [761] new device number 2
Aug 23 14:04:49 VDR-Server vdr: [790] frontend 0/0 tuner thread started (pid=761, tid=790, prio=high)
Aug 23 14:04:49 VDR-Server vdr: [791] device 1 section handler thread started (pid=761, tid=791, prio=low)
Aug 23 14:04:50 VDR-Server vdr: [787] video directory scanner thread ended (pid=761, tid=787)
Aug 23 14:04:50 VDR-Server vdr: [789] epg data reader thread ended (pid=761, tid=789)
Aug 23 14:09:01 VDR-Server CRON[941]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] &

Alles anzeigen

Nachdem der Absturz unmittelbar nach einem Versuch einen Kanal aufzunehmen der bei mir nicht funktioniert da verschlüsselt oder HD. Habe ich alle diese Kanäle aus der channellist zug für zug entfernt. Und die automatische Sendersuche ausgeschaltet.
Nun habe ich folgende Abstürze, in der Syslog stehen nur diese Zeilen:

Code

Aug 26 07:51:06 VDR-Server anacron[591]: Job `cron.daily' terminated
Aug 26 07:51:06 VDR-Server anacron[591]: Normal exit (1 job run)
Aug 26 08:09:01 VDR-Server CRON[2159]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Aug 26 08:17:01 VDR-Server CRON[2379]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 26 08:39:01 VDR-Server CRON[3040]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Aug 26 09:09:01 VDR-Server CRON[3906]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Aug 26 09:17:01 VDR-Server CRON[4122]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 26 09:39:01 VDR-Server CRON[4725]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Aug 26 10:09:01 VDR-Server CRON[5494]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Aug 26 10:17:01 VDR-Server CRON[5706]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Ich bin kein Profi, bitte um Hilfe wo und wie ich noch Daten sammeln kann um den Fehler zu beheben. Nochwas nach dem Absturz geht der Mauszeiger nur mehr ruckartig auch ein Stop vdr hilft nichts.Scheinbar hat es das syslog weggespeichert und eine Neues angelegt. Wie komme ich in so ein abgelegtes syslog?
Bitte um Hilfe !
Wenn ihr mehr Infos braucht bitte sagen wie ich dazu komme.
LG
Hansp

gda · 27. August 2016

Mir ist nicht klar was du jetzt benutzt, yaVDR 0.6.1, oder nacktes Ubuntu mit VDR-Paketen?

Gerald

hansp · 27. August 2016

Ich verwende den VDR headless, also mit den Packeten. Zum Anschauen habe ich 2 Raspberrys mir Kodi und einen mit VOMP.
In der syslog habe ich als Vorgeschichte noch folgndes gefunden:

Code

Aug 27 00:34:10 VDR-Server vdr: [13992] frontend 2/0 timed out while tuning to channel 14 (RTL Austria), tp 112226
Aug 27 00:34:54 VDR-Server vdr: [14001] frontend 5/0 timed out while tuning to channel 240 (DISNEY CH.), tp 211038
Aug 27 00:35:14 VDR-Server vdr: [13992] frontend 2/0 timed out while tuning to channel 241 (EUROSPORT 2), tp 211856
Aug 27 00:35:26 VDR-Server vdr: [13995] frontend 3/0 timed out while tuning to channel 96 (SES), tp 111023
Aug 27 00:35:58 VDR-Server vdr: [14001] frontend 5/0 timed out while tuning to channel 10 (Das Erste), tp 111836
Aug 27 00:36:15 VDR-Server vdr: [14001] frontend 5/0 lost lock on channel 29 (SUPER RTL), tp 112187
Aug 27 00:36:15 VDR-Server vdr: [14001] frontend 5/0 regained lock on channel 29 (SUPER RTL), tp 112187
Aug 27 00:36:19 VDR-Server vdr: [14001] frontend 5/0 lost lock on channel 29 (SUPER RTL), tp 112187
Aug 27 00:36:29 VDR-Server vdr: [13998] frontend 4/0 timed out while tuning to channel 183 (Comedy Central/Kindernet), tp 112343
Aug 27 00:36:35 VDR-Server vdr: [14001] frontend 5/0 timed out while tuning to channel 194 (WDR Bielefeld), tp 112421
Aug 27 00:36:56 VDR-Server vdr: [13992] frontend 2/0 timed out while tuning to channel 9 (Disney Channel), tp 112460
Aug 27 00:37:21 VDR-Server vdr: [14001] frontend 5/0 timed out while tuning to channel 240 (DISNEY CH.), tp 211038
Aug 27 00:37:52 VDR-Server vdr: [13995] frontend 3/0 timed out while tuning to channel 96 (SES), tp 111023
Aug 27 00:38:02 VDR-Server vdr: [13992] frontend 2/0 timed out while tuning to channel 20 (tagesschau24), tp 110743
Aug 27 00:38:16 VDR-Server kernel: [50418.426978] divide error: 0000 [#1] SMP 
Aug 27 00:38:16 VDR-Server kernel: [50418.427019] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_tables x_tables ts2020 rc_dib0700_rc5 bnep mt2060 rfcomm bluetooth nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache xfs libcrc32c rc_tevii_nec ds3000 snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds serio_raw snd_hda_codec_realtek snd_hda_codec_generic dvb_usb_dib0700 dib7000m dib0090 dib0070 dib3000mc dibx000_common dvb_usb_dw2102 i915 dvb_usb snd_hda_intel dvb_core snd_hda_codec lpc_ich rc_core snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer drm_kms_helper snd drm soundcore shpchp mei_me mei ie31200_edac edac_core i2c_algo_bit 8250_fintek mac_hid video parport_pc ppdev lp parport hid_generic usbhid hid ahci libahci r8169 uas mii usb_storage
Aug 27 00:38:16 VDR-Server kernel: [50418.427832] CPU: 2 PID: 13989 Comm: kdvb-ad-2-fe-0 Not tainted 4.2.0-42-generic #49~14.04.1-Ubuntu
Aug 27 00:38:16 VDR-Server kernel: [50418.427888] Hardware name: MSI MS-7758/Z77A-G43 (MS-7758), BIOS V2.1 02/20/2012
Aug 27 00:38:16 VDR-Server kernel: [50418.427933] task: ffff8801727dd280 ti: ffff880212b9c000 task.ti: ffff880212b9c000
Aug 27 00:38:16 VDR-Server kernel: [50418.427979] RIP: 0010:[<ffffffffc008905b>]  [<ffffffffc008905b>] ds3000_set_frontend+0x1cb/0x570 [ds3000]
Aug 27 00:38:16 VDR-Server kernel: [50418.428045] RSP: 0018:ffff880212b9fdc8  EFLAGS: 00010246
Aug 27 00:38:16 VDR-Server kernel: [50418.428078] RAX: 0000000000007451 RBX: ffffffffc008a7a3 RCX: 0000000000000000
Aug 27 00:38:16 VDR-Server kernel: [50418.428121] RDX: 0000000000000000 RSI: ffffffffc0447b50 RDI: ffff8800d49d3800
Aug 27 00:38:16 VDR-Server kernel: [50418.428165] RBP: ffff880212b9fdf8 R08: ffff88021f316640 R09: ffffffff81c15500
Aug 27 00:38:16 VDR-Server kernel: [50418.428209] R10: 0000000000000024 R11: 0000000000000014 R12: ffff8800d49d3800
Aug 27 00:38:16 VDR-Server kernel: [50418.428252] R13: ffff8800d49d3810 R14: ffff8802130a29e8 R15: ffff8802130a2800
Aug 27 00:38:16 VDR-Server kernel: [50418.428297] FS:  0000000000000000(0000) GS:ffff88021f300000(0000) knlGS:0000000000000000
Aug 27 00:38:16 VDR-Server kernel: [50418.428346] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 27 00:38:16 VDR-Server kernel: [50418.428382] CR2: 00007f09e78e2000 CR3: 0000000001c0e000 CR4: 00000000001406e0
Aug 27 00:38:16 VDR-Server kernel: [50418.428426] Stack:
Aug 27 00:38:16 VDR-Server kernel: [50418.428440]  ffff880212b9fdf8 ffffffff8161c884 0000000000000246 ffff8800d49d3810
Aug 27 00:38:16 VDR-Server kernel: [50418.428501]  ffff8802130a2a20 ffff8800d49d3810 ffff880212b9fe28 ffffffffc0089424
Aug 27 00:38:16 VDR-Server kernel: [50418.428551]  0000000100001b00 ffff880212b9fe5c 0000000000000032 0000000000000000

Alles anzeigen

Könnnte es sein das es an den timeouts liegt? Dann kommt immer der div 0 Fehler.
Ich habe wieder Kanäle aus der chennels.conf entfernt die er nicht tunen kann da verschlüsselt.

gda · 27. August 2016

Dann bist du im yaVDR-Forum also falsch, hier geht es um die Distribution yaVDR.

Gerald

hansp · 5. September 2016

Wieso, gibt es auch ein Forum für die yaVDR Pakete? das Basisprogramm ist ja das Gleiche.

mini73 · 5. September 2016

Dieses Unterforum ist normalerweise für die Systeme gedacht, die vom ISO installiert wurden.
Sobald man nur die Paketquellen nimmt und sich sein eigenes System zurecht bastelt (was man natürlich gerne tun darf und sollte!), ist es genau genommen nicht mehr eine yaVDR-Installation. Fragen dazu sollten dann im anderen Unterforum unter "Linux/Betriebssysteme/Debian und Derivate" gestellt werden.

Lars.

hansp · 5. September 2016

Danke für den Hinweis. Werde ich in Zukunft machen.

VDR stürzt täglich nach Neusinstallation auf Ubuntu 14.04 LTS ab

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema