The Linux.uk Community Forum

I have now seen a number of cases where USB devices are not detected.

It seems that the xhci_hcd driver needs to be replaced/reinitialised.

Some of the posts recommend that the computer is completely powered down (I.e. all external devices are unmounted,
the computer is switched off and unplugged from the mains). After a wait of, say, up to 30 minutes, the computer is
rebooted. The xhci_hcd driver should be reinitialised by the reboot, so the USB 3 port should then work fine.

Other posts suggest that instead of a power down and reboot, the xhci_hcd driver could be disabled and then re-enabled
similar to suggestion in https://zedt.eu/tech/linux/restarting-usb-subsystem-centos/

Does anyone know which directory contains the xhci_hcd driver in Debian, please ?

The command fdisk  -l was run as root.

Please see the thread 'problem with USB 3 port' also in Hardware Compatibility' forum.

Other ports (which are all USB 2) cannot be tried at the moment as they are otherwise occupied.

I have a problem with a USB 3 port on a desktop running Debian Linux. The problem started when a system backup was attempted to a portable hard drive plugged into the USB 3 port. The backup operation had previously been done many times with no problems.

This time the mount operation failed with a message of the type 'can't find UUID=....'

Various commands such as fdisk -l showed that the kernel was not detecting the drive.

The drive was unplugged, then replug with a dmesg command issued straight after the replug.
The dmesg output seemed to indicate the portable hard drive itself had some problem.

A new portable hard drive was plugged into the port, but the kernel could not see the new drive, although a slowly flashing light on the drive indicated some power was reaching the hard drive.

I thought that perhaps the port was not supplying enough power to the drive, so I then plugged a new USB flash drive into the port. However the kernel would not recognise the flash drive.

Someone subsequently suggested that perhaps the power pins of the port were working but not the data pins.
This could perhaps be due to a problem with the port's USB header or associated cabling or possibly due to damage to
the host controller or associated wiring.

Any thoughts on this, please.

The desktop is a custom build with a gigabyte motherboard.

I'm not sure offhand which particular board.

The command fdisk -l has already been tried. Also lsusb has been run. In neither case was the hard drive listed,
so the system doesn't see it.

There have been previous problems with the particular USB port, whereby it seemed that another, older hard drive
was suffering hardware problems. Hence the switch to a new hard drive.

The operating system is Debian Jessie (yes, I know it is outdated - a desktop with Buster is to be set up shortly).

The hard drive needs to be used to backup the current system so that relevant files can be transferred to the
new system.

The new hard drive is a WD Elements portable hard drive.

I am beginning to wonder whether the slowly flashing light means the hard drive has been put into standby mode.
This suggests to me that this particular USB port may be low on power and thus cannot power the hard drive properly.

Other USB ports seem to work okay.


The new drive is a portable drive so the USB port should be able to power it.

A new WD Elements portable hard drive has been plugged into a USB 3 port on a Linux desktop.

The hard drive does not appear on an fdisk -l
listing. The small light on the drive is slowly flashing.

What is happening ? Why doesn't the drive appear in the fdisk listing ?

Is the system trying to automatically mount the hard drive ?

Is the USB port underpowered ?

I hesitate to unplug the hard drive while the light is flashing in case this corrupts the filesystem
on the hard drive.

 The hard drive was inserted into another USB port to see whether the first port was faulty.

A card reader had to be removed from its USB port so that the external hard drive could be inserted into that port.

An attempt was then made to mount the hard drive, but the
following happened :-

# mount /media/backup
Failed to write lock '/dev/sde1': Resource temporarily unavailable
Error opening '/dev/sde1': Resource temporarily unavailable
Failed to mount '/dev/sde1': Resource temporarily unavailable

The hard drive was then put back into its original USB port.

The card reader was reinserted into its USB port and an
attempt
was made to mount the card reader but nothing at all happened - there was no message at all.

Can anyone please help to sort this out.

 An external USB hard drive has been used for a number of years to regularly
archive data on a Linux Debian system. The latest attempt to archive data
gave the following error :-

mount /media/backup
mount : can't find UUID=0688802088800FFB

Why does this error occur and how is it fixed ?

Thanks.

Has anyone successfully used an AMD Ryzen 5 3600 in an MSI B450 TOMAHAWK MAX using the stable
release of Debian 10 as the operating system ??

Various reports have led me to believe that third generation AMD Ryzen CPUs will work okay with the stable release
of Buster, so I am trying to arrange the build of a desktop with the stable release of Buster as the operating system.

I aim to use the AMD Ryzen 5 3600 as the CPU and the MSI X570-A PRO as the motherboard.

However i was recently given the following information by an MSI user about the MSI X570-A PRO :-

"See the following link :-

https://community.amd.com/servlet/jiveservlet/downloadimage/2-2975897-167843/MSI_X570-PRO.png. png
As you can see, according to the above link, the BIOS offered by MSI is still Beta, not the final version of
AGESA 1.0.0.5

AGESA 1.0.0.6 is usually the final version that ends the cycle for every Ryzen generation so its a reference
approach has been so for 1st and 2nd Ryzen generations) offering stability regardless of using 2000 or
3000 series.

Also the BIOS should be flashed to AGESA 1.0.0.6 end of 2018 by the seller before the computer is bought"

I have further been informed that the X570 board and Ryzen 3000 series came out about the same time as
the stable release of Buster I.e. July 2019

As mentioned at the beginning of this email, various reports have convinced me that the Ryzen 5 3600 CPU
will work okay with the stable release of Buster. But the MSI X570-A PRO motherboard and its BIOS may have
a serious issue with Buster. Indeed the motherboard may fail to boot.

So I am rather concerned about the stability offered by the BIOS on the MSI X570-A PRO motherboard.

I have just seen the article :-

https://www.phoronix.com/scan.php?page=article&item=3900x-linux-distros&num=1

This shows Debian 10.0 working okay with a Ryzen 9 3900X CPU.

I am puzzled as I thought that the stable release of Debian 10 has problems with third generation Ryzen CPUs.

Any thoughts about this ?

I am trying to get a desktop built with Debian Buster as the operating system.

I am thinking of using a motherboard which has the Realtek 8111H lan controller.

However I have heard that this controller causes problems with Linux.

Can anyone help, please ?

I have discovered that the two CPUs I mentioned are no longer available.

I have now decided to install a third generation Ryzen CPU.

I intend to install the latest stable Buster 4.19 kernel. I would then install the latest back port Buster kernel (5.5 or 5.6).
Then I would see which kernel works best with the Ryzen CPU. I understand that I can choose which kernel to boot using the Advanced Options in
the Grub boot loader. Would this work okay ?

The desktop will be used for office work, not for gaming.

I am deciding between the Ryzen 3 3300X and Ryzen 5 3600 and between the MSI B450-A PRO and the MSI B450 TOMAHAWK.

Many thanks for your replies. I do not understand the inner workings of Debian, so I wish to stick to
using the standard stable version of Buster.

Will the AMD Ryzen 5 2500X and AMD Ryzen 5 2600E work okay with the stable release without any real problem ?

Hi.

Can anyone please answer the following questions :-

(1) Will Debian Buster run okay with Intel 9th generation CPUs ?

(2) Will Debian Buster run okay with AMD Ryzen 3 CPUs ?

(3) Will Debian Buster run okay with AMD Ryzen 5 CPUs ?

Thanks.