Gl.inet Marble openwrt support

What is the status of support for this router?

1 Like

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /proc/mtd
cat /proc/cpuinfo
cat /proc/meminfo
lspci
lsusb
ip link -> follow up with `ethtool -i interface@name before :
1 Like

Unsupported until someone adds it, assuming it's supportable...

I am going to receive it in a few days (just got a heads up from Gl.inet that they shipped it.
I will provide the info, once I have it.
A bit surprised, nobody noticed this device and hasn't added support yet.

1 Like

It's ipq5018, not supported. Just do a search in the forum for ipq50xx.

And no, it's not running OpenWrt, what gl-inet is calling OpenWrt is rather either QSDK or TIP-based.

1 Like

Thats a bummer.
Could it be supported in the future?

As soon as SoC support is added to mainline Linux.

1 Like

a) there is no one working on ipq50xx for OpenWrt yet
b) if there were someone working on it, you could expect them to require many months (double digit) to get it working/ merged.
c) as a) isn't given, chances aren't good at all - not impossible, but not very likely at this stage.

Because of the chipset is not supported, at least won't be in 1-2 years time

The GL-iNet IPQ5018 OSDK is forked from Openwrt 19.07.
The device is lovely, but I cannot recommend picking it up if you want to run actual Openwrt on it.

1 Like

What he said. Do not buy it expecting to run openwrt on it, during it's lifetime. It might get supported, but it will take years, if it ever happens.

1 Like

It seems, Gl.inet claim it will be upgraded to 23 and recently they posted on the forums, that they have uploaded to some openwrt fork? an initial release making it compatible with 23 branch.

That has absolutely nothing to do with openwrt. For openwrt to happen, it needs mainline linux kernel support for ipq5018. To be more specific, you can monitor this PR for the current status of ipq5018. When that's merged, work can start on the specific device, if anyone is interested.

I understand that.
My point was, that at least Gl.inet seem to be interested to make it work.
Unless, they will just somehow make Luci work with their otherwise incompatible fork of openwrt?
Other then that, what do they mean by promising to release a version based on 23.x branch of openwrt?

Thats exactly their plan. To make their qsdk kernel (qualcomm fork) openwrt fork ipq5018 devices somehow use newer kernel, so they use another fork (openwifi) with whatever changes to make that work. If they really wanted to bring mainline openwrt support, they would write pull requests to the linux kernel itself, which they do not do at all.

the SDK they use got upgraded to 23 ?

I think that's mainly done by the hw vendor, Qualcomm in this case, but I don't think they have a very good track record ...

@devast if thats the case, it is unfortunate, though the link that you provided does show some signs of work being done.
@frollic this is what a certain thread on their forum claims.
That they are currently working on releasing firmware update based on 23.x version.
Here is the relevant thread:

And yeah, thats also my question, what about Qualcomm involvment in this?
Since, they released the SDK, it is up to them to merge it into mainline?

yes, but as @matrix200 pointed out, it got nothing to do with us ...

they're the ones providing the vendors with the QSDK used for creating the baseline firmware.

SDK is usally based on an old(er) kernel, and needs to be rolled forward to catch up.
it's still for them to do, unless a 3rd party manages to do it for them.

in the case of OpenWRT, new devices need to have hw support by kernel 6.6.

2 Likes

@frollic @matrix200 @devast
See this thread:

2 Likes

Yeah, I saw it.

AFAIK all the successful boots were using kernel 5.15, only the poster knows how much work's needed to roll forward to 6.6.

it might be hours, days, weeks or months, I'm not hanging around to find out :slight_smile: