forked from codedude/SBC-Testing
Compare commits
6 Commits
| Author | SHA1 | Date |
|---|---|---|
 Bryan Zuelly
|
fdb0448df7 | |
|
Bryan Zuelly
|
92e5cd2db6 | |
|
Bryan Zuelly
|
b2be1ddaee | |
|
Bryan Zuelly
|
fe34d49e6a | |
|
Bryan Zuelly
|
abdd77c2eb | |
 Pratham Patel
|
7437eda814 |
|
|
@ -1,2 +1,3 @@
|
|||
# SBC-Testing
|
||||
|
||||
See testing/2ndRound.md for current testing details.
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
- [2nd Round of Testing](#2nd-round-testing)
|
||||
- [Issues](#issues)
|
||||
|
||||
<a id="2nd-round-testing"></a>
|
||||
### 2nd Round of Testing
|
||||
The 2nd round of testing will include the same as before except that we'll use U-Boot from the Rocky Linux U-Boot Tools package. We'll continue testing the 6.6.x kernel branch.
|
||||
|
||||
| | Tritrium H5 | Le Potato AML-S905X-CC | La Frite AML-S805X-AC | Renegade ROC-RK3328-CC | Odroid-N2 |
|
||||
|:---:|:---:|:---:|:---:|:---:|:---:|
|
||||
| Kernel SBC support | Passed | Passed | | | Passed |
|
||||
| Vendor U-Boot | Not Tested | Passed | | | Not Tested |
|
||||
| Rocky U-Boot | Passed | Failed* | | | Passed* |
|
||||
| USB | Passed | Passed | | | Passed |
|
||||
| Video | Passed | Passed | | | Passed |
|
||||
| Wi-Fi | N/A | N/A | | | N/A |
|
||||
| Ethernet | Passed | Failed | | | Passed |
|
||||
|
||||
*Amlogic U-boot binaries must be fip-signed with Amlogic's tools.
|
||||
|
||||
<a id="issues"></a>
|
||||
### Issues
|
||||
As of 18 January 2024:
|
||||
Amlogic boards must have their U-boot binaries fip-signed. Currently, this affects both the Le Potato and the Odroid-n2. Check the official u-boot docs for additional information. Amlogic requires written permission for using its signing utilites (if i'm reading it correctly.)
|
||||
Le Potato has issues with the ethernet adapter constantly resetting and is currently non-functional.
|
||||
The Odroid N2 is functional other than "reboot" doesnt work and non-functional usb during U-Boot which stops the boot process(although sometimes it has booted so fast you couldnt get even press a key if you wanted to). The "reboot" error is something to the effect of "watchdog didnt stop". Other than that, it seems to work if you can get it to boot on its own.
|
||||
|
||||
As of 21 January 2024:
|
||||
The strange Le Potato issues with the ethernet adapter is related to uboot. It only happens while using the uboot binary from the Rocky Linux U-Boot-Tools package. Using the LibreTech uboot binary, the issue goes away. I suspect there is a piece of the Le Potato U-boot that is not fully upstreamed.
|
||||
|
||||
Fedora is support on the same Libre boards we are testing. They use the libretech provide U-boot. Can we do the same for this handful of boards? (or at least the ones with issues, so far the Le Potato)
|
||||
|
|
@ -2,8 +2,7 @@
|
|||
- [Testing Requirements](#testing-requirements)
|
||||
- [Initial Testing Libre](#initial-testing-libre)
|
||||
- [Initial Testing Summary](#initial-testing-summary)
|
||||
- [2nd Round of Testing](#2nd-round-testing)
|
||||
- [Issues](#issues)
|
||||
|
||||
- [thefossguy](#thefossguy)
|
||||
|
||||
<a id="testing-requirements"></a>
|
||||
|
|
@ -29,19 +28,30 @@ The table above shows the results for intial testing of ```kernel-mainline-sbc``
|
|||
|
||||
As of 3 Jan 2024, the usb issues on the Libre Renegade have been resolved. The Le Potato works fine as well.
|
||||
|
||||
<a id="2nd-round-testing"></a>
|
||||
### 2nd Round of Testing
|
||||
The 2nd round of testing will include the same as before except that we'll use U-Boot from the Rock Linux U-Boot Tools package. We'll continue testing the 6.6.x kernel branch.
|
||||
|
||||
<a id="issues"></a>
|
||||
### Issues
|
||||
|
||||
Rockchip Specific:
|
||||
Turning off that USB config turns off ports on the Renegade but lets us boot on OPi5
|
||||
Turning on that USB config restores USB on the Renegade but borks booting on OPi5(MMC-related)
|
||||
|
||||
|
||||
<a id="thefossguy"></a>
|
||||
### thefossguy
|
||||
|
||||
Considering a pivot to RHEL config + defconfig vs the current Fedora config + defconfig, but it'll take some time.
|
||||
|
||||
|
||||
Old Issues:
|
||||
RK3588[S] specific:
|
||||
There are two configuration options that are unrelated to the MMC subsystem which prevent the kernel in finding an MMC device. The kernel _does boot_, but that is not the "real" kernel which is on the disk, in `/boot/vmlinuz-$(uname -r)`. It is the initramfs, and gets into the dracut emergency shell. Not good.
|
||||
|
||||
Configuration options in question:
|
||||
```
|
||||
CONFIG_ARM_RK3399_DMC_DEVFREQ
|
||||
CONFIG_PHY_ROCKCHIP_INNO_USB2
|
||||
```
|
||||
|
||||
With these options turned off, the kernel does boot into userspace (i.e. you can login via serial/ssh and use it as a normal system). But this means that the USB2.x (I hate the USB naming scheme and won't bother with it) ports on the Libre Renegade SBC (`Libre Computer ROC-RK3328-CC`) stop working. This is confirmed by Bryan (@codedude).
|
||||
|
||||
This means that some other option is interfering with the MMC subsystem. **This is a bad sign**. I (@thefossguy) am unsure how to proceed from here. At the moment, I have found NixOS to work with my manually built U-Boot (v2024.01) and I am diffing that config with the Fedora config (mainly looking at the configs for the clock, mmc, phy and other related subsystems) to see what might be the problem. I don't have any other OS (rather haven't tried any other OS on it, _yet_) for the config comparison.
|
||||
|
||||
<a id="pivot-config"></a>
|
||||
#### Pivot config?
|
||||
I (@thefossguy) am considering to revert from using the Fedora config and go back to the RHEL config. My reasons to consider this move are as following (**but I am not going to do that unless the SIG approves it**):
|
||||
1. Since we are a RHEL clone, it makes sense to use the RHEL config
|
||||
2. For "missing" features:
|
||||
2A. Hardware features not enabled in the RHEL config will be enabled (**and documented as a modification**)
|
||||
2B. Since we are a RHEL clone--and not a Fedora clone--I don't think that anyone will complain for missing features like btrfs, but those can be enabled if someone is willing to test+support feature X
|
||||
3. Since RedHat will not accept these config changes (makes sense, they don't support SBCs) we can have our own "list" of "here's what we have added on top" which can be "advertised" during download/in the readme and could be a differentiating factor over other clones (healthy competition?)
|
||||
|
|
|
|||
Loading…
Reference in New Issue