Jump to content


Photo

Which image to reflash a DM8000


  • Please log in to reply
42 replies to this topic

#1 Marc-UK

  • Senior Member
  • 39 posts

+1
Neutral

Posted 5 December 2014 - 21:39

Hello all,

 

In the download section, I see 0 byte images since 29.11 and 2 images 27.11 and 28.11

 

Which image should I use if I need to reflash my box to get the subsequent updates (but not break second stage)?

 

Which image is the last good one before the new C library? 15.11?

 

Thank you



Re: Which image to reflash a DM8000 #2 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 6 December 2014 - 09:24

There as some problems with the DMM images, which may be solved (or not, not sure yet, see the announcement from last year...)


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Which image to reflash a DM8000 #3 catastrofus

  • Senior Member
  • 3,480 posts

+43
Good

Posted 6 December 2014 - 21:49

There are, at this moment, no working images (for the dm8k) that includes the updated C-library.

The current image (dec 6) isn t working but the image from nov 27 is working but this image doesn t include the new library.

 

Hello all,

 

In the download section, I see 0 byte images since 29.11 and 2 images 27.11 and 28.11

 

Which image should I use if I need to reflash my box to get the subsequent updates (but not break second stage)?

 

Which image is the last good one before the new C library? 15.11?

 

Thank you


2 x ultimo4k (dvb-c fbc + 1 dvb-s2, 9.0r/nb) + een et10k/osmini ((nb) geen tuners en dus fallbackclient, nb) met een Synology ds214+ (2 x 6 TB) op DSM 7.1.1 in ziggo oost (voormalig @Home) + A1/A2/A3/HB (TechniSat)
 


Re: Which image to reflash a DM8000 #4 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 6 December 2014 - 22:23

Self build dm8k works perfect with libc-2.20 . As long the libc-3.1 headers are used wen compiling.



Re: Which image to reflash a DM8000 #5 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 6 December 2014 - 22:42

Self build dm8k works perfect with libc-2.20 . As long the libc-3.1 headers are used wen compiling.

 

Without libc-3.1 what error do you get?


Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #6 Marc-UK

  • Senior Member
  • 39 posts

+1
Neutral

Posted 6 December 2014 - 22:58

 

There are, at this moment, no working images (for the dm8k) that includes the updated C-library.

The current image (dec 6) isn t working but the image from nov 27 is working but this image doesn t include the new library.

Thank you Catastrofus

 

Image from 27.11 disappeared and only 28.11 is left. Does this one work? Does it also use the old library?



Re: Which image to reflash a DM8000 #7 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 6 December 2014 - 23:03

 

Self build dm8k works perfect with libc-2.20 . As long the libc-3.1 headers are used wen compiling.

 

Without libc-3.1 what error do you get?

 

Enigma start stops start stops in a continu loop. I just shut box off builded again with preferred headers 3.1. and reflashed all ok



Re: Which image to reflash a DM8000 #8 catastrofus

  • Senior Member
  • 3,480 posts

+43
Good

Posted 6 December 2014 - 23:33

I think the image from nov 28 will also work but it still uses the old libc.

 

 

 

 

There are, at this moment, no working images (for the dm8k) that includes the updated C-library.

The current image (dec 6) isn t working but the image from nov 27 is working but this image doesn t include the new library.

Thank you Catastrofus

 

Image from 27.11 disappeared and only 28.11 is left. Does this one work? Does it also use the old library?

 


2 x ultimo4k (dvb-c fbc + 1 dvb-s2, 9.0r/nb) + een et10k/osmini ((nb) geen tuners en dus fallbackclient, nb) met een Synology ds214+ (2 x 6 TB) op DSM 7.1.1 in ziggo oost (voormalig @Home) + A1/A2/A3/HB (TechniSat)
 


Re: Which image to reflash a DM8000 #9 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 6 December 2014 - 23:41



Self build dm8k works perfect with libc-2.20 . As long the libc-3.1 headers are used wen compiling.


Without libc-3.1 what error do you get?
Enigma start stops start stops in a continu loop. I just shut box off builded again with preferred headers 3.1. and reflashed all ok

And the error is? If the problem is enigma2 it should be fixed there right?
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #10 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 6 December 2014 - 23:59

 

 

 

Self build dm8k works perfect with libc-2.20 . As long the libc-3.1 headers are used wen compiling.


Without libc-3.1 what error do you get?
Enigma start stops start stops in a continu loop. I just shut box off builded again with preferred headers 3.1. and reflashed all ok

And the error is? If the problem is enigma2 it should be fixed there right?

 

Sorry don't have the error no time, I needed the box to watch . Just by setting preferred libc headers to 3.1 it works (it was really not there for nothing) . It's not enigma as this works fine now. Some off the library's will not be compatible with kernel anymore. And that's why enigma does not start. But wich lib. ?? That's the question of the day



Re: Which image to reflash a DM8000 #11 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 08:25


Sorry don't have the error no time, I needed the box to watch . Just by setting preferred libc headers to 3.1 it works (it was really not there for nothing) . It's not enigma as this works fine now. Some off the library's will not be compatible with kernel anymore. And that's why enigma does not start. But wich lib. ?? That's the question of the day

 

So you don't have the time, OpenPLi do not have Dreambox receivers any more, the OpenPLi statement is clear... Dreamboxes will build until came to a non usable state.

 

Maybe that time has come? ;)

 

So if nobody take the task to find what is causing the error with newer libc on Dreamboxes, will be da end of OpenPLi fur Dreamboxes....


Edited by athoik, 7 December 2014 - 08:25.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #12 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 08:49

Temporary solution (until the next error)

 

opkg update
opkg install enigma2-src

 

Then change the following : /usr/lib/enigma2/python/Components/NimManager.py

 

-                                if "DVB-S2" in types:
+                                if "DVB-S2" in types and "DVB-S" in types:
                                        # DVB-S2 implies DVB-S support
                                        types.remove("DVB-S")

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #13 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 7 December 2014 - 09:13

How strange that this is cause by a libc header change??? Do you have an explanation? Maybe d4l api upgrade?


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Which image to reflash a DM8000 #14 isson

  • Senior Member
  • 37 posts

+1
Neutral

Posted 7 December 2014 - 11:25

 

Temporary solution (until the next error)

opkg update
opkg install enigma2-src

Then change the following : /usr/lib/enigma2/python/Components/NimManager.py

-                                if "DVB-S2" in types:
+                                if "DVB-S2" in types and "DVB-S" in types:
                                        # DVB-S2 implies DVB-S support
                                        types.remove("DVB-S")

Thanks your support . i changed /usr/lib/enigma2/python/Components/NimManager.py but showing only DVB-S2 channels.Box dm500hd


Edited by isson, 7 December 2014 - 11:27.

WeTek Play


Re: Which image to reflash a DM8000 #15 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 7 December 2014 - 11:51

 


Sorry don't have the error no time, I needed the box to watch . Just by setting preferred libc headers to 3.1 it works (it was really not there for nothing) . It's not enigma as this works fine now. Some off the library's will not be compatible with kernel anymore. And that's why enigma does not start. But wich lib. ?? That's the question of the day

 

So you don't have the time, OpenPLi do not have Dreambox receivers any more, the OpenPLi statement is clear... Dreamboxes will build until came to a non usable state.

 

Maybe that time has come? ;)

 

So if nobody take the task to find what is causing the error with newer libc on Dreamboxes, will be da end of OpenPLi fur Dreamboxes....

 

 

So it be then.

 

I give You the error. Quit simple the dreambox linux kernel only supports libc-headers. 3.1  . That's it, nothing more or less.

 

The same problem is on vuduo kernels and a lot off other boxes. It's not specific for dm boxes.



Re: Which image to reflash a DM8000 #16 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 7 December 2014 - 12:23

Well seems that for dvb-S support You need the correct libc-headers. not for dvb-S2. But Why don'y ask me. I just give the way off building image how it work's. More I can't do. If You find a better way off course it's ok. But removing dvb-S support seems not to be the solution. (note kernel is closed source and dvb modules also). That's why I think there is no other solution then using the right libc headers version. Off course I maybe wrong.

 

Perhaps building with a fixed lower libc header version (for all boxes ) may do as well.



Re: Which image to reflash a DM8000 #17 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 12:39

With the above patch at least you have the system working, right? So there is nothing wrong in the libraries.

 

Back to the issue now,

 

It seems that delsys doesn't contain the compatible values (DVB-S2 implies DVB-S, same for DVB-T2 implies DVB-T).

 

Using the latest libc on kernels less than kernel 3.3 (newer vu+ with 3.3 kernel have that problem?) they don't populate correctly the delsys.

 

So what we need to find is what changed and either patch kernel either fix enigma2 (depending where the issue is)


Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #18 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 12:49

Kernel < 3.3 dosn't contain DTV_ENUM_DELSYS


Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Which image to reflash a DM8000 #19 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 7 December 2014 - 12:50

With the above patch at least you have the system working, right? So there is nothing wrong in the libraries.

 

Back to the issue now,

 

It seems that delsys doesn't contain the compatible values (DVB-S2 implies DVB-S, same for DVB-T2 implies DVB-T).

 

Using the latest libc on kernels less than kernel 3.3 (newer vu+ with 3.3 kernel have that problem?) they don't populate correctly the delsys.

 

So what we need to find is what changed and either patch kernel either fix enigma2 (depending where the issue is)

That I did not checked, but as far I can see You can't patch kernel. It's comming from manifacturer compiled. The modules also.

 

Maybe not a library but a file which enigma2 needs. If you just omit dvb-S support in enigma2 it seemes to work , but no dvb-S  channels anymore. 9 changes on 10 it's even not the kernel self. But just the dvb driver. And that You can't patch. Somehow there is a declaration into the libc-headers specific to kernel or for the dvb module. If You could find that perhaps patching the headers file by just adding it, that could solve the issue. And then working with one specific libc-header 3.3 where patch is applied. Problem is to find which declaration is missing.



Re: Which image to reflash a DM8000 #20 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 13:16

Kernel < 3.3 dosn't contain DTV_ENUM_DELSYS

 

But libc-header contains DTV_ENUM_DELSYS...

 

So most probably the following code needs more finetuning or we need to add DTV_ENUM_DELSYS support into kernels 3.1 and 3.2.

#ifdef DTV_ENUM_DELSYS
                        struct dtv_property p[1];
                        p[0].cmd = DTV_ENUM_DELSYS;
                        struct dtv_properties cmdseq;
                        cmdseq.num = 1;
                        cmdseq.props = p;
                        if (::ioctl(m_fd, FE_GET_PROPERTY, &cmdseq) >= 0)
                        {
                                m_delsys.clear();
                                for (; p[0].u.buffer.len > 0; p[0].u.buffer.len--)
                                {
                                        fe_delivery_system_t delsys = (fe_delivery_system_t)p[0].u.buffer.data[p[0].u.buffer.len - 1];
                                        m_delsys[delsys] = true;
                                }
                        }
#else
                        /* old DVB API, fill delsys map with some defaults */
                        switch (fe_info.type)
                        {
                                case FE_QPSK:
                                {
                                        m_delsys[SYS_DVBS] = true;
#if DVB_API_VERSION >= 5
                                        if (fe_info.caps & FE_CAN_2G_MODULATION) m_delsys[SYS_DVBS2] = true;
#endif
                                        break;
                                }
                                case FE_QAM:
                                {
#if DVB_API_VERSION > 5 || DVB_API_VERSION == 5 && DVB_API_VERSION_MINOR >= 6
                                        m_delsys[SYS_DVBC_ANNEX_A] = true;
#else
                                        m_delsys[SYS_DVBC_ANNEX_AC] = true;
#endif
                                        break;
                                }
                                case FE_OFDM:
                                {
                                        m_delsys[SYS_DVBT] = true;
#if DVB_API_VERSION > 5 || DVB_API_VERSION == 5 && DVB_API_VERSION_MINOR >= 3
                                        if (fe_info.caps & FE_CAN_2G_MODULATION) m_delsys[SYS_DVBT2] = true;
#endif
                                        break;
                                }
                                case FE_ATSC:   // placeholder to prevent warning
                                {
                                        break;
                                }
                        }
#endif

Edited by athoik, 7 December 2014 - 13:16.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users