garfius

Members
  • Content Count

    12
  • Joined

  • Last visited

About garfius

  • Rank
    Member

Recent Profile Visitors

255 profile views
  1. I enabled GPIO serial ports via armbianEnv.txt on my Orange pi One, good. Case for port 1 But the serial port file /dev/ttyS1 comes out with wrong permissions, so it cannot be used at first. Just needed: chmod 666 /dev/ttyS1 optional: chown root:root /dev/ttyS1 Thanks
  2. But this only seems to check, not repair. https://unix.stackexchange.com/questions/400851/what-should-i-do-to-force-the-root-filesystem-check-and-optionally-a-fix-at-bo Says: This DID a check, but to force a fix too, you need to specify fsck.repair="preen", or fsck.repair="yes But not where to write this commands...
  3. Thanks! The working commands: #--locate which partition-- df -h #--set check interval-- tune2fs -l /dev/mmcblk0p1 tune2fs -i 2 /dev/mmcblk0p1 tune2fs -c -1 /dev/mmcblk0p1 To check FS every boot: tune2fs -l /dev/mmcblk0p1 tune2fs -i 1 /dev/mmcblk0p1 tune2fs -c 1 /dev/mmcblk0p1
  4. Thanks, but this is not the goal. The goal is to fix any corrupt file at next startup sequence, damage done by an unexpected power off. Already done in other OS, like dietPi or ubuntu on legacy kernels, but don't know the procedure here. The target is an armbian set up on a hard-to-reach place, and i need reliability. Thanks again.
  5. I was reading about hecking the filesystem / Seems the way is: touch /forcefsck But this action does not fix, so we need 'somewhere': fsck.repair=yes How do i have to do it? Thanks.
  6. ---prelude--- Hi! I just installed ARMbian on my AllWinner H3 boards, and works great! (better than DietPi). The only perk was to enable GPIO serial uart ports, edited armbianEnv.txt: overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 uart1 uart2 param_uart1_rtscts=1 param_uart2_rtscts=1 Worked. ---Question---- Where can i find a list of possible 'armbianEnv.txt' parameters for AllWinner H3 boards ?¿ ---Thanks--- The best distro for cheap boards. See hard work here
  7. The ONLY thing a distro is supposed to provide is BOOT, the distro must the one to deal with low-level problems. If the low-level problems are not solved this is s DISTRO-DEVELOPER-ONLY distro. You will never be any popular if you do not provide a sure boot, most people does not have time to deal with such incomplete software.
  8. The ONLY thing a distro is supposed to provide is BOOT, the distro must the one to deal with low-level problems. If the low-level problems are not solved this is s DISTRO-DEVELOPER-ONLY distro. You will never be any popular if you do not provide a sure boot, most people does not have time to deal with such incomplete software. Also you are disrespectful. Le'ts play: your software is unusable crap and your glasses are moron-like close your mouth some d*** may come in.
  9. Leaving armbian for good, it's too incompatible. None of 2 sd cards boot. But there are others that will. I will use a better distribution able to boot. Tnks.
  10. I will not spend money (serial debug) and lots of days to simply boot and test a distribution, i will keep using distributions able to turn on hdmi and show login prompt. All unmodified hardware, all unmodified software, multiple sd card tested. This is not my fault. Armbian needs improvements, i'll try again when this didtribution archieve a single thing: BOOT. See ya.
  11. I have bought an Orange pi One, and i need to get wireless. I have an rtl8188 and a rtl8192. Tested: 1-Official android: workd slow, no wifi 2-Ubuntu lxde 0.9.1: downloaded kernel and cross compiler... error compiling module driver 3-Raspbian: no kernel headers-->Error compiling the kernel. 4-Armbian: No boot No hdmi signal, red light blinking || keeps rebooting What shall i do? Does this board worth it? Thanks.