USB ports don't work after encryption

whois1230 · 09-27-2018, 07:28 AM

Hi, this is a continuation of my older thread: https://www.linuxquestions.org/quest...96#post5908096

My laptop is Dell Latitude E6410 and my operating system is Linux Mint 18.3 Cinnamon 64-bit. I reinstalled Mint to encrypt my OS and my Home folder, which was successfull, and after updating the kernel and everything else, my laptop doesn't recognize USB devices anymore. I tried my USB Wi-Fi adapter(which I need, because my internal Wi-Fi adapter is not working properly) as well as my USB mouse and external USB HDD in all different ports. None of these devices is being recognized. The external HDD's light blinks, but it won't open up.

p.s. The OS version was the same before the reinstall and encryption.

RandomTroll · 09-27-2018, 04:22 PM

This is a hardware event, not software. I've had laptops that allowed me to disable the USB ports. Check your BIOS setup. Your report sounds as though data access through them has been blocked; the HDD's light going on means it's getting power.

IsaacKuo · 09-27-2018, 05:01 PM

It might be a software issue. I've had a computer where the USB ports "stopped" working after a kernel upgrade. But I could boot up using the previous (older) kernel and the USB ports worked. So, the USB ports were just fine, it's just that something was not working right with the relevant kernel modules. At some point, after later updates, I could boot up with the newer (updated) kernel and the USB ports worked just fine.

This was with a Dell Precision T3500 desktop computer, after dist-upgrading from Debian 8 to Debian 9. I don't remember the exact kernel versions at the time of my USB port troubles.

whois1230 · 03-12-2019, 11:30 AM

I ran Dell System Diagnostics and will post the results here: https://imgur.com/a/4LiZmx2 It's a confirmed hardware problem. I used Linux Mint 18.2 for a long time on this laptop. After reinstalling Mint(so that I can encrypt the OS and home folder), the USB ports stopped working. I also installed Windows 7 and all of the needed drivers, and it didn't work then too. I checked the BIOS(which is the newest version) and all was OK there. https://imgur.com/a/9WAUYlG
System Board/Interrupt controller/PIC functionality test:

Test result: fail

Error code 4C00:0522

Msg: SYSTEM - The interrupt controller, or a device attached to it... Couldn't get the whole message.

whois1230 · 03-17-2019, 09:33 AM

Update: The laptop recognizes my smartphone and can charge it, but the option to transfer files does not come up. It also recognizes my external hard drive as I plug it in and it lights, but still doesn't open it. It recognizes USB but cannot open a USB storage flash drive. I tried with several USB sticks. Again, it has something to do with the Motherboard's interrupt controller.

RandomTroll · 03-17-2019, 12:38 PM

Quote:

Originally Posted by whois1230

Update: The laptop recognizes my smartphone and can charge it, but the option to transfer files does not come up.

My un-'smart'phone can be charged from my computer but doesn't connect data-ly. Some USB cables are power-only, not data. Some want that when charging in a public place to prevent hacking.

Quote:

Originally Posted by whois1230

It also recognizes my external hard drive as I plug it in and it lights, but still doesn't open it. It recognizes USB but cannot open a USB storage flash drive. I tried with several USB sticks.

What do you mean by 'recognize'? What does

Code:

lsusb

return? If you run as root?

Quote:

Originally Posted by whois1230

it has something to do with the Motherboard's interrupt controller.

Interrupt controllers can be programmed to mask interrupts (= ignore them). I have never seen one fail.

whois1230 · 03-17-2019, 01:44 PM

Quote:

Originally Posted by RandomTroll

My un-'smart'phone can be charged from my computer but doesn't connect data-ly. Some USB cables are power-only, not data. Some want that when charging in a public place to prevent hacking.

What do you mean by 'recognize'? What does

Code:

lsusb

return? If you run as root?

Interrupt controllers can be programmed to mask interrupts (= ignore them). I have never seen one fail.

I've described the problem in more detail here: https://www.dell.com/community/Latit...t/false#M11224 There are images included. As for the command:

Code:

user@user-Latitude-E6410 ~ $ sudo lsusb
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@user-Latitude-E6410 ~ $

RandomTroll · 03-18-2019, 12:48 AM

I'll let the Dell community address the problem there. lsusb reports no attached devices. (I don't need to run lsusb as root.)

JJJCR · 03-18-2019, 02:12 AM

No need to run lsusb as root

Have you checked this:

Quote:

'dmesg|tail' after plug in the USB drive

What's the output of this:

Quote:

lshw -short -class storage -class disk

whois1230 · 03-18-2019, 07:47 AM

Quote:

Originally Posted by RandomTroll

I'll let the Dell community address the problem there. lsusb reports no attached devices. (I don't need to run lsusb as root.)

Quote:

Originally Posted by JJJCR

No need to run lsusb as root

Have you checked this:

What's the output of this:

I attached the USB device and ran the commands:

Code:

user@user-Latitude-E6410 ~ $ lsusb
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@user-Latitude-E6410 ~ $ dmesg|tail
[  300.296241] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=29685 DF PROTO=TCP SPT=443 DPT=60916 WINDOW=0 RES=0x00 RST URGP=0 
[  302.058546] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=29844 DF PROTO=TCP SPT=443 DPT=60910 WINDOW=0 RES=0x00 RST URGP=0 
[  302.465174] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=29925 DF PROTO=TCP SPT=443 DPT=60918 WINDOW=0 RES=0x00 RST URGP=0 
[  303.111125] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=30013 DF PROTO=TCP SPT=443 DPT=60936 WINDOW=0 RES=0x00 RST URGP=0 
[  303.380928] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=30037 DF PROTO=TCP SPT=443 DPT=60948 WINDOW=0 RES=0x00 RST URGP=0 
[  304.372442] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=30089 DF PROTO=TCP SPT=443 DPT=60946 WINDOW=0 RES=0x00 RST URGP=0 
[  305.550589] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=30187 DF PROTO=TCP SPT=443 DPT=60954 WINDOW=0 RES=0x00 RST URGP=0 
[  324.363644] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:40:a5:ef:32:45:14:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=8203 PROTO=2 
[  330.186552] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=31203 DF PROTO=TCP SPT=443 DPT=60886 WINDOW=0 RES=0x00 RST URGP=0 
[  349.363583] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:40:a5:ef:32:45:14:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=8204 PROTO=2 
user@user-Latitude-E6410 ~ $ lshw -short -class storage -class disk 
WARNING: you should run this program as super-user.
H/W path         Device      Class       Description
====================================================
/0/100/1f.2                  storage     82801 Mobile SATA Controller [RAID mode
/0/2             scsi1       storage     
/0/2/0.0.0       /dev/cdrom  disk        DVD+-RW TS-U633J
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.
user@user-Latitude-E6410 ~ $

dc.901 · 03-18-2019, 09:38 AM

Quote:

Originally Posted by whois1230

Code:

user@user-Latitude-E6410 ~ $ lsusb
...
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.
...

Please run:

Code:

sudo lsusb

AND

sudo dmesg | tail

JJJCR · 03-21-2019, 03:28 AM

Quote:

Originally Posted by whois1230

Hi, this is a continuation of my older thread: https://www.linuxquestions.org/quest...96#post5908096

My laptop is Dell Latitude E6410 and my operating system is Linux Mint 18.3 Cinnamon 64-bit. I reinstalled Mint to encrypt my OS and my Home folder, which was successfull, and after updating the kernel and everything else, my laptop doesn't recognize USB devices anymore. I tried my USB Wi-Fi adapter(which I need, because my internal Wi-Fi adapter is not working properly) as well as my USB mouse and external USB HDD in all different ports. None of these devices is being recognized. The external HDD's light blinks, but it won't open up.

p.s. The OS version was the same before the reinstall and encryption.

I re-read your post, this happens after the OS encryption. After encrypting the OS, all USB devices are not working.
If you have an extra thumbdrive and a Linux Mint Live CD or other Linux OS.

Try encrypting the thumbdrive, after encryption plug it to the encrypted Mint OS.

If it works, then I guess Encrypted OS can only read Encrypted USB which which should not be of course. However, if it really works then it could be a limitation and might be address in future releases.

whois1230 · 03-21-2019, 04:26 AM

Quote:

Originally Posted by dc.901

Please run:

Code:

sudo lsusb

AND

sudo dmesg | tail

Quote:

Originally Posted by JJJCR

I re-read your post, this happens after the OS encryption. After encrypting the OS, all USB devices are not working.
If you have an extra thumbdrive and a Linux Mint Live CD or other Linux OS.

Try encrypting the thumbdrive, after encryption plug it to the encrypted Mint OS.

If it works, then I guess Encrypted OS can only read Encrypted USB which which should not be of course. However, if it really works then it could be a limitation and might be address in future releases.

Code:

user@user-Latitude-E6410 ~ $ sudo lsusb
[sudo] password for user: 
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@user-Latitude-E6410 ~ $ sudo dmesg | tail
[  753.314364] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9500 DF PROTO=TCP SPT=443 DPT=52368 WINDOW=0 RES=0x00 RST URGP=0 
[  753.811514] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9528 DF PROTO=TCP SPT=443 DPT=52372 WINDOW=0 RES=0x00 RST URGP=0 
[  754.396739] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9585 DF PROTO=TCP SPT=443 DPT=52346 WINDOW=0 RES=0x00 RST URGP=0 
[  755.215846] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9680 DF PROTO=TCP SPT=443 DPT=52378 WINDOW=0 RES=0x00 RST URGP=0 
[  755.290253] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9686 DF PROTO=TCP SPT=443 DPT=52304 WINDOW=0 RES=0x00 RST URGP=0 
[  756.704265] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=9950 DF PROTO=TCP SPT=443 DPT=52396 WINDOW=0 RES=0x00 RST URGP=0 
[  758.479650] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=10283 DF PROTO=TCP SPT=443 DPT=52214 WINDOW=0 RES=0x00 RST URGP=0 
[  776.866060] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:40:a5:ef:32:45:14:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=21170 PROTO=2 
[  779.744078] [UFW BLOCK] IN=eno1 OUT= MAC=5c:26:0a:4f:31:1b:40:a5:ef:32:45:14:08:00 SRC=216.162.47.68 DST=192.168.10.101 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=13235 DF PROTO=TCP SPT=443 DPT=52398 WINDOW=0 RES=0x00 RST URGP=0 
[  801.866057] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:40:a5:ef:32:45:14:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=21173 PROTO=2 
user@user-Latitude-E6410 ~ $

The OS is no longer encrypted, nor is the home folder. I reinstalled after that, but the USBs still do not get recognized.

dc.901 · 03-21-2019, 07:23 AM

Quote:

Originally Posted by whois1230

The OS is no longer encrypted, nor is the home folder. I reinstalled after that, but the USBs still do not get recognized.

Let's do some basic checks:
1) USB ports on the computer are enabled in BIOS?
2) USB devices you are trying on this machine, works in different machine?

JJJCR · 03-22-2019, 03:42 AM

Have you tried to temporarily stop UFW and check whether the usb will be detected?

sudo ufw disable