Werner

Members
  • Content Count

    967
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Werner reacted to soerenderfor in Stability of RockPro64   
    @wolf7250 - here you go, here is a couple i got home.

    Delock 4 port SATA PCI Express Card - Marvell 88SE9215 - Works out of the box.
     
    StarTech.com 4 Port PCI Express SATA III 6Gbps RAID Controller Card with Heatsink (PCIe SATA 3 Controller Adapter (PEXSAT34RH), Styreenhed til lagring (RAID), 4 Kanal, SATA 6Gb/s lavprofil, 600 MBps, RAID 0, 1, 10, JBOD, PCIe 2.0 x2, for P/N: ST521PMINT - Marvell 88SE9230) - Some problems. But i did mange to get it working.

    DeLOCK - Lagringskontrol - SATA 6Gb/s - 600 MBps - RAID 0, 1, 10 - PCIe 2.0 x4 (Producent: DeLOCK | Model-nr.: DEL-89395 - Marvell 88SE9215) - Some probs. But did mange to get it working.

    Ziyituod PCIe SATA Card, 4 Port (SA3014 - Marvell 9215) Works out of the box.
  2. Like
    Werner reacted to lanefu in Helios4 Support   
    Yes plug them into another linux box and read up on mdraid / mdadm recovery. https://raid.wiki.kernel.org/index.php/RAID_Recovery
  3. Like
    Werner reacted to soerenderfor in Stability of RockPro64   
    @wolf7250 - That card from pine64 should be avoided in my opinion, i did only have trubles with it.  I have only cards with Marvell chipset, and i found out buy a simple card not a fancy raid card - less problems. I can later today find my different cards and name them for you.
  4. Like
    Werner reacted to 5kft in OPi Zero - why are frequencies above 1.008GHz unavailable?   
    Done!  https://github.com/armbian/build/commit/91156f11922c00227211d1d765512f09b6398d1a
     
    verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 cpu-clock-1.368GHz-1.3v rootdev=UUID=84d54d78-1a45-4366-9776-2fa013e0e1e6 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.37 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.37 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 1.37 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:89.25%, 648 MHz:0.49%, 816 MHz:1.19%, 960 MHz:0.01%, 1.01 GHz:3.74%, 1.06 GHz:0.01%, 1.10 GHz:0.86%, 1.15 GHz:0.01%, 1.20 GHz:0.82%, 1.22 GHz:0.01%, 1.25 GHz:0.73%, 1.30 GHz:0.01%, 1.37 GHz:2.89% (287)  
  5. Like
    Werner reacted to 5kft in OPi Zero - why are frequencies above 1.008GHz unavailable?   
    @Adrian Cable - I made the changes for sunxi-current and pushed to the repo:  https://github.com/armbian/build/commit/b2adb2935b4dcee57c982a1447de8cf75760dd2a.  This change adds a new boot overlay for the sun8i-h3 that enables a maximum of 1.3GHz at a CPU core voltage of 1.3v.  If you use this overlay, I strongly recommend you try driving the board hard to ensure stability (e.g., "stress --cpu 4", etc.)  Historically on most of my boards the maximum I could push to was 1.2GHz at 1.3v, which is why I added a 1.2GHz overlay for the H5 (and I could only get to 1.368GHz w/a 1.4v core voltage).  I can do the same for the H3, but am short on time atm.  I'll also add this overlay to sunxi-legacy as well, but I won't be able to get to this later.
     
    I tested this on one of my H3 boards w/a max CPU voltage of 1.3v:
     
    /boot/armbianEnv.txt (note the addition of "cpu-clock-1.3GHz-1.3v" to the "overlays=" line):
    verbosity=7 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost0 usbhost1 usbhost2 uart1 cpu-clock-1.3GHz-1.3v rootdev=UUID=3ad712a7-75cb-4ac1-8cfa-dbb67df8f239 rootfstype=f2fs extraargs=net.ifnames=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u  
    After booting with this overlay, from "cpufreq-info", w/everything else at the defaults, maximum clock rate is now 1.30GHz:
    analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.30 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 1.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:96.94%, 648 MHz:0.35%, 816 MHz:0.04%, 960 MHz:0.03%, 1.01 GHz:0.03%, 1.06 GHz:0.02%, 1.10 GHz:0.02%, 1.15 GHz:0.03%, 1.20 GHz:0.02%, 1.22 GHz:0.01%, 1.25 GHz:0.01%, 1.30 GHz:2.50% (253) Please give this a try and let me know how it goes   If 1.3GHz is unstable, I'll try to expedite adding the 1.2GHz overlay as well.
     
  6. Like
    Werner reacted to 5kft in OPi Zero - why are frequencies above 1.008GHz unavailable?   
    Because the opp table in the DTs are common and used for all H3/H5 boards, not just your specific OPi Zero.  The CPU regulator voltage defines the maximum clock rate available, specific to each board.
     
     
    Actually this behavior is completely correct - it's how the CPU clock system is defined.  You do not want to make a general PR to increase the default clocks for lower voltages here because this will introduce instabilities across all other AW-based boards (!).
     
    There is a very easy way to enable this, however - you can use an overclock overlay.  I created a few of these a couple of years ago; see this thread for more information: 
     
     
    Now I just noticed that this patch apparently didn't make it over to the new sunxi-current branch (5.7); I'll fix this.  I also used the H5 prefix for this - I haven't tried it on an H3, but given the common opp table it should work.  I'll take a look at cleaning this up now for sunxi-current and will post back.
  7. Like
    Werner reacted to martinayotte in Switching SUNXI-DEV to 5.8.y (h3-h5-h6/megous)   
    Oh ! I've completely forgot about the hack, I've forgot to add it in /etc/rc.local of the 5.8.y build ... I will check now ...
     
    EDIT: Thanks for the reminder : it is not freezing any more, at least until now !
  8. Like
    Werner reacted to Adrian Cable in OPi Zero - why are frequencies above 1.008GHz unavailable?   
    Werner - that's a great idea! In case you or others want to test as well, here are my corrected lines in the DTS for the OPi Zero:
     
     
                    opp-1104000000 {
                            opp-hz = < 0x00 0x41cdb400 >;
                            opp-microvolt = < 0x13d620 0x13d620 0x13d620 >;
                            clock-latency-ns = < 0x3b9b0 >;
                    };
                    opp-1200000000 {
                            opp-hz = < 0x00 0x47868c00 >;
                            opp-microvolt = < 0x13d620 0x13d620 0x13d620 >;
                            clock-latency-ns = < 0x3b9b0 >;
                    };
                    opp-1296000000 {
                            opp-hz = < 0x00 0x4d3f6400 >;
                            opp-microvolt = < 0x13d620 0x13d620 0x13d620 >;
                            clock-latency-ns = < 0x3b9b0 >;
                    };
                    opp-1368000000 {
                            opp-hz = < 0x00 0x518a0600 >;
                            opp-microvolt = < 0x13d620 0x13d620 0x13d620 >;
                            clock-latency-ns = < 0x3b9b0 >;
                    };
     
    Running now at 1.368GHz and hasn't crashed. I'm going to try stress etc. and see what happens.
     
    -Adrian
  9. Like
    Werner reacted to MacBreaker in SimpNAS Beta Released!   
    Hi Tido,
     
    thanks for clarification of root or root privileges.
    i didn't know this, sorry.
     
    I will read the README.md and start over again on the weekend.
     
     
    Ich hoffe...
  10. Like
    Werner got a reaction from Tido in Help Test Upcoming Armbian v20.08 (Caple)!   
    https://docs.google.com/spreadsheets/d/11iid35ZGlTws1XOqSMJIw0y7nK6bNdpqVq6I4JFihuo/edit?usp=sharing
  11. Like
    Werner reacted to Igor in Cannot login google services using Chromium   
    Snap version of Chromium seems to work while we were trying to use hack to provide snap-less Ubuntu. Now its snap and chromium less, preinstalled with Firefox and one can install Chromium via snap.
  12. Like
    Werner got a reaction from lanefu in Cannot login google services using Chromium   
    ...and adding firefox or better firefox-esr (since it is in both Ubuntu and Debian AFAIK) to the list of desktop packages?
  13. Like
    Werner reacted to lanefu in Help Test Upcoming Armbian v20.08 (Caple)!   
    We have nightly images built available for the boards below.   Please help us test and report your experience via This Google Form.
     
    Images are available via our normal Armbian download page.  Just scroll to the bottom to the "nightly build" section.
     
     
    Bananapi Bananapim2plus Bananapim2zero Bananapipro Clearfogbase Clearfogpro Cubietruck Espressobin Helios4 Lepotato Lime-a64 Nanopct4 Nanopiair Nanopim4 Nanopim4v2 Nanopi-r1 Nanopi-r2s Odroidc2 Odroidc4 Odroidn2 Odroidxu4 Orangepi3 Orangepi4 Orangepione Orangepipc Orangepipc2 Orangepipcplus Orangepizero Orangepizeroplus2-h3 Orangepizeroplus2-h5 Pine64 Pinebook-a64 Pineh64 Pineh64-b Rock64 Rockpi-4a Rockpi-4b Rockpi-e Teres-a64 Tinkerboard Tritium-h3 Tritium-h5
  14. Like
    Werner reacted to iav in Armbian IRC Channel   
    Or via matrix bridge: #freenode_#armbian:matrix.org
  15. Like
    Werner reacted to Clément Peron in Unable to make Panfrost work on H6   
    @Werner @NicoD There seems to have an issue with the clock implementation in the kernel.
    You can look at @megi explanation about PLL lock of the NKMP clock.
     
    Allwinner GPU clock is actually prone to overshooting which make the GPU DVFS not usable at the time.
  16. 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?
  17. Like
    Werner got a reaction from NicoD in Unable to make Panfrost work on H6   
    Not very good...But I dont wanna spoiler you
  18. 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.
  19. Like
    Werner got a reaction from rforcen in desktop background on cyan -> SOLVED!   
    Broken monitor/cable?
  20. 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.
  21. 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
  22. 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.
  23. 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.
  24. 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.
  25. 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