This issue has been resolved in Recalbox v7

Many people are using a NAS nowadays. Probably the most commonly used protocol is Server Message Block (SMB). This could be utilized since the XBox Media Center days. SMB is still available when adding a new source, but it is not working in Recalbox v7.0. It had been working in v6.1.1 just fine.

details:
When creating a new source, I choose SMB, but none of the sources on the network show. There are usually at least two: my NAS and my router.
When I create the source manually, I enter all details and when finished, Kodi instantly reports "software caused connection abort", therefore it seems that it is not even trying to connect. On the other hand, when my NAS is off, the error message reads something like "no route to server".

side note:
EmulationStation states in network settings that it is "not connected", even though wifi is connected and a LAN cable is plugged in. Yet Kodi tells that it is connected properly (in its network settings).
Another hint in this direction: when I manually create an SMB share, Kodi states "the connection to the network location couldn't be established. This could be due to the network not being connected. Would you like to add it anyway?"

The raspi is obviously connected to the network since it received its static DHCP IP address from the router and can play youtube videos. I can ping the raspi from my PC.

Hardware: Raspi 3b+

@drpoucevert said in SMB not working in Recalbox v7.0:

i think the problem comes from our smb protocol on our nas
mine has a smb1 and i think kodi leia has gone to smb2/3

This was a very good finding. The SMB version of the NAS was actually the culprit.
I had already set Kodi to not care about the minimum SMB version (nor the maximum SMB version), but it still did not work with my NAS, which turned out to run SMBv1. I wonder why the SMB version setting in Kodi does not work as I expected.
Maybe it would work if Kodi were set to "minimum version = 1". The setting can be found here:
Settings -> Services -> SMB Client

I solved the issue by changing the max SMB version in my NAS. Since it was running Samba 3.6.6, I needed to edit this file:
/etc/samba/smb.conf
I added this line to the global section:
max protocol = SMB2
Don't forget to restart after applying this change.

Source: https://wiki.samba.org/index.php/Samba_3.6_Features_added/changed#SMB2_support

Hi.
I have a Raspberry Pi 3 model B and the official Raspi 3 power brick straight from PiHut (5.1V 2.5A). Everything worked fine with Recalbox 7.x until Kodi suddenly vanished from the menus. I guess part of my file system was corrupted due to ungraceful shutdown. Anyway, I took this as a queue to finally update Recalbox and flashed the latest version on my SD card using the Raspi Imager program (Windows 11).
Unfortunately, the system is running very unstable now with the latest Recalbox version. About every 2nd boot the system crashes with an "undervoltage alert", during the boot screen.
I also tried another power brick with 3A 5V (noname). With that one the system did nothing at all.
Is anyone else experiencing this issue?

I flashed the current LibreElec onto my SD card. It never shows an undervoltage alert when I use the original power brick.

It seems that I cannot edit my previous post, so I create new posts for my updates and additional findings:

I played around a bit and found out that the issue seems to be related to large pictures, maybe in the area of 3000x2500 px, with some being around 2500x3500 px.
On the other hand, resized to 200px height, these pictures did not crash the current version's Kodi, even when using progressive. Baseline did not crash Kodi, either.

As now, I would recommend to resize pictures to a max of 4 megapixels.

Discourse:
This reminds me of back in the day, using XBMC on the original XBox, which also had issues with pictures > 6 megapixels. But it did not crash and instead simply not render the pictures at all.

Hi ho.

I have quite a big issue when Kodi needs to generate thumbnails. With the current version (Recalbox 9.1), Kodi almost consistently crashes while it is generating thumbnails for the "big thumbnails" view (5 or 6 pictures per row).

My system setup:
Hardware: Raspi 3B+ with legit 32GB class10 microSD card by SanDisk
As per my setting, Kodi launches on boot. I set the thumbnail size to "200" manually. I tried both 1400 MHz and 1450 MHz overclocking.
It does not matter if my pictures are on the SD card or USB thumbdrive. USB is set as system location ATM.
I never get the "low power" warning.

How to crash:
I have folders with around 200 pictures each. Most of them are around 1920x1080 px in size. I usually enter the current folder and wait for all the thumbnails to generate. But with the current version, it does not generate all thumbnails on its own, therefore I scroll down further manually. That is usually when it crashes.

The crash looks something like this:
black screen, Recalbox splash screen (with the Pac-Man ghosts), Kodi splash scren, Kodi.
Sometimes after crashing it does not restart Kodi, but drops me into Emulation Station.

Past observations:
There had been the very same issue with v6 Dragonblaze, but only if the pictures were saved "progressive" (as opposed to "baseline"). Therefore, I saved/converted all my pictures to baseline, also for the current setup.
I was unable to find any clue what makes Kodi crash.

@alvin said in Recalbox v8.0.2 on Raspi 3 B -> Undervoltage Alert:

@tosnic
Maybe the SD-Card itself is damaged.
Did you try another one ?

The SD card seems to work fine. I am currently running LibreElec on that Raspi with that SD card with no issues.

Regarding 3A recommendation for the power supply:
It indeed seems that my power supply is a bit weak (can they weaken over time?). Even LibreElec (Kodi Leia) now regularly shows the undervoltage warning symbol (flash), but it did not crash yet.
On the other hand, I tried the latest LibreElec Kodi Matrix) and it crashed regularly, but without a message. I did not check the logs, though. I assume that the latest software demands 3A power supplies

BTW: I did not overclock my Raspi in either configuration.

Hi.
I have a Raspberry Pi 3 model B and the official Raspi 3 power brick straight from PiHut (5.1V 2.5A). Everything worked fine with Recalbox 7.x until Kodi suddenly vanished from the menus. I guess part of my file system was corrupted due to ungraceful shutdown. Anyway, I took this as a queue to finally update Recalbox and flashed the latest version on my SD card using the Raspi Imager program (Windows 11).
Unfortunately, the system is running very unstable now with the latest Recalbox version. About every 2nd boot the system crashes with an "undervoltage alert", during the boot screen.
I also tried another power brick with 3A 5V (noname). With that one the system did nothing at all.
Is anyone else experiencing this issue?

I flashed the current LibreElec onto my SD card. It never shows an undervoltage alert when I use the original power brick.

@zing Thanks. Resetting Realbox fixed the issue.

I would expect there to be a way to reset the controls on a per game basis. But the one I found in the ES ingame options rendered the gamepad completely useless for that "game session".
Also, I wished that "resetting Recalbox" in the Emulation Station Menu mentioned that it also resets Kodi in the process

This topic seems to address exactly the problem I am experiencing, too. But I am wondering why this took so long to surface, considering the latest version has been released for 2 months now.

Anyway, this is my setup:
Recalbox 7.2.2 reloaded
Raspi 3 B+
64 GB SD card by SanDisk (class 10, rated for 80 MB/s read speed)
Original Power Supply (according to the PiHut) with 2.5 Amps
Genuine Sony Dualshock3 Controllers (2 of them acting the same) via Bluetooth

Games tried:
PSX:
Alien Resurrection (E)
Medal of Honor Underground (G)

SNES:
ALTTP Randomizer

The issue:
the controllers are not responing at all after a game is launched. Neither the ingame inputs worked, nor the hotkey commands (e.g., enter menu or exit game). Strangely enough, the controllers somehow worked at a time, but only some commands, which were all over the place (e.g., up = left). After properly configuring the controller in EmulationStation it ceased working ingame completely as described above.

Probably the solution:
This issue remained until I actually re-plugged my controllers and entered a game in that state. Now they work fine even wirelessly.

Another issue:
But in a few PSX-games I had previously configured for analog input (which Recalbox never saved) the controller is not detected by the game. Therefore, the games moan about the gamepad being unplugged. No setting I tried worked. But at least the EmulationStation inputs (Hotkey commands) still work.

@drpoucevert said in SMB not working in Recalbox v7.0:

@Tosnic thanks for that ,

i found a soureceforge page for the DNS 320 that shows how to force smb2 and 3 but it will screw up my backup so there is no way i'm going through the whole process of shifting my backup to have a proper working smb

is there any way i can access my samba settings in ms DNS320?

thank you

I am not sure if I understood you correctly, so I took the liberty of changing your post how I understood it (above).

But I still do not understand how changing your NAS to SMBv2 or v3 impacts your backup. It seems like you should expand your research to a place dedicated to your NAS (or its OS).

BTW: In case anyone is wondering about my instructions from the previous post: I am running a Linux NAS (Open Media Vault).

@drpoucevert said in SMB not working in Recalbox v7.0:

i think the problem comes from our smb protocol on our nas
mine has a smb1 and i think kodi leia has gone to smb2/3

This was a very good finding. The SMB version of the NAS was actually the culprit.
I had already set Kodi to not care about the minimum SMB version (nor the maximum SMB version), but it still did not work with my NAS, which turned out to run SMBv1. I wonder why the SMB version setting in Kodi does not work as I expected.
Maybe it would work if Kodi were set to "minimum version = 1". The setting can be found here:
Settings -> Services -> SMB Client

I solved the issue by changing the max SMB version in my NAS. Since it was running Samba 3.6.6, I needed to edit this file:
/etc/samba/smb.conf
I added this line to the global section:
max protocol = SMB2
Don't forget to restart after applying this change.

Source: https://wiki.samba.org/index.php/Samba_3.6_Features_added/changed#SMB2_support

@drpoucevert nope
do you have the same issue?

@dstroy It seems that way. In Kodi Krypton I could not find the option to toggle UPnP. In Kodi Leia the option is disabled by default.
But changing to DLNA would simply circumvent the issue, not solve it.