Ok, mit dem 384 funktioniert wieder alles.
Danke für Hilfe.
Ok, mit dem 384 funktioniert wieder alles.
Danke für Hilfe.
Ok, dann versuche ich das mal. Aber nicht mehr heute.
Installiert sind die folgenden:
dddvb, 0.9.22.0yavdr0, 3.13.0-121-generic, x86_64: installed
dddvb, 0.9.22.0yavdr0, 3.13.0-125-generic, x86_64: installed
dddvb, 0.9.22.0yavdr0, 3.13.0-129-generic, x86_64: installed
dddvb, 0.9.22.0yavdr0, 3.13.0-132-generic, x86_64: installed
dddvb, 0.9.22.0yavdr0, 3.13.0-133-generic, x86_64: installed
nvidia, 381.22, 3.13.0-121-generic, x86_64: installed
nvidia, 381.22, 3.13.0-125-generic, x86_64: installed
nvidia, 381.22, 3.13.0-129-generic, x86_64: installed
nvidia, 381.22, 3.13.0-132-generic, x86_64: installed
nvidia, 381.22, 3.13.0-133-generic, x86_64: installed
Als ich die GT1030 einbaute habe ich mir den Treiber von der nvidia-Seite von hand installaliert. Das ist der 381.22. Der wird laut kern.log auch geladen.
root@vdr01:~# cat /var/log/kern.log | grep nvidia
Oct 22 22:04:56 vdr01 kernel: [50924.061157] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 23 15:58:12 vdr01 kernel: [ 2.360865] nvidia: module license 'NVIDIA' taints kernel.
Oct 23 15:58:12 vdr01 kernel: [ 2.369504] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
Oct 23 15:58:12 vdr01 kernel: [ 2.372309] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 23 15:58:12 vdr01 kernel: [ 2.373165] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 23 15:58:13 vdr01 kernel: [ 5.947971] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 23 15:58:14 vdr01 kernel: [ 7.019692] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 23 15:58:15 vdr01 kernel: [ 7.504609] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 23 15:58:53 vdr01 kernel: [ 47.620516] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 23 15:59:34 vdr01 kernel: [ 2.457279] nvidia: module license 'NVIDIA' taints kernel.
Oct 23 15:59:34 vdr01 kernel: [ 2.493745] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
Oct 23 15:59:34 vdr01 kernel: [ 2.887774] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 23 15:59:34 vdr01 kernel: [ 2.889003] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 23 15:59:35 vdr01 kernel: [ 5.918464] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 23 15:59:36 vdr01 kernel: [ 6.780473] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 23 15:59:37 vdr01 kernel: [ 7.263641] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 23 20:59:41 vdr01 kernel: [18011.401915] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 24 17:20:30 vdr01 kernel: [ 2.298591] nvidia: module license 'NVIDIA' taints kernel.
Oct 24 17:20:30 vdr01 kernel: [ 2.303317] nvidia: module verification failed: signature and/or required key missing - tainting kernel
Oct 24 17:20:30 vdr01 kernel: [ 2.307543] nvidia-nvlink: Nvlink Core is being initialized, major device number 250
Oct 24 17:20:30 vdr01 kernel: [ 2.324170] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 24 17:20:30 vdr01 kernel: [ 2.326434] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 24 17:20:31 vdr01 kernel: [ 5.994139] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 24 17:20:32 vdr01 kernel: [ 6.989872] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 24 17:20:33 vdr01 kernel: [ 7.555347] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 24 22:38:59 vdr01 kernel: [19115.242088] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 25 15:52:52 vdr01 kernel: [ 2.369527] nvidia: module license 'NVIDIA' taints kernel.
Oct 25 15:52:52 vdr01 kernel: [ 2.397339] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
Oct 25 15:52:52 vdr01 kernel: [ 2.402260] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 25 15:52:52 vdr01 kernel: [ 2.404371] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 25 15:52:53 vdr01 kernel: [ 5.791688] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 25 15:52:54 vdr01 kernel: [ 6.754533] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 25 15:52:55 vdr01 kernel: [ 7.311756] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 25 21:36:58 vdr01 kernel: [20652.260296] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 26 16:11:05 vdr01 kernel: [ 2.281435] nvidia: module license 'NVIDIA' taints kernel.
Oct 26 16:11:05 vdr01 kernel: [ 2.284537] nvidia: module verification failed: signature and/or required key missing - tainting kernel
Oct 26 16:11:05 vdr01 kernel: [ 2.288760] nvidia-nvlink: Nvlink Core is being initialized, major device number 251
Oct 26 16:11:05 vdr01 kernel: [ 2.289695] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 26 16:11:05 vdr01 kernel: [ 2.291008] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 26 16:11:06 vdr01 kernel: [ 5.902717] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 26 16:11:07 vdr01 kernel: [ 6.923789] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 26 16:11:08 vdr01 kernel: [ 7.449173] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 26 16:29:20 vdr01 kernel: [ 1101.607299] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 26 16:29:59 vdr01 kernel: [ 2.370326] nvidia: module license 'NVIDIA' taints kernel.
Oct 26 16:29:59 vdr01 kernel: [ 2.381124] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
Oct 26 16:29:59 vdr01 kernel: [ 2.382038] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 26 16:29:59 vdr01 kernel: [ 2.382254] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 26 16:30:01 vdr01 kernel: [ 6.099674] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 26 16:30:01 vdr01 kernel: [ 6.993146] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 26 16:30:02 vdr01 kernel: [ 7.544730] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 26 22:20:32 vdr01 kernel: [21037.897998] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 27 19:08:41 vdr01 kernel: [ 1.600448] nvidia: module license 'NVIDIA' taints kernel.
Oct 27 19:08:41 vdr01 kernel: [ 1.606585] nvidia-nvlink: Nvlink Core is being initialized, major device number 250
Oct 27 19:08:41 vdr01 kernel: [ 1.955180] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 27 19:08:41 vdr01 kernel: [ 1.955819] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 27 19:08:44 vdr01 kernel: [ 4.849321] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 27 19:08:45 vdr01 kernel: [ 5.752810] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 27 19:08:46 vdr01 kernel: [ 6.277799] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 27 20:14:57 vdr01 kernel: [ 3978.806224] nvidia-modeset: Freed GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Oct 27 20:15:38 vdr01 kernel: [ 2.339461] nvidia: module license 'NVIDIA' taints kernel.
Oct 27 20:15:38 vdr01 kernel: [ 2.351528] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
Oct 27 20:15:38 vdr01 kernel: [ 2.352742] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
Oct 27 20:15:38 vdr01 kernel: [ 2.352964] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Oct 27 20:15:40 vdr01 kernel: [ 6.150581] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 27 20:15:40 vdr01 kernel: [ 7.020976] nvidia 0000:01:00.0: irq 47 for MSI/MSI-X
Oct 27 20:15:41 vdr01 kernel: [ 7.511299] nvidia-modeset: Allocated GPU:0 (GPU-a624d19f-082c-cb8d-0b65-f0a3a473c824) @ PCI:0000:01:00.0
Nicht sehr viel anderes:
method return sender=:1.6 -> dest=:1.46 reply_serial=2
int32 250
string "Remote control disabled"
written backup for DP-0 to /var/lib/vdr/.kodi/.display_cache/DP-0-videodevice.xml
Xlib: extension "GLX" missing on display ":1".
/usr/bin/kodi: line 179: 2230 Segmentation fault "$LIBDIR/${bin_name}/${bin_name}.bin" $SAVED_ARGS
Crash report available at /var/lib/vdr/kodi_crashlog-20171027_201612.log
method return sender=:1.6 -> dest=:1.50 reply_serial=2
int32 250
string "Remote control enabled"
Ein Template für die /etc/init/kodi.conf habe ich nicht . Meine sieht so aus:
#################################################################################
# #
# The following configuration file is generated automatically by the yaVDR #
# system. Don't change this file as every update of yaVDR will overwrite #
# the local changes. Instead put your required customizations #
# into /etc/yavdr/templates_custom/ based on the original templates #
# under /usr/share/yavdr/templates. #
# #
# http://www.yavdr.org/developer-zone/template-overview/ #
# #
# #
#################################################################################
description "XBMC Daemon"
author "Steffen Barszus "
env DISPLAY=:1
export DISPLAY
env HOME=/var/lib/vdr
export HOME
setuid vdr
setgid audio
pre-start script
vdr-dbus-send /Remote remote.Disable ||:
if [ ! -z $STANDALONE ] ; then
touch /tmp/.standalone
fi
if [[ "$DISPLAY" == ":1.1" && "$(dbget vdr.tempdisplay)" == ".1" ]]; then
DISPLAY=":1"
elif [[ "$DISPLAY" == ":1" && "$(dbget vdr.tempdisplay)" == ".1" ]]; then
DISPLAY=":1$(dbget vdr.tempdisplay)"
fi
export DISPLAY
/usr/bin/set-kodi-display ||:
while [ ! -e /var/run/lirc/lircd ]; do sleep 1; done
end script
pre-stop script
kodi-send --action="Quit" ||:
end script
post-stop script
/bin/rm -f /tmp/.standalone
vdr-dbus-send /Remote remote.Enable ||:
sudo /sbin/initctl emit --no-wait vdr-frontend-restart
end script
exec kodi --standalone --lircdev /var/run/lirc/lircd
Hallo,
ich habe gestern mein yarVDR ein update verpasst. Das lief ohne (erkennbare) Probleme duch. Heute muste ich feststellen das kodi nicht mehr startet. Hier die Ausgabe wenn ich versuche kodi von der Konsole zu starten:
Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
Xlib: extension "GLX" missing on display ":1".
/usr/bin/kodi: Zeile 179: 4961 Speicherzugriffsfehler "$LIBDIR/${bin_name}/${bin_name}.bin" $SAVED_ARGS
Im crashlog steht:
19:13:40.618 T:139838134147072 NOTICE: special://profile/ is mapped to: special://masterprofile/
19:13:40.618 T:139838134147072 NOTICE: -----------------------------------------------------------------------
19:13:40.618 T:139838134147072 NOTICE: Starting Kodi (17.4 Git:20170824-nogitfound). Platform: Linux x86 64-bit
19:13:40.618 T:139838134147072 NOTICE: Using Release Kodi x64 build
19:13:40.618 T:139838134147072 NOTICE: Kodi compiled Aug 24 2017 by GCC 4.8.4 for Linux x86 64-bit version 3.13.11 (199947)
19:13:40.618 T:139838134147072 NOTICE: Running on Ubuntu 14.04.5 LTS, kernel: Linux x86 64-bit version 3.13.0-133-generic
19:13:40.618 T:139838134147072 NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
19:13:40.618 T:139838134147072 NOTICE: Host CPU: Intel(R) Core(TM) i5-4690S CPU @ 3.20GHz, 4 cores available
19:13:40.618 T:139838134147072 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
19:13:40.618 T:139838134147072 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/x86_64-linux-gnu/kodi
19:13:40.618 T:139838134147072 NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/x86_64-linux-gnu/kodi/addons
19:13:40.618 T:139838134147072 NOTICE: special://masterprofile/ is mapped to: /var/lib/vdr/.kodi/userdata
19:13:40.618 T:139838134147072 NOTICE: special://envhome/ is mapped to: /var/lib/vdr
19:13:40.618 T:139838134147072 NOTICE: special://home/ is mapped to: /var/lib/vdr/.kodi
19:13:40.618 T:139838134147072 NOTICE: special://temp/ is mapped to: /var/lib/vdr/.kodi/temp
19:13:40.618 T:139838134147072 NOTICE: special://logpath/ is mapped to: /var/lib/vdr/.kodi/temp
19:13:40.618 T:139838134147072 NOTICE: The executable running is: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin
19:13:40.618 T:139838134147072 NOTICE: Local hostname: vdr01
19:13:40.618 T:139838134147072 NOTICE: Log File is located: /var/lib/vdr/.kodi/temp//kodi.log
19:13:40.618 T:139838134147072 NOTICE: -----------------------------------------------------------------------
19:13:40.623 T:139838134147072 ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
19:13:40.634 T:139838134147072 NOTICE: load settings...
19:13:40.641 T:139838134147072 ERROR: PulseAudio: Failed to connect context
19:13:40.641 T:139838134147072 NOTICE: PulseAudio might not be running. Context was not created.
19:13:40.691 T:139838134147072 NOTICE: Found 1 Lists of Devices
19:13:40.691 T:139838134147072 NOTICE: Enumerated ALSA devices:
19:13:40.691 T:139838134147072 NOTICE: Device 1
19:13:40.692 T:139838134147072 NOTICE: m_deviceName : default
19:13:40.692 T:139838134147072 NOTICE: m_displayName : Default (HDA Intel PCH ALC892 Analog)
19:13:40.692 T:139838134147072 NOTICE: m_displayNameExtra:
19:13:40.692 T:139838134147072 NOTICE: m_deviceType : AE_DEVTYPE_PCM
19:13:40.692 T:139838134147072 NOTICE: m_channels : FL,FR,BL,BR,FC,LFE,SL,SR
19:13:40.692 T:139838134147072 NOTICE: m_sampleRates : 44100,48000,96000,192000
19:13:40.692 T:139838134147072 NOTICE: m_dataFormats : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
19:13:40.692 T:139838134147072 NOTICE: m_streamTypes : No passthrough capabilities
19:13:40.692 T:139838134147072 NOTICE: Device 2
19:13:40.692 T:139838134147072 NOTICE: m_deviceName : @:CARD=PCH,DEV=0
19:13:40.692 T:139838134147072 NOTICE: m_displayName : HDA Intel PCH
19:13:40.692 T:139838134147072 NOTICE: m_displayNameExtra: ALC892 Analog
19:13:40.692 T:139838134147072 NOTICE: m_deviceType : AE_DEVTYPE_PCM
19:13:40.692 T:139838134147072 NOTICE: m_channels : FL,FR,BL,BR,FC,LFE,SL,SR
19:13:40.692 T:139838134147072 NOTICE: m_sampleRates : 48000
19:13:40.692 T:139838134147072 NOTICE: m_dataFormats : AE_FMT_S32NE
19:13:40.692 T:139838134147072 NOTICE: m_streamTypes : No passthrough capabilities
19:13:40.692 T:139838134147072 NOTICE: Device 3
19:13:40.692 T:139838134147072 NOTICE: m_deviceName : iec958:CARD=PCH,DEV=0
19:13:40.692 T:139838134147072 NOTICE: m_displayName : HDA Intel PCH
19:13:40.692 T:139838134147072 NOTICE: m_displayNameExtra: ALC892 Digital S/PDIF
19:13:40.692 T:139838134147072 NOTICE: m_deviceType : AE_DEVTYPE_IEC958
19:13:40.692 T:139838134147072 NOTICE: m_channels : FL,FR
19:13:40.692 T:139838134147072 NOTICE: m_sampleRates : 32000,44100,48000,88200,96000,192000
19:13:40.692 T:139838134147072 NOTICE: m_dataFormats : AE_FMT_RAW,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
19:13:40.692 T:139838134147072 NOTICE: m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512
19:13:40.692 T:139838134147072 NOTICE: Device 4
19:13:40.692 T:139838134147072 NOTICE: m_deviceName : hdmi:CARD=NVidia,DEV=0
19:13:40.692 T:139838134147072 NOTICE: m_displayName : HDA NVidia
19:13:40.692 T:139838134147072 NOTICE: m_displayNameExtra: HDMI
19:13:40.692 T:139838134147072 NOTICE: m_deviceType : AE_DEVTYPE_HDMI
19:13:40.692 T:139838134147072 NOTICE: m_channels : FL,FR
19:13:40.692 T:139838134147072 NOTICE: m_sampleRates : 32000,44100,48000,88200,96000,176400,192000
19:13:40.692 T:139838134147072 NOTICE: m_dataFormats : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
19:13:40.692 T:139838134147072 NOTICE: m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD
19:13:40.695 T:139838134147072 NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
19:13:40.696 T:139838134147072 NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
19:13:40.696 T:139838134147072 NOTICE: Default Video Player: VideoPlayer
19:13:40.696 T:139838134147072 NOTICE: Default Audio Player: paplayer
19:13:40.696 T:139838134147072 NOTICE: Disabled debug logging due to GUI setting. Level 0.
19:13:40.696 T:139838134147072 NOTICE: Log level changed to "LOG_LEVEL_NORMAL"
19:13:40.696 T:139838134147072 NOTICE: CMediaSourceSettings: loading media sources from special://masterprofile/sources.xml
19:13:40.696 T:139838134147072 NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
19:13:40.696 T:139838134147072 NOTICE: Loaded playercorefactory configuration
19:13:40.696 T:139838134147072 NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
19:13:40.696 T:139838134147072 NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
19:13:40.703 T:139838134147072 NOTICE: Running database version Addons27
19:13:40.743 T:139838134147072 NOTICE: ADDONS: Using repository repository.xbmc.org
19:13:40.902 T:139838134147072 NOTICE: Checking resolution 16
19:13:40.943 T:139838134147072 ERROR: Failed to find matching visual
Ja, das war's. Danke.
Upstart ist mir leider nicht so geläufig wie /etc/init.d/ Scripte.
Nein, nur openbox. Da habe ich aber das selbe Problem wie mit X. Er startet immer wieder neu.
root@vdr01:/home/udo# ps -ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:01 /sbin/init
2 ? S 0:00 [kthreadd]
3 ? S 0:00 [ksoftirqd/0]
5 ? S< 0:00 [kworker/0:0H]
7 ? S 0:02 [rcu_sched]
8 ? S 0:00 [rcuos/0]
9 ? S 0:00 [rcuos/1]
10 ? S 0:01 [rcuos/2]
11 ? S 0:01 [rcuos/3]
12 ? S 0:00 [rcu_bh]
13 ? S 0:00 [rcuob/0]
14 ? S 0:00 [rcuob/1]
15 ? S 0:00 [rcuob/2]
16 ? S 0:00 [rcuob/3]
17 ? S 0:01 [migration/0]
18 ? S 0:00 [watchdog/0]
19 ? S 0:00 [watchdog/1]
20 ? S 0:00 [migration/1]
21 ? S 0:00 [ksoftirqd/1]
23 ? S< 0:00 [kworker/1:0H]
24 ? S 0:00 [watchdog/2]
25 ? S 0:00 [migration/2]
26 ? S 0:00 [ksoftirqd/2]
28 ? S< 0:00 [kworker/2:0H]
29 ? S 0:00 [watchdog/3]
30 ? S 0:00 [migration/3]
31 ? S 0:00 [ksoftirqd/3]
33 ? S< 0:00 [kworker/3:0H]
34 ? S< 0:00 [khelper]
35 ? S 0:00 [kdevtmpfs]
36 ? S< 0:00 [netns]
37 ? S< 0:00 [writeback]
38 ? S< 0:00 [kintegrityd]
39 ? S< 0:00 [bioset]
41 ? S< 0:00 [kblockd]
42 ? S< 0:00 [ata_sff]
43 ? S 0:00 [khubd]
44 ? S< 0:00 [md]
45 ? S< 0:00 [devfreq_wq]
46 ? S 0:12 [kworker/0:1]
48 ? S 0:00 [khungtaskd]
49 ? S 0:00 [kswapd0]
50 ? S< 0:00 [vmstat]
51 ? SN 0:00 [ksmd]
52 ? SN 0:00 [khugepaged]
53 ? S 0:00 [fsnotify_mark]
54 ? S 0:00 [ecryptfs-kthrea]
55 ? S< 0:00 [crypto]
67 ? S< 0:00 [kthrotld]
88 ? S< 0:00 [deferwq]
89 ? S< 0:00 [charger_manager]
136 ? S< 0:00 [kpsmoused]
151 ? S 0:00 [scsi_eh_0]
152 ? S 0:00 [scsi_eh_1]
153 ? S 0:00 [scsi_eh_2]
154 ? S 0:00 [scsi_eh_3]
155 ? S 0:00 [scsi_eh_4]
156 ? S 0:00 [scsi_eh_5]
158 ? S 0:00 [kworker/u8:3]
159 ? S 0:00 [kworker/u8:4]
162 ? S 0:00 [kworker/u8:7]
176 ? S 0:00 [jbd2/sdb1-8]
177 ? S< 0:00 [ext4-rsv-conver]
322 ? Ss 0:00 /lib/systemd/systemd-udevd --daemon
369 ? S 0:00 [irq/45-mei_me]
383 ? S< 0:00 [ddbridge]
400 ? S< 0:00 [hd-audio0]
427 ? S< 0:00 [hd-audio1]
440 ? S< 0:00 [kvm-irqfd-clean]
547 ? Ss 0:00 rpcbind
577 ? Ss 0:00 rpc.statd -L
618 ? S 0:00 [scsi_eh_6]
619 ? S 0:00 [usb-storage]
700 ? S< 0:00 [xfsalloc]
701 ? S< 0:00 [xfs_mru_cache]
702 ? S< 0:00 [xfslogd]
703 ? S< 0:00 [xfs-data/sda1]
704 ? S< 0:00 [xfs-conv/sda1]
705 ? S< 0:00 [xfs-cil/sda1]
706 ? S< 0:00 [xfs-reclaim/sda]
707 ? S< 0:00 [xfs-log/sda1]
708 ? S< 0:00 [xfs-eofblocks/s]
709 ? S< 0:00 [kworker/0:1H]
710 ? S 0:00 [xfsaild/sda1]
739 ? S< 0:00 [rpciod]
742 ? S<s 0:00 /usr/sbin/eventlircd -f --socket=/var/run/lirc/lircd
746 ? S< 0:00 [nfsiod]
749 ? Ss 0:00 /usr/bin/irexec /etc/lirc/lircrc
763 ? Ss 0:00 smbd -F
775 ? Ss 0:00 rpc.idmapd
793 ? Ss 0:00 dbus-daemon --system --fork
794 ? Ss 0:00 /usr/sbin/lircd --nodaemon --output=/var/run/lirc/lircd.794 --driver=irman --device=/dev/ttyatric
801 ? Ss 0:00 /usr/bin/python /usr/bin/lircd2uinput
848 ? Ss 0:00 /lib/systemd/systemd-logind
859 ? Ssl 0:00 rsyslogd
868 ? S 0:00 avahi-daemon: running [vdr01.local]
869 ? S 0:00 avahi-daemon: chroot helper
871 ? S 0:00 smbd -F
883 ? S 0:00 smbd -F
894 ? S< 0:00 [kworker/u9:2]
1105 ? Ss 0:00 dhclient -1 -v -pf /run/dhclient.p2p1.pid -lf /var/lib/dhcp/dhclient.p2p1.leases p2p1
1198 ? Ssl 0:00 /usr/bin/tntnet
1222 ? Ss 0:00 dbus-daemon --config-file=/var/lib/vdr/plugins/dbus2vdr/network.conf --address=tcp:host=vdr01,bind=*,port=0 --print-address
1238 ? Ss 0:00 nmbd -D
1304 ? S< 0:00 [cifsiod]
1333 ? S 0:00 [cifsd]
1341 tty4 Ss+ 0:00 /sbin/getty -8 38400 tty4
1342 tty5 Ss+ 0:00 /sbin/getty -8 38400 tty5
1350 ? S 0:00 [nfsv4.0-svc]
1377 tty3 Ss+ 0:00 /sbin/getty -8 38400 tty3
1386 tty6 Ss+ 0:00 /sbin/getty -8 38400 tty6
1414 ? Ss 0:00 /usr/sbin/sshd -D
1427 ? Ss 0:00 acpid -c /etc/acpi/events -s /var/run/acpid.socket
1429 ? Ss 0:00 cron
1430 ? Ss 0:00 atd
1469 ? Ssl 0:00 /usr/sbin/automount
1497 ? Ssl 0:00 /usr/bin/python3 /usr/bin/avahi-linker
1500 ? Ssl 0:00 python3 /usr/bin/prevent-umount-on-pause
1692 ? S< 0:00 [nfsd4]
1693 ? S< 0:00 [nfsd4_callbacks]
1694 ? S 0:00 [lockd]
1697 ? S 0:00 [nfsd]
1698 ? S 0:00 [nfsd]
1699 ? S 0:00 [nfsd]
1700 ? S 0:00 [nfsd]
1701 ? S 0:00 [nfsd]
1702 ? S 0:00 [nfsd]
1703 ? S 0:00 [nfsd]
1704 ? S 0:00 [nfsd]
1707 ? Ss 0:00 /usr/sbin/rpc.mountd --manage-gids
1808 ? S 0:00 [kauditd]
2055 ? Ss 0:00 sshd: udo [priv]
2170 ? S 0:00 sshd: udo@pts/3
2171 pts/3 Ss 0:00 -bash
2188 pts/3 S 0:00 su
2200 pts/3 S 0:00 bash
2289 tty1 Ss+ 0:00 /sbin/getty -8 38400 tty1
2653 ? Sl 0:00 /usr/lib/udisks/udisks-daemon --no-debug
2655 ? S 0:00 udisks-daemon: not polling any devices
2848 ? S 0:00 [kworker/3:0]
2860 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon
2926 ? Sl 0:00 /usr/lib/policykit-1/polkitd --no-debug
2968 ? Ss 0:00 su -c ck-launch-session udisks-glue -c /etc/udisks-glue/config --foreground vdr
2979 ? Ss 0:00 ck-launch-session udisks-glue -c /etc/udisks-glue/config --foreground
2987 ? S 0:00 udisks-glue -c /etc/udisks-glue/config --foreground
3015 ? S 0:00 upstart-udev-bridge --daemon
3018 ? S 0:00 upstart-socket-bridge --daemon
3021 ? S 0:00 upstart-file-bridge --daemon
3510 ? S 0:00 [kworker/1:1]
3701 ? S 0:00 [kworker/u8:0]
4448 ? S 0:00 [kworker/0:0]
4791 ? S< 0:00 [kworker/u9:1]
4809 tty2 Ss+ 0:00 /sbin/getty -8 38400 tty2
4870 ? S 0:00 [kworker/3:2]
5088 ? S<sl 0:30 /usr/bin/vdr
5111 ? S 0:00 [kdvb-ad-0-fe-0]
5115 ? D 0:05 [kdvb-ad-1-fe-0]
5118 ? S 0:00 [kdvb-ad-2-fe-0]
5121 ? S 0:00 [kdvb-ad-3-fe-0]
5166 ? Ss 0:00 /usr/bin/python3 /usr/bin/vdr-net-monitor
5169 ? Ssl 0:00 /usr/bin/python3 /usr/bin/vdr-update-monitor -w /srv/vdr/video.00/.update
5185 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
5187 ? Ss 0:00 /usr/bin/openbox --config-file /etc/openbox/rc.xml --startup /sbin/initctl emit --no-wait openbox-started
5191 ? S 0:00 [irq/47-nvidia]
5192 ? S 0:00 [nvidia]
5193 ? S 0:00 [kworker/1:4]
5212 ? S 0:00 wmdrawer -c /etc/wmdrawer/system
5224 ? S 0:00 [kworker/2:5]
5225 ? S 0:00 [kworker/2:7]
5255 ? Ssl 0:00 /usr/bin/python3 /usr/bin/on_vdr -c python /usr/bin/frontend
5257 ? S 0:00 python /usr/bin/frontend
5286 ? S 0:00 wmdrawer -c /etc/wmdrawer/web
5316 ? S 0:00 wmdrawer -c /etc/wmdrawer/media
5347 ? S 0:00 wmdrawer -c /etc/wmdrawer/games
5377 ? S 0:00 wmdrawer -c /etc/wmdrawer/tools
5650 ? S 0:00 [kworker/u8:1]
5654 pts/3 R+ 0:00 ps -ax
root@vdr01:/home/udo#
Ich bin über ssh angemeldet, ich denke da hat das keinen Sinn, oder ? Was sollte da passieren ? (Ah: X-Server neu starten. Will ich aber nicht. Ich will in beenden) Bei mir passiert nicht's.
Nö, auch nicht.
root@vdr01:/home/udo# killall X
X: Kein Prozess gefunden
root@vdr01:/home/udo# ps -ax | grep X
4862 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
5065 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# kill $(pidof X)
root@vdr01:/home/udo# ps -ax | grep X
5146 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# ps -ax | grep X
5185 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
5230 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo#
Alles anzeigen
Nö, leider nicht.
root@vdr01:/home/udo# init 3
root@vdr01:/home/udo# ps -ax | grep X
3795 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
4220 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# ps -ax | grep X
3795 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
4223 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# init 3
root@vdr01:/home/udo# ps -ax | grep X
3795 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
4275 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# kill 3795
root@vdr01:/home/udo# ps -ax | grep X
4436 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo# ps -ax | grep X
4451 tty7 Ss+ 0:00 /usr/bin/X -nolisten tcp -noreset :1 vt7
4460 pts/3 S+ 0:00 grep --color=auto X
root@vdr01:/home/udo#
Alles anzeigen
Hallo,
ich möchte ein Grafiktreiber (nvidia-381) von Hand installieren. Dabei sagt er mir das noch ein X Server läuft. Alle meine Versuche
den zu beenden sind bis jetzt gescheitert. Selbst der kill Befehl hilft nicht (der x server erschein nach kurzer Zeit wieder in ps -ax mit neuer pid).
In htop habe ich auch versucht die programme zu beenden. Der selbe Effekt, nach kurzer Zeit starten sie wieder neu.
Ich bin da etwas genervt wegen so einer einfachen Aufgabe das Forum fragen zu müssen. Also: Wie kann ich den X-Server (und auch die anderen Progrannme) in yavdr beenden (ohne das sie wieder neu starten) ? Ich bin dabei über ssh angemeldet.
Hallo,
ich versuche gerade ein vdr mit den e-tobi-Paketquellen einzurichten.
Ich bin hinter einem apt-cacher-ng Proxy, der in der apt-conf als Acquire::http::proxy eingetragen ist.
Ich habe Debian Jessie (minimal) installiert.
Dann die Paketquellen zu source.list hinzugefügt:
# deb cdrom:[Debian GNU/Linux 8.1.0 _Jessie_ - Official Multi-architecture amd64/i386 NETINST #1 20150606-18:40]/ jessie main
#deb cdrom:[Debian GNU/Linux 8.1.0 _Jessie_ - Official Multi-architecture amd64/i386 NETINST #1 20150606-18:40]/ jessie main
deb http://ftp.de.debian.org/debian/ jessie main non-free contrib
deb-src http://ftp.de.debian.org/debian/ jessie main non-free contrib
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free
# deb http://www.debian-multimedia.org testing main
deb http://e-tobi.net/vdr-experimental jessie base addons vdr-multipatch
Alles anzeigen
Bei einem apt-get update erhalte ich:
.
.
.
Fehl http://e-tobi.net jessie/base amd64 Packages
500 Bad redirection (invalid URL)
Fehl http://e-tobi.net jessie/addons amd64 Packages
500 Bad redirection (invalid URL)
Fehl http://e-tobi.net jessie/vdr-multipatch amd64 Packages
500 Bad redirection (invalid URL)
.
.
.
W: Fehlschlag beim Holen von http://e-tobi.net/vdr-experimental/dists/jessie/base/binary-amd64/Packages 500 Bad redirection (invalid URL)
W: Fehlschlag beim Holen von http://e-tobi.net/vdr-experimental/dists/jessie/addons/binary-amd64/Packages 500 Bad redirection (invalid URL)
W: Fehlschlag beim Holen von http://e-tobi.net/vdr-experimental/dists/jessie/vdr-multipatch/binary-amd64/Packages 500 Bad redirection (invalid URL)
E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.
Alles anzeigen
Ok, da er die Seiten auf https umgestellt hat, dachte ich den source.list Eintrag ändern:
Das brachte dann das:
E: Der Treiber f�r Methode /usr/lib/apt/methods/https konnte nicht gefunden werden.
N: Ist das Paket apt-transport-https installiert?
Ok, apt-get install apt-transport-https ausgeführt. Dann apt-get update:
.
.
.
Fehl https://e-tobi.net jessie/base amd64 Packages
Received HTTP code 403 from proxy after CONNECT
Fehl https://e-tobi.net jessie/addons amd64 Packages
Received HTTP code 403 from proxy after CONNECT
Fehl https://e-tobi.net jessie/vdr-multipatch amd64 Packages
Received HTTP code 403 from proxy after CONNECT
.
.
.
W: Fehlschlag beim Holen von https://e-tobi.net/vdr-experimental/dists/jessie/base/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT
W: Fehlschlag beim Holen von https://e-tobi.net/vdr-experimental/dists/jessie/addons/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT
W: Fehlschlag beim Holen von https://e-tobi.net/vdr-experimental/dists/jessie/vdr-multipatch/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT
E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.
Alles anzeigen
Ein zusätzlicher Eintrag Acquire::https::proxy in der apt.conf hat nichts geändert.
Was mache ich falsch bzw. fehlt noch ?