ist ein kernel update nicht gefährlich?
# kdetv
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
proxy_msg: connect: error 2, Datei oder Verzeichnis nicht gefunden
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Verbindung über Socket
fehlgeschlagen, Server läuft nicht.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
$Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
Opened /dev/vbi
Try to open V4L2 2.6 VBI device, libzvbi interface rev.
$Id: io-v4l2k.c,v 1.28 2005/05/25 02:26:41 mschimek Exp $
Opened /dev/vbi
/dev/vbi (V-Stream Studio TV Terminator) is a v4l2 vbi device,
driver saa7134, version 0x0000020e
Using streaming interface
Current scanning system is 625
Querying current vbi parameters... success
VBI capture parameters supported: format 59455247 [GREY], 27000000 Hz, 2048 bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
VBI capture parameters granted: format 59455247 [GREY], 27000000 Hz, 2048 bpl, o ffs 256, F1 7...22, F2 319...334, flags 00000000
Nyquist check passed
Request decoding of services 0x60000c7f, strict level -1
Will capture services 0x0000041f, added 0x41f commit:1
Requesting 16 streaming i/o buffers
Mapping 16 streaming i/o buffers
Successful opened /dev/vbi (V-Stream Studio TV Terminator)
kdetv: WARNING: MainWindow::setupInfraRed(): Lirc not available
kdetv: WARNING: VolumeController :: doSetVolume: AudioManager failed, trying SourceManager
kdetv: WARNING: VolumeController :: doSetVolume: AudioManager failed, trying SourceManager
QDateTime::fromString:Parameter out of range
« Suse: Keine grafische Oberfläche nach Nv-Treiber installation | Linux geht nicht ins Internet » | ||