[qubes-users] Re: Qubes support for PS2 mouse / keyboard

2017-07-07 Thread 0spinboson
There are quite a lot of 'modern' HIDs that no longer support ps/2 via 
converter; google may be able to tell you whether your devices do. ps/2 should 
'just work', unless you built and are running a kernel with support disabled.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9b28b9de-9463-4ce5-8b12-51a473ab0854%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-06 Thread 0spinboson
fyi: Ryzen pinctrl/gpio issue should be fixed in 4.11.9; not yet backported to 
4.9: 

commit 0ec03ce7d79dc9a5c47d26bab38c78075d42de9c
Author: Thomas Gleixner
Date:   Tue May 23 23:23:32 2017 +0200

pinctrl/amd: Use regular interrupt instead of chained

commit ba714a9c1dea85e0bf2899d02dfeb9c70040427c upstream.

The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO
interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up
hard on boot when the AMD pinctrl driver is initialized. The reason is an
interrupt storm. It's not clear whether that's caused by hardware or
firmware or both.

Using chained interrupts on X86 is a dangerous endavour. If a system is
misconfigured or the hardware buggy there is no safety net to catch an
interrupt storm.

Convert the driver to use a regular interrupt for the demultiplex
handler. This allows the interrupt storm detector to catch the malfunction
and lets the system boot up.

This should be backported to stable because it's likely that more users run
into this problem as the AMD Ryzen machines are spreading.

Reported-by: Kevin Vandeventer
Link: https://bugzilla.suse.com/show_bug.cgi?id=1034261

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ef96e304-398d-4082-bcc3-85b1efe67de9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to Switch Keyboard Layouts?

2017-07-04 Thread 0spinboson
On Tuesday, July 4, 2017 at 11:11:56 PM UTC+2, J. Eppler wrote:
> Hello, 
> 
> how can I switch keyboard layouts in a AppVM? I tried to use the XCFE menu 
> item to switch layouts. However, it only works for Dom0. In addition, I tried 
> to use xkb-switch, but without much success. Interesting about xkb-switch is 
> the fact, that it shows I use a US layout in the VM, which is surprising 
> because I use a QWERTZ (German) layout and it works. I wonder where the 
> keyboard layout information are stored.
> 
> Back to the keyboard layout switching. I would like to be able to switch my 
> keyboard layout multiple times while working in a VM. Does anybody has a 
> solution or idea on how to achieve it?

rightclicking the entry in the Qubes Manager, set keyboard layout, doesn't work?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/67e79060-ef35-4e8d-8d24-c08496d0eb19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to enlarge the size of hvm?

2017-07-01 Thread 0spinboson
On Saturday, July 1, 2017 at 9:13:40 AM UTC+2, jaki...@gmail.com wrote:
> Guess I didn't make myself clear. I meant the size of the display itself not 
> the size of storage. 
> 
> In Qubes manager I only see the disk storage, and memory CPU. I'm not seeing 
> any settings in relation to the display. 
> 
> Inside the vm in display settings my resolution is at max option of 1024x68.

I see. No, that is something that just follows from the screen size for me 
(with seamless mode disabled). E.g. when I tell it to use the left side of the 
screen, the Qubes Video Driver changes the resolution on the fly. Did you 
install the Qubes Windows tools?

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e2e0c0de-921d-4d2e-8605-fb50f40afa09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to enlarge the size of hvm?

2017-07-01 Thread 0spinboson
On Saturday, July 1, 2017 at 12:13:31 AM UTC+2, jaki...@gmail.com wrote:
> Where in Qubes manager is the hvm size displayed?

... Right-click the entry in the Manager, then choose settings. Increase to 
desired size.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/602de063-1744-4f2b-9395-06962eb42219%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to enlarge the size of hvm?

2017-06-30 Thread 0spinboson
On Friday, June 30, 2017 at 9:42:58 PM UTC+2, jaki...@gmail.com wrote:
> I just installed Windows 7pro but can't find how to resize the VM to 
> something larger. Can someone link me the info for that?

Enlarge in the Qubes Manager, then open Computer Management inside the VM and 
expand the partition to match the new size.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/601272c2-f584-4868-8bd5-e520a0c0fce5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [qubes-devel] Re: Re: Request for feedback: 4.9 Kernel

2017-06-29 Thread 0spinboson
On Thursday, June 29, 2017 at 10:10:43 PM UTC+2, Reg Tiangha wrote:
> On 06/29/2017 04:59 AM,
> 0spinbo...@gmail.com wrote:
> > fyi: this kernel built as-is will cause kernel panics on (some, common) 
> > Ryzen motherboards. Issue is described here among other places: 
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
> > This happens as soon as config_pinctrl_amd is set to 'm' in the build 
> > config. Un-setting it should evade the issue (as I've not yet seen a proper 
> > fix for it).
> >
> 
> I've now disabled it in my branch. But reading through the thread, they
> say it's been fixed but I can't figure out what part in their changelog
> addresses it. Did they merely disable the kernel option as well, or was
> there an actual patch? Latest 4.9 version is now 4.9.35 and there
> doesn't seem to be anything obvious in the .34 and .35 changlogs that I
> can see that addresses it either. But then again, maybe I don't know
> what I'm looking for.

I couldn't tell either, other than that they seem to have moved to a newer 
branch. Very messy bug thread, to be sure.
The option seems to be disabled in some distro-shipped kernels (such as f26, 
iirc), so not everyone runs into it either, which made it seem distro-specific.

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3b2fede2-e649-4cd0-a2ee-100bed519219%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-devel] Re: [qubes-users] Re: Request for feedback: 4.9 Kernel

2017-06-29 Thread 0spinboson
fyi: this kernel built as-is will cause kernel panics on (some, common) Ryzen 
motherboards. Issue is described here among other places: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
This happens as soon as config_pinctrl_amd is set to 'm' in the build config. 
Un-setting it should evade the issue (as I've not yet seen a proper fix for it).

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7c97c7d2-5199-451a-99e9-ca9fea95ae71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HOWTO: Compiling Kernels for dom0

2017-06-27 Thread 0spinboson
On Tuesday, June 27, 2017 at 10:42:51 PM UTC+2, Reg Tiangha wrote:
> On 2017-06-27 1:53 PM, Reg Tiangha wrote:
> > On 2017-06-27 1:37 PM,
> > 0spinboson wrote:
> > 
> >> Thanks. Was already up to date, though, and all gzip-related options were 
> >> enabled (as before). Only change was a new package req 
> >> (elfutils-libelf-devel).
> >> As for new info, I have frustratingly little to offer:
> >> -
> >>  mkdir -p 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18
> >> + 
> >> PATH=/sbin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/user/.local/bin:/home/user/bin
> >> + dracut --nomdadmconf --nolvmconf --kmoddir 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64/lib/modules/4.11.7-18.pvops.qubes.x86_64
> >>  --modules 'kernel-modules qubes-vm-simple' --conf /dev/null --confdir 
> >> /var/empty -d 'xenblk xen-blkfront cdrom ext4 jbd2 crc16 dm_snapshot' 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >>  4.11.7-18.pvops.qubes.x86_64
> >> Kernel version 4.11.7-18.pvops.qubes.x86_64 has no module directory 
> >> /lib/modules/4.11.7-18.pvops.qubes.x86_64
> >> ldconfig: need absolute file name for configuration file when using -r
> >> dracut: ldconfig might need uid=0 (root) for chroot()
> >> ++ lsinitrd 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >>  usr/lib/modules/4.11.7-18.pvops.qubes.x86_64/modules.dep
> >> + modules_dep=
> >> + '[' -z '' ']'
> >> ++ mktemp -d
> >> + tmpdir=/tmp/tmp.0U02gQXJIH
> >> + zcat 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >> + cpio -imd -D /tmp/tmp.0U02gQXJIH
> >>
> >> gzip: 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs:
> >>  not in gzip format
> >> cpio: premature end of archive
> >> + exit 1
> >> error: Bad exit status from /var/tmp/rpm-tmp.MAZxNe (%install)
> >> 
> >> (If there is a way to get more (relevant) information, you'll have to tell 
> >> me where to (start) look(ing), sorry.)
> >>
> > 
> > 
> > Curious:  What is your build environment for this kernel? I only ever
> > use/test FC23 because that's what my dom0 runs, but there have been
> > issues when the compile environment is different (ex. FC25).
> > 
> > I've only ever gotten gzip errors if I completely remove gzip support
> > from my config options, but I've only seen it appear at boot and not at
> > compile time.
> > 
> 
> Also, are you using the 4.11 patches from the Hardened Kernel project? I
> remember rpm generation failing one time (can't remember the exact error
> message) with one version of their patches (it patched in properly and
> successfully compiled, but just died when it came to generating the
> rpms), which eventually got fixed in a later revision. If you're using
> them but haven't updated it recently, their latest version is 4.11.7.a:
> 
> https://github.com/copperhead/linux-hardened/releases
> 
> I also have a branch that tracks just that, which is essentially the
> same as my devel-4.11 branch but just adds in and updates the
> linux-hardened patches as those get released, mainly for convenience:
> 
> https://github.com/rtiangha/qubes-linux-kernel/tree/devel-4.11-hard

It seems building works fine on fc23. Wonder what changed between 6/17 and 
today that fc25 no longer compiles kernels, though.

Wasn't using any patches from the hardening project. 

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e5c7979e-9338-45f9-aa6d-7f51aaa65f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HOWTO: Compiling Kernels for dom0

2017-06-27 Thread 0spinboson
On Tuesday, June 27, 2017 at 8:28:55 PM UTC+2, Reg Tiangha wrote:
> On 06/27/2017 08:09 AM, Epitre wrote:
> > Le mardi 27 juin 2017 12:40:00 UTC+2, 0spin...@gmail.com a écrit :
> >> Anyone have an idea why, since 4.11.7, I am always getting a "initramfs 
> >> not in gzip format" error?
> > Hi, same problem for me with 4.11.7. I also tried to select only AMD family 
> > (my type of processor) and it results the same.
> >
> 
> I just tried 4.11.7 for myself on my machine, and it works fine in both
> dom0 and in VMs.
> 
> So, if you're using my development branch, make sure to run 'git pull'
> to ensure everything is synced up (for example, if you haven't done it
> in a while, then you may not have the XSA 216 security patches applied
> to your kernel that were released last week):
> 
> https://github.com/rtiangha/qubes-linux-kernel/tree/devel-4.11
> 
> Otherwise, make sure your config file has these options set (use 'make
> menuconfig' and search for them to ensure they're set correctly):
> 
> CONFIG_HAVE_KERNEL_GZIP=y
> 
> CONFIG_RD_GZIP=y
> 
> CONFIG_DECOMPRESS_GZIP=y
> 
> 
> If that still doesn't work, then more information is needed. But for
> now, try the above and see if that works.

Thanks. Was already up to date, though, and all gzip-related options were 
enabled (as before). Only change was a new package req (elfutils-libelf-devel).
As for new info, I have frustratingly little to offer:
-
 mkdir -p 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18
+ 
PATH=/sbin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/user/.local/bin:/home/user/bin
+ dracut --nomdadmconf --nolvmconf --kmoddir 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64/lib/modules/4.11.7-18.pvops.qubes.x86_64
 --modules 'kernel-modules qubes-vm-simple' --conf /dev/null --confdir 
/var/empty -d 'xenblk xen-blkfront cdrom ext4 jbd2 crc16 dm_snapshot' 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
 4.11.7-18.pvops.qubes.x86_64
Kernel version 4.11.7-18.pvops.qubes.x86_64 has no module directory 
/lib/modules/4.11.7-18.pvops.qubes.x86_64
ldconfig: need absolute file name for configuration file when using -r
dracut: ldconfig might need uid=0 (root) for chroot()
++ lsinitrd 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
 usr/lib/modules/4.11.7-18.pvops.qubes.x86_64/modules.dep
+ modules_dep=
+ '[' -z '' ']'
++ mktemp -d
+ tmpdir=/tmp/tmp.0U02gQXJIH
+ zcat 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
+ cpio -imd -D /tmp/tmp.0U02gQXJIH

gzip: 
/home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs:
 not in gzip format
cpio: premature end of archive
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.MAZxNe (%install)

(If there is a way to get more (relevant) information, you'll have to tell me 
where to (start) look(ing), sorry.)

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6ba1dd86-75a5-4625-ae40-c283d66a7c72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HOWTO: Compiling Kernels for dom0

2017-06-27 Thread 0spinboson
Anyone have an idea why, since 4.11.7, I am always getting a "initramfs not in 
gzip format" error?

-- 
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4adbb4b5-d1f0-4203-a192-1e7c002c5371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.