Disk expansion card in the left front port is not detected on Fedora

Framework Laptop 13 Linux
1

I need your help to solve an issue I am facing that is related to disk expansion card auto-detection. Thanks.

Summary

My 250 GB expansion card is not detected when it is inserted into the left front port. But it is detected into the right front port.

My environment

  • Framework 11th Gen. Batch 2.
  • OS: Fedora 36.
  • BIOS version: 03.10
  • Kernel: 5.19.8-200.fc36.x86_64 (uname -r)
  • Window manager: Sway
    $ rpm -q sway
sway-1.7-1.fc36.x86_64
  • nautilus (GUI filter):
    $ rpm -q nautilus
nautilus-42.2-1.fc36.x86_64

I have the expansion cards below.

  • USB-C Expansion Card x 2
  • USB-A Expansion Card
  • 250 GB Expansion Card

Reproducing steps

First imagine the 2 conditions below. The “USB-C”, “USB-A”, “250GB” mean the expansion card.

Condition A

               Back
       +--------------------+
       |                    |   
 USB-C [                    ] USB-C
 Left  |      Keyboard      | Right
 USB-A [                    ] 250GB
       |                    |   
       |      Touchpad      |   
       |                    |   
       +--------------------+
               Front

Condition B

               Back
       +--------------------+
       |                    |   
 USB-C [                    ] USB-C
 Left  |      Keyboard      | Right
 250GB [                    ] No expansion card
       |                    |
       |      Touchpad      |   
       |                    |
       +--------------------+
               Front

Condition A:

  1. Insert 250GB expansion card into the right front port.
  2. Run the nautilus.
  3. The “250 GB Volume” is detected and printed on the left menu of the nautilus GUI. Click the “250 GB Volume” on the menu.
  4. The df -hT command prints the result below.
    $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
...
/dev/sda1      vfat      233G   64K  233G   1% /run/media/jaruga/1A53-9E55
  5. Insert USB memory stick into the left front USB-A expansion card.
  6. The “JUNARUGA” (the volume name of the USB memory stick) is detected and printed on the left menu of the nautilus GUI. Click the “JUNARUGA” on the menu.
  7. The df -hT command prints the result below.
    $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
...
/dev/sda1      vfat      233G   64K  233G   1% /run/media/jaruga/1A53-9E55
/dev/sdb1      vfat      1.9G 1013M  900M  53% /run/media/jaruga/JUNARUGA
  8. Disconnect the “250 GB Volume” and “JUNARUGA” from the menu of the nautilus GUI. The df -hT doesn’t print both USB disk’s info.

Condition B

  1. Insert 250GB expansion card into the left front port.
  2. Run the nautilus.
  3. The “250 GB Volume” is NOT detected and NOT printed on the left menu of the nautilus GUI.

Questions

  • Why does the “250 GB Volume” (250GB expansion card) not detected in condition B? Is it a software or hardware problem?
  • Do you know how to detect the expansion card without the GUI filter app “nautilus” from the command line without sudo on Fedora?
  • What is the best practice to mount the disk expansion card on Fedora?

Addtional info

The tlp is enabled with the config file below.

/etc/tlp.conf

PCIE_ASPM_ON_BAT=powersupersave
USB_AUTOSUSPEND=0
2

Related to this thread, I am asking on the Ask Fedora forum about the USB external drives (disks) topic. - Detecting and mounting USB external drives with CLI - Ask Fedora

3

In both cases (A and B), does lsusb show the card?

4

Hi, thanks for the response Below is the result in both cases (A and B). In the case A, the lsusb showed the card. But in the case B, the lsusb didn’t show the card.

I executed the lsusb and udisksctl status commands that I just learned the command today.

Case (Condition) A

I inserted the 250GB expansion card into the right front port, and the USB memory stick into the left front USB-A expansion card. Both are not mounted at this state.

The lsusb showed the Bus 002 Device 002: ID 13fe:6500 Kingston Technology Company Inc. USB DISK 3.2 (maybe that is 250GB expansion card), and Bus 003 Device 005: ID 054c:0243 Sony Corp. MicroVault Flash Drive (= USB memory stick)

In the result of the udisksctl status the 250GB expansion card was detected as “sda”, and the memory stick was detected as “sdb”. The df -hT didn’t show the “sda” and “sdb” as these disks are not mounted.

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 005: ID 054c:0243 Sony Corp. MicroVault Flash Drive
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 13fe:6500 Kingston Technology Company Inc. USB DISK 3.2
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ udisksctl status
MODEL                     REVISION  SERIAL               DEVICE
--------------------------------------------------------------------------
WD_BLACK  SN750 2TB       112000WD  212348800457         nvme0n1 
USB DISK 3.2              PMAP      0700179D34878816     sda     
Sony Storage Media        0100      5A08072934737        sdb

Case (Condition) B

The lsusb didn’t show the 250GB expansion card.

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ udisksctl status
MODEL                     REVISION  SERIAL               DEVICE
--------------------------------------------------------------------------
WD_BLACK  SN750 2TB       112000WD  212348800457         nvme0n1

The journalctl -f showed the logs below.

$ journalctl -f
...
Nov 05 22:14:11 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:14:11 fedora kernel: usb usb3-port4: Cannot enable. Maybe the USB cable is bad?

In the case (condition) B, the journalctl -f printed the logs below. The tlperror log Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot. was appeared the in both cases A and B. So, maybe it’s not related to the undetected 250GB expansion card in case B. I am checking this post about the tlp error.

$ journalctl -f
Nov 05 22:25:56 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:00 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:04 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:07 fedora tlp[24002]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:07 fedora tlp[24002]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:07 fedora tlp[24002]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:07 fedora tlp[24002]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:07 fedora tlp[24002]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:07 fedora tlp[24002]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:08 fedora tlp[24035]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:08 fedora tlp[24035]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:08 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:08 fedora tlp[24035]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:08 fedora tlp[24035]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:08 fedora tlp[24035]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:08 fedora tlp[24035]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:08 fedora tlp[24067]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:08 fedora tlp[24067]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:08 fedora tlp[24067]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:08 fedora tlp[24067]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:08 fedora tlp[24067]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:08 fedora tlp[24067]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:09 fedora tlp[24100]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:09 fedora tlp[24100]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:09 fedora tlp[24100]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:09 fedora tlp[24100]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:09 fedora tlp[24100]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:09 fedora tlp[24100]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:10 fedora tlp[24133]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:10 fedora tlp[24133]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:10 fedora tlp[24133]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:10 fedora tlp[24133]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:10 fedora tlp[24133]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:10 fedora tlp[24133]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:11 fedora tlp[24166]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:11 fedora tlp[24166]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:11 fedora tlp[24166]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:11 fedora tlp[24166]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:11 fedora tlp[24166]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:11 fedora tlp[24166]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:11 fedora tlp[24198]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:11 fedora tlp[24198]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:11 fedora tlp[24198]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:11 fedora tlp[24198]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:11 fedora tlp[24198]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:11 fedora tlp[24198]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:12 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:12 fedora tlp[24230]: Error: conflicting power-profiles-daemon.service is enabled, power saving will not apply on boot.
Nov 05 22:26:12 fedora tlp[24230]: >>> Invoke 'systemctl mask power-profiles-daemon.service' to correct this!
Nov 05 22:26:12 fedora tlp[24230]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Nov 05 22:26:12 fedora tlp[24230]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Nov 05 22:26:12 fedora tlp[24230]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Nov 05 22:26:12 fedora tlp[24230]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Nov 05 22:26:16 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:20 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:24 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
Nov 05 22:26:28 fedora kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
5

Seeing the first comment on the [TRACKING] Linux battery life tuning, the tlp service is conflicted with the power-profiles-daemon.service.

I executed the commands below to suppress the error and warning. Then the tlp errors and warnings were suppressed.

$ sudo systemctl mask power-profiles-daemon.service
Created symlink /etc/systemd/system/power-profiles-daemon.service → /dev/null.

$ sudo systemctl mask systemd-rfkill.service
Created symlink /etc/systemd/system/systemd-rfkill.service → /dev/null.
6

Now the problematic logs are only below.

$ journalctl -f
...
Nov 07 20:10:29 fedora kernel: usb usb2-port3: attempt power cycle
Nov 07 20:10:30 fedora kernel: usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
Nov 07 20:10:32 fedora kernel: usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
Nov 07 20:10:32 fedora kernel: usb usb3-port4: attempt power cycle
Nov 07 20:10:39 fedora kernel: usb usb2-port3: attempt power cycle
Nov 07 20:10:40 fedora kernel: usb usb3-port4: Cannot enable. Maybe the USB cable is bad?
Nov 07 20:10:42 fedora kernel: usb usb2-port3: config error

Reading…

Edited: Reading the bug report about a similar issue in kernel org below, my next action can be that I will build the latest kernel, test it, and email the linux-usb@vger.kernel.org mailing list (the article).

201209 – Plugging Kingston USB Reader gives "Cannot enable. Maybe the USB cable is bad?"

All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release.