Samsung Galaxy Note II

malloc · 12-24-2012, 05:45 PM

This is so terribly annoying. I've had it with Slackware. I've been a loyal user of Slackware for over 10 years, but now I've soon had more than enough.

Take a look at this: http://www.youtube.com/watch?v=7waXXfyq4NI

The Galaxy Note II seems to work in USB mass storage mode out of the box on Ubuntu. Why doesn't this work in Slackware?

Kernel ring buffer (dmesg) shows the following when the device is connected via USB:

Code:

hub 1-5:1.0: state 7 ports 4 chg 0000 evt 0008
hub 1-5:1.0: port 3, status 0100, change 0001, 12 Mb/s
usb 1-5.3: USB disconnect, device number 17
usb 1-5.3: unregistering device
usb 1-5.3: unregistering interface 1-5.3:1.0
usb 1-5.3: unregistering interface 1-5.3:1.1
usb 1-5.3: unregistering interface 1-5.3:1.2
usb 1-5.3: usb_disable_device nuking all URBs
hub 1-5:1.0: debounce: port 3: total 100ms stable 100ms status 0x100
hub 1-5:1.0: state 7 ports 4 chg 0000 evt 0008
hub 1-5:1.0: port 3, status 0101, change 0001, 12 Mb/s
hub 1-5:1.0: debounce: port 3: total 175ms stable 100ms status 0x101
hub 1-5:1.0: port 3 not reset yet, waiting 10ms
usb 1-5.3: new high-speed USB device number 18 using ehci_hcd
hub 1-5:1.0: port 3 not reset yet, waiting 10ms
usb 1-5.3: skipped 1 descriptor after endpoint
usb 1-5.3: skipped 4 descriptors after interface
usb 1-5.3: default language 0x0409
usb 1-5.3: udev 18, busnum 1, minor = 17
usb 1-5.3: New USB device found, idVendor=04e8, idProduct=6860
usb 1-5.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-5.3: Product: SAMSUNG_Android
usb 1-5.3: Manufacturer: SAMSUNG
usb 1-5.3: SerialNumber: 4df101e2382e8f27
usb 1-5.3: usb_probe_device
usb 1-5.3: configuration #1 chosen from 1 choice
usb 1-5.3: adding 1-5.3:1.0 (config #1, interface 0)
usb 1-5.3: adding 1-5.3:1.1 (config #1, interface 1)
usb 1-5.3: adding 1-5.3:1.2 (config #1, interface 2)
usb 1-5.3: adding 1-5.3:1.3 (config #1, interface 3)

lsusb shows me:

Code:

Bus 001 Device 018: ID 04e8:6860 Samsung Electronics Co., Ltd

However lsscsi gives me nothing I can mount.

What do I need to do to be able to mount this device?

I've tried to set (in Android) the device into MTP mode and PTP mode, PTP would require ptpcam or something equivalent and ptpcam --list-devices gives me nothing, but I want USB, not PTP.

acid_kewpie · 12-25-2012, 03:04 AM

if it's like the S3, and I'd certainly expect it to be, it will NOT function as a mass storage device. Samsung deliberately removed that config in favour of MTP. you should be able to install libmtp under slack to get it going.

malloc · 12-25-2012, 11:49 PM

Quote:

Originally Posted by acid_kewpie

if it's like the S3, and I'd certainly expect it to be, it will NOT function as a mass storage device. Samsung deliberately removed that config in favour of MTP. you should be able to install libmtp under slack to get it going.

Thanks for the tip.

I've now tried with MTP, I already had version 1.1.1 installed, so I tried that first, with the following results:

Code:

# mtp-detect 
libmtp version: 1.1.1

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2.
   Found 1 device(s):
   Samsung: GT-P7510/Galaxy Tab 10.1/S2 (04e8:6860) @ bus 1, dev 20
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

I then proceeded to install version 1.1.5, which as of this date appears to be the latest version. With 1.1.5 I got the following results:

Code:

# mtp-detect 
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 22
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

I also tried "mtp-connect" which seems to detect the device correctly, but still fails to connect. The device works perfectly fine in Windows, I can copy data to it with no issues.