TNAP-7 Image Discussion

Thanks again. Sorry for my ignorance but I don't know how to make a zipped folder? If there is a next time (likely) I will ask how. If I ask now I will probably forget.

I just looked a post 175 again, and this:
"Deleting the enigma2 folder is similar to a factory reset. If you have access to telnet, the above commands should work."
That's what happened. Thanks...
 
Look....The main thing is the logs got posted!! Thanks! And now you know how to regain control of a FTA receiver.

The logs show the image that you are using is from about 2 weeks ago, dated 0201. Most of the crashes have been fixed. TNAP-7 is not available for download at the moment. But you may try to install the latest version which should be on the feeds sometime today.
 
Thanks. The mio4kplus will be removed from the build. Might try it again latter, but I simply cannot support a box like this that I cannot see.
 
Thanks for the log. What you or someone else will have to do is find a display combination that works, then post the files for it.

For example, the /usr/share/enigma2/display folder from a TNAP image besides TNAP 7 may work. The problem is I posted a folder from TNAP 6 here at one point and was told the display did not work. So I am at a loss now as to what needs to be done, plus I cannot try any files or other solutions to see what happens. If the display can't be fixed then it will have to be removed from the build.
 
el bandido said:
Thanks for the log. What you or someone else will have to do is find a display combination that works, then post the files for it.

For example, the /usr/share/enigma2/display folder from a TNAP image besides TNAP 7 may work. The problem is I posted a folder from TNAP 6 here at one point and was told the display did not work. So I am at a loss now as to what needs to be done, plus I cannot try any files or other solutions to see what happens. If the display can't be fixed then it will have to be removed from the build.
Click to expand...
Those display skins in the plugins don't even install on the 0216 build. Like they are blocked from installing. I have all 1-7 downloaded from the 0209 build but non do anything in 0216 build. I think they installed in the 0212 build but didn't do anything.
 
Correct. They are not in 0216 because they served no purpose. The display should work in 0216. Probably the only reason it does not work is the display file is not correct in /usr/share/enigma2/display.
 
I think my internet connection had stopped when I tried installing the first time. Tried again and they installed and show in GUI Settings> Front Panel Display>skin setup. Non do anything.
 
Let's try this again to be clear so we do not waste each other's time.

We need to find a file that works when properly added to the display folder in: /usr/share/enigma2/display
Instead of building 20-30 images that have to be downloaded and installed, try the attached display files and see if one of them will work.
 

Attachments

el bandido said:
Let's try this again to be clear so we do not waste each other's time.

We need to find a file that works when properly added to the display folder in: /usr/share/enigma2/display
Instead of building 20-30 images that have to be downloaded and installed, try the attached display files and see if one of them will work.
Click to expand...
Nothing is working other than the word Edision when booting up and white loading bar on the 0216 or 0212-0213 images. Doesn't seem to be a problem with the usr/share/enigma2/display.
something broke somewhere else. All the display skins 1-7 work in the 0209 image so they should work on 0216.
 
Should work and do work are two different things. Plus I cannot tell you what the build looked like on 0209 as much has changed since then. I will just pull it from the build until something can be figured out with it. As it is now, about the same as looking for a needle in a haystack. And you would think the /usr/share/enigma2/display Folder could be transferred between 0209 and 0216 images and solve the problem. Apparently that is not the case.
 
Never say it aint True because it may be. Udev apparently has nothing even related to a display. How did you come to that conclusion? Take a look at the udev-extraconf:


Makefile: 
SRC_URI += " \
    file://mount.sh \
    file://automount.rules \
    file://localextra.rules \
    file://write-deviceinfo.rules \
    file://device-info.sh \
    file://startup.sh \
    file://startup.rules \
    file://40-realtek-zerocd.rules \
"

do_install:append() {
    if [ -n "${MTD_BLACK}" ]; then
        echo "/dev/${MTD_BLACK}*" >> "${D}${sysconfdir}/udev/mount.ignorelist"
    fi
    install -m 0644 ${S}/write-deviceinfo.rules    ${D}${sysconfdir}/udev/rules.d/write-deviceinfo.rules
    install -m 0755 ${S}/device-info.sh ${D}${sysconfdir}/udev/scripts/device-info.sh
    install -m 0644 ${S}/startup.rules    ${D}${sysconfdir}/udev/rules.d/startup.rules
    install -m 0755 ${S}/startup.sh ${D}${sysconfdir}/udev/scripts/startup.sh
    install -m 0644 ${S}/40-realtek-zerocd.rules   ${D}${sysconfdir}/udev/rules.d/40-realtek-zerocd.rules
}

I do not know what it would take to roll back that package and test it. The display issue is both interesting and aggravating.
 
el bandido said:
Never say it aint True because it may be. Udev apparently has nothing even related to a display. How did you come to that conclusion? Take a look at the udev-extraconf:


Makefile: 
SRC_URI += " \
    file://mount.sh \
    file://automount.rules \
    file://localextra.rules \
    file://write-deviceinfo.rules \
    file://device-info.sh \
    file://startup.sh \
    file://startup.rules \
    file://40-realtek-zerocd.rules \
"

do_install:append() {
    if [ -n "${MTD_BLACK}" ]; then
        echo "/dev/${MTD_BLACK}*" >> "${D}${sysconfdir}/udev/mount.ignorelist"
    fi
    install -m 0644 ${S}/write-deviceinfo.rules    ${D}${sysconfdir}/udev/rules.d/write-deviceinfo.rules
    install -m 0755 ${S}/device-info.sh ${D}${sysconfdir}/udev/scripts/device-info.sh
    install -m 0644 ${S}/startup.rules    ${D}${sysconfdir}/udev/rules.d/startup.rules
    install -m 0755 ${S}/startup.sh ${D}${sysconfdir}/udev/scripts/startup.sh
    install -m 0644 ${S}/40-realtek-zerocd.rules   ${D}${sysconfdir}/udev/rules.d/40-realtek-zerocd.rules
}

I do not know what it would take to roll back that package and test it. The display issue is both interesting and aggravating.
Click to expand...
With the 0209 image I used webif to upgrade one packge at a time. After each package I did a restart. after that package it broke.
Had to reflash to fix and then skipped that package and installed everything else to be upgraded. Display is working fine.
That one pakage is the only one not installed and the image is stable.
 
Thanks!
I'll investigate this issue thoroughly. While it does seem unusual for udev-extraconf to break a front display, udev rules can affect device nodes and permissions for hardware devices like front panels. Let me examine the situation......
 
As a test, reinstall udev-extraconf_1.1-r0.34_cortexa15hf-neon-vfpv4.ipk
Copy the attached file to the box (/tmp) and install:
cd /tmp
opkg install --force-reinstall udev-extraconf_1.1-r0.34_cortexa15hf-neon-vfpv4.ipk
reboot

What this does:
Removes 1 line
21 KERNEL=="oled0", SYMLINK+="dbox/oled0"
22 KERNEL=="fp0", SYMLINK+="dbox/fp0"
23 KERNEL=="lcd0", SYMLINK+="dbox/lcd0"
24 -KERNEL=="lcd0", SYMLINK+="dbox/oled0"
24 KERNEL=="dboxlcd", SYMLINK+="dbox/lcd0"
25 KERNEL=="vtuner[0-9]*", SYMLINK+="misc/vtuner%n"
26 KERNEL=="pvr", SYMLINK+="misc/pvr
 

Attachments

Back
Top