1. Home
  2. Omega Talk
  3. [SOLVED] Kernel corrupted after factory reset

[SOLVED] Kernel corrupted after factory reset

  • D

    Been trying to reset Omega 2+ chip using factory button. But it appeared to become dead.
    Tried to do multiple recovery steps found across this forum, but didn't help. I tried to get debugging information from the serial port and here what I have:

    [   27.629441] =====================================================
[   27.635625] Channel 1 : Dirty = 780, False CCA = 0, Busy Time = 3909, Skip Channel = FALSE
[   27.644023] Channel 2 : Dirty = 652, False CCA = 0, Busy Time = 1623, Skip Channel = FALSE
[   27.652419] Channel 3 : Dirty = 668, False CCA = 0, Busy Time = 1426, Skip Channel = FALSE
[   27.660815] Channel 4 : Dirty = 684, False CCA = 0, Busy Time = 1454, Skip Channel = FALSE
[   27.669205] Channel 5 : Dirty = 700, False CCA = 0, Busy Time = 3033, Skip Channel = FALSE
[   27.677583] Channel 6 : Dirty = 1150, False CCA = 0, Busy Time = 3913, Skip Channel = FALSE
[   27.686065] Channel 7 : Dirty = 760, False CCA = 0, Busy Time = 1967, Skip Channel = FALSE
[   27.694461] Channel 8 : Dirty = 756, False CCA = 0, Busy Time = 1824, Skip Channel = FALSE
[   27.702857] Channel 9 : Dirty = 752, False CCA = 0, Busy Time = 316, Skip Channel = FALSE
[   27.711165] Channel 10 : Dirty = 748, False CCA = 0, Busy Time = 995, Skip Channel = FALSE
[   27.719554] Channel 11 : Dirty = 1000, False CCA = 0, Busy Time = 4141, Skip Channel = FALSE
[   27.728105] =====================================================
[   27.734296] Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 2
[   27.743036] Min Dirty = 652
[   27.745865] ExChannel = 0 , 0
[   27.748879] BW        = 20
[   28.551976] device eth0.1 entered promiscuous mode
[   28.556855] device eth0 entered promiscuous mode
[   28.588837] br-wlan: port 1(eth0.1) entered forwarding state
[   28.594681] br-wlan: port 1(eth0.1) entered forwarding state
[   30.588807] br-wlan: port 1(eth0.1) entered forwarding state
[   32.028929] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944
[   32.028929]
[   32.042988] Rebooting in 3 seconds..

    So, any recommendations about how to get the device back to life?

    0 M 1 Reply
  • M

    when u try to startup normal at which point it fails?

    have you tried to install new os from usb?

    0 D 1 Reply
  • D

    @Marc-André-Fleischmann When I started it the LED kept blinking as it supposes to do during ordinary boot and then stopped doing so, looked like dead.

    I haven't tried installing new OS from USB because I don't have one at this particular moment, however, I'd try that later today. Is there any other way to make it work without USD drive at this moment?

    0
  • M

    You can try to use the webbased installation. But then you need an ethernet expansion.

    When not try:
    https://docs.onion.io/omega2-docs/Firmware-Flashing-from-USB-storage.html

    0 D 1 Reply
  • D

    @Marc-André-Fleischmann, since i have Omega 2+, would that work with a microSD card?

    0
  • M

    With ethernet expansion try:
    https://docs.onion.io/omega2-docs/Firmware-Flashing-Web-Recovery.html

    better keep out anything except what is in description

    0 D 1 Reply
  • D

    @Marc-André-Fleischmann well, I don't have ethernet extension, because there was no need purchasing that one, thought.

    0
  • M

    Then you should use the USB option. And you can only use an USB storage. There is no option to use the microSD card.

    0 D 1 Reply
  • D

    @Marc-André-Fleischmann Hopefully, you were wrong. If you have Omega 2+ that has microSD card slot you can restore the firmware, just substitute "USD device" onto "microSD card". Going to write up an article.

    0
  • D

    The problem was solved. The device can be restored from a microSD card, see description: https://community.onion.io/topic/3019/how-to-fix-device-firmware-with-a-microsd-card

    0 G 1 Reply
  • G

    @Denys-Makogon said in [SOLVED] Kernel corrupted after factory reset:

    The problem was solved. The device can be restored from a microSD card, see description: https://community.onion.io/topic/3019/how-to-fix-device-firmware-with-a-microsd-card

    Sorry I'm afraid you are mistaken.
    Your How to fix device firmware with a microSD card description seems to be wrong.
    I think Omega2(+) can not be restored from a microSD card with @Colt-Burns's method.
    Omega 2+ USB Firmware Install after Brick.

    Apologies if I misunderstood something.
    Please let us know how did you mount the microSD card on UBoot.
    Please let us know how did you write the image to the Flash from that microSD card.
    A full (step by step 😉 log of your procedure would be nice.
    Thank you in advance..

    0 D 1 Reply
  • D

    @György-Farkas Okay. I did the following steps:

    Please let us know how did you write the image to the Flash from that microSD card.

    1. Took my microSD card and formatted, in FAT.
    2. Downloaded an image from an Onion Omega official firmware repository.
    3. Renamed a file to omega2.bin
    4. Moved omega2.bin to the microSD card.
    5. Mounted (physically) a card to its slot.
    6. Turned on Omega 2+ chip with pressed restore button.
    7. Picked restore from USB storage device.
    8. Voila, the device was updated and functions correctly.

    Please let us know how did you mount the microSD card on UBoot

    I didn't do that on my own. Just followed the steps I mentioned above.

    0 G 1 Reply
  • G

    @Denys-Makogon

    Probably you did not watch the UBoot messages after step #7 😉

    Option [2] selected.
    System Load Linux then write to Flash via USB Storage.
    Looking for a USB Storage.
    If suitable image is found on USB Storage writing to Flash will be attempted.
    U-Boot will look for a FAT file system.
    (Re)start USB...
    LOW LEVEL INIT USB0:
    Scanning bus 0 for devices...
    ...
    USB_STORAGE: 0 Storage Device(s) found
    No USB Storage found. No F/W upgrade from USB Storage will be attempted.

    After this your Omega2+ performed a normal boot.
    I think your kernel was not corrupted or you were able to fix it fully accidentally... 😉

    0 D 1 Reply
  • D

    @György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional.

    0 G 1 Reply
  • G

    You wrote:
    Omega2+, probably 0.1.10 b160

    ...
[   28.551976] device eth0.1 entered promiscuous mode
[   28.556855] device eth0 entered promiscuous mode
[   28.588837] br-wlan: port 1(eth0.1) entered forwarding state
[   28.594681] br-wlan: port 1(eth0.1) entered forwarding state
[   30.588807] br-wlan: port 1(eth0.1) entered forwarding state
[   32.028929] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944
[   32.028929]
[   32.042988] Rebooting in 3 seconds..

    I wrote in Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ... and a possible reason on 2017-02-05:
    Omega2+, 0.1.9 b150 (from 0.1.5 b130 to 0.1.9 b150 several FirmWares), without dock / with Arduino Dock 2

    ...
[   20.900878] device eth0.1 entered promiscuous mode
[   20.905758] device eth0 entered promiscuous mode
[   20.940478] br-wlan: port 1(eth0.1) entered forwarding state
[   20.946310] br-wlan: port 1(eth0.1) entered forwarding state
[   22.939289] br-wlan: port 1(eth0.1) entered forwarding state
[   24.809528] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944
[   24.809528] 
[   24.823293] Rebooting in 3 seconds..

    This Kernel panic is a known bug of the closed source MediaTek WiFi driver. Now we know it can not manage if there is a WiFi AP in the neighborhood with some Unicode character in its SSID.
    Onion @administrators deeply kept silent about this bug.

    It seems Onion's new WARP CORE driver (also closed source ???) can manage this situation.
    Unfortunately Onion @administrators do not say too much about this bug feature (as usual ;-).

    Since you did not mount the microSD card it is absolutely invisible for the bootloader (Das U-Boot).

    @Denys-Makogon said in [SOLVED] Kernel corrupted after factory reset:

    @György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional.

    Well... no one but you should know if this correct (or not 😉

    0
onion 43 reset 27 kernel panic 14 recovery mode 9
Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.