Posts by WarpLover

    I am having a strange new issue. I'll cut to the chase. Because of the issue, I used Remove From Library. And now I cannot get that TV show to ever show up in the library after that, even after an new SD card with a new LE install in it. Where in Kodi do you reverse the "Remove From Library" status? That's just one problem.

    My library is on a samba share on a NAS.

    The second issue: some TV show's labeling is totally screwed up when you find them. Sometimes the season or episode is wrong, sometimes the title of the episode is wrong, or any combination of those. After straitening several existing shows out, and adding missing episodes, the newest episodes sometimes refuse to show up in the library. I can see them in the FILES area but not in the library. The content of the TV Show is set to TV Show/Local (should not be using an external database). While trying to solve this issue I ran into the OP issue.

    I feel so ignorant.

    I used putty. I made my way to the log file. I looked at it briefly with nano, but my skills end there. How do I copy the file to somewhere on the RP64 where it can be seen from windows, or how do I copy it directly to windows, so I can work with it from there? Can it be zipped and pasted from where it resides?

    I saw the segmentation error first thing in the file.

    I'm still trying to get it to paste from LE this morning.

    hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too :)

    I am curious. Did you get Argon's remote control? If so, have you tried the on/off function with your new Pi5?


    hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too :)

    Does this case have any LEDs that you find annoying?

    The problem has been found.

    I removed the pcie cable and did a fresh reinstall of LE wo/addons. It played 7 movies back to back overnight. I'd say that is stable.

    As you might have already guessed the user was the issue, but I need to put some of the blame on the Raspberry Pi Foundation.

    After ONE insertion of the PCIE cable, the connector on the Pi side is damaged. The moving lock down piece now comes completely out of the connector. And that connector does not look easily replaceable. The cable was obviously working and you could see the marks where the connectors made contact on the ribbon cable to each trace and on each end.

    I think about all the other connectors chosen for the PI and realize most of them are quality and will provide for hundreds of insertions, but not this jank-a-fied pcie connector. The Pi is a hobbyist board made for building and rebuilding, except for that connector (space constraints, I know). The geekworm connector looks even jankier but lasted through the first insertion. An old windows meme came to mind 'plug and pray'. I'm not left with a feeling of quality.

    It feels a little dishonorable, but I am going to see if I can return this Pi. I don't feel 100% at fault.

    Thanks for all of you who spoke up and helped. I hope this record helps someone in the future.

    I've learned a little about the logging system and that is certainly a plus. Man hugs ensue. $$$ Donation has been given.

    Now to look at the RockPro64.

    PS no use trying the other ribbon cable now.

    I shut down the pi so I can take the m.2 board out. In the mean time I hooked the RockPro64 up and it is scanning in the changes in the library. Been moving a lot of stuff. When that is done, I will play tv episodes until the RockPro64 shows it's problem, and post that log.

    By then the RPi5 will be ready to fire up and we'll see if the problem persists without a m.2 HAT. If it does, we'll post that log. If it no longer shows the problem, then I'll add the "new" pcie cable and HAT, and perhaps try your command, although I am not sure where cmdline.txt exists.


    Code
    May 31 11:08:04.570436 RPi5a kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
    May 31 11:08:04.570750 RPi5a kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
    May 31 11:08:04.570864 RPi5a kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
    May 31 11:08:04.657093 RPi5a kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
    May 31 11:08:04.657277 RPi5a kernel: nvme nvme0: Shutdown timeout set to 8 seconds
    May 31 11:08:04.660439 RPi5a kernel: nvme nvme0: 4/0/0 default/read/poll queues
    May 31 11:08:04.670425 RPi5a kernel: nvme nvme0: Ignoring bogus Namespace Identifiers

    The dates in the log indicate it has had that error since Feb when it was new.

    I removed the pcie cable from the RPi5. M.2 is now neutered. It waits for the RockPro64 to fail, and then it's the Pi's turn.

    I had all the skins and a dozen addons installed including several weather addons. I wanted to see the if RPi5 could do the heavy lifting of some of the skins. The Pi did not disappoint, but some of the skins did. And I cannot find a way to make the unwanted skins go away using the GUI.

    When I rebuild the RPi5 with an SD card, there will be no addons. I will certainly report back after the first unexplained reboot with a log file.

    After we are done testing in that mode and it's time to go back to the M.2, I'll put the better pcie cable in then.

    I will certainly follow the instructions for the Argon box. I am giving it to someone who is less technical than I am. Being able to turn on and off with a remote control was a must to keep it simple. So I am going to pound on it with testing before I send it off to him.

    I ordered a quality flexible pcie cable - I think it's the one Jeff Geerling showed. I could try to replace the current cable. I already have that on hand. And then there is the "crappy" pcie connector on the Pi and on the X1003. I hate them. I really don't want to touch them much.

    I could eliminate the m.2 board and see what happens with just an SD card. The SD card experiment would eliminate all those pcie pieces from the picture. Those connectors could be a potential culprit.

    Would there be any value in replacing the Rpi5 with the RockPro64, turn on logging, and run it until it reboots? And would those results shed any light on what is going on with the Pi? (as a reminder, the rock sbc randomly reboots in the same way, which is why I bought the pi).

    You guys are a gold mine and we lowly users totally appreciate what you do for us!

    PS Speaking of Gremlins, isn't it always after midnight?

    That seems to be describing what happened at the end of a movie I watched. Played fine until the end, then the audio seemed to have trouble keeping up. It is a setting I recently turned on. Back to default now.

    But that is not when it crashed. It was during the next show, a TV show and it was playing fine when it rebooted.

    I searched the log for fail, volt, and under. There's no sign of a power issue using those keywords.

    I am about to build another RPi5 system for a gift once the parts arrive. It will be in a Argon ONE v3 nvme case. I sure hope that is not going to have gremlins.

    The NAS device supports multiple users and access rights, so create a "kodi" user with read-only access to media and then relax and watch movies. In the rather unlikely event someone compromises your home network and obtains the insecure password; they can steal copies of your movies, but cannot do more. If that risk bothers you, disable Samba and SSH services and the insecure password cannot be accessed.

    I will disable. As always, thanks.

    edit:

    I am a little slow I guess. I just realized there are two logins for the NAS, admin and user. I was conflating them in my mind. Please forgive.

    The original post concerned open text password in LE. Now we are moving into linux zealotry.

    Attack the OP and his HW, but ignore the open text password problem that is apparently there because it's convenient for those who install from the command-line.

    You aren't going to sway any windows users that way you argue. If fact, windows users know it's the guys who know linux who would be doing the attack. I have nothing against linux. I used to run ubuntu when they tried to force us into Win8. So I already know what it is like to try to replace everything with a linux equiv. I have one expensive OCR program which will not move to linux - some kind of licensing thing.

    enough

    good day