Smargo direkt verbinden geht nicht

[mxer]

So, ich habe mal wieder was ausgegraben
Fritte 7170 mit oscam-svn5825-mips-freetz-webif-libusb
Smargo auf 1.5 Auto, Normal, 0, 0
Karte V13

Freetz oscam.config

Spoiler

[global]
logfile = /var/media/ftp/uStor01/oscam.log
clienttimeout = 7000
fallbacktimeout = 4000
bindwait = 5
unlockparental = 1
nice = -1
maxlogsize = 0
waitforcards_extra_delay = 100
preferlocalcards = 1
saveinithistory = 1
lb_savepath =
lb_stat_cleanup = 24

[monitor]
hideclient_to = 15
appendchaninfo = 0

[cs357x]
port = 12005

[webif]
httpport = 16666
httphelplang = de
httpcss = /var/media/ftp/uStor01//cs/oscam//proflinux_ddcstyle.css
httprefresh = 10
httpallowed = 192.168.178.1-192.168.178.29

Freetz Oscam.server

Spoiler

[reader]
label = sky
protocol = smartreader
device = Serial:Reader 4Cxxxxx
services = sky,sky-hd,!sky-ppv,!sky-bb,sky-hdplus
showcls = 0
caid = 09C4
boxid = 12345678
atr = hab ich
detect = cd
group = 1
emmcache = 1,3,2

Nun das Problem:

Spoiler

2000/01/01 1:03:30 5421B8 s reader check thread started
2000/01/01 1:03:30 5421B8 s check thread started
2000/01/01 1:03:30 5421B8 s creating thread for device Serial:Reader 4Cxxxxx
2000/01/01 1:03:30 5421B8 s loadbalancer: can't read from file /tmp/.oscam/stat
2000/01/01 1:03:30 5421B8 s waiting for local card init
2000/01/01 1:03:30 55C760 h HTTP Server listening on port 16666
2000/01/01 1:03:30 55B048 r Using 0x82 as endpoint for smartreader hardware detection
2000/01/01 1:03:30 55B048 r Found reader with serial Reader 4Cxxxxx at 001:004
2000/01/01 1:03:30 55B048 r Found smartreader device Serial:Reader 4Cxxxxx
2000/01/01 1:03:30 55B048 r reader sky initialized (device=Serial:Reader 4Cxxxxx, detect=cd, mhz=357, cardmhz=357)
2000/01/01 1:03:31 0 sky card detected
2000/01/01 1:03:31 55B048 r using ATR from reader config
2000/01/01 1:03:31 55B048 r ATR: xxxxx
2000/01/01 1:03:41 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:03:51 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:04:01 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:04:01 55B048 r Maximum frequency for this card is formally 5 Mhz, clocking it to 4.80 Mhz
2000/01/01 1:04:12 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:04:22 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:04:22 55B048 r card system not supported
2000/01/01 1:04:22 55B048 r Normal mode failed, reverting to Deprecated Mode
2000/01/01 1:04:22 55B048 r using ATR from reader config
2000/01/01 1:04:22 55B048 r ATR: xxxxx
2000/01/01 1:05:33 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:05:43 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:05:53 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:06:03 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:06:13 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:06:13 55B048 r Maximum frequency for this card is formally 5 Mhz, clocking it to 4.80 Mhz
2000/01/01 1:06:24 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:06:34 55B048 r usb bulk write failed : ret = -7
2000/01/01 1:06:34 55B048 r card system not supported
2000/01/01 1:06:34 55B048 r card initializing error
2000/01/01 1:06:34 5421B8 s init for all local cards done
2000/01/01 1:06:34 5421B8 s anti cascading disabled

Egal was ich als MHz oder CardMHz einstelle, oder sonst wo, geht nicht.
Die Ftdi-Treiber sind deaktiviert.
Was mir auffällt: egal ob ich device_out_endpoint = 0x82 oder nix einstelle, es steht nach dem Verlassen und
wieder aufrufen auf default.

Warum das Ganze?
Vorteile :

feste verlinkung

Schnellerer Initialisierungsvorgang

Bessere ecm Zeiten

Es soll bis zu 0.1s bei den ECM bringen. Hört sich nach nix an, könnte aber entscheidend sein.
Vor Allem, wenn mehrere Clients an einer z.B. V13 hängen.

Kann geschlossen werden, habe hier ein HowTo dafür: