Hello
I have limpt error when I try do connect my Nintendo Switch (via DBI) to my laptop.
In Win10 it works fine and I can transfer files.
Any help on how to solve this?
[jesuslinux@A4910MJ ~]$ mtpfs
Listing raw device(s)
Device 0 (VID=057e and PID=201d) is a Nintendo Switch / Switch Lite.
Found 1 device(s):
Nintendo: Switch / Switch Lite (057e:201d) @ bus 1, dev 4
Attempting to connect device
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
I read that post prior to posting myself.
System is updated.
I rebooted and the issue persists.
Cannot transfer files from PC to device.
Device shows:
Bus 001 Device 002: ID 057e:201d Nintendo Co., Ltd DBI
[jesuslinux@A4910MJ ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 057e:201d Nintendo Co., Ltd DBI
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 003 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. HP Wide Vision HD
Bus 003 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio
Bus 003 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse
Does the device appear in Thunar? You might need gvfs-mtp for that functionality if you don’t already have it installed. If you do, it’s possible that GVFS is automounting it stopping MTPfs from accessing it.
The device appear in Thunar. It is when I try do copy files from PC to device partition that I get the error:
[jesuslinux@A4910MJ ~]$ mtp-detect
libmtp version: 1.1.22
Listing raw device(s)
Device 0 (VID=057e and PID=201d) is a Nintendo Switch / Switch Lite.
Found 1 device(s):
Nintendo: Switch / Switch Lite (057e:201d) @ bus 1, dev 4
Attempting to connect device(s)
Android device detected, assigning default bug flags
USB low-level info:
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 057e
idProduct: 201d
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 4
Device entry info:
Vendor: Nintendo
Vendor id: 0x057e
Product: Switch / Switch Lite
Product id: 0x201d
Device flags: 0x18008106
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Device info:
Manufacturer: Nintendo
Model: Switch
Device version: 21.2.0
Serial number: XTJ10848261211
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: Get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1007: Get object handles
1008: Get object info
1009: Get object
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1019: Move object
101b: Get partial object
95c1: Get Partial Object (64bit Offset)
95c2: Send Partial Object
95c3: Truncate Object
95c4: Begin Edit Object
95c5: End Edit Object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9808: Send object property list
Events supported:
0x4002: ObjectAdded
0x4003: ObjectRemoved
0x4004: StoreAdded
0x4005: StoreRemoved
0x400e: UnreportedStatus
0x4007: ObjectInfoChanged
0xc801: ObjectPropChanged
Device Properties Supported:
0xd402: Friendly Device Name
0xd406: Session Initiator Info
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY GROUP 0x0
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY GROUP 0x0
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form GET/SET GROUP 0x0
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY GROUP 0x0
dc04: Object Size UINT64 data type READ ONLY GROUP 0x0
dc44: Name STRING data type GET/SET GROUP 0x0
3001: Association/Directory
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY GROUP 0x0
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY GROUP 0x0
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form GET/SET GROUP 0x0
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY GROUP 0x0
dc04: Object Size UINT64 data type READ ONLY GROUP 0x0
dc44: Name STRING data type GET/SET GROUP 0x0
Storage Devices:
StorageID: 0x00010001
StorageType: 0x0004 removable RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 492411289600
FreeSpaceInBytes: 339388923904
FreeSpaceInObjects: 1073741824
StorageDescription: 1: SD Card
VolumeIdentifier:
StorageID: 0x00010002
StorageType: 0x0001 fixed ROM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0001 read only
MaxCapacity: 16507699200
FreeSpaceInBytes: 15808167936
FreeSpaceInObjects: 1073741824
StorageDescription: 2: Nand USER
VolumeIdentifier:
StorageID: 0x00010003
StorageType: 0x0001 fixed ROM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0001 read only
MaxCapacity: 2683027456
FreeSpaceInBytes: 1150959616
FreeSpaceInObjects: 1073741824
StorageDescription: 3: Nand SYSTEM
VolumeIdentifier:
StorageID: 0x00010005
StorageType: 0x0004 removable RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 492411289600
FreeSpaceInBytes: 339388923904
FreeSpaceInObjects: 1073741824
StorageDescription: 5: SD Card install
VolumeIdentifier:
StorageID: 0x00010006
StorageType: 0x0003 fixed RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 16507699200
FreeSpaceInBytes: 15808167936
FreeSpaceInObjects: 1073741824
StorageDescription: 6: NAND install
VolumeIdentifier:
StorageID: 0x00010007
StorageType: 0x0003 fixed RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 492411289600
FreeSpaceInBytes: 339388923904
FreeSpaceInObjects: 1073741824
StorageDescription: 7: Saves
VolumeIdentifier:
StorageID: 0x00010008
StorageType: 0x0001 fixed ROM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0002 read only + object deletion
MaxCapacity: 0
FreeSpaceInBytes: 0
FreeSpaceInObjects: 1073741824
StorageDescription: 8: Album
VolumeIdentifier:
Special directories:
Default music folder: 0xffffffff
Default playlist folder: 0xffffffff
Default picture folder: 0xffffffff
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: DBI MTP Responder
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
OK.
Out o curiosity:
I have MX Linux XFCE installed on dual boot with Manjaro XFCE on the same machine.
On MX Linux file transfer works as expected no libmtp error…
You have been asked to change the topic title, but either missed or ignored the request. I have taken the liberty of renaming your topic title to: “Nintendo Switch: System reports device is busy”.
Is there a question here?
Information that might possibly be useful:
1. Which GRUB instance is being used to boot these OS instances?
GRUB installed by MX Linux XFCE?
GRUB installed by Manjaro XFCE?
Something else?
2. Does it make a difference if you shutdown MX Linux (instead of rebooting directly) and waiting a minute or two before then booting into Manjaro?
Sorry I didn’t know what I should rename the topic to…
1 - The GRUB Being used is the MX Linux one.
2 - The issue started at first boot into Manjaro. In Thunar it says the error above.
I boot into MX and it works with no problems…
