[Request] MochaBin Installation Guide

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

[Request] MochaBin Installation Guide

Postby MrW01f » Sun Nov 20, 2022 12:23 am

has anyone been able to install Archlinux arm on a M2 Sata drive?
is it possible to post a guide, step by step, to install archlinux from the installed ubuntu?

I tried to follow multiple guide, but none of them worked.

Thanks,
MrW01f
 
Posts: 4
Joined: Sun Nov 20, 2022 12:17 am

Re: [Request] MochaBin Installation Guide

Postby technosf » Mon Nov 21, 2022 9:23 pm

Yup, I did it here: https://archlinuxarm.org/forum/viewtopic.php?f=65&t=16239

Once caveat though - and its a big one - Ethernet networking ceased working after doing a pacman -Syu. I do not have the opportunity to figure out why.

I'd love to see MochaBin get its own install instructions and mainlined!
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 130
Joined: Sat Jan 08, 2011 10:54 pm

Re: [Request] MochaBin Installation Guide

Postby jimduchek » Wed Dec 28, 2022 6:53 am

I'm going to be working on this. I'm starting from a point of _serious_ fucking frustration with Globalscale about their utter lack of communication and documentation, and there's absolutely no chance I will _EVER_ give them crowdfunding money again, but I waited long enough for this thing, I'm going to make it do what I want.
jimduchek
 
Posts: 5
Joined: Tue Aug 01, 2017 5:24 pm

Re: [Request] MochaBin Installation Guide

Postby Mettacrawler » Sat Jan 21, 2023 3:00 pm

I wrote a Mochabin installation guide. Please let me know if you want any improvements to it.

https://gist.github.com/ambiamber/99e8444115f4c09253f30d5c74182c6e
Mettacrawler
 
Posts: 56
Joined: Sun Mar 18, 2018 7:19 pm

Re: [Request] MochaBin Installation Guide

Postby Mettacrawler » Sun Jan 22, 2023 12:58 pm

technosf wrote: $this->bbcode_second_pass_quote('', 'O')nce caveat though - and its a big one - Ethernet networking ceased working after doing a pacman -Syu. I do not have the opportunity to figure out why.


You can put all the updates on except for the kernel package and it works fine for me.

$this->bbcode_second_pass_code('', 'warning: linux-aarch64: ignoring package upgrade (5.18.1-1 => 5.19.8-1)')

One of the possibilities is that 5.19.8 has new configuration options that 5.18.1 doesn't have and those options are mandatory for Mochabin and unset.

Some of the log message while booting 5.19.8 show that the crypto fell off and 20,000 gallons of entropy was dumped into the sea ( https://www.youtube.com/watch?v=3m5qxZm_JqM )

$this->bbcode_second_pass_code('', '
Jan 18 21:59:42 alarm kernel: alg: No test for authenc(hmac(sha224),rfc3686(ctr(aes))) (safexcel-authenc-hmac-sha224-ctr-aes)

Jan 18 21:59:42 alarm kernel: WARNING: CPU: 1 PID: 204 at kernel/dma/mapping.c:199 __dma_map_sg_attrs+0x58/0x90
Jan 18 21:59:42 alarm kernel: Modules linked in: tag_dsa mv88e6xxx(+) dsa_core bridge stp llc sfp crypto_safexcel(+) mdio_i2c marvell mvpp2 authenc libdes phylink mvmdio armada_thermal sbsa_gwdt fuse
Jan 18 21:59:42 alarm kernel: CPU: 1 PID: 204 Comm: kworker/u8:2 Not tainted 5.19.8-1-aarch64-ARCH #1
Jan 18 21:59:42 alarm kernel: Hardware name: Globalscale MOCHAbin (DT)
Jan 18 21:59:42 alarm kernel: Workqueue: wq_ring1 safexcel_dequeue_work [crypto_safexcel]
...skip...
Jan 18 21:59:42 alarm kernel: Call trace:
Jan 18 21:59:42 alarm kernel: __dma_map_sg_attrs+0x58/0x90
Jan 18 21:59:42 alarm kernel: dma_map_sg_attrs+0x10/0x24
Jan 18 21:59:42 alarm kernel: safexcel_send_req+0x11c/0x740 [crypto_safexcel]
Jan 18 21:59:42 alarm kernel: safexcel_aead_send+0xac/0xd0 [crypto_safexcel]
Jan 18 21:59:42 alarm kernel: safexcel_dequeue+0x74/0x230 [crypto_safexcel]
Jan 18 21:59:42 alarm kernel: safexcel_dequeue_work+0x20/0x2c [crypto_safexcel]
Jan 18 21:59:42 alarm kernel: process_one_work+0x1a4/0x300
Jan 18 21:59:42 alarm kernel: worker_thread+0x6c/0x40c
Jan 18 21:59:42 alarm kernel: kthread+0xe4/0xf0
Jan 18 21:59:42 alarm kernel: ret_from_fork+0x10/0x20
Jan 18 21:59:42 alarm kernel: ---[ end trace 0000000000000000 ]---
')

$this->bbcode_second_pass_code('', '
Jan 18 21:59:42 alarm kernel: alg: ahash: safexcel-xcbc-aes test failed (wrong result) on test vector 0, cfg="init+update+final aligned buffer"

Jan 18 21:59:42 alarm kernel: alg: self-tests for safexcel-xcbc-aes (xcbc(aes)) failed (rc=-22)
Jan 18 21:59:42 alarm kernel: WARNING: CPU: 3 PID: 401 at crypto/testmgr.c:5753 alg_test+0x1e8/0x4b0
Jan 18 21:59:42 alarm kernel: Modules linked in: tag_dsa mv88e6xxx(+) dsa_core bridge stp llc sfp crypto_safexcel(+) mdio_i2c marvell mvpp2 authenc libdes phylink mvmdio armada_thermal sbsa_gwdt fuse
Jan 18 21:59:42 alarm kernel: CPU: 3 PID: 401 Comm: cryptomgr_test Tainted: G W 5.19.8-1-aarch64-ARCH #1
Jan 18 21:59:42 alarm kernel: Hardware name: Globalscale MOCHAbin (DT)
...skip...
Jan 18 21:59:42 alarm kernel: Call trace:
Jan 18 21:59:42 alarm kernel: alg_test+0x1e8/0x4b0
Jan 18 21:59:42 alarm kernel: cryptomgr_test+0x2c/0x50
Jan 18 21:59:42 alarm kernel: kthread+0xe4/0xf0
Jan 18 21:59:42 alarm kernel: ret_from_fork+0x10/0x20
')

$this->bbcode_second_pass_code('', '
Jan 18 21:59:42 alarm kernel: alg: ahash: safexcel-cmac-aes test failed (wrong result) on test vector 0, cfg="init+update+final aligned buffer"

Jan 18 21:59:42 alarm kernel: alg: self-tests for safexcel-cmac-aes (cmac(aes)) failed (rc=-22)
Jan 18 21:59:42 alarm kernel: WARNING: CPU: 1 PID: 405 at crypto/testmgr.c:5753 alg_test+0x1e8/0x4b0
Jan 18 21:59:42 alarm kernel: Modules linked in: tag_dsa mv88e6xxx(+) dsa_core bridge stp llc sfp crypto_safexcel(+) mdio_i2c marvell mvpp2 authenc libdes phylink mvmdio armada_thermal sbsa_gwdt fuse
Jan 18 21:59:42 alarm kernel: mv88e6085 f212a200.mdio-mii:03: configuring for inband/2500base-x link mode
Jan 18 21:59:42 alarm kernel: CPU: 1 PID: 405 Comm: cryptomgr_test Tainted: G W 5.19.8-1-aarch64-ARCH #1
Jan 18 21:59:42 alarm kernel: Hardware name: Globalscale MOCHAbin (DT)
Jan 18 21:59:43 alarm kernel: pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
...skip...
Jan 18 21:59:43 alarm kernel: Call trace:
Jan 18 21:59:43 alarm kernel: alg_test+0x1e8/0x4b0
Jan 18 21:59:43 alarm kernel: cryptomgr_test+0x2c/0x50
Jan 18 21:59:43 alarm kernel: kthread+0xe4/0xf0
Jan 18 21:59:43 alarm kernel: ret_from_fork+0x10/0x20
')
Mettacrawler
 
Posts: 56
Joined: Sun Mar 18, 2018 7:19 pm

Re: [Request] MochaBin Installation Guide

Postby technosf » Mon Jan 23, 2023 2:40 am

I'd be interested if MACCHIATObin users also have found that when they updated their kernels that $this->bbcode_second_pass_quote('', 't')he crypto fell off and 20,000 gallons of entropy was dumped into the sea
.

Perhaps someone can tow a new build outside of the environment and figureout which switches to twiddle so it all the front won't fall off in new builds.
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 130
Joined: Sat Jan 08, 2011 10:54 pm

Re: [Request] MochaBin Installation Guide

Postby technosf » Mon Jan 23, 2023 4:56 am

I hope to try and get to reinstalling this week, and will blacklist the kernel in pacman.

This does bring up the thought of backups and restores. I like and endorse BTRFS for this very reason, among others, and if I can get MochaBin booting off BTRFS it might be time to look at getting a timeshift package def, and perhaps grub-btrfs too to help with wayward kernels.
[size=85] MochaBin 5G || NSA325 [/size]
technosf
 
Posts: 130
Joined: Sat Jan 08, 2011 10:54 pm

Re: [Request] MochaBin Installation Guide

Postby jayce » Tue Jan 24, 2023 2:48 pm

I followed the guide (also blacklisted the kernel).

But two USB-hubs are missing in arch.

The lsusb with OpenWrt SNAPSHOT r21826-26c095cb4d shows:
$this->bbcode_second_pass_code('', 'Bus 003 Device 002: ID 0424:2134 SMSC USB2134B
Bus 002 Device 001: ID 1d6b:0003 Linux 5.15.88 xhci-hcd xHCI Host Controller
Bus 004 Device 003: ID 13fe:6000 USB DISK 3.0
Bus 004 Device 002: ID 0424:5534 SMSC USB5534B
Bus 004 Device 001: ID 1d6b:0003 Linux 5.15.88 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.88 xhci-hcd xHCI Host Controller
Bus 003 Device 001: ID 1d6b:0002 Linux 5.15.88 xhci-hcd xHCI Host Controller')

In arch lsusb only shows:
$this->bbcode_second_pass_code('', 'Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub')

Now the external USB-ports are not working (see e.g missing USB DISK 3.0 in the arch output).

Anyone got the same issue?
jayce
 
Posts: 1
Joined: Tue Jan 24, 2023 2:28 pm

Re: [Request] MochaBin Installation Guide

Postby Mettacrawler » Wed Jan 25, 2023 2:52 am

I got networking to work on 5.19. The trick is to just stay away from that crypto stuff.
https://www.theonion.com/man-who-lost-everything-in-crypto-just-wishes-several-t-1848764551

$this->bbcode_second_pass_code('', '$ cat /etc/modprobe.d/crypto_safexcel.conf
blacklist crypto_safexcel')
There's supposed to be a working EIP-97 device on some Marvell boards. I don't know if the Mochabin has one or not. I just know that the networking will break if the module is installed and you are running Linux 5.19.8.

USB works on the Ubuntu 18.04 the device ships with, but not on linux-aarch64 (5.19.8) and linux-aarch64-rc. (6.0.0-rc5)
Ubuntu 18.04 from Globalscale has Linux version 5.4.163-00034-ga7e9e3c22288 based on an LTS.
OpenWrt 22.03.3, r20028-43d71ad93e has kernel 5.10.161 LTS.
Robert Marko and and Pali Rohár have contributed to the mainline Linux, there's a good chance that USB would work on 6.1 or 6.2.
Mettacrawler
 
Posts: 56
Joined: Sun Mar 18, 2018 7:19 pm

Re: [Request] MochaBin Installation Guide

Postby Mettacrawler » Fri Feb 03, 2023 1:52 pm

I got USB to work. This parameter needs to be set:

CONFIG_PHY_MVEBU_CP110_UTMI

That parameter does not exist in the old kernel versions used on Ubuntu 18.04 and OpenWRT. Linux 5.18 onward has it (older versions might have it too, I didn't check).

Some documentation is here:
https://www.kernel.org/doc/Documentation/devicetree/bindings/phy/marvell%2Carmada-cp110-utmi-phy.yaml

$this->bbcode_second_pass_code('', '$ uname -srv
Linux 6.1.9-1-aarch64-ARCH #1 SMP PREEMPT Fri Feb 3 12:54:09 EST 2023

$ zgrep CONFIG_PHY_MVEBU_CP110 /proc/config.gz
CONFIG_PHY_MVEBU_CP110_COMPHY=y
CONFIG_PHY_MVEBU_CP110_UTMI=y

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0424:5534 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0424:2134 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub')

It is no longer necessary to blacklist the crypto_safexcel module, networking is operational with it loaded, but these message are still emitted:

$this->bbcode_second_pass_code('', 'alg: No test for authenc(hmac(sha224),cbc(aes)) (safexcel-authenc-hmac-sha224-cbc-aes)
alg: No test for authenc(hmac(sha384),cbc(aes)) (safexcel-authenc-hmac-sha384-cbc-aes)
alg: No test for authenc(hmac(sha224),rfc3686(ctr(aes))) (safexcel-authenc-hmac-sha224-ctr-aes)')

See this forum thread for discussion about Linux 6.1.10
viewtopic.php?f=23&t=16280&p=70651#p70651

The pull request for the update is here:
https://github.com/archlinuxarm/PKGBUILDs/pull/1984
Binary packages of the work-in-progress can be found here:
https://github.com/lynix/linux-aarch64-bin
Mettacrawler
 
Posts: 56
Joined: Sun Mar 18, 2018 7:19 pm

Next

Return to ARMv8

Who is online

Users browsing this forum: No registered users and 8 guests