Adding OpenWrt support for QNAP QHora-301W

For Developers
767

Can I ask what is the benefit of loading from userspace?

768

You are not going to like this because I know your opinion on the NSS build, and I have not tested yet as its daytime and they are all online so kick in the face if I reset the AP...

Using the NSS build loading from NVMEM 10g-1 does not work... I am unsure if it will now though (after loading the fw as above), untested still, as I run this floor on 10g-2 and 10g-1 empty... And like I said, they are all online :wink:

1 Like
769

Ok I took the chance:

[150430.774158] nss-dp 3a001800.dp5 10g-1: PHY Link up speed: 10000
[150430.774330] br-lan: port 5(10g-1) entered blocking state
[150430.779265] br-lan: port 5(10g-1) entered forwarding state

It works.

1 Like
770

Important, earlier on (same boot, no reboots since) I ran the 2:

ssdk_sh debug phy set 0 0x4004c441 0x8
ssdk_sh debug phy set 8 0x4004c441 0x8

commands.

So maybe this is why it works? Still untested.

771

Really cool that you made it. I think it's worth trying this method as I still experience this glitch and we better have an alternate method and can utilize the stock FW too.
Can you write the recipe to load the 10G FW from userspace.

772

How is AQR firmware loaded in OEM? From u-boot?

773

AFAIK it's loaded from userspace. See the link above.
@anom3 Did you write a script in init.d and used aq-fw-download tool to load the FW?

774

It still does not work btw...

I mean, everything looks like it should work, but it doesnt:

  1. Install 5.4.C on mtd10 + mtd11.
  2. Load from NVMEM.
  3. So at this point 10g-1 is broken.
  4. Load using aq-fw-download.
  5. Adapter restarts (dmesg) but still broken, 10g-1 autoneg timeout.
1 Like
775

Looks expected that it doesn't work when loaded from userspace either. Because I think no matter what way the firmware was loaded (U-Boot, NVMEM or userspace) it should work once loaded.
It's still good that we can now load it from userspace too even though the port actually doesn't work.
Every manufacturer AFAIK load the FW from userspace obviously (for a reason) using scripts to configure/set additional parameters and it works that way.
So if we could figure out what "magic" they do we may be able to finally have it working. All stock firmwares are NSS enabled too.

776

They dont do anything magical, all that those 2 same writes to PHY regs do are:

  1. Enable USXGMII MAC autoneg
  2. Restart PHY autoneg

Both of these are already done by SSDK after FW is loaded

1 Like
777

For AQR114C there is something more in the init script (wan_AQR_monitor.sh): OpenWrt support for Linksys MX8500 - #24 by lytr

1 Like
778

@robimarko I've used "magic" just as a metaphor and because I don't have the complete understanding what the script does.
I'm really well aware that you are one of the most knowledgeable persons here especially on this topic too.
That's why, I really appreciate your feedback and clarification here.
Still I think my logic is right and I really wonder why only one of the 10G ports, doesn't work.
Considering the stock firmware limited capabilities compared to what OpenWrt gives us, I really don't believe (don't trust) the stock firmware (10G FW in this case) is definitely better than the (generic) one we use in OpenWrt.

779

Trust me I get what you are trying to say.

1 Like
780

Ok, so lets try and figure out what they are doing:

  • 0x401ec430 0xc0ef
    1E.C430 is Global LED Provisioning 1

  • 0x401ec431 0xc0e0
    1E.C431 is Global LED Provisioning 2

  • 0x40070010 0x91e1
    7.1 is Autonegotiation Standard Status 1.
    No idea what they are trying to set here as most bits are RO or duplicates from another register, only reserved bits are RW

  • 0x40070000 0x3200
    7.0 is Autonegotiation Standard Control 1.
    They are restarting autonegotation here, required after FW is loaded.

  • 0x4004c441 0x8
    4.C441 XAUI RX Reserved Vendor Provisioning 2.
    They are enabling USXGMII MAC Autoneg, this is also a standard thing.

The only one that I dont have any docs on is:
0x401e2680 0x1
But given that 1E.2681 is Global Common POR control 2 and it only does resetting my bet is that its another reset register.

2 Likes
781

I quote myself.

Do you have any suggestion how can I investigate this?
I suppose not many people do it, plug in and out their cables too often. But as I tested another device I had to do this several times and that's the result. Port simply stops working.
I've found this while testing kernel 6.6 on RB5009 and another possible issue.

782

Well, I wouldn't know even where to start honestly

783

Hello,
I have problems with the WLAN on the device. It stops working every few weeks. The Wireless Overview tab in Luci then shows that no devices are connected. If I then click on "Restart" on radio0 and radio1, they no longer start and turn "red". Only a reboot of the router helps. Unfortunately I have no more log messages at the moment, next time I will try to find and save them.

Has anyone ever heard of such problems that WLAN is stop working or do they have them too?
Should I open a separate topic or is it ok to ask here?

EDIT: Could it be that the device could have a problem with the 802.11r Fast Transition setting on the WLAN Roaming tab? I had activate this. Is something like this known?

784

Can you backup a uboot file and share it? geart thanks

785

Can you backup a uboot file and share it? geart thanks

786

I keep having this problem with the device. Every few days the WLAN stops working, only a reboot helps.
This is currently in the log.

Sat May 25 20:23:55 2024 kern.warn kernel: [359691.308746] ath11k_warn: 70 callbacks suppressed
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.308769] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.312459] ath11k c000000.wifi: failed to send pdev bss chan info request
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.320158] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.326870] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.333530] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.340094] ath11k c000000.wifi: failed to submit beacon template command: -108
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.346311] ath11k c000000.wifi: failed to update bcn template: -108
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.353980] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.360323] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sat May 25 20:23:55 2024 kern.warn kernel: [359691.367068] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID

Should I open a separate post or is it ok here?