062621AM

Members
  • Content Count

    22
  • Joined

  • Last visited


Reputation Activity

  1. Like
    062621AM reacted to Igor in Is Powering Down a Work-In-Progress?   
    ./h3fakeoff 
  2. Like
    062621AM reacted to kexec in Orangepi 3 h6 allwiner chip   
    No, I use  apkpure package manager. To much effort needs to be put in, to get google working
  3. Like
    062621AM reacted to martinayotte in Orangepi 3 h6 allwiner chip   
    The OPi-H6 boards are WIP (aka "Work in Progress"), this means you need to build the images yourself.
    It is pretty straight forward : https://docs.armbian.com/Developer-Guide_Build-Preparation/
  4. Like
    062621AM reacted to Tido in Orangepi 3 h6 allwiner chip   
    here you find the overview:  https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
  5. Like
    062621AM reacted to Werner in Orangepi 3 h6 allwiner chip   
    It is the same SoC so yes, it may suffer from all these issues as well.
  6. Like
    062621AM reacted to mboehmer in Rock PI 4   
    Sorry, no link, it was direct contact with the German distributor by phone (and some luck, talking about my specfifc requirements).
  7. Like
    062621AM reacted to IgorS in Real time clock DS3231   
    I have seen many tutorials about connecting real time clock hardware on Orange Pi and Raspberry Pi.
    What i didn't like was removing of fake-hwclock service, because I want that RTC works when it is connected, and fake-hwclock when RTC is not connected.
    Therefore, I changed /sbin/fake-hwclock script to work in this way.
     
    So, here is how to do this, tested on OrangePi+2E, Armbian Ubuntu legacy kernel:
    Purchase cheap DS3231 module on eBay (cca. $1) like this one:
    http://www.ebay.com/itm/DS3231-AT24C32-IIC-Modul-High-Precision-Real-Time-Clock-Module-Arduino-New-/292041844936?hash=item43ff0ce8c8:g:d80AAOSwdGFYtsFP
    Put battery in module.
    Shutdown and powerof OPi and connect module:
    Orange (i2c0 bus) RTC module (DS3231 RTC + 24C32 eeprom) 1 3.3V 2 VCC 3 PA12 (TWI0_SDA/DI_RX/PA_EINT12) 3 SDA 5 PA11 (TWI0_SCK/DI_TX/PA_EINT11) 4 SCL 9 GND 1 GND Power up OPi
    Install i2c-tools.
    sudo apt install i2c-tools Type command:
    i2cdetect -y 0 You should see:
    0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that module is connected properly and that we have DS3231 on address 0x68 and eeprom 24C32 on address 0x57.
    Type:
    sudo echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device i2cdetect -y 0 You should see:
    0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that system is now using our RTC. Also, now should exist new device /dev/rtc1
    Be sure that your system time is right, and type:
    sudo hwclock -w -f /dev/rtc1 Now our RTC must have right time. Check with:
    sudo hwclock -r -f /dev/rtc1 If everithing was ok, copy /sbin/fake-hwclock to bacup (just in case)
    sudo cp ~/programming/sh/fake_hwclock/sbin/fake-hwclock /sbin/fake-hwclock Edit /sbin/fake-hwclock and place this code in it:
    Reboot.
    Now you should have right system time backed up by RTC.
     
  8. Like
    062621AM reacted to Igor in Orange Pi PC+ running Armbian Xenial 5.38 kernel 3.4.113 Pink Screen after intermittent Power Up   
    We stopped to deal with this kernel (3.4.y) a long time ago and you will not find many people around that still do something about it. We fixed a ton of issues but it's impossible to fix them all with resources that are around. Fixes that were discovered are usually implemented. That's what our project essentially do.
     
    Virtually all devs are working only on a modern kernel, (4.17.y ->), which will soon cover most of the functionality. Actually, when video/3D acceleration is working, these old kernel images are going to be trashed. We keep them solo for multimedia capabilities.
     
    This is an old issue which is gone from my head so rather try to do some search for a possible solution.