<- I remember that the dual card is visible differently than two singles.
ls -a /dev/dvb/adapter0
. .. ca0 demux0 dvr0 frontend0 net0
ls -a /dev/dvb/adapter1
. .. ca0 demux0 dvr0 frontend0 net0
Show your ls output.
Posted 15 May 2021 - 09:45
<- I remember that the dual card is visible differently than two singles.
ls -a /dev/dvb/adapter0
. .. ca0 demux0 dvr0 frontend0 net0
ls -a /dev/dvb/adapter1
. .. ca0 demux0 dvr0 frontend0 net0
Show your ls output.
Posted 21 May 2021 - 18:41
I see the wrong definition of frontends in the script. If there are two dvb cards, then nim_sockets should look different.
For example:
NIM Socket 0: Type: DVB-S2 Name: Montage Technology DS3000 Has_Outputs: no Frontend_Device: 0 NIM Socket 1: Type: DVB-S2 Name: Technisat SkyStar USB HD (DVB-S/S2) Has_Outputs: no Frontend_Device: 1
But in both cases we have frontend0. Most likely, changes hase accumulated in the kernels and enigma2.
First of all, you need to make sure that your dvb cards order is always the same. At me after 5 cold starts, PIC-E was detected first, and then USB. If there are two PCI-E cards, the order may be random. What will be the order in the case of a dual card, I don't know. If it changes from start to start, then you will have to write somesing like "/etc/udev/rules.d/99-dvb-symlinks.rules" with the assignment of links frontend2 and 3.
You can check the current order either by looking at the links properties of /sys/class/dvb/dvb0.demux0 and /sys/class/dvb/dvb1.demux0 or by the commands:
udevadm info -a /dev/dvb/adapter0/frontend0
and
udevadm info -a /dev/dvb/adapter1/frontend0.
In this case, I will not be able to automate the recording of the nim_sockets file. But I made some changes in prestart.sh. Now need for the second card to have a link ~frontend1 in the /dvb folder.
The channels will probably need to rescan. So far I have not noticed any glitches in switching from card to card. Regarding ca0 on the second card, you need to check it yourself.
Posted 21 May 2021 - 19:18
<- I have dvbsoftwareca working fine on frontend0 and frontend1. True, I watch encoded channels only on one satellite. There's just nothing more to watch, everything is the same everywhere.
Posted 21 May 2021 - 22:52
Can the remote control be used?
Lirc + any remote.
When updating the program. Did I reinstall the program again?
Yes, surely.
How do I make the video fill the screen?
F11 temporaly or in OSD menu constantly.
Posted 22 May 2021 - 19:36
<- I have dvbsoftwareca working fine on frontend0 and frontend1. True, I watch encoded channels only on one satellite. There's just nothing more to watch, everything is the same everywhere.
Yes it works in a specific order ... that's the problem.
If you switch the coaxial cables it will work on adapter0 only.
I tried the new prestart script, if i restart dvbsoftwareca it creates 3 CA devices
dvbsoftwareca: registering adapters dvbsoftwareca: register adapter0/ca0 @ minor: 0000 dvbsoftwareca: registered CA0 device for adapter0 dvbsoftwareca: register adapter1/ca0 @ minor: 0004 dvbsoftwareca: registered CA0 device for adapter1 dvbsoftwareca: register adapter1/ca1 @ minor: 0005 dvbsoftwareca: registered CA1 device for adapter1 dvbsoftwareca: registered 3 CA devices
But i can't see any difference, oscam can decrypt channels on adapter0 only.
Edited by roxette, 22 May 2021 - 19:42.
Posted 24 May 2021 - 14:02
I see one oddity. We may don't make symlink to rontendN at all, but for the second adapter need to write in nim_sockets: "Frontend_Device: 1".
I don’t know why this happens, but dvb cards are switched faster. This is what I did in the last commit.
I have no problem with SNR. This was written by a user whose SNR is always 0 and I advised him to disable the EncryptedChannel plugin.
Posted 25 May 2021 - 16:38
Edited by roxette, 25 May 2021 - 16:41.
Posted 12 June 2021 - 21:11
ptergrand, is DVB card single or multi? Is this message persistent? I don't remember the reason, but I saw this. This may be due to the absence of a second card in the /dev/dvb folder, for example. If there is a multicard, then the folder /dev/dvb should contain all the tuners. But my patch doesn't is reason this in any way.
Posted 13 June 2021 - 12:33
This problem has always existed or occurs in one of the newer versions of e2? Do you use both tuners or only the first one?
Which command should I use to update the program again?
I didn't understand the question.
Posted 14 June 2021 - 09:34
Learn to attach logs, not screenshots. I have to pull information out of you as on interrogation to understand what's happening.
e2 is not updated by itself. What is the output of the command
git log
in the source tree or what is written in the Menu->About version e2?
What happens if you rewrite the settings file from the original directory and recreate your own?
What happens if you manually create symlinks ~frontend1 on frontend0 inside /dev/dvb/adapter0 folder and start e2 again without restarting the PC?
lsdvb
?
Edited by 1455, 14 June 2021 - 09:41.
Posted 14 June 2021 - 17:08
What are you guys talking about?
The "stopped" message is related to clearmem plugin
def __chckState(self): def subStart(): if cfg.enable.value: self.state = cfg.enable.value self.ClearMemTimer.start(int(cfg.timeout.value)*60000) self['message_label'].setText(_("Started")) else: self['message_label'].setText(_("Stopped")) if cfg.scrinfo.value and ClearMemAuto.dialog is not None: ClearMemAuto.dialog.show() self.ClearMemWatchDog.stop() if self.instance and cfg.enable.value != self.state: if self.ClearMemTimer.isActive(): self.ClearMemTimer.stop() subStart()
self.ClearMemWatchDog.start(int(cfg.timescrinfo.value) * 1000)
It's very weird that both of you didn't even care to read my reply.
I even wrote some turkish words from google but it seems that it was hidden to @ptergrand
By the way, @ptergrand if you come on the forum to talk with a specific person just let us know so i don't bother replying to your posts anymore.
Edited by roxette, 14 June 2021 - 17:10.
0 members, 1 guests, 0 anonymous users