Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Today
  2. TonyMac32

    Le Potato - writing armbian to eMMC

    I have a CoCo 2 and a Model 100 Portable.
  3. Yes I did notice odd numbers but forgot to check. I do have some thermometer around but I am not close to the boards until tomorrow evening.
  4. parrotgeek1

    Orange Pi i96

    No - source: had 2G-IoT; threw it in trash
  5. Took me over a year to isolate this bug. Randomly, I have found that /boot/armbianEnv.txt had unconsistent content. Examples: .tty1tty1LOGIN.8 ¹[fU7ttyS0tyS0LOGINusbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u network={ ssid="Demaine_40_Grd_Rue_Chambre-BP" #psk="1234567890" psk=693d195a3bf2ab6defbcc0b54604ced4286a067996138db6dc793d8648f67d79 } usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u network={ ssid="fabste" #psk="1234567890" psk=95342031a4b28398045e1761f9c64f8454902e80d37102e5476fa79abd59e144 } 2 } usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u At last, I have found that "fabste" is the SSID of the network of my neighbour. How did this get here ? The bug occurs only on Orange Pi Zero boards ... which need to perform wifi scan. Does not happen on boards that operate as WIFI AP, or use ethernet. The wifi scan is required to connect to the AP. The scan seem to produce a temp file somewhere (maybe in /tmp, not sure). Then, later, /etc/init.d/armhwinfo runs this, which is very suspicious to me: read USBQUIRKS <${TMPFILE} sed -i '/^usbstoragequirks/d' /boot/armbianEnv.txt echo "usbstoragequirks=${USBQUIRKS}" >>/boot/armbianEnv.txt and if this is followed by a power failure, you end up with a corrupted file: It's a rare issue from Google point of view; but it's known, and it makes most of my opi0 unusable. Sooner or later, it affects 100% of my opi0 that work as wifi clients. It rendends my pis unusable because I need very specific features which are set in /boot/armbianEnv.txt , usually w1-gpio. When the file is corrupted, and after reboot, I loose control over my 1W devices, and the whole project got broken. Here is my fstab, in case it matters: UUID=ebe9dacf-124f-486c-b6c1-08749e209374 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 I am not sure how to fix this at the distribution level: - use something different than sed in armhwinfo to alter /boot/armbianEnv.txt - perform a sync - change ext4 features - change mount options For now, I am trying to write a personnal fix: record a backup copy of /boot/armbianEnv.txt and restaure it if critical words like "overlay_prefix=sun8i-h3" disappear. Note that, when the file is heavily broken, for all 3 examples above, the pi can boot, establish network connexion, and remains reachable, mostly. I only loose the 1W or GPIO feature. There seem to be very good default settings set as fallback somewhere else. Here are unaffected opis: verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=cir usbhost2 usbhost3 w1-gpio param_w1_pin=PA15 rootdev=UUID=ebe9dacf-124f-486c-b6c1-08749e209374 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 w1-gpio param_w1_pin=PA15 rootdev=UUID=ebe9dacf-124f-486c-b6c1-08749e209374 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I am not sure why one has an empty line. But in both case, the usbstoragequirks line is doubled, and identical to my eyes. This means, /etc/init.d/armhwinfo tries to add already existing data. This script lacks checks !!! .
  6. count-doku

    read first How to build my own image or kernel?

    I used this as a patch. That enables building of the pcm5102a module. Put it in userpatches/kernel/yourkernel I got the feeling that Kconfig just doesnt show entries without a text in menuconfig. diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig index c367d110..87c6ae4c 100644 --- a/sound/soc/codecs/Kconfig +++ b/sound/soc/codecs/Kconfig @@ -680,7 +680,7 @@ config SND_SOC_PCM3168A_SPI select REGMAP_SPI config SND_SOC_PCM5102A - tristate + tristate "Texas Instruments PCM5102A CODEC - I2S" config SND_SOC_PCM512x tristate
  7. Since "dd" doesn't any "verify" during or after "writing", there is no guaranty that binary integrity is Ok.
  8. martinayotte

    OPi Lite 2 + RPi.GPIO

    You can look at this library, but you will need to tweak base register address to meet the one for H6 : You can read what I've answered previously here :
  9. Newcomer

    Armbian for Amlogic S802/S812

    Hello i own an old mxii 2gb tv box (i think is k200) and i was looking for ages to find a working dtb.img. I tried all of them from many armbian images and nothing worked. But this worked like a charm. How do you find it? From which one armbian image? The only problem i have now is that all armbian i tried does not recognise wifi neither internal nor usb external
  10. @frank-w as far as I understand the purpose for boards which have a SoC link to a DSA is that eth0 should be always up not? see here for config.. e.g. everything related to wan/lan starts with 10. by default all interfaces are bridged and should get their IP by DHCP. It's not 100% satisfying but as long as people don't mess and use networkD, it should work. If people try to use archaic /etc/network and do insane stuff there.. well networkD might not play well as most services which end with s D... For the board bring up, it was IMO the best way to get it working. For configuration afterward.. well people have to understand network d good enough to configure it properly.. If they just purge part without understanding and reading this thread here.. Well you're on your own.. I won't support your mess. one of my concerns when I started the work on this board: and it seems to become true.. It is a board for experienced users or people willing to learn stuff.. @frank-w or @Igor can you please link this thread into the BPi forum? so that people read stuff (or at least have a chance to read) before they mess up their images. I think I was quite open during development/board bring up. Nobody cam up with better ideas how to solve stuff so I did it the way I think it's acceptable...
  12. amirul

    Armbian for TV box rk3328

    5.67 20181117 seems to run better for me, let's see how it goes
  13. Christians

    /var/log always filling up

    /var/log started filling up only a few weeks ago, on 18.04. I upgraded in the hope the issue would go away - it did not. armbianmonitor: showed "no space left on device" I have since disabled log in /etc/default/armbian-ramlog, rebooted enabled ramlog, rebooted increased ramlog to 100M armbianmonitor: no more space issues shown It could be that my issue is fixed. Thank You.
  14. Hello jscax, Are you saying that the YS-IRTM uses the "UPD6121". I thought it used a STC11F02 microcontroller. I am frustrated about finding information on the module I bought - looks like the one in your link to Aliexpress. STC11F02 is an 8051 micro - I will see if I can use STC software to get the embedded firmware, and try to disassemble it.
  15. Boogaloo

    i2c and i2s on rock64

    Hi, Have you managed to use I2C with Rock64 ? I will soon have to port part of a project under ESP8266 to Rock64, and I need to use I2C with an Oled SSD1306 controller, thanks in advance for sharing your experience.
  16. I made some changes to my fork, in particular I reverted back kernel configs to current mainline and just enabled brcmfmac and remote GPIO IR drivers, both as modules. I'm a bit puzzled by brcmfmac firmware handling, in particular the place the driver looks into for the firmware and nvram. Currently I add extraargs=brcmfmac.alternative_fw_path=ap6330 in armbianEnv.txt and firmware files are put in /lib/firmware/ap6330/brcm path. I'm still studying a way to be consistent with armbian-firmware ampak drivers approach, so any suggestion in this sense is appreciated.
  17. Reddwarf

    ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)

    I have tried all the gxbb dtb's on previous versions and the only one that works with those mentioned boxes is the p200 dtb.
  18. nonobond007

    move home on sd card

    Hello, thank you for the answer but I managed it thanks to this method (4.2 section of this web page -French Ubuntu site - : ) Copy the contents of the current / home into the new: sudo rsync -av /home/ /new.home Check for security the contents of the future / home: ls -la /new.home Then change the name of the old / home to /old.home: sudo mv /home /old.home Restart Disk-Manager to assign the new mount point / home to the sdaX partition Restart the computer. The new / home is mounted and in use.
  19. TonyMac32

    Odroid C2 general

    I would agree with that, but some of these are simple enough with the documentation in the kernel. The C2 appears to be set up for overlays, I'll have to experiment with that as well.
  20. Thanks for reply. I did the way you told and discovered, that UUID was correct in /etc/fstab on my SDCard and different from given in an error message. So i suggested wrong UUID was in linux image, and checked "/boot". The uInitrd symlink was pointing to "dev" version, while others were pointing to "next". Re-linking it back to "next" helped to boot my board, and then i found both image packages installed and removed "linux-image-dev-sunxi".
  21. martinayotte

    Orange Pi PC 1-Wire

    Why the pullup is commented out ? Do you have an external one ? This doesn't come from Armbian patches, maybe a bug have been introduced upstream ... On my side, my DS18B20 is registering properly on my OPi_2E under 4.19.2 : [ 20.168937] w1_master_driver w1_bus_master1: Attaching one wire slave 28.000005a2fac5 crc ea
  22. esbeeb

    NextCloudPi on Armbian ( tested odroid HC1 )

    Yay, the Nextcloud install worked really well. The trick was to completely reflash the MicroSD card with the latest Armbian first. After the NCP installation was all done successfully, when I visited the URL with no FQDN (just https://nextcloudpi and https://nextcloudpi:4443), then it all worked well. Edit: I was able to get my FQDN working well with the following command, as root: sudo -u www-data /var/www/nextcloud/occ config:system:set trusted_domains 9
  23. shaun27

    Quick review of NanoPi Fire3

    Bit of an update regarding power button not working on nanopi fire3. Tech support got back to me and its missing a driver which is located friendlyarm kernel source code. I am not sure how to implement this yet but will look into it as and when i get some more time, hopefully we can implement this into armbian.
  24. After re-installing to the latest Armbian, my DNS issues went away. PS: Try the command: sudo systemd-resolve --status
  25. Seasalt

    Armbian for Amlogic S9xxx kernel 4.1x (>= ver 5.55)

    I am using the latest version. Zram is a total success. Has made a big difference to my Mecool 1 GB s912. Much Much more stable OS. But I lost ethernet driver so I just plugged a wifi dongle in and all is working. Thanks heaps babes.
  26. Gianni Romano

    Guide: Orage Pi Zero WiFi AP hotspot

    Which version of orange Pi has a better chip suitable for being used as stable AP?
  1. Load more activity