2072 replies to this topic

[roxette]

I don't use lirc.

Doesn't matter means?

You still see black bar after you set aspect ratio to automatic?

Edited by roxette, 29 January 2022 - 00:40.

[NadjmGharib]

Yes I can still see it. Nothing changes when I change the settings

[roxette]

Restart e2pc to apply the changes.

[roxette]

 

 

 

 

I reversed e2pc patch in order to use e2_procfs module.

It works, new settings can be added too.

It's the 1st time to see that T2MI raw mode setting.

 

I think it's time to clean e2pc patch coz it sounds bit unprofessional to use /usr/local/e2/etc/stb instead of /proc/stb.

Attached Files

•  stb.png   29.76KB   2 downloads
•  lnb.png   242.86KB   2 downloads

Edited by roxette, 31 January 2022 - 19:42.

[1455]

I also tried this module from 'rpi'. What do I think about this... In fact, the stb folder can be deleted in the ep2c version. Nothing will be mentioned in the logs. Or its files can be zero-sized. It's just that my predecessors thought that the routes should match and took this folder from dreambox. But this is a common stub. The file /proc/bus/nim_sockets will be empty and there will be no write access. Sorces from 'rpi' are for older kernels and are very capricious. I made a patch for 5.13 and brought back references to /proc/stb/. Module worked on e2pc with Intel graphics. But another machine with a 5.4 kernel and nvidia graphics had a major crash. After removing the e2_procfs module, enigma started to into a black screen and no more happend. I spent 2 days, but it was not possible to find the cause and I had to restore the system from the image. So, I don't want these 10 users of mine to get pissed off with claims. Maybe it need more time more, but there's no point in it. I won't include this it in git.

 

[roxette]

I didn't know that you give up easily 

nim_sockets is not in /proc/stb

So you can leave it as is in /etc/tuxbox

The module worked for me using kernel 5.4 and 5.15 without a problem.

If there is a crash it means there a conflict file

Check if you are still using /usr/local/e2/etc/stb somewhere.

My sugesstion is you make an optional e2_procfs script which will replace 4_build_openpliPC.sh if someone interested to use it.

It has been 10 years and e2pc scripts are the same.

It would be cool if you implement something new.

[1455]

I have already explained why this idea is useless and even harmful. Do you really think that I could not organize nim_sockets? I can send a link to my archive. The question is closed. Make your fork on git.

[roxette]

I have already explained why this idea is useless and even harmful. 

Then remove /usr/local/e2/etc/stb from e2pc scripts.

 

 

. The file /proc/bus/nim_sockets will be empty and there will be no write access. 

If you know how to handle it why you wrote that?

 

The question is closed. Make your fork on git.

 

By the way, i didn't pm you to close the conversation, i'm posting in public.

If you can't do it someone else can.

I feel sorry for telling you that idea in the 1st place.

Edited by roxette, 2 February 2022 - 16:30.

[1455]

You're trying to put a driver on a device that doesn't exist, but ubuntu sees things differently.

But you gave a good idea to exclude the reference to values that are not in the ubuntu. For example, 'frontpocessor' and the like. However, this will not improve e2pc in any way. Let others users say about this.

 

[roxette]

You want to improve e2pc?

Milaebrothers was working on it here

https://github.com/m...pc-softhddevice

I told you if you can continue his work.

You said it's byond your ability right?

When i told you about procfs driver i didn't mention anything about e2pc improvement however the question to other forum users.

Whichever is better?

Replacing /proc/stb directory with /usr/local/e2/ .. blablabla

more than 300 times.

Or 

Compile/load procfs driver?

[NadjmGharib]

Has anything changed?

I have reinstalled the program, But when I run the program The logo image appears, then the program freezes

[NadjmGharib]

The program freezes on the logo image

 

[1455]

What is written in /tmp/BootLogEnigma2 after running TESTS/DEBUG_LVL_4.sh ? Rename /usr/local/e2 folder to /usr/local/e2_old and build enigma2 and plugins again.

[NadjmGharib]

Thanks, the problem is solved

 

[roxette]

Hi,

Good to know that you started OpenPLipc_procfs repo.

Although sometimes you seems bit unfriendly but i think you're a nice guy 

I noticed you decided to use /proc/bus/nim_sockets instead of /etc/tuxbox/nim_sockets

In case someone has a problem with that you can change it to /etc/tuxbox/nim_sockets by editing /lib/python/Components/NimManager.py

You have added new folders in /proc/stb like encoder folder but it's empty.

[roxette]

Hi,

There is a problem in procfs last commit

In Expert Settings click on Display setup, e2pc will crash.

 File "/usr/local/e2/lib/enigma2/python/Components/config.py", line 1768, in __getattr__
    raise AttributeError(name)
AttributeError: showTv
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0x7f0f7d1560f0>>,('OkCancelActions', 'ok')) failed)

[roxette]

 

 

It should look like that.

Attached Files

•  lcd.png   229.27KB   2 downloads

Edited by roxette, 7 February 2022 - 20:39.

[1455]

Removed some unused values leading nowhere. Everything is much more complicated than I thought before. Initially source was not suitable for OpenPli at all. I had to pull out all available values from enigma. It took a lot of time.

[roxette]

You're right, source was made for enigma2 on Raspberry Pi with minimal values.

It's a nice idea though.

Now, you should name change

MODULE_DESCRIPTION("RaspberryPi enigma2 procfs driver");

to

MODULE_DESCRIPTION("e2pc procfs driver");

You are doing a good job .. thx 

[roxette]

Oops, i mean now you should change*