Opened 11 years ago

Closed 11 years ago

#2882 closed defect (fixed)

oscam build #7767 fails to recognize BskyB 0963 card

Reported by: breakdaice Owned by:
Priority: blocker Component: Card support
Severity: medium Keywords: skyuk bskyb 0963
Cc: Sensitive: no

Description

Revision

build #7767

Issue Description

oscam build #7767 fails to recognize BskyB 0963 card

When the issue occurs

During card init

How the issue is reproducable

Every time oscam starts.

Attachments (1)

0963_error.txt (3.7 KB ) - added by breakdaice 11 years ago.
debug_log

Download all attachments as: .zip

Change History (12)

by breakdaice, 11 years ago

Attachment: 0963_error.txt added

debug_log

comment:1 by Jan Gruuthuse, 11 years ago

Had the same issue, wanted to find out where problem started.
Reloaded [7762] build and installed, same for [7763], [7764], [7765], [7766] and [7767]. and guess what the fault is gone? CARDOK (no entitlements)

2012/10/20 15:53:06 11C9BA0 r skyuk [smartreader] ATR: 3F FD 13 25 02 50 00 0F 33 B0 0F 69 FF 4A 50 D0 00 00 53 59 02
2012/10/20 15:53:06 11C9BA0 r skyuk [smartreader] Cardfrequency advertised by ATR is 5 Mhz, set clock of readerdevice to 4.80 Mhz as specified by user in reader MHZ setting
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] Card type: SYAV
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] Rom version: 40LF
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] parental lock setting: 3F 00 0E 00
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] type: VideoGuard BSkyB (0963), caid: 0963
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] serial: ########, BoxID: ########, baseyear: 1997
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] ready for requests
2012/10/20 15:53:07 11C9BA0 r skyuk [smartreader] found card system videoguard2
2012/10/20 15:53:07 11C9BA0 r skyuk [videoguard2] card detected
2012/10/20 15:53:07 11C9BA0 r skyuk [videoguard2] type: VideoGuard BSkyB (0963)

or it was lowering the cardmhz:
mhz = 500
cardmhz = 368

Version 1, edited 11 years ago by Jan Gruuthuse (previous) (next) (diff)

comment:2 by gf, 11 years ago

Please try r7770. It contains an important bug fix that might affect you.

comment:3 by breakdaice, 11 years ago

Well, it ain't much better:


OSCam << cardserver started at Sun Oct 21 11:59:03 2012


2012/10/21 11:59:03 0 s starting thread log_list_thread
2012/10/21 11:59:03 0 s log_list_thread thread started
2012/10/21 11:59:03 0 s >> OSCam << cardserver started, version 1.20-unstable_svn, build #7774 (x86_64-redhat-linux-ssl-libusb)
2012/10/21 11:59:03 0 s version=1.20-unstable_svn, build #7774, system=x86_64-redhat-linux-ssl-libusb, nice=-1
2012/10/21 11:59:03 0 s client max. idle=120 sec, debug level=255, filter_sensitive=1
2012/10/21 11:59:03 0 s max. logsize=10 Kb, loghistorysize=4096 bytes
2012/10/21 11:59:03 0 s client timeout=5000 ms, fallback timeout=2500 ms, cache delay=0 ms
2012/10/21 11:59:03 0 s services reloaded: 0 services freed, 0 services loaded, rejected 0
2012/10/21 11:59:03 0 s userdb reloaded: 2 accounts loaded, 0 expired, 0 disabled
2012/10/21 11:59:03 0 s signal handling initialized (type=sysv)
2012/10/21 11:59:03 0 s 775 service-id's loaded in 1ms
2012/10/21 11:59:03 0 s oscam.tiers loading failed
2012/10/21 11:59:03 0 s oscam.provid loading failed, wrong format?
2012/10/21 11:59:03 0 s 0 lengths for caid guessing loaded
2012/10/21 11:59:03 0 s 0 entries read from oscam.whitelist
2012/10/21 11:59:03 0 s 0 entries read from oscam.cacheex
2012/10/21 11:59:03 0 s Starting listener 0
2012/10/21 11:59:03 0 s monitor: initialized (fd=6, port=988)
2012/10/21 11:59:03 0 s Starting listener 0
2012/10/21 11:59:03 0 s newcamd: initialized (fd=7, port=34000, crypted)
2012/10/21 11:59:03 0 s -> CAID: 0963 PROVID: 000000
2012/10/21 11:59:03 0 s Starting listener 0
2012/10/21 11:59:03 0 s csp: disabled
2012/10/21 11:59:03 0 s starting thread http
2012/10/21 11:59:03 0 s http thread started
2012/10/21 11:59:03 0 s starting thread reader check
2012/10/21 11:59:03 0 s reader check thread started
2012/10/21 11:59:03 0 s starting thread check
2012/10/21 11:59:03 0 s check thread started
2012/10/21 11:59:03 0 s skyukhd [mouse] creating thread for device /dev/ttyUSB0
2012/10/21 11:59:03 0 s loadbalancer: can't read from file /tmp/.oscam/stat
2012/10/21 11:59:03 0 s waiting for local card init
2012/10/21 11:59:03 92FDE80 h HTTP Server listening on port 8080
2012/10/21 11:59:05 92FBF90 r skyukhd [mouse] Reader initialized (device=/dev/ttyUSB0, detect=cd, mhz=600, cardmhz=368)
2012/10/21 11:59:06 92FBF90 r skyukhd [mouse] card detected
2012/10/21 11:59:09 92FBF90 r skyukhd [mouse] ATR: F8 00
2012/10/21 11:59:09 92FBF90 r skyukhd [mouse] ERROR: Could not read reader->convention
2012/10/21 11:59:09 92FBF90 r skyukhd [mouse] Error activating card.
2012/10/21 11:59:13 92FBF90 r skyukhd [mouse] ATR: F8 00
2012/10/21 11:59:13 92FBF90 r skyukhd [mouse] ERROR: Could not read reader->convention
2012/10/21 11:59:13 92FBF90 r skyukhd [mouse] Error activating card.
2012/10/21 11:59:17 92FBF90 r skyukhd [mouse] ATR: F8 00
2012/10/21 11:59:17 92FBF90 r skyukhd [mouse] ERROR: Could not read reader->convention
2012/10/21 11:59:17 92FBF90 r skyukhd [mouse] Error activating card.
2012/10/21 11:59:17 92FBF90 r skyukhd [mouse] card initializing error

comment:4 by theparasol, 11 years ago

For sure its no better coz 7770 only affects internal readers not mouse readers you are using.
And your ATR is all wrong since its starts with F8 00 ....
And only allowed chars for "F8" / first ATR char is 3B or 3F and your reader is reporting F8, so there must be something wrong with cardspeed or readerspeed.

comment:5 by breakdaice, 11 years ago

No if you have a look here: http://www.streamboard.tv/oscam/attachment/ticket/2882/0963_error.txt you'll see that it did get proper ATR with #7767

comment:6 by Deas, 11 years ago

@breakdaice

no, theparasol is right...

0963_error.txt: (device=/dev/ttyUSB0, detect=cd, mhz=500, cardmhz=500)
your last log: (device=/dev/ttyUSB0, detect=cd, mhz=600, cardmhz=368)

in reply to:  4 comment:7 by breakdaice, 11 years ago

Replying to theparasol:

For sure its no better coz 7770 only affects internal readers not mouse readers you are using.

You are absolutely right! Nothing has changed:


OSCam << cardserver log switched at Sun Oct 21 17:32:32 2012


2012/10/21 17:32:31 0 s starting thread log_list_thread
2012/10/21 17:32:31 0 s log_list_thread thread started
2012/10/21 17:32:31 0 s >> OSCam << cardserver started, version 1.20-unstable_svn, build #7774 (x86_64-redhat-linux-ssl-libusb)
2012/10/21 17:32:31 0 s version=1.20-unstable_svn, build #7774, system=x86_64-redhat-linux-ssl-libusb, nice=-1
2012/10/21 17:32:31 0 s client max. idle=120 sec, debug level=0, filter_sensitive=1
2012/10/21 17:32:31 0 s max. logsize=10 Kb, loghistorysize=4096 bytes
2012/10/21 17:32:31 0 s client timeout=5000 ms, fallback timeout=2500 ms, cache delay=0 ms
2012/10/21 17:32:32 0 s services reloaded: 0 services freed, 0 services loaded, rejected 0
2012/10/21 17:32:32 0 s userdb reloaded: 2 accounts loaded, 0 expired, 0 disabled
2012/10/21 17:32:32 0 s signal handling initialized (type=sysv)
2012/10/21 17:32:32 0 s 775 service-id's loaded in 17ms
2012/10/21 17:32:32 0 s oscam.tiers loading failed
2012/10/21 17:32:32 0 s oscam.provid loading failed, wrong format?
2012/10/21 17:32:32 0 >> OSCam << cardserver log switched, version 1.20-unstable_svn, build #7774 (x86_64-redhat-linux-ssl-libusb)
2012/10/21 17:32:32 0 version=1.20-unstable_svn, build #7774, system=x86_64-redhat-linux-ssl-libusb, nice=-1
2012/10/21 17:32:32 0 client max. idle=120 sec, debug level=0, filter_sensitive=1
2012/10/21 17:32:32 0 max. logsize=10 Kb, loghistorysize=4096 bytes
2012/10/21 17:32:32 0 client timeout=5000 ms, fallback timeout=2500 ms, cache delay=0 ms
2012/10/21 17:32:32 0 s 0 lengths for caid guessing loaded
2012/10/21 17:32:32 0 s 0 entries read from oscam.whitelist
2012/10/21 17:32:32 0 s 0 entries read from oscam.cacheex
2012/10/21 17:32:32 0 s Starting listener 0
2012/10/21 17:32:32 0 s monitor: initialized (fd=3, port=988)
2012/10/21 17:32:32 0 s Starting listener 0
2012/10/21 17:32:32 0 s newcamd: initialized (fd=7, port=34000, crypted)
2012/10/21 17:32:32 0 s -> CAID: 0963 PROVID: 000000
2012/10/21 17:32:32 0 s Starting listener 0
2012/10/21 17:32:32 0 s csp: disabled
2012/10/21 17:32:32 0 s starting thread http
2012/10/21 17:32:32 0 s http thread started
2012/10/21 17:32:32 0 s starting thread reader check
2012/10/21 17:32:32 0 s reader check thread started
2012/10/21 17:32:32 0 s starting thread check
2012/10/21 17:32:32 0 s check thread started
2012/10/21 17:32:32 0 s skyukhd [mouse] creating thread for device /dev/ttyUSB0
2012/10/21 17:32:32 0 s loadbalancer: can't read from file /tmp/.oscam/stat
2012/10/21 17:32:32 0 s waiting for local card init
2012/10/21 17:32:32 17FF9CA0 h HTTP Server listening on port 8080
2012/10/21 17:32:34 17FF7DB0 r skyukhd [mouse] Reader initialized (device=/dev/ttyUSB0, detect=cd, mhz=500, cardmhz=500)
2012/10/21 17:32:35 17FF7DB0 r skyukhd [mouse] card detected
2012/10/21 17:32:41 17FF7DB0 r skyukhd [mouse] ATR: 3F FD 13 25 02 50 00 0F 33 B0 0F 69 FF 4A 50 D0 00 00 53 59 02
2012/10/21 17:32:42 17FF7DB0 r skyukhd [mouse] Cardfrequency advertised by ATR is 5 Mhz, set clock of readerdevice to 5.00 Mhz as specified by user in reader MHZ setting
2012/10/21 17:32:46 17FF7DB0 r skyukhd [mouse] card system not supported
2012/10/21 17:32:46 17FF7DB0 r skyukhd [mouse] Normal mode failed, reverting to Deprecated Mode
2012/10/21 17:32:52 17FF7DB0 r skyukhd [mouse] ATR: 3F FD 13 25 02 50 00 0F 33 B0 0F 69 FF 4A 50 D0 00 00 53 59 02
2012/10/21 17:32:53 17FF7DB0 r skyukhd [mouse] Cardfrequency advertised by ATR is 5 Mhz, set clock of readerdevice to 5.00 Mhz as specified by user in reader MHZ setting
2012/10/21 17:32:59 17FF7DB0 r skyukhd [mouse] card system not supported
2012/10/21 17:32:59 17FF7DB0 r skyukhd [mouse] card initializing error

comment:8 by theparasol, 11 years ago

Can you pinpoint more precise which rev your mouse reader actually got broken?

in reply to:  8 comment:9 by breakdaice, 11 years ago

Replying to theparasol:

Can you pinpoint more precise which rev your mouse reader actually got broken?

Sorry, don't know. Just did a fresh install with latest trunk and discovered it's broken. :(

comment:10 by breakdaice, 11 years ago

I bought Smargo and switched to smartreader mode. Now all is fine!

comment:11 by Deas, 11 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.