What's new

[Alpha][MU-MIMO] Early preview of 380.59

  • 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!

Thanks for the reply. One more question :) Do you think that these issues with 380.x and the RT-AC68 have to do with the binary components or the code?

If you're referring to the bug involving the 2.4 GHz band and NAT acceleration, no, it was a bug that Asus addressed with 380_2695.
 
updated ac68u to alpha 1 and had issue with usb thumbdrive. The drive won't mount and get the following in logs

Apr 6 22:32:09 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 1
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 2
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 6 22:32:09 kernel: scsi2 : usb-storage 1-1:1.0
Apr 6 22:32:10 kernel: scsi 2:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
Apr 6 22:32:10 kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] 30375936 512-byte logical blocks: (15.5 GB/14.4 GiB)
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Write Protect is off
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: sda: sda1 < sda5 >
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Attached SCSI removable disk
Apr 6 22:32:10 hotplug[17920]: USB /dev/sda5(ntfs) failed to mount at the first try!
Apr 6 22:32:10 usb: USB /dev/sda5(ntfs) failed to mount At the first try!
Apr 6 22:32:11 kernel: tntfs: disagrees about version of symbol module_layout
Apr 6 22:32:11 syslog: USB /dev/sda5(ntfs) failed to mount at the first try!
Apr 6 22:32:11 usb: USB /dev/sda5(ntfs) failed to mount At the first try!
Apr 6 22:32:11 kernel: tntfs: disagrees about version of symbol module_layout

Removed drive, rebooted device, reinserted drive, all produced same log. I even re-partitioned drive and reformatted it. Was not an issue in 380.58 and prior.
 
i flashed RT-AC68U_380.59_alpha1-g26b553b firmware....IPTV working, all scripts working.....this is for now, about two hours of testing.....great job done as allways @RMerlin.....:)

i have online this version 2 days and have to post here that i not have any problems with it....iptv over udpxy working again(380.58 didn`t), using also entware, openvpn,pixelserv-tls,ab-solution,dnscrypt-proxy and all going well....all good feedback from me.....
 
updated ac68u to alpha 1 and had issue with usb thumbdrive. The drive won't mount and get the following in logs

Apr 6 22:32:09 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 1
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 2
Apr 6 22:32:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Apr 6 22:32:09 kernel: scsi2 : usb-storage 1-1:1.0
Apr 6 22:32:10 kernel: scsi 2:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
Apr 6 22:32:10 kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] 30375936 512-byte logical blocks: (15.5 GB/14.4 GiB)
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Write Protect is off
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: sda: sda1 < sda5 >
Apr 6 22:32:10 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 6 22:32:10 kernel: sd 2:0:0:0: [sda] Attached SCSI removable disk
Apr 6 22:32:10 hotplug[17920]: USB /dev/sda5(ntfs) failed to mount at the first try!
Apr 6 22:32:10 usb: USB /dev/sda5(ntfs) failed to mount At the first try!
Apr 6 22:32:11 kernel: tntfs: disagrees about version of symbol module_layout
Apr 6 22:32:11 syslog: USB /dev/sda5(ntfs) failed to mount at the first try!
Apr 6 22:32:11 usb: USB /dev/sda5(ntfs) failed to mount At the first try!
Apr 6 22:32:11 kernel: tntfs: disagrees about version of symbol module_layout

Removed drive, rebooted device, reinserted drive, all produced same log. I even re-partitioned drive and reformatted it. Was not an issue in 380.58 and prior.

Exactly the same problem here on my 2tb WD drive but I didn't do a reset so full testing wasn't done.

Reverted to last stable and the drive was mounted fine.

By the looks of it there's something up with the Tuxera NTFS module.

Apr 6 22:32:11 kernel: tntfs: disagrees about version of symbol module_layout
 
I have a rt-ac3100 and alpha 2 did not work well. After updating from .58 it locked up just after it finished loading the new firmware. Had to hold the rest button while it booted up. It finally booted, I did a factory reset and the 2.4 band did not work. My slingbox connects to that band and it saw it but it couldn't connect to it. It was really late so I didn't look at any log files. I reloaded .58 and everything works now.
 
I have a rt-ac3100 and alpha 2 did not work well. After updating from .58 it locked up just after it finished loading the new firmware. Had to hold the rest button while it booted up. It finally booted, I did a factory reset and the 2.4 band did not work. My slingbox connects to that band and it saw it but it couldn't connect to it. It was really late so I didn't look at any log files. I reloaded .58 and everything works now.

3100 here and I had no such issues you describe loading or using Alpha 2 so far it's been running fine. :)
 
Hi,
I'm using Merlin 380.59 A2
It's working fine so far without any issues I can see
Thank you
 
3100 here and I had no such issues you describe loading or using Alpha 2 so far it's been running fine. :)
It was weird. That was the first problem I have had since the first day I bought it back in November. This router and Merlin's firmware are awesome.
 
It was weird. That was the first problem I have had since the first day I bought it back in November. This router and Merlin's firmware are awesome.

Agree love the 3100 best router I ever spend money on. And yes having Merlin just makes it even better. :D:)
 
Alpha 2 working really well so far on my AC3100. I have noticed one thing though Merlin. I have a couple PS4's that play online, and I use UPnP with them, which is working fine. The thing I noticed is the system log port forwarding section, isn't showing me using any ports actively under the UPnP section. Which I know for sure is actively using a couple ports. I do have some port forwarding rules, and they're properly showing up, just not the UPnP ports.
 
Alpha 2 working really well so far on my AC3100. I have noticed one thing though Merlin. I have a couple PS4's that play online, and I use UPnP with them, which is working fine. The thing I noticed is the system log port forwarding section, isn't showing me using any ports actively under the UPnP section. Which I know for sure is actively using a couple ports. I do have some port forwarding rules, and they're properly showing up, just not the UPnP ports.
Same here on the RT-AC88U. Reverted back to Alpha 1 and the port forwarding log populates UPnP ports properly.
 
Going to try Alpha 2 for my AC-87u tonight and see if it could finally solve the Android 5GHz battery drain issue :)
 
All these successful review makes my waiting for official 380.59 so much more unbearable!!!!
 
Alpha2 seems to be incompatible with the Astrill Router Applet (which is better than the standard OpenVPN client because it includes an Accelerator). I tested on the AC3200U but can test on the AC88U as well.

I have been using Merlin and the Astrill Router Applet for years - and have never had this problem. It is unable to load the astrill.asp file.
 
Just upgraded my 87U from 380.58 to 380.59 Alpha 2.

No immediate issues seen. All looks to be okay, so far so good! :)
 
Just upgraded my 87U from 380.58 to 380.59 Alpha 2.

No immediate issues seen. All looks to be okay, so far so good! :)
Did you factory reset first?

I would like to try the alpha too but do not want to re-setup everything...

Sent from my Nexus 6P using Tapatalk
 
Asus RT-AC88U
Merlin Firmware 380.59 Alpha2-g1ff739b
Factory Reset has been applied

Heavy long term streaming while using the 380.59 Alpha2 firmware on the Asus RT-AC88U in Media Bridge Mode results in a critical failure.

Ways I have managed to create repeatable crashes:
1. Use the PlayStation 4 Remote Play feature just debuted along PS4 firmware 3.50.
a. Configured the Remote Play client for High Settings (720p & High Quality)
2. Have the PlayStation 4 stream for hours on end to the media bridge.
a. Playing is not required, just leaving it in the background streaming will eventually trigger the bug.
3. Watch the Asus RT-AC88U suffer the following failures with no logged entries explaining the failures.
a. Sudden Reboot.
b. Total loss of connection to the Access Point that forces a manual reboot.

I have my doubt it'll help, but just for completeness sake.

The Remote Play client uses IPv4 TCP & UDP

TCP port 9295 is the destination
It appears the UDP port is randomly selected from the Dynamic Range (60908 in this instance is the destination)
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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