I have been sick since a week now, hence the delay in the response. Please accept my apologies for the same.
I have gone throught the code of getMyCollectionStats function in volumio and it seems it deals with the metadata of the songs. IIRC you had mentioned in the past that you had tried to set language as French. I wonder if your song filenames or metadata contains some French characters and the issue is due to some missing character set support.
Would it be possible for you to share some of your songs to help me try reproduce the issue on my side?
I tried to scan my music library in a different repertory where I copied my files in many batches. WhenI reached around 17000 files, then I got a first spontaneous reboot from the VIM3, but I could go back within Volumio. When I tried to copy more files, then I lost completely access to Volumio…
As you said a significant part of the files I copied and scanned contain French characters. I use the software SongKong to tag them.
May I remind you that using the PC version from Volumio, I did not face any issue when scanning my music library: this means to me that there is something specific with your version that leads to this phenomenon
Its based on upstream volumio code which uses older 4.9 kernel. Only change I have made is to update u-boot binaries to match that of fenix 1.5.2 release
I know that. The thing is every device platform in volumio is using a different kernel and its not clear whats the common base kernel config volumio needs. So that leaves me with only one choice which is to try toggling bunch of kernel configs and share the image and see if that solved your issue. If you can share some sample music files that can help replicate the issue on my side, then I can do this iteration a lot faster and only have to share the final working image with you.
I know you are getting frustated. But please also think from my perspective, I am trying to troubleshoot an issue that I cannot reproduce on my side.
Sorry for being a bit rude to you: I understand clearly that it is difficult to work out something that you cannot reproduce. As you said my library mixes files whose metada are if different languages. But what I do not understand is that my music library works quite well with moode or volumio but not with your porting to the khadas vim system: my raspberry has 2 gb of memory, so has the vim3 (maybe more). My feeling is that there is some overflow somewhere… (The scanning worked well until a certain amount of files and then the system seemed to loose it stability).
Thank you anyway for your support.
@philippe_kertesz Please do try the below image that I shared today. This is not based on my changes, Instead its based on the upstream volumio kernel that runs on their rivo and similar devices which uses VIM3L. So I am hoping you won’t face the issue on this one.
Boots fine for me. The zip file contains 2 files inside i.e. image file and its checksum. Make sure that you had extracted the zip file and selected image file for flashing.
Once I mistakenly gave the zip file to Raspberry pi imager and it dd-ed it as it is to the sdcard. Your booting issue kind of reminds me of the same.
I extracted the zip before flashing using the Raspberry Imager. Looking at the “title” of our exchanges I noticed that it is talking about VIM3L, but my VIM is a VIM3 one. Is this the problem ?
I eventually erased the VIM3 emmc flash and it booted ! But now, I am unable to mount my network library: volumio says that it cannot detect my drives…
Does it still not able to detect your NAS if you manually specify its URI? As I understand the volumio has two mode for detecting NAS. In auto mode you wont have to give any details. But in manual mode you give the uri some thing like whats shown here - How to add music from a shared folder on a Synology NAS?
As I put a fan on the VIM3 board, it is a bit difficult to read: I used OOWOW to display the Hardware revision. It is V12 (I hope that this info will be useful to you)
Interesting…Its same software that they ship on their rivo, integro and primo device only without myvolumio support. Only thing I did was to update u-boot assuming older one will have boot issues on newer revisions as mentioned in the first post of the thread. The bootloader that was in there was having creation date of 2020.
Maybe we can try this.
Open volumio.local in a browser and go to the NAS settings page.
Open another tab and go to volumio.local/dev in a browser and start livelog.
Now switch back to first tab and try to enter your NAS details again and see if it detects.
If it doesn’t, then we should have some kind of log in the text area near the livelog button. You can share that with me and I can try to look if there was some error.
For NFS, it says access denied by server. My guess is may be there were issues with credentials or something else. Not sure. Probably you can get more information in logs of your NAS