+ Antworten
Seite 11 von 12 ErsteErste ... 9101112 LetzteLetzte
Ergebnis 101 bis 110 von 112
  1. #101
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    519
    Thanks
    137
    Thanked 601 Times in 244 Posts
    @marto: I can confirm the things you have observed; I have noticed them too. Apparently something inside Enigma2 dies, after which the spinner appears (when on), or it becomes impossible to return from standby. That the decoding of a transmitter continues is normal, as this is done in hardware. In both cases you lose the possiblity to control the receiver with the remote control or the frontpanel keys. As both functions are realised in the driver for the frontprocessor, it may be a solution to switch back to the original ipbox driver, although this needs fixing (that was the original problem and reason for my rewrite attempt). Unfortunately I do not have the time at moment to address this problem in depth.

    @harryhase: you are experiencing a problem that I can not solve at the moment. There is nothing wrong with the image and also nothing wrong with what you are doing. The problem is the bootloader. The USB capable bootloaders for all HS7xxx models all share the same problem: after finding the USB stick to boot from they switch off the power supply to the stick, causing /dev/sda not to be made and the bootloop ending in a time out. This means the bootprocess is extermely stick dependent (I have only one stick out of more than 35 that sometimes works). In the past I have looked for a workaround for several times now and have not found one, other than fixing the bootloader, of which I do not have the source code.

    I can have a look if somebody can get me the source code of the USB enabled bootloader, or at least the code to read/flash an .ird file.

    Regards,

    Audioniek.
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark Triplex, Amiko Alien 3, Sogno Spark Revolution, Topfield TF7710HDPVR, Kathrein UFS912, Vizyon revolution 820HD PVR, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  2. The Following 2 Users Say Thank You to Audioniek For This Useful Post:



  3. #102
    Neuer Benutzer
    Registriert seit
    26.05.2012
    Beiträge
    9
    Thanks
    4
    Thanked 0 Times in 0 Posts
    Hi, Audioniek and thanks for confirming the issues! Perhaps you can use the frontprocessor driver from "PKT Hyperion 5.5 CUBEREVO", which is a very stable image, but outdated already, or even from the latest HDMU images for this box...


  4. #103
    Erfahrener Benutzer Avatar von harryhase
    Registriert seit
    26.01.2013
    Beiträge
    196
    Thanks
    34
    Thanked 55 Times in 31 Posts
    @Audioniek: Did you ever tried booting with active usb hub, that maybe works?
    maybe we can ask nit or gost4711 if they have the source code, the titanit has a own bootloader


  5. #104
    Neuer Benutzer
    Registriert seit
    29.12.2015
    Beiträge
    14
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Zitat Zitat von Audioniek Beitrag anzeigen

    @harryhase: you are experiencing a problem that I can not solve at the moment. There is nothing wrong with the image and also nothing wrong with what you are doing. The problem is the bootloader. The USB capable bootloaders for all HS7xxx models all share the same problem: after finding the USB stick to boot from they switch off the power supply to the stick, causing /dev/sda not to be made and the bootloop ending in a time out. This means the bootprocess is extermely stick dependent (I have only one stick out of more than 35 that sometimes works). In the past I have looked for a workaround for several times now and have not found one, other than fixing the bootloader, of which I do not have the source code.

    I can have a look if somebody can get me the source code of the USB enabled bootloader, or at least the code to read/flash an .ird file.

    Regards,

    Audioniek.
    but why didn’t we face the same issue with PKT image and your old images (Non Openpli) with the same bootloader?

    Asking only to understand the difference.


  6. #105
    Developer
    Registriert seit
    18.07.2012
    Ort
    Ridderkerk, Niederlande
    Beiträge
    519
    Thanks
    137
    Thanked 601 Times in 244 Posts
    @tanaka:

    Good point. Apparently the PKT people have found a solution outside the bootloader I have not thought of yet. I will look into the problem again. If anyone has a suggestion for a solution within the image, I am glad to here it.

    Regards,

    Audioniek.
    Receivers: Rebox: RE-4000, 8000, 9000, 2200, 2210, 2220, 4200, 4210, 4220, 8220, 8500, SAB Unix Triple, Golden Media Spark Triplex, Amiko Alien 3, Sogno Spark Revolution, Topfield TF7710HDPVR, Kathrein UFS912, Vizyon revolution 820HD PVR, nBox BKSA/BSLA/BXZB/BZZB, Vitamin HD 5000
    Sats: Astra 1, 2 & 3, Hotbird
    Main activity: building my own E2 images for Fortis receivers

  7. The Following 2 Users Say Thank You to Audioniek For This Useful Post:



  8. #106
    Erfahrener Benutzer Avatar von harryhase
    Registriert seit
    26.01.2013
    Beiträge
    196
    Thanks
    34
    Thanked 55 Times in 31 Posts
    okay, i see what we need to get it to boot; A kind of usb-reset or refresh of the usb devices. it is not a problem of the bootloader, because a part of the image is already running bevor it stop.

    1) take a usb hub with at minimum 2 ports
    2) let the device boot until you see the message of #100 in the terminal
    3) pull off the usb-stick and
    4) wait a second
    5) plug the usb-stick into the other port
    6) the device continuses the booting and the image starts


    edit: not working every time, but now i can see the problem, if the usb-stick is not lightning, than it does not work, if it lights it works. i seems like the usb driver are not correct, so that it is not every time correct initialized

    edit2: if i change the uImage (from PKT) then it all the time starts booting (okay, not starting, because not the right initialisation, but they have solved this issue)
    Geändert von harryhase (04.06.2020 um 20:53 Uhr)


  9. #107
    Neuer Benutzer Avatar von aness
    Registriert seit
    07.05.2012
    Beiträge
    17
    Thanks
    11
    Thanked 4 Times in 4 Posts
    Thanks Audioniek great work we wait to usb cubrevo images

  10. The Following User Says Thank You to aness For This Useful Post:



  11. #108
    Neuer Benutzer
    Registriert seit
    27.02.2015
    Beiträge
    1
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Hi Audioniek Cuberevo Mini II Micom front panel driver version V1.08Audioniek initializing
    [cuberevo_micom] 1. = 0x08
    [cuberevo_micom] 3. = 0x06
    [cuberevo_micom] 5. = 0x02
    [cuberevo_micom] Pos. response received (0xeb)
    [cuberevo_micom] Command processed - remaining jiffies 119
    [cuberevo_micom] 7. = 0x08
    [cuberevo_micom] 9. = 0x06
    [cuberevo_micom] 11. = 0x02
    [cuberevo_micom] Pos. response received (0xeb)
    [cuberevo_micom] Command processed - remaining jiffies 119
    [cuberevo_micom] 13. = 0x08
    [cuberevo_micom] 15. = 0x06
    [cuberevo_micom] 17. = 0x02
    [cuberevo_micom] Pos. response received (0xeb)
    [cuberevo_micom] Command processed - remaining jiffies 120
    [cuberevo_micom] Frontpanel version: 02.06.2008
    [cuberevo_micom] Probe: Micom front panel real time clock
    micom-rtc micom-rtc: rtc core: registered micom as rtc0
    [cuberevo_micom] Unknown IOCTL 0x5401.
    [cuberevo_micom] micomWriteString UTF8 text: [LOAD], len = 4
    [cuberevo_micom] micomWriteString Non-UTF8 text: [LOAD], len = 4
    [cuberevo_micom] Text: LOAD (len = 14)
    [cuberevo_micom] close minor 0


  12. #109
    Benutzer
    Registriert seit
    24.05.2014
    Beiträge
    36
    Thanks
    11
    Thanked 18 Times in 14 Posts

  13. The Following 2 Users Say Thank You to ainouna For This Useful Post:



  14. #110
    Neuer Benutzer
    Registriert seit
    28.12.2012
    Beiträge
    8
    Thanks
    0
    Thanked 1 Time in 1 Post
    Thank you again for your hard work. I posted back a while about 1028 or at7500 having issues with a particular signal and posted a file for it. I have narrowed it down to 1 particular type of signal...DVB S2 30000 SR 5/6 FEC...does not matter if channel is MPEG 2 or 4 ... the tuner has trouble locking that signal...S2 8psk 30000 SR 5/6 FEC......thank you for looking at that.


Berechtigungen

  • Neue Themen erstellen: Ja
  • Themen beantworten: Ja
  • Anhänge hochladen: Ja
  • Beiträge bearbeiten: Ja
  •