I did some tests and when I boot from sdcard, I have no problem mount the partitions from emmc.
Then most likely a needed kernel driver is bulld as module and not available at boot time.
I did some tests and when I boot from sdcard, I have no problem mount the partitions from emmc.
Then most likely a needed kernel driver is bulld as module and not available at boot time.
Linux 5.8.0-50-generic x86_64
Same kernel, same behavior (still assuming it is a kernel issue).
If you like to test different kernel versions there is a script to easily administarte mainline kernels: GitHub - pimlie/ubuntu-mainline-kernel.sh: Bash script for Ubuntu (and derivatives) to easily (un)install kernels from the Ubuntu Kernel PPA. Please read the Warnings section. In addition test if the grub boot menu can be activated by pressing ESC or holding the Shift key on your machine before installing any additional kernel.
Likely the Fire Sticks are not using nmblookup, but I do have no experience with kodi on android.
I will create a kodi PR the next few days to select the public IP address.
I don't see any work around because nmblookup is the first method tried by kodi.
To complete chewitt 's analysis for the driver build: you are using a DKMS Makefile not working in LE build system.
Use:
PKG_NAME="RTL8125B"
PKG_VERSION="cb398363f11d742d880b8bb80763d050f00e7e98"
PKG_SHA256="8f05052c59e69a8bf0ada420d25ef29f54a38d25e0fd841e9df9e61145a48f55"
PKG_LICENSE="GPL"
PKG_SITE="https://github.com/awesometic/realtek-r8125-dkms/"
PKG_URL="https://github.com/awesometic/realtek-r8125-dkms/archive/${PKG_VERSION}.tar.gz"
PKG_DEPENDS_TARGET="toolchain linux"
PKG_NEED_UNPACK="$LINUX_DEPENDS"
PKG_LONGDESC="Realtec RTL8125 driver for Linux"
PKG_IS_KERNEL_PKG="yes"
make_target() {
kernel_make V=1 \
-C $(kernel_path) \
M="$PKG_BUILD/src"
}
makeinstall_target() {
cd $PKG_BUILD
mkdir -p $INSTALL/$(get_full_module_dir)/$PKG_NAME
cp src/*.ko $INSTALL/$(get_full_module_dir)/$PKG_NAME
}
Display More
In case of the bug linked in post 2 (or any other kernel issue) use a kernel on the server that is not affected, i.e. an older one.
This will be fixed in LE with Intel Media Driver 2021Q1 Release - 21.1.3 by heitbaum · Pull Request #5287 · LibreELEC/LibreELEC.tv · GitHub
The crash is because of using CPU features in the initial test code of media-driver and/or gmmlib that are not available on older CPUs.
Do you mean it won't be fixed in an official build of Libreelec?
It will be fixed when it is fixed in the kernel. With seeing your ETA quote I would not hold breath.
I've just found a "community build" by "Sky42" version 10 generic. Do you think this will fix my WiFi problem?
Unlikely, unless there was motivation to include the external driver by owning such a realtek chip.
Likely the 5.8.0-50 kernel now include a backport of the failing patch. Yo can try to continue using 5.8.0-49 or 5.8.0-48 until the bug is fixed.
Sorry for the 8821 to 8822 fault.
Usually third party Realtek drivers can be included into a community build, but will not be added any more to official builds.
You can use the existing drivers as exsamples.
Using samba you likely did create some files/directories with capital letters. Do:
mkdir -p /storage/.config/firmware/rtw88
wget -P /storage/.config/firmware/rtw88 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtw88/rtw8822c_fw.bin
You may have to download rtw8822c_wow_fw.bin too.
On the bottom of Hauppauge WinTV-HVR-2200 - LinuxTVWiki is a note that the card is at least not working in some Supermicro boards.
First the card has to be listed in dmesg/journal log or via lspci before any driver can be used on it.
The easiest way to test this on different OS versions without touching your installation on HD is to create an install stick, boot it through the syslinux boot menu to the first installer screen, press Alt-F3 to get the debug console and type lspci. Candidates are 9.2.6, 9.95.1 and the latest nightly from Index of /
Which build host do you use?
There was a similar report: Raspberry Pi 4, Latest Master Build Failure for target:kodi
keka1234 It's a common mechanical issue that the card bracket is pulling out the PCI-E contacts. In worst case you have to bend the bracket to get reliable contact.