Jump to content

Search the Community

Showing results for tags 'orangepi-rk3399'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 2 results

  1. I have my RK3399-based device booting with my own working kernel and device tree. I want to erase the root partition and install Debian from one of the official ARM distros, but I'm not sure how to do this. Obviously, I can't just boot into the Debian installer like on an X86 machine. What I think I need is a root partition of a vanilla Debian install, because then I can just point U-boot to the root partition and Debian should boot (hopefully into an installer). What's the best way to proceed?
  2. I've got an OrangePi based on the Rockchip RK3399. The official OrangePi Debian version I'm using is Armbian-based I believe and uses a 5.10 kernel. I want to upgrade the kernel as later ones support some video features of the RK3399 I want to use. The problem is, if I build the kernel using the standard vanilla method from kernel.org sources even using the same config file from the running kernel without changing anything (make olddefconfig), the device won't boot when I symlink the new kernel to /boot/Image. Interestingly, it does boot if I symlink the new initrd to /boot/uInitrd, but only with the old kernel. Is there something special I need to do to the kernel that Armbian expects? Are there required secure keys or anything that u-boot expects that aren't in my new kernel? I thought the problem might be missing kernel patches, but as far as I know RK3399 support is mainlined already, so new kernels should support it. Any help is appreciated!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines