Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNES mini not detected when flashing the kernel #308

Open
ncarrier opened this issue Mar 23, 2020 · 4 comments
Open

SNES mini not detected when flashing the kernel #308

ncarrier opened this issue Mar 23, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@ncarrier
Copy link

Describe the bug
When trying to install the kernel, the snes isn't detected when it reboots.

To Reproduce
Steps to reproduce the behavior:

  1. Click on Kernel - Install / Repair
  2. Put the console in FEL mode
  3. Wait until the dialog indicates a timeout

Expected behavior
The kernel should be properly installed and the snes should reboot.

Additional context
It occurs using debian 10 and Hackshi2-CE version 3.6.1-rc4.
The snes shows up as a network adapter and obtains a link local address.
It's possible to do ssh and ftp on it.

Madmonkey instructed me to do run /etc/init.d/S93mdnsd restart twice using ssh.
This workaround works great and allows to install hakchi and synchronize the product, but needs to be done each time the product reboots.

@ncarrier ncarrier added the bug Something isn't working label Mar 23, 2020
@danaak
Copy link

danaak commented Apr 27, 2020

After digging for a while with the same issue I think I found a solution..

Disable IPv6 for your network adapter.

Disconnect/Reconnect to your network and reopen hakchi. It should be able to detect the console and connect automatically

@ArieKindicator
Copy link

ArieKindicator commented Apr 28, 2020

Device: SNES Mini Classic EU
OS: Windows 10 Pro, version 2004, build 19041.208, Windows Feature Experience Pack 120.2202.130.0
Hakchi2CE: lastest release 3.8

Disable/add hakchi2CE the firewall (as suggested in the pop up screen), or your suggestion to disable IPv6 of the network adapters (Samsung Mobile USB device) didn't work.

The device is recognized in FEL mode but when (re)booting into normal mode Windows 10 Pro* won't recognize the device.
I also de- and reinstalled the USB drivers (with USBDeview) and tried a few older version releases of Hakchi2CE.

What didn't work:

  1. Kernel reset
  2. Uninstall
  3. Factory Reset

After executing one of the above tasks, rebooting the device into 'normal' (non FEL mode) never finishes and the pop up message is displayed (to wait or add hakchi2CE to the firewall rules.)
The progress bar when rebooting the device stalls at 14 - 25 %.
Windows device manager outputs a Code 45 for the "Nintendo Classic" driver: device is not connected to the computer or there is no connection.

The log file:
Base directory: E:\Linked_Hakchi2CE (portable mode) Loading configuration Loading spine templates Starting, version: 3.8.0 Loading libretro core info files ...Executing task: ModTasks.GetHmods Tasker completed all tasks, conclusion: Success Building libretro core cross index Done, 24 cores loaded Loading E:\Linked_Hakchi2CE\data\nescarts.xml Loading SNES Cartridge Cache SNES XML loading done, 786 roms total NES XML loading done, 2150 roms total [Upgrade] No upgrade action needed .Executing task: LoadGamesTask.LoadGames Executing task: LoadGamesTask.CreateListViewGroups Executing task: LoadGamesTask.LoadGamesFromFiles Loading original games data Executing task: LoadGamesTask.AssignGroupsToGames Executing task: LoadGamesTask.AssignListViewGroups Executing task: LoadGamesTask.UpdateListView Tasker completed all tasks, conclusion: Success ............................................Executing task: <>c__DisplayClass0_0.<DownloadFile>b__0 Executing task: <>c__DisplayClass1_0.<MoveFile>b__0 Tasker completed all tasks, conclusion: Success Local hakchi.hmod version info: boot 1.0.3, kernel 3.4.113.29-madmonkey, script v1.0.4-126 Service added: Instance: hakchi Type: _ssh._tcp IP: 169.254.13.37 Port: 22 Txt: hwid=0461872a 87203146 9d28c927 6c118000, type=snes, region=eur Attempting to connect to 169.254.13.37... Unable to connect to SSH server at 169.254.13.37:22 (Een verbindingspoging is mislukt omdat de verbonden party niet correct heeft geantwoord na een bepaalde tijd, of de gemaakte verbinding is mislukt omdat de verbonden host niet heeft geantwoord) Failure. DNS Resolution returned IPs: 169.254.13.37 Attempting to connect to 169.254.13.37... Unable to connect to SSH server at 169.254.13.37:22 (Een verbindingspoging is mislukt omdat de verbonden party niet correct heeft geantwoord na een bepaalde tijd, of de gemaakte verbinding is mislukt omdat de verbonden host niet heeft geantwoord) Failure.

@ArieKindicator
Copy link

ArieKindicator commented Apr 30, 2020

I decided to use the usb transfer method to uninstall everything with the uninstall hmod as the previous efforts didn't work and didn't uninstall anything as I still was able to play every game with the installed cores (see previous message).

The uninstall hmod removed every hmod from my device [assumption as i cant access the device over ftp as this requires a 'normal' connection and not FEL mode], unfortunately also the "USB-host" files and boots into the original games (menu) and refuses to recognize any connected usb flash drives.

I tried to reinstall the required USB-host files but Kernel > Install/Repair won't finish. The FEL mode obviously works but rebooting afterwards to 'normal' mode doesn't. Exactly the same issues as described in the previous message.

My best guess is that it is a device driver issue. The device driver (Nintendo Classic) is unable to detect a connected device when it is in ''normal'' mode (Code 45 error). Note: i also tried different usb cables of which i knew that previously worked just fine.)

@ArieKindicator
Copy link

ArieKindicator commented May 28, 2020

I was able to install hakchi2-ce 2.8 (debug) on my SNESCM using a laptop, running Windows 10 Pro, version 1909, installation date Januari 26, 2020. Build: 18363.592. Not part of an insider/preview ring.

The device is recognized on my laptop in normal and FEL mode. However, the pc still won't recognize a connected device in normal mode.

For now, i can at least use the device again and update all cores using the usb tranfer method.

BTW, is there a way to manually (force) uninstall or install the necessary usb drivers from the hakchi2CE GUI? I would like to be able to uninstall the usb drivers and hakchi2CE (re)installing the usb drivers automatically. Just to make sure that the usb drivers are installed correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants