Hi Everybody,
I have ivtv working fine, such that cat /dev/video > foo.mpg produced a file
with video and audio that plays back properly with xine and alsa09. I have a
Hauppauge 350.
However, when I fire up first the mythbackend and then the mythfrontend and
try to watch TV, the mythfrontend appears to hang. I see these error
messages:
mythfrontend:
linuxpc> ( setenv QTDIR /usr/lib/qt-3.0.3 ; mythfrontend )
connecting to backend server: 127.0.0.1:6543
QDir::readDirEntries: Cannot read the directory: /dev/sound
QDir::readDirEntries: Cannot read the directory: /dev/sound
mythbackend:
linuxpc> ( setenv QTDIR /usr/lib/qt-3.0.3 ; mythbackend )
Starting up as the master server.
adding: tux as a player 1
adding: tux as a player 0
adding: tux as a player 0
adding: tux as a remote ringbuffer
Changing from None to WatchingLiveTV
VIDIOCGCAP:: Invalid argument
VIDIOCSAUDIO: Invalid argument
My hostname is 'tux'. I don't know why its looking for /dev/sound - I have no
such file on my machine, and sound playback with ALSA 0.9.2 seems to work
just fine (there is no /dev/sound in snddevices, but there is /dev/snd -
symlinking the two together doesn't solve the problem). aRtsd is not
running.
Finally, I found this info in /var/log/messages:
Apr 27 19:51:01 tux kernel: ivtv: v4l2 open on minor 0
Apr 27 19:51:01 tux kernel: ivtv: current minor 0
Apr 27 19:51:01 tux kernel: ivtv: opened card # 0, stream 0
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0xc0347604
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0xc0347604
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x40347605
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x40347605
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x803c7601
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0xc0307602
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0xc0307602
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x40307603
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x40307603
Apr 27 19:51:01 tux kernel: ivtv: v4l2 close
Apr 27 19:43:16 tux modprobe: modprobe: Can't locate module char-major-10-134
Any ideas would be most appreciated! Thanks in advance.
Andy
--
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA USA
http://www.wlug.org
I have ivtv working fine, such that cat /dev/video > foo.mpg produced a file
with video and audio that plays back properly with xine and alsa09. I have a
Hauppauge 350.
However, when I fire up first the mythbackend and then the mythfrontend and
try to watch TV, the mythfrontend appears to hang. I see these error
messages:
mythfrontend:
linuxpc> ( setenv QTDIR /usr/lib/qt-3.0.3 ; mythfrontend )
connecting to backend server: 127.0.0.1:6543
QDir::readDirEntries: Cannot read the directory: /dev/sound
QDir::readDirEntries: Cannot read the directory: /dev/sound
mythbackend:
linuxpc> ( setenv QTDIR /usr/lib/qt-3.0.3 ; mythbackend )
Starting up as the master server.
adding: tux as a player 1
adding: tux as a player 0
adding: tux as a player 0
adding: tux as a remote ringbuffer
Changing from None to WatchingLiveTV
VIDIOCGCAP:: Invalid argument
VIDIOCSAUDIO: Invalid argument
My hostname is 'tux'. I don't know why its looking for /dev/sound - I have no
such file on my machine, and sound playback with ALSA 0.9.2 seems to work
just fine (there is no /dev/sound in snddevices, but there is /dev/snd -
symlinking the two together doesn't solve the problem). aRtsd is not
running.
Finally, I found this info in /var/log/messages:
Apr 27 19:51:01 tux kernel: ivtv: v4l2 open on minor 0
Apr 27 19:51:01 tux kernel: ivtv: current minor 0
Apr 27 19:51:01 tux kernel: ivtv: opened card # 0, stream 0
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0xc0347604
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0xc0347604
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x40347605
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x40347605
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x803c7601
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0xc0307602
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0xc0307602
Apr 27 19:51:01 tux kernel: ivtv: v4l2 ioctl 0x40307603
Apr 27 19:51:01 tux kernel: ivtv: ivtv-api.c: unknown ioctl 0x40307603
Apr 27 19:51:01 tux kernel: ivtv: v4l2 close
Apr 27 19:43:16 tux modprobe: modprobe: Can't locate module char-major-10-134
Any ideas would be most appreciated! Thanks in advance.
Andy
--
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA USA
http://www.wlug.org