Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

[Scott Russell]

Hi,
So, now trying to access rescue mode.  I followed the instructions
here.
https://www.qubes-os.org/doc/uefi-troubleshooting/#accessing-installer-rescue-mode-on-uefi
  But, I seem unable to get into rescue mode.  Was just wondering when I
should be using the Ctrl+ALt+F2.  Should this be after the disk
encryption password entry, or before?  I have tried both, but neither seem
to work.  But I was a bit impatient, so will try again when I have more
time to wait.
Obviously this is critical for me to investigate why my kernel is causing a
reboot loop.

   thanks for any advice.
   Sc0tt...

On Thu, 23 Jan 2020 at 08:08, Scott Russell 
wrote:

> Hi, the one thing I did notice, was at the end of the install, you have to
> remove the install pendrive from the laptop, before you reboot.  It took me
> 3 or 4 attempts to work that one out.  I don't remember that you can eject
> it, but it does give you some kind of warning to remove the cd or similar
> before rebooting.  Not sure what it is doing, but it gave the same black
> screen on reboot, but then it just worked if I removed the pen drive,
> before reboot.  Give that a try and let me know if it works.  I probably
> will do a complete re+install now I have things working(well wireless via a
> usb dongle, but working).
>
>  good luck
>
> Sc0tt...
>

-- 
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/CAAvfSaLxdC%2BcHG%3Ds5VFjpkuxqr%3DTQ7gHfXRwyUV92-ycvqijrQ%40mail.gmail.com.

Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

[Scott Russell]

Hi, the one thing I did notice, was at the end of the install, you have to
remove the install pendrive from the laptop, before you reboot.  It took me
3 or 4 attempts to work that one out.  I don't remember that you can eject
it, but it does give you some kind of warning to remove the cd or similar
before rebooting.  Not sure what it is doing, but it gave the same black
screen on reboot, but then it just worked if I removed the pen drive,
before reboot.  Give that a try and let me know if it works.  I probably
will do a complete re+install now I have things working(well wireless via a
usb dongle, but working).

 good luck

Sc0tt...

-- 
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/CAAvfSaJVv%2BnybvuHyerNtiBZX7Rd3iF3AF5Wr13R7hYGj9KrBQ%40mail.gmail.com.

Aw: Re: Re: [qubes-users] Installation freezes before displaying installer - UEFI-Troublshooting impossible

[anbe2015]

 

Good evening Claudia and all the other readers,

 

> What was the full command you used to write the ISO to the USB drive? Are you absolutely sure you wrote it to /dev/sdb and not /dev/sdb1?

 

I followed completely the Installation-Guide on "https://www.qubes-os.org/doc/installation-guide/":

 

$ sudo dd if=Qubes-R4.0.2-x86_64.iso of=/dev/sdb bs=1048576 && sync

-and-

$ sudo dd if=Qubes-R4.0.3-x86_64.iso of=/dev/sdb bs=1048576 && sync

 

both under an Ubuntu-Linux and yes I wrote to /dev/sdb not sdb1.

 

 

I tried also the RUFUS-Tool under Windows, discribed in the Installation-Guide above, with "dd-image-mode". However, everytime it ends in a read-only filesystem on the created usb-drive, where I can't modify the files, which are all necessary for troubleshooting.

 

 

And everytime it creates a linux-file-system, so that the usb-drives(s) can't be used under windows again... but also can't formated under Linux. So I now zero out the drives with "sudo dd if=/dev/zero of=/dev/sdb", in hope, that I after that can format the usb-drives under Linux with FAT-Format to use it again.

 

Than I will at last idea use the RUFUS-Tool and write the usb-drive in "iso-image-mode" to try to get writing-acess and then doing the installation again with modified files for troubleshooting.

 

 

> It should be mounted as vfat, not iso9660. You can try mounting it as vfat with `mount -t vfat /dev/sdb1 /mnt`, but I don't think it'll work without being rewritten.

 

I'll try this, after my laptop is ready with zero-out the first usb-drive... unfortunately it needs a lot of time. After that I don't know, what can be done yet. But thanks a lot for your answers and suggestions.
 





-- 
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/trinity-d09c335e-fce1-4d99-8e25-21e4a24e5fff-1579728974203%403c-app-webde-bap30.

Re: [qubes-users] Re: qvm-create-windows-qube 2.0

[River~~]

No unman, please get off my case on this.

You misrepresent my intention totally, and ate responding without showing
signs of having read the material I pointed you to.

My *original* original post on this subject, which I pointed you to, asked
whether that expectation was reasonable, and awokd said that it usually
does work.

In that thread, xao pointed me to a list of packages relevant to minimal
templates, and suggested I used that to guide me.

My first post in this thread tried to pass that information on to other
people, as it seemed relevant.  That earlier thread also pointed to issue
#5123, which if you read the first post of that issue, starts from the
assertion that it seems I'm not the only Qubes user to come with that
expectation.

You say:

> I think your expectation is misplaced - ...

Then please explain exactly why issue #5123, which I also pointed you to
and which you also do not seem to have read, has adjusted the contents of
the Debian template to meet the fact that (according to the first post in
that issue) seems to be a common expectation.

> ... they are different distros, ...

They are actually both parts of the Qubes distro here, installed by either
the Qubes installer or from the Qubes repo -- their history from other
distros is irrelevant. And yes, when you install a real Debian you get
promoted for firmware. When you install the Qubes template you get no such
prompt.

Indeed, you install the Debian template using DNF not apt, because the
Qubes system regards it as software for Dom0.

>
> Your original post seemed to suggest that the Debian template didn't come
> with packages required to act as sys-XXX - this isn't true.

This is true.

Please stop denying that fact. It doesn't work before I followed xao's
advice, it does work after. Therefore at least one of those packages was
essential. And every one of the other packages added by #5123 will be
essential for some other users: that's why they are there.

Clearly a sys net Qube needs a working firmware *for* *the* *computer*
*it's* *on*, not just for some other hardware. End of.

That's why #5123 was accepted, because it fixed exactly this problem (or
certainly attempted to).

> It *may* lack
> packages required for some hardware -

 May 

It does lack them. Please stop undermining the facts. I told you that
installing them made it work. Do you not believe me

> just install them.

Exactly so.

That's exactly why it is helpful that xao pointed me to a list in the docs.
That's exactly why it's helpful for me to pass that advice on to others,
until such time as the "fully firmwared" Debian template becomes the norm
(as Chris pointed out in the earlier thread). That's exactly why it is
profoundly unhelpful for you to undermine that sounds advice.

> (The same is
> true for the Fedora templates)

Er no.

If a Fedora template didn't work it would be reported as a bug as soon as
the first user found they couldn't update through sys-net. And would be
acknowledged as a bug without all this prevarication, and it would not get
out of the rc1 stage, if it even got that far.

The reason the Debian one slips through the net is that it is not critical
in that sense. People can (and according to #5123 actually have) given up
on the Debian templates for sys-net due to this issue.

Whatever you think, the ppl who maintain the Qubes system accepted that as
an issue and believe it to be fixed by adding those firmware files. I'm
simply reporting that back.

But believe what you like.

This exchange is now closed as far as I am concerned.

-- 
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/CAK3jUKruysb66%3DitPNeO02qCZzTz-1r17q5PdgSf%2Bqg-q6vz_A%40mail.gmail.com.

Re: [qubes-users] debian-10-minimal template sudo

[Chris Laprise]

On 1/22/20 2:57 PM, Dominique St-Pierre Boucher wrote:

Good afternoon,

I know that I have seen that somewhere but I am unable to find it. The 
debian-10-minimal template sudo require a password. How do I change 
that? I don't remember how to do it!!


The minimal templates don't have the qubes-core-agent-passwordless-root 
package installed, so there is no way for a user to initiate root access 
from inside the VM.


Instead, you can run commands as root from dom0 with 'qvm-run -u root 
vmname "commands"'. You could use that to install the above package to 
make 'sudo' work like a regular template, or you could do what I prefer 
and tie sudo to a dom0 yes/no prompt:


https://www.qubes-os.org/doc/vm-sudo/#replacing-passwordless-root-access-with-dom0-user-prompt

--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/bd435ec6-7c67-62da-7d0b-337e2b5b8ae9%40posteo.net.

Re: Aw: Re: [qubes-users] Installation freezes before displaying installer - UEFI-Troublshooting impossible

[Claudia]

January 22, 2020 11:36 AM, anbe2...@joker.ms wrote:

> Hello Claudia,
> 
> thanks so much for your answer.
> 
>> Once you write the image file with dd, you should be able to mount the ext3 
>> /boot filesystem
> read/write
> 
>> just like you would any partition on a flash drive. It should no longer 
>> appear as an iso once
> it's written to
> 
>> the flash drive, it should show up like an external hard drive would. You 
>> may have to unplug it
> and plug it
> 
>> back in for the kernel to recognize the new partitions on it. Also, make 
>> sure you're writing to
> /dev/sdb
> 
>> and not /dev/sdb1 for example.
> 
> My system mounts the usb-stick as following:
> 
> $ mount -l
> 
> $ /dev/sdb1 on media/username/Qubes-R4.0.2-x86_64 type iso9660
> (ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=40
> ,uhelper=udisks2) [Qubes-R4.0.2-x86_64]

What was the full command you used to write the ISO to the USB drive? Are you 
absolutely sure you wrote it to /dev/sdb and not /dev/sdb1?

It should be mounted as vfat, not iso9660. You can try mounting it as vfat with 
`mount -t vfat /dev/sdb1 /mnt`, but I don't think it'll work without being 
rewritten.

-- 
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/a57791a95220e0af8578c82b5ed4128a%40disroot.org.

[qubes-users] debian-10-minimal template sudo

[Dominique St-Pierre Boucher]

Good afternoon,

I know that I have seen that somewhere but I am unable to find it. The 
debian-10-minimal template sudo require a password. How do I change that? I 
don't remember how to do it!!

Thanks

Dominique

-- 
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/7d11b881-f356-4c7a-9247-0c8db5b513e5%40googlegroups.com.

Re: [qubes-users] Re: Write-error on swap-device after having a full storage

[Steve Coleman]

On 2020-01-22 12:22, Vít Šesták wrote:
*APL external email warning: *Verify sender 
qubes-users+bncbct5hvg33eerbs4julyqkgqezk4s...@googlegroups.com before 
clicking links or attachments


I have tried to debug it further. Unfortunately, I am unable to attach 
the VM's drive to a DVM:


$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'


How can I do that?


Would this help?

How to mount LVM image
https://www.qubes-os.org/doc/mount-lvm-image/



Regards,
Vít Šesták 'v6ak'

--
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/6e388d39-6ef4-4035-80be-23b7e9d1eab6%40googlegroups.com 
.


--
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/c1083eec-9f7e-df0a-3af0-c8dd5a56b67f%40jhuapl.edu.

Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

[Scott Russell]

Hi,
 Yes, so I go a bit further.  I was actually looking for /dev/xvdi in
the work vm, but it never appeared.  I had seen /dev/sda, but having run
qvm-block in DOM0, I was really looking for the /dev/xvdi as the device in
the work vm.  Anyway, once I realised I was looking for /dev/sda1 then it
was all easy(your prompting of check dmesg worked).   Networking was still
an issue, so I managed to find and old asus USB-N13 usb network adapter,
which was recognised by the kernel.  So, suddenly I was working.  Next I
thought I would update the kernel to the llatest.  I got 5.4.16?  Well, I
am not really sure, now, as when I reboot it just will not log me in.  Just
reboots every time I login.  It was working fire with the stable kernel,
just not latest.
   Thanks for taking the time to respond.  I knew I was doing something
totally silly.   Any ideas on how to revert to the old kernel so I can
recover would be appreciated.

Sc0tt


On Wed, 22 Jan 2020 at 12:27, Ilpo Järvinen 
wrote:

> On Wed, 22 Jan 2020, Scott Russell wrote:
>
> > HI, So, since I have no networking, I decided to install the
> networking
> > via a usb pen drive.  However, I seem unable to mount the usb drives in
> any
> > vm, tried the fedora-29 template, and also the work vm, or sys-firewall.
> > But each time I click the icon to attach, it reports successfully
> attached,
> > but when I go to the vm, it does not show up.  I can see from qvm-block
> that
> > is is attached from dom0, also tried manually attaching via command line,
> > but again, it reports attached, but cannot see in the work vm that it is
> > thre.  but when I do a "df -h" or try to list the devices in /dev/xvdi,
> it
> > is not there on the work vm.  It seems like a pretty simple thing to
> > attach the pendrive.  I have tried several pen drives, but seem unable to
> > mount them in any vm.  Have re-read the docs several times, and no-one
> seems
> > to have this issue, so I am probably doing something fundamentally
> wrong?
> > Any advice or hints greatly appreciated?.
>
> I have some problem in understanding what exactly you're doing here as
> your description seems to mix "attaching" and "mounting". In addition
> to attaching the block device, you may have to mount the block device
>   mount /dev/xvdi /home/user/somepath
> as a separate step to get it to appear under /home/user/somepath (and df
> will only show mounted drives).
>
> Or did you try to say there's no /dev/xvdi device? ...In that case, check
> the dmesg if the device is detected by the kernel.
>
> --
>  i.
>
>
> > On Tue, 14 Jan 2020 at 13:14, Ilpo Järvinen <
> ilpo.jarvi...@cs.helsinki.fi>
> > wrote:
> >   On Tue, 14 Jan 2020, Scott Russell wrote:
> >
> >   > Hi,   I am installing qubes to an X1 gen2 extreme.  Gone well
> >   so far, but
> >   > then I stumbled into a problem with wifi.  Unfortunately the
> >   intel ax200 is
> >   > not supported in linux kernel till after kernel5-1+.  (
> https://www.intel.com/content/www/us/en/support/articles/05511/
> >   networ
> >   > k-and-i-o/wireless-networking.html).
> >
> >   I didn't get AX 200 to work myself and I just use a stop-gap USB
> >   WLAN
> >   dongle solution currently. I tried with latest kernels, various
> >   firmware
> >   versions, and even went to dkms backport of iwlwifi but none of
> >   those
> >   worked.
> >
> >   It just seems the iwlwifi driver, despite claims of AX 200 being
> >   supported
> >   since 5.1, may not work for all (some have gotten it to work but
> >   I'm not
> >   sure if anyone among them with Qubes).
> >
> >   > So, I was wondering on what my options would be.  My first
> >   thought having
> >   > reviewed a few posts, was that I would need to compile the
> >   latest kernel and
> >   > use this in the sys-net.
> >   > Then, I thought, maybe there is already a "latest kernel"
> >   somewhere that I
> >   > could just install without the need for compiling a new one.
> >
> >   Yes, kernel-latest package is already available using
> >   qubes-dom0-update.
> >   Certainly worth a test.
> >
> >   > As an aside, does this mean I should change the underlying
> >   template for
> >   > sys-net and logically the sys-firewall, or should I keep the
> >   sys-net as a
> >   > custom kernel version only.  If there are other ways, any
> >   advice is
> >   > appreciated.   A lot to learn here, but happy to work through
> >   any
> >   > suggestions.
> >
> >   Kernel version, when provided from dom0, is independent of the
> >   template.
> >   It is possible to use the kernel from the template if you set
> >   "kernel"
> >   of the VM to empty (for HVMs).
> >
> >   > So, the question is ,can I upgrade the kernel from 4.4.x to
> >   5.1+ in an easy
> >   > and safe way, or am I driven to playing

Aw: Re: Re: [qubes-users] Installation freezes before displaying installer - UEFI-Troublshooting impossible

[anbe2015]

Hello Claudia, hello Tobias,

 

>> $ mount -l

>> $ /dev/sdb1 on media/username/Qubes-R4.0.2-x86_64 type iso9660

>
> There's your problem. It's mounted with the "ro" flag. Not sure why, but it should be easy to get around.

 

Unfortunately not...

 

> Try this first:
> sudo mount -o remount,rw /dev/sdb1 /media/username/Qubes*

 

Result is: mount: cannot remount /dev/sdb1 read-write, is write-protected

 


> Or, if that doesn't work, do this instead:
> sudo umount /dev/sdb1
> sudo mount /dev/sdb1 /mnt

 

Result is here: mount: /dev/sdb1 is write-protected, mounting read-only

 

 

I tried both, as normal user with sudo and as root-user (sudo -s and then the suggested commands above).

 

The content of the original downloaded *.iso-file from QubesOS is read-only, so it transfered it to the usb-stick with dd read-only, too.

 

Actually I tried it with the ISO-File for version R4.0.3, too, but still the same problem as with R4.0.2. The ISO-File-Content, what is transfered to USB-Stick is read-only. I know it, cause I do the troubleshooting as discribed under "https://www.qubes-os.org/doc/uefi-troubleshooting/", directly in the ISO-File, too.



 



-- 
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/trinity-679d21da-6311-4c96-ac0e-22d286b7e294-1579718499110%403c-app-webde-bap07.

[qubes-users] Re: Write-error on swap-device after having a full storage

[Vít Šesták]

I have tried to debug it further. Unfortunately, I am unable to attach the 
VM's drive to a DVM:

$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'

How can I do that?

Regards,
Vít Šesták 'v6ak'

-- 
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/6e388d39-6ef4-4035-80be-23b7e9d1eab6%40googlegroups.com.

[qubes-users] Re: Write-error on swap-device after having a full storage

[Vít Šesták]

I have tried to debug it further. Unfortunately, I am unable to attach the 
VM's drive to a DVM:

$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'

How can I do that?

Regards,
Vít Šesták 'v6ak'

On Wednesday, January 22, 2020 at 1:43:00 PM UTC+1, Vít Šesták wrote:
>
> Hello,
> I have done this:
>
> 1. Started a template VM update.
> 2. It seems to have run out of space during the update.
> 3. I extended the storage.
>
> Expected result: After extending the storage, it works again.
>
> Actual result: I can boot neither the VM nor the related Template-based 
> VMs. When I try to do so, it switches to emergency mode and I cannot do 
> anything with the VM. It shuts down quickly.
>
> Excerpt from the log:
>  
> https://gist.github.com/v6ak/6685d7b6b686076ff9486bd60d2950e0
>
> This is very strange. The swap file is created again and again on start, 
> isn't it? So, there cannot be no relict from the last run, can it?
>
> Other TemplateVMs work correctly.
>
> Regards,
> Vít Šesták 'v6ak'
>

-- 
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/7eb29a3c-e40a-4e92-86ae-27f7294c7027%40googlegroups.com.

[qubes-users] MWC Barcelona 2020 Event Attendee list

[Lindsey Bushman]

Hi, I hope you are doing well.



I was on company’s website recently and found your company as a part of *MWC
Barcelona 2020Event.*



I am just trying to connect with you to see if you have any interest in
acquiring *Attendee contacts for MWC Barcelona 2020 Event, *which will help
you to drive more traffic to your booth at the show and also helps you for
your marketing and demand generation activities.



Kindly let me know your interest, so that I can get back to you with
counts, pricing and other data guarantees for your review.



I look forward to hear back from you. Thank you.



Regards,

*Lindsey Bushman** | Marketing specialist*

-- 
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/CAPEnDf3y3LgjR%3D73zDnp_GwJoZZXBq9cmvZHQe5qLe%3DsHXu02g%40mail.gmail.com.

Re: [qubes-users] Upgrading/creating "special" VMs (sys-net, vault, etc)

[Claudia]

January 22, 2020 12:21 PM, "unman"  wrote:

> On Wed, Jan 22, 2020 at 03:09:31AM +, Claudia wrote:
> 
>> January 21, 2020 7:04 PM, "Dan Krol"  wrote:
>> 
>> So to clarify:
>> 
>> Sys-net and sys-firewall (and sys-vpn if you use it) will need it enabled.
>> 
>> When you say "need it enabled", you're just referring again to "provides 
>> network", is that correct?
>> 
>> And secondly: Do I understand correctly so long as any qube sits in between 
>> two other qubes in the
>> networking chain, it automatically acts as a basic firewall? That's all that 
>> sys-firewall is?
>> 
>> From what I understand, sys-firewall is special in that it dynamically 
>> changes firewall rules for
>> different VMs. That's where the firewall rules in the VM Settings GUI and 
>> qvm-firewall are applied.
>> If you just create a new blank VM in place of sys-firewall, you can set up 
>> static firewall rules,
>> but it won't by default know how to do any of the dynamic / user-defined 
>> rule stuff.
> 
> This isn't quite true - there's nothing special about sys-firewall. *Any* qube
> which provides network (and has relevant packages installed) will
> provide dynamic firewall. If you use the full templates it will work
> automatically.

O, so that's what "provides network" means? Now it's starting to make 
sense. Thanks for clarifying.

Is there anything special about any VMs, other than:
dom0: obviously
debian-10, fedora-30, whonix-{ws,gw}-15: install path is controlled by rpm, 
i.e. reinstalling the package would overwrite the templateVM image - unlike a 
user-created or cloned TemplateVM
sys-net: provides network, assigned PCI network devices by default, clocksyncd 
service
sys-usb: assigned USB controllers by default
sys-firewall: provides network, netVM=sys-net (as opposed to the global default 
of sys-firewall or sys-whonix)
sys-whonix: provides network, netVM=sys-firewall (as opposed to the global 
default of sys-whonix in some installations)

So in other words, you could delete any of these, and then just make a new VM 
with the same template and the same VM settings, and it would function just 
like the original, without any modifications inside the VM itself?

I've heard that recreating a broken sys-net for example is not that simple, so 
I assumed there was something special about the sys-* VMs (or at least 
sys-net). Is that not actually the case?

-- 
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/c3317508c056ed1da28cddac69d8ca63%40disroot.org.

Re: Aw: Re: [qubes-users] Installation freezes before displaying installer - UEFI-Troublshooting impossible

[Claudia]

January 22, 2020 11:36 AM, anbe2...@joker.ms wrote:

> Hello Claudia,
> 
> thanks so much for your answer.
> 
>> Once you write the image file with dd, you should be able to mount the ext3 
>> /boot filesystem
> read/write
> 
>> just like you would any partition on a flash drive. It should no longer 
>> appear as an iso once
> it's written to
> 
>> the flash drive, it should show up like an external hard drive would. You 
>> may have to unplug it
> and plug it
> 
>> back in for the kernel to recognize the new partitions on it. Also, make 
>> sure you're writing to
> /dev/sdb
> 
>> and not /dev/sdb1 for example.
> 
> My system mounts the usb-stick as following:
> 
> $ mount -l
> 
> $ /dev/sdb1 on media/username/Qubes-R4.0.2-x86_64 type iso9660
> (ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=40
> ,uhelper=udisks2) [Qubes-R4.0.2-x86_64]

There's your problem. It's mounted with the "ro" flag. Not sure why, but it 
should be easy to get around.

> Can you say me the exact command I have to write into my terminal to mount 
> the ext3 / boot
> filesystem read/write just you mentioned above?

Try this first:

sudo mount -o remount,rw /dev/sdb1 /media/username/Qubes*
sudo nano /media/username/Qubes*/EFI/BOOT/BOOTX64.cfg
sudo umount /dev/sdb1

Or, if that doesn't work, do this instead:

sudo umount /dev/sdb1
sudo mount /dev/sdb1 /mnt
sudo nano /mnt/EFI/BOOT/BOOTX64.cfg
sudo umount /mnt


>> Actually, are you getting "Read-only filesystem" or "Permission denied" when 
>> you mount the first
> partition
> 
>> of the USB drive (not the iso file) and edit BOOTX64.cfg?
> 
> The filesystem ist "read-only".
> 
>> Also, try a different flash drive if you have one. It's possible it's 
>> showing up as write
> protected for one
>> reason or another which causes the fs to be mounted readonly.
> 
> Same problem with another usb-stick.
> 
>> Alternatively, I once had an issue with the installer freezing, and I was 
>> able to get around it
> by repeatedly
>> pressing ctrl-alt-f2 early during the boot process, and about 50% of the 
>> time it would change
> TTYs without
>> freezing and then I could switch back to the graphical installer on TTY1. I 
>> don't know if it has
> worked for
>> anyone else, but it might be worth a try.
> 
> Unfortunately it doesn't work.
> 
> These are the last lines, before my installation-process freezes:
> 
> [XEN] echoes
> 3...2...1...
> Xen is relinquishing VGA console
> 
> and then the black screen and after a moment, the system shuts down. if I try 
> it with plugged power
> cord, the system boots after the black screen and than the same thing again 
> and again...

-- 
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/eac8e5890e5b9549a11f13e983f144b2%40disroot.org.

Re: [qubes-users] Re: qvm-create-windows-qube 2.0

[unman]

On Mon, Jan 20, 2020 at 10:35:43PM +, River~~ wrote:
> On 17:33, Mon, 20 Jan 2020 unman  >
> >
> > So what you mean is that *your* Debian-9 template (updated) does not
> > work as a template for sys-XXX qubes on *your* hardware.
> > That's different.
> 
> I think you are missing my point here. The Fedora templates do work on both
> my laptops, the (older) Debian templates didn't.
> 
> My expectation, which seems reasonable to me, was that the so called "full"
> Debian template would be a drop in replacement for the full Fedora one, and
> in fact that expectation turns out to be false: further work is needed to
> make it work in some cases, including mine.
> 
> The fact that it happens to work on some other hardware does not alter the
> fact that (at the time those Debian templates were issued) they were not
> drop in replacements.
> 
> The fact that other ppl have hardware that fortuitously avoids that
> difference is good luck for you but does not negate my point.
> 

I think your expectation is misplaced - they are different distros, with
different packages, and even where packages *seem* to be the same, their
contents may differ.
Hardware support is difficult. In *many* cases the templates will be
interchangeable. In some, not. You will often see people here being advised to
switch templates to resolve hardware issues for this very reason.

Your original post seemed to suggest that the Debian template didn't come
with packages required to act as sys-XXX - this isn't true. It *may* lack
packages required for some hardware - just install them. (The same is
true for the Fedora templates)

-- 
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/20200122125143.GA5906%40thirdeyesecurity.org.

[qubes-users] Write-error on swap-device after having a full storage

[Vít Šesták]

Hello,
I have done this:

1. Started a template VM update.
2. It seems to have run out of space during the update.
3. I extended the storage.

Expected result: After extending the storage, it works again.

Actual result: I can boot neither the VM nor the related Template-based 
VMs. When I try to do so, it switches to emergency mode and I cannot do 
anything with the VM. It shuts down quickly.

Excerpt from the log:
 
https://gist.github.com/v6ak/6685d7b6b686076ff9486bd60d2950e0

This is very strange. The swap file is created again and again on start, 
isn't it? So, there cannot be no relict from the last run, can it?

Other TemplateVMs work correctly.

Regards,
Vít Šesták 'v6ak'

-- 
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/5cf927e1-fc0a-4ad2-b00b-b00232b4944b%40googlegroups.com.

Re: [qubes-users] Upgrading/creating "special" VMs (sys-net, vault, etc)

[unman]

On Wed, Jan 22, 2020 at 03:09:31AM +, Claudia wrote:
> January 21, 2020 7:04 PM, "Dan Krol"  wrote:
> 
> > So to clarify:
> > 
> >> Sys-net and sys-firewall (and sys-vpn if you use it) will need it enabled.
> > 
> > When you say "need it enabled", you're just referring again to "provides 
> > network", is that correct?
> > 
> > And secondly: Do I understand correctly so long as any qube sits in between 
> > two other qubes in the
> > networking chain, it automatically acts as a basic firewall? That's all 
> > that sys-firewall is?
> 
> >From what I understand, sys-firewall is special in that it dynamically 
> >changes firewall rules for different VMs. That's where the firewall rules in 
> >the VM Settings GUI and qvm-firewall are applied. If you just create a new 
> >blank VM in place of sys-firewall, you can set up static firewall rules, but 
> >it won't by default know how to do any of the dynamic / user-defined rule 
> >stuff.
> 

This isn't quite true - there's nothing special about sys-firewall. *Any* qube
which provides network (and has relevant packages installed) will
provide dynamic firewall. If you use the full templates it will work
automatically.

-- 
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/20200122122131.GB5704%40thirdeyesecurity.org.

Aw: Re: [qubes-users] Installation freezes before displaying installer - UEFI-Troublshooting impossible

[anbe2015]

Hello Claudia,

thanks so much for your answer.

 

> Once you write the image file with dd, you should be able to mount the ext3 /boot filesystem read/write

> just like you would any partition on a flash drive. It should no longer appear as an iso once it's written to

> the flash drive, it should show up like an external hard drive would. You may have to unplug it and plug it

> back in for the kernel to recognize the new partitions on it. Also, make sure you're writing to /dev/sdb

> and not /dev/sdb1 for example.

 

My system mounts the usb-stick as following:

$ mount -l

$ /dev/sdb1 on media/username/Qubes-R4.0.2-x86_64 type iso9660 (ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400,uhelper=udisks2) [Qubes-R4.0.2-x86_64]

 

Can you say me the exact command I have to write into my terminal to mount the ext3 / boot filesystem read/write just you mentioned above?

 

 

> Actually, are you getting "Read-only filesystem" or "Permission denied" when you mount the first partition

> of the USB drive (not the iso file) and edit BOOTX64.cfg?

 

The filesystem ist "read-only".

 

 

> Also, try a different flash drive if you have one. It's possible it's showing up as write protected for one

> reason or another which causes the fs to be mounted readonly.

 

Same problem with another usb-stick.

 

 

> Alternatively, I once had an issue with the installer freezing, and I was able to get around it by repeatedly

> pressing ctrl-alt-f2 early during the boot process, and about 50% of the time it would change TTYs without

> freezing and then I could switch back to the graphical installer on TTY1. I don't know if it has worked for

> anyone else, but it might be worth a try.

 

Unfortunately it doesn't work.

 

 

These are the last lines, before my installation-process freezes:

 

[XEN] echoes

3...2...1...

Xen is relinquishing VGA console

 

and then the black screen and after a moment, the system shuts down. if I try it with plugged power cord, the system boots after the black screen and than the same thing again and again...

 



-- 
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/trinity-bd8a094a-8f31-46a4-bc44-5860b7473c97-1579692987055%403c-app-webde-bs36.

Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

['awokd' via qubes-users]

Scott Russell:
> HI,
> So, since I have no networking, I decided to install the networking via
> a usb pen drive.  However, I seem unable to mount the usb drives in any vm,
> tried the fedora-29 template, and also the work vm, or sys-firewall.  But
> each time I click the icon to attach, it reports successfully attached, but
> when I go to the vm, it does not show up.  I can see from qvm-block that is
> is attached from dom0, also tried manually attaching via command line, but
> again, it reports attached, but cannot see in the work vm that it is thre.
> but when I do a "df -h" or try to list the devices in /dev/xvdi, it is not
> there on the work vm.  It seems like a pretty simple thing to attach the
> pendrive.  I have tried several pen drives, but seem unable to mount them
> in any vm.  Have re-read the docs several times, and no-one seems to have
> this issue, so I am probably doing something fundamentally wrong?  Any
> advice or hints greatly appreciated?.

I had this problem yesterday as well, with /dev/xvdi not appearing. Try
updating dom0 and your templates and rebooting. It worked for me after that.

-- 
- 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/e99c28b2-bf1b-2ae8-d6e9-e1fe9197bd43%40danwin1210.me.

Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

['Ilpo Järvinen' via qubes-users]

On Wed, 22 Jan 2020, Scott Russell wrote:

> HI,     So, since I have no networking, I decided to install the networking
> via a usb pen drive.  However, I seem unable to mount the usb drives in any
> vm, tried the fedora-29 template, and also the work vm, or sys-firewall. 
> But each time I click the icon to attach, it reports successfully attached,
> but when I go to the vm, it does not show up.  I can see from qvm-block that
> is is attached from dom0, also tried manually attaching via command line,
> but again, it reports attached, but cannot see in the work vm that it is
> thre.  but when I do a "df -h" or try to list the devices in /dev/xvdi, it
> is not there on the work vm.  It seems like a pretty simple thing to
> attach the pendrive.  I have tried several pen drives, but seem unable to
> mount them in any vm.  Have re-read the docs several times, and no-one seems
> to have this issue, so I am probably doing something fundamentally wrong? 
> Any advice or hints greatly appreciated?. 

I have some problem in understanding what exactly you're doing here as
your description seems to mix "attaching" and "mounting". In addition
to attaching the block device, you may have to mount the block device
  mount /dev/xvdi /home/user/somepath
as a separate step to get it to appear under /home/user/somepath (and df 
will only show mounted drives).

Or did you try to say there's no /dev/xvdi device? ...In that case, check 
the dmesg if the device is detected by the kernel.

-- 
 i.


> On Tue, 14 Jan 2020 at 13:14, Ilpo Järvinen 
> wrote:
>   On Tue, 14 Jan 2020, Scott Russell wrote:
> 
>   > Hi,   I am installing qubes to an X1 gen2 extreme.  Gone well
>   so far, but
>   > then I stumbled into a problem with wifi.  Unfortunately the
>   intel ax200 is
>   > not supported in linux kernel till after kernel5-1+.  
> (https://www.intel.com/content/www/us/en/support/articles/05511/
>   networ
>   > k-and-i-o/wireless-networking.html).  
> 
>   I didn't get AX 200 to work myself and I just use a stop-gap USB
>   WLAN
>   dongle solution currently. I tried with latest kernels, various
>   firmware
>   versions, and even went to dkms backport of iwlwifi but none of
>   those
>   worked.
> 
>   It just seems the iwlwifi driver, despite claims of AX 200 being
>   supported
>   since 5.1, may not work for all (some have gotten it to work but
>   I'm not
>   sure if anyone among them with Qubes).
> 
>   > So, I was wondering on what my options would be.  My first
>   thought having
>   > reviewed a few posts, was that I would need to compile the
>   latest kernel and
>   > use this in the sys-net. 
>   > Then, I thought, maybe there is already a "latest kernel"
>   somewhere that I
>   > could just install without the need for compiling a new one.
> 
>   Yes, kernel-latest package is already available using
>   qubes-dom0-update.
>   Certainly worth a test.
> 
>   > As an aside, does this mean I should change the underlying
>   template for
>   > sys-net and logically the sys-firewall, or should I keep the
>   sys-net as a
>   > custom kernel version only.  If there are other ways, any
>   advice is
>   > appreciated.   A lot to learn here, but happy to work through
>   any
>   > suggestions.   
> 
>   Kernel version, when provided from dom0, is independent of the
>   template.
>   It is possible to use the kernel from the template if you set
>   "kernel"
>   of the VM to empty (for HVMs).
> 
>   > So, the question is ,can I upgrade the kernel from 4.4.x to
>   5.1+ in an easy
>   > and safe way, or am I driven to playing with the
>   kernel compilation?
> 
> 
>   --
>    i.
> 
> 
>

-- 
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/alpine.DEB.2.20.2001221219130.25645%40whs-18.cs.helsinki.fi.

Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme

[Scott Russell]

HI,
So, since I have no networking, I decided to install the networking via
a usb pen drive.  However, I seem unable to mount the usb drives in any vm,
tried the fedora-29 template, and also the work vm, or sys-firewall.  But
each time I click the icon to attach, it reports successfully attached, but
when I go to the vm, it does not show up.  I can see from qvm-block that is
is attached from dom0, also tried manually attaching via command line, but
again, it reports attached, but cannot see in the work vm that it is thre.
but when I do a "df -h" or try to list the devices in /dev/xvdi, it is not
there on the work vm.  It seems like a pretty simple thing to attach the
pendrive.  I have tried several pen drives, but seem unable to mount them
in any vm.  Have re-read the docs several times, and no-one seems to have
this issue, so I am probably doing something fundamentally wrong?  Any
advice or hints greatly appreciated?.



On Tue, 14 Jan 2020 at 13:14, Ilpo Järvinen 
wrote:

> On Tue, 14 Jan 2020, Scott Russell wrote:
>
> > Hi,   I am installing qubes to an X1 gen2 extreme.  Gone well so far, but
> > then I stumbled into a problem with wifi.  Unfortunately the intel ax200
> is
> > not supported in linux kernel till after kernel 5-1+.  (
> https://www.intel.com/content/www/us/en/support/articles/05511/networ
> > k-and-i-o/wireless-networking.html).
>
> I didn't get AX 200 to work myself and I just use a stop-gap USB WLAN
> dongle solution currently. I tried with latest kernels, various firmware
> versions, and even went to dkms backport of iwlwifi but none of those
> worked.
>
> It just seems the iwlwifi driver, despite claims of AX 200 being supported
> since 5.1, may not work for all (some have gotten it to work but I'm not
> sure if anyone among them with Qubes).
>
> > So, I was wondering on what my options would be.  My first thought having
> > reviewed a few posts, was that I would need to compile the latest kernel
> and
> > use this in the sys-net.
> > Then, I thought, maybe there is already a "latest kernel" somewhere that
> I
> > could just install without the need for compiling a new one.
>
> Yes, kernel-latest package is already available using qubes-dom0-update.
> Certainly worth a test.
>
> > As an aside, does this mean I should change the underlying template for
> > sys-net and logically the sys-firewall, or should I keep the sys-net as a
> > custom kernel version only.  If there are other ways, any advice is
> > appreciated.   A lot to learn here, but happy to work through any
> > suggestions.
>
> Kernel version, when provided from dom0, is independent of the template.
> It is possible to use the kernel from the template if you set "kernel"
> of the VM to empty (for HVMs).
>
> > So, the question is ,can I upgrade the kernel from 4.4.x to 5.1+ in an
> easy
> > and safe way, or am I driven to playing with the kernel compilation?
>
>
> --
>  i.

-- 
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/CAAvfSa%2BZ1n%2BDTe699epXuTpa5_5EwqtsKA6VM9q1pYGVzpRdBQ%40mail.gmail.com.