User Info
Welcome Guest.
Please login or register.
Did you miss your activation email?
September 26, 2018, 08:25 am

Login with username, password and session length
Home Forum Help Login Register   Search:     Advanced search
SatelliteHome - Canada's most knowledgeable satellite discussion forum  |  Support  |  AzBox miniMe American Edition  |  MiniMe not booting
« previous next »
Pages: 1 Go Down Print
Author Topic: MiniMe not booting  (Read 4044 times)
icen
Newbie
*
Offline Offline

Posts: 5

« on: April 18, 2015, 08:34 pm »


Hello,

I've been on f/w 2.05 for some time now but just recently I went to start up my receiver and it does not complete its boot cycle. When I attempt to start it, I see the "AzBox starting..." message, followed by the splash screen which shows "American edition by AzBox Americas". It then goes back
to just the plain "AzBox starting..." message for a while then it disappears completely and a black screen remains. At this point I cannot interact with it at all via the remote.

I am able to ping and telnet to the unit, however. I'm just not sure which steps to take to recover it. If a factory reset will help and is possible from a telnet session, I would gladly do so.

Any help would be appreciated.



Thanks,


    Erik
Logged
g17feedhunter
Jr. Member
**
Offline Offline

Posts: 93

« Reply #1 on: April 21, 2015, 12:12 pm »

I have found this before..

Couple things..

Try booting in safe mode, then booting in regular mode.

Step 1 - Hold the power button till it flashes, then hold down 1 on the remote constantly till it says booting in safe mode
Step 2 - Once it boots, reboot it, hold down the 0 until it says AZBOX Starting

if these do not work, get a USB stick, load the firmware on to the USB stick and boot in safe mode, once booted re-flash the firmware... worked for me..
Logged
icen
Newbie
*
Offline Offline

Posts: 5

« Reply #2 on: April 21, 2015, 12:24 pm »

I have found this before..

Couple things..

Try booting in safe mode, then booting in regular mode.

Step 1 - Hold the power button till it flashes, then hold down 1 on the remote constantly till it says booting in safe mode
Step 2 - Once it boots, reboot it, hold down the 0 until it says AZBOX Starting

if these do not work, get a USB stick, load the firmware on to the USB stick and boot in safe mode, once booted re-flash the firmware... worked for me..


Great, thanks for the suggestion, I will give it a try tonight and reply here afterwards.


    Erik
Logged
PwrSurge
AzBox Americas staff member
Administrator
*****
Offline Offline

Posts: 111


AzBox Americas
« Reply #3 on: April 21, 2015, 12:59 pm »

Hello,

I've been on f/w 2.05 for some time now but just recently I went to start up my receiver and it does not complete its boot cycle. When I attempt to start it, I see the "AzBox starting..." message, followed by the splash screen which shows "American edition by AzBox Americas". It then goes back
to just the plain "AzBox starting..." message for a while then it disappears completely and a black screen remains. At this point I cannot interact with it at all via the remote.

I am able to ping and telnet to the unit, however. I'm just not sure which steps to take to recover it. If a factory reset will help and is possible from a telnet session, I would gladly do so.

Any help would be appreciated.



Thanks,


    Erik

When you are booting your receiver, does the last channel that you were watching still have signal?  If it no longer has signal then the receiver may take longer to reboot as it attempts to tune in a non-existent carrier.  If you wait about 1 minute, the tuning attempt should timeout and the remote should respond again.

If you often have temporary channels in your list due to blind-scanning, you should change your Start Channel Setting to a fixed permanent channel by going to System settings -> Extended settings -> Start Channel Settings and turn from last Channel off.  Once this is done, select TV Channel from the same menu with the green key and choose the desired channel.  Always having the receiver boot to an active channel will prevent this issue from occurring.

Logged
icen
Newbie
*
Offline Offline

Posts: 5

« Reply #4 on: April 21, 2015, 01:04 pm »

When you are booting your receiver, does the last channel that you were watching still have signal?  If it no longer has signal then the receiver may take longer to reboot as it attempts to tune in a non-existent carrier.  If you wait about 1 minute, the tuning attempt should timeout and the remote should respond again.

If you often have temporary channels in your list due to blind-scanning, you should change your Start Channel Setting to a fixed permanent channel by going to System settings -> Extended settings -> Start Channel Settings and turn from last Channel off.  Once this is done, select TV Channel from the same menu with the green key and choose the desired channel.


Unfortunately it doesn't show any channel/signal detail whatsoever - and it's quite possible it was last left on a wild feed which no longer exists. I have left the receiver in that state for about 20 minutes and it hasn't responded. I will make that change in the System Settings menu when I am able to, though.


    Erik
Logged
PwrSurge
AzBox Americas staff member
Administrator
*****
Offline Offline

Posts: 111


AzBox Americas
« Reply #5 on: April 21, 2015, 01:44 pm »


Unfortunately it doesn't show any channel/signal detail whatsoever - and it's quite possible it was last left on a wild feed which no longer exists. I have left the receiver in that state for about 20 minutes and it hasn't responded. I will make that change in the System Settings menu when I am able to, though.


    Erik

What do you currently see on the screen?  Which color is the power button LED light?

If you are able to telnet to the unit, login with root as username then type in the dmesg command and paste the last 25 lines that you get.
Logged
icen
Newbie
*
Offline Offline

Posts: 5

« Reply #6 on: April 21, 2015, 10:40 pm »

What do you currently see on the screen?  Which color is the power button LED light?

If you are able to telnet to the unit, login with root as username then type in the dmesg command and paste the last 25 lines that you get.


Just got home to try it out - currently the screen is blank after trying to boot it up and the remote does not respond. The LED light is blue, and here is the output from the dmesg command (I grabbed more than 25 since some error messages appeared outside of that):


[   21.980000] JFFS2 notice: (293) check_node_data: wrong data CRC in data node at 0x02b795c4: read 0xf357f83b, calculated 0x894728f4.
[   25.750000] SMP865x manual blit 1
[   25.750000] New FB OSD resolution [1280:720] , virtual [1280:1440], bpp 32
[   25.780000] SMP865x: OSD: dst_surf = 8b7f9b58, size = 3686400
[   25.840000] SMP865x FB PAN: 0 0
[   27.150000] Chip Ver:{1}.{0}.{2}  API Ver:{1}.{0}.{7}  Patch Ver:{1}.{0}.{57}
[   27.760000] SMP865x: AUDIO SET_MIXER
[   29.130000] SMP865x audio: AC3
[   29.550000] SetOutMod: 1080i60
[   29.910000] Mode:   74175824, 1920,  540, 2200,  44,  88, 148, 0, 1125,  2,  5, 15, 0, VideoTiming_1920x1080i@59.94Hz, 1
[   29.910000]
[   29.910000] |||--  Applying output options - HDMI="NONE"[16:9](YCbCr 709), CAV="1080i59"[16:9](YCbCr 709), CVBS="NTSC_M"[16:9](YCbCr 601)  --|||
[   29.910000]
[   30.670000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/SLi.c:3044] ERROR(RM_NOT_SUPPORTED): SLi13T only supports EDID read!
[   30.670000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/hdcp.c:333] ERROR(RM_NOT_SUPPORTED): [HDCP] Can not read Bcaps/Bstatus!
[   30.680000]
[   30.680000] |||--  Applying output options - HDMI="HDMI_1080i60"[16:9](RGB 16..235), CAV="1080i60"[16:9](YCbCr 709), CVBS="NTSC_M"[16:9](YCbCr 601)  --|||
[   30.680000]
[   31.120000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/SLi.c:3044] ERROR(RM_NOT_SUPPORTED): SLi13T only supports EDID read!
[   31.120000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/hdcp.c:333] ERROR(RM_NOT_SUPPORTED): [HDCP] Can not read Bcaps/Bstatus!
[   31.430000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/SLi.c:3044] ERROR(RM_NOT_SUPPORTED): SLi13T only supports EDID read!
[   31.430000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/hdcp.c:333] ERROR(RM_NOT_SUPPORTED): [HDCP] Can not read Bcaps/Bstatus!
[   31.440000]
[   31.440000] |||--  Applying output options - HDMI="HDMI_1080i60"[16:9](RGB 16..235), CAV="1080i60"[16:9](YCbCr 709), CVBS="NTSC_M"[16:9](YCbCr 601)  --|||
[   31.440000]
[   31.880000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/SLi.c:3044] ERROR(RM_NOT_SUPPORTED): SLi13T only supports EDID read!
[   31.880000] [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/kernel/rmhdmi/src/hdcp.c:333] ERROR(RM_NOT_SUPPORTED): [HDCP] Can not read Bcaps/Bstatus!
[   63.420000] SMP865x: VIDEO SELECT SOURCE MEMORY
[   63.440000] SMP865x: VIDEO PLAY
[   63.440000] SMP865x STC PLAY
[   63.440000] SMP865x: VIDEO CONTINUE
[   63.440000] SMP865x: VIDEO CLEAR
[   63.460000] SMP865x STC STOP
[   63.470000] SMP865x: Video new PTS value 0
[   63.470000] SMP865x STC PLAY
[   63.620000] SMP865x: VIDEO STOP
[   63.620000] SMP865x STC STOP
[   63.620000] SMP865x: VIDEO SELECT SOURCE DEMUX
[  129.320000] em8xxx0 [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:885] Address with ID 0x001b0007 not found
[  135.310000] em8xxx0 [/work/novo/mrua_SMP8654F_3_11_1_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:885] Address with ID 0x001b0007 not found
[  145.440000] SMP865x: Audio open the buffer pools
[  145.440000] SMP865x: Audio DMA pool id = 0
[  145.460000] SMP865x: Video open the buffer pools
[  145.460000] SMP865x: Video DMA pool id = 1
[  145.460000] SMP865x: Demux[PVR] open the buffer pools
[  145.460000] SMP865x: Demux[PVR] DMA pool id = 2
[  145.460000] SMP865x: Demux[VTuner] open the buffer pools
[  145.460000] SMP865x: Demux[vTuner] DMA pool id = 3
[  145.460000] SMP865x: Init Sigma Demux Tasks
[  145.460000] TANGO3_DMX
[  145.460000] TANGO3_DMX
[  145.460000] TANGO3_DMX
[  145.460000] SMP865x: Init Sigma VCXO
[  145.460000] SMP865x: start kVcxoRegulate
[  145.460000] SMP865x: start kMonitorVideo
[  145.460000] SMP865x: start kTask1
[  145.460000] SMP865x: start kTask2
[  145.460000] SMP865x: start kTask3
[  207.570000] SMP865x: VIDEO SELECT SOURCE MEMORY
[  207.590000] SMP865x: VIDEO PLAY
[  207.600000] SMP865x STC PLAY
[  207.600000] SMP865x: VIDEO CONTINUE
[  207.600000] SMP865x: VIDEO CLEAR
[  207.610000] SMP865x STC STOP
[  207.620000] SMP865x: Video new PTS value 0
[  207.620000] SMP865x STC PLAY
[  207.770000] SMP865x: VIDEO STOP
[  207.770000] SMP865x STC STOP
[  207.770000] SMP865x: VIDEO SELECT SOURCE DEMUX
[  499.280000] ir raw data: 01 ce 5f 47 b8 55



Thanks,

    Erik
Logged
PwrSurge
AzBox Americas staff member
Administrator
*****
Offline Offline

Posts: 111


AzBox Americas
« Reply #7 on: April 22, 2015, 12:13 pm »

Please try the following:

1. In terminal, type the following command: poweroff

2. Once the power button LED light turns pink, unplug the power cord from the back of the receiver and wait 60 seconds.

3. Plug the power back on and see if the unit boots.  If not, issue the dmesg command in telnet again

4. If you still see the following line in DMESG output even after following the above steps then your main flash partition is corrupt and you need to reflash the firmware in safe mode in order to resolve this issue

Quote
JFFS2 notice: (293) check_node_data: wrong data CRC in data node at 0x02b795c4: read 0xf357f83b, calculated 0x894728f4.


Logged
icen
Newbie
*
Offline Offline

Posts: 5

« Reply #8 on: April 22, 2015, 09:14 pm »

Please try the following:

1. In terminal, type the following command: poweroff

2. Once the power button LED light turns pink, unplug the power cord from the back of the receiver and wait 60 seconds.

3. Plug the power back on and see if the unit boots.  If not, issue the dmesg command in telnet again

4. If you still see the following line in DMESG output even after following the above steps then your main flash partition is corrupt and you need to reflash the firmware in safe mode in order to resolve this issue


Just tried this and still had the CRC error, so I followed g17feedhunter's advice about holding the power button, waiting for it to flash then press and hold 1. I was then able to get it to start in safe mode and re-flash 2.05. All seems well,
the receiver is now back up and running normally. Thanks to you both!


    Erik
Logged
Pages: 1 Go Up Print 
« previous next »
 

SMF 2.0.15 | SMF © 2017, Simple Machines
Simple Audio Video Embedder
SimplePortal 2.3.6 © 2008-2014, SimplePortal
| Theme by nesianstyles | Buttons by Andrea