lanefu
-
Posts
1339 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by lanefu
-
-
does Armbian image use same DDR blobs as Joshua's?
-
3 hours ago, pkfox said:
does this use NetworkManager ?
I believe so. The other Armbian user space tools for networking do.
-
11 hours ago, ReneHegewald said:
if work with Sata1 from Kernel "6.8.2-edge-rockchip-rk3588" .. works fine
There are rk3588 edge overlays available for SATA
https://github.com/armbian/build/tree/main/patch/kernel/rockchip-rk3588-edge/overlay
-
don't know if this method still works but thought i'd share it
https://github.com/armbian/documentation/issues/116 -
You would need to use the Armbian build tool to build a custom kernel with the missing modules such as tcp-nvme.
The Linux-modules-extras won't be an option in Armbian because it's only to supplement a specific corresponding Debian official kernel.
-
Try using Armbian builder to build an image there is a 4se config in there
I added it after helping some one in irc one night. I don't recall the state. I don't have a 4se
https://github.com/armbian/build/blob/main/config/boards/rock-4se.csc
-
I believe those accelerations are only available on rklinux using the legacy/vendor kernel.
Armbian's Odroid M1 does not support rklinux only mainline linux.https://github.com/armbian/build/blob/main/config/boards/odroidm1.conf#L6
-
11 hours ago, wasuu said:
Is it possible to just use the dts file from the friendly elecs github repository ?
nope that's from the rockchip 6.1 vendor kernel. It's not compatible with mainline linux
-
On 1/11/2024 at 8:33 PM, Dysmas said:
@LiX, could you make your work available somewhere ? Either the full build or the things you have modified and some short indications to help me build, I am not familiar with armbian yet. I know the R5S version works on the R5C, but with the problems of the leds and the ethernet ports names.
LiX's Nanopi-R5C CSC stuff is in the Armbian build tree, but no automated community images are being published currently.
Unofficial unsupported R5C builds here:
https://refuge.armsurvivors.icu/lanefu/lanefu_24.2.0-trunk_Nanopi-r5c_bookworm_current_6.6.13/https://refuge.armsurvivors.icu/lanefu/lanefu_24.2.0-trunk_Nanopi-r5c_sid_edge_6.7.1/
-
This won't feel very helpful, but basically you'll need to make a device tree for the cm3588 nas board.
I've yet to find a good read on introducing people to device tree and how to navigate but hopefully you can find something.
Example:
https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dts
-
On 11/18/2023 at 9:55 PM, lanefu said:
Okay new discovery.. seem's to be a drive-specific issue....
Experiencing Issue with no init on boot issue on -- Samsung SSD 860 PRO 256GBUser here had similar issues with EVO 860
Weirdest coincidental solution ever. Guessing early console some how gave more time for the drive to init in time?
-
Okay new discovery.. seem's to be a drive-specific issue....
Experiencing Issue with no init on boot issue on -- Samsung SSD 860 PRO 256GBI have another device working fine on boot.. no issue. -- Samsung SSD 860 EVO 500GB
even tried moving both drives around different slots. Behavior was consistent -
Another me too
Drives don't initialize on boot.. ATA ports show down... if i hot plug a drive, it comes right up.
Observed issue on fresh kernel builds of
6.1.626.6.1
Tried fresh uboot from edge as well.
-
Make sure you're building with EXPERT=yes
The rk3588 edge kernel is already 6.6 rc1
https://github.com/armbian/build/blob/main/config/sources/families/rockchip-rk3588.conf#L32
-
54 minutes ago, lanefu said:
nanopi-r5s has been added in a community support configuration. It is available via the EXPERT mode of the builder. It requires EDGE kernel, but mainline support is good
here's an unsupported, unofficial build. Mainline kernel, Mainline Uboot.https://refuge.armsurvivors.icu/lanefu/lanefu_23.08.0-trunk_Nanopi-r5s_bookworm_edge_6.5.3/
-
nanopi-r5s has been added in a community support configuration. It is available via the EXPERT mode of the builder. It requires EDGE kernel, but mainline support is good
https://github.com/armbian/build/blob/main/config/boards/nanopi-r5s.csc
I'm using as a router on debian sid via the clammy-ng router framework
-
5 hours ago, Dianne S. said:
When I replaced rk3399-pinebook-pro.dtb with the version from Kali Linux, it booted, I got the display, and everything worked. I now finally have Armbian running from the emmc, albeit with the device tree blob from Kali Linux.
When was your PBP made? Is it from one of the newer production runs from past year?
Mines from 2nd gen. (Pre covid era) I remember seeing Kali had a few extra patches for the newer PBPs
-
7 minutes ago, Dianne S. said:
I have a USB-to-emmc adapter. If I were to simply write the image directly to the emmc from my workstation, would that be expected to work?
Yep writing image directly to emmc should be fine. Has been the case historically for me.
-
I downloaded xfce for PBP from armbian website, flashed to sdcard with etcher and booted successfully.
Caveat I don't have emmc chip installed and nothing on SPI.
So yeah could easily be manjaro uboot allergies to trying to pivot to armbian to boot.
If possible just wipe emmc
-
The quickest fix for the user will be to use armbian-config to select a mirror.
The redirector dev may be able to add some exceptions but geoiop data will never be 100% accurate
-
Don't confuse current circumstance with an overt decision. What have you done to troubleshoot and participate in diagnosing and solving the problem?
Also look-up maintainer
-
The Armbian images shrink the filesystem down to a minimal footprint that then expand to the max of the sdcard on first boot. You're cloning the image after it's been expanded from first boot stage
You'll want to shrink the root file system and the partition before imagine.
Rather than making a golden image, using the Armbian build tool and the customize image hooks to install your packages would be a more appropriate solution
-
On 5/14/2022 at 4:34 AM, Cucaracha said:
I have the same issue and I've tested the script with the --delete option. The change solved my issue. Before I had about 74 MB in /var/log.hdd/journal. After the change and executing the cronjob I have about 7 MB now. So the ramdisk will not be overfilled anymore.
I've created a pull request with this small change: https://github.com/armbian/build/pull/3779
thank you! merged! -
Or I guess Balbes support is free and easy.
Note this is balbes and not official support status
RockPi 5b / Kernel 6.8.2 / dtb overlay
in Rockchip
Posted
That should be resolved as of this PR
https://github.com/armbian/build/pull/6580