garfius

What have you used?

Same situation here. Documenting. kernel module sunxi-cedrus seems to work, i see it responsible for: /dev/v4l <= /dev/media0 <= /dev/video0 <= I guess the correct ffmpeg codec might be h264_v4l2m2m, but when i use it, i always get: [h264_v4l2m2m @ 0x26de9c0] Could not find a valid device [h264_v4l2m2m @ 0x26de9c0] can't configure encoder A command example might be: ffmpeg -i input.mp4 -an -vcodec h264_v4l2m2m -b:v 2M -pix_fmt nv21 out.mp4 So i guess we are missing an environment variable or a library, or permissions? Any help will be appreciated. Thanks. ------------------------extension--------------- using: ffmpeg -loglevel debug -i /home/garfius/input.mp4 -vf scale=1920:1080 -vcodec h264_v4l2m2m -y -an -pix_fmt nv12 -b:v 2M test.mp4 Get: [Parsed_scale_0 @ 0x21ed1a0] w:1024 h:768 fmt:yuvj420p sar:1/1 -> w:1920 h:1080 fmt:nv12 sar:3/4 flags:0x4 [h264_v4l2m2m @ 0x21ba660] probing device /dev/video0 [h264_v4l2m2m @ 0x21ba660] driver 'cedrus' on card 'cedrus' in splane mode [h264_v4l2m2m @ 0x21ba660] v4l2 capture format not supported [h264_v4l2m2m @ 0x21ba660] Could not find a valid device [h264_v4l2m2m @ 0x21ba660] can't configure encoder

Hello, i have an Orange Pi One H3 512Mb, running Hass(docker) pretty well for years. System Specifications: USB - 1Tb TF card (micro SD), via usb adapter, bought as fat32, formatted as exFat. - Arduino Nano-CH340 GPIO - Arduino Pro mini as binary sensor TF card (micro SD) - SanDisk 16Gb Kernel - Linux armbianKickAss 5.15.72-sunxi #22.08.4 SMP Fri Oct 7 16:45:35 UTC 2022 armv7l GNU/Linux PROBLEM: Commands 'mv' and 'cp' to 1Tb card results in the loss of files. Beheaviour: -shows the files for some time -Detected corruption when folder listed as follows: d????????? ? ? ? ? ? myFolder -fsck.exfat detects a LOT of errors, and removes most of the files TF card details Disk /dev/sda: 1000 GiB, 1073742872576 bytes, 2097154048 sectors Disk model: STORAGE DEVICE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xff629fb5 Device Boot Start End Sectors Size Id Type /dev/sda1 32 2097154047 2097154016 1000G 7 HPFS/NTFS/exFAT Destruction of data root@armbianKickAss:/mnt# fsck.exfat -a /dev/sda1 exfatfsck 1.3.0 Checking file system on /dev/sda1. File system version 1.0 Sector size 512 bytes Cluster size 256 KB Volume size 1000 GB Used space 110 GB Available space 890 GB ERROR: unknown entry type 0xb0. Fix (Y/N)? Y ERROR: too long label (215 chars). ERROR: unknown entry type 0xf4. Fix (Y/N)? Y ----------------a lot of repeating lines----------- ERROR: unknown entry type 0x9f. Fix (Y/N)? Y Totally 13 directories and 19 files. File system checking finished. ERRORS FOUND: 77, FIXED: 76.

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

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...

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

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.

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.

Thanks!

---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

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.

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.

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.

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.