Jump to content

Cornelius

  • Posts

    42
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Mars
  • Interests
    Immediate Disintegration

Contact Methods

  • IRC
    #arm-img-builder
  • Github
    https://github.com/pyavitz

Recent Profile Visitors

2502 profile views
  1. If you open the dts file for said board, you'll see something like this a few lines down from the top -> model = "Hardkernel ODROID-C4"; Whatever you put in there is what will spit out the model. You can name it -> model = "Hookers and Flapjacks"; Although, beyond laughs I see no real point in changing this.
  2. I've also noticed using an overlay to overclock the RK3399 on 5.15.y doesn't work, although in my testing it does work fine on 5.17 / 5.18.y. One solution is to patch the rk3399-opp.dtsi and add a turbo-mode switch. This way the board can be overclocked on the fly with a simple `echo "1" > sudo tee /sys/devices/system/cpu/cpufreq/boost`. 013-rk3399-opp-overclock-2GHz-turbo-mode.patch
  3. What does your extlinux/extlinux.conf file look like? Without seeing the contents I can't be sure, but on its face it looks like it can't load the files, because it can't find them. For example; since you are now booting from a boot partition, it shouldn't be checking for `/boot/$file. Instead it should be loading the files from the `/` of the boot partition.
  4. Armv7 and Locales can sometimes be a bitch. Have you tried? sudo apt update; sudo apt install -y locales-all
  5. I'll start by saying I don't own the board, but as this has come up and seems to be a problem across many boards using the same SoC and bits, it would appear on its face that the fix is probably generally the same across them all. Give or take a few differences? My github reference to the issue: https://github.com/armbian/build/issues/1352#issuecomment-952077351 I've included two patches you could test that I made for 5.10.y as that appears to be the kernel ur using. One thing I do not mention in the github issue is I also include the following to /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. bluetooth hidp rfcomm bnep hci_uart 002-sun50i-h5-orangepi-zero-plus2-rfkill-gpio.patch 001-sun50i-h5-orangepi-zero-plus2-bluetooth-support.patch
  6. I can't be 100% sure, but I believe I saw a pull request for this some time ago where some one removed some things related to the reboot issue. I haven't scanned through the patch set as of late, but in my testing the following is needed. Need to revert: drivers/gpu/drm/meson/meson_drv.c https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L524 https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L542 Add Odroid reboot: https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L2323 https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/odroid/002-linux-odroid-patch-set.patch#L2533 If you review the pull request, you can see where the revert and odroid power reset patch was removed: https://github.com/armbian/build/pull/3154/files As for mainline u-boot the only thing of real importance is the following revert: https://github.com/armbian/build/pull/3154/files#diff-65100acf19e202ac3f3980da554c205752ea3c67d08fc4a3b445d4397189d12fR36 With out it, the boards "especially the N2/+ will kernel panic, as the reserved memory "CMA pool won't be set correctly". So the patch forces the boards to be marked nomap, hence populated after uboot hands off to the kernel.
  7. I believe what is required is this commit added to the meson64 patch set. https://github.com/tobetter/linux/commit/a026e2e9f55116e81ed49f48d918fdb91e28eff6
  8. sudo apt install -y python3-pip; sudo pip3 install bpytop
  9. That's my N2+ burning on all cores running slightly under clocked. It is very rare if it ever gets to 50*C. So for sure the script comes in handy.
  10. I've seen that happen before and has more to do with how people set the systemd services on the OS up more than anything. Most services "if any?" don't account for the rc-local service, so sometimes putting a sleep on your script is the easiest route to take. Happy its working for you.
  11. On the unit make sure what the script is looking for is there `ls /sys/devices/virtual/thermal/thermal_zone0/trip_point_4_temp` As far as I know, on Hardkernel, Armbian and my own image that is the only location that the trip point is located? I guess I should add a check in the functions there to give an error, instead of a bash cry? As for the trip points, I didn't develop anything and as far as I know in my testing that can be set to whatever? It doesn't have to be 35000, it could be 20000 if someone so wanted, which would just make the fan run all the time as the board idles higher than that. I place mine at 45000 as it seems like a happy medium when compiling on it.
  12. In the terminal execute: fan-ctrl -h This will show you a list of all the options available, which include the trip points you can set. Once you select a trip point the script takes note of the choice you made and runs its self. Your trip point is now set and the fan will spin up at the given temp you chose. So in rc.local from that point on you just need to use the run function: fan-ctrl -r You can look over the script here to see what its actually doing: https://github.com/pyavitz/scripts/blob/master/fan-ctrl
  13. Remove all this from /etc/rc.local: [Service] ExecStart=/usr/local/bin/fan-ctrl -r &>/dev/null Type=oneshot RemainAfterExit=yes [Install] WantedBy=multi-user.target EOF sudo systemctl enable odroid-fan-ctrl # Options Odroid N2 Trip Point Usage: fan-ctrl -h -1 65°C -2 55°C -3 45°C -4 35°C -r Run -u Update The script is downloaded already, correct? Set the trip point, for example: fan-ctrl -3 Now have the script run upon boot by adding it to /etc/rc.local. Example: #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. /usr/local/bin/fan-ctrl -r exit 0 That's it!
  14. It's pretty much just a copy and paste job, the above commands do all the work for you. I've personally never used it on Armbian and the only thing I can think of that could create a problem is if the service runs before the armbian-hardware-optimize.service. If that's the case, its an easy enough mod to the odroid-fan-ctrl.service file followed by a daemon-reload. But yeah, using the /etc/rc.local file will accomplish the same thing. You only need to set the trip point once and then have the rc-local service run the script: fan-ctrl -r
  15. I created a script to set the trip point, which can then be run at boot with a service or by placing it in /etc/rc.local # Script sudo wget https://raw.githubusercontent.com/pyavitz/scripts/master/fan-ctrl -P /usr/local/bin sudo chmod +x /usr/local/bin/fan-ctrl # Service sudo tee /etc/systemd/system/odroid-fan-ctrl.service <<EOF [Unit] Description=Odroid Fan Control ConditionPathExists=/usr/local/bin/fan-ctrl [Service] ExecStart=/usr/local/bin/fan-ctrl -r &>/dev/null Type=oneshot RemainAfterExit=yes [Install] WantedBy=multi-user.target EOF sudo systemctl enable odroid-fan-ctrl # Options Odroid N2 Trip Point Usage: fan-ctrl -h -1 65°C -2 55°C -3 45°C -4 35°C -r Run -u Update The systemd service runs 'fan-ctrl -r' during boot. One down side is that it requires sudo to work, so you would need to either edit the script to your needs or setup sudo, so that you don't need a password to execute. But then again, it shouldn't matter when being run as a service, as root shouldn't care about sudo?
×
×
  • Create New...