Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - kater_mikesch

Seiten: [1]
1
Sundtek MediaTV Pro / Re:[USB 3.0] Freeze durch USB DVB-C Stick ?
« am: November 18, 2014, 10:30:25 Nachmittag »
Kannst du usb 3.0 im bios deaktivieren(xhci)?
Schau dir sonst folgenden Thread noch einmal an:
http://support.sundtek.com/index.php/topic,1756.0.html

2
Sundtek MediaTV Pro / Re:VDR mit zwei Sundtek Devices
« am: November 15, 2014, 07:41:29 Nachmittag »
Hallo Sundtek,

vielen Dank für die Antwort.

Ich habe die Maschine einmal durchgestartet, der Fehler ist weiterhin vorhanden.

ps fax | grep vdr:
/usr/bin/vdr -v /srv/vdr/video.00 -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s -E /var/cache/vdr/epg.data -u vdr -g /tmp --port 6419 --resdir=/usr/share/vdr --cachedir=/var/cachevdr --dirnames=,,1 --lirc=/var/run/lirc/lircd -w 60 -P vnsiserver -t 10

cat /etc/defaults/vdr:
# /etc/default/vdr
#
# See also /usr/share/doc/vdr/README.Debian.gz
#

# Change to 1 to enable vdr's init-script
ENABLED=1

# Change this to 1 if you want vdr to be able to shutdown the
# computer
ENABLE_SHUTDOWN=0

# Options that will be passed to vdr's commandline
# for example: OPTIONS="-w 15"
OPTIONS="-w 60"

cat /var/lib/vdr/setup.conf:
AlwaysSortFoldersFirst = 1
AntiAlias = 1
AudioLanguages =
ChannelEntryTimeout = 1000
ChannelInfoPos = 0
ChannelInfoTime = 5
ChannelsWrap = 0
ColorKey0 = 0
ColorKey1 = 1
ColorKey2 = 2
ColorKey3 = 3
CurrentChannel = 1
CurrentDolby = 0
CurrentVolume = 255
DefaultLifetime = 99
DefaultPriority = 50
DelTimeshiftRec = 0
DeviceBondings =
DiSEqC = 0
DisplaySubtitles = 0
EmergencyExit = 1
EPGBugfixLevel = 3
EPGLanguages =
EPGLinger = 0
EPGScanTimeout = 5
FoldersInTimerMenu = 1
FontFix = Courier:Bold
FontFixSize = 14
FontFixSizeP = 0.030000
FontOsd = Sans Serif:Bold
FontOsdSize = 15
FontOsdSizeP = 0.031000
FontSml = Sans Serif
FontSmlSize = 13
FontSmlSizeP = 0.028000
InitialChannel =
InitialVolume = -1
InstantRecordTime = 180
JumpPlay = 0
JumpSeconds = 60
JumpSecondsSlow = 10
LnbFrequHi = 10600
LnbFrequLo = 9750
LnbSLOF = 11700
MarginStart = 2
MarginStop = 10
MarkInstantRecord = 1
MaxVideoFileSize = 2000
MenuKeyCloses = 0
MenuScrollPage = 1
MenuScrollWrap = 0
MinEventTimeout = 30
MinUserInactivity = 300
MultiSpeedMode = 0
NameInstantRecord = TITLE EPISODE
NextWakeupTime = 0
NumberKeysForChars = 1
OSDAspect = 1.000000
OSDHeight = 403
OSDHeightP = 0.840000
OSDLanguage =
OSDLeft = 58
OSDLeftP = 0.080000
OSDMessageTime = 1
OSDSkin = lcars
OSDTheme = default
OSDTop = 38
OSDTopP = 0.080000
OSDWidth = 624
OSDWidthP = 0.870000
PauseKeyHandling = 2
PauseLastMark = 0
PauseLifetime = 1
PauseOnMarkSet = 0
PausePriority = 10
PlayJump = 0
PositionerLastLon = 0
PositionerSpeed = 15
PositionerSwing = 650
PrimaryDVB = 1
ProgressDisplayTime = 0
RcRepeatDelay = 300
RcRepeatDelta = 100
RecordingDirs = 1
ResumeID = 0
SetSystemTime = 0
ShowChannelNamesWithSource = 0
ShowInfoOnChSwitch = 1
ShowRemainingTime = 0
ShowReplayMode = 0
SiteLat = 0
SiteLon = 0
SplitEditedFiles = 0
StandardCompliance = 0
SubtitleBgTransparency = 0
SubtitleFgTransparency = 0
SubtitleLanguages =
SubtitleOffset = 0
SVDRPTimeout = 300
TimeoutRequChInfo = 1
TimeSource =
TimeTransponder = 0
UpdateChannels = 0
UseDolbyDigital = 1
UsePositioner = 0
UseSmallFont = 1
UseSubtitle = 1
UseVps = 0
VideoDisplayFormat = 1
VideoFormat = 0
VpsMargin = 120
ZapTimeout = 3


Kann ich eventuell mit weiteren Logs oder Configs weiterhelfen?

3
Sundtek MediaTV Pro / VDR mit zwei Sundtek Devices
« am: November 15, 2014, 06:32:48 Nachmittag »
Hallo Zusammen,

ich habe an meinem VDR zwei DVB Karten von Sundtek laufen. Ein paralleles Fernsehen von bei zwei Fernsehern ist jedoch nicht möglich. Muss man seitens sundtek conf oder VDR noch Einstellungen tätigen? Liegt es vielleicht am VNSI-Server? Müssen hier weitere Einstellungen getätigt werden? Besten Dank bereits im Voraus.


sudo /opt/bin/mediaclient -e:
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Digital Home (USB 2.0)]  DVB-C, DVB-T, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1.5
  [SERIAL]:
     ID: U121211082239
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

device 1: [MediaTV Pro III USB (EU)]  DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1.6
  [SERIAL]:
     ID: U140808190409
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput1
  [OSS]:
     OSS0: /dev/dsp0

vdr -V:
vdr (2.1.6/2.1.6) - The Video Disk Recorder
vnsiserver (1.1.0) - VDR-Network-Streaming-Interface (VNSI) Server

sudo /opt/bin/mediaclient --lc:
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  1672 ... vdr
  1672 ... vdr
/dev/dvb/adapter0/dvr0:
  1672 ... vdr
/dev/dvb/adapter0/demux0:
  1672 ... vdr (0012)
  1672 ... vdr (0014)
  1672 ... vdr (0000)
  1672 ... vdr (0011)
  1672 ... vdr (0010)
  1672 ... vdr (0069)
  1672 ... vdr (1a05)
  1672 ... vdr (1a06)
  1672 ... vdr (1a07)
  1672 ... vdr (1a09)
  1672 ... vdr (1a0a)
  1672 ... vdr (1a08)
  1672 ... vdr (0068)
/dev/mediainput0:
  No client connected
/dev/dvb/adapter1/frontend0:
  No client connected
/dev/dvb/adapter1/dvr0:
  No client connected
/dev/dvb/adapter1/demux0:
  No client connected
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput1:
  No client connected
/dev/dsp0:
  No client connected

lsb_release -a:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise

4
Sundtek MediaTV Pro / Re:Oops Kernal Panic MediaTV Pro III
« am: November 15, 2014, 06:26:26 Nachmittag »
Hallo Zusammen,

es funktioniert mit den Einstellungen im BIOS einwandfrei.

Besten Dank!

5
Sundtek MediaTV Pro / Re:Oops Kernal Panic MediaTV Pro III
« am: November 12, 2014, 09:01:47 Nachmittag »
Hallo Sundtek und Cheese,

vielen Dank für die Unterstützung.

Ich habe nun im BIOS folgende Einstellung deaktiviert:
ASUS BIOS-->Advanced Mode-->Advanced-->USB Configuration-->Intel xHCI Mode-->Deaktivieren

Ich werde entsprechendes Feedback geben, ob das System die 24 Stunden schafft :-)

6
Sundtek MediaTV Pro / Re:Oops Kernal Panic MediaTV Pro III
« am: November 08, 2014, 07:52:15 Vormittag »
Das Problem besteht trotz neuster Treiber weiterhin

7
Sundtek MediaTV Pro / Re:Oops Kernal Panic MediaTV Pro III
« am: November 05, 2014, 07:48:33 Nachmittag »
Ich habe gerade gesehen, dass seit dem 04.11.2014 neue Treiber zur Verfügung stehen. Ich habe diese jetzt installiert. Können die neuen Treiber die o.g. Probleme beheben?

8
Sundtek MediaTV Pro / Re:Oops Kernal Panic MediaTV Pro III
« am: November 05, 2014, 07:10:27 Nachmittag »
Hier hatte ich im Forum einen ähnlichen Fehler, zumindest mit anscheinend gleicher Ursache gefunden:

http://support.sundtek.com/index.php?topic=1600.20;wap2

Ursache:
xhci_queue_new_dequeue_state+0x6c/0xe0

Hier noch ein paar mehr Informationen:

sudo /opt/bin/mediaclient -e:
**** List of Media Hardware Devices ****
device 0: [MediaTV Pro III USB (EU)]  DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 3-3
  [SERIAL]:
     ID: U140808190409
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0

sudo /opt/bin/mediaclient --cpucheck:
Sundtek CPU Check

cpu0:
   this cpu is using the ondemand scheduler
   this might cause some performance issue, please take care
   that the cpu frequency will not change while using the
   TV Tuner

   current scheduler: ondemand
   available schedulers: conservative ondemand userspace powersave performance
   to change the scheduler you might run following command:

   echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

cpu1:
   this cpu is using the ondemand scheduler
   this might cause some performance issue, please take care
   that the cpu frequency will not change while using the
   TV Tuner

   current scheduler: ondemand
   available schedulers: conservative ondemand userspace powersave performance
   to change the scheduler you might run following command:

   echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

cpu2:
   this cpu is using the ondemand scheduler
   this might cause some performance issue, please take care
   that the cpu frequency will not change while using the
   TV Tuner

   current scheduler: ondemand
   available schedulers: conservative ondemand userspace powersave performance
   to change the scheduler you might run following command:

   echo performance > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

cpu3:
   this cpu is using the ondemand scheduler
   this might cause some performance issue, please take care
   that the cpu frequency will not change while using the
   TV Tuner

   current scheduler: ondemand
   available schedulers: conservative ondemand userspace powersave performance
   to change the scheduler you might run following command:

   echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

vdr -V:
vdr (2.1.6/2.1.6) - The Video Disk Recorder
vnsiserver (1.1.0) - VDR-Network-Streaming-Interface (VNSI) Server

sudo /opt/bin/mediaclient --lc:
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  1949 ... vdr
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  1949 ... vdr (0012)
  1949 ... vdr (0014)
  1949 ... vdr (0000)
  1949 ... vdr (0011)
  1949 ... vdr (0010)
  1949 ... vdr (044c)
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput0:
  No client connected
/dev/dsp0:
  No client connected

9
Sundtek MediaTV Pro / [USB 3.0] Oops Kernal Panic MediaTV Pro III
« am: November 05, 2014, 07:08:01 Nachmittag »
Hallo Sundtek Support Team,

nach Kauf und Anschluss des MediaTV Pro III friert mein Ubuntu Nas permanent ein. Nach langen Recherchen und der Übersetzung der Kernal Panic logs in /var/log/syslog bin ich mir ziemlich sicher, dass es an der Hardware bzw. den Treibern in Kombination mit meinem System liegt. Den RAM habe ich mit Memtes86 für ca. 12 Stunden getesetet. Es traten keine Fehler auf. Ebenfalls habe ich das OS auf die neuste LTS 14.04.xx angehoben. Zur Sicherheit, habe ich das neuste Release neu installiert, weil ich dachte es lag am Upgrade. Momentan bin ich zurück auf 12.04.05 LTS.

Das erste was vor dem Einfrireren passiert, ist die Beendung des VDRs, danach folgt das Netzwerk. Das System kann dann nur noch hart ausgeschaltet werden. Ich habe das System nun seit 24 Stunden ohne TV Karte laufen, es läuft einwandfrei durch. Mit TV-Karte läuft es max. 12 Stunden.

Welche weiteren Informationen kann ich liefern, sodass die TV-Karte eventuell augegrenzt werden kann oder wenn es die TV-Karte ist, wir das Problem eingrenzen oder lösen können?


lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise

Auszug aus /var/log/syslog:
Nov  3 20:07:19 tmp kernel: [83418.116752] ------------[ cut here ]------------
Nov  3 20:07:19 tmp kernel: [83418.116773] WARNING: CPU: 0 PID: 1485 at /build/buildd/linux-lts-trusty-3.13.0/drivers/usb/host/xhci-ring.c:613 xhci_find_new_dequeue_state+0x191/0x2e
Nov  3 20:07:19 tmp kernel: [83418.116777] Modules linked in: joydev hid_generic usbhid hid snd_hda_codec_hdmi nfsd nfs_acl auth_rpcgss nfs fscache lockd sunrpc eeepc_wmi asus_wmi s
Nov  3 20:07:19 tmp kernel: [83418.116855] CPU: 0 PID: 1485 Comm: mediasrv Not tainted 3.13.0-32-generic #57~precise1-Ubuntu
Nov  3 20:07:19 tmp kernel: [83418.116859] Hardware name: ASUS All Series/H87I-PLUS, BIOS 2002 07/22/2014
Nov  3 20:07:19 tmp kernel: [83418.116862]  0000000000000265 ffff8800d37c9be8 ffffffff81752c9e 0000000000000007
Nov  3 20:07:19 tmp kernel: [83418.116870]  0000000000000000 ffff8800d37c9c28 ffffffff8106af7c ffffffff81590ca0
Nov  3 20:07:19 tmp kernel: [83418.116876]  ffff8801159c0000 ffff8800d37c9cb0 ffff880035f1fd80 00000000d377f400
Nov  3 20:07:19 tmp kernel: [83418.116883] Call Trace:
Nov  3 20:07:19 tmp kernel: [83418.116896]  [<ffffffff81752c9e>] dump_stack+0x46/0x58
Nov  3 20:07:19 tmp kernel: [83418.116907]  [<ffffffff8106af7c>] warn_slowpath_common+0x8c/0xc0
Nov  3 20:07:19 tmp kernel: [83418.116917]  [<ffffffff81590ca0>] ? trace_xhci_dbg_quirks+0x70/0x70
Nov  3 20:07:19 tmp kernel: [83418.116925]  [<ffffffff8106afca>] warn_slowpath_null+0x1a/0x20
Nov  3 20:07:19 tmp kernel: [83418.116931]  [<ffffffff8159eaf1>] xhci_find_new_dequeue_state+0x191/0x2e0
Nov  3 20:07:19 tmp kernel: [83418.116939]  [<ffffffff81594d58>] xhci_cleanup_stalled_ring+0x78/0x100
Nov  3 20:07:19 tmp kernel: [83418.116947]  [<ffffffff81594f16>] xhci_endpoint_reset+0x136/0x190
Nov  3 20:07:19 tmp kernel: [83418.116956]  [<ffffffff8156737e>] ? usb_alloc_urb+0x1e/0x50
Nov  3 20:07:19 tmp kernel: [83418.116963]  [<ffffffff815669d5>] usb_hcd_reset_endpoint+0x25/0x70
Nov  3 20:07:19 tmp kernel: [83418.116970]  [<ffffffff81569ac8>] usb_enable_endpoint+0xa8/0xb0
Nov  3 20:07:19 tmp kernel: [83418.116977]  [<ffffffff81569b12>] usb_enable_interface+0x42/0x60
Nov  3 20:07:19 tmp kernel: [83418.116983]  [<ffffffff8156a006>] usb_set_interface+0x1f6/0x340
Nov  3 20:07:19 tmp kernel: [83418.116992]  [<ffffffff81574339>] usbdev_do_ioctl+0x589/0xc50
Nov  3 20:07:19 tmp kernel: [83418.117003]  [<ffffffff811182cc>] ? acct_account_cputime+0x1c/0x20
Nov  3 20:07:19 tmp kernel: [83418.117013]  [<ffffffff810a25e9>] ? account_user_time+0x99/0xb0
Nov  3 20:07:19 tmp kernel: [83418.117020]  [<ffffffff81574a2e>] usbdev_ioctl+0xe/0x20
Nov  3 20:07:19 tmp kernel: [83418.117027]  [<ffffffff811dc5c5>] do_vfs_ioctl+0x75/0x2c0
Nov  3 20:07:19 tmp kernel: [83418.117034]  [<ffffffff81022735>] ? syscall_trace_enter+0x165/0x280
Nov  3 20:07:19 tmp kernel: [83418.117039]  [<ffffffff811dc8a1>] SyS_ioctl+0x91/0xb0
Nov  3 20:07:19 tmp kernel: [83418.117051]  [<ffffffff8176847f>] tracesys+0xe1/0xe6
Nov  3 20:07:19 tmp kernel: [83418.117055] ---[ end trace 9fb1c759dc30aa54 ]---
Nov  3 20:07:19 tmp kernel: [83418.117070] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
Nov  3 20:07:19 tmp kernel: [83418.117155] IP: [<ffffffff8159ecac>] xhci_queue_new_dequeue_state+0x6c/0xe0
Nov  3 20:07:19 tmp kernel: [83418.117225] PGD d43a5067 PUD d4370067 PMD 0
Nov  3 20:07:19 tmp kernel: [83418.117276] Oops: 0000 [#1] SMP
Nov  3 20:07:19 tmp kernel: [83418.117314] Modules linked in: joydev hid_generic usbhid hid snd_hda_codec_hdmi nfsd nfs_acl auth_rpcgss nfs fscache lockd sunrpc eeepc_wmi asus_wmi s
Nov  3 20:07:19 tmp kernel: [83418.117895] CPU: 0 PID: 1485 Comm: mediasrv Tainted: G        W    3.13.0-32-generic #57~precise1-Ubuntu
Nov  3 20:07:19 tmp kernel: [83418.117978] Hardware name: ASUS All Series/H87I-PLUS, BIOS 2002 07/22/2014
Nov  3 20:07:19 tmp kernel: [83418.118041] task: ffff8800d296dfc0 ti: ffff8800d37c8000 task.ti: ffff8800d37c8000
Nov  3 20:07:19 tmp kernel: [83418.118108] RIP: 0010:[<ffffffff8159ecac>]  [<ffffffff8159ecac>] xhci_queue_new_dequeue_state+0x6c/0xe0
Nov  3 20:07:19 tmp kernel: [83418.118196] RSP: 0018:ffff8800d37c9c38  EFLAGS: 00010046
Nov  3 20:07:19 tmp kernel: [83418.118245] RAX: 0000000000000000 RBX: ffff8800d37c9cb0 RCX: 0000000000000040
Nov  3 20:07:19 tmp kernel: [83418.118309] RDX: 0000000000000000 RSI: ffff8800d377f8e0 RDI: 0000000000000000
Nov  3 20:07:19 tmp kernel: [83418.118372] RBP: ffff8800d37c9c98 R08: ffff8800d37c9cb0 R09: ffff8800d377f8e0
Nov  3 20:07:19 tmp kernel: [83418.118435] R10: 0000000000000001 R11: 000000000000039d R12: ffff8801159c0000
Nov  3 20:07:19 tmp kernel: [83418.118499] R13: ffff8800d2ac01e8 R14: 0000000000000000 R15: 0000000000000002
Nov  3 20:07:19 tmp kernel: [83418.118564] FS:  00007f834a2fe700(0000) GS:ffff88011fa00000(0000) knlGS:0000000000000000
Nov  3 20:07:19 tmp kernel: [83418.118636] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov  3 20:07:19 tmp kernel: [83418.118688] CR2: 0000000000000010 CR3: 00000000d43c2000 CR4: 00000000001407f0
Nov  3 20:07:19 tmp kernel: [83418.118751] Stack:
Nov  3 20:07:19 tmp kernel: [83418.118772]  ffff8800d37c9ca8 ffff8800d37c9c58 ffffffff81abfdb1 ffff8800d377f8e0
Nov  3 20:07:19 tmp kernel: [83418.118850]  ffff880000000001 00000000d377f401 ffff8801159c0000 ffff8800d2ac01e8
Nov  3 20:07:19 tmp kernel: [83418.118927]  ffff8801159c0000 ffff880115437000 0000000000000002 ffff8801159c0048
Nov  3 20:07:19 tmp kernel: [83418.119006] Call Trace:
Nov  3 20:07:19 tmp kernel: [83418.119037]  [<ffffffff81594dd9>] xhci_cleanup_stalled_ring+0xf9/0x100
Nov  3 20:07:19 tmp kernel: [83418.119101]  [<ffffffff81594f16>] xhci_endpoint_reset+0x136/0x190
Nov  3 20:07:19 tmp kernel: [83418.119160]  [<ffffffff8156737e>] ? usb_alloc_urb+0x1e/0x50
Nov  3 20:07:19 tmp kernel: [83418.119213]  [<ffffffff815669d5>] usb_hcd_reset_endpoint+0x25/0x70
Nov  3 20:07:19 tmp kernel: [83418.119273]  [<ffffffff81569ac8>] usb_enable_endpoint+0xa8/0xb0
Nov  3 20:07:19 tmp kernel: [83418.119330]  [<ffffffff81569b12>] usb_enable_interface+0x42/0x60
Nov  3 20:07:19 tmp kernel: [83418.119388]  [<ffffffff8156a006>] usb_set_interface+0x1f6/0x340
Nov  3 20:07:19 tmp kernel: [83418.119445]  [<ffffffff81574339>] usbdev_do_ioctl+0x589/0xc50
Nov  3 20:07:19 tmp kernel: [83418.119502]  [<ffffffff811182cc>] ? acct_account_cputime+0x1c/0x20
Nov  3 20:07:19 tmp kernel: [83418.119563]  [<ffffffff810a25e9>] ? account_user_time+0x99/0xb0
Nov  3 20:07:19 tmp kernel: [83418.119619]  [<ffffffff81574a2e>] usbdev_ioctl+0xe/0x20
Nov  3 20:07:19 tmp kernel: [83418.119669]  [<ffffffff811dc5c5>] do_vfs_ioctl+0x75/0x2c0
Nov  3 20:07:19 tmp kernel: [83418.119721]  [<ffffffff81022735>] ? syscall_trace_enter+0x165/0x280
Nov  3 20:07:19 tmp kernel: [83418.119779]  [<ffffffff811dc8a1>] SyS_ioctl+0x91/0xb0
Nov  3 20:07:19 tmp kernel: [83418.121833]  [<ffffffff8176847f>] tracesys+0xe1/0xe6
Nov  3 20:07:19 tmp kernel: [83418.123878] Code: 03 84 d7 10 01 00 00 4d 8b 48 08 4c 89 c3 49 89 fc 44 89 55 c0 4c 89 f7 4c 89 ce 4c 8d 68 28 4c 89 4d b8 e8 27 ec ff ff 8b 53 10 <4d
Nov  3 20:07:19 tmp kernel: [83418.128441] RIP  [<ffffffff8159ecac>] xhci_queue_new_dequeue_state+0x6c/0xe0
Nov  3 20:07:19 tmp kernel: [83418.130705]  RSP <ffff8800d37c9c38>
Nov  3 20:07:19 tmp kernel: [83418.132960] CR2: 0000000000000010
Nov  3 20:07:19 tmp kernel: [83418.144000] ---[ end trace 9fb1c759dc30aa55 ]---

10
Software / Re:VDR startet nicht automatisch - no DVB-device found
« am: Oktober 03, 2014, 02:14:17 Nachmittag »
Besten Dank für die schnelle Antwort; funktioniert!

Kurze Anleitung für alle anderen (ich habe einen DVB-C-Anschluss):

sudo vim /etc/sundtek.conf
initial_dvb_mode=DVBC
device_attach=service vdr start

Hier noch eine Anleitung von Sundtek für die sundtek.conf (weitere Parameter):
http://wiki.sundtek.de/index.php/TreiberKonfiguration

11
Software / (GELÖST) VDR startet nicht automatisch - no DVB-device found
« am: Oktober 03, 2014, 01:55:13 Nachmittag »
Hallo Zusammen,

ich habe ein Problem beim Starten des VDRs. Beim Starten von Ubuntu 12.04.05 LTS wird der VDR automatisch gestartet, fährt danach aber sofort wieder herunter, da anscheinend das DVB-Device noch nicht verfügbar ist. Habt ihr eine Idee wie ich das ändern kann? Installiert sind die Sundtek-Treiber vom 02.10.2014. Das OS ist gerade neu installiert und ist mit allen Aktualisierungen installiert.

Hier ein Auszug aus der /var/log/syslog
Oct  3 13:47:30 nas vdr: [1215] VDR version 2.1.6 started
Oct  3 13:47:30 nas vdr: [1215] switched to user 'vdr'
Oct  3 13:47:30 nas vdr: [1215] codeset is 'UTF-8' - known
Oct  3 13:47:30 nas cron[1317]: (CRON) INFO (pidfile fd = 3)
Oct  3 13:47:30 nas cron[1340]: (CRON) STARTUP (fork ok)
Oct  3 13:47:30 nas cron[1340]: (CRON) INFO (Running @reboot jobs)
Oct  3 13:47:30 nas kernel: [   13.558577] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Oct  3 13:47:30 nas kernel: [   13.559189] NFSD: starting 90-second grace period (net ffffffff81cd8cc0)
Oct  3 13:47:31 nas rpc.mountd[1395]: Version 1.2.5 starting
Oct  3 13:47:31 nas afpd[1447]: AFP/TCP started, advertising 192.x.x.x:548 (2.2.1)
Oct  3 13:47:31 nas vdr: [1215] found 28 locales in /usr/share/locale
Oct  3 13:47:31 nas vdr: [1215] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.1.6
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/setup.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/sources.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/diseqc.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/scr.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/channels.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/timers.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/commands.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/reccmds.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/svdrphosts.conf
Oct  3 13:47:31 nas vdr: [1215] loading /var/lib/vdr/keymacros.conf
Oct  3 13:47:31 nas vdr: [1215] registered source parameters for 'A - ATSC'
Oct  3 13:47:31 nas vdr: [1215] registered source parameters for 'C - DVB-C'
Oct  3 13:47:31 nas vdr: [1479] video directory scanner thread started (pid=1215, tid=1479, prio=high)
Oct  3 13:47:31 nas vdr: [1215] registered source parameters for 'S - DVB-S'
Oct  3 13:47:31 nas vdr: [1215] registered source parameters for 'T - DVB-T'
Oct  3 13:47:31 nas vdr: [1215] no DVB device found
Oct  3 13:47:31 nas vdr: [1215] initializing plugin: vnsiserver (1.1.0): VDR-Network-Streaming-Interface (VNSI) Server
Oct  3 13:47:31 nas vdr: [1480] epg data reader thread started (pid=1215, tid=1480, prio=high)
Oct  3 13:47:31 nas vdr: [1480] reading EPG data from /var/cache/vdr/epg.data
Oct  3 13:47:31 nas vdr: [1478] video directory scanner thread started (pid=1215, tid=1478, prio=high)
Oct  3 13:47:31 nas vdr: [1479] video directory scanner thread ended (pid=1215, tid=1479)
Oct  3 13:47:31 nas vdr: [1478] video directory scanner thread ended (pid=1215, tid=1478)
Oct  3 13:47:31 nas vdr: [1215] ERROR: invalid primary device number: 1
Oct  3 13:47:31 nas vdr: [1215] ERROR: no primary device found - using first device!
Oct  3 13:47:31 nas vdr: [1215] ERROR: invalid primary device number: 1
Oct  3 13:47:31 nas vdr: [1215] deleting plugin: vnsiserver
Oct  3 13:47:31 nas vdr: [1480] epg data reader thread ended (pid=1215, tid=1480)
Oct  3 13:47:31 nas vdr: [1215] max. latency time 0 seconds
Oct  3 13:47:31 nas vdr: [1215] exiting, exit code 2
Oct  3 13:47:31 nas kernel: [   13.805461] init: vdr main process (1215) terminated with status 2

Gibt es eine Art beschleunigte Initialisierung oder eine Idee wie ich den VDR mit Zeitverzug starten lassen kann? Ein Sleep von 15 Sekunden im init-Script vom VDR hat nicht geholfen.

Wenn ich den VDR direkt im Anschluss an die Fehlermeldungen im syslog starte, erkennt er die Karte und startet.

Seiten: [1]