NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

DaForc3's avatar
DaForc3
Follower
Jul 02, 2017
Solved

When are we getting NEW firmware for the Nighthawk M1?

The M1 is currently suffering from...   Wireless stops responding Random reboots Battery sometimes refuses to charge Ethernet going to sleep Constant issues with usage meter Poor upload perfor...
Firmware
  • ArodiD's avatar
    ArodiD
    Nov 15, 2017

    Hi  Wiz_THS,

     

    The current implementation on 10.16.04.04 (MR1) is as follows:

    - MR1100 boots up and ethernet port is live for about 30 seconds

    - If Ethernet port detects something plugged in it will remain active

    - If Ethernet port detects nothing is plugged in it will disable the port to preserve battery life

     

    We are investigating ways of keeping the ethernet port active whilst still trying to preserve battery life.  These fixes could possibly be implemented in MR2 but not commited as yet.

     

    Kind Regards,


    ArodiD

MicW's avatar
MicW
Luminary
Aug 09, 2017
Apparently a new firmware came out yesterday. Though there is no information anywhere on what issues it addresses. You could try a manual check under Administration in settings and see if ti will update
Wiz_THS's avatar
Wiz_THS
Aspirant
Aug 10, 2017

My Netgear M1 is up to date and the Ethernet is still going to sleep :-(

 

Does anyone know an ETA to when this issue will be fixed?

  • MicW's avatar
    MicW
    Luminary
    Aug 10, 2017
    Strange, that was supposed to be fixed in firmware NTG9X50C_10.16.04.04. Is that the version you're running?
    • Wiz_THS's avatar
      Wiz_THS
      Aspirant
      Aug 10, 2017

      Correct. I am running NTG9X50C_10.16.04.04 and the ethernet still goes to sleep after a short period. Very annoying!

      • MicW's avatar
        MicW
        Luminary
        Aug 10, 2017

        Have you checked that power saving is turned off for your ethernet card in windows device manager? (assuming you are running windows). I can remember this sort of thing being an issue  way back, when windows would turn the ethernet off when it was idle. This may lead to a follow on where the modem may think there isn't anything using the ethernet and puts its own port to sleep as well.