This is a minimal fix for the correct display
of characters in the applications, especially the console.
For example, if the locale-gen command is only for one locale
locale-gen ru_RU.UTF-8
Then the console application MC instead of a line in the frame outputs:
@
@@@@@@@@@@@@@@@@@@
@ README.md
@@@@@@@@@@@@@@@@@@
@
@
Setting variables to LC_ALL=C LANG=C is not necessary in this construction.
The line with the editor is not needed.
The 'locale-gen en_US.UTF-8 xx_XX.UTF-8' command
will fix this file itself.
* Exit if you can't create a directory
Otherwise the entire folder structure will crash
* git rev-parse --git-dir will always return ".git" line
if we are in the git repository folder.
When there is a symbolic link in the path, some functions
will not return what is expected. This condition is always true.
$(git rev-parse --show-toplevel) != $(pwd)
This commit fixes this threat
these modules arent in the image and also wouldnt be used for sound & network, because other modules are doing this work.
This - now deleted - module-line does generate a error-message in the onscreen-boot-log (not in dmesg) and can be read via :
systemctl status systemd-modules-load.service
result of this command:
Jun 04 13:07:49 npi-a64 systemd-modules-load[531]: Failed to find module 'sunxi_codec'
Jun 04 13:07:49 npi-a64 systemd-modules-load[531]: Failed to find module 'sunxi_i2s'
Jun 04 13:07:49 npi-a64 systemd-modules-load[531]: Failed to find module 'sunxi_sndcodec'
Jun 04 13:07:49 npi-a64 systemd-modules-load[531]: Failed to find module '8723bs'
without this module-line /etc/modules should be empty and the error-message is gone away
the 8723bs seems to be a artifact of teh former PineA64 image where the NanoPi A64 was forrmerly build of.
Maybe also the other 3 modules.
We don't need to enable UARTS and OTG by default on all Nanopi boards. This seems to cause instability on M1
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* fix permisson denied error happening in line 79
`mktemp` creates files with `-rw-------` (on Ubuntu bionic at least), which causes `line 79` to throw a permission denied error if the file isn't world readable.
* fixes umount error caused by single quotes
* force metadata duplication for btrfs root
Without this change metadata duplication is automatically turned off for `mkfs.btrfs` when the **build system** has a SSD drive.
However, since Armbian image is most likely flashed to a SD card afterwards, the drive type of the build host system should not be the deciding factor.
Metadata duplication is a good idea (better reliability) to have on a SD card.
From `man mkfs.btrfs`:
```
-m|--metadata <profile>
Specify the profile for the metadata block groups. Valid values are raid0, raid1, raid5, raid6, raid10, single or dup, (case does not matter).
A single device filesystem will default to DUP, unless a SSD is detected. Then it will default to single.
```
* armbian-resize-filesystem fails on first run due to missing fdisk
The `fdisk` package is missing in the `minimal` image, in bullseye at leat. Maybe other, future minimal images as well.
This will cause the `armbian-resize-filesystem` script to fail on first boot, which contains several
`fdisk` references. This could be fixed in the `bullseye` specific section, but since fdisk is so
essential for Armbian, it's probably best to list it in the general, mandatory packages to make sure it's available in every image in any case.
* fix for https://github.com/armbian/build/issues/1584
Since Debian buster the final `update-initramfs` call must be made
on the finished image where the final root device is mounted, else
`cryptsetup-initramfs` hooks fail to detect the root device.
* Merge remote-tracking branch 'upstream/master'
* make sure cryptsetup-initramfs is installed in any case if CRYPTROOT_SSH_UNLOCK is configured
Before Debian **bullseye**, `cryptsetup-initramfs` was a hard dependency of the `cryptsetup` package. Not anymore.
Therefore we need to install `cryptsetup-initramfs` explicitly, else CRYPTROOT_SSH_UNLOCK won't work.
NanoPi R2S has the same issue as ROC-RK3328-CC.
With working GPIO, during init the GPIO state s reset.
This causes the sdmmc regulator to shut down, preventing detection.
Removing and replacing the card will allow it to be detected, but that should not be necessary.
Fix this by setting the regulator on at boot.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
Link: 75aa567803
Signed-off-by: Jayantajit Gogoi <jayanta.gogoi525@gmail.com>
* patch: kernel: rockchip-dev: Handle more resolutions with HDMI (β)
The added patch add more PLL configurations, in order to satisfy
more HDMI frequencies requirements.
This should allow users to benefit from more resolutions.
However, this is fairly untested. I only tested it on my 1080p
screen and, yeah, it works but so does the kernel without this
patch.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* patch: kernel: rockchip-dev: Handle more resolutions with HDMI (β)
Now with proper patches names.
Anyway :
The added patch add more PLL configurations, in order to satisfy
more HDMI frequencies requirements.
This should allow users to benefit from more resolutions.
However, this is fairly untested. I only tested it on my 1080p
screen and, yeah, it works but it also does without this
patch.
So could anyone test this with the following configurations ?
* [ ] A HDMI 4K screen
* [ ] A HDMI 1366x768 screen resolution
* [ ] A VGA screen with a VGA to HDMI adapter
* [ ] A DVI screen with a DVI to HDMI adapter
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* Using the patches provided by @Kwiboo for HDMI
This provides me way more resolutions, including interlaced modes.
I don't see 4K modes, though the screen attached can't do it,
so I still don't know if that can help provided 4K modes on mainline
kernels.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* Support for 4K screens
Using fixes provided by @czak
Tested and approved by @czak too !
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
There have been intermittent issues with SPDIF output on H3 & H2+ devices.
Digging into the H2+ & H3 datasheets I encountered an important clue on
table 8.7.2.2: s_clk needs to be 4x24.576 MHz or 4x22.5782 Mhz.
Probably due to how SPDIF is a huge oversample of the audio frequency.
Co-authored-by: George Lander <lander@jagmn.com>
* Attach Meson64 CURRENT to 5.6.y and make DEV = CURRENT at this point.
There is a lot of changes to 5.7.y and can be done after release or by someone that feels a need for this right now.
* Delete meson64_fclk_div3.patch
this fix has been upstream for some time, I had issues with it on 5.4, which is why it had been removed there.
* [ meson64 current ] kconfig tweak
disable Rockchip SoC drivers
* [ meson64 current ] remove rockchip patches
* [ meson64 current ] disable CMA patch GX
* [ meson64 current] add libretech cc audio patch
This brings the dts even with the khilman 5.8/integ branch which includes all of the audio changes. The kernel is registering audio devices, however nothing comes out. committed in case someone wants to spend time debugging/testing theories.
* fix permissions
was editing from another machine, accidental change of permissions in the patch
* Set default mixer settings
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* [ meson64 current ] GXL audio commit
This moves to the mainline patches and covers le potato and la frite. Adjusted asound config to handle a commonized sound card name.
* [ meson64 current ] add gxbb audio WIP
Playback is too fast, a clock setting is off somewhere.
* Update kernel configs
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Co-authored-by: Tony <tonymckahan@gmail.com>
