Adding OpenWrt support for QNAP QHora-301W

[    1.834317] Aquantia AQR113C 90000.mdio-1:00: loading firmware version 'v5.4.C CIG WF-1945_0x0 060120 02:47:48' from 'NVMEM'
[   13.256601] Aquantia AQR113C 90000.mdio-1:08: loading firmware version 'v5.4.C CIG WF-1945_0x8 060120 02:47:48' from 'NVMEM'
[   24.861019] Aquantia AQR113C 90000.mdio-1:08: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:08, irq=POLL)
[   24.886040] Aquantia AQR113C 90000.mdio-1:00: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:00, irq=POLL)

guess I have to update the wiki as I'm in debt for now :slight_smile:

4 Likes
root@OpenWrt:~# mtd erase 0:ethphyfw1
Could not open mtd device: 0
Could not open mtd device: 0

root@OpenWrt:/tmp# mtd -n write AQR-G4_v5.4.C-AQR_CIG_WF-1945_0x0_ID44778_VER1630.cld 0:ethphyfw1
Could not open mtd device: 0
Can't open device for writing!

@sppmaster
I end up with the above, would you know why?

had the same issue, instead wrote directly to both mtd devices

1 Like

Nope, sorry I can't tell why? I've followed @robimarko's advice.

And seeing below looked scary.

I've proposed it for safety because if someone doesn't notice the mistake that was eventually made they would be really unpleasantly surprised with no bootable router.
Maybe this 0: is somehow the culprit. Just my speculation, though.

I think that ':' in the partition name is not being parsed as a string, maybe quoting the whole name would work

2 Likes

We can also obtain the mtd from name, will add a parse pipe

1 Like

yep agree it does avoid any fat fingers mistakes...

1 Like

Also, the front leds are not working, I saw a commit related to leds, the config needs to be changed? Didn't do a reset when I uploaded the latest build.

Which LED-s?

The ones in front, I have only the power led lighted up

See this first. You may have to reconfigure them if your settings are older.

The front LEDs work in my case but I've discovered a new issue:

Ports 1 -4 become unusable if the router is started up without hooking up a LAN cable to any of the ports. Clients connected to these ports after the router is fully started up do not get IPs assigned. The ports become fully functional again after a reboot. 10g-1 and 10g-2 ports are not affected, clients connected to these ports get IPs assigned without any issues.

Could your issue be related to the above?

I had them defined, redefined them again with exact the same settings and added the wlan and status. Now they are working

Some fixes were merged to main OpenWrt branch.
Thanks @Lanchon and @robimarko .

Could you briefly highlight what you did to "defined, redefined" them again?

go to led interface, print screen or train your memory, erase all entries and add them again like they were before

1 Like

Sadly this doesn't work in my case.

With the LAN cable disconnected and router rebooted, Lan ports 1 - 4 still unusable in my case. A LAN cable must be plugged into LAN ports 1-4 at startup in order to get these ports working after startup.