- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
M4300-52g kernel not found
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
M4300-52g kernel not found
I have a M4300-52g and when I boot I get this. It never gets to the "checking for application" so I can't seem to reset it or load any new firmare. Only the OOB port seems to be working, none of hte other network ports will.
"
Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Saving Environment to SPI Flash...
SF: Detected MX25L25635E with page size 4 KiB, total 32 MiB
Erasing SPI flash...Writing to SPI flash...done
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
ERROR: Ethernet external port not connected
at bcmiproc_eth.c:125/bcmiproc_eth_open()
Wrong Image Format for bootm command
ERROR: can't get kernel image!"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: M4300-52g kernel not found
IMHO definitely a case for the Netgear support.
Remotely guessing, some issues caused by a variable wrongly set in the u-boot bootloader (which you may or may not be able to address yourself) or issues in the flash memory that the firmware tries to boot from.
What you could try is to stop regular startup and enter the boot loader when connected over serial or the serial-over-usb console (using a Mini USB to USB A cable). You have to hit Q at a certain point when the switch reboots or gets powered on. (See: https://kb.netgear.com/30326/M4300-How-do-I-recover-the-password-using-the-boot-menu)
There should is an option to boot from the backup image which might help in your case. Otherwise there is a way of loading software through USB or XMODEM but at that point I'd really get in touch with Netgear's support.