-------- Original Message --------
Subject: Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections
Date: 04.01.2020 19:14
From: [email protected]
To: awokd <[email protected]>

On 04.01.2020 10:51, 'awokd' via qubes-users wrote:
Lorenzo Lamas:

On Friday, January 3, 2020 at 11:02:24 PM UTC+1, [email protected] wrote:

But the other problem I've had with sys-usb is connecting to external
drives. Here are the copy speeds I get on my machine to an external usb
device:

Tails OS 33mb/sec
Qubes OS 12mb/sec

This is my hardware: https://www.coreboot.org/Board:asus/kgpe-d16

Try adding irqpoll to the end of your kernelopts in qvm-prefs sys-usb.
Had similar behavior with my Corebooted AMD. Please let me know if it
helps you. I think root cause is IRQ setup table issues in Coreboot, but
I'm not sure yet how to confirm or fix.


Unfortunately it doesn't seem to have changed anything. My kernel opts are currently set to:

dom0] qvm-prefs sys-usb
...
kernelopts            -  nopat iommu=soft swiotlb=8192 irqpoll
...

I rebooted sys-usb and am trying to copy a backup to an external USB drive and getting the same pauses and low transfer rates (if not worse actually).

    253,591,552   0%  249.48kB/s  181:19:51  ^C
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(644) [sender=3.1.3]
[sender] io timeout after 60 seconds -- exiting


Thanks for the suggestion though.

When it is not recognizing devices, the Qubes Devices Widget shows an
additional device: "sys-usb:2-1:1 - 138a_003c_0030009d7e88". It is not
visible when everything works fine. Do you have that as well?


Lorenzo Lamas:

I do not get this 'ghost' device. I either get none or a partial list of what should be there.

But that is promising that your USB 3.0 works fine, maybe I should try installing an additional USB card. I currently have the onboard usb slots on the motherboard and a couple built into my case. They seem to behave similarly. Though in the past sometimes switching between them I could get things to show up. That was back on Qubes 3.2 though and have found rebooting to be the more effective solution when things aren't recognized at all.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a5df2d4744464d972a1c67e90d7da69e%40posteo.net.

Reply via email to