[yaVDR-Ansible] "Umfrage" Bootzeiten ...

presskopf · Oct 17th 2020

Hier ist die Ausgabe.

Mir sagt das nicht so viel.

Code

matthias@serrano:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @21.209s
└─multi-user.target @21.206s
└─vdr-net-monitor.service @21.204s
└─vdr.service @7.676s +13.520s
└─x@vt7.service @7.021s +651ms
└─basic.target @3.380s
└─sockets.target @3.379s
└─snapd.socket @3.378s +1ms
└─sysinit.target @3.370s
└─systemd-timesyncd.service @3.168s +202ms
└─systemd-tmpfiles-setup.service @3.114s +44ms
└─local-fs.target @3.082s
└─run-user-666.mount @7.774s
└─local-fs-pre.target @2.884s
└─multipathd.service @2.830s +54ms
└─systemd-udev-settle.service @754ms +2.074s
└─systemd-udev-trigger.service @456ms +293ms
└─systemd-udevd-kernel.socket @428ms
└─system.slice @413ms
└─-.slice @413ms

Display More

Code

matthias@serrano:~$ ll /etc/vdr/conf.d/
total 24K
drwxr-xr-x 2 root root 4.0K Oct 15 23:22 ./
drwxr-xr-x 8 root root 4.0K Oct 15 22:48 ../
-rw-r--r-- 1 root root 275 Aug 4 08:47 00-vdr.conf
-rw-r--r-- 1 root root 135 Oct 15 21:14 02-vdr-charset-override.conf
-rw-r--r-- 1 root root 158 Oct 15 21:18 03-vdr-lirc.conf
-rw-r--r-- 1 root root 145 Oct 15 21:14 04-vdr-hide-first-recordinglevel.conf
lrwxrwxrwx 1 root root 36 Oct 15 23:22 50-conflictcheckonly.conf -> ../conf.avail/conflictcheckonly.conf
lrwxrwxrwx 1 root root 27 Oct 15 21:14 50-dbus2vdr.conf -> ../conf.avail/dbus2vdr.conf
lrwxrwxrwx 1 root root 26 Oct 15 21:17 50-desktop.conf -> ../conf.avail/desktop.conf
lrwxrwxrwx 1 root root 28 Oct 15 21:15 50-devstatus.conf -> ../conf.avail/devstatus.conf
lrwxrwxrwx 1 root root 25 Oct 15 22:44 50-dupiduapi.conf -> ../conf.avail/dupiduapi.conf
lrwxrwxrwx 1 root root 28 Oct 15 23:22 50-epgsearch.conf -> ../conf.avail/epgsearch.conf
lrwxrwxrwx 1 root root 32 Oct 15 23:22 50-epgsearchonly.conf -> ../conf.avail/epgsearchonly.conf
lrwxrwxrwx 1 root root 31 Oct 15 22:09 50-extrecmenung.conf -> ../conf.avail/extrecmenung.conf
lrwxrwxrwx 1 root root 24 Oct 15 22:10 50-femon.conf -> ../conf.avail/femon.conf
lrwxrwxrwx 1 root root 23 Oct 15 22:10 50-live.conf -> ../conf.avail/live.conf
lrwxrwxrwx 1 root root 25 Oct 15 21:15 50-markad.conf -> ../conf.avail/markad.conf
lrwxrwxrwx 1 root root 26 Oct 15 21:15 50-menuorg.conf -> ../conf.avail/menuorg.conf
lrwxrwxrwx 1 root root 26 Oct 15 21:19 50-osd2web.conf -> ../conf.avail/osd2web.conf
lrwxrwxrwx 1 root root 22 Oct 15 22:10 50-pin.conf -> ../conf.avail/pin.conf
lrwxrwxrwx 1 root root 33 Oct 15 23:22 50-quickepgsearch.conf -> ../conf.avail/quickepgsearch.conf
lrwxrwxrwx 1 root root 31 Oct 15 22:11 50-skindesigner.conf -> ../conf.avail/skindesigner.conf
lrwxrwxrwx 1 root root 31 Oct 15 21:21 50-softhddevice.conf -> ../conf.avail/softhddevice.conf
lrwxrwxrwx 1 root root 35 Oct 15 22:20 50-streamdev-server.conf -> ../conf.avail/streamdev-server.conf
lrwxrwxrwx 1 root root 29 Oct 15 22:11 50-systeminfo.conf -> ../conf.avail/systeminfo.conf
lrwxrwxrwx 1 root root 29 Oct 15 22:12 50-vdrmanager.conf -> ../conf.avail/vdrmanager.conf
lrwxrwxrwx 1 root root 29 Oct 15 22:13 50-vnsiserver.conf -> ../conf.avail/vnsiserver.conf

Display More

seahawk1986 · Oct 17th 2020

Was steht denn im Log des VDR? journalctl -u vdr -b -l

Der Skindesigner kann z.B. je nach Skin einige Zeit brauchen, um Bilder passend zur Ausgabeauflösung zu skalieren - ein Celeron J4105 ist ja eher eine gemütliche CPU.

presskopf · Oct 17th 2020

Stimmt natürlich, der J4105 ist keine Wuchtbrumme.

Anbei die Ausgabe.

seahawk1986 · Oct 17th 2020

Da scheint einige Zeit (ca. 9 von den 13 Sekunden, die der VDR zum Starten braucht) für die Initialisierung der Tuner drauf zu gehen. Mir fehlen da Vergleichswerte für Systeme mit vier Tunern, eventuell ist das davon abhängig was beim ersten Zugriff auf einen Tuner funktioniert (dann müsste bei einem Restart des VDR-Prozesses mittels systemctl restart vdr die Initialisierung schneller sein).

Lässt du den Start des VDR verzögern, bis die Tuner von udev komplett initialisiert wurden (mit Instanzen von wait-for-dvb@.service) oder läuft das einfach so?

presskopf · Oct 18th 2020

Also wissentlich habe ich nix zur Verzögerung eingestellt.

In der ansible-Konfiguration (meine hosts_var/localhost) gibt es ja diesen Abschnitt finden. Dort habe ich nichts eingetragen.

Sollte man das komplett auskommentieren?

Code

# wait for dvb devices by adapter number
# NOTE: This only works for devices that are discoverable by udev, not userspace drivers like sundtek tuners!
# e.g. wait_for_dvb_devices: [0, 1] to wait for /dev/dvb/adapter0 and /dev/dvb/adapter1
wait_for_dvb_devices: []

seahawk1986 · Oct 18th 2020

presskopf wrote:

Sollte man das komplett auskommentieren?

Nein, aber tendenziell würde ich das lieber auf die vorhandenen Tuner anpassen.

presskopf · Oct 18th 2020

Okay, Du meinst so?

Code

wait_for_dvb_devices: [0, 1, 2, 3]

seahawk1986 · Oct 18th 2020

Ja, damit sollte man den Fall ausschließen können, dass der VDR zu früh startet. Ob das eine Auswirkung auf die Initialisierungszeiten mit deiner DVB-Karte hat, kann ich dir leider nicht sagen.

davie2000 · Oct 18th 2020

Ja, ich glaub, Seahawk hat genau das gemeint - und war natürlich wieder schneller

Hat zwar jetzt viell. nicht direkt mit der Startzeit zu tun, aber offenbar hast du falsche Shader eingestellt, oder?

Selected deinterlacer for resolution X is not supported by HW (X = 0..4)

Und die Meldungen find ich auch seltsam - wo auch immer diese herkommen:

read incomplete section - len = 2344, r = 1740

presskopf · Oct 18th 2020

presskopf wrote:

Okay, Du meinst so?

Code

wait_for_dvb_devices: [0, 1, 2, 3]

Eine halbe Sekunde haben wir schon.

Code

matthias@serrano:~$ systemd-analyze
Startup finished in 9.026s (firmware) + 6.075s (loader) + 3.872s (kernel) + 20.900s (userspace) = 39.874s
graphical.target reached after 20.862s in userspace
matthias@serrano:~$ systemd-analyze blame
13.690s vdr.service
5.007s systemd-networkd-wait-online.service
2.114s systemd-udev-settle.service
1.824s snap.lxd.activate.service
1.688s snapd.service
1.401s dev-sda2.device
1.284s nfs-server.service
790ms systemd-logind.service
697ms udisks2.service
628ms x@vt7.service
579ms networkd-dispatcher.service
571ms accounts-daemon.service
482ms lircd2uinput.service
441ms mnt-quad2\x2dmusik.mount

Display More

davie2000 Da müsstest Du mir auf die Sprünge helfen.

Was relevant sein könnte:

Code

matthias@serrano:~$ dpkg -l | grep 965
ii i965-va-driver-shaders:amd64 2.4.0-1build1 amd64 VAAPI driver for Intel G45 & HD Graphics family
matthias@serrano:~$ dpkg -l | grep intel
ii intel-microcode 3.20200609.0ubuntu0.20.04.2 amd64 Processor microcode firmware for Intel CPUs
ii libdrm-intel1:amd64 2.4.101-2 amd64 Userspace interface to intel-specific kernel DRM services -- runtime
ii xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64 X.Org X server -- Intel i8xx, i9xx display driver
matthias@serrano:~$ sudo vainfo
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Gemini Lake - 2.4.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointEncSlice
VAProfileVP9Profile2 : VAEntrypointVLD

Display More

seahawk1986 · Oct 18th 2020

Kannst du mal zeigen, welche Optionen du beim Ausgabeplugin gesetzt hast?

grep '^softhd' /var/lib/vdr/setup.conf

presskopf · Oct 18th 2020

Aha, das ist ja interessant. Das System war recht jungfräulich aufgesetzt und da war noch garnix drin.

Jetzt, nachdem ich einmal in die Einstellungen gegangen bin, sind nun die Standardwerte drin.

Eine weitere Sekunde...

Code

matthias@serrano:~$ grep '^softhd' /var/lib/vdr/setup.conf
softhddevice.1080i.CutLeftRight = 0
softhddevice.1080i.CutTopBottom = 0
softhddevice.1080i.Deinterlace = 0
softhddevice.1080i.Denoise = 0
softhddevice.1080i.FirstField = 0
softhddevice.1080i.InverseTelecine = 0
softhddevice.1080i.Scaling = 0
softhddevice.1080i.SecondField = 0
softhddevice.1080i.Sharpen = 0
softhddevice.1080i.SkipChromaDeinterlace = 0
softhddevice.1080i_fake.CutLeftRight = 0
softhddevice.1080i_fake.CutTopBottom = 0
softhddevice.1080i_fake.Deinterlace = 0
softhddevice.1080i_fake.Denoise = 0
softhddevice.1080i_fake.FirstField = 0
softhddevice.1080i_fake.InverseTelecine = 0
softhddevice.1080i_fake.Scaling = 0
softhddevice.1080i_fake.SecondField = 0
softhddevice.1080i_fake.Sharpen = 0
softhddevice.1080i_fake.SkipChromaDeinterlace = 0
softhddevice.576i.CutLeftRight = 0
softhddevice.576i.CutTopBottom = 0
softhddevice.576i.Deinterlace = 0
softhddevice.576i.Denoise = 0
softhddevice.576i.FirstField = 0
softhddevice.576i.InverseTelecine = 0
softhddevice.576i.Scaling = 0
softhddevice.576i.SecondField = 0
softhddevice.576i.Sharpen = 0
softhddevice.576i.SkipChromaDeinterlace = 0
softhddevice.60HzMode = 0
softhddevice.720p.CutLeftRight = 0
softhddevice.720p.CutTopBottom = 0
softhddevice.720p.Deinterlace = 0
softhddevice.720p.Denoise = 0
softhddevice.720p.FirstField = 0
softhddevice.720p.InverseTelecine = 0
softhddevice.720p.Scaling = 0
softhddevice.720p.SecondField = 0
softhddevice.720p.Sharpen = 0
softhddevice.720p.SkipChromaDeinterlace = 0
softhddevice.AudioAutoAES = 0
softhddevice.AudioBufferTime = 0
softhddevice.AudioCompression = 0
softhddevice.AudioDelay = 0
softhddevice.AudioDownmix = 0
softhddevice.AudioDrift = 0
softhddevice.AudioMaxCompression = 0
softhddevice.AudioMaxNormalize = 0
softhddevice.AudioNormalize = 0
softhddevice.AudioPassthrough = 0
softhddevice.AudioSoftvol = 0
softhddevice.AudioStereoDescent = 0
softhddevice.AutoCrop.Delay = 0
softhddevice.AutoCrop.Interval = 0
softhddevice.AutoCrop.Tolerance = 0
softhddevice.Background = 0
softhddevice.BlackPicture = 0
softhddevice.Brightness = 0
softhddevice.ClearOnSwitch = 0
softhddevice.Contrast = 1000
softhddevice.DetachFromMainMenu = 0
softhddevice.EnableDPMSatBlackScreen = 0
softhddevice.HideMainMenuEntry = 0
softhddevice.Hue = 0
softhddevice.MakePrimary = 0
softhddevice.MaxSizeGPUImageCache = 128
softhddevice.Osd.Height = 0
softhddevice.Osd.Width = 0
softhddevice.pip.Alt.Height = 50
softhddevice.pip.Alt.VideoHeight = 50
softhddevice.pip.Alt.VideoWidth = 0
softhddevice.pip.Alt.VideoX = 0
softhddevice.pip.Alt.VideoY = 0
softhddevice.pip.Alt.Width = 0
softhddevice.pip.Alt.X = 0
softhddevice.pip.Alt.Y = 50
softhddevice.pip.Height = 18
softhddevice.pip.VideoHeight = 0
softhddevice.pip.VideoWidth = 0
softhddevice.pip.VideoX = 0
softhddevice.pip.VideoY = 0
softhddevice.pip.Width = 18
softhddevice.pip.X = 79
softhddevice.pip.Y = 78
softhddevice.Saturation = 1000
softhddevice.SkinToneEnhancement = 0
softhddevice.SoftStartSync = 0
softhddevice.StudioLevels = 0
softhddevice.Suspend.Close = 0
softhddevice.Suspend.X11 = 0
softhddevice.UHD.CutLeftRight = 0
softhddevice.UHD.CutTopBottom = 0
softhddevice.UHD.Deinterlace = 0
softhddevice.UHD.Denoise = 0
softhddevice.UHD.FirstField = 0
softhddevice.UHD.InverseTelecine = 0
softhddevice.UHD.Scaling = 0
softhddevice.UHD.SecondField = 0
softhddevice.UHD.Sharpen = 0
softhddevice.UHD.SkipChromaDeinterlace = 0
softhddevice.Video4to3DisplayFormat = 1
softhddevice.VideoOtherDisplayFormat = 1
matthias@serrano:~$ systemd-analyze
Startup finished in 6.897s (firmware) + 6.071s (loader) + 3.854s (kernel) + 20.308s (userspace) = 37.131s
graphical.target reached after 20.281s in userspace
matthias@serrano:~$ systemd-analyze blame
13.607s vdr.service
4.362s systemd-networkd-wait-online.service
2.271s snap.lxd.activate.service
2.154s snapd.service
2.135s systemd-udev-settle.service
1.466s dev-sda2.device
1.242s nfs-server.service
1.103s systemd-logind.service

Display More

davie2000 · Oct 18th 2020

Hmmmm ... ich würd mal sagen, dass die ca. 24 s (kernel+userspace) gar nicht so übel sind.

Leider kommen halt nochmal ca. 13 s für firmware+loader dazu - aber das wird bei dieser Karte halt so sein.
Habe ich hier zB nicht.

presskopf · Oct 18th 2020

Okidoki, ich mag Euch natürlich nicht (zwingend) weiter damit belästigen und danke Euch nochmal!

Vielleicht ist es bei vier Tunern (zwo DVBSky) einfach etwas gemütlicher.

Für mich und mein Weibchen ist es kein Beinbruch. Ich habe es nicht aktiv gemessen, aber uns kommt das Focal schneller vor als das das vorige Bionic.

Taipan · Oct 18th 2020

Startup finished in 4.461s (kernel) + 7.532s (userspace) = 11.993s

graphical.target reached after 7.520s in userspace

Allerdings ohne Tuner, als Streaming-Client

davie2000 · Oct 18th 2020

presskopf wrote:

Okidoki, ich mag Euch natürlich nicht (zwingend) weiter damit belästigen und danke Euch nochmal!

Ich empfinde das überhaupt nicht als Belästigung.

In dem Thread gehts genau darum, seine Erfahrung zu teilen, auf dass viell. auch andere davon profitieren (und noch ein paar (Milli)Sekunden rauskitzeln).

presskopf · Oct 19th 2020

Jetzt hat's mich doch nochmal interessiert.

Kann es sein, dass die Firmware vier mal geladen werden muss und dass das die Zeit kostet?

Code

matthias@serrano:~$ sudo journalctl -k | grep -i dvb
[sudo] password for matthias:
Oct 19 19:15:18 serrano systemd[1]: Created slice system-wait\x2dfor\x2ddvb.slice.
Oct 19 19:15:19 serrano kernel: SMI PCIe driver 0000:01:00.0: card detected: DVBSky S952 V3
Oct 19 19:15:19 serrano kernel: dvbdev: DVB: registering new adapter (SMI_DVB)
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)...
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:01:00.0: DVBSky S952 V3 port 0 MAC: 00:18:42:54:55:52
Oct 19 19:15:20 serrano kernel: dvbdev: DVB: registering new adapter (SMI_DVB)
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:01:00.0: DVB: registering adapter 1 frontend 0 (Montage Technology M88RS6000)...
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:01:00.0: DVBSky S952 V3 port 1 MAC: 00:18:32:54:55:53
Oct 19 19:15:20 serrano kernel: Registered IR keymap rc-dvbsky
Oct 19 19:15:20 serrano kernel: rc rc0: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.0/0000:01:00.0/rc/rc0
Oct 19 19:15:20 serrano kernel: input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.0/0000:01:00.0/rc/rc0/input12
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:04:00.0: card detected: DVBSky S952 V3
Oct 19 19:15:20 serrano kernel: dvbdev: DVB: registering new adapter (SMI_DVB)
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:04:00.0: DVB: registering adapter 2 frontend 0 (Montage Technology M88RS6000)...
Oct 19 19:15:20 serrano kernel: SMI PCIe driver 0000:04:00.0: DVBSky S952 V3 port 0 MAC: 00:18:42:54:55:52
Oct 19 19:15:20 serrano kernel: dvbdev: DVB: registering new adapter (SMI_DVB)
Oct 19 19:15:21 serrano kernel: SMI PCIe driver 0000:04:00.0: DVB: registering adapter 3 frontend 0 (Montage Technology M88RS6000)...
Oct 19 19:15:21 serrano kernel: SMI PCIe driver 0000:04:00.0: DVBSky S952 V3 port 1 MAC: 00:18:32:54:55:53
Oct 19 19:15:21 serrano kernel: Registered IR keymap rc-dvbsky
Oct 19 19:15:21 serrano kernel: rc rc1: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.3/0000:04:00.0/rc/rc1
Oct 19 19:15:21 serrano kernel: input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.3/0000:04:00.0/rc/rc1/input13
Oct 19 19:15:29 serrano kernel: m88ds3103 4-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
Oct 19 19:15:32 serrano kernel: m88ds3103 5-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
Oct 19 19:15:35 serrano kernel: m88ds3103 8-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
Oct 19 19:15:38 serrano kernel: m88ds3103 9-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
matthias@serrano:~$ dmesg | grep -i dvb
[ 4.282037] systemd[1]: Created slice system-wait\x2dfor\x2ddvb.slice.
[ 5.165466] SMI PCIe driver 0000:01:00.0: card detected: DVBSky S952 V3
[ 5.280824] dvbdev: DVB: registering new adapter (SMI_DVB)
[ 5.699137] SMI PCIe driver 0000:01:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)...
[ 5.705932] SMI PCIe driver 0000:01:00.0: DVBSky S952 V3 port 0 MAC: 00:18:42:54:55:52
[ 5.713547] dvbdev: DVB: registering new adapter (SMI_DVB)
[ 5.925977] SMI PCIe driver 0000:01:00.0: DVB: registering adapter 1 frontend 0 (Montage Technology M88RS6000)...
[ 5.932839] SMI PCIe driver 0000:01:00.0: DVBSky S952 V3 port 1 MAC: 00:18:32:54:55:53
[ 5.963619] Registered IR keymap rc-dvbsky
[ 5.995726] rc rc0: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.0/0000:01:00.0/rc/rc0
[ 5.995904] input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.0/0000:01:00.0/rc/rc0/input12
[ 6.023785] SMI PCIe driver 0000:04:00.0: card detected: DVBSky S952 V3
[ 6.139919] dvbdev: DVB: registering new adapter (SMI_DVB)
[ 6.378422] SMI PCIe driver 0000:04:00.0: DVB: registering adapter 2 frontend 0 (Montage Technology M88RS6000)...
[ 6.385266] SMI PCIe driver 0000:04:00.0: DVBSky S952 V3 port 0 MAC: 00:18:42:54:55:52
[ 6.385365] dvbdev: DVB: registering new adapter (SMI_DVB)
[ 6.598139] SMI PCIe driver 0000:04:00.0: DVB: registering adapter 3 frontend 0 (Montage Technology M88RS6000)...
[ 6.605002] SMI PCIe driver 0000:04:00.0: DVBSky S952 V3 port 1 MAC: 00:18:32:54:55:53
[ 6.605013] Registered IR keymap rc-dvbsky
[ 6.605036] rc rc1: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.3/0000:04:00.0/rc/rc1
[ 6.605258] input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:13.3/0000:04:00.0/rc/rc1/input13
[ 15.073121] m88ds3103 4-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
[ 18.053881] m88ds3103 5-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
[ 21.009452] m88ds3103 8-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'
[ 23.961236] m88ds3103 9-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw'

Display More

blueink · Dec 17th 2020

Startup finished in 4.656s (kernel) + 12.924s (userspace) = 17.580s

graphical.target reached after 12.901s in userspace

Real Einschalten bis zum Bild und Ton, inklusive Bios: 28 Sekunden

Uwe0815 · Dec 18th 2020

Ich weiß es garnicht und es interessiert mich eigentlich auch nicht.

Ist mir egal, ob es 30, 60 oder 90 Sekunden dauert.

Uwe

Taipan · Dec 18th 2020

Uwe0815

...spielt ja keine Rolle - den Thread-Ersteller interessiert es aber!

Share