Can not use USB3.0 in DBI-SOLVED

[johnkelvinliu]

DBI 658+firmware 18.0.1, USB 3.0 does not work in DBI. Only usb 2.0. The USB cable was tested that it can run USB 3.0. How to solve it?

Solution of using USB3.0 again with fss0=atmosphere/package3, add usb3force=1 to each boot menu in micro sd card/bootloader/hekate_ipl.ini: [config] autoboot=2 autoboot_list=0 bootwait=0 backlight=100 noticker=0 autohosoff=2 autonogc=1 updater2p=1 bootprotect=0

[CFW - sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 emummc_force_disable=1 icon=bootloader/res/icon_payload.bmp usb3force=1

[CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp usb3force=1

[Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp usb3force=1

---

The about settings does not require below settings as described in DBI readme. micro sd card/atmosphere/config/system_settings.ini : [usb] usb30_force_enabled = u8!0x1

[muxi1]

The same problem here under AMS 1.7.0 / FW 18.0.1 / DBI 658. USB 3.0 is displayed as enabled in the DBI system info. Installations via the MTP responder are only carried out with USB 2.0. However, I have set USB 3.0 via exosphere.ini.

[rashevskyv]

Works fine on kefir

[rashevskyv]

It is works fine. There in no any exclusive features for kefir. You should check your own armosphere settings

[RoboFox83]

I was having the same issue as johnkelvinliu.

I have two switches both on 18.0.0 on AMS 1.7. Both had usb30_force_enabled = u8!0x1 under system_settings.ini . One connects at 2.0 and the other at 3.0, using the same cable/port on my PC.

While looking at info from DBI the one that was working shows USB 3.0 says no for Force enable USB 3.0 and the one connecting at USB 2.0 says enabled for Forced enable USB 3.0. Which I would expect the opposite results.

After digging further I found the USB 3.0 Switch was booting using a modified fusee.bin with sigpatches. Where the USB 2.0 was using Hekate with fss0 method to boot Atmosphere.

It seems the fss0 method doesn't obey my system_settings.ini file, even though the info in DBI says it's forced. Using a modified fusee.bin to boot it with my sigpatches appears to enable USB 3.0 for me. Maybe just adding usb3force=1 to fss0 would work, but that setting says if it doesn't exist it should use system_settings.ini.. which according to DBI it is, but it doesn't actually appear to be enabling it.

Hope this helps, I'm pretty new to all this so please excuse that.

[johnkelvinliu]

I also find something similar. An old instruction a few years ago also said the fss0 would disable the settings in microSDcard/atmosphere/config/system_settings.ini. It states that typing the followings words in microSDcard/bootloader/hekate_ipl.ini would help in this case: usb3force=1 However it did not state clearly where should we type it in the file. If it is typed under [config], nothing happens; While typing it under [CFW - emuMMC], DBI can not connect to the computer via USB. Therefore it does not work.

Yes, it is confirmed that [RoboFox83] solution works! Thanks alot.

[rashevskyv]

Or use kefir instead. With much more benefits

[SwimmingTiger]

For the Hekate configuration with fss0=atmosphere/package3, you need to add usb3force=1 to each boot menu.

This is my hekate_ipl.ini:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=89
noticker=0
autohosoff=1
autonogc=1
updater2p=1
bootprotect=0

[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
usb3force=1

[EMU Online]
fss0=atmosphere/package3
kip1=atmosphere/kips/loader.kip
emupath=emuMMC/RAW1
emummcforce=1
usb3force=1

[EMU Offline]
fss0=atmosphere/package3
kip1=atmosphere/kips/loader.kip
emupath=emuMMC/RAW2
emummcforce=1
cal0blank=1
kip1patch=nosigchk
usb3force=1

[johnkelvinliu]

Yes, it works without using modified fusee which is much more simple, thx. What is the usage of using a raw partitions named EMU online?

[belmer95]

Ho avuto lo stesso problema di johnkelvinliu.

Ho due switch entrambi su 18.0.0 su AMS 1.7. Entrambi avevano usb30_force_enabled = u8!0x1 in system_settings.ini . Uno si collega a 2.0 e l'altro a 3.0, usando lo stesso cavo/porta sul mio PC.

Esaminando le informazioni da DBI, quello che funzionava mostrava che USB 3.0 diceva no per Forza abilitazione USB 3.0 e quello che si collegava a USB 2.0 diceva abilitato per Forza abilitazione USB 3.0. Da cui mi sarei aspettato risultati opposti.

Dopo aver scavato ulteriormente, ho scoperto che lo Switch USB 3.0 si avviava usando un fusee.bin modificato con sigpatches. Mentre l'USB 2.0 utilizzava Hekate con metodo fss0 per avviare Atmosphere.

Sembra che il metodo fss0 non rispetti il ​​mio file system_settings.ini, anche se le informazioni in DBI dicono che è forzato. Usare un fusee.bin modificato per avviarlo con i miei sigpatch sembra abilitare USB 3.0 per me. Forse aggiungere semplicemente usb3force=1 a fss0 funzionerebbe, ma quell'impostazione dice che se non esiste dovrebbe usare system_settings.ini... che secondo DBI è così, ma in realtà non sembra abilitarlo.

Spero che questo vi sia utile. Sono piuttosto nuovo in tutto questo, quindi scusatemi.

I also have the same problem, can you send me the link to download the modified fusee.bin?