Jump to content

denni_isl

Members
  • Posts

    125
  • Joined

  • Last visited

Posts posted by denni_isl

  1. sudo nano /etc/default/cpufrequtils 

    ENABLE=true
    MIN_SPEED=600000
    MAX_SPEED=2016000
    # performance i firefox preferences i 6 
    # MAX_SPEED=1800000
    #GOVERNOR=ondemand
    GOVERNOR=performance

    and firefox, Preferences, General, Performance, Use hardware acceleration when available, Content process limit 6

     

    Screenshot_2020-08-17_12-28-22.png

  2. Probably not supported yet.   Try - Chromium > chrome://gpu

     

    I get

    Quote

    Graphics Feature Status

    Canvas: Software only, hardware acceleration unavailable

    Flash: Unavailable

    Flash Stage3D: Unavailable

    Flash Stage3D Baseline profile: Unavailable

    Compositing: Unavailable

    Multiple Raster Threads: Force enabled

    Out-of-process Rasterization: Unavailable

    Hardware Protected Video Decode: Unavailable

    Rasterization: Hardware accelerated

    Skia Renderer: Disabled

    Video Decode: Unavailable

    Viz Display Compositor: Enabled

    Viz Hit-test Surface Layer: Enabled

    Vulkan: Disabled

    WebGL: Hardware accelerated but at reduced performance

    WebGL2: Unavailable

     

  3. nanopi-m4v2 - kernel 5.3.11 usb-storage not working and external usb sound card not detected and flickering screen after armbian-config firmware upgrade yesterday (4.jan) but usb network and keyboard working fine.   The same with kernel 5.4.0 (all of them, also 19.11.5.365)

  4. Quote

    Dec 23 13:35:02 localhost nm-dispatcher: req:2 'connectivity-change': new request (2 scripts)
    Dec 23 13:35:02 localhost nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
    Dec 23 13:35:03 localhost systemd[1]: Started Samba NMB Daemon.
    Dec 23 13:35:03 localhost systemd[1]: Starting Samba SMB Daemon...
    Dec 23 13:35:03 localhost systemd[1]: Started Samba SMB Daemon.
    Dec 23 13:35:05 localhost chronyd[1037]: Selected source x.x.x.x
    Dec 23 13:35:05 localhost chronyd[1037]: System clock wrong by -1.542673 seconds, adjustment started
    Dec 23 13:35:05 localhost chronyd[1037]: System clock was stepped by -1.542673 seconds
    Dec 23 13:35:10 localhost systemd[1]: NetworkManager-dispatcher.service: Succeeded.
    Dec 23 13:35:16 localhost systemd[1]: systemd-hostnamed.service: Succeeded.
    Dec 23 13:35:18 localhost systemd[1]: dev-ttyFIQ0.device: Job dev-ttyFIQ0.device/start timed out.
    Dec 23 13:35:18 localhost systemd[1]: Timed out waiting for device /dev/ttyFIQ0.
    Dec 23 13:35:18 localhost systemd[1]: Dependency failed for Serial Getty on ttyFIQ0.
    Dec 23 13:35:18 localhost systemd[1]: serial-getty@ttyFIQ0.service: Job serial-getty@ttyFIQ0.service/start failed with result 'dependency'.
    Dec 23 13:35:18 localhost systemd[1]: dev-ttyFIQ0.device: Job dev-ttyFIQ0.device/start failed with result 'timeout'.
    Dec 23 13:35:18 localhost systemd[1]: Reached target Login Prompts.
    Dec 23 13:35:18 localhost systemd[1]: Reached target Multi-User System.
    Dec 23 13:35:18 localhost systemd[1]: Reached target Graphical Interface.
    Dec 23 13:35:18 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Dec 23 13:35:18 localhost systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
    Dec 23 13:35:18 localhost systemd[1]: Started Update UTMP about System Runlevel Changes.
    Dec 23 13:35:18 localhost systemd[1]: Startup finished in 52.814s (kernel) + 1min 30.570s (userspace) = 2min 23.384s.

     

    This is a output of tail -f /var/log/syslog on Linux rockpro64 5.3.11-rockchip64 #19.11.3 SMP PREEMPT Mon Nov 18 21:03:09 CET 2019 aarch64 GNU/Linux so my network dongle is working better now on this kernel after the armbian-config update today 

  5. Had to look up NXP, newer heard of it before and it is huge Multi National company originated out of Holland from Philips to be more precise https://en.wikipedia.org/wiki/NXP_Semiconductors  employing 31.000 people (11.2000 engineers).   Remember when I did read about The Chinese graduating around 300.000 engineers a year, about 20 years ago, which made you came to the conclusion that the world was changing rapidly.

     

  6. SUCCESS AT LAST!   Installing a Realtech wireless wifi dongle driver on rockpro64.  

    Okay being a stubborn person,  is sometimes beneficial.  

    I was at last able to install driver for my speedy Chinese USB dongle with Realtech ship. lsusb gives vendor 0bda and product b812 witch is dependent upon driver rtl8812bu.     Now I want to contribute to the community on how.  Did fallow the instructions on  https://docs.armbian.com/Developer-Guide_Build-Preparation/   compiled a new kernel and U-boot,   It did produce 5 *.deb files; linux-source-default-rockchip64_5.67_all.deb, linux-headers-rockchip64_5.67_arm64.deb,  linux-u-boot-rockpro64_5.67_arm64.deb, linux-image-rockchip64_5.67_arm64.deb  and installed them on the rockpro64 board.   It did also include  /usr/src/linux-source-4.4.167-rockchip64.tar.xz which I extracted into /usr/src/linux-headers-4.4.167-rockchip64 directory and did make clean (because of previous compile error of lacking files) and then make scripts (and viola it did work!!!).   Then it was github next and this driver did look promising https://github.com/cilynx/rtl88x2BU_WiFi_linux_v5.3.1_27678.20180430_COEX20180427-5959  Fallowed the instructions of dkms install there

     

    Quote

    cd rtl88x2BU_WiFi_linux_v5.3.1_27678.20180430_COEX20180427-5959 VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf) sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER} sudo dkms add -m rtl88x2bu -v ${VER} sudo dkms build -m rtl88x2bu -v ${VER} sudo dkms install -m rtl88x2bu -v ${VER} sudo modprobe 88x2bu

     

     

    And it did work!   Almost all the headache was because of the driver needing kernel source not just the headers under /usr/src/linux-headers-$(uname -r)

     

    Quote

    wlx000  IEEE 802.11AC  ESSID:"my_connection-5G"  Nickname:"<WIFI@REALTEK>"
              Mode:Managed  Frequency:5.22 GHz  Access Point: 00:00:00:00:00:00  
              Bit Rate:867 Mb/s   Sensitivity:0/0  
              Retry:off   RTS thr:off   Fragment thr:off
              Encryption key:****-****-****-****-****-****-****-****   Security mode:open
              Power Management:off
              Link Quality=100/100  Signal level=-36 dBm  Noise level=0 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0

     

     

     

    20181223_135937.jpg

  7. 8 minutes ago, Igor said:


    And who should do that? We provide a list of (good) ones - on the download pages - that work out of the box. For each kernel/board. It's planned to do more indeep testings, but day has only 24h. Some of the testings can be found scattered in this topic and elsewhere on the forum.

    Did not see this threat before.  Interesting.    If only I had programming experience I would be willing to try to help out with migrating all those rtl--- modules on github to arm64.   What  i can see is that coordinated effort must be the best way to get the compiling environment right and then being able to adjust those modules.   

     

    Btw. you at armbian are doing a excellent  job.

     

  8. Both firefly rk3399 and rockpro64 are amazing products, and working like a charm with armbian though still lacking some things.   Firefly is more working out of the box when rockpro64 does not yet support for it's components like the audio jack, wifi module and isa(okay in cli)  slot.   Then it is the usual thing that the hardware that is ahead of the software.   But what did take me with a surprise is the lack of comparability with usb wifi dongles now almost as common as coffee <_<.  

  9. Thank you for the respond.   It is actually a good point, and understood.   And this https://www.armbian.com/get-involved/#communication

    and the Armbian documentations are actually the best source I have seen on the net for the everyday hobbyist wanting to get a better understanding of computers and now those days embedded systems.    Regarding this issues with being unable to compile drivers for for arm64 boards, I have came to the conclusions that it is actually because aarch64 is just not there yet.   And I am not a programmer so I have to remind my self ... hands off.   arm64 is like a new kid in the block in the linux world.   Android is just another story.     Is there any migrating from Android to linux in the arm and arm64 support?   Or is the Android source closed from the linux world?    Now I am wondering how far arm64 is in it's development.   Did see this of non supported software from debian site. https://wiki.debian.org/Arm64PortANFUList

    and it is quite a lot.  

     

     

  10. Being a stubborn person, I am still trying to get a rtl8811cu for usb wifi dongle vendor 0bda and product c811 up and running.   The main hurdle have been a this error messages when doing make scripts from /usr/src/linux-headers-4.4.166-rockchip64/

     

    Quote

    root@rockpro64:/usr/src/linux-headers-4.4.166-rockchip64# make scripts
      CHK     scripts/mod/devicetable-offsets.h
      HOSTCC  scripts/selinux/genheaders/genheaders
    scripts/selinux/genheaders/genheaders.c:13:10: fatal error: classmap.h: No such file or directory
     #include "classmap.h"
              ^~~~~~~~~~~~
    compilation terminated.
    scripts/Makefile.host:91: recipe for target 'scripts/selinux/genheaders/genheaders' failed

     

  11. When you do gdisk -l /dev/mmcblk1  or fdisk -l you can se that the partition table that armbian is using is MBR (dos).   Is any particular reason for this?  When you go to the new and improved firefly rk3399 manual page you can see it is making problem when flashing through USB-C cable and upgrade_tool v. 1.24 and v. 1.34 (GBT friendly)  http://wiki.t-firefly.com/en/Firefly-RK3399/flashing-notes.html  .       

  12. Now when development kernel 4.19.0-rk3399 is running on both firefly rk3399 and rockpro64, On the first day I have notices 3 issues:  #1. Serial debugging through minicom is not possible, there is no /dev/ttyUSB0 (ls /dev/ttyUSB*).  tail -f /var/log/syslog

    Quote

    failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/fe3c0000.usb/usb2/2-1/2-1.1 2 6': No such file or directory

      #2. It is not possible to install rtl8812au driver for my usb wifi dongle on rockpro64.    But this is a work in progress.

      #3. Bluetooth missing.  "This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.

  13. Did armbian-config through ssh and did system and nightly development build.  Now the display is back with kernel 4.19.0 .

     

    Quote

    steini@firefly:~$ ssh 192.168.1.8
    steini@192.168.1.8's password:
     ____            _    ____               __   _  _   
    |  _ \ ___   ___| | _|  _ \ _ __ ___    / /_ | || |  
    | |_) / _ \ / __| |/ / |_) | '__/ _ \  | '_ \| || |_
    |  _ < (_) | (__|   <|  __/| | | (_) | | (_) |__   _|
    |_| \_\___/ \___|_|\_\_|   |_|  \___/   \___/   |_|  
                                                         

    Welcome to ARMBIAN 5.67.181213 nightly Ubuntu 18.04.1 LTS 4.19.0-rc4-rockchip64   
    System load:   1.27 0.53 0.19      Up time:       1 min        
    Memory usage:  8 % of 3886MB     IP:            192.168.1.8
    CPU temp:      40°C               
    Usage of /:    10% of 56G        

    [ General system configuration (beta): armbian-config ]

    New to Armbian? Check the documentation first: https://docs.armbian.com
    Last login: Sat Dec 15 18:46:01 2018

    steini@rockpro64:~$ uname -a
    Linux rockpro64 4.19.0-rc4-rockchip64 #5 SMP Fri Dec 14 01:01:49 CET 2018 aarch64 aarch64 aarch64 GNU/Linux
    steini@rockpro64:~$

     

  14. Ok, this is getting somewhere. 

    Quote

    uname -a                                                                                     
    Linux rockpro64 4.18.0-rc8-rk3399 #8 SMP Mon Aug 13 03:04:15 CEST 2018 aarch64 aarch64 aarch64 GNU/Linux

    But there is no display connection.   So just connecting from firefly rk3399 to rockpro64 through minicom /dev/ttsyUSB0 and serial debug device, and ssh and trying to figure out why there is no display connection through hdmi with kernel 4.18.0.    Do you have any ideas?   

     

    This is what is in /etc/X11/xorg.conf.d/01-armbian-defaults.conf

     

    Quote

    Section "Monitor"
            Identifier              "Monitor0"
            Option                  "DPMS" "false"
    EndSection
    Section "ServerFlags"
            Option                  "BlankTime" "0"
            Option                  "StandbyTime" "0"
            Option                  "SuspendTime" "0"
            Option                  "OffTime" "0"
    EndSection

     

     

     

  15. It is not so simple.   It seems to me that the kernel headers and kernel source are not available for kernel 4.4.166.

     

    Quote

    root@rockpro64:/home/steini# ls /usr/src
    linux-headers-4.4.156-rk3399      linux-rockchip64-default_4.4.156_5.60_config
    linux-headers-4.4.156-rockchip64  linux-source-4.4.156-rockchip64.tar
    root@rockpro64:/home/steini# 

     

  16. Get this error when trying to install rtl8812au-dkms on a armbian ubuntu 18.04 desktop for rockpro64. 

    Quote

    oot@rockpro64:/home/steini# dkms status
    rtl8812au, 4.3.8.12175.20140902+dfsg: added
    root@rockpro64:/home/steini# dkms autoinstall
    Error! Your kernel headers for kernel 4.4.166-rockchip64 cannot be found.
    Please install the linux-headers-4.4.166-rockchip64 package,
    or use the --kernelsourcedir option to tell DKMS where it's located
    root@rockpro64:/home/steini# uname -a
    Linux rockpro64 4.4.166-rockchip64 #17 SMP Mon Dec 3 16:25:27 CET 2018 aarch64 aarch64 aarch64 GNU/Linux

     

    Then when searching in aptitude for kernel-headers-4.4.166 then they are not available.    It is also impossible to compile because of the missing kernels headers. 

     

  17. Did try armbian for firefly rk3399 and it did work quite well, actually much better than the firefly ubuntu 16.04.   Then I did install the system on the emmc with armbian-config and was very fast.    Somehow I managed to corrupt the emmc later on and now I can only use one SD image from firefly on the board ( mentioned here  http://bbs.t-firefly.com/forum.php?mod=viewthread&amp;tid=1921&amp;extra=page%3D1&amp;page=2  

     

    Now I am wiping the emmc wit blkdiscard /dev/mmcblk1 hoping to be able to flash with upgrade_tool.     Is it possible to install armbian for firefly on the official firefly SD image and then from there to the emmc drive.   Did try it before with armbian-config but it did not offer to flash boot from emmc sd and usb.   

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines