With today's update, kernel and enigma2 console messages show up in display, making enigma2 crash on channel change
27 replies to this topic
Re: Today's update makes box non-working #2
-
- Senior Member
- 120 posts
+7
Neutral
Posted 6 November 2011 - 08:19
I did the online update too and indeed there is the console message during boot/restart but it doesn't crash for me on channel change.
VU+ Ultimo 4K; Clarke-Tech et9000
Re: Today's update makes box non-working #3
-
- Member
- 21 posts
0
Neutral
Posted 6 November 2011 - 08:32
... the same problem ...
Re: Today's update makes box non-working #4
-
- Senior Member
- 389 posts
+68
Good
Posted 6 November 2011 - 08:38
i can confirm the console messages and the reboot on channel change - find attached two crash logs
Attached Files
-
enigma2_crash_1320564545.log 16.9KB
9 downloads
-
enigma2_crash_1320564731.log 16.9KB
5 downloads
Most problems can be solved simply by a closer look.
Re: Today's update makes box non-working #5
-
- Senior Member
- 1,449 posts
+69
Good
Posted 6 November 2011 - 08:51
enigma2 crashes when it tries to display something in the framebuffer (on channel change the infobar is displayed) and at the same time the kernel or enigma2 process writes something to console, which is also shown in the framebuffer.
Is there a quick way to disable framebuffer console output? In /proc/cmdline i see console=null but init process and enigma2 messages still go to framebuffer.
What a stupid idea of the driver developers to enable fb console without some testing first!
Is there a quick way to disable framebuffer console output? In /proc/cmdline i see console=null but init process and enigma2 messages still go to framebuffer.
What a stupid idea of the driver developers to enable fb console without some testing first!
Re: Today's update makes box non-working #6
-
- Senior Member
- 1,449 posts
+69
Good
Posted 6 November 2011 - 09:10
After further investigation it seems it only crashes when infobar is displayed. So it might be not fb related after all. Itried with default Magic skin, the same result.
I will try a fresh reflash instead of upgrade, maybe something went wrong on update.
Even if FB console is not to blame, showing init process messages in screen is not elegant, it needs to be disabled.
I will try a fresh reflash instead of upgrade, maybe something went wrong on update.
Even if FB console is not to blame, showing init process messages in screen is not elegant, it needs to be disabled.
Re: Today's update makes box non-working #7
-
- Senior Member
- 389 posts
+68
Good
Posted 6 November 2011 - 09:15
in the german CT board one user told that he did a complete new flash (without online update) - there are no prblems changing channels
Most problems can be solved simply by a closer look.
Re: Today's update makes box non-working #8
-
- Senior Member
- 1,449 posts
+69
Good
Posted 6 November 2011 - 09:21
I temporary disabled "show infobar on zap" and i can work the box without crashing. If I enable it again, it crashes
Re: Today's update makes box non-working #9
-
- PLi® Core member
- 14,045 posts
+298
Excellent
Posted 6 November 2011 - 09:30
Found the bug, I'll start new builds...
Real musicians never die - they just decompose
Re: Today's update makes box non-working #10
-
- Senior Member
- 85 posts
+2
Neutral
Posted 6 November 2011 - 09:35
with de default screen the system works good.
D.
D.
Re: Today's update makes box non-working #11
-
- PLi® Core member
- 56,259 posts
+691
Excellent
Posted 6 November 2011 - 09:35
No picons I suggest....
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Today's update makes box non-working #12
-
- Senior Member
- 85 posts
+2
Neutral
Posted 6 November 2011 - 09:55
No picons I suggest....
great! ty!
Re: Today's update makes box non-working #13
-
- PLi® Core member
- 14,045 posts
+298
Excellent
Posted 6 November 2011 - 09:56
Online update now should already fix the etxx00 boxes, the builds for these boxes are ready.
Real musicians never die - they just decompose
Re: Today's update makes box non-working #14
-
- Senior Member
- 389 posts
+68
Good
Posted 6 November 2011 - 09:56
i can confirm that with the fix the channel change is ok even with infobar.Found the bug, I'll start new builds...
Only the ugly console messages are still there...
Most problems can be solved simply by a closer look.
Re: Today's update makes box non-working #15
-
- Senior Member
- 104 posts
+7
Neutral
Posted 6 November 2011 - 10:12
I actually think the console msg are great so i guess it's down to personal taste.
Have a nice day
so i guess it's down to personal taste. Have a nice day
Edited by satdvb, 6 November 2011 - 10:12.
Re: Today's update makes box non-working #16
-
- Senior Member
- 389 posts
+68
Good
Posted 6 November 2011 - 10:18
maybe - but a config to deactivate this would be nice
Most problems can be solved simply by a closer look.
Re: Today's update makes box non-working #17
-
- Senior Member
- 1,449 posts
+69
Good
Posted 6 November 2011 - 10:19
I actually think the console msg are great
Have a nice day
It's an STB, not a computer. And a configuration option to enable it for people who like it would be better to have it enabled for all.
Re: Today's update makes box non-working #18
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 6 November 2011 - 12:21
You can unbind the console from the framebuffer:
echo 0 > /sys/class/vtconsole/vtcon1/bind
but I do like the console
Especially during the autorestore / autoinstall phase, it's good to see what is going on.
echo 0 > /sys/class/vtconsole/vtcon1/bind
but I do like the console
Especially during the autorestore / autoinstall phase, it's good to see what is going on.
Re: Today's update makes box non-working #19
-
- Senior Member
- 389 posts
+68
Good
Posted 6 November 2011 - 12:46
mmh, that doesn't work for me...
/sys/devices/virtual/vtconsole/vtcon1/bind still is at "1." even after reboot
/sys/devices/virtual/vtconsole/vtcon1/bind still is at "1." even after reboot
Edited by Steffen, 6 November 2011 - 12:49.
Most problems can be solved simply by a closer look.
Re: Today's update makes box non-working #20
-
- PLi® Core member
- 32,766 posts
+245
Excellent
Posted 6 November 2011 - 15:54
sure, it's bound by default, so after reboot the default '1' is visible again.
Also tagged with one or more of these keywords: ET9000
OpenPLI auf et9000 mit crashlog bei rebootStarted by manyone, 8 Dec 2019  et9000
|
|
|
||
ET9000 with SSD crashesStarted by erwin288, 26 Jan 2019 ET9000, SSD, Xtrend, crash
|
|
|
||
Sundtek USB Kabel tuner ET9000Started by KBDE, 23 Jan 2019 sundtek, cablescan, ET9000
|
|
|
||
Geluid stopt bij afspelen MKV ET9000Started by jbnl, 24 Nov 2018 mkv, et9000, geluid
|
|
|
||
Xbox One USB tuner op de ET9000Started by jbnl, 4 Sep 2017 usb, xtrend, et9000, tuner
|
|
|
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
