[qubes-users] HCL - MSI-GP72-6QE Leopard Pro

[A Luciani]

-- 
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/CANRmXeo_f2-dZKam86MnYqEYDY3GHUx1mS4nsdcG1bbsAaxqxA%40mail.gmail.com.


Qubes-HCL-Micro_Star_International_Co___Ltd_-GP72_6QE-20210401-040340.yml
Description: Binary data


Qubes-HCL-Micro_Star_International_Co___Ltd_-GP72_6QE-20210401-040340.cpio.gz
Description: application/gzip

Re: [qubes-users] HCL - MSI-GP72-6QE Leopard Pro

[Sven Semmler]

Thank you A. Luciani for your HCL report!

Since you haven't provided any notes/comments I assume everything works 
for you?


Your HCL report is now part of this pull request:

https://github.com/QubesOS/qubes-hcl/pull/57

... and will be visible on the website soon!

/Sven

--
 public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

--
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/2fcda5c4-eb02-58ef-e08e-c1b9cd95d238%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Re: How to build Qubes with patches from Xen ?

[Josef Johansson]

Hi,

You should take my words with a grain of salt since I'm doing this the 
first time around. But anyhow.

Go to https://www.qubes-os.org/doc/qubes-iso-building/ and make sure you 
have a Fedora  VM to download everything to, and plenty of space.

Download a builder.conf file from 
https://github.com/QubesOS/qubes-release-configs/blob/master/R4.0/qubes-os-iso-full-online.conf
 
(or 4.1 if that's the version you are building)

In that file, add vmm-xen under COMPONENTS

run
make remount
make install-deps
make get-sources

Now, go into qubes-src/vmm-xen and add you patch as a file.
Enter xen.spec.in and add your patch-file under upstreamable, you'll notice 
the pattern.

Go back to qubes-builder and run make vmm-xen, and the rest of the entries 
in $COMPONENTS in builder.conf.

( At this point you have rpm-files inside chroot-* in qubes-builder that 
you actually could install in dom0 instead of building a full ISO. )

run
make iso

please note that it will take a while.

On Friday, 26 March 2021 at 01:18:01 UTC+1 Zophikel wrote:

>
> Yesterday I filed an issue regarding hardware support for my HPZ800 and 
> Nehalem era cpu’s I was wondering how to build a custom qubes image/iso 
> where the following xenpatch 
> is
>  
> included ?

-- 
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/7ddd3180-2d4b-4060-bda3-a4a3d41aef68n%40googlegroups.com.

[qubes-users] Re: Poor battery life running Qubes

[Josef Johansson]

Hi,

Just curious, is xen-acpi-processor module loaded in dom0 (lsmod / modprobe 
xen-acpi-processor) and what does xenpm get-cpufreq-para tell you?

On Monday, 29 March 2021 at 16:07:53 UTC+2 jonath...@gmail.com wrote:

> Hi there
>
> I've been using Qubes for about 18 months now, and it's great. My only 
> complaint is the poor battery life I get. I've followed various 
> recommendations within qubes-users about using powertop and tlp, but 
> nothing seems to address the rapid decline in power I experience when 
> running on battery. 
>
> Some system information:
>
> Kernel Version Linux version 5.4.88-1.qubes.x86_64
> System Name PurismLibrem 15 v44.0 (Pureboot)
> CPU Information 2 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
> OS Information Qubes release 4.0 (R4.0) 
>
> Probably the biggest clue I have received was from running tlp stat, which 
> suggests:
>
> "Reconfigure your Linux kernel with PM_RUNTIME=y to reduce your laptop's 
> power consumption."
>
> This seems to be reinforced by the following output from powertop:
>
> Untunable Software Issues
> Description
> I2C Adapter i2c-3 has no runtime power management
> I2C Adapter i2c-4 has no runtime power management
>
> Optimal Tuned Software Settings
> Description
> NMI watchdog should be turned off
> Enable SATA link power management for host0
> Enable SATA link power management for host1
> Enable Audio codec power management
> Runtime PM for I2C Adapter i2c-1 (i915 gmbus dpb)
> Runtime PM for I2C Adapter i2c-2 (i915 gmbus dpd)
> Runtime PM for I2C Adapter i2c-0 (i915 gmbus dpc)
> Runtime PM for I2C Adapter i2c-5 (SMBus I801 adapter at efa0)
> Runtime PM for PCI Device Samsung Electronics Co Ltd Device a808
> Runtime PM for PCI Device Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
> Gen Core Processor Thermal Subsystem
> Runtime PM for PCI Device Qualcomm Atheros AR9462 Wireless Network Adapter
> Runtime PM for PCI Device Intel Corporation Device 9d24
> Runtime PM for PCI Device Intel Corporation Device 9d30
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP HD Audio
> Runtime PM for PCI Device Intel Corporation Xeon E3-1200 v6/7th Gen Core 
> Processor Host Bridge/DRAM Registers
> Runtime PM for PCI Device Intel Corporation Device 9d4e
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP Thermal 
> subsystem
> Runtime PM for PCI Device Intel Corporation HD Graphics 620
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
> Controller
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP SMBus
> Runtime PM for PCI Device Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 
> v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP PCI Express 
> Root Port #5
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP PMC
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP SATA 
> Controller [AHCI mode]
> Runtime PM for PCI Device Intel Corporation Sunrise Point-LP PCI Express 
> Root Port #9 
>
> Looking at 
> https://github.com/QubesOS/qubes-linux-kernel/blob/master/config-base, I 
> can see CONFIG_PM_RUNTIME is absent from the config. I'm willing to try 
> recompiling the Linux kernel for Qubes with PM_RUNTIME=y, but my 
> understanding is that I would need to set up a VM running Fedora 25. Before 
> I head down that rabbit hole, I wanted to ask if anyone had experienced 
> similar problems and tried this solution. Further, is there a reason that 
> flag is not currently included in the base config?
>
> Thanks in advance,
>
>
> Jonathan
>
>

-- 
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/f30fb136-4fa5-43ed-8fb1-be66e47a0158n%40googlegroups.com.

Re: [qubes-users] Networking issue with sys-whonix, missing vif*

[Josef Johansson]

Hi,

As another data point:
This is happening in debian-10 as well. However not in debian-11.

On Friday, 19 March 2021 at 20:24:57 UTC+1 awokd wrote:

> Vladimir Lushnikov:
> > Hello,
> > 
> > Since updating to latest Whonix 15/Qubes R4.1, I am having issues with
> > sys-whonix not bringing up the virtual interfaces for downstream VMs
> > correctly. I could find nothing conclusive in the bug tracker but am
> > hesitant to raise it on qubes-issue in case it only affects me.
> > 
> > The symptoms are as follows:
> > 
> > * AppVMs connected to sys-whonix do not get networking
> > * There is an incorrect nameserver specified in the AppVM
> > /etc/resolv.conf (the IP does not match the IP of sys-whonix)
> > * There are no vif* interfaces in sys-whonix, or they are down and have
> > no IP address
> > * There are errors in the logs of sys-whonix like:
>
> Was this a fresh install of R4.1? If so, an issue would probably be the 
> best course of action since it's not released yet, so might not have 
> been widely encountered. If you upgraded by some other means, try 
> uninstalling the various Whonix templates & VMs and reinstalling via the 
> Salt commands documented on the Whonix website.
>
> -- 
> - don't top post
> Mailing list etiquette:
> - trim quoted reply to only relevant portions
> - when possible, copy and paste text instead of screenshots
>

-- 
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/bb5c3603-1733-4bef-ae9e-f3fef19321cdn%40googlegroups.com.

[qubes-users] HCL- Dell-Latitude-E6320(intel i7)

[A Luciani]

Installation instructions

   1. Use ISO Qubes
   2. Make sure secure boot is off
   3. When booting to install, select “Install Qubes OS"
   4. Finish installation and boot into OS

Nothing special about this model. ISO r4.1 does not boot (without changed
parameters).
Remarks

The important things work:

   - Wifi
   - Sound
   - HDMI
   - USB (internal & external)
   - Fedora 32/33

Not tested:

   - Bluetooth
   - Microphone
   - PCI Wireless 5550 WWAN Mobile Broadband DW5550
   but both seems to 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/CANRmXep0UAn7BRKAhB_Noymtz5NtKwZmRYYgwb0QtYLHKvHsBw%40mail.gmail.com.


Qubes-HCL-Dell_Inc_-Latitude_E6320-20210401-215801.yml
Description: Binary data

[qubes-users] Re: Compiling XEN 4.15 in vmm-xen

[Josef Johansson]

So basically, since I'm moving from 4.14 to 4.15, there is a lot of 
dependencies e.g. core-libvirt, qubes-vchan-xen and kernel-qubes-vm that 
needs to be recompiled against the new xen-devel.

I just missed the warnings about xen-libs not being possible to upgrade.

core-libvirt fails on 3 tests though.

-- 
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/76eee58a-40b6-4b85-8389-f8ecd0b1e7f9n%40googlegroups.com.

[qubes-users] Re: Audio on HP Z8

[Beto HydroxyButyrate]

Turns out someone had disabled the audio device in the BIOS.  Can't imagine 
who
I now have a built-in audio device which knows it has a place to plug in 
headphones.

Sweet.

On Wednesday, 31 March 2021 at 18:40:33 UTC+10 Beto HydroxyButyrate wrote:

> Just tried to listen to something on my Qubes system.  I know it works on 
> the Intel NUC systems, but on the HP it doesn't.  Nothing.
>
> I have an audio device.  See below for the `lspci` output.  The 
> PulseAudioManager shows zero hardware devices, just the dummy one.
>
> Any ideas?  I am supposedly on the most recent.
>
> 2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0
> Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr+ Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> SERR-  Latency: 0, Cache Line Size: 32 bytes
> Interrupt: pin B routed to IRQ 317
> Region 0: Memory at b024 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [48] Vendor Specific Information: Len=08 
> Capabilities: [50] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s 
> <4us, L1 unlimited
> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ 
> Unsupported-
> RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
> MaxPayload 256 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
> TransPend-
> LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit 
> Latency L1 <1us
> ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ 
> DLActive- BWMgmt- ABWMgmt-
> DevCap2: Completion Timeout: Not Supported, TimeoutDis-, 
> LTR+, OBFF Not Supported
>  AtomicOpsCap: 32bit+ 64bit+ 128bitCAS-
> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, 
> LTR-, OBFF Disabled
>  AtomicOpsCtl: ReqEn-
> LnkSta2: Current De-emphasis Level: -3.5dB, 
> EqualizationComplete-, EqualizationPhase1-
>  EqualizationPhase2-, EqualizationPhase3-, 
> LinkEqualizationRequest-
> Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Address: fee000b8  Data: 
> Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
> Len=010 
> Capabilities: [150 v2] Advanced Error Reporting
> UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta:  RxErr- BadTLP+ BadDLLP+ Rollover- Timeout- 
> NonFatalErr-
> CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
> NonFatalErr+
> AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- 
> ECRCChkCap+ ECRCChkEn-
> MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
> HeaderLog:    
> Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI)
> ARICap: MFVC- ACS-, Next Function: 0
> ARICtl: MFVC- ACS-, Function Group: 0
> Kernel driver in use: snd_hda_intel
> Kernel modules: snd_hda_intel
>
>
>

-- 
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/9f36b565-de0a-46ff-b458-a71476208c79n%40googlegroups.com.

[qubes-users] Backup to SMB mounted NAS in AppVM

[Beto HydroxyButyrate]

Last night I tried to run QubesBackup, selecting an AppVM as the target, 
and then selecting the SMB-mounted (r/w) folder. 
The backup process started, and the progress bar presented a small sliver 
of blue on the left, but was 0%.  Nothing was ever written to the target.  
No errors were ever suggested by the backup process.  Pretty much 0% CPU 
was being used in dom0.

After several hours, I closed the dom0 QubesManager window, which also 
closed the backup window, and tried re-running it directly as "Qubes 
Backup" from the menu.  It claimed I had a backup running.  Still nothing 
whatsoever written to SMB mounted folder.

Has anyone successfully written to SMB mounted share using backup?

-- 
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/714a2077-ca37-4e32-a1d1-65a9f55aeb57n%40googlegroups.com.

[qubes-users] Screen shot: open in DocumentViewer in AppVM

[Beto HydroxyButyrate]

When I screen scrape in dom0, one option is to open in DocumentViewer in 
one AppVM.
I assume it is because this is the only AppVM I have DocumentViewer added 
to the big menu.  Anyway, nothing ever happens.  Does anyone use this?  Has 
anyone used this?

I also try "Copy to the ClipBoard" assuming I can then do a "Copy Dom0 
Clipboard" and then paste in some AppVM but when I select "Copy Dom0 
Clipboard" I get a "dom0 clipboard is empty!" popup.

I'm trying to optimise the workflow of scraping screen and getting it to 
where I want it but the only way I can get it to work is to save it to 
Pictures in dom0 and then manually xfer it to some target VM and then 
rummage about in on the appVM  Rather cumbersome.

I'd also like to optimise the screen capture initiation.  On other 
platforms, I have a nice control-meta-cokebottle sequence.  I actually 
don't know what it is.  My fingers know.

-- 
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/2f91434f-5c4c-4998-937d-7aa1448223bdn%40googlegroups.com.