Posts made by jp123

It will work fine for hours, playing any game. Then, some time later if you try to play another game or the same game, it will display the start screen and then quit after several seconds, back to Emulation Station.

I have found that if it doesn't crash within the first five to ten seconds, it won't crash at all.

In the logs, I get the message "stack smashing detected" (below).

The two times that I have gotten it to "work" again were when I tried renaming one of the memory card files (not sure if that did anything), and when I tried enabling logging in the dolphin-emu, hoping to catch an error message, after which it started the game perfectly. Although, subsequent trials had the same issue of quitting after a few seconds (and with nothing meaningful in the logs). I don't think either of these actions actually had any direct effect, but I am wondering if the act of changing something about dolphin-emu had some indirect effect?

I will also note that doing the following

# export DISPLAY=:0.0
# XDG_CONFIG_HOME=/recalbox/share/system/configs XDG_DATA_HOME=/recalbox/share/saves /usr/bin/dolphin-emu-nogui -e "/recalbox/share/roms/gamecube/All Games/Super Smash Bros. Melee (Europe) (En,Fr,De,Es,It).iso"

seems to work consistently without issue.

I do get these following messages when I run the above (no-gui) command:

12:38:353 PowerPC/SignatureDB.cpp:124 E[HLE]: Wrong size! Found __DBExceptionDestination at 80336234 (size: 0000002c instead of 00000010)!
12:38:353 PowerPC/SignatureDB.cpp:124 E[HLE]: Wrong size! Found SystemCallVector at 8034810c (size: 00000084 instead of 00000020)!
12:38:354 PowerPC/SignatureDB.cpp:124 E[HLE]: Wrong size! Found OSSwitchFPUContext at 803459b8 (size: 000000cc instead of 00000084)!
12:38:354 PowerPC/SignatureDB.cpp:124 E[HLE]: Wrong size! Found OSLoadContext at 80345550 (size: 000000e0 instead of 000000d8)!
12:38:354 PowerPC/SignatureDB.cpp:124 E[HLE]: Wrong size! Found Reset at 80346ed4 (size: 000000b8 instead of 00000070)!

and:

12:39:727 BPStructs.cpp:684 W[Video]: Unknown BP opcode: address = 0x00000069 value = 0x0000049e
12:39:727 BPStructs.cpp:684 W[Video]: Unknown BP opcode: address = 0x00000046 value = 0x0000024c

but, I wonder if those are normal?

Finally, here are the contents of es_launch_stderr.log after GameCube crashes:

31:35:757 NANDContentLoader.cpp:208 W[DIO]: CreateFromDirectory: error opening /recalbox/share/saves/dolphin-emu/Wii/title/00000001/00000002/content/title.tmd
31:35:442 HW/WiimoteReal/WiimoteReal.cpp:657 N[Wiimote]: WiimoteReal::Initialize
31:35:442 HW/WiimoteReal/WiimoteReal.cpp:476 N[Wiimote]: Wiimote scanning has started.
31:35:446 ConfigManager.cpp:86 N[BOOT]: Saving settings to /recalbox/share/system/configs/dolphin-emu/Dolphin.ini
31:35:696 AlsaSoundStream.cpp:191 N[Audio]: ALSA gave us a 8192 sample "hardware" buffer with 32 periods. Will send 256 samples per fragments.

31:35:696 AlsaSoundStream.cpp:222 N[Audio]: ALSA successfully initialized.

31:35:696 Boot/Boot.cpp:248 N[BOOT]: Booting /recalbox/share/roms/gamecube/All Games/Super Smash Bros. Melee (Europe) (En,Fr,De,Es,It).iso
31:36:722 HLE/HLE_OS.cpp:47 N[OSREPORT]: 81200308->81300000| Apploader Initialized.  $Revision: 28 $.
31:36:722 HLE/HLE_OS.cpp:47 N[OSREPORT]: 81200324->81300000| This Apploader built Nov 30 2001 13:36:06
31:36:897 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: M
31:36:898 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: Dolphin OS $Revision: 49 $.M
31:36:898 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: Kernel built : Dec 17 2001 18:46:45M
31:36:899 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: Console Type : Development HW3M
31:36:899 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: Memory 24 MBM
31:36:899 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: Arena : 0x804dff60 - 0x817f66e0M
31:36:908 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: app booted from bootromM
31:40:425 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # ---------------------------------------------M
31:40:425 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: #    Super Smash Bros. MeleeM
31:40:425 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: #M
31:40:425 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # Distribution 2M
31:40:425 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # Language 2M
31:40:426 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # DbLevel 0M
31:40:426 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # Arena Size 19 MBM
31:40:426 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # ARAM Free Size 9 MBM
31:40:426 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # DATE Mar 13 2002  TIME 00:54:01M
31:40:427 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: # GC Calendar Year 2019 Month 1 Day 14M
31:40:427 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: #             Hour 18 Min 31 Sec 36 M
31:40:427 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: #M
31:40:427 HW/EXI_DeviceIPL.cpp:339 N[OSREPORT]: M
*** stack smashing detected ***: /usr/bin/dolphin-emu terminated
======= Backtrace: =========
/lib64/libc.so.6(+0x6ec65)[0x7fa84bce6c65]
/lib64/libc.so.6(__fortify_fail+0x37)[0x7fa84bd6fc27]
/lib64/libc.so.6(__fortify_fail+0x0)[0x7fa84bd6fbf0]
/lib64/libresolv.so.2(+0x8109)[0x7fa847bb0109]
[0x7fa83bb63e80]
======= Memory map: ========
00400000-01200000 r-xp 00000000 08:12 8174                               /usr/bin/dolphin-emu
013ff000-01428000 rw-p 00dff000 08:12 8174                               /usr/bin/dolphin-emu
01428000-01ea1000 rw-p 00000000 00:00 0
02870000-02c94000 rw-p 00000000 00:00 0                                  [heap]
41bc5000-41bc9000 r-xp 00000000 00:00 0
41f68000-44f68000 rwxp 00000000 00:00 0
2300000000-2302000000 rw-s 00000000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
2500000000-2502000000 rw-s 00000000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
257e000000-2580000000 rw-s 02040000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
2580000000-2582000000 rw-s 00000000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
25c0000000-25c2000000 rw-s 00000000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
25e0000000-25e0040000 rw-s 02000000 00:14 27102                          /dev/shm/dolphinmem.0 (deleted)
...

(please let me know if it would be helpful to post more of the dump)

Thank you for any help with this!

I am trying to use Recalbox on a Dell Optiplex that does not have built-in wifi. After some trouble getting a RealTek RTL8188EUS dongle to work, I have decided to just get another one.

Before I order, I have been looking through the compatibility list:
https://github.com/recalbox/recalbox-os/wiki/Compatibility-(EN)

The only one on that list that will work with v4.1 has two antennas:
https://www.amazon.com/Netis-Wireless-Long-Range-High-Gain/dp/B006THNH7Q

is the assumption that anything from a prior version should also work on a newer version?

The Compatibility List is confusing, since for example it will list "RT5370" as working for one device, but not working for another. And most devices don't list the chipsets so it is unclear what to look for.

Or some devices don't have the same chipset mentioned on the compatibility page. Like the Ourlink Wifi Adapter here is not "RTl8192cu" according to the q/a:
https://www.amazon.com/OURLiNK-600Mbps-Wireless-Network-Computer/dp/B011T5IF06

I am looking for someone to please tell me that they have tried a particular wifi dongle and have confirmed that it works with 4.1 - preferably one that is small.

If need be, I will order the one with two antennas, but looking for other options.

Thanks!

If you think it will be easier to just get a different wifi dongle, I'd happily order one. I just don't want to do that only to find that the problem is not related to the dongle.

But, if there is a particular wifi dongle that is known to work well, I'd much rather pay the 10 dollars for it then spend a lot of time trying to diagnose this issue.

@paradadf OK, I just tried version "2018.12.24.Christmas.Beta" on a different usb stick and it is the exact same problem. (Also, still getting the error when I try to save a config via the web ui, but at least I can update the config file manually.)

I am starting to wonder if the issue is simply the driver not being there, because I don't get anything listed for wlan0 when I do ifconfig -a.

But, it does seem to recognize the dongle, since I get all this when I plug it in:

[    3.916054] usb 3-6: new high-speed USB device number 5 using xhci_hcd
[    4.064417] usb 3-6: New USB device found, idVendor=0bda, idProduct=f179
[    4.064418] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.064419] usb 3-6: Product: 802.11n
[    4.064420] usb 3-6: Manufacturer: Realtek
[    4.064420] usb 3-6: SerialNumber: 00E0302D80F8

I am just surprised that there is no notification about anything failing when wifi does not connect. Is there any way at all to get the log message when recalbox tries to connect to the wifi and fails?

@paradadf Aha, I searched the forum and could not find that link. Thanks.

@paradadf Another thing, which I doubt is related, but just mentioning that when I make config changes in the recalbox.local web ui, I get this message when I save:
"An error occurred while saving the configuration."

I think that might have something to do with permissions on the storage device, although I can edit the config file manually (also from the web ui) no problem, so not sure.

I am just mentioning in case it might somehow be related to the wifi issue.

@paradadf

The device appears to be recognized:

# dmesg | grep -i realtek
[    8.031045] usbcore: registered new interface driver ums-realtek
[    8.757683] usb 3-3: Manufacturer: Realtek
...

I'm not sure what else I might look for here.

Where could I find the latest beta?

I tried modifying this hoping that it would find it on restart, but it did not:

## Automatically check for updates at start (0,1)
updates.enabled=1
# Update type : default to stable
updates.type=beta

Is there a .img that I can download or do I need to build it manually from the latest in the repo?

@paradadf Thanks for the fast response.

Before I try the beta, I'm wondering how I can even know what the problem might be. Is there a log file that will tell me why the wifi is not connected?

It looks like realtek drivers already exist on the current version that I am using:

# ls /lib/modules/4.8.11/kernel/drivers/net/wireless/realtek
rtl818x   rtl8xxxu  rtlwifi

So, what would be different about the beta version?

I just set up a new Recalbox instance (v18.07.13 - x86_64) on a Dell OptiPlex 3020.

I am able to connect the device to a network via an ethernet cable, but when I enter wifi settings and unplug the cable, it goes to "Status: Not Connected | IP Address Not Connected".

The PC does not have a built-in wifi card, but I have a Realtek 802.11n 00E0302D80F8.

I have confirmed by ssh'ing into the recalbox device and running lsusb.py, which shows me:

# lsusb.py
 WARNING: Failure to read usb.ids
(<type 'exceptions.IOError'>, IOError(2, 'No such file or directory'), <traceback object at 0x7fd8eb250830>)
usb3             1d6b:0002 09  2.00  480MBit/s 0mA 1IF  (Linux 4.8.11 xhci-hcd xHCI Host Controller 0000:00:14.0) hub
 3-4             1a2c:0023 00  1.10  1.5MBit/s 98mA 2IFs (USB USB Keykoard)
 3-2             0781:5576 00  2.00  480MBit/s 200mA 1IF  (SanDisk Cruzer Facet 4C532005720511102073)
 3-9             046d:c216 00  2.00   12MBit/s 100mA 1IF  (Logitech Logitech Dual Action 943B3916)
 3-10            046d:c216 00  2.00   12MBit/s 100mA 1IF  (Logitech Logitech Dual Action 9441ACA9)
 3-3             0bda:f179 00  2.00  480MBit/s 500mA 1IF  (Realtek 802.11n 00E0302D80F8)

So, the device is detected.

Further, I can boot the PC in Windows and connect to the wireless network with the same SSID and key, without issue, and no need to install any special drivers.

And I know that I can connect to my network with recalbox in general, because I have a Raspberry Pi Recalbox that connects to the network without issue.

So, why is it not able to connect via wifi? Where can I even start to try to debug this issue?

I did look here:
https://github.com/recalbox/recalbox-os/wiki/Compatibility-(EN)

And indeed, RealTek is not listed among the compatible wifi dongles, but I would think that it wouldn't show up in that lsusb list if it was not detected, right?

Before I order a new wifi dongle, is there a more definitive way to determine why it's not connecting? Is there a log file? Or some other way to test the connection?

I could not find anything in the forums that deals with this specifically.