2062 replies to this topic

[1455]

You did it well.  

[Shadowman94]

Black screen on start is solved...

 

1. Im using NODM for start xserver and its need to run --verbose mode.

2, In enigma2.sh the enigma2 is loaded in LD_PRELOAD, so its not good idea....  changed to:

LD_PRELOAD=$LIBS
${EXEC_PREFIX}/bin/enigma2

need to separate from lib loader.

 

Can u remove predefined banquets in your packages? its annoying a bit for need to delete always

Edited by Shadowman94, 9 August 2017 - 10:09.

[1455]

Excellent!

 

My question is to connoisseurs. How to raise the level of DEBUG in the new Enigma? He is very meager:

PYTHONPATH: /usr/local/e2/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
.......................................

[Shadowman94]

 

Excellent!

 

My question is to connoisseurs. How to raise the level of DEBUG in the new Enigma? He is very meager:

PYTHONPATH: /usr/local/e2/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA_DEBUG_LVL=3
.......................................

I have to check it after, but after restart pc again black screen... I dont know why, and this couse by enigma2, cuz i tried to start teamspeak3 client, and it works...

but after i started engima2 screen goes to 1080p resolution and black screen and if i close enigma2 then resolution is not change back and still black screen, until i manually change VT with ALT + CTRL + 1 and back to GUI...

 

In Xorg log:

 

[  3551.493] (WW) RADEON(0): Page flip failed: No space left on device

[  3551.588] (WW) RADEON(0): flip queue failed: No space left on device

Edited by Shadowman94, 9 August 2017 - 11:52.

[1455]

predefined banquets

 

Did you mean archived plugins? OK. A "banquet" is a feast about a successful work.

[Shadowman94]

 

predefined banquets

 

Did you mean archived plugins? OK. A "banquet" is a feast about a successful work.

 

Sorry i misstyped, Bouquets ( favorited channels )

[1455]

OK. I'll also clean the package of unnecessary skins and stuff. I did not think about the size of the downloaded archive.

[Shadowman94]

OK. I'll also clean the package of unnecessary skins and stuff. I did not think about the size of the downloaded archive.

Much better :-D and i solved blackscreen problem... have problem with enigma2 lcd feature... its want to open /dev/fb1 and this is symlinked fb0... so when change this resolution, the xorg resolution is reset.

I compiled enigma2 with this parameter: --with-lcddev=/dev/fb10  (fb10, 11, the point is provide non-existent frame buffer).

Edited by Shadowman94, 9 August 2017 - 21:48.

[1455]

And if you remove from enigma2_pre_start.sh

sudo ln -s /dev/fb0 /dev/fb1

what will happen? I thought, since the enigma asks, then i need to give her a fb1.

[1455]

So I checked on 17.04 on the old computer and

#sudo ln -s /dev/fb0 /dev/fb1

helped! There is no longer that defect I wrote about earlier. (The top half of the screen is black or black squares at the top of the screen). It is interesting that on 16.04 there is no such defect.

[1455]

<- But then the enigma crash on subtitles.

[1455]

<- On the some older video cards, the command

hwinfo --framebuffer

shows that resolution 1920x1080 is absend! This problem is unsolvable. On such video cards, subtitles will not work in the resolution of the enigma screen.

[1455]

In /etc/modprobe.d/blacklist-framebuffer.conf need comment:

#blacklist vesafb
#blacklist nvidiafb

or

#blacklist radeonfb

In /etc/modprobe.d/modules need add:

vesafb
fbcon

In /etc/default/grub need add resolution from your hwifo --framebuffer:

#GRUB_GFXMODE="1280x1024"
GRUB_GFXMODE="1920x1080"
#GRUB_GFXMODE="1280x800"
GRUB_GFXPAYLOAD_LINUX="keep"

Then:

update-initramfs -u
update-grub
reboot

[1455]

<- Fore example, Ubuntu 17.04, AMD Athlon™ 64 X2 Dual Core Processor 6000+, GeForce 8600:
Possibly framebuffer resolution not more GRUB_GFXMODE=800x600 with /dev/fb1. The enigma don't fall into a black screen or black squares. Maybe not enough memory. I don't know. Subtitles don't work (crash), but with this resolution I don't need to delete /dev/fb1.

Edited by 1455, 10 August 2017 - 12:45.

[Shadowman94]

Intresting... Im using ubuntu server 16.04.5 LTS. Subtitles is not required for me
Any idea how can i make work lirc with serial com port support?
I have home made IR serial reciever.

[1455]

http://forum.free-x....27484#post27484    message 12

https://bitbucket.or...Cat/media_build

 

On 16.04 with kernel 4.4 - IR serial exactly is OK.  I attached the wrong archive above. Try again according to the instructions. If you can not download in the process, then tell me what to send.

But on 17.04 generally a disaster with lirc serial and I don't now what to do.

Edited by 1455, 11 August 2017 - 18:43.

[1455]

<- make work lirc with serial com port support:

https://bbs.archlinu...ic.php?id=30330

Q:With what kernel?

[1455]

For Ubuntu-17.04 now is used gstreamer1.0 because the rewind and position indicator didn't work.

[1455]

I found that at 17.04 there are "i686-linux-gnu" and "i386-linux-gnu" simultaneously! Need time to think.
Please wait or use 16.04.

[Shadowman94]

I found that at 17.04 there are "i686-linux-gnu" and "i386-linux-gnu" simultaneously! Need time to think.
Please wait or use 16.04.

 

Pasted from other place.

 

A Brief Explanation of CPU Naming Schemes:

The X86 processors started with the Intel 8086 processor way back in 1978. They were incrementally improved (80186, 80286) and then Intel released the Intel 386 (i386) in 1980. That was then followed by he 486 (i486), the Pentium (i586), and the Pentium Pro/2/3/4 and Celeron (i686). At the same time, rival AMD released their Athlon/Duron/T-bird (also i686).

Since all these processors were based on the same architecture (basically they read/wrote 1's and 0's in the same way), and their names all contained "86", the whole family was collectively called "X86". All the X86 processors including and after the 386 are 32-bit.

The difference between a Pentium/Celeron and an Athlon/Duron or Athlon/Sempron is that Pentium and Athlon are the top-performing, more expensive models whereas the Celeron/Duron/Sempron are cheaper, less powerful chips. They are not a different architecture.

Since 2000, the trend has been to move toward 64-bit processors, and several different architectures popped up. DEC's Alpha and Motorola's PPC chips have been 64-bit for a while, but Intel's Itanium and Xeon and AMD's Athlon64 are the new kids on the block.

The difference between the Itanium (IA64) and PowerPC (PPC) versus the Athlon64 is that the Itanium and PPC have completely different architectures (they speak different 1 and 0 languages), whereas the Athlon64 speaks the same language as the 32-bit X86 processors, but adds 64-bit memory registers. Therefore the name of the Athlon64 in generic terms is "X86_64".

Intel, not to be outdone, has since redesigned its 64-bit Xeon processors to use the same kind of architecture as the Athlon64, calling it "Intel Extended Memory 64 Technology" (EM64T). Basically they couldn't say they copied AMD without being laughed at in irony (since AMD got its start by simply copying Intel's chips). Both the AMD64 and the Intel EM64T processors are collectively called "X86_64".

The Intel Core processors come in two types. The original Core Duo processor is a 32-bit processor with two cores (i686). The Core 2 Duo is a 64-bit processor with two cores. The Core Duo (to the best of my knowledge) is a regular X86 processor, while the Core 2 Duo is an X86_64.

Certain models of the Pentium 4 processor (not just the Xeon) were shipped with "EM64T" technology. These processors (such as the Intel Pentium 4 521) are essentially the same as an AMD64 in their architecture, and are capable of running both 32-bit software and OSes as well as 64-bit. Software compiled for AMD64 should work on these processors.

In 2008, Intel developed a new brand name called i7, which despite its confusing name is NOT a new i786 architecture. Instead, it's just another set of X86_64 chips. For more information, look here.

Edited by Shadowman94, 14 August 2017 - 20:46.