That’s one of the problems with snapshots: you can’t install kernel modules via opkg. See here:
https://openwrt.org/faq/cannot_satisfy_dependencies
Only workaround i know: build the images by yourself and include all required kernel modules
For sure I was able to install luci-ssl while using the "official" SNAPSHOT build. Probably another SNAPSHOT target (kmods and packages) was compiled in the meantime.
Yes, there is also a difference in the snapshots provided by OpenWrt ant the one I build:
- The OpenWrt ones can download all kernel modules until a new build is available
- With my builds, kernel modules are not available at all because the build versions differ
Theoretically I can build all kernel modules with my environment and provide it as a zip. But as long it is only for testing, I try to avoid the effort
1 Like
D-Link EAGLE PRO AI R32
OpenWrt 23.05.4
works great!
1 Like
D-Link EAGLE PRO AI R32
OpenWrt 23.05.4
is 160mhz channels work in progress? i can select 160mhz on luci but i get only 80mhz
Today I've installed OperWrt 23.05.4. I used the recovery image and the recovery web ui to deploy it.
However, I am surprised to see the partition layout is the old one:
[root@OpenWrt-R32] ~$ cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "Preloader"
mtd1: 00040000 00020000 "ATF"
mtd2: 00080000 00020000 "Bootloader"
mtd3: 00040000 00020000 "BootConfig"
mtd4: 00040000 00020000 "Odm"
mtd5: 00080000 00020000 "Config1"
mtd6: 00080000 00020000 "Config2"
mtd7: 02d00000 00020000 "Kernel1"
mtd8: 003a0000 00020000 "kernel"
mtd9: 02500000 00020000 "ubi"
mtd10: 02d00000 00020000 "Kernel2"
mtd11: 00100000 00020000 "Factory"
mtd12: 00200000 00020000 "Mydlink"
mtd13: 00300000 00020000 "Storage"
Another issue: I've installed only a few packages, and I ran into a "no space left on device" issue:
[root@OpenWrt-R32] ~$ opkg install luci-app-samba4
Installing luci-app-samba4 (git-23.142.65904-c0478f0) to root...
Downloading https://downloads.openwrt.org/releases/23.05.4/packages/aarch64_cortex-a53/luci/luci-app-samba4_git-23.142.65904-c0478f0_all.ipk
Installing samba4-libs (4.18.8-1) to root...
Collected errors:
* verify_pkg_installable: Only have 1376kb available on filesystem /overlay, pkg samba4-libs needs 8995
* opkg_install_cmd: Cannot install package luci-app-samba4.
Here is the status of the used/free space on /overlay partition:
[root@OpenWrt-R32] ~$ df -h /
Filesystem Size Used Available Use% Mounted on
overlayfs:/overlay 24.5M 21.9M 1.3M 94% /
And I have only 255 packages installed:
[root@OpenWrt-R32] ~$ opkg list_installed|wc -l
255
Just for comparison: on an Asus RT-AX53U router with OpenWrt 22.03.2, where I implemented my own partition layout (mtd5: 07820000 00020000 "ubi"), I have 394 packages installed, which take only 8.4MB of space out of 84.8MB:
[root@OpenWrt-AX53U] ~$ opkg list_installed|wc -l
394
[root@OpenWrt-AX53U] ~$ df -h /
Filesystem Size Used Available Use% Mounted on
overlayfs:/overlay 84.8M 8.4M 72.0M 11% /
How is this possible? Is the compression level of /overlay partition worse in 23.05.4 than in 22.03.2?
Any suggestion is highly appreciated.
Thanks,
Cristian
Hi Cristian,
Until now, there was no pull request for the new memory layout. So all the official OpenWrt builds use the OEM compatible layout.
That's something I don't know.
Would it be possible to build a "forked" version of stable 23.05.4 but with the custom partition layout?
I know this is a hack, but that way I would ensure the 23.05.4 stable kernel modules will be always accesible by opkg.
Thanks!
LE: what if instead of completely removing the "Kernel2" partition, we would set it to the minimal size accepted? (I believe that would be the "erase size" = 0x20000 = 128KB)
Would this ensure compatibility with the OEM partition layout?
Short answer: yes, search for "vermagic" in the forum, there might be hints how to do it.
Long answer: see here
From my point of view every change in the memory layout would break the OEM compatibility. Question is, if the compatibility is really required. It's an option to switch back to OEM firmware quickly, but the same result can be achieved by flashing the decrypted factory images via recovery web interface. Unfortunately there were some changes in the firmware crypto recently. If you flash an OEM firmware which is not compatible to the crypto settings in the ODM partition, you're not able to flash any OEM firmware update anymore.
1 Like
Hi! I installed 23.05.4 when it came out. It worked fine. I used "Flashing via Recovery Web Interface:" method from https://github.com/openwrt/openwrt/pull/14060
Today I flashed dlink_eagle-pro-ai-r32-a1-squashfs-sysupgrade.bin ab2dd41963a849404de6e11cf1919a713433c607794ba4bbb0630261b868dc24 8170.3 KB Thu Aug 22 19:19:08 2024 via luci and apparently it didn't work. Some of the LEDs flashed for a bit, then the orange power LED lit up and that's it.
Any ideas?
Hello @dubhater,
do you have some more information:
- Is the new image an official one from the firmware selector? Is it the current shaphot version?
- Did you enable "keep settings" while flashing the new image?
- What is the color of the LED? Is the power led blinking white after a reset and afterwars constantly on?
- can you ping the router after flashing the new image?
- I saw that in some cases a power cycle was required to boot, did you check that?
- Is flashing via recovery still working? (Note that this will probably erase all your settings)
dlink_eagle-pro-ai-r32-a1-squashfs-sysupgrade.bin ab2dd41963a849404de6e11cf1919a713433c607794ba4bbb0630261b868dc24 8170.3 KB Thu Aug 22 19:19:08 2024 came from here: https://downloads.openwrt.org/releases/23.05-SNAPSHOT/targets/mediatek/mt7622/ It seems to be the current snapshot.
I think I did enable "keep settings". There were three checkboxes. The first one was ticked. The rest were not. I left them like that. I think the first one was "keep settings".
I turned it off and on again from the switch. At first the internet LED (orange) and 2.4 GHz LED (white) turn on. About a second later the power LED (white) and 5 GHz LED (white) turn on weakly, not at full brightness. Another second later all LEDs turn off and the power LED (orange) turns on and stays on. Nothing more happens. No LEDs blink.
Of course the wifi networks are not visible to clients. I will try a wired computer later. Mine only has wifi.
I turned it off and on a few times now. Nothing changed.
It seems like you don't have any magical solutions 
so I will void the warranty and attach my PL2303 device.
No, I don’t have a magic trick, didn’t see this problem before.
It's booting kernel 4.4.124: https://0x0.st/XyFl.txt
Looks like it tries to boot from the first partition:
NAND read: device 0 offset 0x2c0000, size 0x3a0800
But the kernel cannot be loaded:
## Loading kernel from FIT Image at 4007ff28 ...
Could not find configuration node
ERROR: can't get kernel image!
Then it tries to boot from the second partition:
NAND read: device 0 offset 0x2fc0000, size 0x2000
Kernel 4.4 indicates OEM firmware, but for me it's not clear why it cannot be booted anymore.
Update: the kernel command line still indicates boot from the first partition:
bootargs:(console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs boot_part=Kernel1)
So it tries to boot the kernel from partition two in the end, but I assume with using the roots from the OpenWrt partition
Is there anything you would like me to do before I try the recovery web interface again?
A dump of the Kernel1 partition would be great, but it would also include the configuration with all credentials and so on.
What would be interesting for me: is the issue reproducible? So if you flash the recovery of 23.05.4 again, is sysupgrad to the current snapshot failing again?
If this is the case, what about the other way around: Is sysupgrade to 23.05.4 working after flashing the snapshot recovery image?
I loaded the snapshot initramfs image and copied the Kernel1 partition that way. I would like to delete the passwords from it before sharing it with you, but I don't know how.
I was able to flash the snapshot recovery image and everything is fine now. I would rather not break it again.
Hello Rolando,
for my R32 with flashing Openwrt 23.05.4, there is only 24.5M for the overlay; however the version build from you that is 64.6M.
would you tell me or share how to build a larger space for the overlay?
thanks a lot!
BR,
JasonHCH
Hello @dubhater,
The image with the larger partition size was a custom image which merged the two firmware partitions to one big partition.
You can have a look at the changes here: