[qubes-users] Trying to connect phone to Qubes os(4.0)

[Tae Hwan Kim]

Hi.
I am trying to connect my android phone to my work vm in qubes os. So I 
tried this.

1. Changed AppVM(work) to HVM because PVH mode no PCI passthrough which I 
am trying to do.
2. 
lsusb

Bus 001 Device 002: ID 1004:61f9 LG Electronics
3. And then I did 
readlink  /sys/bus/usb/devices/usb1

and it returned
../../../devices/pci:00/:00:14.0/usb1

4. finally
qvm-pci attach --persistent work dom0:00_14.0

But it says "empty response" and doesn't work.
I followed this step .
Am I doing right? In the result of lsusb says my usb connected in Bus 001 
so I did 

readlink /sys/bus/usb/devices/usb1 instead of usb3(in document). Did I do it 
correctly?

In final step I just changed : to _ like 00:14.0 to 00_14.0. 
I tried dom0:00:14.0 but doesn't work

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6e1fa3e5-e58f-4a68-b115-ac50c2e8bbc4%40googlegroups.com.

Re: [qubes-users] Re: has google- chrome slowed down for anyone else?

[pixel fairy]

On Mon, Dec 16, 2019 at 10:44 AM pixel fairy  wrote:

>
>
> On Saturday, December 14, 2019 at 4:05:12 AM UTC-8, Daniil Travnikov wrote:
>>
>> Actually the same problem I have in Brave Browser which use chromium.
>>
>> Try this:
>> 1. Open chrome://flags
>> 2. Change 'Override software rendering list' on 'Enabled'.
>>
>
> Thanks. seemed slightly better, but the problems still there. glad theres
> other browsers
>

i take that back, its much better, but still a little there.

>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CACr%3DtZfdrazd4ppkiARu-fAoqjZVt0Zi5cw4kr7xG3StvFe_EA%40mail.gmail.com.

[qubes-users] Qubes freezes during installation process

[Slightly Different]

Hi Qubes users,

A few days ago I came across Qubes and after I did my research, I decided that 
I want to use Qubes.

Therefore I have had a look at the installation guide. The pre-installation 
part was peanuts, I finished that.

However during doing the installation part itself, I faced a problem that I 
can't solve by myself.

To understand the problem I need to give you some context.

I downloaded Qubes-R4.0.1-x86_64.iso from 
https://www.qubes-os.org/downloads/#qubes-release-4-0-1 and used rufus-3.8.exe 
to burn the ISO file on an empty 64GB USB flash drive.

After that I rebooted my computer, started it in BIOS mode and made sure to run 
the iso file from the 64GB USB flash drive. 

Qubes OS boots up for the first time and I selected "Test this media & install 
Qubes R4.0.1"

After that I saw some command lines and then I saw the welcome screen. 

But it said "WELCOME TO QUBES R4.0.2-rc3" instead of R4.0.1

In that same welcome screen I set English (United States) as language during 
the installation process.

I hit the continue button and after that nothing happened. It looked like it is 
frozen. I waited a while, way longer than what the installation guide 
incidated, but it still doesn't do anything.

Hopefully you can help me to solve this problem.

Please don't hesitate tell me if there's anything that isn't clear for you. I 
will try to elaborate on it.

P.S. English isn't my main language so please forgive me if I've made any 
grammar mistakes ;)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e2df70e8-7eaf-410f-8445-8085ed283d90%40googlegroups.com.

Re: [qubes-users] Soundquality

[Claudia]

Myros:

Hello,

I'm a relatively new user and not very fit at this.
Windows and Ubuntu i had before could handle the sound very good, but since
i installed Qubes it sounds like a metal bin.

Any suggestions what i can do?

Greez Myros


What soundcard do you have? And what driver is it using?

Open a dom0 terminal and run 'lspci -k'. Also run 'aplay -l'.

There are some settings you can tweak in alsa generally, with regardless 
of driver/hardware. For example, run 'alsamixer' in dom0 terminal, and 
make sure "gain" is zero. Other settings are specific to your exact 
hardware or driver. For example, if your driver is snd_hda_intel, 
setting the model= parameter or enable_msi=0 can sometimes help.


Does it sound okay in a Fedora 25 live CD?

If this is a new-ish machine, upgrading the kernel might help. 
https://www.qubes-os.org/doc/software-update-dom0/#kernel-upgrade


Here are some links that might be helpful.
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Audio_Quality
https://help.ubuntu.com/community/HdaIntelSoundHowto#Choosing_Your_Model
https://www.kernel.org/doc/html/latest/sound/hd-audio/notes.html
https://wiki.parabola.nu/Advanced_Linux_Sound_Architecture#Unmuting_the_channels
https://wiki.parabola.nu/Advanced_Linux_Sound_Architecture#High_quality_resampling
https://wiki.parabola.nu/Advanced_Linux_Sound_Architecture#Poor_sound_quality_or_clipping

-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/74d61465-8a1b-1de0-64d0-61c622532a15%40vfemail.net.

Re: [qubes-users] wipe released diskspace of a disposable VM's

[Claudia]

brendan.h...@gmail.com:

Disposable VMs were not developed with anti-forensics in mind (e.g. no 
protection in jurisdictions where you can be forced to hand over your drive 
password
Never thought about it, but that makes sense. I can see how it would be 
easy to confuse "non-persistence of malware" aspect and the 
"non-persistence (non-remenance) of data" aspect, though.


But then... What does the checkbox mean, "Keep dispVM in memory", under 
global settings (R3.2, at least)? Screenshot attached.



That being said...

In 4.0 (updated) qubes now calls blkdiscard on volumes being removed before 
invoking lvremove. If you happen to use a SED SSD and you have manually enabled 
discards through all layers to the physical drive, then, depending on the 
manufacturer implementation, the data from a shutdown disposable VM might not be 
recoverable even with your disk password. >
No guarantee but I recommend enabling discards all the way down.

After some forensics experiments, I put together a rough-at-the-edges bash 
script that does a rather good job of ensuring the volumes are not recoverable.

It creates an over-provisioned lvm volume In the current pool, overlays a new 
randomly keyed luks volume on top, makes that into an lvm pv, layers lvm vg and 
finally an lvm thin pool on top.

Adds that new thin pool to qvm-pools, copies templates and VMs there, 
temporarily modifies the global default pool setting (needed to be sure *all* 
volumes related to the VMs were in the ephemeral pool) and starts up some 
sessions.

I need to make it a bit more flexible but it served my need.

Once all started VMs are shut down, the script unwinds all the storage layers.

Since the luks layer was random keyed, that data is gone once unmounted.

Been meaning to clean it up and share at some point.

Brendan




I sort of like the idea mentioned in bug #904, about doing the crypto 
inside the dispVM itself, so that 1) the key is scrubbed by Xen when the 
dispVM is shut down, and 2) data is non-recoverable instantly so you 
don't have to wait until all dispVMs have been shut down for example. 
Incidentally this approach actually offers a lot of improvement in 
scenarios where the machine is seized while it's on and unlocked, too, 
but that's another topic.


That being said, do you think it's currently possible to set up a dispVM 
template so dispVMs run off encrypted storage? I'm thinking maybe a 
startup script that overwrites /dev/xvdc (volatile.img) with a dm-crypt 
container? Or perhaps it could be done at the filesystem level instead, 
with ecryptfs or encfs using random keys, and dm-crypt for swap? Or even 
just disable swap and mount a tmpfs over /home, if you have have enough 
ram or don't write much data in dispVMs.


Just bouncing around some ideas. Seems like it might be possible to do 
something like that, and perhaps simpler than the ephemeral pool 
approach, depending on your situation. Thoughts?



-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/82fee1d4-92d1-9dbf-3b25-d40f14a67317%40vfemail.net.

[qubes-users] Soundquality

[Myros]

Hello,

I'm a relatively new user and not very fit at this.
Windows and Ubuntu i had before could handle the sound very good, but since 
i installed Qubes it sounds like a metal bin.

Any suggestions what i can do?

Greez Myros

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/79876191-86e9-4e38-8edf-92c84730e44b%40googlegroups.com.

[qubes-users] Has anyone a intel Wi-Fi 6 AX200 working in sys-net (fedora/debian)?

[Axel Schöner]

Hi,

 

 

i'm trying to get my Wifi working AX200 in a Gigabyte Aero15 (Clevo barebone).

I didn't get it running also with newer kernels 5.3.11 and 5.4.

 

In dmesg i see the following:


4.106832] iwlwifi :00:06.0: Failed to configure RX queues: -5
[    4.108379] iwlwifi :00:06.0: Firmware not running - cannot dump
error
[    4.132303] iwlwifi :00:06.0: Applying debug destination
EXTERNAL_DRAM
[    4.301597] iwlwifi :00:06.0: FW already configured (0) -
re-configuring
[    4.502163] iwlwifi :00:06.0: Microcode SW error detected.
Restarting 0x200.
[    4.502310] iwlwifi :00:06.0: Start IWL Error Log Dump:
[    4.502324] iwlwifi :00:06.0: Status: 0x0090, count: 6
[    4.502340] iwlwifi :00:06.0: Loaded firmware version: 48.4fa0041f.0
[    4.502356] iwlwifi :00:06.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
[    4.502372] iwlwifi :00:06.0: 0x22F0 | trm_hw_status0
[    4.502387] iwlwifi :00:06.0: 0x | trm_hw_status1
[    4.502402] iwlwifi :00:06.0: 0x004F8E3C | branchlink2
[    4.502415] iwlwifi :00:06.0: 0x004E4FF4 | interruptlink1
[    4.502430] iwlwifi :00:06.0: 0x004E4FF4 | interruptlink2
[    4.502445] iwlwifi :00:06.0: 0x00016FF4 | data1
[    4.502458] iwlwifi :00:06.0: 0x1000 | data2
[    4.502470] iwlwifi :00:06.0: 0xF008 | data3
[    4.502483] iwlwifi :00:06.0: 0x | beacon time
[    4.502496] iwlwifi :00:06.0: 0x00054309 | tsf low
[    4.502508] iwlwifi :00:06.0: 0x | tsf hi
[    4.502522] iwlwifi :00:06.0: 0x | time gp1
[    4.502535] iwlwifi :00:06.0: 0x0005A48B | time gp2
[    4.502547] iwlwifi :00:06.0: 0x0001 | uCode revision type
[    4.502563] iwlwifi :00:06.0: 0x0030 | uCode version major
[    4.502579] iwlwifi :00:06.0: 0x4FA0041F | uCode version minor
[    4.502613] iwlwifi :00:06.0: 0x0340 | hw version
[    4.502628] iwlwifi :00:06.0: 0x18C89000 | board version
[    4.502644] iwlwifi :00:06.0: 0x801EF500 | hcmd
[    4.502656] iwlwifi :00:06.0: 0x0002 | isr0
[    4.502668] iwlwifi :00:06.0: 0x | isr1
[    4.502681] iwlwifi :00:06.0: 0x08F2 | isr2
[    4.502693] iwlwifi :00:06.0: 0x00C1FFCC | isr3
[    4.502706] iwlwifi :00:06.0: 0x | isr4
[    4.502718] iwlwifi :00:06.0: 0x | last cmd Id
[    4.502731] iwlwifi :00:06.0: 0x00016FF4 | wait_event
[    4.502744] iwlwifi :00:06.0: 0x | l2p_control
[    4.502757] iwlwifi :00:06.0: 0x | l2p_duration
[    4.502770] iwlwifi :00:06.0: 0x | l2p_mhvalid
[    4.502783] iwlwifi :00:06.0: 0x | l2p_addr_match
[    4.502798] iwlwifi :00:06.0: 0x0009 | lmpm_pmg_sel
[    4.502811] iwlwifi :00:06.0: 0x | timestamp
[    4.502823] iwlwifi :00:06.0: 0x0828 | flow_handler
[    4.502888] iwlwifi :00:06.0: Start IWL Error Log Dump:
[    4.502901] iwlwifi :00:06.0: Status: 0x0090, count: 7
[    4.502916] iwlwifi :00:06.0: 0x2034 | NMI_INTERRUPT_WDG
[    4.502931] iwlwifi :00:06.0: 0x | umac branchlink1
[    4.502946] iwlwifi :00:06.0: 0xC008CC3C | umac branchlink2
[    4.502961] iwlwifi :00:06.0: 0x8048E6D8 | umac interruptlink1
[    4.502977] iwlwifi :00:06.0: 0xC00869FC | umac interruptlink2
[    4.502992] iwlwifi :00:06.0: 0x0004 | umac data1
[    4.503004] iwlwifi :00:06.0: 0xC00869FC | umac data2
[    4.503017] iwlwifi :00:06.0: 0x | umac data3
[    4.503029] iwlwifi :00:06.0: 0x0030 | umac major
[    4.503042] iwlwifi :00:06.0: 0x4FA0041F | umac minor
[    4.503055] iwlwifi :00:06.0: 0x0005A47F | frame pointer
[    4.503070] iwlwifi :00:06.0: 0xC08869A8 | stack pointer
[    4.503085] iwlwifi :00:06.0: 0x0009050D | last host cmd
[    4.503100] iwlwifi :00:06.0: 0x | isr status reg
[    4.503127] iwlwifi :00:06.0: Fseq Registers:
[    4.503146] iwlwifi :00:06.0: 0xE101 | FSEQ_ERROR_CODE
[    4.503168] iwlwifi :00:06.0: 0x00290006 | FSEQ_TOP_INIT_VERSION
[    4.503191] iwlwifi :00:06.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[    4.503214] iwlwifi :00:06.0: 0xA503 | FSEQ_OTP_VERSION
[    4.503237] iwlwifi :00:06.0: 0x8003 | FSEQ_TOP_CONTENT_VERSION
[    4.503260] iwlwifi :00:06.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[    4.503283] iwlwifi :00:06.0: 0x00100530 | FSEQ_CNVI_ID
[    4.503302] iwlwifi :00:06.0: 0x0532 | FSEQ_CNVR_ID
[    4.503321] iwlwifi :00:06.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[    4.503346] iwlwifi :00:06.0: 0x0532 | CNVR_AUX_MISC_CHIP
[    4.702303] iwlwifi :00:06.0: 0x05B0905B |
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    4.702330] iwlwifi :00:06.0: 0x025B |
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    4.702447] iwlwifi :00:06.0: Firmware error during
reconfiguration - reprobe!
[    4.702559] iwlwifi :00:06.0: FW error in SYNC CMD
RFH_QUEUE_CONFIG_CMD
[    

[qubes-users] Re: has google- chrome slowed down for anyone else?

[pixel fairy]

On Saturday, December 14, 2019 at 4:05:12 AM UTC-8, Daniil Travnikov wrote:
>
> Actually the same problem I have in Brave Browser which use chromium.
>
> Try this:
> 1. Open chrome://flags
> 2. Change 'Override software rendering list' on 'Enabled'.
>

Thanks. seemed slightly better, but the problems still there. glad theres 
other browsers

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b50d3fbb-43ef-4f30-9602-7c134690a615%40googlegroups.com.