Opened 9 years ago

Closed 8 years ago

#9508 closed Bug Report - General (Upstream Bug)

Problem with CI Card

Reported by: gludie@… Owned by: danielk
Priority: minor Milestone: unknown
Component: MythTV - DVB Version: 0.23-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Hi,

I hope this issue is worth a ticket, but I now searched a lot for a similar problem, but did not find anything.

Symptom: If I insert a cam module (alphacrpyt light) into the CI module, mythtv hangs with Status "L_ _ ". Independently if FTA or scrambled. If I disconnect the cam, the status immediatly changed to LMS and current channel can be watched.

If I reinsert the cam module - same story as before ... hangs with status L

What did I check: ==dmesg==

2557.060154] adapter has MAC addr = 00:d0:5c:24:1d:a5

[ 2557.066324] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1e.0/0000:0a:0c.0/input/input7 [ 2557.072464] budget_ci: CI interface initialised [ 2557.196281] dvb_ca adapter 1: DVB CAM detected and initialised successfully [ 2557.276213] DVB: registering adapter 1 frontend 0 (ST STV0299 DVB-S)... [ 2784.312153] dvb_ca adapter 1: DVB CAM detected and initialised successfully

The card itself worked this afternoon, and I did not exactly know, if it is in relation with a change in udev. I tried to create links with a own udev rules, because I have two adapters, but at the moment I disabled it and work with the automatic assigned adapter ids.

Distribution: ubuntu 10.04 lts mythtv: 0-23-fixes cards: Hauppage Nova S PCI CI , Technisat Skystar 2 rev2.8 0a:0a.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02) 0a:0b.0 Ethernet controller: Broadcom Corporation NetXtreme? BCM5705_2 Gigabit Ethernet (rev 03) 0a:0c.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

0a:0a.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02)

Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card Flags: bus master, slow devsel, latency 32, IRQ 22 Memory at d0000000 (32-bit, non-prefetchable) [size=64K] I/O ports at 4000 [size=32] Kernel driver in use: b2c2_flexcop_pci Kernel modules: b2c2-flexcop-pci

0a:0c.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

Subsystem: Technotrend Systemtechnik GmbH Device 100f Flags: bus master, medium devsel, latency 123, IRQ 20 Memory at d0020000 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_ci dvb Kernel modules: budget-ci

Please let me know, if further information needed

Change History (5)

comment:1 Changed 9 years ago by Raymond Wagner

Version: Unspecified0.23-fixes

comment:2 Changed 8 years ago by tapsa19@…

I have exactly the same problem. When I installed the net card it worked ok with the cam. But I needed to fiddle with the udev to have card devices to have fixed names and this issue came up. When I removed the cam the L moved to LMS. My CAM is SmarDTV Conax 4.00e and I have Technotrend C1501 DVB-C PCI with Technotrend Budget PCI CI.

comment:3 Changed 8 years ago by beirdo

Component: MythTV - GeneralMythTV - DVB
Owner: set to danielk

comment:4 Changed 8 years ago by stuartm

Status: newinfoneeded_new
Type: Bug ReportBug Report - General

I don't think anything has changed in this area of the code, but can you upgrade to 0.24.2 or the beta of 0.25 (released tomorrow) and see if it makes any difference.

comment:5 Changed 8 years ago by Kenni Lund [kenni a kelu dot dk]

Resolution: Upstream Bug
Status: infoneeded_newclosed

I'm closing this as an upstream bug. I've recently purchased a TechnoTrend? CT-3650 CI tuner and I ran into the same issue as described in this report. The issue existed both on 0.24-fixes and on git master. Once I moved to a recent kernel together with the latest V4L-DVB git master branch, the issue went away. I'm currently running with MythBuntu? 11.10 with its stock kernel + a recent V4L-DVB git master checkout + 0.24-fixes. I haven't had the issue with this setup.

Another thing, which gave me a great headache while I was debugging the issue, was that the tuner didn't always work as expected if I had removed and reinserted the CAM after the system had booted. If I did this, I had to reload the drivers and restart the backend (or simply just reboot the system and leave the CAM inserted at all times).

Note: See TracTickets for help on using tickets.