USB 3.0 problem on Dell Inspiron n7110

English Hardware
#1

I’m running OpenSuse 13.2 on my laptop (Dell Inspiron N7110). When I connect a USB 3.0 device the kernel recognize it but the system doesn’t show anything. The log after executing dmesg is the following:

1086.287858] usb 2-1.3: new high-speed USB device number 5 using ehci-pci
1086.374600] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5581
1086.374610] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
1086.374615] usb 2-1.3: Product: Ultra
1086.374619] usb 2-1.3: Manufacturer: SanDisk
1086.374622] usb 2-1.3: SerialNumber: 4C530001270203118111
1086.375372] usb-storage 2-1.3:1.0: USB Mass Storage device detected
1086.376768] scsi7 : usb-storage 2-1.3:1.0
1087.380152] scsi 7:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
1087.380925] sd 7:0:0:0: Attached scsi generic sg3 type 0
1087.382358] sd 7:0:0:0: [sdc] 60751872 512-byte logical blocks: (31.1 GB/28.9 GiB)
1087.383857] sd 7:0:0:0: [sdc] Write Protect is off
1087.383867] sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
1087.386377] sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
1087.415769] sdc: sdc1
1087.419771] sd 7:0:0:0: [sdc] Attached SCSI removable disk
1095.062686] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
1095.827676] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC= SRC=fe80:0000:0000:0000:be77:37ff:fe69:7f1c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
1110.448949] usb 2-1.3: USB disconnect, device number 5
1127.023894] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
1191.178600] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
1319.266711] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
1464.836920] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=bc:77:37:69:7f:1c:00:25:9e:fb:20:01:08:00 SRC=10.8.133.38 DST=10.8.128.207 LEN=78 TOS=0x00 PREC=0x00 TTL=127 ID=7622 PROTO=UDP SPT=64878 DPT=137 LEN=58
1566.962722] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=bc:77:37:69:7f:1c:00:25:9e:fb:20:01:08:00 SRC=10.8.47.237 DST=10.8.128.207 LEN=78 TOS=0x00 PREC=0x00 TTL=124 ID=24438 PROTO=UDP SPT=58530 DPT=137 LEN=58
1575.467380] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
1716.086601] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=bc:77:37:69:7f:1c:00:25:9e:fb:20:01:08:00 SRC=10.8.135.244 DST=10.8.128.207 LEN=78 TOS=0x00 PREC=0x00 TTL=127 ID=27205 PROTO=UDP SPT=64297 DPT=137 LEN=58
2087.844200] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:00:1b:fc:e9:c5:38:86:dd SRC=fe80:0000:0000:0000:021b:fcff:fee9:c538 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=87 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=47
2120.600390] SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC= SRC=fe80:0000:0000:0000:be77:37ff:fe69:7f1c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44

Can anyone help me?

#2

Hi
Does the system have USB 3.0 ports? If so it may only be on one side. You can check via;


lsusb

Do you see a “3.0 root hub” listed?

#3

Well the disk is recognised it (otherwise the above would not happen). Now you need to to know if is mounted

/sbin/fdisk -l

mount|grep sdc
#4

BTW, what does the following say about the device?

/usr/sbin/blkid
#5

It’s not clear that there is a problem.

I plug in a USB flash drive, and get:


[235212.110139] usb 1-1.1: new high-speed USB device number 4 using ehci-pci
[235212.196403] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5530
[235212.196407] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[235212.196410] usb 1-1.1: Product: Cruzer Glide
[235212.196412] usb 1-1.1: Manufacturer: SanDisk
[235212.196414] usb 1-1.1: SerialNumber: 4C532009470422119153
[235212.228676] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[235212.228832] scsi6 : usb-storage 1-1.1:1.0
[235212.228911] usbcore: registered new interface driver usb-storage
[235212.233631] usbcore: registered new interface driver uas
[235213.231615] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Glide     1.26 PQ: 0 ANSI: 5
[235213.231809] sd 6:0:0:0: Attached scsi generic sg4 type 0
[235213.233807] sd 6:0:0:0: [sdd] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[235213.235389] sd 6:0:0:0: [sdd] Write Protect is off
[235213.235395] sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00
[235213.236428] sd 6:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[235213.247199]  sdd: sdd1 sdd2
[235213.251747] sd 6:0:0:0: [sdd] Attached SCSI removable disk

But the KDE device notifier does not show.

I expect this. I can manually mount the disk (with the “mount” command).

Incidentally, this is a Dell Inspiron 660, the usb device is USB2 and I plugged into a USB2 port (because that’s what’s on the front).

The particular USB happens to contain the DVD install iso for installing Tumbleweed. My experience is that the KDE device notifier will tell me about a USB with a live iso, but it won’t tell me about a USB with the DVD installer. I’m not sure why. If I recall correctly, this changed around opensuse 12.1 or 12.2.

#6

Yes, I see it. The output is the following:

Bus 002 Device 004: ID 8086:0189 Intel Corp.
Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 1bcf:2b80 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

#7

The output of /sbin/fdisk -l is the following:

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x07f2837e

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 * 206848 104872319 104665472 49.9G 83 Linux
/dev/sda3 104872384 976773167 871900784 415.8G 83 Linux

And the output for

mount|grep sdc

[/QUOTE] is empty

#8

The output of that command is:

/dev/sda1: LABEL=“System Reserved” UUID=“C6E60DD5E60DC721” TYPE=“ntfs” PARTUUID=“07f2837e-01”
/dev/sda2: UUID=“8378d11e-09a8-493f-bcab-6714fa4b1f43” TYPE=“ext4” PTTYPE=“dos” PARTUUID=“07f2837e-02”
/dev/sda3: LABEL=“Data” UUID=“61485527-df99-4b1f-b071-b9dddfddb865” TYPE=“ext4” PARTUUID=“07f2837e-03”

#9

Hi
OK, so I’m now assuming two issues, one, not connecting at USB 3.0 and not identified as being mounted (BTW it’s sdc1 not sdc).

Are any of the USB ports on the device colored blue, if so this is the USB 3.0 port.

On this system when plugging in a USB 3.0 device I see;


[591740.660498] usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd
[591740.677678] usb 4-2: Parent hub missing LPM exit latency info.  Power management will be impacted.
[591740.680049] usb 4-2: New USB device found, idVendor=13fe, idProduct=5200
[591740.680056] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[591740.680062] usb 4-2: Product: Patriot Memory
[591740.680067] usb 4-2: Manufacturer:         
[591740.680073] usb 4-2: SerialNumber: 070144F832282881
[591740.681996] usb-storage 4-2:1.0: USB Mass Storage device detected
[591740.682137] scsi10 : usb-storage 4-2:1.0
[591741.681245] scsi 10:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
[591741.681816] sd 10:0:0:0: [sdb] 123502592 512-byte logical blocks: (63.2 GB/58.8 GiB)
[591741.682709] sd 10:0:0:0: Attached scsi generic sg2 type 0
[591741.682779] sd 10:0:0:0: [sdb] Write Protect is off
[591741.682786] sd 10:0:0:0: [sdb] Mode Sense: 2b 00 00 08
[591741.683771] sd 10:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[591741.869115]  sdb: sdb1
[591741.872782] sd 10:0:0:0: [sdb] Attached SCSI removable disk

As you can see from the first line it’s using the xhci_hcd driver (USB 3.0).

What is the device, it’s not formatted exfat by chance?

#10

Yes, I have two USB 3.0 blue ports. The device is a SanDisk memory stick with FAT32 filesystem, but I have the same problem with an external hard disk drive.

#11

Just checking: Did this command get run after the device was plugged in. If so, I’m surprised since sdc was reported in your dmesg output. So, maybe the device disappears a short time after being connected?

#12

That is exactly what happens, I connect my USB 3.0 device, it is recognized but after that it disapears and the USB 3.0 ports (not the USB 2.0 ports) become unavailable until I reboot the computer.

#13

I would expect to see more messages from the kernel relating to sdc, if there are problems. They could be filtered and captured with something like

tail -f /var/log/messages|grep sdc

Observe what happens when device plugged in. There may well be open bugs on this already.

#14

There is no messages file, in that folder all that I have is:

alternatives.log boot.log hp lastlog pk_backend_zypp README tuned vboxadd-install-x11.log wtmp YaST2 zypper.log-20150313.xz
apache2 btmp journal mysql pk_backend_zypp-1 samba updateTestcase-2015-03-23-16-05-11 VBoxGuestAdditions.log wtmp-20150313.xz zypp zypper.log-20150318.xz
apparmor cups kdm.log ntp pm-powersave.log snapper.log updateTestcase-2015-03-24-15-18-48 VBoxGuestAdditions-uninstall.log Xorg.0.log zypper.log
audit faillog krb5 pbl.log pm-suspend.log tomcat vboxadd-install.log wpa_supplicant.log Xorg.0.log.old zypper.log-20150215.xz

#15

That just means you don’t have syslog (or similar) running. You can still get kernel messaging via journactl though.

For more info

man journalctl
#16

On Thu, 26 Mar 2015 03:46:01 +0000, ltmartin wrote:

> I’m running OpenSuse 13.2 on my laptop (Dell Inspiron N7110). When I
> connect a USB 3.0 device the kernel recognize it but the system doesn’t
> show anything.

As it happens, I have this exact same laptop here.

Never had a problem with USB drives on the USB3 port - in fact, just plugged one in, and the system showed it as soon as it was plugged in:


 5307.673676] usb 2-1.2: new high-speed USB device number 8 using ehci-pci
 5307.760635] usb 2-1.2: New USB device found, idVendor=0781, idProduct=556c
 5307.760645] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
 5307.760650] usb 2-1.2: Product: Ultra
 5307.760653] usb 2-1.2: Manufacturer: SanDisk
 5307.760657] usb 2-1.2: SerialNumber: 20044321711D8B41B33C
 5307.761265] usb-storage 2-1.2:1.0: USB Mass Storage device detected
 5307.761788] scsi8 : usb-storage 2-1.2:1.0
 5308.766149] scsi 8:0:0:0: Direct-Access     SanDisk  Ultra            1.26 PQ: 0 ANSI: 5
 5308.766821] sd 8:0:0:0: Attached scsi generic sg2 type 0
 5308.768286] sd 8:0:0:0: [sdb] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
 5308.769989] sd 8:0:0:0: [sdb] Write Protect is off
 5308.770014] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
 5308.771115] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 5308.784713]  sdb: sdb1
 5308.789018] sd 8:0:0:0: [sdb] Attached SCSI removable disk

So perhaps we should compare what’s different in our setups.

I’m using GNOME3 here, otherwise generally stock 13.2 installation - kernel is the desktop kernel.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#17

I’m using KDE 4.14.6 and my Kernel version is 3.16.7-7-desktop. Note that this happens when I connect the USB 3 device on an USB 3 port, if I plug the USB 3 on an USB 2 port it works well.

#18

On Sat, 28 Mar 2015 12:16:01 +0000, ltmartin wrote:

> I’m using KDE 4.14.6 and my Kernel version is 3.16.7-7-desktop. Note
> that this happens when I connect the USB 3 device on an USB 3 port, if I
> plug the USB 3 on an USB 2 port it works well.

Same kernel version that I’m using, just a difference in desktop.

If I have some free time tomorrow, I’ll try starting KDE (don’t think I
have it installed, but that’s easily dealt with) and see if I can
duplicate. I think I’m using the same type of device you are (the Sandisk
ultra flash drive, though I didn’t know it was USB 3.0), so we should
have a minimum of differences in our setups.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#19

The message I get is the following:

Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: New USB device found, idVendor=0781, idProduct=5581
Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: Product: Ultra
Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: Manufacturer: SanDisk
Apr 02 13:41:29 SHEKINAH.CU kernel: usb 4-1: SerialNumber: 4C530001270203118111
Apr 02 13:41:29 SHEKINAH.CU kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
Apr 02 13:41:29 SHEKINAH.CU kernel: scsi7 : usb-storage 4-1:1.0
Apr 02 13:41:29 SHEKINAH.CU mtp-probe[2520]: checking bus 4, device 2: “/sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/usb4/4-1”
Apr 02 13:41:29 SHEKINAH.CU mtp-probe[2520]: bus: 4, device: 2 was not an MTP device
Apr 02 13:41:30 SHEKINAH.CU kernel: scsi 7:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] 60751872 512-byte logical blocks: (31.1 GB/28.9 GiB)
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Write Protect is off
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Mode Sense: 43 00 00 00
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
Apr 02 13:41:30 SHEKINAH.CU kernel: sdb: sdb1
Apr 02 13:41:30 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Attached SCSI removable disk
Apr 02 13:41:32 SHEKINAH.CU kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 02 13:41:32 SHEKINAH.CU udisksd[1522]: Mounted /dev/sdb1 at /run/media/leandro/C6F1-F14F on behalf of uid 1000
Apr 02 13:42:16 SHEKINAH.CU kernel: SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=bc:77:37:69:7f:1c:00:25:9e:fb:20:01:08:00 SRC=10.8.13.240 DST=10.8.128.207 LEN=78 TOS=0x00 PREC=0x00 TTL=124 ID=2864 PROTO=UDP SPT=52057 DPT=137 LEN
Apr 02 13:42:20 SHEKINAH.CU cntlm[1038]: 127.0.0.1 CONNECT mtalk.google.com:5228
Apr 02 13:42:41 SHEKINAH.CU kernel: SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=bc:77:37:69:7f:1c:54:04:a6:4f:b4:33:08:00 SRC=10.8.128.219 DST=224.0.0.251 LEN=73 TOS=0x00 PREC=0x00 TTL=255 ID=37162 DF PROTO=UDP SPT=5353 DPT=5353
Apr 02 13:42:42 SHEKINAH.CU cntlm[1038]: 127.0.0.1 CONNECT mtalk.google.com:443
Apr 02 13:42:43 SHEKINAH.CU kernel: SFW2-INext-DROP-DEFLT IN=wlp1s0 OUT= MAC=33:33:00:00:00:fb:54:04:a6:4f:b4:33:86:dd SRC=fe80:0000:0000:0000:5604:a6ff:fe4f:b433 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=93 TC=0 HOPLIM
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Unhandled error code
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb]
Apr 02 13:43:17 SHEKINAH.CU kernel: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] CDB:
Apr 02 13:43:17 SHEKINAH.CU kernel: Write(10): 2a 00 03 14 b0 40 00 00 01 00
Apr 02 13:43:17 SHEKINAH.CU kernel: end_request: I/O error, dev sdb, sector 51687488
Apr 02 13:43:17 SHEKINAH.CU kernel: Buffer I/O error on device sdb1, logical block 51665568
Apr 02 13:43:17 SHEKINAH.CU kernel: lost page write due to I/O error on sdb1
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] Unhandled error code
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb]
Apr 02 13:43:17 SHEKINAH.CU kernel: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Apr 02 13:43:17 SHEKINAH.CU kernel: sd 7:0:0:0: [sdb] CDB:
Apr 02 13:43:17 SHEKINAH.CU kernel: Write(10): 2a 00 03 14 b0 20 00 00 02 00

#20

Did you finally tested OpenSuse 13.2 with KDE and USB 3.0 devices?