Looks like sysupgrade is working however anyone got luci operational
seeing:
regexp could be something like 'pkgname*' '*file*' or similar
e.g. opkg info 'libstd*' or opkg search '*libop*' or opkg remove 'libncur*'
root@OpenWrt:~# opkg install luci
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (libpthread and libpthread) providing same name marked HOLD or PREFER. Using latest.
Package luci (git-20.074.84698-ead5e81) installed in root is up to date.
root@OpenWrt:~# /etc/init.d/uhttpd enable
root@OpenWrt:~# /etc/init.d/uhttpd restart
4+0 records in
4+0 records out
root@OpenWrt:~#
This will get the router booted with openwrt from there you can issue update and install packages, now I am still having issues getting luci working on this so if you figure that out or have built a sysupgrade with luci working please let me know.
what routeros version have you been using? I have 6.48.5 and cant make it work
update: now managed to downgrade to 6.47.8 which is my factory firmware. @markbirss could you make it work?
question: should I jailbreak or wait for a more final version to be done? what do you think @voip2014? btw..the initramfs file you mention in your oct17 post is the one from may?
More details please; tell us the process you tried?
Jailbreak will not help you. A build based on Robi's PR will be a near final version, and any testing helps.
The initramfs file has -initramfs in the file name. It should end something like -initramfs-kernel.bin
It looks like @voip2014 has not provided a recent initramfs, and from an older initramfs, you will not be able to (reliably) install a sysupgrade.
You should be compiling the image yourself, or at least be aware that something could add a nasty bonus (example: botnet) to third party compiled image.
If you could not get the initramfs to start, my usual suggestions are:
Use RouterBOOT BOOTP mode (the default), and a BOOTP/TFTP server (example: dnsmasq-full on openwrt)
Start to hold in the reset button on the hapac3 before (or just after, for a different RouterBOOT version) you supply power.
Continue to hold this button in while the LED changes from off (takes some time to load RouterBOOT), to solid (stays for 5+s), to flashing (5s), to solid (5s), to off, then let go. It might be 20s of button held total, watch the changing light pattern to make sure you get to NetInstall phase.
Ok. I was trying to avoid building the image myself because I didnt want to make a mistake. But I guess that is how we learn :). I am building it now in a ubuntu VM. It seems that it take a long time, so I will leave it there overnight (btw, do you know how many steps the make has? or more or less how long would it take? I have an M1 mac and running a ubuntu server VM).
first compiled is tools, then toolchain, target/linux compile, package, and finally target/linux install
It does take hours for the toolchain (parts that let you build for specific architecture—arm a7 in this case) to build.
these show as make -C toolchain
This only needs to happen once (if you keep the build directory). Occasional updates (to the toolchain) mean parts of it get recompiled now and again.
Once you have a toolchain, the device kernel might take 30 minutes, and another 30 minutes for the device packages and image.
These times are very hardware dependent, but should give you a rough idea.
go ahead and let us know if they work, and feel free to compile it yourself if you can so far no issues on the compile with luci as of today.
Note: most app packages require 5.4.155-1-6b609bad… while 5.4.150-1-07af304a… is installed from the build above, until this is calling the right kernel most apps will not install correctly.
