Jump to content

Magnets

Members
  • Posts

    50
  • Joined

Posts posted by Magnets

  1. On 11/14/2020 at 5:25 PM, Werner said:

    All kernel and header packages for the sunxi family are built from https://github.com/megous/linux/tree/orange-pi-5.9

     

    I'm running 5.10.12 on opi PC2 and gettin the same problem with V4L2_PIX_FMT_SUNXI_TILED_NV12 which is not defined in /usr/include/linux/videodev2.h

     

    It is defined in that source tree

    https://github.com/megous/linux/blob/orange-pi-5.10/include/uapi/linux/videodev2.h

     

    How is it getting lost in the armbian build process?

  2. I had a problem with ext4 and data being committed every 30 seconds and changing commit interval in fstab made no difference to fix it I modified:

     

    /proc/sys/vm/dirty_expire_centisecs

     

    to 500 (5 seconds). 30 seconds is default

     

    You can monitor it with:

     

     cat /proc/meminfo | grep "Dirty" -A1

     

  3. The latest update on my OPI pc2 has reduced the max cpu freq from 1.3ghz to 1.01ghz.

     

    I believe the old minfreq was 120mhz?

     

    linux-stretch-root-next-orangepipc2_5.85_arm64.deb

     

    /etc/default/cpufrequtils

    
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=480000
    MAX_SPEED=1010000
    GOVERNOR=ondemand
  4. I have a similar issue on opi PC2 with 4.19.25-sunxi64 and a DVB-T2 USB dongle. The problem is solved by locking the frequency scaling.

    E.g. I have

     

    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=120000
    MAX_SPEED=1400000
    #MAX_SPEED=500000
    GOVERNOR=conservative

    If MIN_SPEED and MAX_SPEED are the same you don't get any problems.

    Performance gov works OK (it locks to max freq)

    ondemand or interactive don't fix it unless you lock frequency

    I can lock frequency at 420mhz and it works fine so it's not related to actual frequency

    If I set MIN=800 and max=1300 it still gives problems

     

    my error:

    [ 6382.756348] rcu: INFO: rcu_sched self-detected stall on CPU
    [ 6382.756892] rcu:     1-....: (5601 ticks this GP) idle=d8a/1/0x4000000000000004 softirq=227944/227947 fqs=2034
    [ 6382.756957] rcu:      (t=5250 jiffies g=486985 q=1835)
    [ 6382.757208] Task dump for CPU 1:
    [ 6382.757310] kworker/1:2     R  running task        0  4002      2 0x0000002a
    [ 6382.757904] Workqueue: events dbs_work_handler
    [ 6382.758057] Call trace:
    [ 6382.758316]  dump_backtrace+0x0/0x1c0
    [ 6382.758526]  show_stack+0x14/0x20
    [ 6382.758703]  sched_show_task+0x160/0x198
    [ 6382.758900]  dump_cpu_task+0x40/0x50
    [ 6382.759103]  rcu_dump_cpu_stacks+0xc0/0x100
    [ 6382.759281]  rcu_check_callbacks+0x594/0x780
    [ 6382.759455]  update_process_times+0x2c/0x58
    [ 6382.759664]  tick_sched_handle.isra.5+0x30/0x48
    [ 6382.759844]  tick_sched_timer+0x48/0x98
    [ 6382.760013]  __hrtimer_run_queues+0xe4/0x1f8
    [ 6382.760172]  hrtimer_interrupt+0xf4/0x2b0
    [ 6382.760378]  arch_timer_handler_phys+0x28/0x40
    [ 6382.760563]  handle_percpu_devid_irq+0x80/0x138
    [ 6382.760765]  generic_handle_irq+0x24/0x38
    [ 6382.760960]  __handle_domain_irq+0x5c/0xb0
    [ 6382.761107]  gic_handle_irq+0x58/0xa8
    [ 6382.761249]  el1_irq+0xb0/0x140
    [ 6382.761466]  __usb_hcd_giveback_urb+0x98/0x148
    [ 6382.761649]  usb_giveback_urb_bh+0xdc/0x170
    [ 6382.761821]  tasklet_action_common.isra.3+0x7c/0x168
    [ 6382.761961]  tasklet_action+0x24/0x30
    [ 6382.762107]  __do_softirq+0x10c/0x200
    [ 6382.762238]  irq_exit+0xac/0xc0
    [ 6382.762431]  __handle_domain_irq+0x60/0xb0
    [ 6382.762567]  gic_handle_irq+0x58/0xa8
    [ 6382.762706]  el1_irq+0xb0/0x140
    [ 6382.762915]  clk_propagate_rate_change+0x30/0xe0
    [ 6382.763088]  clk_propagate_rate_change+0x90/0xe0
    [ 6382.763262]  clk_propagate_rate_change+0x90/0xe0
    [ 6382.763465]  clk_core_set_rate_nolock+0x1c0/0x1f8
    [ 6382.763649]  clk_set_rate+0x38/0xa8
    [ 6382.763807]  dev_pm_opp_set_rate+0x1f0/0x540
    [ 6382.764083]  set_target+0x40/0x70 [cpufreq_dt]
    [ 6382.764276]  __cpufreq_driver_target+0x184/0x5b0
    [ 6382.764463]  od_dbs_update+0x140/0x1a0
    [ 6382.764660]  dbs_work_handler+0x3c/0x70
    [ 6382.764858]  process_one_work+0x1e4/0x360
    [ 6382.765042]  worker_thread+0x48/0x4b0
    [ 6382.765195]  kthread+0x128/0x130
    [ 6382.765367]  ret_from_fork+0x10/0x1c

    some others with the issue:

     

    https://github.com/armbian/build/issues/1000

  5. On the PC2 I found the default governor (ondemand?) makes the freq spike too much, conservative prevents it from just hitting max freq every time you load it.

     

    I run conservative with an up_threshold of 50 (I think default is 25%)

     

    IIRC the parameter that allows it to consider IO as part of the load is not available on conservative so you lose a small amount of performance at the top end. If you're using USB wifi dongles it also doesn't want to increase freq in a hurry when running conservative.

     

  6. I have just noticed the same issue when trying to use armbian-config on pi pc2, as have others here:

    https://github.com/armbian/config/issues/33

     

    My armbianEnv.txt looks like this

    
    /var/log.hdd/aptitude {
      rotate 6
      monthly
      compress
      missingok
      notifempty
    }
    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

     

    How can I regenerate armbianEnv.txt without doing a reinstall?

     

    edit: pulled it from the .img

  7. I thought I'd share some links to JMS578 based enclosures I've found:

     

    ACASIS FA-08US - cheapest on ebay but also on ali https://www.aliexpress.com/item/Acasis-fa08us-2-5-inch-usb3-0-aluminum-external-hard-drive-disk-SATA-SSD-mechanical-solid/32818921168.html

    Metal enclosure with plastic tray, has 4 mounting holes to secure the drive to the tray. Firmware Version: v0.5.0.8

     

    CHIPAL clear enclosure - Firmware Version: v133.2.0.2. This enclosure gave me errors after running fstrim with an ADATA SU650 but not with another SSD I have. It works fine with discard. The SU650 + fstrim works fine in the ACASIS enclosure.

     

    JZYuan adapter - according the pictures on aliexpress it has JMS578 but I've not personally tested it

  8. Mt76 based dongles should work. A6210 works OK for me. I get around 160mbit/250mbit on 5ghz AC

    110mbit on 2.4ghz

    Around £15 on ebay. Argos sell them for £30 but reduce to £20 on occasion

     

    https://wireless.wiki.kernel.org/en/users/drivers/mediatek

    The drivers are under active development https://github.com/openwrt/mt76/commits/master

     

    some of the RTL8812AU yellow dongles from china come with RTL8812CU now. RTL8812AU perform bad even under windows so likely have poor design

  9. On 12/17/2018 at 5:35 AM, svts said:

    So the problem was solved!

    
    sed -i -e '1imw.l 0x01C20020 0x80101810\' /boot/boot.cmd
    mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

    The reason of crashes was DRAM PLL value which seems too high for the boards I have.

    Default DRAM_PLL value set by u-boot 2017.05+ is 624MHz. It seems not all board support this value.

    I changed it to 600MHz by setting 0x01c20020 register to 0x1810 value (instead of 0x1910 set by u-boot) and there's no any crash anymore.

     

    The script adds "mw.l 0x01C20020 0x80101810" line to boot.cmd and then compiles boot.scr.

    After that u-boot will change DRAM_PLL value to a bit lower one to avoid crashes.

     

    Thanks everybody who helped me to find a solution.

    Special thanks to @znoxx for testing and logging :)

     

     

    Great work! I have the same problem with a PC 2 which came direct from the manufacturer

     

    Your script has some unicode characters so I removed them:

    sed -i -e '1imw.l 0x01C20020 0x80101810\' /boot/boot.cmd
    mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

     

  10. 15 hours ago, guidol said:

    Not for $20 shipped, but with the -for me - cheap NAS case the NanoPi Neo2 LTS is a option.

    The Neo2 is available with 512MB or 1GB of Ram and works fine inside the NAS-Case
    (I got 2 of these combinations running over a year).

     

    armbian-support for the Neo2 (H5-CPU) is fine. HDMI isnt included, but with the NAS-case he has 2 USB 2.0-Ports, GBE,
    a power-switch AND a proper Power-connector for a normal 12V power-supply :)

    Neo2 LTS:
    https://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180

    NAS-case:
    https://www.friendlyarm.com/index.php?route=product/product&path=85&product_id=222

    Neo2_LTS.jpg

    Neo2_NAS_case.jpg

    Neo2_NAS_PCB.jpg

     

    That looks neat and essentially gives me 3 USB ports as I would be using USB-SATA adapter anyway but it's $55 USD including shipping to the UK

     

    7 hours ago, manuti said:

    OPi PC 2 is around 23€ including ship cost to my country. But for my is a huge upgrade from OPi PC Gigabit and cpu extensions made the difference.

     

    sound good

  11. I have an orange pi PC that I use as a simple NAS (NFS, smb, iscsi) and for openVPN occasionally but want something new with GbE.

     

    What is the best upgrade that will give me 2 or more usb ports, GbE and a faster processor? With decent software support (:P)? I don't need HDMI or wifi but it would be a plus

    512MB-1GB RAM

     

    opi zero plus?

    opi PC 2?

     

    Around $20 shipped ideally

  12. Using performance gov on opi PC with Sandisk 16GB A1 on a usb card reader


     

            Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2
            Output is in kBytes/sec
            Time Resolution = 0.000001 seconds.
            Processor cache size set to 1024 kBytes.
            Processor cache line size set to 32 bytes.
            File stride size set to 17 * record size.
                                                                  random    random     bkwd    record    stride
                  kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
              102400       4     3546     3573     5092     5086     4412     2948
              102400      16     4588     8634    15272    15273    13885     7955
              102400     512    21594    30277    36395    36542    35605    27344
              102400    1024    28300    32080    36932    37035    36661    26242
              102400   16384    30036    32860    37809    37933    37894    28773
    
    iozone test complete.

    Purchased from aliexpress ($5) but the scratch & verify sticker says it's genuine

     

    My samsung evo 64gb went read-only recently (20 months old) and then would not boot. I copied to another card and ran fsck and all seems OK. I think the later evos were not as well made as the earlier batches.

     

     

  13. I updated to head and recompiled and still have a black screen.

     

    Do I need to edit the kernel config? CONFIG_CMA_SIZE_MBYTES is set to 16

     

    edit: appears not, this is from dmesg
     

     cma: CMA: reserved 128 MiB at 58000000
    
    Kernal Command Line: ... cma=96M

     

  14. Thanks.

     

    Desktop works but HW video decoding doesn't, I just get a black window - the same video works on my OpiPC.

    Does VDPAU support TV out/CVBS?

     

    Using: Armbian_5.35_Orangepizero_Debian_jessie_default_3.4.113_desktop

  15. 12 hours ago, nopnop2002 said:

     

    When you'd like to know the model number of the ILITEK driver IC, use this one.

    https://github.com/nopnop2002/lcd_id

     

     

    Mine is:

     

    Read Registers on MCUFRIEND UNO shield
    controllers either read as single 16-bit
    e.g. the ID is at readReg(0)
    or as a sequence of 8-bit values
    in special locations (first is dummy)
    reg(0x0000) 15 80       ID: ILI9320, ILI9325, ILI9335, ...
    reg(0x0004) 00 01 00 01 Manufacturer ID
    reg(0x0009) 00 01 00 01 00      Status Register
    reg(0x000a) 00 00       Get Powsr Mode
    reg(0x000c) 00 00       Get Pixel Format
    reg(0x0061) 00 00       RDID1 HX8347-G
    reg(0x0062) 00 01       RDID2 HX8347-G
    reg(0x0063) 00 00       RDID3 HX8347-G
    reg(0x0064) 00 00       RDID1 HX8347-A
    reg(0x0065) 00 00       RDID2 HX8347-A
    reg(0x0066) 00 00       RDID3 HX8347-A
    reg(0x0067) 00 00       RDID Himax HX8347-A
    reg(0x0070) 00 00       Panel Himax HX8347-A
    reg(0x00a1) 00 00 00 00 00      RD_DDB SSD1963
    reg(0x00b0) 00 00       RGB Interface Signal Control
    reg(0x00b4) 00 00       Inversion Control
    reg(0x00b6) 00 00 00 00 00      Display Control
    reg(0x00b7) 00 00       Entry Mode Set
    reg(0x00bf) 00 00 00 00 00 00   ILI9481, HX8357-B
    reg(0x00c0) 00 00 00 00 00 00 00 00 00  Panel Control
    reg(0x00c8) 00 14 00 14 00 14 00 14 00 14 00 14 00      GAMMA
    reg(0x00cc) 00 02       Panel Control
    reg(0x00d0) 00 5a 00    Power Control
    reg(0x00d2) 00 be 00 be 00      NVM Read
    reg(0x00d3) 00 ff 00 ff ILI9341, ILI9488
    reg(0x00da) 00 00       RDID1
    reg(0x00db) 00 00       RDID2
    reg(0x00dc) 00 00       RDID3
    reg(0x00e0) 16 06 16 06 16 06 16 06 16 06 16 06 16 06 16 06     GAMMA-P
    reg(0x00e1) 07 88 07 88 07 88 07 88 07 88 07 88 07 88 07 88     GAMMA-N
    reg(0x00ef) 00 00 00 00 00 00   ILI9327
    reg(0x00f2) 00 00 00 00 00 00 00 00 00 00 00 00 Adjust Control 2
    reg(0x00f6) 00 54 00 54 Interface Control

     

    The number on the back is: 61580

    The board looks exactly like the one Neo posted further up, i.e. without the 3.3v regulator

  16. I'm not having any luck getting an image. I've connected mine (same model as Neo) as shown in the first video.

     

    If I don't connect the backlight (3v3) then the screen flashes faintly sometimes when using test programs. When the backlight is connected it doesn't appear to do anything - just a white screen

×
×
  • Create New...