New Asus GT-AX6000 Log

[EH53]

I just purchased a new GT-AX6000 from Amazon and noticed in the log that there are entries from May 5 that reference Merlin. Is this normal or did Amazon sell me a refurbished router? Here is an example from the log:

May 5 05:05:15 kernel: Verify that the firmware has been loaded with good CRC: OK
May 5 05:05:15 kernel: Firmware loading completed successfully: v2.2.8
May 5 05:05:15 kernel: Adjusted QGPHY: qphy_ctrl=0x00041000 ext_pwr_down=0x0
May 5 05:05:15 kernel: ^[[0;30;102m=== Start of 10G Active Ethernet Initialization for core 0 port 0 ===^[[0m
May 5 05:05:15 kernel: --- Step 0 powerup/reset sequence of core #0 at address 6
May 5 05:05:15 kernel: INFO MerlinSupport::_merlin_core_power_op: assert IDDQ|RESET|REFCLK_RESET to power down Serdes
May 5 05:05:15 kernel: INFO MerlinSupport::_merlin_core_power_op(): START powering up Merlin Core #0 with PRTAD = 6, ln_offset_stap = 0
May 5 05:05:15 kernel: INFO MerlinSupport::_merlin_core_power_op(): Disable IDDQ
May 5 05:05:15 kernel: INFO MerlinSupport::_merlin_core_power_op(): Provide a delay of 1ms after IDDQ is de-asserted
May 5 05:05:15 kernel: INFO MerlinSupport::_merlin_core_power_op(): Disable serdes_reset and refclk_reset
May 5 05:05:15 kernel: Toggle Serdes Core #0 PMD and uC reset.
May 5 05:05:15 kernel: INFO MerlinSupport::merlin_core_init(): END. Core #0 with PRTAD = 6, ln_offset_stap = 0
May 5 05:05:15 kernel: MerlinSupport::merlin16_serdes_init(): Step 4. Assert micro reset
May 5 05:05:15 kernel: MerlinSupport::merlin16_serdes_init(): Step 6. Micro code load and verify
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): INFO: Start to download firmware to core # 0
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): Checking init_done initial value passed...
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): INFO: wait 8192 comclks for ~32KB code ram initialization...
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): Checking init_done passed ...
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): INFO: wait 1024 comclks for 3KB data ram initialization...
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): Checking init_done passed ...
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): begin writing firmware to the program ram ...
May 5 05:05:15 kernel: #################################################################################
May 5 05:05:15 kernel: Done.
May 5 05:05:15 kernel: MerlinSupport::merlin_load_firmware(): end writing firmware to the program ram ...
May 5 05:05:15 kernel: MerlinSupport::merlin16_serdes_init(): Step 6.1 De-assert micro reset
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_active(): wait 50us comclks for micro to be up...
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_active(): Checking uc_active passed ...
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_active(): micro is ready for command ...
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_crc_verify(): micro is ready for command ...
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_crc_verify(): DSC ready for command is not working; SerDes is probably reset!!! reset_state = 7
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_crc_verify(): uCode CRC Verify ...
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_crc_verify(): wait 500us for crc verify to be done ...
May 5 05:05:15 kernel: already waiting 1 ms
May 5 05:05:15 kernel: already waiting 2 ms
May 5 05:05:15 kernel: already waiting 3 ms
May 5 05:05:15 kernel: already waiting 4 ms
May 5 05:05:15 kernel: already waiting 5 ms
May 5 05:05:15 kernel: already waiting 6 ms
May 5 05:05:15 kernel: already waiting 7 ms
May 5 05:05:15 kernel: MerlinSupport::merlin_wait_uc_crc_verify(): CRC verification passed ...
May 5 05:05:15 kernel: INFO MerlinSupport::merlin16_serdes_init(): END Merlin Initialization procedure
May 5 05:05:15 kernel: MerlinSupport::merline_speed_set_core(): Step 7 Config Speed to 2
May 5 05:05:15 kernel: No option found for: "-d ML_C_VCO_10P3125", added default value 0 in index 9

 

[ColinTaylor]

It's normal.

The 5th May is the default date the router has when it's powered on and hasn't yet obtained the correct date/time from the internet.

The Merlin reference is a Broadcom chipset feature and has nothing to do with Merlin's third party firmware.

 

[EH53]

It's normal.

The 5th May is the default date the router has when it's powered on and hasn't yet obtained the correct date/time from the internet.

The Merlin reference is a Broadcom chipset feature and has nothing to do with Merlin's third party firmware.

Thanks for the quick reply. I am glad I don't need to return the router as it is running really well so far!