Hi,
I can’t find any information on the way to install arm64 kernel on l009.
Is it really possible, right now with a recent kernel?
Thanx for your help.
See the 7.22beta release topic
Thank you
And it works.
2 Likes
Like a charm. I confirm…
So, this page is wrong ? https://mikrotik.com/product/l009uigs_rm
Not really.
It is still being shipped as ARM.
But since 7.22 beta you can move it to ARM64.
I ask myself, "But why???"
Why not 64 if the CPU supports it...
Same sentiment here.
And what with Hex Refresh, Hex S 2025, AX Lite, ... ?
They are in the same boat.
1 Like
Really??? 
I'd never looked into it, because it seemed obvious to me...
Perhaps it was due to software size issues that exhausted the space on the NAND/XOR Flash, and the L009 has more space???
As in
64 bit capable cpu limited to 32 bit.
For now only L009 has the key to open the door.
But you know, since you don't look for the port, which you don't know exists, you don't even look for the key...
So a small patch to netinstall would be enough to install ARM64 on these models anyway... Maybe...
Hex S 2025 / Refresh have exact same storage/ RAM as L009.
Ax Lite half but exact same processor as L009.
Anyone the same?...
503 Service Unavailable
No server is available to handle this request.
If someone have one of those models, what options appear on terminal with
/system/routerboard/settings set preferred-architecture= and press <TAB>?....
I was going to try that later this evening on Hex S 2025..
1 Like
No success.
It keeps coming up as arm in netinstall even though you can set it to preferred-architecture=arm64.
I don't want to sound trivial, but I have to ask...
Did you first update the firmware, unlock everything in device-mode,
and perform a cold reboot with the new firmware you already used to start the machine?
I understand why you ask. No problem.
Device is unlocked.
system device-mode/print
mode: advanced
allowed-versions: 7.13+,6.49.8+
flagged: no
flagging-enabled: yes
scheduler: yes
socks: yes
fetch: yes
pptp: yes
l2tp: yes
bandwidth-test: yes
traffic-gen: no
sniffer: yes
ipsec: yes
romon: yes
proxy: yes
hotspot: yes
smb: yes
email: yes
zerotier: yes
container: no
install-any-version: no
partitions: no
routerboard: yes
And yes, I did update firmware, reboot, set preferred-architecture to ARM64
/system/routerboard/settings> print
auto-upgrade: yes
boot-device: try-ethernet-once-then-nand
preboot-etherboot: disabled
preboot-etherboot-server: any
cpu-frequency: 950MHz
preferred-architecture: arm64
boot-protocol: bootp
force-backup-booter: no
silent-boot: no
protected-routerboot: disabled
reformat-hold-button: 20s
reformat-hold-button-max: 10m
And then reboot.
Device comes up in netinstall but only as arm.
Probably, in the L009, some bit in the firmware has changed, which, by reading the "arm64" property, tells netinstall that it can use arm64 instead of arm, or it loads the ARM64 bootloader instead of ARM, and that's it, or the bootloader loaded by netinstall reads this information from the firmware before being "seen" online...
But I think that by fiddling with a few bytes... who knows...
And the fact that it saves this info in the RouterBOARD in products that are for now not supported, maybe in the future...