• Content Count

  • Joined

  • Last visited

  1. I solved this problem temporarily by setting the CPU governor from "performance" to "conservative". This helped reduce the CPU temperature by at least 10°C At least now the fan doesn't spin up as often, maybe once every 15-30 min. I think I might also buy a Noctua NF-A4x10 fan to be able to reduce the temperature even more. Does anyone know if the Noctua fan fits on the same heatsink the stock fan came with?
  2. I'm not sure what makes you think this is a hardware issue. I've tried Arch Linux ARM, and it works fine every time, with the fstab modifications et al.
  3. Does anyone know any way to fix the annoying way the fan works on this device? Even on idle load, the fan spins up every couple of minutes, keeps spinning for a few seconds, then turns off again, only to repeat a few minutes later. I can't even sleep in the same room the device is in... I've tried using this: And it hasn't really solved anything, as the fan cannot start on PWM values lower than 100... it instead makes squeaking noises. So having adjusted the script, nothing has really changed. Is there something I could do to fix this in software? Perhaps something that doesn't involve getting the heatsink for it, or use a different fan. Currently I can't modify anything about the SBC due to the case I got for it...
  4. Okay, I've since reflashed Armbian on the micro SD card, and I no longer had this problem... until today, when I added a partition to fstab, which makes me think your comment on that might have some relevance. How does one deactivate log2ram? For now I've removed the binary from /usr/sbin/ as I couldn't find any pertinent guide to turning it off. Also the uninstall script that comes with the software isn't present in this distro. Mind elaborating a bit? I haven't used that yet. I'll try it if I run out of options. The LAN cable works fine as I've used it with a laptop a week or so ago. Also the power supply is the 6A one provided by Hardkernel, so I doubt it's unfit for this SBC. I did try to change the port to which the cable's connected, but this hasn't helped...
  5. So I have this issue with the XU4, where at times when I start device from the main power button, it doesn't seem to properly connect to the LAN, in such a way that I cannot ssh to it, nor ping it. Since the device is headless, and I can't control it through LAN, I have no way of looking at dmesg during the problematic boots. Are there specific logs I could look at to diagnose this problem?
  6. So I wanted to set up an Odroid XU4 as a low-power low-cost NAS and "seedbox" for a personal project, and I wanted to have a GUI that doesn't take too many resources (or spin the fan too much) due to the fact that qBittorrent can't run as a thin client, and I don't want to have to use a WebUI, nor do I want to use a different client (Transmission frequently has security issues, and Deluge is a bit too resource-intensive). I'm currently using the XU4 headless, and only have it hooked up to LAN, so it's a bit difficult to tell what's going on at system initialisation, and since I'm controlling the device through SSH, I'm unable to manually start X11 after booting and logging in. I've tried to install the desktop packages through the armbian ncurses setup, but I felt it was a bit bloated (I don't really need compositing or any fancy effects, nor do I need all the features in XFCE, and I have no use of PulseAudio), so I decided to set up my own DE, with OpenBox, and no login manager, just so I could VNC into the XU, and look at qBittorrent. So I've installed xorg and it's requirements, also OpenBox, I've set up ~/.xinitrc to start openbox-session, and I've set /etc/X11/Xorg.conf to this: Section "Device" Identifier "Dummy" Driver "dummy" VideoRam 256000 Option "IgnoreEDID" "true" Option "NoDDC" "true" EndSection Section "Monitor" Identifier "Monitor" HorizSync 15.0-100.0 VertRefresh 15.0-200.0 EndSection Section "Screen" Identifier "Screen" Monitor "Monitor" Device "Dummy" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1920x1080" "1280x1024" EndSubSection EndSection But for some reason, X11 doesn't seem to start at all (there are no logs under /var/log/) when I boot the device. I've tried issuing this command after browsing around for a solution: systemctl set-default But it doesn't seem to have fixed anything. Is there something else that needs to be done in order to tell the OS to run X11 at startup? Also, does anyone else know of a more efficient way to do this? VNC seems to cause XU's fan to spin constantly, which I assume means it takes a bit of a toll on the device from what I could tell.