Opened 12 years ago

Closed 11 years ago

#7862 closed defect (invalid)

HVR-4000 sometimes Crash by Switch Channel from DVB-S to DVB-T

Reported by: wuliwux1@… Owned by: Janne Grunau
Priority: minor Milestone: 0.24
Component: MythTV - DVB Version: 0.22-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


hi, first sorry for my bad english... ;-)

i have the hauppauge HVR-4000 with mythbuntu 9.10 and mythtv backend version: Please include all output in bug reports. MythTV Version : 23069 MythTV Branch : branches/release-0-22-fixes Network Protocol : 50 Library API : 0.22.20091023-1 QT Version : 4.5.2 Options compiled in:

linux profile using_oss using_alsa using_pulse using_jack using_backend using_dvb using_firewire using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

the card works, but when i switch from dvb-t to dvb-s sometimes the picture hang and i can do nothing to wake up the mythtvfrontend.


Attachments (1)

mythbackend.log (4.7 KB) - added by wuliwux1@… 12 years ago.
mythbackend log

Download all attachments as: .zip

Change History (5)

Changed 12 years ago by wuliwux1@…

Attachment: mythbackend.log added

mythbackend log

comment:1 Changed 11 years ago by Stuart Auchterlonie

Milestone: 0.220.24

Bumping open 0.22 milestone tickets to 0.24

comment:2 Changed 11 years ago by sphery

dup of #7676 ?

comment:3 Changed 11 years ago by robertm

Status: newinfoneeded_new

It appears the default firmware and driver for this device were a total disaster until very recently. I'm asking that anyone considering opening a ticket with a tuning or scanning issue with the HVR-4000 compile current v4l-dvb modules and get a current firmware installed (not the packaged one).

Can you please complete the above and then retest?

After some discussion with one of the linuxtv devs, ther driver itself appears to have a timing issue that is probably causing this, but getting current drivers and testing will let us know whether the issue needs more attention on their side.

comment:4 Changed 11 years ago by robertm

Resolution: invalid
Status: infoneeded_newclosed

No response.

Note: See TracTickets for help on using tickets.