[mythtv-users] DVB-S -> mythsetup -> problems, backend -> kill

post post at mhr.at
Sat Sep 25 08:39:47 EDT 2004


I just finished my first MythTV 0.16 installation on a Gentoo sytem with 
kernel 2.6.8.1 and two Hauppauge WinTV Nexus-S DVB-S cards with a 
CI-slot-adapter each.

MythTV looks great to me, and generally it's working, but the DVB-S part.

When accessing mythsetup, I can select both cards in the "Capture Card 
Setup", I can access the advanced configuration, but when playing arround 
in "Card Verification Wizard", I most of the time get no real signal lock. 
When entering transponder data manually, it does not work at all, and when 
I select a stored channel (I entered two channels on different transponders 
for testing), I sometimes get

-----
Status: SIGNAL CARRIER VITERBI SYNC LOCK
Signal/Noise: 0%
Signal Strength: arround 67%
Bit Error Rate: 0
Uncorreced Blocks: 0
-----

but sometimes I also got something with good and reasonable Signal/Noise. 
When playing arround with this "Card Verification Wizard", I the mythsetup 
often kills itself, just telling "memory-access-error". This computer is 
set up correctly, and everthing else is working pretty normally, and there 
is definitely no memory problem. No idea, what's that about, in the console 
it's reporting some normal locking things:

-----
bash-2.0.5b$ mythsetup
Would you like to clear all capture card settings before starting 
configuration? (no)
Would you like to clear all program/channel settings before starting 
configuration? (no)
2004-09-22 20:24:01 DVB#0 StatusMonitor Starting
2004-09-22 20:24:03 DVB#0 Using DVB card 0, with frontend 
STV0299/TSA5059/SL1935 based.
Resetting slot 0...ok.
Resetting slot 1...ok.
2004-09-22 20:24:03 DVB#0 CAM - Initialized successfully.
2004-09-22 20:24.03 DVB#0 ERROR - Invalid symbol rate parameter
Resetting slot 0...ok.
Resetting slot 1...ok.
Speicherzugriffsfehler (= translated from German: memory-access-error)
bash-2.0.5b$
-----

When starting the backend, everthing seems normal, nothing special in the 
backend-log:

-----
dvb-s # tail -f /var/log/mythtv/mythbackend.log
Starting up as the master server.
Resetting slot 0...ok.
Resetting slot 1...ok.
Resetting slot 0...ok.
Resetting slot 1...ok.
-----

I can access all the parts, browse my disk, play a video-file in mplayer, 
access the plug-ins (like mythweather, which works and looks quite nice), 
all seems to be working fine.

But as soon as I select "Watch TV", the screen goes black, the backend just 
gets killed without anything in the backend-log (just the backend process 
disappears, the pid-file stays, and has to be deleted, before I can zap & 
start the daemon again). This is the output in the frontend console:

-----
bash-2.05b$ mythfrontend
2004-09-22 20:48:44 mythfrontend version: 0.16.20040906-1 www.mythtv.org
2004-09-22 20:48:44 Enabled verbose msgs : important general
2004-09-22 20:48:44 Registering Internal as a media playback plugin.
2004-09-22 20:48:44 Registering MythDVD DVD Media Handler as a media handler
2004-09-22 20:48:44 Registering MythDVD VCD Media Handler as a media handler
Failed to run 'cdrecord --scanbus'
2004-09-22 20:48:45 Registering MythMusic Media Handler as a media handler
SIP listening on IP Address 192.168.1.30:5060 NAT address 192.168.1.30
SIP: Cannot register; proxy, username or password not set
Unable to open mixer: '/dev/mixer1'
2004-09-22 20:48:51 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5)
2004-09-22 20:48:51 Using protocol version 13
2004-09-22 20:48:51 Using protocol version 13
2004-09-22 20:48:51 Using protocol version 13
Errm, event socket just closed.
2004-09-22 20:49:00 ReadStringList timeout (quick).
Remote encoder not responding.
QSocketDevice::writeBlock: Invalid socket
2004-09-22 20:49:00 Error writing stringlist
Remote encoder not responding.
QSocketDevice::writeBlock: Invalid socket
2004-09-22 20:49:00 Error writing stringlist
Remote encoder not responding.
.
.
.
and so on (repeating until strg-c)
-----

I really would appreciate some advice, I don't know what to do. My hardware 
and Gentoo setup seems to be all ok, I even tried some modifications in my 
kernel setup (disabling 4k stacks and disabling REGPARM), but nothing changed.

Is it the DVB-part of MythTV, that causing this problems ???

Should I try the actual CVS version ???

If I can't get it to work, I probably will have to try the VDR project, but 
I really would like to stick with MythTV, as I mainly want to watch 
video-files, not satellite-tv (this is just for casual wathing, and some 
recording, so I can life with the limited DVB support in the actual MythTV 
version, if I ever get it to work at all).

--
Sincerely,
Master One




More information about the mythtv-users mailing list