Open SaulGoodman1337 opened 2 years ago
hmmm. minisatip Feb 6 07:54:12 gbue4k daemon.notice minisatip[11314]: get_signal took 48 ms for adapter 0 handle 6 (status: 31, ber: 0, strength:23, snr: 217, force scan 0)
strength is 23 instead of 23[0..9]... the values already come out of the driver wrong. i still can't get rid of the feeling that something is going wrong with the parsing. in the driver itself! the values do not look like fantasy values, but they are chopped off. Do you have an idea or maybe a contact to which I can turn?
What does this show:
modinfo /usr/share/platform/dvb.ko
What happen if in place of enigma2 used neutrino?
What does this show:
modinfo /usr/share/platform/dvb.ko
minisatip: unrecognized option '--cleanpsi' root@gbue4k:~# modinfo /usr/share/platform/dvb.ko filename: /usr/share/platform/dvb.ko license: GPL description: BCM7xxx dvb adapter driver version: 20200723104807-u171 depends: vermagic: 4.1.20-1.9 SMP mod_unload ARMv7 p2v8
Ok, I have to same driver data on my Quad 4K. Strange I do not see this problem here
Have to say that (to me) the signal strength on Gigablue is somewhat buggy. I do not see the jumping but now I have connected to the JESS LNB it seems somehow different a much(much) lower value.
Which values ? For me ist seems that the 3 Digit values are chopped. Instead of 240 i have 22,23 or 24. Somethimes 38... Somethimes 4.. I think this is a Driver issue and No Problem that you can fix. But... In minisatip which i Test at the moment(sorry for that) is the Option to force the Signal strenght to a value.
I think this is a good Feature Request. Easy to implement i think.
Yes does values I have seen as well, as well just half the value.
I am not sure what you need to understand my problem. But my signal strength is sometimes not read correctly. instead of 240 a 2 is transmitted. then again the 240. this leads in the TVheadend to jumping signal strengths from 1% to 100%. I have a Gigablue UE4K in conjunction with a Gigablue SCR LNB