Posts by Can'tThinkOfOne

Have I used my quota of questions up?

I tried to run PASTEKODI again following some stuttering last night but it says FILE ALREADY EXISTS. I assume this is the previous one I sent so what do I need to do?

These changes have not made any difference so next time I power it on, I'll get a log sorted.

OK thanks. I've made a couple of adjustments as described although I wasn't totally clear on the Whitelist part, which wasn't activated. I've turned on the 3:2 part to see what happens. The Refresh part is now on Start/Stop as stated. I'll run a film later and see if there are any differences.

I'm running the RPi into a 1080 TV which I only use as a monitor via HDMI which I think runs at 60fps so 4K/HDR doesn't come into it. I'm pretty certain it's not a network issue as it is fast. There would be no other traffic on the network when the RPi is in action. Incidentally I can view films directly on my TV/monitor as it is also connected over Ethernet, thus bypassing the RPi. The computing power in my TV/Monitor is nowhere near the RPi and it never stutters so my feeling is it is a setting somewhere that needs adjusting. My entire house was wired late last year with CAT6E cable throughout so there shouldn't be any problems there.

I have a 4GB Raspberry Pi 4B connecting to my LAN over 1GB. My network is all 2.5GBE capable except for the RPi. I connect to my Windows media file storage computers no problem but I have an issue whereby after watching a film for, say, half an hour, it starts stuttering. The video starts to jerk and the audio with it. It looks like it is skipping frames and then catching up. It eventually gets to the point where it doesn't catch up. My temporary fix is to stop the film and restart where it left off whereby it usually gets to the end without further issue.

OK, the RPi 4 is now plugged into cable in its new home so no more wireless issues and it is working much better. I do now have a couple of usage issues but I will start a new thread for these. Thanks again.

Thanks again. I'm not sure why the log should show Kodi starts before the network is up as I have it set to wait, maximum time to wait 10 seconds. As I mentioned my incorrect setting for wireless, just to reiterate, It was actually only functioning on wireless as wired was turned off. Given that I kept getting Invalid Password I'm not sure why it is working at all as I at no point was able to put my password in successfully. This likely also explained the slow access. It is today functioning correctly with an IP address over DHCP and signal strength is at 74%. The wireless problem will soon be no more soon as I am moving the RPi4 to a different location where currently there is no Ethernet. I am awaiting a powerline/homeplug system to arrive in which case I will use that with all the associated problems solved hopefully. I am currently only doing the initial setup while I am waiting. These issues are purely off the back of a fresh, clean install and they are problems I hadn't encountered before.

Sorry, things keep changing and I gave you some misinformation and this part is bizarre. I am not on wired as I thought as I had switched it off so it was working on wireless. Yesterday I had No Route To Host, today it works. I have several computers functioning on my LAN and they all work all the time. There is no logic to this because last attempt failed with Incorrect Password so I hadn't got past that stage; it just decided to accept my last attempt belatedly. Even though accessing the servers is very slow, once I select, for example, a film, it is so far playing flawlessly.

OK, is this what you need:

https:/paste.libreelec.tv/star-primate.log

Note that I am not having the No Route To Host issue today but access to the shares is painfully slow and I'm still wired. Also, my little mini wireless keyboard/mouse combo has stopped connecting/working in case there is anything in the log.

OK. Thanks for your reply. I have seen other reports of the Invalid Password from other users but no solution. The passphrase is not wrong or illegal as it works on my RPi5. A bit of research tells me that the internal wireless in these devices is a little on the weak side, as you state, so Invalid Password may not be the problem, just mis-reported. I can try moving it closer to my main wireless source but my home is MESHed and signals are decent so may not help. I should point out that I have activated DLNA and can set my shares up with that and they work, at least as of yesterday. I'll turn it on today and try and get more info.

I understand what No Route To Host means in technical terms but not the way this is happening. Not being hugely technical, bear with me while I work out how to do what you are asking.

I meant to point out that these problems occurred over wired connection, as of course I had no wireless function. I've never used SSH but I do have Putty installed and just need to figure out how it all works.

Thanks again. I'll get back....

I have 2 Raspberry Pis, a 4B and a 5. The RPi 5 is set up to access Windows 10 network shares, works on wireless and all is well. The 4B is a different ballgame. I have just downloaded and installed 12.02 to a USB flash drive, the SD card no longer working, and it all installed no problem. I then install the AMBER skin as it has better functionality for me. First problem is I get INVALID PASSWORD when setting up wireless so I can't do it. There is nothing wrong with my password. Secondly, I cannot access Windows shares until WS-Discovery is active. Unfortunately this is buried away under the basic settings and off by default. Having turned it on, SMB begins to function and I can see my network. I set up all the shared folders I need and check they all work normally and all is good. However, following a restart, there is no access to any shares - NO ROUTE TO HOST error. Well there was a route to host when I set it up and the screen that comes up in place showing various shares allows me to access the shares, suggesting there is a route to host. I then deleted everything and set it all up again using IP addresses and that all went to plan. 20 minutes later and without a restart I get the same error - NO ROUTE TO HOST.

There is clearly a route to host as I can access it in other ways, just not via the dashboard. My RPi 5 is rock solid stable with the same settings.

I know how to use Kodi but am not a technical person so please, nothing complicated. I checked 20 pages of threads without success before submitting this.