Official package feeds for custom OpenWrt

For Developers
1

I can see that the feeds are set to a non-existent SNAPSHOT url. As I understand this is to prevent incompatibility, but what do I do to be able to use the packages?

I have tried to add the 25.10 kmod feeds just to see, but I get these meaningless errors (I guess kernels are not compatible)

root@WR702N:~# apk add kmod-fs-ext4
ERROR: unable to select packages:
  kernel-6.12.62~c81ce0f2cc70167ae758fc67a16fcce5-r1:
    breaks: kmod-fs-ext4-6.12.62-r1[kernel=6.12.62~09061d117cbed01409d998106bfccfdd-r1]
            kmod-lib-crc16-6.12.62-r1[kernel=6.12.62~09061d117cbed01409d998106bfccfdd-r1]
    satisfies: world[kernel=6.12.62~c81ce0f2cc70167ae758fc67a16fcce5-r1]
               kmod-ath-6.12.62.6.18-r1[kernel=6.12.62~c81ce0f2cc70167ae758fc67a16fcce5-r1]
               ...

I see two options:

  1. editing feeds (tried and failed)
  2. compiling OpenWrt to be compatible with package/kmod feeds

As the first option has failed, how do I compile custom OpenWrt release images that are compatible with the feeds? (and works seamlessly like an official release)

2

The kmods have to come from your custom build.

You could modify vermagic for the custom build, to make it match the one from "here".

1 Like
3

Is there seriously no way to compile an identical kernel version with a few small tweaks and use it?

I want to keep my sanity and not compile literally everything myself

What is vermagic?

4

Most of the compile time is spent on building the kernel AFAIK (been a while since I did it though).

The unique kernel ID string that makes kmods from a diff kernel fail to load.

By coincidence, it's mentioned in a thread created earlier today - [TOOL] [WIN/LINUX] routerFW: Dockerized OpenWrt Builder (Stateful Upgrades, IPK Import, Vermagic).

1 Like
5

The vermagic fix is exactly what I need. Thanks. Now I know how to proceed

6

I think you're going down the wrong path here...
vermagic is like the safety barrier to stop the modules going off the road on an incompatible kernel.

Hacking vermagic is not what you want to do.
You want to have a consistent kernel to the modules.
With snapshot, this doesn't really happen. Each snapshot is exactly that, a snapshot in time. So if you later try to use modules from a different snapshot, they are incompatible.

Are you not able to use the firmware selector to get a full set of modules that you want? This would ensure that they are all consistent (at the time you request them).

If you want custom modules, then self-compiling is likely the way..

1 Like
7

I am compiling because the firmware for my device no longer exists (tp-link WR703/WR702) and I can do so because my device has 16M Flash+64M RAM

So I can not avoid compiling, firmware selector no longer has my device

I also know the risks, so for the time being I just add the kmods I need directly to my image, and then use the regular package feeds for the rest. I am still going to keep vermagic in mind for future use if this is not good enough

8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.