What's new

Beta Asuswrt-Merlin 386.5 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Last night when I could not sleep (one of those nights when your mind is racing), I decided to go through the logs. One thing I noticed is below.
Are these normal or anything to worry about?

May 5 01:05:03 kernel: Bad block table found at page 131008, version 0x01
May 5 01:05:03 kernel: Bad block table found at page 130944, version 0x01
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000002ea0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x0000032e0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000003a20000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000004160000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000006640000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000006fc0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x00000fba0000
 
Last night when I could not sleep (one of those nights when your mind is racing), I decided to go through the logs. One thing I noticed is below.
Are these normal or anything to worry about?

May 5 01:05:03 kernel: Bad block table found at page 131008, version 0x01
May 5 01:05:03 kernel: Bad block table found at page 130944, version 0x01
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000002ea0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x0000032e0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000003a20000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000004160000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000006640000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x000006fc0000
May 5 01:05:03 kernel: nand_read_bbt: bad block at 0x00000fba0000
Can you confirm that this is something that has only appeared since installing this beta firmware?
 
@kernol...do you use the default settings for cake and do you use the cake add on as well?

I did play with the Cake add-on some time back - but found I didn't need it.
I guess settings will vary a lot - but the below image is my current setup with PPPoE fibre connection at 100 up and 200 down.
I used to set speed at 5% discount to actual rated speed - but given the built in reduction that cake applies to whatever you specify - full speed setting works a treat for me :D ...

cake-settings.png
 
Can you confirm that this is something that has only appeared since installing this beta firmware?
Colin, Unfortunately I cannot, or at least I do not remember seeing. If it helps, these were noticed after a reboot. Do you see this in your logs?

Other than this, router is working very well.
 
Colin, Unfortunately I cannot, or at least I do not remember seeing. If it helps, these were noticed after a reboot. Do you see this in your logs?

Other than this, router is working very well.
I don't see those messages because I don't have the same model router as you. If you do a forum search you will see these sorts of messages have been reported in the past. If you suspect these messages are caused by the beta firmware I suggest you backup your current configuration, reinstall 386.4, do a WPS reset and then restore your configuration. Then check whether the messages are still present. If not present, update to this beta and check again.
 
I don't see those messages because I don't have the same model router as you. If you do a forum search you will see these sorts of messages have been reported in the past. If you suspect these messages are caused by the beta firmware I suggest you backup your current configuration, reinstall 386.4, do a WPS reset and then restore your configuration. Then check whether the messages are still present. If not present, update to this beta and check again.
Colin, you are right. I did a search and found an old thread from 2020 where @RMerlin himself quoted as : "That's perfectly normal, and nothing new - bad block tables have been used since Asus switched to NAND, with the RT-AC66U back in 2012"
So guess al is normal. Thanks.
 
Wow! I did a dirty upgrade on my AX88u (long shot) after I had multiple issues today.
I've installed Entware with multiple addons.
My network is mach more stable. I'm surprise after lots of issues on last .4 alpha / bèta builds.
 
Thanks Eric! Just installed the 386.5_beta2 build to my AX86U.

Btw, just wanna ask is there a way to save the amtm add ons installed if going to upgrade the firmware?

I know the a "must" way is to hard reset the router after the each flash.

Thanks guys!
 
Everyday at around 11AM Lisbon time, I get the log spammed with this and internet goes down.
Solution is reboot the router.


Code:
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Mar  1 11:00:25 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Mar  1 11:00:25 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
 
What's this for? I noticed that roaming assistant is not functioning properly. And even sometimes all of my devices are connected to the Router and nothing else to the node.

1646135843182.png
 
Really excited about the final release of this one, going to take a day off work so I can install it in peace without the family complaints.
 
Thanks Eric! Just installed the 386.5_beta2 build to my AX86U.

Btw, just wanna ask is there a way to save the amtm add ons installed if going to upgrade the firmware?

I know the a "must" way is to hard reset the router after the each flash.

Thanks guys!
No need to reset after upgrade to beta 2. It is working well for me as is.
 
Everyday at around 11AM Lisbon time, I get the log spammed with this and internet goes down.
Solution is reboot the router.


Code:
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Mar  1 11:00:24 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Mar  1 11:00:25 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Mar  1 11:00:25 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0

I mentioned the same thing a few days ago., back on post #52. I wasn't sure if it was because of the new version, or if because of the new version I was looking at my logs more and noticed it.

Our RT-AC86Us are getting old and maybe starting to wear out? The thought was that the flash has some bad blocks, unless the bcm63_nand code has changed? Just a guess.
 
I mentioned the same thing a few days ago., back on post #52. I wasn't sure if it was because of the new version, or if because of the new version I was looking at my logs more and noticed it.

Our RT-AC86Us are getting old and maybe starting to wear out? The thought was that the flash has some bad blocks, unless the bcm63_nand code has changed? Just a guess.
This started on this new version.
And even I don't look at logs, the internet goes down and I have to reboot, so...

I don't have a guess
 
Thanks Eric! Just installed the 386.5_beta2 build to my AX86U.

Btw, just wanna ask is there a way to save the amtm add ons installed if going to upgrade the firmware?

I know the a "must" way is to hard reset the router after the each flash.

Thanks guys!
Can't you just "safely remove usb" from gui then flash the RMerlin fw?
That's what works for me. Although, I do a full reset at each fw release.
Beta working well in The Griswald environment, Thank You RMerlin!
 
Last edited:
@kernol...do you use the default settings for cake and do you use the cake add on as well?
There is utility in adding the add-on in addition to enabling the Merlin-built-in version of Cake?
 
Finally to some action on my two GT-AXE11000's. BTW...no way will the AXE11000's remain in a AiMesh connection, will drop same day after joining. My other units of different models all have stayed in the AiMesh, never dropped. I will log this as an issue with ASUS Technical support.

Taking one AXE11000 out of AiMesh, did a WPS button hold down and power on to wipe the unit with 386.5 Beta1 installed. On power up, followed the advanced setting process. At the panel to setup Wireless, if you selected you didn't want separate 2.4/5/6GHz bands, you still had to setup two SSID's, one for 2.4&5GHz and the other for 6GHz. I noted later on the GUI panel for Wireless, you then could define one SSID for all three bands, as per picture.
1646164422113.png

I have used "Smart Connect" for like two years and been very successful with it for my 30-40 devices in the house, from 15yrs old to current. Some devices like FEIT smart lightbulbs, LaCrosse clocks do need a defined 2.4GHz band, which I do via the Guest Network.

The WiFi Survey worked for 2.4GHz band. Didn't work for the 5 & 6GHz bands.
1646165453003.png


Unable to get my Lenovo T480 with the Intel AX210 6GHz capable card to actually connect at 6GHz, best was 5GHz. Will look at this in coming days on forums.
1646165998877.png


Edit to place in values on speed thruput: Note the GT-AXE11000 is faster around the GUI panels as I did the config setup, then the RT-AX88U it's to replace. Also for my laptop, the wireless thruput tests are about faster..was 450-500Mb/s now 700-750MB/s in my test setup and now running the main house setup. I primarily use www.nperf.com for these quick tests.

Also for ASUS support is to get the DST end day correct for GMT-05:00. Should be 1st weekend in Nov. Been broke for at least twelve months, I'll get it logged with ASUS support.
1646164778348.png
 
Last edited:
Also for ASUS support is to get the DST end day correct for GMT-05:00. Should be 1st weekend in Nov. Been broke for at least twelve months, I'll get it logged with ASUS support.
View attachment 39916
Personally, I wouldn't bother even telling Asus about the DST issues: it has become clear that many manufacturers (Asus included) don't even bother trying to correlate time zones with (likely) corresponding DST start and end dates, as those are like shifting sands in many parts of the world. Frankly, I don't blame them, and it is often left up to the users to look up and correct these dates as needed for our particular country/state/region.
 
Personally, I wouldn't bother even telling Asus about the DST issues: it has become clear that many manufacturers (Asus included) don't even bother trying to correlate time zones with (likely) corresponding DST start and end dates, as those are like shifting sands in many parts of the world. Frankly, I don't blame them, and it is often left up to the users to look up and correct these dates as needed for our particular country/state/region.
Asus does try, they even moved the DST database into a file that is dynamically downloaded from their web server, allowing them to regularly update it as needed. However if you have already configured the timezone with a previously incorrect start/end time, the updated database will not correct this. The user has to change to a different timezome, then switch back to the correct timezone - this will update the saved start/end time in nvram.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top