Create the image. Boot the image. Enable SSH, and /flash will exist (it won't be writeable unlesss you remount as read-write). Or create the image and connect to any OS and the files are in the boot partttion where you can edit them. I'm not sure what you did, but it sounds like over-thinking things.
Posts by chewitt
-
-
See if rebooting the router works?
-
I don't have a "solution" .. but here's some thoughts that might be useful:
GTX260 does not have any on-board audio capabilities; it is normally a DVI output only card and DVI does not carry audio. As this is the era before nVidia figured out how to do HDMI properly the card shipped with a cable that connects the motherboard soundcard digital output (S/PDIF) to unused pins in the DVI connector which a custom nVidia DVI to HDMI adaptor uses to present "HDMI" audio to a TV or AVR. HDMI and S/PDIF send the same signal, so this allows the card to send full 8-channel audio via HDMI (over S/PDIF the bandwidth is reduced and the receiver will not support more than 6-channel, i.e. 5.1 audio). For this to work in Windows an nVidia audio driver must be used .. so likely there is something similar under linux. If you are using DVI not HDMI i'm wondering what might happen if this cable is disconnected and/or any nvidia audio modules are blacklisted to prevent them from being used.
The kodi.log only shows "nVidia" audio devices being presented by ALSA, yet some fiddling with pulse (which reads hardware capabilities from the kernel in addition to being aware of ALSA devices) managed to get some audio out. I suspect via you've managed to route audio to the internal card; either by ignoring the nVidia devices or via snoop/dmix sending data to all devices. When fiddling with the config in alsamixer did you save/store the active configuration? .. this is not automatic.
In the past (when we supported mk1 AppleTV devices which I maintained) the PCM output volume needed to be 100% before S/PDIF output worked; any less and the signal strength wasn't enough to be correctly carried (S/PDIF is digital but the signal still needs to be clean/strong enough for comms to work). The description of audio needing to be zero is the exact opposite, but makes me wonder if anything above zero results in additional audio data being mixed into the audio output and disrupting the digital signal.
-
Currently no 4K and no HDR, the focus is on getting 1080p decoding and seeking working reliably. Both will be added later (no ETA on when, there are a lot of depdencies).
-
-
DDuck007 LibreELEC-Generic.x86_64-9.80.8.img.gz <= see if this image works, it's current LE master with mesa bumped to v20.3.1 which includes the fix that I flagged earlier.
-
It can probably be done, but there's no official interest in doing it as Intel Gen10 GPUs will be supported in LE10 and you can use a nightly image from Index of / to run Kodi (Generic is quite stable).
-
To herd the conversation in a more useful direction, this smells like the same problem Black Screen after Updating - LightDM/Xorg dosnt start / Pacman & Package Upgrade Issues / Arch Linux Forums and this patch may be the fix upgpkg: mesa 20.3.0-3: radeonsi: fix regression on gpus using the rad… · archlinux/svntogit-packages@2a3a08a · GitHub
-
This is perhaps worth a read: Infra-Red Remotes - LibreELEC.wiki - the initial section(s) of the page have a good description of how LE handles input devices and interaction with Kodi. It might give hints on which layer you want to inject events to.
-
Random guess. Have you enabled "wait for network" in Network settings? .. LE boots fast so Kodi will often start before the network stack is up, which means the SQL DB is not accessible when Kodi attempts to connect with it. No DB = "all my movies are gone" reports from users.
-
Win10 wants to use authenticated accesss to SMB shares, so enable SMB authentication in LE settings. Working?
-
No sound from either port, or no sound from both ports at the same time?
-
What am I missing?
It looks like you are missing a legal source of media. No further support.
-
You have banned add-ons installed. No further support will be provided unless you come back with a clean system.
see: Official:Forum rules/Banned add-ons - Official Kodi Wiki
-
Index of / <= search for RPi4
-
I recently dug out the unfinished HEVC work that Maxime Jourdan started in 2019 and managed to tweak a few bits to get it to compile, and 8-bit media playback works quite well, although the decoder predates lots of the compliance work on stateful APIs so probably needs changes before things like seeking will work properly. However 10-bit media deadlocks the box immediately so there is something fundementally broken there and since the 8-bit and 10-bit code paths are firmly entangled I've had to revert the changes to have a usable image. In current state 1080p HEVC works fine on G12A and newer boxes that have the CPU grunt to software decode it, but older GXBB, GXL and GXM devices are too weak. I'm not aware of anyone working on HEVC support so I'm not expecting HEVC to improve anytime soon.
I've never seen eMMC corruption issues so cannot comment on that.
-
AFAIK these are not supported. They are not impossible to support, but we have a long-running policy of ignoring requests to add support for more Realtek devices that need out-of-tree vendor drivers that are poorly written, poorly maintained, and usually break with each new kernel release (the novelty of hunting down patches wears off over time). That's probably not the answer you're loking for, but that's the situation.
-
Create a playlist, use autostart.py (Google it with Kodi wiki) to start the playlist on Kodi start. I'm not sure if the OSD is a function of the Skin or core Kodi code, but experiment with skins; something like AEON might allow this to be disabled, or you can modify a skin to hide this function.
