Jump to content

Search the Community

Showing results for tags 'orangepi3b'.

  • 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

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 12 results

  1. Hello, I'm trying to install Armbian using `armbian-install` on NVMe, with bootloader on eMMC. I have installed 64GB Foresee eMMC module and 256GB WD SN530 2242 SSD. When I boot from SD card, both storages are detected. Using fdisk, I made them both `dos` (mbr) partitioned. Then I invoke `armbian-install`, it proceeds without any problems using eMMC+sata/nvme/usb option, and I have now 512 MB boot partition on eMMC, the rest of eMMC space as secondary, f2fs partition, and ext4 partition nvme0n1p1 containing the rest of the system. I power the system off, take the SD card out, and boot again.. and I'm stuck in initramfs. From it, I can mount the nvme0n1p1 manually without problems, so the partition is readable and mountable. When I mount nvme0n1p1 as `/` and try to `exit` from initramfs, I am getting kernel panic, but I don't know if it's related or not. It seems to be not a PSU issue (I tried a few 5V 2-3A), not an SD card issue (the system boots and works fine from it), nor the eMMC issue (I installed the system onto the 64GB eMMC only, without nvme, and it worked as well). Tried installing both Armbian_community_24.5.0-trunk.6_Orangepi3b_bookworm_legacy_5.10.160_minimal and Armbian_23.11.1_Orangepi3b_bookworm_edge_6.6.2, both exhibit the same behavior. What's wrong with me and what can I do to fix the boot? I searched for solutions around, but did not find any similar...
  2. I can't activate the orange pi 3b uarts Armbian Community_24.2.0-trunk.540_Orangepi3b_jammy_legacy_5.10.160_gnome_desktop, I did it this way armbianEnv.txt overlays=uart3-m0 uart7-m2 uart9-m2 overlays=uart3 uart7 uart9
  3. I found it very confusing that Armbian doesn't seem to follow the Ubuntu/Debian traditional scheme for naming kernel modules: linux-image-*, linux-modules-* and linux-headers-*. I need them to cross compile out-of-tree kernel module in `schroot`. Armbian seem to have only `linux-image-edge-rockchip64` and `linux-headers-edge-rockchip64`. What's the reasoning behind such design decision? Moreover, I've noticed kernel packages incorporate all the logic that make the board bootable, instead having more generic kernel binaries and relying on `flash-kernel` tool that both Ubuntu and Debian widely use. I wonder why not? What are chances in future `linux-image-*` could be split and have matching `linux-modules-*` package as upstream? Is there any maintained roadmap to figure out most recent supported numbered kernel package, so I could have Orange Pi 3B board with fixed (pinned) kernel version out-of-the-box? Thank you.
  4. Hi, please provide me with link where can I download OS - armbian or ubuntu built for the board OrangePi 3B with RK3566 CPU. http://www.orangepi.org/…tml Thank you very much.
  5. When I boot any variant with kernel 6..x.x from SD there is no problem with hdmi. When I flash the same variant to the nvme, it boots fine but there is no hdmi output. The orange pi logo appears for a second, then nothing. I can ssh in and everthing works fine. Any variant with 5.x.x kernel works fine from the nvme, with hdmi output. What I don't understand is that if I have output to hdmi when booting from sd, why not from nvme. What I think is relevent entries in the boot log is below. mmu fe043e00.iommu: Enable stall request timed out, status: 0x00030b Jan 30 09:38:22 orangepi3b kernel: rk_iommu fe043e00.iommu: Enable stall request timed out, status: 0x00001d Jan 30 09:38:22 orangepi3b kernel: rk_iommu fe043e00.iommu: Page fault at 0x00000000ee086d40 of type read Jan 30 09:38:22 orangepi3b kernel: rk_iommu fe043e00.iommu: iova = 0x00000000ee086d40: dte_index: 0x3b8 pte_index: 0x86> Jan 30 09:38:22 orangepi3b kernel: rk_iommu fe043e00.iommu: mmu_dte_addr: 0x00000001f4ffa000 dte@0x00000001f4ffaee0: 0x> Jan 30 09:38:22 orangepi3b kernel: rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 Jan 30 09:38:22 orangepi3b kernel: rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 Jan 30 09:38:22 orangepi3b kernel: rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 Jan 30 09:38:22 orangepi3b kernel: rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 Jan 30 09:38:22 orangepi3b kernel: rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at Thanks
  6. Do the minimal versions of the distributions still support HDMI ? Specifically orange pi 3b kernel 6.7.2 Thanks
  7. With my bigtreetech 7” hdmi lcd the orange pi 3b does not show image with edge kernel. It works with legacy. if i ssh it to it, dmesg show some error about unsupported mode and no crt connected. best regards Jesper
  8. Hello, As far as i know Orange PI 3B using the Rockchip RK3566, is this SOC support graphic acceleration? I am running Armbian 23.8.2 Jammy with bleeding edge Linux 6.5.2-edge-rockchip64, only 1 tab of Chromium with video player but the CPU reached 100% all time
  9. The image is coped on SD using: sudo dd if=Armbian_23.8.2_Orangepi3b_bookworm_edge_6.5.2.img of=/dev/sda bs=1M status=progress The initial startup is fine (booting, setting of root password, user name/password, wifi setup as well as locales/tzdata). We obtain a system with working internet connection, it can be upgraded using apt etc. However, after reboot wifi fails (the first impression was that we installed something wrong during upgrade phase. However, the sequence: fresh sdcard boot, armbian initialization, reboot (through the reboot command, not a button)) still results in the following: 1708 [ 6.944457] WCN_ERR: read marlin3E chip id fail, ret=-110 1709 [ 6.944506] WCN: marlin_scan_finish! 1710 [ 6.944515] sdiohal:probe ok 1711 [ 6.944740] sdiohal:scan end! 1712 [ 6.944756] WCN: then marlin start to download 1713 [ 6.944802] WCN: marlin_request_firmware from /lib/firmware/wcnmodem.bin start! 1714 [ 6.949062] kworker/0:3: vmalloc error: size 18446744073709551615, exceeds total pages, mode:0xcc0(GFP_KERNEL), nodemask=(null),cpuset=/,mems_allowed=0 1715 [ 6.949147] CPU: 0 PID: 73 Comm: kworker/0:3 Not tainted 6.5.2-edge-rockchip64 #1 1716 [ 6.949162] Hardware name: Rockchip RK3566 OPi 3B (DT) 1717 [ 6.949173] Workqueue: events pre_btwifi_download_sdio 1718 [ 6.949205] Call trace: 1719 [ 6.949212] dump_backtrace+0x94/0x114 1720 [ 6.949230] show_stack+0x18/0x24 1721 [ 6.949241] dump_stack_lvl+0x48/0x60 1722 [ 6.949260] dump_stack+0x18/0x24 1723 [ 6.949273] warn_alloc+0x118/0x1b0 1724 [ 6.949290] __vmalloc_node_range+0x724/0x770 1725 [ 6.949302] vmalloc+0x5c/0x6c 1726 [ 6.949312] load_firmware_data_path+0x64/0x220 1727 [ 6.949327] pre_btwifi_download_sdio+0xe8/0x182c 1728 [ 6.949341] process_one_work+0x214/0x4a0 1729 [ 6.949355] worker_thread+0x6c/0x430 1730 [ 6.949366] kthread+0x104/0x108 1731 [ 6.949377] ret_from_fork+0x10/0x20 Full 'armbianmonitor -U' output is provided here https://pastebin.com/87nvKDsN I hope that somebody might get an idea what's happening inside... Kind regards, al P.S. this result doesn't depend on to which wifi network I'm connected (2.4GHz/5GHz).
  10. I successfully booted this one and connected over Ethernet. Haven't checked WiFi yet. However, the observation comparing to the original Rockchip's Jammy image: the serial port goes quiet after the U-Boot fires up the kernel. The bootloader on the board and the _original_ kernel use non-standard 1500000 baudrate serial speed for the console. I haven't looked into Armbian's guts yet, but I assume it's a matter of right kernel boot arguments for this board to actually spit out kernel output over serial. What I'm not sure is if the console can be cloned between serial and UI over HDMI (console on the frame buffer if I'm right). I'm open to experimentation and pushing a PR, but hints would be welcome where to look at. Thank you. Disclaimer My company has some plans related to RK3366 being proposed as SBC platform to host our products, hence interest in the Orange Pi 3B - the board we're exercising now. But nothing is set in stone yet. If this succeeds, we may commit to certain maintenance efforts at some later date.
  11. Armbian_23.8.2_Orangepi3b_bookworm_edge_6.5.2.img boots, runs, and installs OK on Orange Pi 3B. Tested on 4GB RAM model with 256GB eMMC. - WiFi works* - HDMI audio works - 3D acceleration Panfrost driver works I installed xorg, mesa, x11vnc, jwm, pulseaudio, and flatpak native packages, which was followed by adding Kodi flatpak. Everything worked - with one caveat: there is a delay between keystrokes and output. Typing locally is fine, the problem manifests itself during an inbound SSH connection or when using a remote control app for Kodi on Android mobile. I have tried first replacing pulseaudio with pipewire (no change), making sure that WiFi powersave was disabled (it is by default through NetworkManager conf.d override), then I decided to disable IPv6 in NM system-connections. This had no immediate effect but after some time, likely when the previous IPv6 lease had expired, the delay problem was resolved. [edit] The input delay problem is still there. Looks like it sort of "unclogs" itself once continuous network data flow is received but is always stuck on initial input when characters are not repeated. Any ideas what else to check? [edit 2] This network input delay problem is not exclusive to Armbian. I see the same outcome with Orangepi3b_1.0.0_debian_bookworm_desktop_xfce_linux5.10.160.img and RaspiOS Bullseye kernel 5.10.160. There are no issues when using a third party USB WiFi adapter instead of the onboard chip. Good job Armbian! 👍 So now OPi3B build needs a maintainer.
  12. I have been trying to research this and have come up a bit blank. I am trying to figure out if I need to do anything special to enable panfrost. I have built a jammy and bookworm image using the stable kernel. Both boot fine, but are both using llvmpipe. It does look like its trying to use panfrost. Inside of dmesg: [ 20.098662] panfrost fde60000.gpu: clock rate = 594000000 [ 20.098685] panfrost fde60000.gpu: bus_clock rate = 500000000 [ 20.098820] panfrost fde60000.gpu: Looking up mali-supply from device tree [ 20.099041] panfrost fde60000.gpu: _of_add_opp_table_v2: no supported OPPs [ 20.099287] panfrost fde60000.gpu: devfreq init failed -2 [ 20.099301] panfrost fde60000.gpu: Fatal error during GPU init [ 20.099458] panfrost: probe of fde60000.gpu failed with error -2 I tried building with a newer kernel, but was having issues on boot. I haven't dug into that further yet. Anyone have any thoughts or advise? Thanks
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines