B1300 Image Builder

stangri · 2018-03-03T00:11:29.209Z

@kyson-lok how can I build the vanilla OpenWrt image for B1300?

PS. Even tho your custmized GL-Inet image builds successfully, there’s a bunch of the dependency errors and the init script errors while building the image, stuff like:

Activating init scripts
/etc/init.d/inetd does not have a START or STOP value
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/firewall_gl: line 9: uci: command not found
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/firewall_gl: line 10: uci: command not found
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/firewall_gl: line 11: uci: command not found
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyfi-bridging: line 13: /lib/functions/hyfi-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyfi-bridging: line 14: /lib/functions/hyfi-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyfi-bridging: line 15: /lib/functions/hyfi-network.sh: No such file or directory
/etc/init.d/ssid_steering does not have a START or STOP value
Create './build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/filesystems'.
Add 'ntfs-3g' to known filesystems.
/etc/init.d/odhcpd does not have a START or STOP value
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/acd: line 26: /lib/functions/hyfi-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/acd: line 27: /lib/functions/hyfi-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/acd: line 28: /lib/functions/hyfi-network.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyd: line 32: /lib/functions/hyfi-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyd: line 33: /lib/functions/hyfi-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/hyd: line 34: /lib/functions/hyfi-network.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/thermal: line 7: /lib/ipq806x.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/lbd: line 20: /lib/functions/lbd-config.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/lbd: line 21: /lib/functions/whc-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/lbd: line 22: /lib/functions/whc-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/repacd: line 42: /lib/functions/whc-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/repacd: line 43: /lib/functions/whc-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/repacd: line 44: /lib/functions/whc-network.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/repacd: line 45: /lib/functions/repacd-netdet.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/wsplcd: line 27: /lib/functions/hyfi-debug.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/wsplcd: line 28: /lib/functions/hyfi-iface.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/wsplcd: line 29: /lib/functions/hyfi-network.sh: No such file or directory
./build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/root-ipq806x/etc/init.d/qcmbr: line 9: /lib/functions.sh: No such file or directory
/etc/init.d/qcmbr does not have a START or STOP value

kyson-lok · 2018-03-05T01:24:14.913Z

[1] You can ignore those errors.
[2] You can build vanilla from OpenWRT/LEDE source code, or vanilla-imagebuilder.

stangri · 2018-03-05T03:17:44.920Z

@kyson-lok: using vanilla image builder I get:

$ make image PROFILE=glinet_gl-b1300
Building images for ipq806x - GL.iNet GL-B1300
Packages: base-files busybox dnsmasq dropbear firewall fstools ip6tables ipq-wifi-glinet_gl-b1300 iptables kernel kmod-ata-ahci kmod-ata-ahci-platform kmod-ata-core kmod-ath10k kmod-gpio-button-hotplug kmod-leds-gpio kmod-usb-core kmod-usb-dwc3-of-simple kmod-usb-ledtrig-usbport kmod-usb-ohci kmod-usb-phy-qcom-dwc3 kmod-usb2 kmod-usb3 libc libgcc logd mtd netifd odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe swconfig uboot-envtools uci uclient-fetch wpad-mini

...

Configuring libubox.
Configuring libuclient.
Configuring uclient-fetch.
Configuring libpthread.
Configuring opkg.
Configuring kmod-nls-base.
Configuring kmod-usb-core.
Configuring libubus.
Configuring libjson-c.
Configuring libblobmsg-json.
Configuring ubusd.
Configuring ubus.
Configuring libnl-tiny.
Configuring iw.
Configuring wireless-regdb.
Configuring kmod-cfg80211.
Configuring hostapd-common.
Configuring kmod-mac80211.
Configuring kmod-ath.
Configuring kmod-ath10k.
Configuring busybox.
Configuring kmod-scsi-core.
Configuring kmod-ata-core.
Configuring kmod-ata-ahci-platform.
Configuring kmod-nf-reject6.
Configuring libuci.
Configuring swconfig.
Configuring kmod-usb-dwc3.
Configuring kmod-lib-crc-ccitt.
Configuring kmod-usb-dwc3-of-simple.
Configuring kmod-usb-phy-qcom-dwc3.
Configuring kmod-slhc.
Configuring kmod-ppp.
Configuring kmod-pppox.
Configuring kmod-pppoe.
Configuring kmod-nf-reject.
Configuring kmod-nf-ipt.
Configuring kmod-ipt-core.
Configuring kmod-nf-conntrack.
Configuring kmod-ipt-conntrack.
Configuring jshn.
Configuring netifd.
Configuring libjson-script.
Configuring ubox.
Configuring procd.
Configuring jsonfilter.
Configuring usign.
Configuring lede-keyring.
Configuring ubi-utils.
Configuring fstools.
Configuring fwtool.
Configuring base-files.
Configuring kmod-nf-nat.
Configuring uboot-envtools.
Configuring kmod-usb-ohci.
Configuring dnsmasq.
Configuring kmod-usb-ehci.
Configuring kmod-usb2.
Configuring kmod-usb3.
Configuring libxtables.
Configuring libip4tc.
Configuring libip6tc.
Configuring kmod-nf-conntrack6.
Configuring kmod-ipt-nat.
Configuring firewall.
Configuring kmod-nf-ipt6.
Configuring kmod-ip6tables.
Configuring odhcp6c.
Configuring uci.
Configuring wpad-mini.
Configuring dropbear.
Configuring mtd.
Configuring odhcpd-ipv6only.
Configuring ppp.
Configuring kmod-leds-gpio.
Configuring kmod-gpio-button-hotplug.
Configuring logd.
Configuring kmod-ata-ahci.
Configuring iptables.
Configuring ip6tables.
Configuring kmod-usb-ledtrig-usbport.
Configuring ppp-mod-pppoe.
Collected errors:
 * opkg_install_cmd: Cannot install package ipq-wifi-glinet_gl-b1300.
Makefile:146: recipe for target 'package_install' failed
make[2]: *** [package_install] Error 255
Makefile:109: recipe for target '_call_image' failed
make[1]: *** [_call_image] Error 2
Makefile:202: recipe for target 'image' failed
make: *** [image] Error 2

Without specifying the profile the image builder completes successfully, however I’m not sure if it gets the proper wifi firmware file then. Please advise.

kyson-lok · 2018-03-05T04:24:16.071Z

All right, Our engineer will fix this. You should download LEDE buildroot instead of vanilla imagebuilder to build b1300 image currently.

justin · 2018-03-05T18:48:09.758Z

It would be great also if a clean firmware image was provided pre-compiled in the future from GL-Inet

kyson-lok · 2018-03-06T01:15:10.093Z

Thanks for your suggestion.

stangri · 2018-03-08T03:11:52.725Z

@kyson-lok – any idea when the snapshot image builder would be fixed to produce a working image for B1300?

kyson-lok · 2018-03-08T03:57:35.089Z

@stangri I have sent you an email which is included a ipk binary.

stangri · 2018-03-15T02:59:23.777Z

@kyson-lok – thank you, it worked for a while, but today I have grabbed a new image builder from snapshots and there’s no profile for B1300 there anymore!

How can I build vanilla image now?

Also, with the vanilla image builder the leftmost ethernet port doesn’t work at all (the middle one is LAN and the rightmost is WAN, but the leftmost doesn’t work). I’ve tried adding the switch and switch_vlan entries in /etc/config/network and it didn’t seem to help. So two questions:

How can I build vanilla image now that the B1300 profile is not included in the snapshot image builder?
What do I need to edit in the configs to make use of the leftmost ethernet port?

Thanks!

stangri · 2018-04-22T11:38:15.106Z

@kyson-lok the B1300 gor moved to the ipq40xx platofrm and its image builder includes the profile for B1300, however the ipq-wifi-glinet_gl-b1300 package is still missing from the vanilla snapshot repo. The file you’ve sent me previously was built for the ipq806x platform (cortex a15) while the current platform is ipq40xx (cortex a7). Can you please send me or post somewhere the ipq-wifi-glinet_gl-b1300 built with the ipq40xx SDK?

kyson-lok · 2018-04-23T01:33:58.520Z

@stangri We have submit patch to ath10k-firmware, so this dependency is useless, you can remove it.

kyson-lok · 2018-04-23T04:37:30.831Z

@stangri Have sent to you, pls check out e-mail. We have submitted patch to ath10k-firmware, after mergeing this dependency ipk will be deleted from openwrt.

stangri · 2018-08-01T04:43:38.760Z

Reviving this…

@kyson-lok, @alzhao and @hansome.

Initial support for B1300 was under the IPQ806x target tree and I’ve managed to make a few builds with the lede snapshot image builder before B1300 was migrated into IPQ40xx tree.

When the B1300 was switched into IPQ40xx tree, one of my customers noted significant decrease of the wireless performance under load (20-30 clients) with the images generated with the IPQ40xx builder comparing to the images made with the IPQ806x builder.

Do you gentlemen have an idea why is that and what can be done to restore the wireless performance under load to the same level it used to be on images made for B1300 with the IPQ806x image builder?

I’m talking about the vanilla OpenWrt here, without GL-Inet customizations.

Can this still be used in any way to generate a vanilla OpenWrt image?

Thanks!

alzhao · 2018-08-01T04:45:20.848Z

I don’t think that is easy now. We used Qualcomm proprietary WiFi driver. Open source drive do have issues in performance.

kyson-lok · 2018-08-01T05:30:57.013Z

The imagebuilder can’t generate a vanilla OpenWrt image. That’s qsdk imagebuilder.

paulham · 2018-09-24T06:49:05.974Z

Why is there a need for an image builder? Surely all B1300 owners have the same hardware so why does each person have to compile the image themselves?

Sorry if this seems a newbie question, but a pre-compiled version would help a lot of people and it is difficult to see why one is not made available but the image builder is.

alzhao · 2018-09-24T08:30:41.941Z

Some people just want to have more software compiled in the firmware. So once they reset the firmware their stuff is still there.That is what an Imagebuilder used for.

Johnex · 2018-09-24T19:25:34.851Z

Think of it like this. If you save all your router configuration, you can restore it if something happens.

Unfortunately, that does not install your software too.

So with imagebuilder you can basically have exactly the same as the GL compiled builds, BUT you can also choose to add your software into the image, so if you ever need to flash it again, your programs are also installed.

paulham · 2018-09-25T06:56:18.317Z

Sorry I understood that this was a vanilla OpenWRT/LEDE installation. Not an image builder for the present GLiNet firmware.
I would like to change to OpenWRT/LEDE because there is software installation options for things such as Adblock and wireguard in the present GLiNET firmware, and from what I have read above you need a certain level of expertise to compile the firmware.

Thanks, it makes more sense now.

Johnex · 2018-09-25T09:53:10.930Z

You can both add and remove programs using the GL imagebuilder.
If you need to compile some program that is not in the GL package list, then yes you would have to compile it using the OpenWrt compile tools.