<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic [AP3610] ERROR: Cannot boot either kernel image, dropping to interactive shell. in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36276#M1768</link>
    <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
I need for recovery a AP3610 with kernel error. Does anyone know how I can fix this error? Some steps for getting the firmware image on the access point would be nice to have&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Chris&lt;BR /&gt;
&lt;BR /&gt;
U-Boot 1.2.0.07-dirty (Sep 23 2015 - 14:24:57)&lt;BR /&gt;
&lt;BR /&gt;
Primary Image&lt;BR /&gt;
&lt;BR /&gt;
DRAM:  128 MB&lt;BR /&gt;
Flash: 16 MB&lt;BR /&gt;
In:    serial&lt;BR /&gt;
Out:   serial&lt;BR /&gt;
Err:   serial&lt;BR /&gt;
Net:   eth0&lt;BR /&gt;
Hit any key to stop autoboot:  0&lt;BR /&gt;
### JFFS2 loading 'boot_kernel.img2' to 0x80400000&lt;BR /&gt;
Scanning JFFS2 FS: . done.&lt;BR /&gt;
### JFFS2 load complete: 2979 bytes loaded to 0x80400000&lt;BR /&gt;
&lt;BR /&gt;
## Checking Image at 80400000 ...&lt;BR /&gt;
   Image Name:   Boot ROM Script&lt;BR /&gt;
   Created:      2010-06-21  17:46:19 UTC&lt;BR /&gt;
   Image Type:   PowerPC Linux Script (uncompressed)&lt;BR /&gt;
   Data Size:    2915 Bytes =  2.8 kB&lt;BR /&gt;
   Load Address: 00000000&lt;BR /&gt;
   Entry Point:  00000000&lt;BR /&gt;
   Verifying Checksum ... OK&lt;BR /&gt;
## Executing script at 80400000&lt;BR /&gt;
check for watchdog, limit=3...&lt;BR /&gt;
check for reset by watchdog...&lt;BR /&gt;
no watchdog...&lt;BR /&gt;
bSaveEnviron=0 image_order=primary secondary&lt;BR /&gt;
### JFFS2 loading 'primary.gz.uImage' to 0x80500000&lt;BR /&gt;
### JFFS2 load complete: 5352637 bytes loaded to 0x80500000&lt;BR /&gt;
ready to boot kernel, starting watchdog...&lt;BR /&gt;
## Booting image at 80500000 ...&lt;BR /&gt;
   Image Name:   Linux Kernel Image (LZMA)&lt;BR /&gt;
   Created:      2015-12-02  17:31:56 UTC&lt;BR /&gt;
   Image Type:   MIPS Linux Kernel Image (uncompressed)&lt;BR /&gt;
   Data Size:    5352573 Bytes =  5.1 MB&lt;BR /&gt;
   Load Address: 84000000&lt;BR /&gt;
   Entry Point:  8400239c&lt;BR /&gt;
   Verifying Checksum ... Bad Data CRC&lt;BR /&gt;
boot failed - stopped watchdog&lt;BR /&gt;
### JFFS2 loading 'secondary.gz.uImage' to 0x80500000&lt;BR /&gt;
### JFFS2 load complete: 5352801 bytes loaded to 0x80500000&lt;BR /&gt;
ready to boot kernel, starting watchdog...&lt;BR /&gt;
## Booting image at 80500000 ...&lt;BR /&gt;
   Image Name:   Linux Kernel Image (LZMA)&lt;BR /&gt;
   Created:      2015-09-23  18:24:46 UTC&lt;BR /&gt;
   Image Type:   MIPS Linux Kernel Image (uncompressed)&lt;BR /&gt;
   Data Size:    5352737 Bytes =  5.1 MB&lt;BR /&gt;
   Load Address: 84000000&lt;BR /&gt;
   Entry Point:  8400239c&lt;BR /&gt;
   Verifying Checksum ... Bad Data CRC&lt;BR /&gt;
boot failed - stopped watchdog&lt;BR /&gt;
ERROR: Cannot boot either kernel image, dropping to interactive shell.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 13 Apr 2016 18:37:00 GMT</pubDate>
    <dc:creator>n_n__n_n_</dc:creator>
    <dc:date>2016-04-13T18:37:00Z</dc:date>
    <item>
      <title>[AP3610] ERROR: Cannot boot either kernel image, dropping to interactive shell.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36276#M1768</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
I need for recovery a AP3610 with kernel error. Does anyone know how I can fix this error? Some steps for getting the firmware image on the access point would be nice to have&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Chris&lt;BR /&gt;
&lt;BR /&gt;
U-Boot 1.2.0.07-dirty (Sep 23 2015 - 14:24:57)&lt;BR /&gt;
&lt;BR /&gt;
Primary Image&lt;BR /&gt;
&lt;BR /&gt;
DRAM:  128 MB&lt;BR /&gt;
Flash: 16 MB&lt;BR /&gt;
In:    serial&lt;BR /&gt;
Out:   serial&lt;BR /&gt;
Err:   serial&lt;BR /&gt;
Net:   eth0&lt;BR /&gt;
Hit any key to stop autoboot:  0&lt;BR /&gt;
### JFFS2 loading 'boot_kernel.img2' to 0x80400000&lt;BR /&gt;
Scanning JFFS2 FS: . done.&lt;BR /&gt;
### JFFS2 load complete: 2979 bytes loaded to 0x80400000&lt;BR /&gt;
&lt;BR /&gt;
## Checking Image at 80400000 ...&lt;BR /&gt;
   Image Name:   Boot ROM Script&lt;BR /&gt;
   Created:      2010-06-21  17:46:19 UTC&lt;BR /&gt;
   Image Type:   PowerPC Linux Script (uncompressed)&lt;BR /&gt;
   Data Size:    2915 Bytes =  2.8 kB&lt;BR /&gt;
   Load Address: 00000000&lt;BR /&gt;
   Entry Point:  00000000&lt;BR /&gt;
   Verifying Checksum ... OK&lt;BR /&gt;
## Executing script at 80400000&lt;BR /&gt;
check for watchdog, limit=3...&lt;BR /&gt;
check for reset by watchdog...&lt;BR /&gt;
no watchdog...&lt;BR /&gt;
bSaveEnviron=0 image_order=primary secondary&lt;BR /&gt;
### JFFS2 loading 'primary.gz.uImage' to 0x80500000&lt;BR /&gt;
### JFFS2 load complete: 5352637 bytes loaded to 0x80500000&lt;BR /&gt;
ready to boot kernel, starting watchdog...&lt;BR /&gt;
## Booting image at 80500000 ...&lt;BR /&gt;
   Image Name:   Linux Kernel Image (LZMA)&lt;BR /&gt;
   Created:      2015-12-02  17:31:56 UTC&lt;BR /&gt;
   Image Type:   MIPS Linux Kernel Image (uncompressed)&lt;BR /&gt;
   Data Size:    5352573 Bytes =  5.1 MB&lt;BR /&gt;
   Load Address: 84000000&lt;BR /&gt;
   Entry Point:  8400239c&lt;BR /&gt;
   Verifying Checksum ... Bad Data CRC&lt;BR /&gt;
boot failed - stopped watchdog&lt;BR /&gt;
### JFFS2 loading 'secondary.gz.uImage' to 0x80500000&lt;BR /&gt;
### JFFS2 load complete: 5352801 bytes loaded to 0x80500000&lt;BR /&gt;
ready to boot kernel, starting watchdog...&lt;BR /&gt;
## Booting image at 80500000 ...&lt;BR /&gt;
   Image Name:   Linux Kernel Image (LZMA)&lt;BR /&gt;
   Created:      2015-09-23  18:24:46 UTC&lt;BR /&gt;
   Image Type:   MIPS Linux Kernel Image (uncompressed)&lt;BR /&gt;
   Data Size:    5352737 Bytes =  5.1 MB&lt;BR /&gt;
   Load Address: 84000000&lt;BR /&gt;
   Entry Point:  8400239c&lt;BR /&gt;
   Verifying Checksum ... Bad Data CRC&lt;BR /&gt;
boot failed - stopped watchdog&lt;BR /&gt;
ERROR: Cannot boot either kernel image, dropping to interactive shell.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Apr 2016 18:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36276#M1768</guid>
      <dc:creator>n_n__n_n_</dc:creator>
      <dc:date>2016-04-13T18:37:00Z</dc:date>
    </item>
    <item>
      <title>RE: [AP3610] ERROR: Cannot boot either kernel image, dropping to interactive shell.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36277#M1769</link>
      <description>You should contact GTAC for assistance, the unit will need to be replaced or repaired based on your contract agreement (if any) with Extreme. &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/Return-Material-Authorization-RMA-Process-and-FAQ" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/Return-Material-Authorization-RMA-Process-...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Apr 2016 19:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36277#M1769</guid>
      <dc:creator>Doug</dc:creator>
      <dc:date>2016-04-13T19:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: [AP3610] ERROR: Cannot boot either kernel image, dropping to interactive shell.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36278#M1770</link>
      <description>We've got the same error on multiple AP3705 and managed to solve this issue.&lt;BR /&gt;
When you get to the interactive shell (console), you can logon with admin, pwd= new2day&lt;BR /&gt;
Here you can list the files present in you AP.&lt;BR /&gt;
In our case we saw following list by using the command 'ls':&lt;BR /&gt;
 drwxr-xr-x       0 Thu Jan 01 00:00:41 1970 var&lt;BR /&gt;
 drwxr-xr-x       0 Thu Jan 01 00:00:25 1970 home&lt;BR /&gt;
 -rw-r--r--    4142 Thu Jan 01 00:00:28 1970 confData.bin&lt;BR /&gt;
 -rw-r--r-- 2628118 Thu Jan 01 00:03:36 1970 diag.gz.uImage&lt;BR /&gt;
 -rwxr-xr-x    4442 Thu Jan 01 00:00:27 1970 v2_confData.bin&lt;BR /&gt;
 -rw-r--r--    2992 Fri Nov 30 18:31:15 2012 boot_kernel.img2&lt;BR /&gt;
 -rw-r--r--    2992 Fri Nov 30 18:31:15 2012 boot_kernel.bak2&lt;BR /&gt;
 -rw-r--r-- 5228994 Wed May 21 09:41:14 2014 primary.gz.uImage&lt;BR /&gt;
 -rw-r--r-- 4974535 Thu Jan 01 00:02:34 1970 secondary.gz.uImage&lt;BR /&gt;
&lt;BR /&gt;
You can load the secondary image into memory:&lt;BR /&gt;
	fsload secondary.gz.uImage&lt;BR /&gt;
And boot the image that is now loaded in memory:&lt;BR /&gt;
	bootm&lt;BR /&gt;
&lt;BR /&gt;
After two bootcycles, the AP booted with the stock image and was up and running.&lt;BR /&gt;
I recommend to upgrade your AP with your controller afterwards</description>
      <pubDate>Wed, 21 Aug 2019 19:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3610-error-cannot-boot-either-kernel-image-dropping-to/m-p/36278#M1770</guid>
      <dc:creator>iT-eEg</dc:creator>
      <dc:date>2019-08-21T19:42:00Z</dc:date>
    </item>
  </channel>
</rss>

