garfius
-
Posts
15 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by garfius
-
-
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/LinuxPROBLEM:
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 filesTF 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
-
2 hours ago, martinayotte said:
Check "man tune2fs", there the option "-c <n>" to call fsck.ext4 every "n" reboot.
But this only seems to check, not repair.
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...
-
2 hours ago, martinayotte said:
Check "man tune2fs", there the option "-c <n>" to call fsck.ext4 every "n" reboot.
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/mmcblk0p1To check FS every boot:
tune2fs -l /dev/mmcblk0p1 tune2fs -i 1 /dev/mmcblk0p1 tune2fs -c 1 /dev/mmcblk0p1 -
1 hour ago, Tido said:
Hi, you can start here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system
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.
-
17 hours ago, martinayotte said:
If you means overlays parameters, it is describe in /boot/dtb/overlay/README.sun8i-h3-overlays.
d
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=1Worked.
---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
-
1 hour ago, Igor said:
Now it is.
I asked for serial console output to rule out possible board hardware troubles. We have seen that some boards failed to initialize with a modern u-boot which is used in just about every build. But since you rather waste my time than buying a serial console for 2USD this tells me that it's no use to help you.
1. This image: https://dl.armbian.com/orangepione/Ubuntu_xenial_default.7z2. Boot this way:
U-Boot SPL 2017.05-armbian (Jun 13 2017 - 15:34:52) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2017.05-armbian (Jun 13 2017 - 15:34:52 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 38518 bytes read in 147 ms (255.9 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3565 bytes read in 195 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 115 bytes read in 157 ms (0 Bytes/s) 5154669 bytes read in 512 ms (9.6 MiB/s) 4750952 bytes read in 510 ms (8.9 MiB/s) Found legacy kernel configuration 34880 bytes read in 450 ms (75.2 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5154605 Bytes = 4.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 512MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0x56000000, 0x60000000]! Loading, please wait... starting version 229 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 48744/90432 files, 288129/361472 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 16.04.2 LTS! [ OK ] Reached target Encrypted Volumes. [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket. [ OK ] Created slice User and Session Slice. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Created slice System Slice. [ OK ] Reached target Slices. Starting Restore / save the current clock... Starting Nameserver information manager... Starting Create list of required st... nodes for the current kernel... [ OK ] Created slice system-serial\x2dgetty.slice. Mounting Debug File System... Mounting POSIX Message Queue File System... Starting Set console keymap... [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Paths. [ OK ] Started Trigger resolvconf update for networkd DNS. Starting Remount Root and Kernel File Systems... [ OK ] Listening on Syslog Socket. Starting Load Kernel Modules... [ OK ] Listening on Journal Audit Socket. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Started Restore / save the current clock. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK ] Started Set console keymap. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Load Kernel Modules. [ OK ] Started Nameserver information manager. [ OK ] Reached target Network (Pre). Starting Apply Kernel Variables... Mounting FUSE Control File System... Activating swap /var/swap... Starting udev Coldplug all Devices... Starting Load/Save Random Seed... Starting Create Static Device Nodes in /dev... [ OK ] Mounted FUSE Control File System. [ OK ] Activated swap /var/swap. [ OK ] Started Apply Kernel Variables. [ OK ] Started Load/Save Random Seed. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started udev Coldplug all Devices. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Reached target Swap. [ OK ] Started udev Kernel Device Manager. [ OK ] Mounted /tmp. [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Reached target Local File Systems. Starting Armbian enhanced Log2Ram... Starting Raise network interfaces... Starting Set console font and keymap... [ OK ] Started Armbian enhanced Log2Ram. [ OK ] Started Set console font and keymap. [ OK ] Found device /dev/ttyS0. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ OK ] Started ifup for eth0. [ OK ] Reached target Sound Card. [ OK ] Created slice system-getty.slice. Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Started Raise network interfaces. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Reached target System Time Synchronized. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Started Daily apt activities. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. Starting Armbian filesystem resize service... [ OK ] Started Armbian filesystem resize service. [ OK ] Reached target Basic System. Starting Login Service... Starting Permit User Sessions... [ OK ] Started Regular background program processing daemon. Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: Start/stop sysstat's sadc... Starting Save/Restore Sound Card State... Starting Daily apt activities... Starting LSB: Starts LIRC daemon.... Starting System Logging Service... Starting LSB: Armbian gathering hardware information... [ OK ] Started D-Bus System Message Bus. Starting Network Manager... [ OK ] Started System Logging Service. [ OK ] Started Permit User Sessions. [ OK ] Started Save/Restore Sound Card State. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started LSB: Start/stop sysstat's sadc. [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started Network Manager. [ OK ] Started Login Service. Starting Network Manager Script Dispatcher Service... Starting Network Manager Wait Online... [ OK ] Reached target Network. [ OK ] Started Unattended Upgrades Shutdown. Starting OpenBSD Secure Shell server... Starting LSB: set CPUFreq kernel parameters... Starting Set console scheme... [ OK ] Started OpenBSD Secure Shell server. [ OK ] Started Set console scheme. [ OK ] Started Network Manager Script Dispatcher Service. Starting Hostname Service... [ OK ] Started LSB: set CPUFreq kernel parameters. [ OK ] Started Hostname Service. Starting LSB: Set sysfs variables from /etc/sysfs.conf... Starting Authenticate and Authorize Users to Run Privileged Tasks... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Started Network Manager Wait Online. [ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Reached target Network is Online. Starting LSB: Start NTP daemon... Starting /etc/rc.local Compatibility... Starting LSB: Advanced IEEE 802.11 management daemon... Starting LSB: disk temperature monitoring daemon... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started LSB: Start NTP daemon. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Ubuntu 16.04.2 LTS orangepione ttyS0 orangepione login:
Good luck with distributions that works
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.
-
2 hours ago, tkaiser said:
That's great! We had a patch in the repo last year allowing users to use such very slow SD cards but we removed it by intention. Life is too short to deal with ignorants flooding the forum with weird questions that are all only related to them wanting to run their boards off of crappy SD cards.
Better choose another distro if you're willing to ignore low-level hardware problems! Good luck!
As soon as you can afford buying an SD card that does not suck you can give it a try again.
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.
-
11 hours ago, tkaiser said:
No way, too slow, bootloader times out. Check this link and start to buy something reliable and fast enough: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card
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.
-
On 24/1/2017 at 5:41 PM, Igor said:
Start with getting started https://docs.armbian.com and get serial console to debug.
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.
-
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.
Question about playing video
in Orange Pi Zero 2
Posted
What have you used?