scall...@posteo.net:
>
>
> Original Message
> Subject: Re: [qubes-users] Re: sys-usb issues recognizing devices &
> maintaining drive connections
> Date: 04.01.2020 19:14
> From: scall...@posteo.net
> To: awokd
>
> On 04.01.2020 10:51,
Claudia:
> January 4, 2020 9:35 AM, "awokd' via qubes-users"
> wrote:
>> The Xen logs look similar to mine. I don't have kfd on my system.
>
> From what I saw, I think kfd is an AMD thing. Do you have AMD?
Yes. Pre-Ryzen, but the AMD IOMMU init in Xen
Guerlan:
> I'm trying to install macOS on Qubes. For it, it needs Qemu. There are two
> qemu-* in dom0:
>
> qemu-img-xen and qemu-nbd-xen
>
> I can't find options to see which versions of qemu they are. Where's the
> simple `qemu` command? And is it rigth to run it in dom0?
>
You don't want to
Lorenzo Lamas:
>
> On Friday, January 3, 2020 at 11:02:24 PM UTC+1, scal...@posteo.net 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
tetrahedra via qubes-users:
> From back in the 3.2 era:
>
> https://www.qubes-os.org/news/2017/04/26/qubes-compromise-recovery/
> $ qvm-backup-restore --paranoid-mode
>
> On my 4.0 install this option does not appear. Is it no longer
> considered necessary?
>
Looks like it is coming back:
https:
Claudia:
> I'm getting this message in my logs, about an IOMMU error, on both 4.0.2 and
> the F31-based 4.1 build. I'm as certain as I can be that the IOMMU is enabled
> in BIOS. I'm having issues with passthru and I'm wondering if this might be
> the cause.
> https://bugzilla.redhat.com/show_
Dylan:
> Hi, I've recently installed Qubes R4 on a IBM X3550 M4 and everything
> worked as expected apart from the networking. Originally I thought this
> might be a problem with R4 so I upgraded to R4.0.2 but no avail.
>
> The connection is detected as being plugged in, I've tried manually sett
tetrahedra via qubes-users:
> Solution:
> qvm-prefs MYVM kernelopts "nopat single"
>
> where `nopat` is whatever kernel options were previously listed in the
> output of `qvm-prefs MYVM kernelopts`
>
> Unfortunately there is still the problem that the VM is killed after 60
> seconds because Qube
Aaron Janse:
> On Saturday, December 28, 2019 at 4:14:43 PM UTC-8, Aaron Janse wrote:
>
>> My Googling/DuckDuckGoing skills have failed me. Any advice for how to
>> disable HPET? I couldn't find it anywhere in the BIOS settings.
BIOS settings was what I had in mind, unfortunately.
> Of course t
fiftyfourthparal...@gmail.com:
> Happy new year, fellow Qubers!
And you.
> Using 4.0.2-rc3, I managed to get all the way to actual installation after
> battling several major issues (like m.2 not appearing), but it seems like
> I've hit a brick wall. Installation freezes/fails during installati
trueriver:
> Hi I have found some new info relating to an old thread (~1 yr). What's the
> etiquette here: do I add a new reply to the old thread, or do I start a new
> one?
>
> I ask because different forums I am on have different requests about this
> one! ... oh yes and because I have notice
trueriver:
> Booting into recent install of Qubes 4.0.1 I have just realised I have not
> been setting the grub2 menu: it goes right in to loading Xen and then I see
> the four Tuxes. Is this an EFI thing, or a new feature of this version?
>
> (I ask because as well as changing Qubes versions I'
trueriver:
> I tried simply changing the template in qube settings, and some things worked
> and others didn't. Notably sys-usb stops recognising any USB device, and
> sys-net doesn't recognise WiFi.
>
> Is this a stupid idea, or are there straightforward ways to make it work?
>
> Ideally I'd l
trueriver:
> Hi, I am upgrading from Qubes 4.0 to 4.0.1 anyway. I notice that there is now
> a Debian 10 template and there are clear instructions for how to install, but
> that Q 4.0.1 still uses Debian 9.
>
>
> Am I right in thinking that the template from the newer version of Debian
> shoul
mas...@tuta.io:
> Now I have to solve "unable to reset PCI device, 00:14.0: no FLR, PM reset
> or bus reset available ...", but there's a thread on Github.
Enable the "no strict reset" option for the PCI device that is causing
problems via Qube Settings on the problem VM, then Devices tab, then
Charles Peters:
> In late September I backed up qubes using a new WD Elements external
> drive. At the time I don't think I had sys-usb installed. Yesterday when
> I tried to do the backups I was unable to mount the WD Elements drive,
> another USB connected Toshiba hard drive, or the Toshiba dri
Claudia:
> December 26, 2019 12:59 PM, "awokd' via qubes-users"
> wrote:
>
>> Claudia:
>>
>> TLDR; check bottom of https://community.amd.com/thread/241650, looks
>> like there was a recently released related updated. Not sure if
>> applicabl
tetrahedra via qubes-users:
> On Fri, Dec 27, 2019 at 09:57:16AM +0100, tetrahedra via qubes-users wrote:
>> Unfortunately I need to get work done so have to reboot to "just make it
>> go away" but I am still interested in troubleshooting ideas (for when it
>> happens next).
Investigate xl top mor
tetrahedra via qubes-users:
> On Fri, Dec 27, 2019 at 09:05:52AM +0100, tetrahedra via qubes-users wrote:
>> On Fri, Dec 27, 2019 at 08:33:10AM +0100, tetrahedra via qubes-users
>> wrote:
>>> Periodically all graphics-heavy apps (Firefox, ...) in all VMs seem to
>>> slow down simultaneously. Reboot
tetrahedra via qubes-users:
> On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
>> There's a brief discussion at https://www.qubes-os.org/doc/networking/,
>> but there may be more detailed notes in the source code for Qubes' VM
>>
Aaron Janse:
> On Thursday, December 26, 2019 at 5:31:50 AM UTC-8, awokd wrote:
>
>> What happens if you use an options line like the following?
>>
>> options=console=vga loglvl=all efi=no-rs
>>
>
> ```
> (XEN) Platform timer is 23.999MHz HPET
> (XEN) [...]
> (XEN) CPU0: No irq handler for vect
Guerlan:
> I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug
> kernel suspend problems. However, on dom0 there's no pm-suspend command.
>
> How can I install SECURELY this command or how to substitute for another
> one?
>
> This is the command:
>
> sudo sh -c "sync && echo
'Chökie Gyaltsen' via qubes-users:
> Thank you very much for your answers, my replies in bold below.
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users
> qubes-us
'Chökie Gyaltsen' via qubes-users:
> On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users
> qubes-users@googlegroups.com wrote:
>> In which log
>> are you seeing the above error?
>
> This message is from journalctl -ax and persisted af
Aaron Janse:
> At this point, I got the black screen described in issue #5165 (3).
> Following
> the advice there, I updated my options line to the following:
> ```
> options=console=vga efi=attr=uc noapic x2apic=off loglvl=all efi=no-rs
> iommu=no-igfx dom0_mem=min:1024M dom0_mem=max:4096M ucod
Spleen Productions:
>
>
> I have a HVM with a bootloader .ISO loaded in the VM.
> I would like to swap the cdrom and point it to another .ISO located in an
> AppVM.
> I cannot detach the device since i get an empty response from qubesd(see
> journalctl in dom0 for details).
> Is there any way t
Robert M:
> Claudia,
>
> Sorry for the late reply. Here are my answers:
>
>- Yes, i modified the BOOTx63.cgf file in ANACONDA.
What were your modifications? Per
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer
? Try also
https://www.qubes-os
rickey:
> Good evening Everyone,
> I have installed previously Qubes 3.2.1 on a Dell's Optiplex 3010, Small
> form factor desktop pc, and I was able to use it.
> When I tried to install the Qubes versions mentioned above on the same
> hardware, it is showing the message into the attached screensh
Claudia:
TLDR; check bottom of https://community.amd.com/thread/241650, looks
like there was a recently released related updated. Not sure if
applicable to your situation.
> This caused a very sneaky problem on my machine. My USB controllers are in
> the same group as my
> GPU, sound card, and S
'Chökie Gyaltsen' via qubes-users:
> Thank you, i removed the alpha_support and with that the gtk errors i was
> having vanished along with the tainted kernel messages.
> Also noticed improvement of the speed of the graphics. Things appear to move
> smoother and faster screen. Does that make sen
Ondřej Šulák:
> Hello everyone,
>
> I'm pretty new to QubesOS, and I have just start experimenting. I have
> installed Qubes 3.2.1 (because of incompabilities with my HW), upgraded
> Debian Template to Debian 10 and also sys-whonix Service VM to Debian 10.
>
> When I try to run apt update in De
Ray Joseph:
> I opened sys-usb settings and found the controller listed in the settings
> pane (on the right). The control button/bar at the bottom entitled
> "Configure strict reset for PCI devices". I clicked on the controller in
> the ‘selected’ window, then clicked the strict reset button
tetrahedra via qubes-users:
> I haven't been able to find any documentation for what network
> interfaces sys-net is expected to expose internally. If I want to create
> my own sys-net from scratch, how does Xen/Qubes send network traffic to
> sys-net, to be sent onwards to my NIC?
>
There's a bri
Eva Star:
> Hello,
> To enable swap trim need to add "discard=once".
> The string at /etc/fstab will be like this?
> "*default,discard=once,x-systemd-device*"
> After editing fstab need to run something?
> Thanks
>
Yes, to the line:
/dev/mapper/qubes_dom0-swap swap swap
defaults,x-systemd.devic
brendan.h...@gmail.com:
> If fedora were still running init, I'm pretty sure I could find the right
> place to do this, but with systemd, I am quite discombobulated.
Perhaps that is the "do one thing, and do it well" systemd strives for.
> 1. Where/how do I insert a thin_trim of the qubes_00 po
B. Kent:
>
>- Created the USB installer disk and then tried to modify the
>BOOTX64.cfg file (with VI), USB filesystem is Read Only
> - I've read that I need to mount the Qubes ISO on my laptop, edit
> BOOTX64.cfg from the ISO and then save that file...then create a new
> US
'Chökie Gyaltsen' via qubes-users:
> Hello all,
>
>
> I've just installed Qubes latest preview 3. Installed it offline, so all the
> logs you will see are from a disconnected system. There are some services
> disabled related to security that worry me ( listed below ). Also some
> entries tha
Tae Hwan Kim:
> Hi all!
> I am trying to use Qubes OS as a mobile development machine.
>
> My backend server is running in work vm at localhost:4000
> And I am testing my app in real device that is connected using USB cable.
>
> The frontend client should send request to my backend server
> (loc
Guerlan:
> Am I doing things rigth now?
Pretty much, thank you. It's also considerate to trim parts of the prior
thread that are no longer under active discussion, or needed for context.
> So, xen.cfg contains things like
>
> default=4.19.71-1.pvops.qubes.x86_64
>
> [4.14.74-1.pvops.qubes.x86_
'Crypto Carabao Group' via qubes-users:
> Hello All,
>
> What is the general procedure in Qubes 4, if we can open the Luks, but then
> pool00 seems inaccessible with rdsosreport message:
> Check of pool qubes_dom0/pool00 failed (status:1). Manual repair required!
There's not a general procedure
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
> r
Slightly Different:
>
> 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
Claudia:
> My original thought was to just give each one its own directory in
> /boot/efi/EFI/, but the /boot/efi/EFI/qubes/ path seems to be hard coded
> somewhere, probably either in the grub2-efi package (which installs a
> precompiled efi binary to that directory) or in a grub2-install hook
> s
Myros:
> Hi,
>
> I installed Win10 and that worked without a problem, but then i installed
> the windows tools on it, and now nothing opens at all. i think that has to
> do with seamless-mode... (i forgot to give the vm internet, so it was
> unable to download certain things)
>
> So not only f
Myros:
>
>>
>>> Workarounds would be to upgrade Whonix from 14 to 15 per the docs on
>>> their site, or to use Qubes 4.0.2rc2 which comes with upgraded Whonix
>>> templates.
>>>
>> Make that 4.0.2rc3.
>>
>
> can i just dist-upgrade in dom 0?
>
No, that won't get your templates upgraded. If
r...@aarden.me:
> It has taken four years to get to here. I have tried this with Debian and
> Qube OS. I could not get Xen on Debian to work due to my wireless only
> networking of my laptop. With Qubes, it has been getting wireless and USB
> to both work. This time, wireless worked maybe.
'awokd' via qubes-users:
> Workarounds would be to upgrade Whonix from 14 to 15 per the docs on
> their site, or to use Qubes 4.0.2rc2 which comes with upgraded Whonix
> templates.
>
Make that 4.0.2rc3.
--
- don't top post
Mailing list etiquette:
- trim quoted repl
Myros:
> Hello,
>
> As suggested by the doc i should use this commands after first boot:
>
> $ sudo qubes-dom0-update --enablerepo=qubes-templates-community
> --action=upgrade qubes-template-whonix-gw-14
> $ sudo qubes-dom0-update --enablerepo=qubes-templates-community
> --action=upgrade qubes-
Markus Tester:
> Hello Everyone
> Today i tried to install Cubes OS on my new Laptop (Acer Nitro 5 with a
> Nvidea
> Geforce GTX 1050). I checked the BIOS for VTX and VTD, both are enabled
> alongside of UEFI and Secure boot.
> I downloaded Qubes-R4.0.1-x86_64.iso checked the signature, and trie
tetrahedra via qubes-users:
> However, when I try to configure sys-firewall to use sys-net2 instead of
> sys-net for networking, I get the error:
> ERROR Basic tab: Failed to access 'netvm' property
This should work, but make sure sys-firewall is shutdown before
attempting to change. If it still
pkw:
>
>
> W dniu niedziela, 8 grudnia 2019 18:13:58 UTC+1 użytkownik pkw napisał:
>> *sdc 8:32 0 465,8G 0 disk ├─sdc1 8:33 0 1G 0 part
>> └─sdc2 8:34 0 464,8G 0 part└─qubes 253:00 464,8G 0 crypt*
>>
>>
>> root@X230:/qubes# mount /dev/mapper/qubes /qub
pkw:
>
>
> W dniu niedziela, 8 grudnia 2019 16:30:43 UTC+1 użytkownik pkw napisał:
>>
>>
>>
>> W dniu niedziela, 8 grudnia 2019 16:20:20 UTC+1 użytkownik awokd napisał:
>>>
>>>
>>> Yes, you should be able to mount the drive either in another system or
>>> with a rescue boot CD/image on the same
IT Geek:
> Hi,
>
> my qubes installation won't boot, I have no backup... :/
>
> I started it today, dom0 started but any of the VMs could'nt start. there
> was an error:
>
> "domain has failed to start volume qubes_dom0/vm... missing" - more less. I
> cant remember exact error
>
> then I rebo
Dave:
> I have a broken app-vm, from which I want to recover the usr home dir.
> I want to mount the private.img as a vol to the new working vm using
> qvm-block so I can copy user files in accordance with instructions here:
> https://www.qubes-os.org/news/2017/04/26/qubes-compromise-recovery/
>
jonbrownmaste...@gmail.com:
> What equipment do I need to install Heads firmware on Thinkpad x230? Do you
> mind linking required items I need to purchase to do this?
>
This is off topic for Qubes mailing list, but it's the same equipment as
needed for Coreboot, so
https://harmonicflow.org/blog/F
jonbrownmaste...@gmail.com:
> Can someone link me which Thinkpad x230 I should get and best parts to get
> to upgrade it to make a high performance version.
>
https://insurgo.ca/produit/qubesos-certified-privacybeast_x230-reasonably-secured-laptop/
--
- don't top post
Mailing list etiquette:
-
E. Foster:
> How would you create a sys for USBs (files, apps, etc) ?
> sys USB mouse(if needed)? (currently works, but I don't see sys-usb in the
> drop down menu, but is it safe?)
> sys USB biometric reader? (potentially a way to speed up logins or
> temperature readings)
Check out https
mrqubesh...@airmail.cc:
> Hello,
>
> I recently copied my AppVMs (and some custom templates) onto my
> secondary drive according to this guide [1].
> Now that I have reinstalled my QubesOS onto my main drive and unlocked
> my secondary drive, I can't access the AppVMs saved.
The reinstall is what
haaber:
> Hi, I try to play with an programmable esp32 (pretty much like arduino,
> but with wireless on board). The problem I have arises from sys-usb: the
> usb widget spills out the odd error "QubesException - device attach
> failed: no device info received. Connection faild. Check backend for
>
haaber:
> since my last updates using --enablerepo=qubes*testing I have some
> reproducible problem: each time I close the laptop lid, it seems I have
> to reboot my machine. Problem known? Any cure known? Where/How to find
> out more? Cheers, Bernhard
>
Might be worth mentioning on the appropriat
Sven Semmler:
> Since I have two full days of work in that VM that I haven't pushed to the
> git server yet, my first impulse is to get my source code out of there to a
> safe place. I understand I can do that with qvm-block but I have no idea
> where to find the volume of the standalone VM (as
nanop...@tuta.io:
> Hello there, I realized that everytime I made a new Qubes VM, I have been
> checking the "provides network" option turning it into a NetVM.
> I mistakenly believed that the option of "provides network" meant that the VM
> would need connectivity (yeah, I didn't RTFM), so now t
'Zeko' via qubes-users:
>
> I changed autostart to False in the qubes.xml entry for sys-usb but the OS
> still starts sys-usb and panicks like before.
In that same file and general location, remove the line beginning with
. This
will remove the USB PCI controller from sys-usb.
> Also if I didn
Sphere:
> However, a ram stick just died on me this week and I badly need all the RAM
> that I could get. Even right now, my dom0 is actively using just about 940
> MB worth of RAM... which is why I think it would be best if I could
> permanently allocate 2048M to dom0 instead of 4096M for my c
'Zeko' via qubes-users:
> [ OK ] Stopped target Local File Systems
> Unmounting /boot... (if it matters, boot is on a USB device)
Probably.
> [ 172.272900 ] usb 1-12: USB disconnect, device number 3
> [ OK ] Unmounted /boot.
> [ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet
Dave:
> Hi,
>
> I am trying to update the torbrowser in the Whonix-ws-15-dvm, but cant seem
> to get it updated.
> Thought the torbrowser in the disposablevm could be updated by running the
> "Tor browser Downloader" in the "Template : Whonix-ws-15" ..
> The torbrowser in the template is updated
Claudia:
> So I was wondering, is it possible to run the Qubes dom0 kernel directly
> on the hardware instead of under Xen? How might one go about this? And
> how much work would it involve?
I've had similar troubleshooting needs. Closest I found was to download
Fedora 25 and test under that. Wha
Matthew Roy:
> When attaching a USB device from a new, disposable &
> minimal-template-based, sys-usb, I get the following error:
>
> user@dom0 ~]$ qvm-usb attach disp6xx5 sys-usb-dvm:2-2
>> Device attach failed: No device info received, connection failed, check
>> backend side for details
Try ma
haaber:
> Just a small comprehension question to the microkerel update shipped in
> the last xen update: are these microkernels "flashed" into some cpu
> memory, or are they re-run / setup at each boot again? Cheers, Bernhard
>
I think you mean microcode. From what I know, the CPU starts with burn
> And to follow on, is there a way to tell if I have 4.0 or 4.0.1 or
4.02rc2?
If it's like previous releases, if you have Qubes 4 patched to the
"current" (default) repository, you are running the latest point release
(4.0.1). If you have it patched to "current-testing", you're running the
current
Master Node:
> Hi I was finally able to get a working and running system, I had updated
> everything to whonix 15 and debian 10 leaving fedora 26 as is.
>
> I had turned my pc off and restarted it as normal booting legacy USB threw my
> external m2 drive, as that is how I was able to install I g
Jarrah Gosbell:
> I have upgraded an existing Qubes system to use the AMD RX 5700 XT.
> However, when booting with Xen, the driver is unable to install the GPUs
> firmware. I receive the following error message:
>
> ```
>
> amdgpu [...]: (-14) failed to allocate kernel bo
> amdgpu [...]: failed t
Jarrah Gosbell:
> I have been attempting to get Qubes installed on my Metabox Prime-V
> laptop, which has resulted in the following kernel panic on each boot.
> [qubes-verbose]
> options=console=vga efi=no-rs iommu=no-igfx loglvl=all
> dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,k
collinblainehud...@gmail.com:
> Does anyone know if it's possible to export a Windows vm installed in qubes
> and transfer it to another install of qubes? If yes, can you explain how to
> do this?
>
Using Qubes Backup on the Windows VM, transferring the backup file, and
a Qubes Restore ought to
tetrahedra via qubes-users:
> On Tue, Oct 22, 2019 at 12:09:27AM +, 'Jackie' via qubes-users wrote:
>> Is the appmenus-dispvm feature turned on for the dvm template?
>>
>> qvm-features dvm-template-name appmenus-dispvm 1
>>
>> https://www.qubes-os.org/doc/disposablevm-customization/
>
> Tor Br
Gaijin:
> I've had issues after restoring my backups though. I can't seem to
> upgrade my TemplateVMs without getting the dreaded “Failed to
> synchronize cache for repo” errors
> https://www.qubes-os.org/faq/#i-keep-getting-failed-to-synchronize-cache-for-repo-errors-when-trying-to-update-my-fedo
Strak8:
> Every three months for several years I spend a whole day trying to make the
> second video card work on my laptop.
> 1. The windows 7 VM with the attached video card loads only with less than
> 4GB of RAM (otherwise it is blue screen)
Have you seen
https://github.com/Qubes-Community/
Jin-oh Kang:
> I'll submit the correction PR when I get to have some free time for it. I
> apologize for not having made this clear. Meanwhile if you'd like to do it
> instead -- since you're also the author of the article -- then I'd
> appreciate it ;)
I got it (I think).
--
- don't top post
M
Gaijin:
> I have a worstation on R3.2 and was holding out on an update to R4.x. I
> was hoping that R4.0.2 would have been finalized by now, but news on
> that has been pretty scarce since the July 10 announcement of RC1. I
> can't afford a lot of time to troubleshoot an upgrade on this particular
'mekken1et' via qubes-users:
>
>Problem
> ===
>
> Firefox can leak various IDs from a profile to websites, so different
> sessions can be correlated across different qubes, including DispVMs.
Thank you; nice list.
--
- don't top post
Mailing list etiquette:
- trim
tetrahedra via qubes-users:
> On Thu, Oct 17, 2019 at 01:24:00PM -0700, Jin-oh Kang wrote:
>> The escape sequence crippling is caused by
>> https://github.com/QubesOS/qubes-vmm-xen/blob/xen-4.8/patch-tools-xenconsole-replace-ESC-char-on-xenconsole-outp.patch
>> , which is reasonable given the Qubes
random3uuj via qubes-users:
> On Thu, October 17, 2019 05:06, awokd wrote:
>> random3uuj via qubes-users:
>>> I have the following machine:
>>> Ryzen 5 2600
>>>
>>>
>>> MSI PERFORMANCE GAMING X470 GAMING PLUS
>> There is a good chance it is that Nvidia card. Can you easily switch to
>> AMD instead
Anil Eklavya:
> I am trying to install Qubes on HP Pavillion x360 14 inch (cd0056TX). I have
> tried both in UEFI mode and legacy boot mode. It either doesn’t recognise the
> bootable drive (says not bootable drive), or it stops at one point during
> booting from the installation pen drive and j
random3uuj via qubes-users:
> I have the following machine:
> Ryzen 5 2600
>
> MSI PERFORMANCE GAMING X470 GAMING PLUS
>
> G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4
> 25600) Desktop Memory Model F4-3200C16D-16GVGB
>
> GeForce GTX 1060
>
> I have not been able to
tetrahedra via qubes-users:
> As a result of some issues in a standaloneVM (debian-9), I ended up
> using the Xen hypervisor serial console to migrade to debian-9-testing --
> part way.
> Now when I do `sudo file -s /dev/xvda[1..3]` I do not see any grub
> installation, and running `grub-emu` also
JimmyJames:
>
>
>>
>>> A little later I was prompted to abort because of the fatal error:
>>> DNF Error: Error unpacking rpm package iso-codes-3.70-1.fc25.noarch
>>
>> Did you verify after you burned the DVD?
>>
>>
>> awokd:
>
> No, I didn't verify the DVD after burning -- I didn't know that
JimmyJames:
A little later I was prompted to abort because of the fatal error:
DNF Error: Error unpacking rpm package iso-codes-3.70-1.fc25.noarch
Did you verify after you burned the DVD?
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible
Guerlan:
I have a MediaTek card adapter. I redirected it to the VM. When I run lsusb
inside the VM, it won't appear.
How do I troubleshoot this?
To troubleshoot, check the journalctl logs in the target VM. Otherwise,
leave it in sys-usb and insert some media, and see if you can redirect
the m
M:
The first start up of the pc after the installation of Qubes results in a black
monitor immediately after running the code/script that is related to booting
Qubes OS.
Wonder if the reason could be that I have chosen full encryption and use USB mouse and keyboard. Although the USB-Qube opt
Guerlan:
I installed android-tools and it didn't work.
Are you sure I don't need a sys-usb VM?
If you want to try, in that same link that was posted earlier
(https://www.qubes-os.org/doc/usb-qubes/), look for the part about how
to create one manually. Pay close attention to how to identify a f
M:
> Thanks.
>
> I should just click on OK in the error message and then click on “Continue
> configuration” - or something similar.
>
> I then entered “lspci” in the Dom0 Terminal when logged in as root (do not
> know if it’s also possible to see when logged in as normal user).
>
> I then fou
M:
> Now the motherboard is changed and I have managed to begin the installation
> of Qube OS.
>
> But after the installation, reboot and continuing the installation process, I
> get this error message:
>
> [dom0] Error
> “[‘/user/bin/qvm-start’, ‘sys-firewall’] failed:
> stdout: “”
> stderr:
Guerlan:
I only have one GPU, which is an Intel UDH graphics. Obviously Qubes uses
it to display graphics. However, I think it's theoretically possible to
disable my GPU from dom0 and do a PCI passthrough to another VM, which will
then appear as fullscreen (I will not be able to use Qubes meanwhi
'Oli Sturm' via qubes-users:
> Hi,
>
> I found a problem yesterday: I had some markdown text rendered to HTML with
> the smartypants option to replace "--" with a long dash. The generated file
> contained a unicode entity for that character, I copied it to the clipboard,
> then did Ctrl-Shift-C
anneeyr...@gmail.com:
> When using the dd-method, the pc starts running the check and after about 10
> seconds the screen goes black. Maybe caused by wrong screen/display drivers.
> But I don’t know.
> I have also tried to boot this in legacy mode, but then the screen goes black
> immediately a
thomas.lynch via qubes-users:
> Where may i ask question for help with installation (or is it here)?
Here's good.
> 5. got a progress bar, various messages concerning templates etc. then it
> said something
> about configuring networking. That took a little while, then the screen
> went blac
cacaosu...@tutanota.com:
> Hello !
>
> I broke my qubes, and no appVM start. I'll fix that later, for the moment I
> need to urgently recover files that are stored on my appVM.
>
> I have booted on a lubuntu live usb and try to mount my partition ( located
> on sda ), but didn't succeded.
>
Sake:
This was in your signature, so I'm not sure if you meant to send it but:
> https://qubes-os.info/ seems to be off for months now.
> bad new!
> What's happen?
Please see
https://www.mail-archive.com/qubes-users@googlegroups.com/msg28187.html.
One alternative is to use qubes-users@googlegrou
acharya.sagar.sag...@gmail.com:
> I tried to make things work using Qubes built iso but the updates (dom0)
> instead of stabilizing the system, broke it. I couldn't boot up!
Did you try changing the kernel back? See
https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel.
> Ho
'ScoreB' via qubes-users:
> * What should the owner & permissions be on to be safest as possible but also
> allow the VPN Qube to function properly:
> - /rw/config/rc.local
> -/rw/config/qubes-firewall-user-script
> -/rw/config/vpn/pass.txt
> -/rw/config/vpn/openvpn-client.ovpn
> -/rw/config/vpn/
301 - 400 of 1809 matches
Mail list logo
