guidol

  • Posts

    1768
  • Joined

  • Last visited

Reputation Activity

  1. Like
    guidol reacted to Hans Kurscheidt in Where is "default_trigger" set at boot for red LED Allwinner H5   
    Thank-you, that did the trick!
  2. Like
    guidol reacted to Igor in Armbian 22.02 (Pig) Release Thread   
    Improved testing on hardware - its attached to nightly builds and currently needs to be run manually:
     

     
    connects to the device via SSH as root (ssh key must be there) runs apt update + upgrade reboots waits 3 minutes that machine is back true or false power cycle the board in case of false (where we have power control)  
    Currently 38 boards are attached, but its very simple to add more of them.
  3. Like
    guidol reacted to magic_sam in My pcDuino4 Nano wanted to say "Thank You" :)   
    Dear all,
     
    First post here
     
    I just wanted to thank you for the up-to-date image you made for the pcDuino4 Nano (a.k.a the NanoPI M1):
     
    https://armbian.hosthatch.com/archive/nanopim1/archive/
     
    It's much better than the stock image provided my LinkSprite, based upon Debian 8 "Jessie":
     
    https://www.linksprite.com/pcduino4-nano/
     
    I only had one issue so far with your image, certainly related to the default overclocking at 1368 MHz, which didn't play well with the CPU intensive, NEON optimized tasks I threw at it (BOINC)
     
    I lowered the frequency to 1296 MHz and it's been running stable for a couple of hours now
     
    So thanks again and keep up the good work !
     
    Best regards,
     
    Magic Sam from the Open Pandora / Dragonbox Pyra community
     
    https://www.openpandora.org/
    https://pyra-handheld.com/boards/pages/pyra/
  4. Like
    guidol reacted to MacBreaker in Orange Pi one two usb host ports possible?   
    Yes, that was the information what I was missing..
     
    I was thinking about that, but I didn't find that information.
     
    Thanks for sharing your DTB, but i'm on 5.10.60.
    I froze the kernel and changed my DTB, all is fine now!
     
    @guidol
     
    Liebe Grüsse aus Bishkek/Kirgistan wo ich zeitweise außer in Haiger/Hessen lebe..
  5. Like
    guidol got a reaction from MacBreaker in Orange Pi one two usb host ports possible?   
    As I read
    http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=3399
    it seems to be possible.
    At the URL is a information how to change the .DTB for the OPi Zero to use the USB-OTG as USB-HOST
     
    You have to find the right usb-port (usb@1c19000) in the .DTB/.DTS for the OPi One
     
    DTB to DTS decompile
    dtc -I dtb -O dts /boot/dtb/sun8i-h3-orangepi-one.dtb -o /boot/dtb/sun8i-h3-orangepi-one.dts
     
    EDIT
    change in the .DTS:
    change the line:
                            dr_mode = "otg";
    to                     dr_mode = "host";
    in the section
    usb@1c19000
     
    from: usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x03 0x20>; resets = <0x03 0x11>; interrupts = <0x00 0x47 0x04>; interrupt-names = "mc"; phys = <0x10 0x00>; phy-names = "usb"; extcon = <0x10 0x00>; dr_mode = "otg"; status = "okay"; phandle = <0x48>; }; to: usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x03 0x20>; resets = <0x03 0x11>; interrupts = <0x00 0x47 0x04>; interrupt-names = "mc"; phys = <0x10 0x00>; phy-names = "usb"; extcon = <0x10 0x00>; dr_mode = "host"; status = "okay"; phandle = <0x48>; };  
     
    DTS to DTB compile
    dtc -I dts -O dtb /boot/dtb/sun8i-h3-orangepi-one.dts -o /boot/dtb/sun8i-h3-orangepi-one.dtb
     
    then REBOOT
     
    As attachment the new compiled version (when you have the same kernel as I 5.15.4
     
    @MacBreaker
    PS: Liebe Gruesse nach Hessen - vor 6 Jahren habe ich in Babenhausen bei Frankfurt/Darmstadt gewohnt - nun in der Tuerkei....
    sun8i-h3-orangepi-one.dtb
  6. Like
    guidol got a reaction from NicoD in Video : Armbian for the Raspberry Pi 4 ! ! ! Preview ! ! !   
    @NicoD
    why only for the RPI4?
    I commented out (like you said in the video) the 2GHz overclock out of the config.txt and booted the image on the RPI3b(+)
    for a headless-server-only version (No Desktop)
     
    Little problem was the /erc/rc.local where I mount my SAMBA from another pistyle-sbc, because the Network card is getting up very late.
    So I had to add a "sleep 20" at the beginning of my /etc/rc.local
     
    Armbian on my the RPi 3B v1.2 takes around 185MB for booting - so enough space to do something
     
    Because onboard audio doesnt work I used a USB-Audio with a proper /etc/asound.conf
     
    After a "dpkg-reconfigure console-setup" the RPi does copy many new/current modules again and seem to setup the system better.
     
    To gain back some memory from the RPi3 I changed the GPU memory in the config.txt from 256MB to 32MB to get 950MB useable for the headless-server
     
    armbianmonitor -u result at:
    http://ix.io/3Fly
     
     

  7. Like
    guidol got a reaction from NicoD in Video : Armbian for the Raspberry Pi 4 ! ! ! Preview ! ! !   
    @NicoD
    why only for the RPI4?
    I commented out (like you said in the video) the 2GHz overclock out of the config.txt and booted the image on the RPI3b(+)
    for a headless-server-only version (No Desktop)
     
    Little problem was the /erc/rc.local where I mount my SAMBA from another pistyle-sbc, because the Network card is getting up very late.
    So I had to add a "sleep 20" at the beginning of my /etc/rc.local
     
    Armbian on my the RPi 3B v1.2 takes around 185MB for booting - so enough space to do something
     
    Because onboard audio doesnt work I used a USB-Audio with a proper /etc/asound.conf
     
    After a "dpkg-reconfigure console-setup" the RPi does copy many new/current modules again and seem to setup the system better.
     
    To gain back some memory from the RPi3 I changed the GPU memory in the config.txt from 256MB to 32MB to get 950MB useable for the headless-server
     
    armbianmonitor -u result at:
    http://ix.io/3Fly
     
     

  8. Like
    guidol got a reaction from mahaju in Orange Pi 2G-IOT   
    as a normal armbian-image it should be root as user and 1234 as initial password
  9. Like
    guidol reacted to Gabor Hidvegi in Orange Pi 2G-IOT   
    Hello all,
     
    I bought one of these nice little devices, and and after a week of playing with it, I'm quite satisfied. Of course the software side is not the best, but the board itself is powerful, cheap, and it is full of features.
     
    Right now all I am missing is a working LCD under Linux. I bought the official phone display from Aliexpress, it works under Android, but no success so far in Linux. So I'm looking for some help here with it.
     
    I have cleaned and formatted the kernel source code (kernel/drivers/video/rda directory), it uses and registers the ILI9806g_mcu according to the dmesg output, but there is only garbage on the screen after it is initialized. So I think the FrameBuffer driver maps to a wrong RAM address. The rda-fb module outputs this: "rda-fb rda-fb: init done, 480 x 800 = 1540096, at cf028000, phys 0x8e200000"
    When I convert the 0x8e200000 to decimal, it is an insanely high number (around 2 terabytes), which is suspicious.
     
    Is there anyone here with kernel and LCD programming experience, who could help me with sorting this out?

    I also tried to compile a kernel from the released Android source code, which is a bit different, but it doesn't work either. My next project is to make working the Vivante driver, also found in the Android source.
  10. Like
    guidol got a reaction from NicoD in [Info] BASIC Engine NG (Next Generation) for H3-CPU Boards   
    If you have time and a spare Allwinner H3-CPU system (like the Orange Pi One or PC (not PC2 because of H3 CPU)
    you could try the BASIC Engine NG for H3-PiComputers/Boards.
     
    The - bare metall - BASIC seems to have very powerful commands - see the Online-Manual
     
    A forum in BETA state is at this URL
     
    I downloaded and booted the SDCard-Image from the 14.10.2021 (compressed size 5.4MB) from this directory
    Image was written with Balena Etcher to the SDCard
     
    Have fun and write new BASIC-programms!  
     

     

     

  11. Like
    guidol reacted to sockscap in What actions should I do to make sure bluetooth is completely disabled?   
    Thanks! lsmod / blacklist the modules resolves the issue.
  12. Like
    guidol reacted to Myron in The LED1 and LED2 on the BanabaPi Pro. How do I get them to show MMC card usage and the watchdog heart beat?   
    Thank-you everyone. I would mark multiple solutions, but the board only allows me to mark one.

    I got it working. Used the cron @reboot method on user root.  The LEDs are useful where on the screen it may look like it's got stuck, the LEDs will at least show if there is some activity and if the SOC is still got a heartbeat.  I'm still a noob on the higher technical issues of Linux.  I have one more question to ask and that will be in another thread.    (Yes, I will donate!  I've seen the donate link on the Armbian home page, but as you all know, the budget that keeps the roof over the head, electricity supplied, food on the table, etc... is priority. Shall donate what I can, when I can.)
     
    EDIT: I finally ended up using the /etc/rc.local method.  Thank-you @Werner and @guidol.
  13. Like
    guidol got a reaction from Myron in The LED1 and LED2 on the BanabaPi Pro. How do I get them to show MMC card usage and the watchdog heart beat?   
    on my BananaPi M1 I can only control the green LED, but for that usage I do use the following command-line:
    echo 'mmc0' > /sys/class/leds/bananapi:green:usr/trigger only green LED available: # ls -l /sys/class/leds/ lrwxrwxrwx 1 root root 0 Sep 11 22:11 bananapi:green:usr -> ./../devices/platform/leds/leds/bananapi:green:usr  
  14. Like
    guidol got a reaction from Rabux in NanoPI M4: Disable LEDs and WiFi   
    for the LEDs you can try the following:

    ls -l /sys/class/leds
    (here as example from a NanoPi Neo2):
    lrwxrwxrwx 1 root root 0 Feb 20 21:50 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status
    lrwxrwxrwx 1 root root 0 Feb 20 21:50 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr
     
    then echo none to the trigger of the led-name: 
     
    echo 'none' > /sys/class/leds/[name_of_the_led]/trigger
     
    so it should look like this:
     
    echo 'none' > /sys/class/leds/nanopi:green:status/trigger
     
    You only have to check the led-names of your board and add the commands in /etc/rc.local before "exit 0"
  15. Like
    guidol reacted to lvmc in The repository 'http://apt.armbian.com xenial Release' does not have a Release file.   
    @guidol, I was talking with @Igor these days and I think the main issue is how slow (and prone to errors) is the repository generator scripts for generating packages for all releases... it's time consuming and requires a lot of efforts from him. I'm taking a look at the scripts to see if I find a way to optimize it. Older releases must be support as `csc` I think.
     
    And yes, I'm using exactly the repositories you suggested, thanks:
     
    deb http://ports.ubuntu.com/ xenial main restricted universe multiverse #deb-src http://ports.ubuntu.com/ xenial main restricted universe multiverse deb http://ports.ubuntu.com/ xenial-security main restricted universe multiverse #deb-src http://ports.ubuntu.com/ xenial-security main restricted universe multiverse deb http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse #deb-src http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse deb http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse #deb-src http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse  
    By the way now it's clearly that the affected packages are only the ones that are build by Armbian, not the packages that are provided by the official Ubuntu repositories.
  16. Like
    guidol reacted to Elric in [Solved] Bananapi M1 doesn't boot when Wireless Desktop Reciever is plugged in   
    Downloaded new image Armbian_21.08.1_Bananapi_buster_current_5.10.60.img today, flashed it to sdcard and started with a Unifying reciever plugged-in. Everything was fine, kernel starts without any troubles. Thanks for providing a new installation image!
  17. Like
    guidol reacted to Werner in Armbian (Debian Bulleye) - supported or not?   
    Yes,  Bullseye will be supported while Buster phases out but may take a few additional month to get things prepared.
  18. Like
    guidol reacted to Igor in Problems with the RTL8192cu driver   
    Also for other reason. We keep well known and those a bit less known wireless drivers in best possible shape and bundled with kernels we provide. In theory - users should not need to compile exotic drivers that Linux doesn't support (well enough) on their own, but all dependencies are ready (kernel headers, compilers) - so you can. For things we don't cover, can't bundle (zfs) or for experimenting ...
     

    We all are 
     
    It is impossible to know everything, especially in this tech world full of complicated details.
  19. Like
    guidol reacted to Igor in Problems with the RTL8192cu driver   
    In fact it is. Starting with v197 systemd:
    https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_predictable_network_interface_device_names
     
  20. Like
    guidol got a reaction from gounthar in How would you implement a super precise clock with a board running Armbian?   
    @gounthar also maybe here some other idea?
    https://hackaday.com/2021/08/16/new-part-day-raspberry-pi-hat-for-ieee1588-precision-time-protocol/
  21. Like
    guidol got a reaction from Werner in [Short Info] Pihole on unsupported OS   
    As Hirsute Hippo is at this time also a unsupported OS - there is another catch to get the lighthttpd of pihole working with the Hippo  
     
    While using the PIHOLE_SKIP_OS_CHECK=true the install-routine cant restart the lighthttpd correctly, because the package 
    lighttpd-mod-deflate
    is missing
     
    When the install routine does try to restart the lighthttpd it fails with:
     
    journalctl -u lighttpd configfile.c.461) Warning: "mod_compress" is DEPRECATED and has been replaced with "mod_deflate". A future release of lighttpd 1.4.x will not contain mod_compresss and lighttpd may fail to start up plugin.c.195) dlopen() failed for: /usr/lib/lighttpd/mod_deflate.so /usr/lib/lighttpd/mod_deflate.so: cannot open shared object file: No such file or directory server.c.1238) loading plugins finally failed  
    The Hippo has no mod_compress in the lighthttpd  but its searching for the replacement mod_deflate
     
    mod_deflate can be installed via 
    apt install lighttpd-mod-deflate
     
    While there were also other requirements missing on new installs of pihole I did use the following install-command:
     
    apt install php-cgi php-common php php-sqlite3 dhcpcd5 lighttpd-mod-deflate -y && curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash  
    As a "goodie" you can edit after the installation od pihole the /etc/lighttpd/lighttpd.conf and do the follwoing replacement:
    change line "mod_compress", against "mod_deflate", then save/exit and restart lighthttpd with 
    /etc/init.d/lighttpd restart
     
    This way I got pihole running under Hirsute Hippo  
     
  22. Like
    guidol reacted to BarTender in Odroid C2 : no eth0 with latest image   
    Just had the same problem as well, was running Buster without an issue on my C2 and needed to move to Focal for a few annoying reasons using the non desktop download https://redirect.armbian.com/region/AS/odroidc2/Focal_current and can see I also have the same issue with uboot failing to find the network adapter. I can pull the version out of the running Bionic image and then dd it onto the eMMC.
    I eventually got my host working by taking the uboot from Bionic:
    wget https://armbian.systemonachip.net/archive/odroidc2/archive/Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.7z 7z e Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.7z dd if=Armbian_20.02.8_Odroidc2_bionic_current_5.4.28_desktop.img of=bionicuboot.bin bs=512 seek=1 skip=1 count=4096 then put onto the emmc: dd if=bionicuboot.bin of=/dev/sdb bs=512 seek=1 skip=1  
    Further edit.. I am going to search for my serial console tonight when I get home to help debug the root cause. I am also running the same C2 board revision as @guidol as per this post: 
     
  23. Like
    guidol reacted to qualle337 in Fail to Boot with Serial Device Connected to USB   
    Yes - looks like you're right! Thanks for pointing me in this direction. I'll update the thread when I found a solution (other than plugging in the Arduino after the boot) in case someone else has similar issues.

    Cheers,
    Julius
  24. Like
    guidol reacted to griefman in Failing to Boot   
    So, 
    after struggling for quite some time i finally was able to get things back to normal without losing data (at least i think so).
     
    The problem was apparently a broken kernel upgrade to version 5.10.43 . There were broken symlinks and not only. 
     
    In the end what solved it was the following:
    I first put the latest stable armbian on an sd card and booted with it. then i actually upgraded that image to the latest kernel and copied all version related files from /boot of the sd card to the /boot of the mmc. I also copied the 5.10.45 modules from /lib/module from the sd card to the mmc.
    Fixed all symlinks in /boot and then the device finally booted. After that it was all about reinstalling kernel headers, cleaning up wrong zfs versions and packages and rebooting frequently enough in between
     
    Hope that i didnt break too much and that this helps someone.
  25. Like
    guidol reacted to bartek666666 in Allwiner A10 tablet USB not working [SOLVED]   
    Okay, I'm a noob but finally it works. .dts for anyone that is curious. now i just need to enable LCD in u-boot
     
    /dts-v1/; #include "sun4i-a10.dtsi" #include "sunxi-common-regulators.dtsi" #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/pwm/pwm.h> / { model = "Cubietech Cubieboard"; compatible = "cubietech,a10-cubieboard", "allwinner,sun4i-a10"; aliases { serial0 = &uart0; }; chosen { stdout-path = "serial0:115200n8"; }; hdmi-connector { compatible = "hdmi-connector"; type = "a"; port { hdmi_con_in: endpoint { remote-endpoint = <&hdmi_out_con>; }; }; }; }; &ahci { target-supply = <&reg_ahci_5v>; status = "okay"; }; &codec { status = "okay"; }; &cpu0 { cpu-supply = <&reg_dcdc2>; }; &de { status = "okay"; }; &ehci0 { status = "okay"; }; &ehci1 { status = "okay"; }; &emac { phy-handle = <&phy1>; status = "okay"; }; &emac_sram { status = "okay"; }; &hdmi { status = "okay"; }; &hdmi_out { hdmi_out_con: endpoint { remote-endpoint = <&hdmi_con_in>; }; }; &i2c0 { status = "okay"; axp209: pmic@34 { reg = <0x34>; interrupts = <0>; }; }; &i2c1 { status = "okay"; }; &ir0 { pinctrl-names = "default"; pinctrl-0 = <&ir0_rx_pins>; status = "okay"; }; &mdio { status = "okay"; phy1: ethernet-phy@1 { reg = <1>; }; }; &mmc0 { vmmc-supply = <&reg_vcc3v3>; bus-width = <4>; cd-gpios = <&pio 7 1 GPIO_ACTIVE_LOW>; /* PH1 */ status = "okay"; }; &ohci0 { status = "okay"; }; &ohci1 { status = "okay"; }; &otg_sram { status = "okay"; }; &pio { usb0_id_detect_pin: usb0-id-detect-pin { pins = "PH4"; function = "gpio_in"; bias-pull-up; }; usb0_vbus_detect_pin: usb0-vbus-detect-pin { pins = "PH5"; function = "gpio_in"; bias-pull-down; }; }; &reg_ahci_5v { status = "okay"; }; #include "axp209.dtsi" &ac_power_supply { status = "okay"; }; &reg_dcdc2 { regulator-always-on; regulator-min-microvolt = <1000000>; regulator-max-microvolt = <1400000>; regulator-name = "vdd-cpu"; }; &reg_dcdc3 { regulator-always-on; regulator-min-microvolt = <1000000>; regulator-max-microvolt = <1250000>; regulator-name = "vdd-int-dll"; }; &reg_ldo1 { regulator-name = "vdd-rtc"; }; &reg_ldo2 { regulator-always-on; regulator-min-microvolt = <3000000>; regulator-max-microvolt = <3000000>; regulator-name = "avcc"; }; &reg_usb0_vbus { status = "okay"; }; &reg_usb1_vbus { status = "okay"; }; &reg_usb2_vbus { status = "okay"; }; &spi0 { pinctrl-names = "default"; pinctrl-0 = <&spi0_pi_pins>, <&spi0_cs0_pi_pin>; status = "okay"; }; &uart0 { pinctrl-names = "default"; pinctrl-0 = <&uart0_pb_pins>; status = "okay"; }; &usb_otg { dr_mode = "host"; status = "okay"; }; &usbphy { pinctrl-names = "default"; pinctrl-0 = <&usb0_id_detect_pin>, <&usb0_vbus_detect_pin>; usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */ usb0_vbus_det-gpio = <&pio 7 5 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; /* PH5 */ usb0_vbus-supply = <&reg_usb0_vbus>; usb1_vbus-supply = <&reg_usb1_vbus>; usb2_vbus-supply = <&reg_usb2_vbus>; status = "okay"; };