Search the Community
Showing results for tags 'nanopct4'.
Found 25 results
-
I can't get HDMI output in RK3399 board Nano PC T4, what I have tried https://dl.armbian.com/nanopct4/Noble_current_gnome-kisak https://dl.armbian.com/nanopct4/Bookworm_current_minimal the SSH is working I can only get a black screen on HDMI Kernel 5.x (Armbian 22) works
-
Now the mainline u-boot has decent pcie and pcie phy driver for rk3399. The only deficiency is the clock of pcie phy not included. The first attached patch add this clock so that u-boot proper can load linux kernel residing in an ext4 partition of nvme ssd.pcie_phy_clk.patch The second patch enables loading the environment from a file in an ext4 partition of nvme ssd.env_nvme.patch More conveniently the u-boot proper(u-boot.itb) could be an ordinary file residing in an ext4 partition of nvme ssd. The idbloader(tpl/spl in spi/emmc/sdcard) could load it if pcie nvme support is enabled in spl. That's the third attachment.spl_nvme.patch The usb and usb phy is working so the usbkbd can be used to choose a boot option without a serial port debug console. The last attachment set the default env to enable usbkbd and vidconsole.env_vidconsole_usbkbd.patch And for your convenience my u-boot config for nanopc-t4 also attached here.u-boot.config
-
It does not matter which of the lastest Images I am downloading for the NanoPC T4, none of them is showing any sign of boot sequence. I flashed the images with balena etcher to the SD-Card before. I thought writing the image with etcher to SD-Card is all I need to do. My old system Shaitan with OMV is booting from SD-Card witout any issue. I have no idea, why none of the newer Images escpecially for the NanoPC T4 is not booting at all. Does someone has any idea?
-
Hello, I have been building images for the NanoPC-T4 with armbian successfully in the past. However I now get the error "could not resolve 'ports.ubuntu.com'" when the build tries to install ping_5.1-1_arm64.deb (full log below). Do you have any idea what this comes from and how I could solve/debug this ? Thank you Additional info : I added 8.8.8.8 as an alternative DNS server on my machine, I can ping ports.ubuntu.com successfully. I have cloned the armbian build and head points to this commit https://github.com/armbian/build/commit/5b8d86ae5f6f34cf6cc13edf6b1def2773f66f0a Best regards, Rick -
Hello, i'm using the NanoPC-T4 with Armbian Bookworm (23.8.1 with Linux 6.1.63-current-media) Kernel and Mainsail/Klipper is running on in smooth and gently. Since i want to record timelapse videos, i've decided to buy the orginial "FriendlyELEC Cam1320 PI Camera Module" based on the OV13850. I've connected it in the expectation that it should work together. But the System is not detecting the camera module. $ v4l2-ctl --list-devices rockchip,rk3399-vpu-enc (platform: hantro-vpu): /dev/video2 /dev/video4 /dev/media1 rockchip-rga (platform:rga): /dev/video0 rkvdec (platform:rkvdec): /dev/video3 /dev/media0 rockchip-iep (platform:rockchip-iep): /dev/video1 I found a project which contains patches for the camera module, is there any way to see if these patches are integrated in the armbian kernel? And if not, is it possible to add these patches or is there a way to build a custom kernel with these patches easily? Or am I looking at the wrong place?
-
Hi, since latest upgrade to new kernel 22.02 stable the system becomes unstable. There are issues writing to mmc2 and "EXT4-fs (mmcblk2p1): Remounting filesystem read-only". This does not allow most of the apps to work properly (e.g. openmediavault stops working) I tried to switch back to previous kernel version through armbian-config but that does not work too Pls help. Thanks -
After recent kernel update, USB3.0 ports no longer work, There is an error printed in kernel log. [ 2.826383] phy phy-ff800000.phy.6: phy poweron failed --> -110 [ 2.827119] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core [ 2.827881] dwc3: probe of fe900000.usb failed with error -110 I found this issue in NanoPC T4, but it might also appear in other RK3399 boards. lsusb didn't show any USB3.0 controller. Confirmed this isn't my hardware's problem, another board have this issue too. dwc3.txt
-
I don't have a NanoPC-T4, but I have a NanoPC-T6 which I mainly bought because of the Dual Camera options of the MCAM400 on the T4 and the high-speed encoding properties of the Rockchip... those possibilities should be very similar for the T6 actually... Whatever, the camera configuration seems to be mostly here but I struggle to do the similar thing with the device tree of the T6... Anyone who has an idea about this and is willing to help me with that?
-
NanoPC-T4 My above board successfully installs and is accessible via SSH on all of the following releases. Armbian Bullseye Server and Desktop Armbian Bookworm Server and Desktop Armbian Jammy Desktop In all cases neither the CLI Screen or the desktop screen ever show up via the HDMI. Ive changed HDMI cable, different monitor and different PSU I wondered if there any CLI commands that might help my confirm what the fault is or if the board is broken? Thanks for any help!
-
Hello, I have been trying to get back to a working nanopc-t4. I'm traveling with an almost worthless computer since I accidently let armbian update itself. The next few days I have access to a TV. To get my screen to work I convert the - media - version to support dtb overlays, the build the driver and overlay. This needs the build in the modules to be present. Using uname -r gives me this path. usr/lib/modules/6.2.0-rc8-media/build I can install Linux headers through armbian-config. That does nothing for allowing make in the modules which is what I need. What am I missing and how do I get it? I have installed kernel source and headers and build essential. Thank you
-
How to use GPIOS like the FriendlyELEC's official system? Wiringpi does not work on Armbian, can you adapt the Armbain system of Nanopc T4 to Wiringpi? -
Hello, I stupidly upgraded without thinking about the possible consequences. 6.1 to 6.2. Ive had my /home on nvme. But the nvme drive is no longer recognized. I have managed to get my display back, Im not sure about my panel yet. I had restore my device tree overlay. Ive hacked around losing the nvme. But it would be good to get my nvme drive back. I've got some work to do to deal with not having that storage and what was on it. Can anyone point me in the right direction? Alternatively, maybe it's not too hard to roll back to 6.1? I haven't contemplated that.
-
So, I tried to adapt @Kwiboo and @jernej patches on my 5.6 branch, but this made the kernel fail to boot for no visible reason. Since I were able to boot it without the VPU patches, I'm convinced that it's their readaptation that broke something. The patches applied are here : https://github.com/Miouyouyou/RockMyy64 If someone wants to play with them and determine which one break the boot process.
-
I've built everything into the kernel that I can think of: Device Drivers ---> [*] USB support --> [*] USB Type-C Support --> ** built everything other than alternative mode / display port drivers [*] PHY Subsystem ---> ... [*] Rockchip TYPEC PHY Driver Nothing seems to get it working (other than using the legacy kernel). If I plug in a USB type-c ethernet adapter, the light stays on solid but nothing shows up under lsusb.. I'm not sure what else to try. Any help would be appreciated. -
NanoPC-T4 only has 16GRAM, which is still a bit small for daily use. So I want to put u-boot on emmc or sd card, and install the system on nvme solid state drive. If I want to realize this function, can the armbian-config tool help me realize it quickly? Or do I need to set u-boot parameters and compile by myself, thus installing the system in nvme SSD? -
I bought a NanoPC-T4 development board designed by friendlyelec and installed the Armbian operating system. But the heat generated by the Rk3399 main control chip is too high. I bought an official PWM fan. According to the official wiki, the fan can work normally. However, under the same configuration under Armbian, the fan can’t work normally, so I What work needs to be done? Thanks.
-
Hello, I have had a nanopc-t4 and a few others for a long time now. I have tried to create a working dtb for it a few different times. My understanding of device trees is superficial I have not had good success. I have read the kernels DT docs many times. I can of course run an ancient 4.19 kernel but I would much rather be at the edge. Currently I've got armbian 22, but no edp. I can boot Friendly's lubuntu and then the edp works. Although it is edp or hdmi not both. I must unplug the edp to get the hdmi port to work. Which is really undesirable. If I remember, it can only enable 2 of its 3 hdmi ports at a time, so that is likely a simple DT change. I am wondering if it is even reasonable to wish for a working edp port with a modern kernel on any arm board. Or if possibly someone has a device tree for it that enables the edp. I have not tried an LTS version of armbian, I'm not familiar with the names and versions. I will look. So I'm wondering if anyone has the edp working or can explain where to look and maybe even why this situation exists where device support is lacking in newer kernels. Any help would be appreciated, Erica
-
Hi, community! I wish you have a nice day! Started investigating why do I have problems trying to hear something from headphones. So, I believe there is something about HDMI audio codec related to panfrost, attached you will find info about. I guess this will be useful to catch bugs. I'm 73 years old, started on computers on NCR Century 100 as field engineer. From those years to now, a long development has brought to life.... Cheers, and many thanks to you! dmesg112222.txt armbianmonitor112122.txt
-
root@nanopct4:/home/paco# pulseaudio -check pulseaudio: opción inválida -- 'c' E: [pulseaudio] main.c: Falló al analizar la línea de comando.
-
I planned to upgrade and skip current 5.18 (EOL) with edge 5.19 or just use LTS 5.15. Offcial images 5.19/edge (e.g. Armbian_22.08.1_Nanopct4_sid_edge_5.19.5.img.xz) won't boot at all, maybe a short uboot screen. Using uboot v22.04 like other rk3399 boards did not fix it. SInce the nanopct4.conf is boardfamily=media but also works with rockchip64 (which was changed some time ago), building with boardfamily=rockchip64 current 5.15 or edge 5.19 works fine, the cli builds boot as expected. Maybe a general question, which bordfamily fits now best to nanopct4. I remember exactly problems which were fixed bei 150balbes maintainer when pulling it to media. Thankfully all patches found their way to rockchip64, which seems to be more active for rk3399 in general. Do you have any plans to combine them again? -
root@nanopct4:/boot/overlay-user# armbian-add-overlay lcd-mipi-opi4.dts Armbian is not installed properly. Missing armbian-release or armbianEnv.txt I found 22.08 using extlinux.conf instead of the legacy set of boot.scr + text files. That will miss overlay function when using extlinux ?
-
Hello everyone, I want to use uart4 port for zigbee2mqtt,but I don't know how to activates it.
-
Test version with EFI\Grub support (with HDMI output) for rk3399. for station p1 https://disk.yandex.ru/d/HZ34T76zxS9pnw for nanopc t4 https://disk.yandex.ru/d/SjBMYJ37U6699A firefly-rk3399 https://disk.yandex.ru/d/BfrzRRyvdtavIg
-
I have a weird issue where I have everything working as I want it a few different services running in docker (Pi-Hole, Motioneye, Home Assistant, Emby) and all their individual management pages are accessible. However as soon as i move the install over to emmc, all networking seems to break, with services no longer working, but some admin pages report everything is fine. Pi-Hole for example shows as running but no devices accessing the dns cant load webpages and the pi-hole management pages stop showing any further queries received. ive repeated the process of doing a clean install to sd , everything fine. move to emmc stops working ☹️ -
https://github.com/sigmaris/u-boot First I tried the mainline uboot v2022.04 version and the sigmaris uboot, in the uboot command line I executed the nvme info command and found no nvme devices available. https://github.com/radxa/u-boot Since the radxa version does not have the relevant configuration files for nanopc-t4, the compilation and testing of the radxa version is abandoned. Is the patch in this thread for the mainline v2020.04 release? @piter75 @Hover
