So followed the CLI instructions https://www.qubes-os.org/doc/pci-devices/qvm-pci gives the address of the usbcontroller to be detached dom0:00_.14.5 and tells the following:sys-2usb (no-strict-rest=True), sys-usb (no-strict-reset=true)
Because the linked Qubes instructions apparently only teach how to attach, but not how to detach
Hi Franz,
take a look to the `qvm-pci` man page, it explains how to detach.
take a look to the `qvm-pci` man page, it explains how to detach.
Many thanks it worked perfectly
On Sat, Jun 12, 2021 at 08:23:48AM -0300, Franz wrote:
> >
> >> take a look to the `qvm-pci` man page, it explains how to detach.
> >>
> >>
> >>
> > Many thanks it worked perfectly
> >
>
> It worked perfectly for a week or so, then the mouse stopped working.
> Thomas at Vikings, who built the D8 computer with preinstalled coreboot,
> says it should be a Qubes issue.
>
> How may I tell if it is a Qubes issue or a hardware issue?
> best
>
You aren't clear on what is happened here, because you haven't provided
sufficient detail..
Do you mean that you allocated a USB controller to a sys-usb, to use
with the mouse. After a week, the mouse stopped working.
When both controllers were attached to a single usb-qube the mouse
worked without interruption.
Is that the position?
Did the other USB qube continue to work?
If you type lsusb in the "mouse"-usb do you see the mouse attached?
If you attach another usb device, does lsusb and dmesg show the device
being attached?
If you attach the mouse to the *other* usb qube, does it appear there?
If you revert to a single usb qube, does the mouse work for more than a
week there?
If you move the mouse to the other controller, does the mouse work for
more than a week?
Let's think about this.
Many Qubes users will be using coreboot.
Many Qubes users will be using more than one usb qube.
Many Qubes users use a usb mouse for more than one week without
incident.
What is different about you? Coreboot, Your hardware.
I am not saying that your hardware is at fault - it's just that the most
likely source is *your configuration and hardware in Qubes*.
Of course, if Vikings can point to other users with your hardware and
coreboot build who use Qubes without a problem, that would help too.
I would prepare another usb mouse, that can work with the other usb
qube. Use your mouse-usb qube until it "breaks". Plug the mouse in to
the other usb qube, and start looking at the "broken" usb qube.
Look in logs, for any events that might be associated with the loss of
mouse. Remove and reinsert the broken mouse to see how it is handled.
Remove and reinsert other usb devices to see how they are handled.
journalctl, dmesg are your friends, as well as basic troubleshooting.
(Another mouse, use the other controller, etc)
> > Many thanks it worked perfectly
> >
>
> It worked perfectly for a week or so, then the mouse stopped working.
> Thomas at Vikings, who built the D8 computer with preinstalled coreboot,
> says it should be a Qubes issue.
>
> How may I tell if it is a Qubes issue or a hardware issue?
> best
>
You aren't clear on what is happened here, because you haven't provided
sufficient detail..
Do you mean that you allocated a USB controller to a sys-usb, to use
with the mouse. After a week, the mouse stopped working.
When both controllers were attached to a single usb-qube the mouse
worked without interruption.
Is that the position?Yes, but it worked also when only one USB controller was allocated to the mouse qube.
Did the other USB qube continue to work?yes it works, I am able to mount an external USB drive. Also lsusb works and shows the external USB driveIf you type lsusb in the "mouse"-usb do you see the mouse attached?No, lsusb hangs, with no output
.If you attach another usb device, does lsusb and dmesg show the device
being attached?dmesg on mouse qube gives a lot of errors, even various red ones. But I am totally unable to understand if they are serious or related to the mouse issue.
On Mon, Jun 21, 2021 at 11:22:01PM -0300, Franz wrote:
> >
> Other strange things happened:
> To restore a backup I connected an external USB disk with the backup to the
> second USB qube and under the restore command I clicked on the external USB
> disk to mount it. When I did that, a black background message on the upper
> right part of the screen told me that the disk was removed, while, at the
> same time it was NOT removed at all because the triangle showed that the
> disk was mounted and the content of the external USB disk was shown. Using
> my old and trusted x230 for many years this never happened. So I suppose it
> is strange.
>
> Also, the computer seems much slower than my old x230, which is strange
> being a new computer
>
> If you want me to try commands and report results, just ask, I am very
> willing to do anything that may be helpful to solve these problems.
> best
Hi Franz
Sorry for the radio silence. I'll dig in to the logs you provided in
the morning.
At this stage I would *seriously* be thinking of looking for a refund or
replacement - you simply shouldn't be having these issues with a new
computer, particularly if you had told them you would be running Qubes.
Is it possible for you to boot a live distro from USB and see if the
same issues exist?
--
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 qubes-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210701133325.GB26428%40thirdeyesecurity.org.
On Thu, Jul 1, 2021 at 10:33 AM Unman <un...@thirdeyesecurity.org> wrote:On Mon, Jun 21, 2021 at 11:22:01PM -0300, Franz wrote:
> >
> Other strange things happened:
> To restore a backup I connected an external USB disk with the backup to the
> second USB qube and under the restore command I clicked on the external USB
> disk to mount it. When I did that, a black background message on the upper
> right part of the screen told me that the disk was removed, while, at the
> same time it was NOT removed at all because the triangle showed that the
> disk was mounted and the content of the external USB disk was shown. Using
> my old and trusted x230 for many years this never happened. So I suppose it
> is strange.
>
> Also, the computer seems much slower than my old x230, which is strange
> being a new computer
>
> If you want me to try commands and report results, just ask, I am very
> willing to do anything that may be helpful to solve these problems.
> best
Hi Franz
Sorry for the radio silence. I'll dig in to the logs you provided in
the morning.Many thanks Unman. In the meantime I made other tests for the usb mouse thing and found a constant behaviour:
When the computer is cold, booting has about 50% chances of getting the mouse working when connected to the back USb ports and 25% chances when connected to the USB port in the middle of the board.
When the computer is warm there is no chance of getting the mouse working after booting.
Also I was able to get the files of dmesg and journalctl of the sys-usb VM when mouse works and when mouse does not work, and the red messages are quite different, even if i am unable to understand them.
At this stage I would *seriously* be thinking of looking for a refund or
replacement - you simply shouldn't be having these issues with a new
computer, particularly if you had told them you would be running Qubes.
Is it possible for you to boot a live distro from USB and see if the
same issues exist?
Is it possible for you to boot a live distro from USB and see if the
same issues exist?If I boot from a live Debian everything works. I tried 5 times one after the other and it was much faster and the mouse worked, immediately after tried Qubes and the mouse did not work. So it seems Qubes specific.