Seite 2 von 2 ErsteErste 12
Ergebnis 11 bis 15 von 15
  1. #11
    Anfänger
    Registriert seit
    26.03.2019
    Beiträge
    20
    Thanks (gegeben)
    0
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von el bandido Beitrag anzeigen
    The scan.cpp is used for scan, and has not been changed in months. (see links)

    Again, knowing exactly what the problem is might help get it fixed. No one else seems to have this issue.
    Posting your lamedb file located in /etc/enigma2 of your receiver might help.
    Posting your settings file located in /etc/enigma2 of your receiver might help. (Check the settings file for passwords before posting it.)
    Explaining in detail what channels/transponders are mixed on 125w might help.

    enigma2/lib at 6.4 . openatv/enigma2 . GitHub

    enigma2/lib/dvb at 6.4 . openatv/enigma2 . GitHub
    lamedb Files
    Angehängte Dateien Angehängte Dateien
    Geändert von carlos_08_1 (18.03.2021 um 18:07 Uhr)

  2. Thanks el bandido bedankten sich
    •   Alt Advertising

       

  3. #12

    Registriert seit
    12.05.2015
    Beiträge
    103
    Thanks (gegeben)
    303
    Thanks (bekommen)
    28
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    You may try moving the ScanSetup file from ATV 6.3 to ATV 6.4. This file is located in /usr/lib/enigma2/python/Screens of the receiver. It looks like there were some changes made to this file around November, 2020. Change that file, Reboot the box and see if there is any difference..

    As for duplicate channels, or channels mixing, I do not see them yet in the files that you have posted. What is the exact problem on 125w? One of your lamedb files does not have 125w on it.

  4. #13

    Registriert seit
    12.05.2015
    Beiträge
    103
    Thanks (gegeben)
    303
    Thanks (bekommen)
    28
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    I downloaded and extracted OpenATV 6.3 and 6.4 images for the Solo4k receiver. It looks like there was a driver change in February-2021.

    6.3 image drivers:
    drwxr-xr-x 2 pli pli 4096 Jan 11 04:58 .
    drwxr-xr-x 4 pli pli 4096 Jan 11 04:59 ..
    -rw-r--r-- 1 pli pli 8116 Nov 19 12:28 bcm_event.ko
    -rw-r--r-- 1 pli pli 5988 Nov 19 12:28 brcmfb.ko
    -rw-r--r-- 1 pli pli 29952 Nov 19 13:03 cdfs.ko
    -rw-r--r-- 1 pli pli 6725424 Nov 19 12:28 dvb_base.ko
    -rw-r--r-- 1 pli pli 704108 Nov 19 12:28 dvb-bcm7376.ko
    -rw-r--r-- 1 pli pli 2804 Nov 19 12:28 fpga_directc.ko
    -rw-r--r-- 1 pli pli 4904 Nov 19 12:28 procmk.ko
    6.4 image drivers:
    drwxr-xr-x 2 pli pli 4096 Mar 18 16:43 .
    drwxr-xr-x 4 pli pli 4096 Mar 18 16:44 ..
    -rw-r--r-- 1 pli pli 8116 Feb 26 05:59 bcm_event.ko
    -rw-r--r-- 1 pli pli 5988 Feb 26 05:59 brcmfb.ko
    -rw-r--r-- 1 pli pli 29704 Feb 26 06:38 cdfs.ko
    -rw-r--r-- 1 pli pli 6725424 Feb 26 05:59 dvb_base.ko
    -rw-r--r-- 1 pli pli 704108 Feb 26 05:59 dvb-bcm7376.ko
    -rw-r--r-- 1 pli pli 2804 Feb 26 05:59 fpga_directc.ko
    -rw-r--r-- 1 pli pli 4904 Feb 26 05:59 procmk.ko
    You should be able to copy these drivers from the 6.3 image to the 6.4 image, But I cannot guarantee the results. I have transferred drivers from different image versions before, and everything work. I have also transferred drivers from different image versions before, and have the receiver get stuck on boot. Ref-flashing the image fixed it. So transfer drivers at your own risk!

    The seven files shown above that you will need to transfer are located at: /lib/modules/3.14.28-1.8/extra in the receiver. ReBoot the box after transferring the files.
    The About page in the receiver should show the driver change (Menu--->About). You may check the driver information before and after you make the changes. You may also check the dates for the drivers in the different image versions (ATV 6.3 & ATV 6.4).
    Geändert von el bandido (19.03.2021 um 05:06 Uhr)

  5. #14
    Anfänger
    Registriert seit
    26.03.2019
    Beiträge
    20
    Thanks (gegeben)
    0
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von el bandido Beitrag anzeigen
    I downloaded and extracted OpenATV 6.3 and 6.4 images for the Solo4k receiver. It looks like there was a driver change in February-2021.

    6.3 image drivers:


    6.4 image drivers:


    You should be able to copy these drivers from the 6.3 image to the 6.4 image, But I cannot guarantee the results. I have transferred drivers from different image versions before, and everything work. I have also transferred drivers from different image versions before, and have the receiver get stuck on boot. Ref-flashing the image fixed it. So transfer drivers at your own risk!

    The seven files shown above that you will need to transfer are located at: /lib/modules/3.14.28-1.8/extra in the receiver. ReBoot the box after transferring the files.
    The About page in the receiver should show the driver change (Menu--->About). You may check the driver information before and after you make the changes. You may also check the dates for the drivers in the different image versions (ATV 6.3 & ATV 6.4).
    Ok let me try this last option because copy ScanSetup did not work

    I replaced that folder before but I cannot test it at all

  6. #15
    Anfänger
    Registriert seit
    26.03.2019
    Beiträge
    20
    Thanks (gegeben)
    0
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von el bandido Beitrag anzeigen
    I downloaded and extracted OpenATV 6.3 and 6.4 images for the Solo4k receiver. It looks like there was a driver change in February-2021.

    6.3 image drivers:


    6.4 image drivers:


    You should be able to copy these drivers from the 6.3 image to the 6.4 image, But I cannot guarantee the results. I have transferred drivers from different image versions before, and everything work. I have also transferred drivers from different image versions before, and have the receiver get stuck on boot. Ref-flashing the image fixed it. So transfer drivers at your own risk!

    The seven files shown above that you will need to transfer are located at: /lib/modules/3.14.28-1.8/extra in the receiver. ReBoot the box after transferring the files.
    The About page in the receiver should show the driver change (Menu--->About). You may check the driver information before and after you make the changes. You may also check the dates for the drivers in the different image versions (ATV 6.3 & ATV 6.4).
    Seem to have the same problem

    I Open my last backup and those files have date of 2020-04-13

    Scan issue vs openATV 6.3-driver.png


Seite 2 von 2 ErsteErste 12

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 16:44 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,56%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com