Thx. There are a couple of cache settings for network access. I think it's worth to play with them (see post #8).
Yes those are for playback I have zero issues with it if I add it as source.
The issue is kodi wont let you browse NFS shares. It does not even list shares on my local network in browser.
NFS library must be broken in RPi as it worked in NUC.
Can you try the default skin? Maybe you'll see NFS entries afterwards.
nope default shows same behaviour
only way to browse is to add to mediasources.xml
Maybe the output is just invisible, because you don't use the default skin.
Code2024-01-31 17:55:48.834 T:1028 debug <general>: CSkinSettings: no <skinsettings> tag found
Yes I dont use default skin 
OK, if power-on by IR works for you on RPi5, post that solution.
Yes if I buy the rpi5 case then will post if it works
Nekromantik If you want to give something back to the forum, post that solution on Showcase section.
It was not something I came up with. It was posted on the Argon40 forums.
It was 3 years ago so not remember exactly what it was and no longer have the case or Rpi 4b.
I had the Argon One for Rpi4b and it worked well for power on but it did require a lot of fiddling about with script to make it work
was not out of the box working
The logs show content being opened/read from an NFS share so basic access and reading works. I have no other insight to offer as I don't use NFS myself and have nothing setup to test with (and not looking to change that).
NB: The chunksize messages are harmless. Ignore.
ok
nope
you need a HAT or use Argon One case if you want to power on via IR Remote.
Wifi turning on is not possible nor is WOL.
my issue is different then
I turn on my TV which then turns on my AVR and then I have to manually turn on my Pi.
At which point it shows the boot screen and then before it goes into OS it then shows no signal from my tv until I switch AVR inputs. Only happens on boot or reboot.
Display MoreFollowing chewitt's advice, I configured my setup as follows - hopefully anyone with more experience can correct anything that is non-optimal.
System Settings:
Resolution: 1920x1080p
Refresh rate: 60hz
GUI Resolution Limit: 1080 (Comment: I still don't understand why this exists since the Resolution is already limiting the GUI while not limiting the video unless you want it *lower* than the Resolution but I still don't understand the use-case as you can just lower the Resolution)
Player Settings:
Adjust Display Refresh Rate: On Start/Stop (Comment: If you forget to set this, all of your content will be displayed at the resolution & refresh rate in the System Settings)Sync Playback to Display: OFF (Comment: Off is the default but I am calling it out since it will break audio passthrough and since this is largely a Denon thread, I imagine the vast majority of us want the Denon to process audio)
Lessons learned:
Adjust display refresh rate on Start means that once you stop the content, your GUI will stay in the same resolution as the content you last started which is undesirable if you play 24hz content, now the entire GUI stays at 24hz
Adjust display refresh rate on Always means that if you go into the Kodi GUI (not the OSD but things like your Movies menu) you will get hit with a resolution / refresh rate change back to your System Settings. It is not recommended by Kodi and it is definitely jarring so I don't recommend either.
Adjust display refresh rate on Start/Stop is really best of all worlds IMHO. Your display will get synced to your content's resolution / refresh rate when you start the content. If you browse Kodi menus while your content is playing, it will stay at the same resolution / refresh rate which CAN appear a bit sluggish since you'll probably be around 24hz instead of 60hz but it leagues better than the harsh switch of resolution/refresh rate. Once you stop the content, you'll be back to your System Settings. **This setting could actually bite us Denon owners due to the original bug this thread is about - if you start 4k/60hz content, pause the content, then turn off the Denon, that experience should be effectively the same as having your system settings display and refresh at 4k/60hz since once you turn the Denon back on it will try to display 4k/60hz of the paused content.
You might need to do specific whitelisting depending on your content but I left this off and Kodi switches as needed. If I run into content that fails or behaves weird then I may have to revisit but until then I am leaving unconfigured.
Delay after Change of Refresh Rate: This is one that I am currently playing with to find optimal settings but since there is a delay when the resolution / refresh rate is changed such as when starting 4k/24hz content, this setting will delay the start of the media so it isn't "playing" in the background before your TV/Sound is able to play anything. The delay will be unique to all of our equipment stacks but it is probably something you'll want to play with to find your own best delay.
Yes this is optimal but dont you still have the issue with the AVR showing no display until you switch back and forth on the inputs?
On my Pi 5 and Denon AVR even on 1080p 60hz I get the issue.
The temporary workaround was switching refresh rate to 30hz.
No change for me RPI3+, still not working
rpi 5 still not working either
Can you remove / rename the .cache folder for another test?
nope no difference
if this is a Rpi 5 bug do I need to post it in kodi forum?
i just booted up NUC running LE12 nightlies and no issues browsing NFS
I'm not sure, NFS scan in the log is erratic to me. Just try, and go back to the original, if it doesn't work.
Another thing is this:
Code2024-01-31 17:55:50.418 T:1039 debug <general>: NFS: Connected to server 192.168.1.200 and export /mnt/user/Stuff 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS Server max read chunksize (1048576) is bigger than client setting - Using client value 131072 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS Server max write chunksize (1048576) is bigger than client setting - Using client value 131072 2024-01-31 17:55:50.418 T:1039 debug <general>: NFS: chunks: r/w 131072/131072So play with <chunksize> at advancedsettings.xml.
removing those did not help.
this is only happening on rpi5. on nuc its fine with all existing settings and set-up.
Remove this part from advancedsettings.xml, reboot, and try again:
Code<videolibrary> <importwatchedstate>true</importwatchedstate> <importresumepoint>true</importresumepoint> <recentlyaddeditems>50</recentlyaddeditems> </videolibrary>
those could impact the nfs browsing?
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
i created thread about NFS access issues on LE12 on RPi 5
Kodi can access files via sources.xml but cant browse it via Kodi
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
Ok will do
The NFS client defaults to NFSv4, is that going to work for your NFS server?
Yes my server uses NFS4 as NUC running LE also used v4 and worked fine.
So on RPi5 latest nightly I cant access NFS shares using browse in Kodi.
When I press on Network File System it does nothing and log states: GetDirectory - Error getting nfs://
Is this known issue? Same wired connection my NUC running nightly can access this fine.
