lucize
November 5, 2024, 12:29pm
827
[ 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
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.
lucize:
@robimarko or someone else, could you please help me with the content of mtd1 for 301w, somehow I made a typo and erased mtd1 instead of mtd10, is that partition critical? can I extract it somehow from the original image?
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
lucize
November 8, 2024, 1:17pm
833
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
lucize
November 8, 2024, 2:06pm
835
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.
lucize
November 8, 2024, 4:09pm
837
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.
opened 12:13AM - 14 Feb 24 UTC
closed 10:31AM - 18 Mar 24 UTC
bug
invalid
### Describe the bug
Updating to the latest snapshot (compared to the 2 weeks… older build) with sysupgrade keeping the settings leads to LEDs no longer working after sysupgrade.
These can be seen in kernel log
```
[ 4.246494] leds-gpio leds: Led green: renamed to green:_1 due to name collision
[ 4.248978] leds-gpio leds: Led green: renamed to green:_2 due to name collision
[ 4.256345] leds-gpio leds: Led green: renamed to green:_3 due to name collision
[ 4.263770] leds-gpio leds: Led green: renamed to green:_4 due to name collision
[ 4.271105] leds-gpio leds: Led amber: renamed to amber:_1 due to name collision
[ 4.278487] leds-gpio leds: Led green: renamed to green:_5 due to name collision
[ 4.285856] leds-gpio leds: Led amber: renamed to amber:_2 due to name collision
[ 4.293257] leds-gpio leds: Led green: renamed to green:_6 due to name collision
[ 4.300616] leds-gpio leds: Led amber: renamed to amber:_3 due to name collision
[ 4.308002] leds-gpio leds: Led green: renamed to green:_7 due to name collision
[ 4.315384] leds-gpio leds: Led amber: renamed to amber:_4 due to name collision
[ 4.322760] leds-gpio leds: Led green: renamed to green:_8 due to name collision
[ 4.330135] leds-gpio leds: Led amber: renamed to amber:_5 due to name collision
```
I played a bit with the LEDs configuration and it seems that LED names were changed (as stated in kernel log due to name collision) and that was the reason they didn't work. I didn't try to reset all settings to deafault to see if they would work without playing with their settings.
Now they are a bit stirred. But switching between the numbers I've found this order of all 9 green coloured LEDs.
I didn't play with amber coloured ones.
![91257b986da805ad2845b2c1e3d199bd5024613b](https://github.com/openwrt/openwrt/assets/46223847/49fc87c2-7d45-4de1-9895-e8b73337b36f)
Previously the device names matched the LED names.
### OpenWrt version
r25275+3-1128290dbf
### OpenWrt release
SNAPSHOT
### OpenWrt target/subtarget
qualcommax/ipq807x
### Device
QNAP 301w
### Image kind
Self-built image
### Steps to reproduce
Usual sysupgrade from older snapshot to the latest one keeping the settings.
### Actual behaviour
_No response_
### Expected behaviour
All the LEDs should work and have names matching device names. This was the case before the latest LED changes for qualcommax.
### Additional info
_No response_
### Diffconfig
_No response_
### Terms
- [X] I am reporting an issue for OpenWrt, not an unsupported fork.
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?
lucize
November 8, 2024, 5:50pm
840
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 .
lucize:
defined, redefined
Could you briefly highlight what you did to "defined, redefined" them again?
lucize
January 10, 2025, 5:09pm
843
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.