ordovice/batocera-switch

SMB Broken after Switch install on batcoera v38

Closed this issue · 15 comments

After installing switch via the "easy method", SMB mount via \ on a windows host no longer works. If I manually re-run batocera-upgrade after installing switch whatever the installer broke with SMB is fixed and switch roms still launch and seem to be playable.

uureel commented

not sure what you mean by "SMB mount vi \ on a windows host no longer works", can you explain and provide steps to reproduce?

If I attempt to mount batocera smb share...ie "net use d: \\ battocera ip address" it fails to mount the share (how I typically transfer content from my pc to my machine running batocera). I did confirm if after installing switch emulation, I re-run the batocera v38 install from command line ie batocera-upgrade https://batocera.org/upgrades/x86_64/stable/last that the batocera smb service works again. This is only a problem with v38 and Ive only tested this with x86_64

uureel commented

i see, thx; can't reproduce it on any box, works fine, samba has worked fine with the addon since i first stumbled on bato @ v35
image
... and works fine, same as accessing via \\batocera

further, if you reflash/upgrade/downgrade batocera, the addon stuff is still being launched via custom.sh on each boot (doing pretty much the same thing running the installer does); that's why you're experiencing 'switch roms still launch and seem to be playable', so in other words your samba issue doesn't seem nor seems to be able to seem, to be related to the addon;
i'll keep this issue open if you can pinpoint something i can reproduce

@paronowitz What is the error you get? I'm unable to reproduce either. Have you tried adding /user:root linux to your command?

Heres an example... I can ftp to the batocera instance but I cannot access the smb share from my windows host after installing switch emulation. If I manually reapply v38, I can once again access the smb share.

error
ftpsuccess

Interesting. Can you expand see details next? I've seen issues with credentials causing issues.

This actually seems to indicate an issue with Batocera loading your network and not the switch add-on.

Any idea why that would only happen after installing switch emulation? Ive tested this on a completely new batocera instance with no roms or config changes.... Image an nvme drive with batcera v38 setup ip etc... everything is accessible as you would expect. Run the switch install script and smb is no longer accessible. Re-run batocera-upgrade https://mirrors.o2switch.fr/batocera/x86_64/stable/last/ and it is accessible again. Its worth noting I did not have the same experience on v37

still can't replicate, tested with v39 now too and still no issues samba related

again, from the perspective of the addon it doesn't matter if you run or re-run batocera-upgrade https://mirrors.o2switch.fr/batocera/x86_64/stable/last/, or otherwise upgrade or downgrade bato to whichever version whichever way, since the addon is being started via custom.sh and remains all the same active after reboot -- so in other words if that's what fixes the issue for you, then it actually doesn't seem to be addon related and more so looks like some weird bato issue

there's also been no changes in the addon from v37 to v38 that could effect anything samba (and i don't think there's ever been anything that could effect samba there), thus, this too might further indicate you're actually in some v38/linux, twilight zone

also noticed you're using overlay (which the addon doesn't use), and one thing running batocera-upgrade https://mirrors.o2switch.fr/batocera/x86_64/stable/last/ actually does is it removes the overlay, so, maybe that's worth checking out

Strange... The only other thing I notices after running the switch install was the OS changed from 38 to 38oc, I just assumed there was some kernel patch involved
image

nope overlay is not used by the installer/updater

The only changes I made from that perspective is swapping out the boot up images/videos but again I tried the same thing using a stock unmodified x86_64 and was able to replicate the issue. I havent tried v39 yet. Im fairly happy with the system config at this point so I dont really need this working (as well as I can use ftp if I really need to transfer any new material). I may try a few other scenarious with a base image just to satisfy my curiosity.

closing as 38 became ood