Qubes OS 4.01 & USB on Thinkpad T450s

[jerome moliere]

Hi all,
first of qll thqnks to the qubes team for this zonderful piece of code...
I started one week ago to migrate seriously to Qubes OS :
- LaTeX and emacs stuff works nicely
- Java runs well inside Stretch or Buster domains
- Thunderbird for my email works perfectly

But I have problems with USB sharing for embedded programming:
- from time to time , USB devices are not seen ( USB keys, hard drives or Freedom NXP KL46Z evaluation boards)
- sometimes I can access the device but once mounted inside the domain (embedded-dev domain running stretch) nothing happens , to pseudo device /dev/ttyACM0 to access it

==> In such case I am supposed to add an udev rule but where ? In my domain I guess? dom0 should be left as is...

I should add that graphical tooling does not work nicely for me:
- Copy/Paste between domains does not work
- USB device mounting does not work

Can you point me to log files , to help you improve QUbes OS...

For the moment, USB sharing is the last barrier befor being able to work mainly with Qubes...

Thanks for your feedbacks & help
Kind regards

[awokd]

jerome moliere:

> - from time to time , USB devices are not seen ( USB keys, hard drives or Freedom NXP KL46Z evaluation boards)
> - sometimes I can access the device but once mounted inside the domain (embedded-dev domain running stretch) nothing happens , to pseudo device /dev/ttyACM0 to access it
>
> ==> In such case I am supposed to add an udev rule but where ? In my domain I guess? dom0 should be left as is...

You could be right, but where are you reading that?

> I should add that graphical tooling does not work nicely for me:
> - Copy/Paste between domains does not work

Are you doing in source domain ctrl-c -> shift-ctrl-c -> in dest domain
shift-ctrl-v -> ctrl-v?

> - USB device mounting does not work

qvm-usb in dom0's terminal is most reliable, but some USB devices don't
like being remapped. If you can give up some protection and have a USB
controller to spare, try attaching it directly to your dev domain.

[jerome moliere]

Thqnks for the answer

On 5/31/19 5:40 PM, 'awokd' via qubes-users wrote:
> jerome moliere:
>
>> - from time to time , USB devices are not seen ( USB keys, hard
>> drives or Freedom NXP KL46Z evaluation boards)
>> - sometimes I can access the device but once  mounted inside the
>> domain (embedded-dev domain running stretch) nothing happens , to
>> pseudo device /dev/ttyACM0 to access it
>>
>> ==> In such case I am supposed to add an udev rule but where ? In my
>> domain I guess? dom0 should be left as is...
>
> You could be right, but where are you reading that?

In a standard Linux box I put some udev rule to be able to see the board
appears as a pseudo device attached on /dev/ttyACM0

You can find here a blog entry dealing with the KL25Z the small sister
from my board...(they are mostly the same)

>
>> I should add that graphical tooling does not work nicely for me:
>> - Copy/Paste between domains does not work
>
> Are you doing in source domain ctrl-c -> shift-ctrl-c -> in dest
> domain shift-ctrl-v -> ctrl-v?

Yes right, I have discovered that shift ctrl c was not properly
propagated so I remapped it to Meta V ...

But now copy does nothing.... The CLI method works ...

>
>> - USB device mounting does not work
>
> qvm-usb in dom0's terminal is most reliable, but some USB devices
> don't like being remapped. If you can give up some protection and have
> a USB controller to spare, try attaching it directly to your dev domain.

Do you mean attaching the USB controller directly ?

I can have a try why not?

I have 3 USB ports on this machine so no problem..


Thanks for the help

>
>

[jerome moliere]

Thanks, you are right but in my case no problem, just using the laptop
's keyboard no external one connected....

On 5/31/19 5:53 PM, awokd wrote:
> jerome moliere:

>
>> Do you mean attaching the USB controller directly ?
>>
>> I can have a try why not?
>>
>> I have 3 USB ports on this machine so no problem..
>

> Careful, ports aren't the same as controllers! If you only have one
> controller and are using a USB keyboard, you might lock yourself out.