Mut@nt HD2400 Sticks on "Booting..."

[yorkshirepudding]

I've had a Mut@nt HD2400 for several years without any problems. A few weeks ago it wouldn't start. After much head scratching, I decided to try another PSU and it worked.
I downloaded the latest OpenVix image and put it on a trusty USB stick that I have reserved for this purpose.
Put it in, power it up, it says Image Found. Flash? Press Up. It spends a couple of minutes flashing. Says Flashing Completed. Says "Booting..." Stays on "Booting..." for as long as I leave it
All this time the Mut@nt logo shows on screen if I have the TV on.

I managed to SSH into it and found the following:

root@mutant2400:/# dmesg
[ 1036.290000] do_page_fault(): sending SIGSEGV to enigma2 for invalid read access from 0000001c
[ 1036.300000] epc = 75cc4abc in libc.so.6[75c40000+18b000]
[ 1036.306000] ra  = 00561460 in enigma2[400000+357000]

Any suggestions for what to try next?
Thanks in advance.

 

[el bandido]

Might help to post the output of init 4 then enigma2

init 4 followed by enigma2 In telnet or terminal should produce a log that you can attach here. The command dmesg did not produce much.

 

[yorkshirepudding]

Might help to post the output of init 4 then enigma2

init 4 followed by enigma2 In telnet or terminal should produce a log that you can attach here. The command dmesg did not produce much.

Thanks for the tip.

root@mutant2400:~# init 4
root@mutant2400:~# enigma2
[Enigma2] PYTHONPATH: /usr/lib/enigma2/python
[Enigma2] DVB_API_VERSION 5 DVB_API_VERSION_MINOR 12
ENIGMA_DEBUG_LVL=4
<    86.238375> 09:08:18.1621 [Avahi] avahi_timeout_new
<    86.238993> 09:08:18.1627 [Avahi] avahi_watch_new(3 0x1)
<    86.239290> 09:08:18.1630 [Avahi] avahi_timeout_update
<    86.239744> 09:08:18.1635 [Avahi] avahi_timeout_new
<    86.240646> 09:08:18.1644 [Avahi] avahi_timeout_free
<    86.241294> 09:08:18.1651 [Avahi] avahi_timeout_new
<    86.242296> 09:08:18.1660 [Avahi] avahi_timeout_free
<    86.242744> 09:08:18.1665 [Avahi] avahi_timeout_new
<    86.243679> 09:08:18.1674 [Avahi] avahi_timeout_free
<    86.244297> 09:08:18.1680 [Avahi] avahi_timeout_new
<    86.245531> 09:08:18.1692 [Avahi] avahi_timeout_free
<    86.245957> 09:08:18.1697 [Avahi] avahi_timeout_new
<    86.247336> 09:08:18.1711 [Avahi] avahi_timeout_free
<    86.247843> 09:08:18.1716 [Avahi] avahi_timeout_new
<    86.249205> 09:08:18.1729 [Avahi] avahi_timeout_free
<    86.249572> 09:08:18.1733 [Avahi] client state: 2
<    86.250542> 09:08:18.1743 [Avahi] avahi_timeout_new
<    86.251907> 09:08:18.1756 [Avahi] avahi_timeout_free
<    86.252345> 09:08:18.1761 [eInit] + (1) Background File Eraser
<    86.252699> 09:08:18.1764 [eInit] + (5) Tuxtxt
<    86.253105> 09:08:18.1768 [eInit] + (8) graphics acceleration manager
<    86.253649> 09:08:18.1774 [bcm] /dev/fb0 Function not implemented
<    86.254078> 09:08:18.1778 [eInit] + (9) Font Render Class
<    86.254391> 09:08:18.1781 [Font] Initializing lib...
<    86.254841> 09:08:18.1786 [Font] Loading fonts...
<    86.255225> 09:08:18.1789 [Font] Intializing font cache, using max. 4MB...
<    86.255663> 09:08:18.1794 [eInit] + (9) gLCD
<    86.256185> 09:08:18.1799 [eFbLCD] /dev/fb1: Function not implemented
<    86.256522> 09:08:18.1802 [eFbLCD] framebuffer /dev/fb1 not available
<    86.256872> 09:08:18.1806 [eDboxLCD] No oled0 or lcd0 device found!
<    86.257281> 09:08:18.1810 [eLCD] (132x64x8) buffer 0x8afb20 8448 bytes, stride 132
<    86.257599> 09:08:18.1813 [gLCDDC] resolution: 132x64x8 stride=132
<    86.257809> 09:08:18.1816 [eInit] + (9) GFBDC
<    86.258134> 09:08:18.1818 [fb] /dev/fb0 Function not implemented
<    86.258258> 09:08:18.1820 [fb] framebuffer not available
<    86.258352> 09:08:18.1821 [gFBDC] no framebuffer available
Segmentation fault
root@mutant2400:~#

 

[el bandido]

No framebuffer... Graphics.

Probably the best way out of this is to reload the image.

 

[yorkshirepudding]

Thank you for your reply.
I've reflashed this multiple times with no difference. I tried the latest version of the 6.6 branch too on the off-chance.
The USB stick has been used successfully for flashing before.
Each time it flashes it says Flashing completed.
I've also downloaded the images to a linux box and used that to copy to the USB stick in case Windows was causing a problem somehow.

 

[el bandido]

Verify again that the image you are trying to load is correct.

See if some of these telnet commands will return something that points to the real problem:

cat /proc/meminfo

grep -E 'MemTotal|MemFree|Buffers|Cached' /proc/meminfo

dmesg | grep -i bad

lsblk

 

[yorkshirepudding]

Thanks again for your persistence. Here is the output of those commands:

root@mutant2400:~# cat /proc/meminfo
MemTotal:        1119636 kB
MemFree:         1083292 kB
MemAvailable:    1047316 kB
Buffers:               0 kB
Cached:            18900 kB
SwapCached:            0 kB
Active:            15888 kB
Inactive:           6156 kB
Active(anon):       3208 kB
Inactive(anon):      120 kB
Active(file):      12680 kB
Inactive(file):     6036 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:        786432 kB
HighFree:         761632 kB
LowTotal:         333204 kB
LowFree:          321660 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          3152 kB
Mapped:             4608 kB
Shmem:               180 kB
Slab:               8016 kB
SReclaimable:       3408 kB
SUnreclaim:         4608 kB
KernelStack:         624 kB
PageTables:          264 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      559816 kB
Committed_AS:      42652 kB
VmallocTotal:     491512 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
root@mutant2400:~# grep -E 'MemTotal|MemFree|Buffers|Cached' /proc/meminfo
MemTotal:        1119636 kB
MemFree:         1083300 kB
Buffers:               0 kB
Cached:            18904 kB
SwapCached:            0 kB
root@mutant2400:~# dmesg | grep -i bad
root@mutant2400:~# lsblk
-bash: lsblk: command not found
root@mutant2400:~#

 

[yorkshirepudding]

I was curious about the last command not being found so dug deeper.

root@mutant2400:~# /bin/busybox --help
BusyBox v1.36.1 () multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
   or: busybox --list
   or: busybox --show SCRIPT
   or: function [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use and BusyBox
        will act like whatever it was invoked as.

Currently defined functions:
        [, [[, addgroup, adduser, ar, arch, arp, arping, ascii, ash, awk, base32, base64, basename, bc, blkid, bunzip2,
        bzcat, cat, chattr, chgrp, chmod, chown, chroot, chrt, chvt, clear, cmp, cp, cpio, crc32, cttyhack, cut, date,
        dc, dd, deallocvt, delgroup, deluser, depmod, devmem, df, diff, dirname, dmesg, dnsdomainname, dos2unix, du,
        dumpkmap, echo, egrep, eject, env, ether-wake, expr, factor, fatattr, fbset, fdisk, fgrep, find, flock, fsck,
        fstrim, fuser, getopt, getty, grep, groups, gunzip, gzip, halt, hdparm, head, hexdump, hexedit, hostname,
        hwclock, i2cdetect, i2cdump, i2cget, i2cset, i2ctransfer, id, ifconfig, ifdown, ifplugd, ifup, inetd, inotifyd,
        insmod, ionice, ip, ipneigh, kill, killall, killall5, klogd, less, link, ln, loadfont, loadkmap, logger,
        logname, logread, losetup, ls, lsattr, lsmod, lsof, lspci, lsusb, lzcat, md5sum, mdev, mesg, mkdir, mkfifo,
        mknod, mkswap, mktemp, modprobe, more, mount, mpstat, mv, nc, netstat, nice, nl, nohup, nologin, nproc,
        nslookup, ntpd, nuke, od, openvt, paste, patch, pgrep, pivot_root, poweroff, printf, pwd, rdate, rdev,
        readlink, readprofile, realpath, reboot, renice, reset, resize, resume, rev, rfkill, rm, rmdir, rmmod, route,
        run-init, run-parts, sed, seedrng, seq, setconsole, setfattr, setlogcons, setserial, setsid, sh, sha1sum,
        sha256sum, sha3sum, sha512sum, shred, shuf, sleep, sort, split, start-stop-daemon, stat, strings, stty,
        sulogin, svok, swapoff, swapon, switch_root, sync, sysctl, syslogd, tail, tar, taskset, tc, tee, telnet,
        telnetd, test, tftp, tftpd, time, timeout, top, touch, tr, tree, true, truncate, ts, tsort, tty, tunctl,
        udhcpc, uevent, umount, uname, uniq, unix2dos, unlink, unxz, unzip, uptime, users, usleep, vi, volname, watch,
        wc, which, who, whoami, whois, xargs, xxd, xzcat, yes, zcat
root@mutant2400:~# blkid
/dev/ubi0_0: UUID="29e83afc-b471-4cba-86a4-005bfbdac25b" TYPE="ubifs"
/dev/mtdblock2: UUID="781558294" TYPE="ubi"
/dev/sdb1: UUID="1b540e8e-c885-444e-b001-f73c6ef5f1e5" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="7ea4f877-688f-4bdd-9a92-833d776763d8"
/dev/sda1: LABEL_FATBOOT="OPENVIX" LABEL="OPENVIX" UUID="EAFE-3CB0" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b0c90a34-01"
root@mutant2400:~#

 

[yorkshirepudding]

Is there any way to determine if this is or isn't hardware failure?

I have taken a close look inside and can see no swollen capacitors, or any other evidence such as scorch marks. The hard drive makes noise (and I can access it over SSH). The splash screen is displayed so the graphics can't be totally dead. I'm at a loss to know what else I can try.

 

[abu baniaz]

Try flashing an older ViX image or try and OEA team image from a branch older than the same one that your current ViX is using. Or PLi.

 

[yorkshirepudding]

Thank you

Try flashing an older ViX image

The earliest I can find is 6.3 https://www.openvix.co.uk/index.php/downloads/mutant-images/hd2400/hd2400-openvix-archives/ which has no different result . Is there any other source for OpenVix images for Mut@nt HD2400?

...or try and OEA team image from a branch older than the same one that your current ViX is using

Where would I find this?

Or PLi.

I've tried all the available versions here with the same end result, except with this when flashing it alternates between "Flashing ..." and "hd2400", doesn't say "Flashing Completed"

 

[el bandido]

Try one of the PLi images in the link:
https://openpli.org/download/mutant/HD2400

 

[yorkshirepudding]

Try one of the PLi images in the link:
https://openpli.org/download/mutant/HD2400

Yes, that was the one I tried:

Or PLi.

I've tried all the available versions here with the same end result, except with this when flashing it alternates between "Flashing ..." and "hd2400", doesn't say "Flashing Completed"

I was wondering if there was anywhere else I should look but sounds like I might have exhausted all the options.

 

[abu baniaz]

Check OpenATV download site for a bootloader for your receiver.

 

[yorkshirepudding]

I've tried the bootloaders here:
https://www.openvix.co.uk/index.php/downloads/bootloaders/mutant-bootloaders/hd2400-bootloaders/

I understand images are different for different enigma2 images, but are the bootloaders different too?

I can't find any dedicated page for openATV bootloaders, but I found a few in the forum that had the exact same date as the bootloaders on the openvix site.

 

[el bandido]

Bootloaders could be thought of similar to the BIOS in Windows or other computers.

Your receiver Is or Was running Linux because you could communicate with it in telnet or terminal. So loading reloading bootloaders will probably not help because that part of the system seemed to be working. Actually, the rest of it looked OK to me, and I do not really understand why it is not working based on the outputs you have shown.