Jump to content

Search the Community

Showing results for tags 'rockpi-4b'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Skype


Github


Location


Interests

  1. IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es". II. Features Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K). - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV. ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed. III. Sources This is the list of the sources used for the packages: IV. FAQ ¿Why did you use Debian Buster as a base for this implementation? It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal. ¿Why Legacy instead of Mainline? This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels. ¿Will you add new features to this implementation? No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
  2. rock@rock-3a:~$ dmesg |grep spi [ 6.279244] spi-nor spi4.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00 [ 6.279275] spi-nor: probe of spi4.0 failed with error -2 the armbianEnv is as below. verbosity=1 bootlogo=false extraargs=systemd.unified_cgroup_hierarchy=0 overlay_prefix=rk35xx fdtfile=rockchip/rk3568-rock-3a.dtb rootdev=UUID=6359cdcb-b9a7-4930-9257-30f4e34b0a4f rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0 param_spidev_max_freq=40000000 Is there anyone know which version is ok for Rock 3a or rock p;i 4b?
  3. Hello, how to get I2C-2 device support in overlay? I have checked /boot/dtb/rockchip/overlay/README.rockchip-overlays and only i2c-7 and i2c-8 seems to be there. GPIO pins are here GPIO2_A0 and GPIO2_A1 https://wiki.radxa.com/Rockpi4/hardware/gpio#Rock_Pi_4A_.2F_4A_Plus_.2F_4B_.2F_4B_Plus_.2F_4C_.2F_4C_Plus.28.3E.3DV1.2.29_general_purpose_input-output_.28GPIO.29_connector Thank you!
  4. This is for those experiencing a similar issue on the Rock Pi 4B (possibly RK3399 in general) who don't have a fix yet. On Armbian Focal current for the Rock Pi 4B the sound from both HDMI and the audio jack stopped working and became undetectable to the system (Both Pulse-audio and ALSA couldn't detect anything except hdmi-sound and even then HDMI sound did not work). I fixed the issue by rolling back to the latest "current" kernel version in armbian-config (5.10.63-rockchip64). Now the system sound has gone back to normal.
  5. Hello. I am finished Armbian Jammy 22.05 Bulseye edge 5.16.20 gnome desktop on a Rockpi4 (rk3399). When I try to overclock from Armbian-config, it doesn't work. That is, I can enter the application, apply rockchip-rk3399-opp-2ghz.dtbo. Then reboot, go to armbian-config and set a new unlocked CPU clock speed of 2.2Ghz. But instead it is only available up to a maximum of 1.8hz. How can this be fixed? Do I have to create an image from scratch, or maybe there is some trick?
  6. With Armbian v20.11 one can write mainline u-boot image to board's SPI and enjoy booting nvme drives without any mmc devices. Prerequisities: ROCK Pi 4(A/B/C) v1.4 or 1.3 with SPI soldered in (v1.3 comes without SPI flash from the factory). If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot If you shorted 23-25 pins in 1.) then: disconnect them after the ROCK Pi 4 fully boot's enable spi-nor by executing (as root): echo spi1.0 > /sys/bus/spi/drivers/spi-nor/bind verify that the SPI mtd interface is enabled by running ls /dev/mtdblock0 if the last command does not list any file then something went wrong between 3.) and 5.) Run nand-sata-install choose option: "Boot from SPI - system on SATA, USB or NVMe" choose NVMe partition, eg. /dev/nvme0n1p1 accept erasing of the choosen partition with "Yes" choose fs type (tested with ext4) wait a few minutes for rootfs transfer to chosen partition choose writing SPI bootloader with "Yes" confirm that you want to flash it with "Yes" wait ~60 seconds for writing choose Exit Reboot Enjoy Armbian booting with SPI / NVMe Why bother with mainline u-boot? It is known to boot some NVMe drives that legacy u-boot from Radxa has issues with, eg. SAMSUNG 970 EVO Plus and SAMSUNG PM981. This does not mean that all NVMe drives are supported, YMMV. Which NVMe drives are known to be working? Corsair MP510 240GB/480GB/960GB Gigabyte SSD M.2 2280 PCIe x2 Model:GP-GSM2NE8128GNTD HP SSD EX900 M.2 NVMe 120GB. Model: 2YY42AA#ABB Intel SSD 660p Model:SSDPEKNW512GB Kingston A1000 SSD 240GB (PHISON PS5008-E8-10) Kingston A2000 M.2 2280 PCIe NVMe PNY 250GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4 Sabrent Rocket 256GB NVMe PCIe M.2 2280 Samsung 970 EVO Plus SSD 250GB M.2 2280, PCIe 3.0 x4, NVMe, 3500/2300 MB/s Samsung PM981 256GB XPG SX6000 Lite 128GB (ASX6000LNP-128GT-C) Why not using Radxa's u-boot SPI image? Ambian's u-boot configuration is incompatible with Radxa's SPI image Why Armbian is using u-boot that is incompatible with Radxa's? It uses mainline u-boot with Open Source TPL/SPL/proper and BL31 from Rockchip packaged into u-boot and we may switch to using open source ATF instead of the BL31 in the future. Can I boot Radxa's images with Armbian's u-boot written to SPI? Yes. Armbian's SPI u-boot is compatible with Radxa's images available here: https://github.com/radxa/rock-pi-images-released/releases It may not be compatible with some older images (released before July 2020) because of the device tree filename change.
  7. Hello all, I have a RockPi 4B in use and wanted to connect my 7" display from Raspberry via the display port. According to these instructions, it should also work. https://wiki.radxa.com/Rockpi4/hardware/display#Raspberry_Pi_7_inch_Touch_Display But unfortunately I can't find this file under "boot" because I'm using an ARMBIAN image. How can I address this 7" display? Can anyone help me here? Best regards from Berlin Z. Matthias
  8. Hi, I'm using a RockPi 4 B as a wifi access point. Everything is working fine with good performances until the Wifi stop working, usually after 3-4 days. When that happens, dmesg is flooded with these logs : [221057.075187] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221057.075202] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [221124.657840] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217786] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217806] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 Reloading `brcmfmac` module do not fix the issue, only a reboot. I'm using the latest firmware provided by armbian-firmare : # dmesg | grep brcm Jan 28 09:36:13 crumble kernel: [240969.028417] brcmfmac: F1 signature read @0x18000000=0x15294345 Jan 28 09:36:13 crumble kernel: [240969.038152] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.041051] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.radxa,rockpi4b.txt failed with error -2 Jan 28 09:36:13 crumble kernel: [240969.042548] usbcore: registered new interface driver brcmfmac Jan 28 09:36:13 crumble kernel: [240969.149643] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.149719] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available Jan 28 09:36:13 crumble kernel: [240969.149965] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Feb 11 2020 11:54:51 version 7.45.96.61 (be7af2d@shgit) (r745790) FWID 01-a41d86bd es7.c5.n4.a3 I'm not sure where to go from there. How can I debug or workaround this issue ?
  9. I know that not all features of legacy vendor kernels can be supported in mainline kernels. However, has anyone considered and/or attempted to get the OTG capability working in a current/mainline kernel? I have a couple different projects where I need to have OTG working so I can have the RockPi 4 be a USB device (e.g. mass storage, ethernet, etc.). For the time being this means I can only use the legacy kernels, but I am hoping that might change in the future. There are a number of different RK3399 boards with DWC3 controllers that could benefit from such a feature being available, right? Since I don't understand the kernel/driver/platform glue layers well enough to make an attempt myself, I am hoping someone who knows more about this might have some extra info? Is it planned for the future? Too complex? Something else?
  10. I have tried the following: ------------------------------------------------------------------------ CONVERT dtb to dts ------------------------------------------------------------------------ dtc -I dtb -O dts /boot/dtb-4.4.192-rockchip64/rockchip/rk3399-rockpi4b.dtb -o /boot/dtb-4.4.192-rockchip64/rockchip/rk3399-rockpi4b.dts ------------------------------------------------------------------------ EDIT dts ------------------------------------------------------------------------ nano /boot/dtb-4.4.192-rockchip64/rockchip/rk3399-rockpi4b.dts ---------------------------------------------------------------------------------- uart4 enabled: serial@ff370000 { compatible = "rockchip,rk3399-uart\0snps,dw-apb-uart"; reg = < 0x00 0xff370000 0x00 0x100 >; clocks = < 0x31 0x06 0x31 0x22 >; clock-names = "baudclk\0apb_pclk"; interrupts = < 0x00 0x66 0x04 0x00 >; reg-shift = < 0x02 >; reg-io-width = < 0x04 >; pinctrl-names = "default"; pinctrl-0 = < 0x81 >; status = "okay"; assigned-clocks = < 0x31 0x0c >; assigned-clock-parents = < 0x31 0x01 >; phandle = < 0x114 >; }; uart4 disable as it uses the same pins as SPI1: serial@ff370000 { compatible = "rockchip,rk3399-uart\0snps,dw-apb-uart"; reg = < 0x00 0xff370000 0x00 0x100 >; clocks = < 0x31 0x06 0x31 0x22 >; clock-names = "baudclk\0apb_pclk"; interrupts = < 0x00 0x66 0x04 0x00 >; reg-shift = < 0x02 >; reg-io-width = < 0x04 >; pinctrl-names = "default"; pinctrl-0 = < 0x81 >; status = "disable"; assigned-clocks = < 0x31 0x0c >; assigned-clock-parents = < 0x31 0x01 >; phandle = < 0x114 >; }; spi1 is disabled: spi@ff1d0000 { compatible = "rockchip,rk3399-spi\0rockchip,rk3066-spi"; reg = < 0x00 0xff1d0000 0x00 0x1000 >; clocks = < 0x08 0x48 0x08 0x15c >; clock-names = "spiclk\0apb_pclk"; dmas = < 0x41 0x0c 0x41 0x0d >; dma-names = "tx\0rx"; interrupts = < 0x00 0x35 0x04 0x00 >; pinctrl-names = "default"; pinctrl-0 = < 0x4d 0x4e 0x4f 0x50 >; #address-cells = < 0x01 >; #size-cells = < 0x00 >; status = "disabled"; phandle = < 0x106 >; }; SP1 enable: spi@ff1d0000 { compatible = "rockchip,rk3399-spi\0rockchip,rk3066-spi"; reg = < 0x00 0xff1d0000 0x00 0x1000 >; clocks = < 0x08 0x48 0x08 0x15c >; clock-names = "spiclk\0apb_pclk"; dmas = < 0x41 0x0c 0x41 0x0d >; dma-names = "tx\0rx"; interrupts = < 0x00 0x35 0x04 0x00 >; pinctrl-names = "default"; pinctrl-0 = < 0x4d 0x4e 0x4f 0x50 >; #address-cells = < 0x01 >; #size-cells = < 0x00 >; status = "okay"; phandle = < 0x106 >; }; save CTRL-O exit: CTRL-X ------------------------------------------------------------------------ CONVERT (BACK) dts to dtb ------------------------------------------------------------------------ dtc -I dts -O dtb /boot/dtb-4.4.192-rockchip64/rockchip/rk3399-rockpi4b.dts -o /boot/dtb-4.4.192-rockchip64/rockchip/rk3399-rockpi4b.dtb reboot And it never wakes up again! Is there any way to make the SPI working on this board??
  11. Hi there, I have a rockpi 4b running armbian bionic desktop legacy kernel 4.4y on a 128 GB emmc module, I’d like to use this machine as a server. I was just tinkering around with Plex, .bashrc and crontab while all of a sudden the keyboard mapping over RDP changed (e.g. > became ;, ~ became @ etc) (indication of the problem?). I tried to fix this by changing the system keyboard layout and running dpkg-reconfigure keyboard-configuration, this all didnt work. I decided to reboot the machine to see if that would work. After the reboot I could not connect to either RDP or SSH so I decided to connect the machine to a HDMI monitor. This resulted in the following output: Can anyone help me understand what I am seeing here and how this could have happened ? Is this even Ubuntu ? Or is this GRUB ? Where in the boot process is this ? My guess is that the whole EMMC is disconnected but this seems very weird since I did not touch the board in any way. (I have no SD installed) I’m now thinking of solving this problem by attaching the emmc to a sd reader and backing up the etc,home,opt,root,srv,usr and var folder, reflashing the image and putting the folders back. This is however a very destructive process so I hope something less destructive is possible. I also even don’t know if this is going to work since I have no idea how this problem was caused. Can anyone help me please ? Thanx in advance! Thank you in advance
  12. Hello, I think this is my first post here. I am trying to operate an Epson L4150 on-board Rock pi4 b multifunction printer. I was successful in running the printer. But the scanner is another story. Xsane does not recognize it. I have been trying to install the driver which is downloaded from the Epson page, but it is for armhf. I tried a dpkg --add-architecture armhf, then update, but when I try to run install.sh from the Epson driver, it throws error: E: Failed to locate package libboost-filesystem1.58.0 Somebody could help me? Thank you
  13. I recently plugged in a 4TB Seagate Expansion hard drive and it worked fine. After rebooting the Rockpi4B via 'sudo reboot' the drive is not recognised - dmesg shows: [ 3.877060] sd 1:0:0:0: [sdb] Unit Not Ready [ 3.877082] sd 1:0:0:0: [sdb] Sense Key : 0x4 [current] [ 3.877094] sd 1:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 Any ideas?
  14. Hello, I have an ARMBIAN image 08.21.6 kernel 5.10.16 it works very well on rockpi 4B + rev 1.6 I tested the last Kernel but without more success. when we fix the ip address and we up (several times) the eth0 network this one puts to work at a time. Do you have an idea ? Regards.
  15. I loaded both the Raxda Debian OS and the Armbian OS on the Rock Pi 4A+ (4GB RAM / 32GB eMMC) integrated eMMC chip and both boot fine. I then ran the Phoronix pts/scikit-learn benchmark and got a big discrepancy in performance: https://openbenchmarking.org/result/2112285-NE-2112281NE08 The Raxda Debian OS (noted as rockpi4a+raxdadebian in the benchmark) performs basically the same as the Rock Pi 4A version (noted as rockpi4-rk3399 running Armbian), as expected. The Armbian OS (tested multiple times as rockpi4a-emmc, rockpi4a+, rockpi4a+governor, and rockpi4a+armbian) all perform terribly. Thoughts?
  16. Greetings ! I am new to Armbian , I am using Rockpi4B for our development . I have successfully built and checked the working of the image. We have few developed application and service files . How can I include these applications and service files as a part of Armbian image. Thanks in Advance
  17. Hi there, i'm trying to getting Armbian working on my RockPi 4B. Installation and everything went fine. Even my Intel 660 2TB NVMe SSD was detected as I booted the SD card Image (created with Etcher). But as I booted the image from eMMC (flashed the image via dd if=image.img of=/dev/mmcblk1); it booted fine so far, but it doesn't detect the NVMe SSD... If I return to uSD Boot, it is detected again... Here is the log output of dmesg | grep nvme from "Boot from eMMC" root@rockpi-4b:~# dmesg | grep nvme [ 2.754457] nvme nvme0: pci function 0000:01:00.0 [ 2.754688] nvme 0000:01:00.0: enabling device (0000 -> 0002) [ 64.489438] nvme nvme0: I/O 0 QID 0 timeout, disable controller [ 64.597365] nvme nvme0: Device shutdown incomplete; abort shutdown [ 64.598050] nvme nvme0: Identify Controller failed (-4) [ 64.598064] nvme nvme0: Removing after probe failure status: -5 Here is the log output of dmesg | grep nvme from "Boot from SD" root@rockpi-4b:~# dmesg | grep nvme [ 2.218883] nvme nvme0: pci function 0000:01:00.0 [ 2.218955] nvme 0000:01:00.0: enabling device (0000 -> 0002) [ 2.470965] nvme nvme0: 6/0/0 default/read/poll queues [ 2.473631] nvme0n1: p1 p2 Any idea what went wrong and how to fix it?
  18. Hello all, I have a question today regarding ARMBIAN - Linux and the configuration of the ZRAM .... Under the ARMBIAN for RockPI 4 I have a ZRAM for the SWAP and a ZRAM for /var/log. Is it possible that I change this configuration and use the eMMC memory for these two areas? Because the big problem with /var/log is that it is simply too small and thus constantly runs into "ERROR" -> volume full. Thank you very much and I am looking forward to constructive contributions to solve my problem. Kind regards
  19. Hello together, I have a RockPI 4B board with the extension for M.2 SSD applications. I wanted to install a 120 GB SSD disk, but unfortunately I cannot find it under "fdisk -l". Can anyone help me here with what I can do? Are there any tricks or the like to make this work? Kind regards Z. Matthias
  20. pi@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchipes8316c [rockchip,es8316-codec], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMICODEC [HDMI-CODEC], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 pi@rockpi-4b:~$ How is it possible to turn on the sound on HDMI? There is sound on the 3.5mm socket. But when I click on the speaker in the top right, then Volume Control. Only "Analog Output" can be selected as output devices.
  21. mboehmer

    Rock PI 4

    Hi all, a new RK3399 board appeared, it is called RockPi4 I have two of these beasts here already, and they works nicely - I like the small details about it (nice eMMC fixture, all heat plates on the bottom side for simple cooling, and an M.2 PICe slot for my second network card Do you see any chance to get Armbian working on that beast, and if so, what can *I* do (with my limited experience in kernel programming)? Debian is working on it already, in case you need more specific information please let me know. Any help is appreciated. So far, Michael
  22. I have 2 issues in LibreOffice installed by default in Armbian, running on RockPi 4B. First: special characters aren't working. Second: filenames or folders using special characters are not recognized - therefore I can't access or edit my files, and even can't save files with special characters... anyone has a tip to solve these two issues? Thanks a lot
  23. I understand that this problem is not related to armbian. I tries asking NexDock but they don't know how to make it. So, I just wonder anybody knows how to let armbian on Rock PI4B work with NexDock 360's keyboard ? I know when using Raspberry PI, I can add a line dtoverlay=dwc2,dr_mode=host to /boot/config.txt. But when using armbian, there is no config.txt in /boot. Thanks.
  24. Dear Armbian supporters, Using kernel 5.10.21-rockchip64 on Rock Pi 4 (and 5.10.21-sunxi on Lime2), I am not able to mount a LUKS-encrypted drive. Changing the kernel to 5.10.16-rockchip64/5.10.16-sunxi I am able to mount the LUKS-encrypted drive again. Error message when trying to mount the drive is: "No key available with this passphrase". Which change could have introduced this bug? Greetings a5s397
  25. Problem: No usb power on all ports except for OTG port on Rock Pi 4C. Images: Ubuntu Bionic Legacy Desktop, Ubuntu Focal Legacy, Ubuntu Focal Current Desktop Monitoring information: Ubuntu Bionic Legacy Desktop - http://ix.io/2wlL Ubuntu Focal Current Desktop: http://ix.io/2wlZ
×
×
  • Create New...