View previous topic :: View next topic |
Author |
Message |
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Sun Aug 09, 2020 9:23 pm Post subject: External USB 3.0 with ext4 problem on 5.4.48-gentoo-x86_64 |
|
|
I've problem with external USB 3.0 with ext4 problem on 5.4.48-gentoo-x86_64. I can't mount flash usb with ext4 partition.
On the same time, with FAT32 usb on this system all is ok. On 4.19.97-gentoo-x86_64 on this system with ext4 flash there were none of them. Ext4 flash drive works well on the other computer under 4.19.97-gentoo-x86_64 kernel as well.
So, now I have in dmesg:
Code: |
[ 548.774921] scsi 9:0:0:0: Direct-Access JetFlash Transcend 128GB 1100 PQ: 0 ANSI: 6
[ 548.775264] sd 9:0:0:0: Attached scsi generic sg9 type 0
[ 548.775823] sd 9:0:0:0: [sdi] 246841344 512-byte logical blocks: (126 GB/118 GiB)
[ 548.776274] sd 9:0:0:0: [sdi] Write Protect is off
[ 548.776278] sd 9:0:0:0: [sdi] Mode Sense: 43 00 00 00
[ 548.776729] sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 548.793822] sdi: sdi1
[ 548.795616] sd 9:0:0:0: [sdi] Attached SCSI removable disk
[ 579.886957] usb 4-4.3: Disable of device-initiated U1 failed.
[ 579.890418] usb 4-4.3: Disable of device-initiated U2 failed.
[ 580.203917] usb 4-4.3: reset SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[ 580.307337] usb 4-4.3: reset SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[ 580.330001] sd 9:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
[ 580.330007] sd 9:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 0e b6 7c 70 00 00 08 00
[ 580.330011] blk_update_request: I/O error, dev sdi, sector 246840432 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 608.854891] udevd[5154]: worker [5404] /devices/pci0000:00/0000:00:14.0/usb4/4-4/4-4.3/4-4.3:1.0/host9/target9:0:0/9:0:0:0/block/sdi is taking a long time
|
I've no systemd and no part of it (elogind as well is not in my system). If it matters...
Please help! |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54834 Location: 56N 3W
|
Posted: Sun Aug 09, 2020 10:25 pm Post subject: |
|
|
zerbino,
If UAS is in use, turn it off.
You may need to rebuild the kernel for that. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Mon Aug 10, 2020 5:48 am Post subject: |
|
|
NeddySeagoon wrote: | If UAS is in use, turn it off. You may need to rebuild the kernel for that. |
I've done that. I remove CONFIG_USB_UAS. Now there are no errors in dmesg when I plug in USB:
----
[ 11.467665] hub 3-13:1.0: USB hub found
[ 11.467686] hub 3-13:1.0: 4 ports detected
[ 108.847154] usb 4-4.3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 108.869625] usb 4-4.3: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00
[ 108.869628] usb 4-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 108.869631] usb 4-4.3: Product: Mass Storage Device
[ 108.869633] usb 4-4.3: Manufacturer: JetFlash
[ 108.869635] usb 4-4.3: SerialNumber: 08M8JWH1CZX3PKLO
----
But that's it. There are no USB sticks in fdisk list (ext4, fat32...), so I just cannot mount them anyway -- neither automount, nor udevil or just mount. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54834 Location: 56N 3W
|
Posted: Mon Aug 10, 2020 9:40 am Post subject: |
|
|
zerbino,
Your USB stick should be listed in dmesg like
Code: | [ 986.076021] usb 2-4: new high-speed USB device number 3 using ehci-pci
[ 986.233751] usb 2-4: New USB device found, idVendor=26bd, idProduct=9917, bcdDevice= 1.10
[ 986.233753] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 986.233755] usb 2-4: Product: USB DISK 3.0
[ 986.233756] usb 2-4: Manufacturer:
[ 986.233757] usb 2-4: SerialNumber: 07014540B3B25A85
[ 986.233874] usb-storage 2-4:1.0: USB Mass Storage device detected
[ 986.234020] scsi host11: usb-storage 2-4:1.0
[ 987.248909] scsi 11:0:0:0: Direct-Access USB DISK 3.0 PMAP PQ: 0 ANSI: 6
[ 987.248990] sd 11:0:0:0: Attached scsi generic sg11 type 0
[ 987.249671] sd 11:0:0:0: [sdj] 120933888 512-byte logical blocks: (61.9 GB/57.7 GiB)
[ 987.250293] sd 11:0:0:0: [sdj] Write Protect is off
[ 987.250296] sd 11:0:0:0: [sdj] Mode Sense: 2b 00 00 08
[ 987.250915] sd 11:0:0:0: [sdj] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 987.578001] sdj: sdj1
[ 987.580352] sd 11:0:0:0: [sdj] Attached SCSI removable disk |
The first line that you didn't post should have mentioned usb-storage.
Is the USB_STORAGE option on in your kernel?
I have it as a module
Code: | CONFIG_USB_STORAGE=m | but built in works too. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Mon Aug 10, 2020 11:29 am Post subject: |
|
|
NeddySeagoon wrote: | Is the USB_STORAGE option on in your kernel?
I have it as a module
Code: | CONFIG_USB_STORAGE=m | but built in works too. |
I've recompile kernel with following settings:
Code: |
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
# CONFIG_USB_UAS is not set
|
After reboot I've try to plugin FAT32 usb stick. Mounts ok.
Unplug it, plugin ext4 one. Same old deal. Can't mount it and there are errors in dmesg:
Code: |
[ 11.489859] hub 3-13:1.0: USB hub found
[ 11.489918] hub 3-13:1.0: 4 ports detected
[ 11.769612] scsi 8:0:0:0: Direct-Access Generic- USB3.0 CRW-CF/MD 1.00 PQ: 0 ANSI: 6
[ 11.777574] scsi 8:0:0:1: Direct-Access Generic- USB3.0 CRW-SD 1.00 PQ: 0 ANSI: 6
[ 11.785684] scsi 8:0:0:2: Direct-Access Generic- USB3.0 CRW-MS 1.00 PQ: 0 ANSI: 6
[ 11.786092] sd 8:0:0:0: Attached scsi generic sg6 type 0
[ 11.786311] sd 8:0:0:1: Attached scsi generic sg7 type 0
[ 11.786599] sd 8:0:0:2: Attached scsi generic sg8 type 0
[ 11.818996] sd 8:0:0:0: [sdf] Attached SCSI removable disk
[ 11.821391] sd 8:0:0:2: [sdh] Attached SCSI removable disk
[ 11.828620] sd 8:0:0:1: [sdg] Attached SCSI removable disk
[ 62.369124] usb 4-4.4: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 62.386852] usb 4-4.4: New USB device found, idVendor=13fe, idProduct=6300, bcdDevice= 1.10
[ 62.386856] usb 4-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 62.386858] usb 4-4.4: Product: USB DISK 3.0
[ 62.386860] usb 4-4.4: Manufacturer: Wilk
[ 62.386862] usb 4-4.4: SerialNumber: 07018AAEAD02AE53
[ 62.387762] usb-storage 4-4.4:1.0: USB Mass Storage device detected
[ 62.388018] scsi host9: usb-storage 4-4.4:1.0
[ 63.413804] scsi 9:0:0:0: Direct-Access Wilk USB DISK 3.0 PMAP PQ: 0 ANSI: 6
[ 63.414311] sd 9:0:0:0: Attached scsi generic sg9 type 0
[ 63.414419] sd 9:0:0:0: [sdi] 60567552 512-byte logical blocks: (31.0 GB/28.9 GiB)
[ 63.414682] sd 9:0:0:0: [sdi] Write Protect is off
[ 63.414684] sd 9:0:0:0: [sdi] Mode Sense: 45 00 00 00
[ 63.414919] sd 9:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 64.135730] sdi: sdi1
[ 64.136821] sd 9:0:0:0: [sdi] Attached SCSI removable disk
[ 64.262450] FAT-fs (sdi1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 76.165304] usb 4-4.4: USB disconnect, device number 4
[ 84.399342] usb 4-4.1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 84.421833] usb 4-4.1: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00
[ 84.421837] usb 4-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 84.421839] usb 4-4.1: Product: Mass Storage Device
[ 84.421841] usb 4-4.1: Manufacturer: JetFlash
[ 84.421843] usb 4-4.1: SerialNumber: 08M8JWH1CZX3PKLO
[ 84.424955] usb-storage 4-4.1:1.0: USB Mass Storage device detected
[ 84.425137] scsi host9: usb-storage 4-4.1:1.0
[ 85.884008] scsi 9:0:0:0: Direct-Access JetFlash Transcend 128GB 1100 PQ: 0 ANSI: 6
[ 85.884409] sd 9:0:0:0: Attached scsi generic sg9 type 0
[ 85.884860] sd 9:0:0:0: [sdi] 246841344 512-byte logical blocks: (126 GB/118 GiB)
[ 85.885317] sd 9:0:0:0: [sdi] Write Protect is off
[ 85.885321] sd 9:0:0:0: [sdi] Mode Sense: 43 00 00 00
[ 85.886484] sd 9:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 85.909490] sdi: sdi1
[ 85.911314] sd 9:0:0:0: [sdi] Attached SCSI removable disk
[ 115.935905] usb 4-4.1: Disable of device-initiated U1 failed.
[ 115.939400] usb 4-4.1: Disable of device-initiated U2 failed.
[ 116.252889] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 116.362901] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 116.388823] sd 9:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
[ 116.388828] sd 9:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 0e b6 7f 00 00 00 08 00
[ 116.388833] blk_update_request: I/O error, dev sdi, sector 246841088 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 116.862434] usb 4-4.1: Disable of device-initiated U1 failed.
[ 116.865887] usb 4-4.1: Disable of device-initiated U2 failed.
[ 117.189513] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 117.212204] sd 9:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 117.212210] sd 9:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 00 40 00 00 08 00
[ 117.212214] blk_update_request: I/O error, dev sdi, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 117.684653] usb 4-4.1: Disable of device-initiated U1 failed.
[ 117.688169] usb 4-4.1: Disable of device-initiated U2 failed.
[ 117.999533] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 118.022192] sd 9:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 118.022198] sd 9:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 00 10 00 00 08 00
[ 118.022202] blk_update_request: I/O error, dev sdi, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 145.961037] udevd[2267]: worker [4922] /devices/pci0000:00/0000:00:14.0/usb4/4-4/4-4.1/4-4.1:1.0/host9/target9:0:0/9:0:0:0/block/sdi is taking a long time
[ 150.069189] usb 4-4.1: Disable of device-initiated U1 failed.
[ 150.072691] usb 4-4.1: Disable of device-initiated U2 failed.
[ 150.386153] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 150.489530] usb 4-4.1: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 150.512347] sd 9:0:0:0: [sdi] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
[ 150.512366] sd 9:0:0:0: [sdi] tag#0 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00
[ 150.512370] blk_update_request: I/O error, dev sdi, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
|
|
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Mon Aug 10, 2020 8:29 pm Post subject: |
|
|
Oh. May be this helps, but all was broken down after last upgrade. Before it I've used udisks to automount.
There were a rules in /etc/udev/rules.d/
99-udisks2.rules:
Code: | ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1" |
and
Code: | 12-media-by-label-auto-mount.rules
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
# Import FS infos
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise specify one
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# Global mount options
#ACTION=="add", ENV{mount_options}="uid=1000,umask=022,dmask=0"
ACTION=="add", ENV{mount_options}="uid=1000,gid=1000,umask=022,dmask=0"
# Filesystem-specific mount options
#ACTION=="add", ENV{ID_FS_TYPE}=="ext2|ext3", ENV{MOUNT_OPTS}="defaults,nodiratime,noatime,commit=350"
ACTION=="add", ENV{ID_FS_TYPE}=="ext2|ext3", ENV{mount_options}="rw,nosuid,nodev,relatime,uhelper=udisks2"
#ACTION=="add", ENV{ID_FS_TYPE}=="vfat", ENV{mount_options}="$env{mount_options},codepage=866,iocharset=utf8"
ACTION=="add", ENV{ID_FS_TYPE}=="vfat", ENV{mount_options}="$env{mount_options},defaults,utf8"
ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", ENV{mount_options}="defaults,$env{mount_options}"
# Mount the device
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
# Exit
LABEL="media_by_label_auto_mount_end" |
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 23093
|
Posted: Tue Aug 11, 2020 11:05 pm Post subject: |
|
|
Are the working and non-working ports different types? Perhaps one is a USB3 port and one is a USB2 port, and that is why you get different results for each of them. If so, if we know what the working and non-working types are, we can determine how to adjust your configuration to fix this. Please show the output of lsusb with:- No relevant devices plugged in
- The device plugged in to a port that works as desired
- The device plugged in to a port that does not work as desired
Label each output accordingly. |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Wed Aug 12, 2020 8:12 am Post subject: |
|
|
Hu wrote: | Are the working and non-working ports different types? Perhaps one is a USB3 port and one is a USB2 port, and that is why you get different results for each of them.
|
The back port has a blue color (not the black one as two other back USB 2.0 ports), and I've take a look in manual to make sure of it. It is USB 3.0 definitely.
Output of lsusb with:
- No relevant devices plugged in
Code: |
Bus 003 Device 011: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 004 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 002: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W]
Bus 003 Device 010: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 004 Device 003: ID 0bda:0321 Realtek Semiconductor Corp. USB3.0 Card Reader
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 028: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 003 Device 009: ID 041e:3f04 Creative Technology, Ltd E-Mu 0404
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
The device plugged in to a port that works as desired
Code: |
Bus 003 Device 011: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 004 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 002: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W]
Bus 003 Device 030: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 003 Device 010: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 004 Device 003: ID 0bda:0321 Realtek Semiconductor Corp. USB3.0 Card Reader
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 028: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 003 Device 009: ID 041e:3f04 Creative Technology, Ltd E-Mu 0404
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
The device plugged in to a port that does not work as desired
Code: |
Bus 003 Device 011: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 002: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W]
Bus 004 Device 023: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 004 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 010: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 004 Device 003: ID 0bda:0321 Realtek Semiconductor Corp. USB3.0 Card Reader
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 028: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 003 Device 009: ID 041e:3f04 Creative Technology, Ltd E-Mu 0404
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
|
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 23093
|
Posted: Thu Aug 13, 2020 2:01 am Post subject: |
|
|
As I read that output, when the device works, it is plugged in to a USB 2.0 hub. When it fails, it is plugged in to a USB 3.0 hub. This suggests to me that your system cannot operate a USB mass storage device using USB3, but can when the device degrades to USB2 mode for compatibility with the older port. Is your kernel compiled with the required USB3 support, often called XHCI? |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
Posted: Thu Aug 13, 2020 3:08 pm Post subject: |
|
|
Hu wrote: | Is your kernel compiled with the required USB3 support, often called XHCI? |
Code: |
lsmod | grep hci
xhci_pci 20480 0
xhci_hcd 299008 1 xhci_pci
ahci 40960 6
libahci 40960 1 ahci
|
And kernel settings:#
Code: |
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=m
CONFIG_USB_XHCI_DBGCAP=y
CONFIG_USB_XHCI_PCI=m
CONFIG_USB_XHCI_PLATFORM=m
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not set
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_HCD_PCI=m
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_HCD_PLATFORM is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_U132_HCD is not set
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_HCD_ISO=y
# CONFIG_USB_SL811_CS is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_SSB is not set
# CONFIG_USB_HCD_TEST_MODE is not set
|
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54834 Location: 56N 3W
|
Posted: Thu Aug 13, 2020 7:16 pm Post subject: |
|
|
zerbino,
Please pastebin the output of for the working and non working case.
I want to check your USB bus device tree and power distribution.
is huge. It will not fit into a post. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
zerbino n00b
Joined: 10 Apr 2014 Posts: 13
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|