Jump to content

Werner

Administrators
  • Posts

    4437
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Werner reacted to Igor in armbian + nanopi duo2 + citadel -> cant instal   
    Its almost certainly not.
     

    Focal = Ubuntu 20.04 user land. It might work but you are asking for troubles. Safer start is with Bionic / Buster, but still you need to follow their instructions. If their fancy auto install doesn't work, I am sure there must be manual step by step. If we would start to stick nose in such problems, we would not be able to give you opportunity to use this hardware on the level you want to use it.
     

    (compiling on) 512 Mb memory, 4Gb SD card and Ubuntu Focal ... you are walking on the extreme edge with everything. Perhaps that would be the general problem no. 1?
  2. Like
    Werner got a reaction from NicoD in Unable to make Panfrost work on H6   
    Not very good...But I dont wanna spoiler you
  3. Like
    Werner got a reaction from NicoD in Amlogic forum adjustments   
    For the Amlogic S905(x) forums add S912 and S922 to it? I don't think there is a need to divite those into the other supported boards.
  4. Like
    Werner got a reaction from rforcen in desktop background on cyan -> SOLVED!   
    Broken monitor/cable?
  5. Like
    Werner reacted to NicoD in Odroid N2+ / N2 Plus   
    Armbianmonitor: http://ix.io/2sUH Hi all. 
    I've recently received the Odroid N2+. Since nobody else started a topic about it, I'll be the one. 
    All works fine with Armbian since not much hardware changes have been made vs the N2. Except for the CPU frequency.
     
    With the Odroid Ubuntu you can set it to 2.4Ghz for the big cores A73 as overclock (2208 stock)., and 2016Mhz for the A53 cores (1908  stock). 

    With Armbian the max clocks are 2Ghz for all cores. Using Armbian Focal 4.9 legacy.
    I tried setting the higher values in config.ini. Also tried with the "meson64_odroidn2_plus.dtb" file from the Odroid Ubuntu. Doesn't boot with that. (What do I know )

    Other changes are the RTC battery that's now on the board. 
    The heatsink has changed a little. But it's still more than sufficient to keep it cool even when overclocked. 

    USB3 still rather s*cks on it. Slow and a lot of issues with 2.4Ghz dongles(wifi/keyboard...).
    Too bad they didn't do anything about that. But that probably could have complicated compatibility with N2 images. 

    Also feels a bit more sluggish than RK3399 on NVMe vs 128GB eMMC on the N2+.  That's what fast I/O does. I'll try on USB3-NVMe later.

    Here some pictures. 1st pic the N2+ with its case open.
    2nd picture the N2 left and the N2+ on the right.

    Cheers all.
  6. Like
    Werner got a reaction from Tido in Armbian image for Lamobo R1 Debian Buster   
    https://armbian.laet.pw/_extra/Armbian_20.08.0-trunk_Lamobo-r1_buster_current_5.7.11.img.xz
    No warranty. No support
  7. Like
    Werner reacted to musicPi in sun4i-drm and LCD-Panels   
    Hello,
    I got I finally working. There are some changes to be done in the device tree to make sun4i-drm and lima work with LCD-Panels on BananaPi / BananaPro.
    Short version: create a panel in device tree and connect it to the correct driver.
    Here's what I did:
    1. Start compilation with
    ./compile.sh CREATE_PATCHES=yes BOARD=bananapipro INSTALL_HEADERS=yes 2. If asked to apply changes modify u-boot-config:
    nano /build/cache/sources/v2020.04/configs/Bananapro_defconfig add
    #5" RGB LCD CONFIG_VIDEO_LCD_MODE="x:800,y:480,depth:24,pclk_khz:30000,le:40,ri:40,up:29,lo:13,hs:48,vs:3,sync:3,vmode:0" CONFIG_VIDEO_LCD_POWER="PH12" CONFIG_VIDEO_LCD_BL_EN="PH8" CONFIG_VIDEO_LCD_BL_PWM="PB2" 3. modify sun7i-a20 device tree
    nano build/cache/sources/v2020.04/arch/arm/dts/sun7i-a20.dtsi add the tcon0_out_lcd section to tcon0:
    tcon0: lcd-controller@1c0c000 { //..... ports { //..... tcon0_out: port@1 { #address-cells = <1>; #size-cells = <0>; reg = <1>; tcon0_out_lcd: endpoint@0 { reg = <0>; remote-endpoint = <&lcd_in_tcon0>; }; tcon0_out_hdmi: endpoint@1 { reg = <1>; remote-endpoint = <&hdmi_in_tcon0>; }; }; }; }; I don't know if it works for tcon1 too but feel free to try. Then add the same lines to tcon1 and replace each "tcon0" with "tcon1".
    Then add a panel section:
    panel: panel { #address-cells = <1>; #size-cells = <0>; port { #address-cells = <1>; #size-cells = <0>; lcd_in_tcon0: endpoint { remote-endpoint = <&tcon0_out_lcd>; }; }; }; If you also want to use tcon1 add lcd_in_tcon1 section .
    My Lemaker 5"LCD-Display uses RGB-Mode so this has to be added to pio section
    pio: pinctrl@1c20800 { compatible = "allwinner,sun7i-a20-pinctrl"; //..... lcd0_rgb888_pins: lcd0-rgb888 { pins = "PD0", "PD1", "PD2", "PD3", "PD4", "PD5", "PD6", "PD7", "PD8", "PD9", "PD10", "PD11", "PD12", "PD13", "PD14", "PD15", "PD16", "PD17", "PD18", "PD19", "PD20", "PD21", "PD22", "PD23", "PD24", "PD25", "PD26", "PD27"; function = "lcd0"; }; //..... }; 4. modify bananapro device tree
    nano build/cache/sources/v2020.04/arch/arm/dts/sun7i-a20-bananapro.dts Add backlight and power management for the panel
    #include <dt-bindings/pwm/pwm.h> / { model = "LeMaker Banana Pro"; compatible = "lemaker,bananapro", "allwinner,sun7i-a20"; //..... backlight: backlight { compatible = "pwm-backlight"; pwms = <&pwm 0 50000 0>; brightness-levels = < 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 5 5 5 6 6 6 7 7 8 8 8 9 9 9 10 10 10 11 11 12 12 12 13 13 14 14 14 15 15 16 16 17 17 17 18 18 19 19 20 20 21 21 21 22 22 23 23 24 24 25 25 26 26 27 27 28 28 29 30 30 31 31 32 32 33 33 34 35 35 36 36 37 38 38 39 39 40 41 41 42 43 43 44 44 45 46 47 47 48 49 49 50 51 51 52 53 54 54 55 56 57 57 58 59 60 61 61 62 63 64 65 65 66 67 68 69 70 71 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 101 102 103 104 105 106 108 109 110 111 112 114 115 116 117 119 120 121 123 124 125 127 128 129 131 132 133 135 136 138 139 141 142 144 145 147 148 150 151 153 154 156 157 159 161 162 164 166 167 169 171 173 174 176 178 180 181 183 185 187 189 191 192 194 196 198 200 202 204 206 208 210 212 214 216 219 221 223 225 227 229 232 234 236 238 241 242 244 246 248 250 253 255>; default-brightness-level = <128>; enable-gpios = <&pio 7 8 GPIO_ACTIVE_HIGH>; /* PH8 */ }; panel_power: panel_power { compatible = "regulator-fixed"; regulator-name = "panel-power"; regulator-min-microvolt = <10400000>; regulator-max-microvolt = <10400000>; gpio = <&pio 7 12 GPIO_ACTIVE_HIGH>; /* PH12 */ enable-active-high; regulator-boot-on; }; }; Configure tcon to use our panel and enable display engine
    &de { status = "okay"; }; &tcon0 { pinctrl-names = "default"; pinctrl-0 = <&lcd0_rgb888_pins>; status = "okay"; }; &panel { compatible = "lemaker,bl050-rgb-002"; power-supply = <&panel_power>; backlight = <&backlight>; }; Add touch driver for edt-ft5x06:
    &i2c3 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&i2c3_pins>; edt: edt-ft5x06@38 { compatible = "edt,edt-ft5x06", "edt,edt-ft5306"; reg = <0x38>; interrupt-parent = <&pio>; interrupts = <7 9 IRQ_TYPE_EDGE_FALLING>; // wake-gpios = <7 7 GPIO_ACTIVE_LOW>; pinctrl-names = "default"; pinctrl-0 = <&edt_ft5x06_pins_a &edt_ft5x06_pins_b>; touchscreen-size-x = <800>; touchscreen-size-y = <480>; //touchscreen-inverted-x; //touchscreen-inverted-y; //touchscreen-swapped-x-y; }; };  Add edt_ft5x06 and backlight pins:
    &pio { edt_ft5x06_pins_a: ft5@0 { // interrupt pins = "PH9"; function = "irq"; drive-strength = <20>; bias-pull-up; }; edt_ft5x06_pins_b: ft5@1 { // reset-gpios pins = "PH7"; function = "gpio_out"; drive-strength = <20>; bias-pull-up; output-high; }; }; &pwm { pinctrl-names = "default"; pinctrl-0 = <&pwm0_pin>, <&pwm1_pin>; status = "okay"; }; Hit <Enter>
     
    If asked the nexttime to press enter:
     
    5. Make sure your panel driver available in kernel drivers. Mine was not. So I had to add it to the simple panel driver which already contains the Lemeker 3,5"LCD-Display.
     
    nano build/cache/sources/linux-mainline/orange-pi-5.4/drivers/gpu/drm/panel/panel-simple.c add this right after lemaker_bl035_rgb_002
    static const struct panel_desc lemaker_bl050_rgb_002 = { .modes = &lemaker_bl050_rgb_002_mode, .num_modes = 1, .size = { .width = 108, .height = 64, }, .bus_format = MEDIA_BUS_FMT_RGB888_1X24, .bus_flags = DRM_BUS_FLAG_DE_HIGH, }; static const struct drm_display_mode lg_lb070wv8_mode = { .clock = 33246, .hdisplay = 800, .hsync_start = 800 + 88, .hsync_end = 800 + 88 + 80, .htotal = 800 + 88 + 80 + 88, .vdisplay = 480, .vsync_start = 480 + 10, .vsync_end = 480 + 10 + 25, .vtotal = 480 + 10 + 25 + 10, .vrefresh = 60, }; and this right after lemaker,bl035-rgb-002
    static const struct of_device_id platform_of_match[] = { { //..... }, { .compatible = "lemaker,bl050-rgb-002", .data = &lemaker_bl050_rgb_002, }, { //..... } } Do steps 3 and 4 to
    build/cache/sources/linux-mainline/orange-pi-5.4/arch/arm/boot/dts/sun7i-a20.dtsi
    and
    build/cache/sources/linux-mainline/orange-pi-5.4/arch/arm/boot/dts/sun7i-a20-bananapro.dts
    and hit <Enter> and proceed build
     
     
    Have a look at this page for other display configurations:
    http://linux-sunxi.org/LCD#Mainline_Linux_.28simple-panel.29
     
    Thanks a lot to sgei and his tutorial!
    Many thanks to authors of another hunderd websites which also helped but I can't even list.
    Please let me know if this works for BananaPi too.
  8. Like
    Werner reacted to Myy in panfrost on RK3288 and GPU on 600MHz problems   
    Thanks for testing ! I guess we can include this patch in the next release, then.
  9. Like
    Werner reacted to DeterminedOpier in OctoPrint on armbian   
    Yea you are probably young though. I'm 54, and wrote one of the first books on remote web publishing (in perl) back in 1996, and never had a computer course in my life. Those days are gone for me. My brain just doesn't want learn entire new things anymore.  I had to ask my sysadmin the other day to remind me how to use nmap so I could find my pi on the network.   At this point I'm just hoping that Mr. @ldiaz can make this thing work. I have a pile of Opi Ones from a failed project a couple years ago and I want to build a print farm for my twins.  This would be a real gift for my lazy old brain.
  10. Like
    Werner reacted to o010b in NanoPi Neo3 rk3399-bluetooth.service   
    /usr/bin/brcm_patchram_plus/rk3399 hogs 100% CPU until rk3399-bluetooth.service is stopped and disabled.
     
    The NanoPi Neo3 does not have bluetooth.
     
     
    Board: Not on the list
  11. Like
    Werner reacted to mboehmer in Odroid C2 on seafloor (part II)   
    Hi all,
     
    as a small status update on the seafloor business, here are some pictures of the new Odroid C2 based instruments which will be deployed in September/October in the northers Pacific.
    Ten modules with different functionality will be deployed, all based on a standard setup of Odroid C2, TRB3sc FPGA based TDC DAQ system, one PADIWA preamp, and a modded mdedia converter serving as a fully configurable mini switch.
     

     
    One of the modules carries several Hamamatsu mini spectrometers, as well as a camera, to observe bioluminescence.

     
    Another module is targeting at muon tracking with SiPM based readout:

     
    I have some more picture of the more "fancy" PMT based modules, but don't want to flood this forum now with too many pictures.
     
    To all of you: thanks for the support you gave us over the last year, and the discussions on specific topics!
     
    Deployment pictures will follow once the modules are in place on the seafloor, 2600m deep in the Pacific (and operational, hopefully, this time we just have a GbE fiber, no serial port...)
     
    See you, Michael
     
     
  12. Like
    Werner reacted to NicoD in Armbian in 3D   
    Good news to have more CSC. I didn't know FriendlyElec also have a +2 board? I thought Orange Pi was the only one with such ridiculous naming. I've got the OPi+2.
    I just checked the eos. Any reason why the OPi2 is eos? It's got the H3 that's supported on many other boards. Orange Pi's are the most downloaded images on Armbian. So I wonder if somethings wrong with it.

    I can just do this. Clear enough I guess.
     

  13. Like
    Werner reacted to NicoD in Armbian in 3D   
    First render.
    I'll make the dirt look more rough. I don't know of the color(colorblind...) I'll make the stone look marble.
     
    I can also make grass and make it look a lot more cheerfull, maybe flowers or so.

  14. Like
    Werner reacted to NicoD in Armbian in 3D   
    I've finished the grave stone. But I'm having troubles making the ground look right. I'll add more texture to it and hope it'll turn out better.
    If anyone has any idea's... Please let me know, mine have dried up.
     

  15. Like
    Werner reacted to NicoD in Armbian in 3D   
    I've finished the EOL background.


    I'm rendering everything in 4K with my N2. I've finished a few.
    Here's one with rounded shape.

    I'll upload them all together when ready. Cheers.
     
  16. Like
    Werner reacted to NicoD in Armbian in 3D   
    I've finished all of them. All 4k except the transport one. That would take too long since there are many light sources and bounces.(+10hours) And even then the quality would be less since I've got to lower some things.
    And the N2 isn't super stable either.
    They are all converted to jpg because the original png's are together 560MB.

    My favorite is the under construction one But you can't use that for supported

    @lanefu If you need anything more, let me know. I hope people are going to like them, I've already seem them too much. 

    Now I can start putting my render farm together to make new animations for my channel.
    Cheers.
    Armbian Backgrounds JPG.7z
  17. Like
    Werner got a reaction from JrRockeTer in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    I've create an issue on jira regarding the zram thingy. Whoever wants to take a shot at it... https://armbian.atlassian.net/browse/AR-382
  18. Like
    Werner reacted to JrRockeTer in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    Check this out @NicoD @Werner, beautiful and it was usable for most of the time
     
    cat /proc/swaps
    Filename                                Type            Size    Used    Priority
    /dev/zram0                              partition       329960  328920  5
    /dev/zram1                              partition       329960  329020  5
    /dev/zram2                              partition       329960  329076  5
    /dev/zram3                              partition       329960  328840  5
    /dev/zram4                              partition       329960  329008  5
    /dev/zram5                              partition       329960  329000  5
    /swapfile                               file            8388604 516160  -2
     
    vmstat 5 100
    procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
     r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
    14  1 2945416  82864   3580 281876   14   20    13     6   44   53  1  0 99  0  0
    10  0 2965260  79092   2084 251232 43369 35211 34502 13287 10110 17175 58 34  6  2  0
     9  0 2999792  83996   4204 293888 32905 38888 31712 27475 9000 15632 61 34  4  1  0
     
    I think most of my original problems were related to: Power, Memory, HEAT
    1- at one time I made a mistake and was not using the factory power supply
    2- the problem with zram and swapping that you fixed for me @NicoD
    3- When I first installed it I had not installed fan management, this should come standard.
    Thanks you, I'll cross post this to my other post
     
  19. Like
    Werner reacted to lanefu in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    It's the spirit of TK and persistent testing and tuning that must live on.... any help in that front is great
  20. Like
    Werner got a reaction from JrRockeTer in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    If you have an NVMe installed anyways you should put the swap there since it is way faster than an eMMC.
    Or investigate if there is a memory leak.
  21. Like
    Werner reacted to NicoD in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    Hi @JrRockeTer 
    Do :
    sudo apt install zram-config and reboot. 
    That will increase your zram from 1024MB to 2048MB. There's a fault in the armbian zram-config. For 4GB ram it should create 2GB zram. But it by default creates 1GB. 

    If you run on an NVMe, then create a big swap file (don't forget sudo, or use "su" before applying the commands :
     
    fallocate -l 8G /swapfile chmod 600 /swapfile mkswap /swapfile swapon /swapfile echo "/swapfile swap swap defaults 0 0" >> /etc/fstab
    I'll check out Focal mainline now on the M4V2. Cheers.
  22. Like
    Werner got a reaction from lanefu in Is there a way to avoid killing processe when out of memory Out of memory: Killed process   
    If you have an NVMe installed anyways you should put the swap there since it is way faster than an eMMC.
    Or investigate if there is a memory leak.
  23. Like
    Werner got a reaction from lanefu in No kvm option in the build process   
    So.... ¯\_(ツ)_/¯
  24. Like
    Werner reacted to lanefu in Armbian v20.08 (Caple) Planning Thread   
    Hi wanted to say we had a really awesome swarm of hacking last weekend.
     
    Also we got a bit distracted on cutting RC branch due to the infrastructure move.
  25. Like
    Werner reacted to piter75 in SOLVED: Nanopi M4V2 Focal Please help, I think I somehow removed my wlan0 interface   
    This happens after upgrading armbian-firmware package and it is already fixed in master and will be part of v20.08 release.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines