Jump to content

Willy Moto

Members
  • Posts

    41
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Willy Moto reacted to Igor in Armbian UEFI (arm64 and x86)   
    Many of us are using Armbian not just on ARM single board computers but also on servers (bare metal & virtual). We use our builds since we trust it more then Debian, Ubuntu, not to mention other distributions that are recklessly updating and one ends up as an OS tester and not OS user. Personally I use Armbian Jammy on Ryzen 9 workstation with great success. My primary use case is development / productivity. For the road I used to have 13" Dell notebook which recently suddenly died. It was out of warranty so I had to get something new. After some testings of various devices I settled with 12th Gen Intel i5-1240P powered Lenovo. Then I tried many general purpose distros to see how well they work and all had some (minor) troubles ... 

    We are having UEFI images (common image) since some time, but UEFI nor desktops were fine tuned nor ready for such performance daily driver desktop usage. We were close, but not close enough to just run it. Past two weeks we have been lifting general UEFI support, fixed many bugs and what came out is "Armbian ultimate developers desktop build".
     

     
    - improved support in GRUB (armbian wallpaper) & HiDPI GRUB support
    - all preinstalled applications are normal apt packages
    - current 5.15.y kernel, Jammy userland (5.19.y has some strange issues)
    - snapd is not installed (user can install it)
    - HiDPI support (automated adjustments on big screen resolutions)
    - NVIDIA graphics acceleration with proprietary driver (x86 only)
    - Intel graphics acceleration also works out of the box
    - preinstalled Google Chrome (x86 only)
    - preinstalled Microsoft Visual Studio Code (x86 only)
    - ZFS 2.1.5 ready (apt install zfsutils-linux zfs-dkms)
    - face unlock works perfectly fine on this laptop
    - installation to SSD drive to dual boot with Windows 10/11 is supported Armbian classical way by transferring actual live image to the prepared partition via nand-sata-install. All you need to do is prepare spare space on your drive, Windows 10/11 or Linux, UEFI support (most if not all hardware for past 10 years has it).
     
    I have tweaked images (XFCE, Gnome, Cinnamon) a bit to my personal needs, but making changes is welcome.
     
    Nice to have: disk encryption within nand-sata-install, small bug fixing, additional DEs. Currently we have CLI, XFCE, Gnome and Cinnamon. Others are too buggy.
     
    https://www.armbian.com/uefi-x86/
    https://www.armbian.com/uefi-arm64/
     
    Please report where it works and how (well)!
  2. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Glad to hear that you solved the issue; I will put this nvram in the armbian firmware repository as well, thanks!
  3. Like
    Willy Moto reacted to Seth in CSC Armbian for RK3318/RK3328 TV box boards   
    happy to report that the official CSC build from github works flawlessly on my rk3318 box that has ap6334. everything seems to be in order, i did have to rename box64 though to fix the slow dependency building, i also have the smartmontools problem on first boot, but not on the second boot, i have not checked succeeding reboot dmesg though since i had to rebuild my klipper environment. running it at 1.3GHz without any problems so far. uses very little resource when printing, 1-5% cpu usage and 14% ram. 2GB ram and 16G EMMC.
  4. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @Willy Moto I had time to check the apt issue about being slow... it definitely too slow when it generates the dependencies tree, so a get a bit deep into.
    In my case I solved going into /etc/apt/sources.conf.d, renaming of any repository (I suggest box64.conf or nala.conf) with suffix .disabled, run apt update, then enabling back the repository and running again apt update.
    Now the dependencies tree is built in a blink of an eye.
  5. Like
    Willy Moto reacted to SteeMan in Allwinner H6   
    @MBB Are you working to get your patches submitted back to base Armbian?  The reason I'm asking is given your current instructions (pull armbian source, apply your zip of patches) you will run into problems over time as the armbian codebase changes, since you aren't tied to a specific git commit or label.  Also long term where do your end users turn for software support?  Armbian certainly isn't setup to provide end user support for projects like this.  Just wondering about how you envision long term support working as it relates to the armbian code you are building on top of.
  6. Like
    Willy Moto reacted to MBB in Allwinner H6   
    For anyone wanting to build from mainline, we have posted an article with our patches.  These include AC200 Ethernet and XR819 wifi support in kernel 5.15.y.  For edge builds, AC200 Ethernet is supported.  To support the XR819, we'll have to create more patches for the changes in kernel 5.19.  The link is https://www.inovato.com/article/building-armbian.
  7. Like
    Willy Moto reacted to MBB in Allwinner H6   
    Hi @SteeMan!  Thanks for reaching out.  We are great fans of Armbian!  This project rests on the great previous work by @balbes150 and as followed up on by @awawa.  We have simply updated those patches.  Currently, our plan was to keep updating our patches (and add other boxes such as the work being done by @jock), but if there is interest in making this a CSC build, I am more than happy to discuss how you'd like us to proceed.  It is certainly our intent to handle all support and not place any burden on Armbian folks.  Is there a good way to discuss in real time?  You can reach me here:  mike at inovato.com.  I am US West Coast.
  8. Like
  9. Like
    Willy Moto reacted to NicoD in Armbian related videos / video documentation thread!   
    Here all other Armbian related videos.
     
     
     
     
     
     
     
     
     
     
     
     
     
     
     

    And lots of review videos on my channel. So subscribe if you're interested.
    Greetings, NicoD
  10. Like
    Willy Moto reacted to Aapo Tahkola in CSC Armbian for RK3318/RK3328 TV box boards   
    @oolonthegreat @uehqsvbm Do not get too attached to devices that refuse to cooperate after a reasonable amount of effort. Just sell it and recover what you can and get one that people have had better success with. I recently fell into this trap with one particular openwrt supported device I have already spent months on it.
     
  11. Like
    Willy Moto reacted to Aapo Tahkola in CSC Armbian for RK3318/RK3328 TV box boards   
    It appears it does not matter when you plug in HDMI cable. But for 3d printer owners out there I made a parametric cooler case(well top of it anyway)
    https://www.thingiverse.com/thing:5447782
    Certainly sorts out the overheating issue for the time being. Tested with cpuburn-a53
    ln -s /sys/devices/virtual/thermal/thermal_zone0/temp /root/temp; cat /root/temp  
  12. Like
    Willy Moto reacted to rpardini in rock-5b with vendor u-boot & vendor kernel; PR and test images   
    Rock 5b test images, from armbian-next. Using vendor u-boot + patches, and vendor kernel, both straight from radxa's git
     
    XFCE desktop with "browsers" app group
    - https://github.com/rpardini/armbian-release/releases/download/20220710b/Armbian_20220710b-rpardini_Rock-5b_jammy_legacy_5.10.66_xfce_desktop.img.xz
     
    CLI
    - https://github.com/rpardini/armbian-release/releases/download/20220710b/Armbian_20220710b-rpardini_Rock-5b_jammy_legacy_5.10.66.img.xz
     
    PR: https://github.com/armbian/build/pull/3984 (against master)
    All work by @amazingfate I just gathered stuff and built images.
    Thanks to @monkaBlyat @lanefu @piter75 @amazingfate for tests / patches etc
     
     
  13. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Announce:
     
    Hello, I want to announce that Community Supported Configuration (CSC) board images are now built again by Armbian servers on a weekly basis!
    This means that you can now download images for CSC boards (including rk3318-box) browsing from https://github.com/armbian/community
     
    Images are built from trunk, GPG-signed and SHA-sum is provided.
     
    I also removed the manual instructions for upgrades: Armbian 22.08 release is imminent and from that time on it will be sufficient to use apt to get kernel upgrades too! Thanks for your patience!
     
    Feel free to donate if you find this useful and wish to offer support to the Armbian developers and maintainers.
     
    Enjoy!
  14. Like
    Willy Moto reacted to hexdump in Tanix TX6S - H616   
    @rzu- i did not try the images from waprme's minimyth2, but i'm using the patches for both the h6 and h616 to build my own images (not armbian) and they are working very well so far - i would say its the most complete patch collection for h616 right now
     
    best wishes and good luck - hexdump
  15. Like
    Willy Moto reacted to Aapo Tahkola in CSC Armbian for RK3318/RK3328 TV box boards   
    So I build a minimal image from sources with Armbian 22.08.0-trunk Bullseye with Linux 5.15.58-rockchip64 and burned it with multitool without erasing emmc this time.
    Connected sigrok-pico to uart tx line and pulseview at 3mhz and 100M samples uart protocol decoder. It was a bit of a pain using a logic analyzer first time but I found a login prompt and so replaced sigrok-pico with ch340g usb uart and was able to login and create account without any issue this time. No wifi so I just stuck ethernet cable to my router and dhcp gave ip address to it. I connected hdmi and now that works as well. It seems that only 2gb of 4gb ram is detected but I can see that this kind of issues has been discussed before on this thread.

    So to sum it up, it seems 5.18 kernel has no hdmi but if you stick ethernet cable to a dhcp capable router one can get the ip and ssh into it - you probably want to use 5.15 kernel for the time being though. Perhaps something along the lines of git-bisect to get to the bottom of the hdmi issue. I do find it a bit strange that hdmi did not seem to work immediately after flashing. Perhaps one needs to replug the hdmi cable after it has booted.
     
    Feel like a winner already, thanks to everyone working on this!
     
  16. Like
    Willy Moto reacted to paradigman in CSC Armbian for RK3318/RK3328 TV box boards   
    I finally managed to solve the problem, my box can connect to wifi with that new 2734C chip.  Thanks to @jock for directing my attention to the nvram file, I was wrong, dtb was not needed to solve it. However, Google didn't help with the solution (I don't even understand how it could have helped), but I contacted the Chinese manufacturer of the box and they helped. I have attached the correct nvram file, the content of which I overwrote the brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt file that comes with the current image. I recommend that you integrate it into the kernel, because the current kernel does not, or at least does not, support this widely used wireless chip.
    nvram_2734c.txt
  17. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N Didn't you try already 5.18? I remember you already had issues with 5.18, but that was my fault because I downvolted the CPU by mistake; upgrade debs should be fixed now and there should be no issues anymore, as long as also other people found them working stable so far.
     
    About the Jammy edge image, it is an experimental image with KDE Plasma preinstalled. It works, but there is a kernel bug in lima that often causes kernel panics, so it is not "public" not suggested to put in any kind of use.
    The bug seems to be fixed in 5.19, so I guess soon there will be a proper publishing.
  18. Like
    Willy Moto reacted to usual user in CSC Armbian for RK3318/RK3328 TV box boards   
    I think I have to disappoint you, see here.
  19. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @DmitryS There is no opensource OpenCL driver in mesa, what you want to use is the closed source binary.
    The closed source binary requires the closed source drivers; it can be installed and probably brought into working state, but it is a real PITA  since it requires the proprietary mali kernel driver first, then the closed source blobs and finally the closed source OpenCL driver. I hope I scared you enough, because that way is very scary by itself.
     
    Just a side consideration: people, in general, should be very thankful for opensource drivers that make things work out of the box  and should heavily blame companies that put obstacles - like ARM does.
  20. Like
    Willy Moto reacted to DmitryS in CSC Armbian for RK3318/RK3328 TV box boards   
    Thanks for the explanation. I finally unbricked it. What I figured out is that I should put a sd-card. I put it into the board, shortened contacts which MattWestB helped me to find and it booted into multitool where I choose to burn another image and now it boots into it from emmc! Thank you guys!
  21. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @Seth the HDMI disappearing is quite disappointing, since I did not tweak that part in 5.18.
     
    Anyway this looks very suspicious to me:
    [ 2.099836] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 2.100004] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes  and maybe is somehow related to EDID or alike
  22. Like
    Willy Moto reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @callegar@Willy Moto@MX10.AC2N
    Ok, I double checked the cpu voltage supply and effectively it seems that in the latest device tree I pushed it way too low... The original device tree of my box said 1.375v@1.3Ghz, the voltage in mainline kernel says 1.300v@1.3Ghz and I set 1.200v@1.3Ghz. That is very good for temperatures and power consumption, but maybe it is a bit too low for stable operations.
     
    I will rebuild the whole set of images, but in the meantime I updated the dtb deb package you can install that should fix issues: https://users.armbian.com/jock/rk3318/upgrade/linux-dtb-edge-rockchip64_22.08.0-trunk_arm64.deb
     
  23. Like
    Willy Moto reacted to callegar in CSC Armbian for RK3318/RK3328 TV box boards   
    After more tests, what makes the difference is probably not the kernel (5.15 vs 5.18) but the dtb: with linux-dtb-current-rockchip64_22.08.0-trunk_arm64.deb and kernel linux-image-current-rockchip64_22.08.0-trunk_arm64.deb (5.15) the system does not boot, but with the same kernel and the former linux-dtb-current-rockchip64_22.05.0-trunk_arm64.deb the system works fine.
  24. Like
    Willy Moto reacted to Igor in work-around for /var/log full at startup   
    This looks like as ready to put it here https://github.com/armbian/build/pulls 
  25. Like
    Willy Moto reacted to Dennboy in work-around for /var/log full at startup   
    After some experimenting I found a way to flush the journal and maintain logs in tmpfs using /run/log/journal, and only have a softlink from /var/log/journal to /var/log.hdd/journal. Additionally the cached journals are to be cleaned up when /var/log becomes too full.
     
     I created the attached patches for armbian-truncate-logs and armbian-ramlog: armbian-truncate-logs.patcharmbian-ramlog.patch 
     
    Some logic was needed in cases where the user decides to do Storage=volatile journal logging in /etc/systemd/journald.conf, or when the user or journald with Storage=persistent creates a /var/log/journal folder which will be moved to /var/log.hdd/journal and replaced by the softlink.
     
    I tested stop, start, write for armbian-ramlog, and truncate-logs. They seem to work fine.
×
×
  • Create New...