Jump to content

kolsi

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I noticed that new kernels' DTB don't contain dsi/dsi1 nodes and they are currently named mipi_dsi/mipi_dsi1 but their content is same. So I renamed the nodes in Rpi LCD overlay. Now the overlay loads correctly but the display still does not work. The following errors are logged: Overlay: /dts-v1/; /plugin/; / { metadata { title ="Enable Raspberry Pi 7-inch Touchscreen on ROCK 4 A/B/SE"; compatible = "rockchip,rk3399"; category = "display"; description = "Enable Raspberry Pi 7-inch Touchscreen on ROCK 4 A/B/SE"; }; fragment@0 { target = <&mipi_dsi>; __overlay__ { dsi1-only; status = "okay"; }; }; fragment@1 { target = <&mipi_dsi1>; __overlay__ { rockchip,dsi-dsi0 = <&mipi_dsi>; status = "okay"; #address-cells = <1>; #size-cells = <0>; rockchip,lane-rate = <696>; ports { #address-cells = <1>; #size-cells = <0>; port@1 { reg = <1>; dsi_out_panel: endpoint { remote-endpoint = <&panel_in_dsi>; }; }; }; }; }; fragment@2 { target = <&i2c1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; raspits_panel: raspits-panel@45 { compatible = "raspberrypi,7inch-touchscreen-panel"; reg = <0x45>; port { panel_in_dsi: endpoint { remote-endpoint = <&dsi_out_panel>; }; }; }; raspits_touch_ft5426: raspits-touch-ft5426@38 { compatible = "raspits_ft5426"; reg = <0x38>; }; }; }; };
  2. Maybe, this is the same issue as on Radxa Rock boards? All USB ports work except OTG port - nothing recognized when inserted into this port.
  3. Same problem here - Rock 4B+. The upper USB3 port is not working. It does not respect OTG-host switch at all. Using device overlay to switch to port to host/peripheral mode does not work either.
  4. Hi, working on Rock Pi 4B++ and trying to make our displays work. Armbian Bookworm 23.8 Raspberry Pi 7" official touchscreen Officialy supported by Radxa (https://wiki.radxa.com/Rockpi4/Raspberry_Pi_official_LCD) but it does not work on Armbian at all. Works on official Radxa Debian image. No display on Armbian. Using device tree overlay from Radxa image - does not work, of course. Waveshare 4.3" touchscreen HDMI (https://www.waveshare.com/wiki/4.3inch_HDMI_LCD_(B)) It works. Image is visible, touchscreen works but the resolution seems to be scrambled. It is 800x480 and it is correctly reported, but the image is somehow distorted. I guess the problem is the aspect ratio which is 15:9. On Raspberry Pi, it works correctly but the following settings is required: How to correct this on Armbian? Waveshare 4.3" touchscreen DSI We also have DSI version of the above display. We have not tried yet but I guess what the result will be, right? So my question is How to make these displays work correctly on Armbian? Thank you.
  5. Same problem here. Anyone made it work? I tried using overlay from official Radxa image but it does not work and it completely stops all other overlays from loading.
  6. I'm not sure whether it is the correct solution, rather a workaround, especially when you don't have this problem. Maybe the waiting should happen in "loadcpufreq", because it also checks for the governor existence before its end and reports that "none" CPU module was loaded.
  7. I don't know but I fixed this issue by waiting for governor in /etc/init.d/cpufrequtils check_governor_avail() { info="/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" for i in $(seq 1 10); do if [ -f $info ]; then break fi sleep 1 done if [ -f $info ] && grep -q "\<$GOVERNOR\>" $info ; then return 0; fi return 1; }
  8. So I tried the official Radxa image for Rock Pi S and thermal zone works correctly there. So it is definitely a bug in Armbian but I guess I cannot expect any support here.
  9. Please check whether this issue might exist for other boards too:
  10. Good. I thought it must be related to the device tree but I'm using the official Armbian Bookworm image for Rock Pi S: Armbian 23.8 Bookworm CLI (https://www.armbian.com/rockpi-s/) https://paste.armbian.com/wuqagapuno How to fix?
  11. So the reason for this problem is when "loadcpufreq" services loads CPU modules, it takes some time to load them. "cpufrequtils" is loaded right after and data in /sys/devices/system/cpu/cpu0/cpufreq don't have to exist yet. When I put "sleep 3" at the beginning of the /etc/init.d/cpufrequtils then the CPU settings are loaded correctly.
  12. I built the following DTS to make onewire to work /dts-v1/; /plugin/; / { compatible = "rockchip,rk3308"; fragment@0 { target-path = "/"; __overlay__ { w1: onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; gpios = <&gpio0 15 0>; // GPIO0_B7 status = "okay"; }; }; }; };
  13. Hello, I have Rock Pi S V13 and Armbian 23.8.1 Bookworm with Linux 6.1.50-current-rockchip64. When I change CPU settings (min frequency, max frequency, scaling governor) using armbian-config, the change works correctly as expected. However, these settings are lost on reboot. When I check the status of cpufrequtils service, it seems that it does not load correctly as it is not able to find the requested governor: But if I start it manually later, it seems to load all my settings correctly: Any ideas to fix the problem except manually reloading it later? armbianmonitor: https://paste.armbian.com/owolufawif
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines