ultimatev...@gmail.com:
Qubes OS version:
R4.0
Affected component(s):
Intel Wireless N 1000
Steps to reproduce the behavior:
I installed QubesOS R4.0 and made it to the installation configuration page
(where the system finishes installing, reboots, and then you are prompted with
the config
Eric Duncan:
Latest 1.17 BIOS, VT-d and Virtualization enabled in BIOS. Various thunderbolt
assists disable/enable, etc options tried on/off. Must use discrete graphics
during install, which is an Nvidia Quatro P2000 (similar to the GTX 1050qm
generation).
Anaconda installer gets past the
Trying to install Qubes R4.0 and R4.0.1-rc2 and receiving the same install
error each time.
https://imgur.com/a/haBeVee
/usr/bin/qvm-start sys-firewall failed
stdout: ""
stderr: "Start failed: internal error: Unable to reset PCI device
:00:1f:6:
no FLR, PM reset or bus
Em domingo, 6 de janeiro de 2019 13:25:17 UTC-2, simon@gmail.com escreveu:
> On Sunday, January 6, 2019 at 1:32:45 PM UTC, Sergio Matta wrote:
> > I think I have a problem with yum file configuration. Fedora 25 looks like
> > ok but Qubes never finds data:
> >
> > Fedora 25 - x86_64 -
Jake wrote on 12/29/18 11:19 PM:
On 12/16/18 9:05 AM, unman wrote:
On Sun, Dec 16, 2018 at 01:57:57AM -0600, Jake wrote:
I need to add an additional yum/dnf repo to install some software, but I
seem to only be able to do it on an appvm/dispvm, not on a template.
When adding the repo to the
one7tw...@gmail.com wrote on 12/28/18 9:33 PM:
Additional note which might be important:
The sys-net VM which is based on the fedora-29 template I have built can
connect to the internet (I tried ping and also using the CLI-browser w3m).
The sys-firewall VM is unable to connect to the internet,
heinrich.ulbricht via qubes-users wrote on 12/27/18 11:29 PM:
I'm using Qubes 4 with USB VM (sys-usb) which is working well.
When attaching USB devices I currently have to manually assign them to AppVMs via the top
right "Qubes Devices" dropdown menu. Which is also working well.
But: I want
haaber:
>> It's running fine for me from a flatpak --user install ... has the
>> advantage that the template only needs flatpak and all signal is in the
>> appVM only.
>>
>> Joh
>>
>> On Fri, 2019-01-04 at 18:57 -0600, Sven Semmler wrote:
>>> Hi,
>>>
>>> I just installed signal-desktop (in the
seshu wrote on 12/26/18 11:05 PM:
On Tuesday, December 25, 2018 at 7:49:17 PM UTC-7, John Smiley wrote:
I install from USB3 stick all the time and it’s fast. Even if it is dropping
back to 2.0, it should not be as slow as you describe.
That is good to hear. I might have just had other
Zbigniew Łukasiak wrote on 12/26/18 6:07 PM:
I try to attach my Android phone (Samsung Galaxy S7) via USB cable to
transfer files to my QubesOS box. From googling around figured out a
plan to attach the USB device to another qube, install the MPT library
there - and use Nautilius to mount the
'yofjueee0fsi22' via qubes-users wrote on 12/26/18 1:02 PM:
Hello, Greeting to all.
Thank for the nice work of Qubes, I'm not a advanced user but really like your
work.
Recently, I had some problem with the system, so had to reinstall Qubes4.0,
tried to do it via DVD, but the error keeps
> Right now I'm not even getting to centos-7:
>
> make get-sources get-sources-extra qubes-vm is stopping at
>
> -> Installing core RPM packages...
> error: Failed dependencies:
> glibc = 2.28-9.fc29 is needed by
> glibc-all-langpacks-2.28-9.fc29.x86_64
> glibc-common = 2.28-9.fc29
It's running fine for me from a flatpak --user install ... has the
advantage that the template only needs flatpak and all signal is in the
appVM only.
Joh
On Fri, 2019-01-04 at 18:57 -0600, Sven Semmler wrote:
Hi,
I just installed signal-desktop (in the template) and now try to run
it in the
---
layout:
'hcl'
type:
'notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'unknown'
remap:
'yes'
brand: |
ASUSTeK COMPUTER INC.
model: |
UX305CA
bios: |
UX305CA.300
cpu: |
Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
cpu-short: |
FIXME
chipset: |
Intel Corporation Xeon
On Sunday, January 6, 2019 at 3:20:08 PM UTC, Plex wrote:
> Is there a technical limitation/reason why a qube private max storage size
> can only go to 1048576MiB in qube manager? Is this a limitation with the qube
> itself or qube manager?
>
> TIA
I should RTFM
On Sunday, January 6, 2019 at 1:32:45 PM UTC, Sergio Matta wrote:
> I think I have a problem with yum file configuration. Fedora 25 looks like ok
> but Qubes never finds data:
>
> Fedora 25 - x86_64 - Updates 1.0 MB/s | 24 MB 00:24
> Fedora 25 - x86_64
Is there a technical limitation/reason why a qube private max storage size can
only go to 1048576MiB in qube manager? Is this a limitation with the qube
itself or qube manager?
TIA
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
I think I have a problem with yum file configuration. Fedora 25 looks like ok
but Qubes never finds data:
Fedora 25 - x86_64 - Updates 1.0 MB/s | 24 MB 00:24
Fedora 25 - x86_64 2.0 MB/s | 50 MB 00:25
Qubes Dom0 Repository (updates)
Not sure if you managed to blacklist the pcspkr module ; if not you
could try to mute the beep: in dom0, run alsamixer (you may have several
cards, for instance I have to run `alsamixer -c1` because the first card
is my hdmi port). There should be a "beep" column - navigate to it and
press "M"
On 1/6/19 12:57 PM, unman wrote:
I didnt mean to give you the brush off - just to remind you that Qubes
*does* allow you to make (serious) mistakes without pain, if you clone
and test first.
Oh yes, everything is fine to me and I got you right. I really
appreciate your way of helping. Have a
On Sun, Jan 06, 2019 at 11:14:27AM +0100, gone wrote:
> On 1/5/19 5:39 PM, unman wrote:
>
> >
> > There really isn't anything to be lost (assuming you are working in a
> > cloned template.)
> >
>
> You are completely right. I should more often just try what happens than ask
> for every little
On 1/5/19 5:39 PM, unman wrote:
There really isn't anything to be lost (assuming you are working in a
cloned template.)
You are completely right. I should more often just try what happens than
ask for every little step in fear of crushing the system on the playground.
--
You received
On 1/2/19 11:24 PM, haaber wrote:
Try these:
As root rmmod pcspkr, should stop it in running machine.
Edit /etc/modprobe.d/blacklist, and insert a line:
blacklist pcspkr
That helps in dom0 terminal, but neither on dom0 login screen nor dom0
xterm. Funny.
If that doesnt work, put the rmmod
23 matches
Mail list logo
