Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - freelancehelp

Pages: [1] 2 3 4
1
General Help & Advice / Re: USB mount
« on: October 27, 2020, 09:01:43 pm »
Thanks, David.

After further investigation, I agree with what you say.

It now seems to me that the situation is as follows :-

Filesystems in /etc/fstab which have the noauto option are not automatically mounted at boot time, so if these filesystems are already
plugged into USB ports at boot time, they would subsequently have to be manually mounted in order to be used.

Filesystems which are plugged into a port after the system has been booted are automatically mounted.

2
General Help & Advice / USB mount
« on: October 27, 2020, 03:49:08 pm »
If a filesystem in /etc/fstab has a noauto entry, can that filesystem only be mounted manually using the mount command or
is there any chance that it will be automatically mounted by
usbmount ?

The filesystem is used in a USB port.

3
General Help & Advice / Opera browser not working
« on: October 01, 2020, 07:06:57 pm »
A version of the Opera browser has been working okay in a Debian Jessie system for about 9 months. Suddenly certain features no longer work :-

(1) Can't open attachments in emails, especially PDF attachments.

(2) Can't use ALT-P to clear cache/cookies

Can anyone explain why this has happened, please.

The version of Opera being used is

opera-stable_64.0.3417.73_amd64.deb

Is there an HTML problem now with this version ?

Does the Opera version need to be updated ?

If so, which version is suitable for Debian Jessie ?

4
Hardware Compatibility / Re: trouble with USB 3 port
« on: August 24, 2020, 06:38:03 pm »
 I am still struggling to solve the problem with the malfunctioning USB 3 port on a desktop
running Debian.

I would be very grateful if someone could please give useful answers to the following questions :-

 (1) Can the desktop be safely rebooted, if needed, given the USB 3 problem?

 (2) Can the USB 3 problem be fixed in some way or is the port now permanently
unavailable?

 (3) If the USB 3 port is unavailable, can the new portable hard drive be used to
     do a back-up of the system from the USB 2 port currently occupied by a card reader
     or is there any risk the card reader will be messed up again afterwards ?

     (On a previous occasion, a portable hard drive was plugged into this USB 2 port
      in place of the card reader. The system issued a message indicating the port was busy.
      The card reader was plugged back into the USB 2 port and it was then found that
      a card inserted into the card reader could not be mounted).

5
Could the problem with the USB port possibly cause a problem if an attempt is made to reboot the system ?

6
The xhci_hcd driver is present, but I now get the following problem :-

The new flash drive was unplugged from the USB 3 port.

As root, the following command was run

dmesg* |* tail


The output was :

[3974120.938338] usb 1-1: new high-speed USB device number 66 using xhci_hcd
[3974126.430777] usb 1-1: new high-speed USB device number 67 using xhci_hcd
[3974131.923271] usb 1-1: new high-speed USB device number 68 using xhci_hcd
[3974137.415713] usb 1-1: new high-speed USB device number 69 using xhci_hcd
[3974142.908184] usb 1-1: new high-speed USB device number 70 using xhci_hcd
[3974148.400664] usb 1-1: new high-speed USB device number 71 using xhci_hcd
[3974153.893132] usb 1-1: new high-speed USB device number 72 using xhci_hcd
[3974159.385762] usb 1-1: new high-speed USB device number 73 using xhci_hcd
[3974164.878067] usb 1-1: new high-speed USB device number 74 using xhci_hcd
[3974170.370558] usb 1-1: new high-speed USB device number 75 using xhci_hcd


Then the new flash drive was plugged back into the USB 3 port and then, again as root,
the following command was run

dmesg | tail -50

The output was as follows :

[3973945.175272] usb 1-1: new high-speed USB device number 34 using xhci_hcd
[3973950.667736] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[3973956.164234] usb 1-1: new high-speed USB device number 36 using xhci_hcd
[3973961.660705] usb 1-1: new high-speed USB device number 37 using xhci_hcd
[3973967.153175] usb 1-1: new high-speed USB device number 38 using xhci_hcd
[3973972.645644] usb 1-1: new high-speed USB device number 39 using xhci_hcd
[3973978.138108] usb 1-1: new high-speed USB device number 40 using xhci_hcd
[3973983.630571] usb 1-1: new high-speed USB device number 41 using xhci_hcd
[3973989.123038] usb 1-1: new high-speed USB device number 42 using xhci_hcd
[3973994.615532] usb 1-1: new high-speed USB device number 43 using xhci_hcd
[3974000.107987] usb 1-1: new high-speed USB device number 44 using xhci_hcd
[3974005.600444] usb 1-1: new high-speed USB device number 45 using xhci_hcd
[3974011.092914] usb 1-1: new high-speed USB device number 46 using xhci_hcd
[3974016.586439] usb 1-1: new high-speed USB device number 47 using xhci_hcd
[3974022.069876] usb 1-1: new high-speed USB device number 48 using xhci_hcd
[3974027.562378] usb 1-1: new high-speed USB device number 49 using xhci_hcd
[3974033.054785] usb 1-1: new high-speed USB device number 50 using xhci_hcd
[3974038.547262] usb 1-1: new high-speed USB device number 51 using xhci_hcd
[3974044.039723] usb 1-1: new high-speed USB device number 52 using xhci_hcd
[3974049.532213] usb 1-1: new high-speed USB device number 53 using xhci_hcd
[3974055.024682] usb 1-1: new high-speed USB device number 54 using xhci_hcd
[3974060.517132] usb 1-1: new high-speed USB device number 55 using xhci_hcd
[3974066.013620] usb 1-1: new high-speed USB device number 56 using xhci_hcd
[3974071.506102] usb 1-1: new high-speed USB device number 57 using xhci_hcd
[3974076.998569] usb 1-1: new high-speed USB device number 58 using xhci_hcd
[3974082.491021] usb 1-1: new high-speed USB device number 59 using xhci_hcd
[3974087.983486] usb 1-1: new high-speed USB device number 60 using xhci_hcd
[3974093.475956] usb 1-1: new high-speed USB device number 61 using xhci_hcd
[3974098.968439] usb 1-1: new high-speed USB device number 62 using xhci_hcd
[3974104.460916] usb 1-1: new high-speed USB device number 63 using xhci_hcd
[3974109.953390] usb 1-1: new high-speed USB device number 64 using xhci_hcd
[3974115.445836] usb 1-1: new high-speed USB device number 65 using xhci_hcd
[3974120.938338] usb 1-1: new high-speed USB device number 66 using xhci_hcd
[3974126.430777] usb 1-1: new high-speed USB device number 67 using xhci_hcd
[3974131.923271] usb 1-1: new high-speed USB device number 68 using xhci_hcd
[3974137.415713] usb 1-1: new high-speed USB device number 69 using xhci_hcd
[3974142.908184] usb 1-1: new high-speed USB device number 70 using xhci_hcd
[3974148.400664] usb 1-1: new high-speed USB device number 71 using xhci_hcd
[3974153.893132] usb 1-1: new high-speed USB device number 72 using xhci_hcd
[3974159.385762] usb 1-1: new high-speed USB device number 73 using xhci_hcd
[3974164.878067] usb 1-1: new high-speed USB device number 74 using xhci_hcd
[3974170.370558] usb 1-1: new high-speed USB device number 75 using xhci_hcd
[3974189.313961] usb 1-1: new high-speed USB device number 76 using xhci_hcd
[3974194.806428] usb 1-1: new high-speed USB device number 77 using xhci_hcd
[3974200.298916] usb 1-1: new high-speed USB device number 78 using xhci_hcd
[3974205.791363] usb 1-1: new high-speed USB device number 79 using xhci_hcd
[3974211.283830] usb 1-1: new high-speed USB device number 80 using xhci_hcd
[3974216.776300] usb 1-1: new high-speed USB device number 81 using xhci_hcd
[3974222.268794] usb 1-1: new high-speed USB device number 82 using xhci_hcd
[3974227.761269] usb 1-1: new high-speed USB device number 83 using xhci_hcd


Why is the above happening ?

7
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 ?

8
Hardware Compatibility / Re: trouble with USB 3 port
« on: August 08, 2020, 04:23:33 pm »
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 ?

9
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.


10
Hardware Compatibility / trouble with USB 3 port
« on: July 30, 2020, 10:05:36 am »
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.

11
The desktop is a custom build with a gigabyte motherboard.

I'm not sure offhand which particular board.

12
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.


13
Hardware Compatibility / light slowly flashing on external hard drive
« on: July 18, 2020, 09:18:23 am »
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.

14
General Help & Advice / Re: Can't mount external hard drive
« on: July 07, 2020, 10:46:29 am »
 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.

15
General Help & Advice / Can't mount external hard drive
« on: July 06, 2020, 11:22:08 am »
 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.

Pages: [1] 2 3 4

SimplePortal 2.3.3 © 2008-2010, SimplePortal