355 replies to this topic

[Teesi]

Hi, 

 

I too have display problem after 7.2 -> 7.3 flash (and restart) : Display shows only static boot-rings, even in standby.

 

My receiver is an old VU+ Ultimo.

 

It seems that /dev/dbox/oled0 is missing (There is /dev/oled0 instead). VU plus specific plugin LEDbrightnesssetup needs it.

 

Doing 'mkdir /dev/dbox', and 'ln /dev/oled0 /dev/dbox', and restarting enigma brang the display back, but this is not proper fix.

 

I hope this helps.

Thank You for developing excellent software !

[WanWizard]

Hallo, gibt es ein Images für die AX61 4K? Danke für Info.

 

Nein.

[nor50]

 

Hallo, gibt es ein Images für die AX61 4K? Danke für Info.

 

Nein.

 

Is this English...? Frustrating when even mods don't follow the rules.

Edited by nor50, 6 September 2020 - 16:56.

[idomonkos]

I had the same problem after updating to 7.3 from 7.2 (UNO 4K SE, small front LCD blank, power led always on - in standby, too)

+ there is some problem with vtuner. I had 4 sat>ip tuners 2+2 dvb-t and dvb-c on PLI 7.2. After update to 7.3 they all went missing and the sat>ip client says no vtuner found.

 

I'm still investigating the problems, but I had to reflash to fix the problems.

After reflash I can open the sat>ip config, but if I setup all 4 tuners and reboot, I get no vtuner found again. I think I had some success with only 2 dvb-c tuners, but I must try it again. Where are the log files for this?

 

 

Hi, 

 

I too have display problem after 7.2 -> 7.3 flash (and restart) : Display shows only static boot-rings, even in standby.

 

My receiver is an old VU+ Ultimo.

 

It seems that /dev/dbox/oled0 is missing (There is /dev/oled0 instead). VU plus specific plugin LEDbrightnesssetup needs it.

 

Doing 'mkdir /dev/dbox', and 'ln /dev/oled0 /dev/dbox', and restarting enigma brang the display back, but this is not proper fix.

 

I hope this helps.

Thank You for developing excellent software !

[base2729]

Ustym 4K ...where is extensions kodi ...where i can find .

[WanWizard]

Please don't double post.

[WanWizard]

For those that haven't updated today, please don't, but wait until the current build is ready. The build of last night has a bug in the default skin.

 

For those that have already updated: the only solution is flash again (with the new image when ready in a few hours), or use this on the commandline:

opkg remove enigma2-plugin-skins-pli-hd --nodeps
opkg install enigma2-plugin-skins-pli-hd

this is because the version has been downgraded, and opkg kan't automatically downgrade packages.

 

Edited by WanWizard, 14 September 2020 - 14:42.
correct CLI statements

[klosz007]

I had weird issue yesterday (Vu+ Duo 4K with OpenPLi 7.3).

 

Tuner was rebooted on Monday 14th because of upgrade to latest version (I noticed OSCAM was upgraded to r11606 If I recall correctly) and it worked fine throughout Tuesday 15th (yesterday). It made a few recordings during the day but when I wanted to watch them in the evening, I noticed that tuner was shut down (it started to boot when I pressed power on remote, rather just wake up).

It wasn't completing boot though - Vu+ logo was displayed first (on HDMI and LCD), then orange OpenPLi logo on HDMI, finally I had no signal on HDMI and LCD screen was getting black, rather than usual Enigma2 GUI... Remote didn't work. But it was possible to SSH into the box and OpenWebIF worked fine.

 

I soon realized that /etc/enigma2/settings file is the issue. When I renamed it and rebooted, box booted up fine, went through initial setup etc. I started making configuration adjustments, rebooting the box from time to time to checks if it is OK and it was fine. Until I made some final adjustments and rebooted and it again, then it fell into the same problem (sadly I do not remember what I changed in the last batch...)

 

I see nothing weird in the settings file. I haven't made any changes to settings in the past few days either. It hangs even if I use settings file from backups. So no idea what is wrong... Settings file was good and out of the blue became bad ? If that was caused by updates then it should start earlier, not yesterday.

Since I had some scheduled recordings for today, I again deleted settings file, went through initial setup and then made some really minimal adjustments and it works.

 

Any idea how to troubleshoot it ? I tried stopping Enigma2 form CLI (init 5) and starting via enigma2.sh but it returns no errors when it hangs... Just something about clearing Txt cache.

[WanWizard]

You can start enigma in debug mode using

init 4
ENIGMA_DEBUG_LVL=4 enigma2

maybe that will tell you more?

 

I'll do an update of my box, see if I can reproduce it.

[klosz007]

Thanks. I'll try to reproduce it as well using method provided.

I found somewhere else how to do it but it was different (init4 then export ENIGMA_DEBUG_LVL=4, then enigma2.sh) and it basically gave me same output as just running enigma2.sh.

[WanWizard]

You shouldn't use enigma2.sh, use the binary. The script does all sort of things with this variable.

[klosz007]

I have currently a number of scheduled recordings (TdF, LeMans 24) so may be hard to find a time slot for testing but I'll try that. That's why I had to find an easy fix quickly.

It should be easy to reproduce - I'm taking my 'old' usual settings file and I'm getting black screen. I'm taking settings file created by initial setup + some minor setup/tweaking (such as recording directories) and it works.

But there's a lot of differences between these two files, so checking/testing each entry one by one would take ages, especially having known that my PC is in another room than my STB with TV set.

I was trying to remove some most suspected entries from usual settings file but no luck. So it was probably caused by some friendly-looking entry.

Nevertheless I'll try debug mode used correctly and see what it tells me.

[klosz007]

With the 'good' settings file (created form scratch by deleting/running wizard/making some basic adjustments), the debug messages scroll for quite a long time and finally stop at that:

 

[eEPGCache] nownext finished(1600285623)

[eEPGCache] schedule other finished(1600285713)

[eEPGCache] schedule finished(1600285715)

[eEPGCache] stop caching events(1600285715)

[eEPGCache] next update in 60 mi

 

With 'bad' one (just more customizations via enigma2 GUI) it quite very quickly hangs at:

 

[Avahi] timeout elapsed

[Avahi] avahi_timeout_update

 

 

[betacentauri]

Please change config step by step and test after each change whether e2 starts. Which is the last config change after that e2 don’t start any more?

[klosz007]

I will look into deeply it after the weekend, currently my box is busy with making scheduled recordings. Problem is that I do not remeber what was changed last, I made a couple of changes before it started to hang again.

[arash47]

dr8000 network problem

Edited by arash47, 20 September 2020 - 05:13.

[arash47]

stbmodel=dm8000

kernelcmdline=ubi.mtd=root root=ubi0:rootfs rootfstype=ubifs rw console=null bmem=102M@154M

nimsockets=NIM Socket 0:

imageissue=openpli 7.3-release %h

 

 

Traceback (most recent call last):

  File "/usr/lib/enigma2/python/mytest.py", line 211, in processDelay

    callback(*retval)

  File "/usr/lib/enigma2/python/Screens/NetworkSetup.py", line 531, in keySaveConfirm

  File "/usr/lib/enigma2/python/Screens/NetworkSetup.py", line 575, in applyConfig

  File "/usr/lib/enigma2/python/Components/Network.py", line 114, in writeNetworkConfig

  File "/usr/lib/enigma2/python/Components/Network.py", line 117, in writeNameserverConfig

IOError: [Errno 90] Too many levels of symbolic links: '/etc/resolv.conf'

[WanWizard]

Login with telnet or connect to the box with CIFS, and delete /etc/resolv.conf.

 

It will be automatically created again by DHCP, or if you use a fixed IP and DNS, configure your network interface again to recreate it.

[arash47]

tanks

[caligula73]

explain why after flashing a fresh image I have to install such a large number of updates?

http://sendfile.su/1577483

http://sendfile.su/1576469