Re: [qubes-users] Request for feedback: 4.9 Kernel
On 05/20/2017 03:42 PM, Reg Tiangha wrote: 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9. I have a 4th Generation Lenovo X1 Carbon (Skylake), and I've been running the 4.8.12-12 kernel from the unstable repo for many months now. I just recently upgraded to 4.9.35-19 and post upgrade resume from sleep(suspend) is no longer reliable. Resume was a huge issue when first setting up this laptop and I only had success with the 4.8.12-12 kernel (and also I had to completely disabled TPM in bios), but after that initial setup it's been rock solid. Post upgrade however, every 2nd or 3rd sleep it will fail to resume and I'm forced to hold the power button down. Regards, Ed -- 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/9c51-1c31-5004-bf94-78db0c41f3f7%40edjusted.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 won't boot with newer kernels on Lenovo T450
On 05/10/2017 12:43 AM, kotov@gmail.com wrote: Hey guys, I had been running Qubes 3.1 without any issues on my Lenovo T450, since the support for 3.1 is over I upgraded to 3.2. At first it worked fine but it stopped booting with newer kernels. It goes on infinite booting cycle. I looked through Qubes's website Lenovo Troubleshooting pages and the following group thread https://groups.google.com/forum/#!topic/qubes-users/UXP8RJffpsY, but was unable to resolve my issue with the information found there. I currently have XEN 4.6.5 and the following kernels: 4.4.62-12 - goes to infinite boot 4.4.38-11 - same 4.1.24-10 - boots fine I tried passing noreboot=true to XEN and modeset=0 to Linux as well as console=hvc0 and earlyprintk=0 as suggested here: https://groups.google.com/forum/#!topic/qubes-users/UXP8RJffpsY, with no luck (except it does not reboot of course just freezes with the blank screen). Could you guys point me in the right direction as to how do I troubleshoot this issue. E.g. outputs something to the console. Thanks! I just purchased a Lenovo Thinkpad X1 Carbon 4th Gen and have been installing qubes on it over the past few days. I had the same troubles you are seeing with your T450. Things were fine with the 3.2 installer and the 4.4.14-11 kernel, but as soon as I updated dom0 which gave me a newer kernel (I forgot which, but probably was 4.4.62-12), the system would no longer reliably boot. It appears it would be trying to show me the screen where it would be prompting me for my LUKS password but would freeze at a black screen. I would have to hold the power button down and boot again. The interesting thing was that maybe 1 out of 20 or 30 tries it would actually work, making it kind of feel like a timing or race condition of some kind. I changed the kernel params, removing "quiet" and adding "text" to try and get some idea what was happening, however, the info moved on the screen so fast and the screen totally blanked without me being able to see anything at all about what was happening. I even tried recording it with my phone camera and had no luck. The X1 Carbon does not have a serial port so I can't do any kind of console logging, and I'm quite sure the issue is happening just before or right around when the usb system is initialized so I can't really do any usb serial logging either. I ran out of ideas trying to troubleshoot the issue and decided to try another tack. I booted with the 4.4.14-11 kernel and ran sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable This installed a much newer kernel 4.8.12-12, and all my boot troubles have since gone away. So it seems whatever the issue is with the newer 4.4 kernels it was fixed in newer versions So maybe you will have luck on your T450 with the 4.8 kernel from unstable. Good Luck! Ed -- 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/a03e56ad-e7e2-c5ae-1110-65a6ab2f9bff%40edjusted.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
On 03/10/2017 01:28 AM, Drew White wrote: Problem is, they don't care. I'm new to this OS and new to this community, however, after searching many many threads for info, looking at git/documentation/etc. I really have not gotten this impression at all, I regularly see developers responding to threads and offering assistance. There are bugs in the tools that I pointed out in version 2 of the tools, and they still aren't fixed. The worse the issues got, the more I pressed it, and the more issues they put in instead of fixing. Then they fixed one issue, and then started putting more in. 3.2.1.3 is alright and works, as I posted about months ago after I upgraded to 3.2.2.3 and it broke Windows and caused lag in the Qubes Video Driver along with a major flicker. The only way to resolve that was to remove QWT and then perform a complete reinstall of it, without the video driver. But to do that I had to start in safe mode, and enable the standard display adapter and disable the Qubes Video. I've been complaining for so long about things it's not funny, and they have not resolved the issues. (yet) That was stared in Qubes 2. Now at Qubes 4, I don't expect there to be any advancement in the Windows integration for the GPU side of things. But I stick to Qubes for security, that's one thing that they did get right, the whole reason behind it. So all in all, since QWT changed hands a couple of times, things went wrong. So in essence, I just hope for the future because having multiple people work on the QWT system and it going wrong mainly after it changed hands, was expected. So, in a few years, the bugs in QWT 2* GFX side might be fixed. Maybe they might do a complete re-write and get it all resolved in a month or 2. I would say my experiences thus far have given me the impression windows support is not a primary focus of this project. Windows tools/support seems to be mainly user contributed, and while mostly functional, Qubes in no way offers the kind of windows experience running on bare metal would get you. This is perfectly ok with me, and in my personal opinion I think if someone is looking for a windows machine with full hardware acceleration (to support something like game playing), Qubes (or almost any virtualization technology) is not going to be the answer. If I were to offer any criticism to the qubes project, strictly regarding Windows support, it would be that their documentation should set expectations of what Windows support is available a little more clearly. After looking at the Qubes homepage a few weeks ago before heading down the road of installing it myself, I was mostly expecting windows support to be on par with linux ( I was never expecting graphics acceleration or much direct hardware, as it is made clear linux appvm's do not support hardware acceleration). I was however expecting things like usb passthrough to work, and I was troubled by problems with the most recent version of QWT which the docs I don't think quite explained (so I decided to help by submitting my experience to the news group archive to hopefully help others) On a personal note, after reading a handful of your emails last night, I found the tone of all your emails leaving a rather poor taste in my mouth. There was an arrogance and sense of entitlement that I think totally detract from any useful information you may have been providing. It sounds like you are doing good work with slackware and with good purpose, but then I read comments like "I know more about qubes than the developers do by now." and "I've been complaining for so long about things it's not funny, and they have not resolved the issues. (yet)" and I'm not sure if you realize just how off putting that is to someone who is working very hard on an open source project. The qubes developers do not owe us anything, rather quite the opposite, we owe them immensely for all their hard work creating a fantastic operating system! Ed -- 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/6e5fe963-e0cf-2bb0-880c-94957e3c2de4%40edjusted.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
On 03/07/2017 08:52 PM, Ted Brenner wrote:
On Mon, Mar 6, 2017 at 8:25 PM, Ed Welch <mailto:e...@edjusted.com>> wrote:
On 03/06/2017 09:16 PM, Ted Brenner wrote:
Thanks for the details Ed. Did you have to start over from
scratch or were you able to remove QWT and then install the older
version?
On Fri, Mar 3, 2017 at 8:46 PM, Ed Welch mailto:e...@edjusted.com>> wrote:
I figured out how to install an older version of
qubes-windows-tools
sudo dnf remove qubes-windows-tools
sudo qubes-dom0-update
--enablerepo=qubes-dom0-current-testing
qubes-windows-tools-3.2.1-3.x86_64
From the testing repo:
http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/
<http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/>
I was able to see the different versions so I chose the most
recent prior to 3.2.2-3, which was 3.2.1-3.
And I have to say, this was a whole different ballgame,
everything with this version went really smoothly, I'm up and
running now with an updated win 7 instance, gui comes up
fine, never even needed debug mode.
I'm not sure if Ted and I are just among the first to do a
clean install with 3.2.1-3 or if there is something about our
systems giving us these issues.
Anyone please let me know how I can help (filing issues in
github, logs, etc) but for now I'm happy with how the older
version is working.
Ed
On 03/03/2017 11:45 AM, Ted Brenner wrote:
For what it's worth, I'm having the exact same issues.
On Fri, Mar 3, 2017 at 9:13 AM, Ed Welch mailto:e...@edjusted.com>> wrote:
Hey everyone, new to qubes, love it!
Getting going with linux I found pretty straight
forward, no issues.
Trying to get a Windows 7 HVM template created, not
going so well.
Thought I would post some of the issues I've had for
posterity and also see if I can get some help.
If you are like me and don't generally read long winded
posts, please at least scroll to my QUESTION at the
bottom :)
Most of the instructions tell you to create a VM,
however, none of them tell you to increase the default
VM specs. For win 7 64 it seems you want to increase
the RAM to 4096MB and primary partition to 40960MB (40G)
I know for a fact 20G is not enough to update windows 7
sp1 to latest.
You'll want to do this before anything else because it's
more difficult to do after you get started
Then I ran into the xen/cirrus video driver issue which
causes windows to freeze on the startup screen, found
this issue with workaround:
https://github.com/QubesOS/qubes-issues/issues/2488
<https://github.com/QubesOS/qubes-issues/issues/2488>
This workaround does the trick, but I think it's
important to note a few additional steps, after the last
setup reboot and BEFORE YOU SHUTDOWN windows and try to
install the windows guest additions.
MAKE SURE to enable login without password through the
netplwiz tool, it seemed like this was the crucial step
in avoiding this issue:
https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ
<https://groups.google.com/forum/#%21msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ>
Also, users mentioned in that thread the importance of
adding more RAM, however, for me it seemed that enabling
login without password was the step that avoided putting
your VM in a totally unrecoverable BSOD loop.
Following the wiki instructions, I then installed the
windows tools from the qubes-dom0-current-testing repo
(and also updated the qrexec_timeout to 300 seconds)
then switching back to the modified instructions for
working around the cirrus/xen bug I was able to boot
into windows and install the windows tools.
This is where I hit my next big stumbling point, during
the installation the PV drivers prompt you to reboot. DO
NOT REBOOT until the installation finishes, I did
eventually see on this page 'Xen PV driver components
may display a message box asking for reboot during
installation – it’s safe to ignore them and defer the
reboot.'
Really this needs to be promoted to
https://www.qubes-os.org/doc/windows-appvms/
<https://www.qubes-os.org/doc/windows-appvms/> IMO and
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
On 03/06/2017 09:16 PM, Ted Brenner wrote: Thanks for the details Ed. Did you have to start over from scratch or were you able to remove QWT and then install the older version? On Fri, Mar 3, 2017 at 8:46 PM, Ed Welch <mailto:e...@edjusted.com>> wrote: I figured out how to install an older version of qubes-windows-tools sudo dnf remove qubes-windows-tools sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools-3.2.1-3.x86_64 From the testing repo: http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/ <http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/> I was able to see the different versions so I chose the most recent prior to 3.2.2-3, which was 3.2.1-3. And I have to say, this was a whole different ballgame, everything with this version went really smoothly, I'm up and running now with an updated win 7 instance, gui comes up fine, never even needed debug mode. I'm not sure if Ted and I are just among the first to do a clean install with 3.2.1-3 or if there is something about our systems giving us these issues. Anyone please let me know how I can help (filing issues in github, logs, etc) but for now I'm happy with how the older version is working. Ed On 03/03/2017 11:45 AM, Ted Brenner wrote: For what it's worth, I'm having the exact same issues. On Fri, Mar 3, 2017 at 9:13 AM, Ed Welch mailto:e...@edjusted.com>> wrote: Hey everyone, new to qubes, love it! Getting going with linux I found pretty straight forward, no issues. Trying to get a Windows 7 HVM template created, not going so well. Thought I would post some of the issues I've had for posterity and also see if I can get some help. If you are like me and don't generally read long winded posts, please at least scroll to my QUESTION at the bottom :) Most of the instructions tell you to create a VM, however, none of them tell you to increase the default VM specs. For win 7 64 it seems you want to increase the RAM to 4096MB and primary partition to 40960MB (40G) I know for a fact 20G is not enough to update windows 7 sp1 to latest. You'll want to do this before anything else because it's more difficult to do after you get started Then I ran into the xen/cirrus video driver issue which causes windows to freeze on the startup screen, found this issue with workaround: https://github.com/QubesOS/qubes-issues/issues/2488 <https://github.com/QubesOS/qubes-issues/issues/2488> This workaround does the trick, but I think it's important to note a few additional steps, after the last setup reboot and BEFORE YOU SHUTDOWN windows and try to install the windows guest additions. MAKE SURE to enable login without password through the netplwiz tool, it seemed like this was the crucial step in avoiding this issue: https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ <https://groups.google.com/forum/#%21msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ> Also, users mentioned in that thread the importance of adding more RAM, however, for me it seemed that enabling login without password was the step that avoided putting your VM in a totally unrecoverable BSOD loop. Following the wiki instructions, I then installed the windows tools from the qubes-dom0-current-testing repo (and also updated the qrexec_timeout to 300 seconds) then switching back to the modified instructions for working around the cirrus/xen bug I was able to boot into windows and install the windows tools. This is where I hit my next big stumbling point, during the installation the PV drivers prompt you to reboot. DO NOT REBOOT until the installation finishes, I did eventually see on this page 'Xen PV driver components may display a message box asking for reboot during installation – it’s safe to ignore them and defer the reboot.' Really this needs to be promoted to https://www.qubes-os.org/doc/windows-appvms/ <https://www.qubes-os.org/doc/windows-appvms/> IMO and in big bold letters DO NOT REBOOT until the installation is completed kind of thing. If you reboot before it finishes this is really unrecoverable and it's easier to just blow away the vm and start again... Ok, so now we get to where I'm stuck, my vm is installed, qubes-windows-tools 3.2.2-3 is installed, however as soon as I start the thing, it boots and the display immediately goes away, found this issue:
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
I figured out how to install an older version of qubes-windows-tools sudo dnf remove qubes-windows-tools sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools-3.2.1-3.x86_64 From the testing repo: http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/ I was able to see the different versions so I chose the most recent prior to 3.2.2-3, which was 3.2.1-3. And I have to say, this was a whole different ballgame, everything with this version went really smoothly, I'm up and running now with an updated win 7 instance, gui comes up fine, never even needed debug mode. I'm not sure if Ted and I are just among the first to do a clean install with 3.2.1-3 or if there is something about our systems giving us these issues. Anyone please let me know how I can help (filing issues in github, logs, etc) but for now I'm happy with how the older version is working. Ed On 03/03/2017 11:45 AM, Ted Brenner wrote: For what it's worth, I'm having the exact same issues. On Fri, Mar 3, 2017 at 9:13 AM, Ed Welch <mailto:e...@edjusted.com>> wrote: Hey everyone, new to qubes, love it! Getting going with linux I found pretty straight forward, no issues. Trying to get a Windows 7 HVM template created, not going so well. Thought I would post some of the issues I've had for posterity and also see if I can get some help. If you are like me and don't generally read long winded posts, please at least scroll to my QUESTION at the bottom :) Most of the instructions tell you to create a VM, however, none of them tell you to increase the default VM specs. For win 7 64 it seems you want to increase the RAM to 4096MB and primary partition to 40960MB (40G) I know for a fact 20G is not enough to update windows 7 sp1 to latest. You'll want to do this before anything else because it's more difficult to do after you get started Then I ran into the xen/cirrus video driver issue which causes windows to freeze on the startup screen, found this issue with workaround: https://github.com/QubesOS/qubes-issues/issues/2488 <https://github.com/QubesOS/qubes-issues/issues/2488> This workaround does the trick, but I think it's important to note a few additional steps, after the last setup reboot and BEFORE YOU SHUTDOWN windows and try to install the windows guest additions. MAKE SURE to enable login without password through the netplwiz tool, it seemed like this was the crucial step in avoiding this issue: https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ <https://groups.google.com/forum/#%21msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ> Also, users mentioned in that thread the importance of adding more RAM, however, for me it seemed that enabling login without password was the step that avoided putting your VM in a totally unrecoverable BSOD loop. Following the wiki instructions, I then installed the windows tools from the qubes-dom0-current-testing repo (and also updated the qrexec_timeout to 300 seconds) then switching back to the modified instructions for working around the cirrus/xen bug I was able to boot into windows and install the windows tools. This is where I hit my next big stumbling point, during the installation the PV drivers prompt you to reboot. DO NOT REBOOT until the installation finishes, I did eventually see on this page 'Xen PV driver components may display a message box asking for reboot during installation – it’s safe to ignore them and defer the reboot.' Really this needs to be promoted to https://www.qubes-os.org/doc/windows-appvms/ <https://www.qubes-os.org/doc/windows-appvms/> IMO and in big bold letters DO NOT REBOOT until the installation is completed kind of thing. If you reboot before it finishes this is really unrecoverable and it's easier to just blow away the vm and start again... Ok, so now we get to where I'm stuck, my vm is installed, qubes-windows-tools 3.2.2-3 is installed, however as soon as I start the thing, it boots and the display immediately goes away, found this issue: https://github.com/QubesOS/qubes-issues/issues/1896 <https://github.com/QubesOS/qubes-issues/issues/1896> which matches the behavior I'm seeing, however, this was fixed some time ago, but not totally sure when it was released?? My second, issue, which may actually be causing the first, seems to best be described in this thread: https://groups.google.com/d/topic/qubes-users/4OgwojFK-sI/discussion <https://groups.google.com/d/topic/qubes-users/4OgwojFK-sI/discussion> Specifically I'm having the issue in the last comment, the only way I can get any UI is if I boot with --debug, and when I
[qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
Hey everyone, new to qubes, love it! Getting going with linux I found pretty straight forward, no issues. Trying to get a Windows 7 HVM template created, not going so well. Thought I would post some of the issues I've had for posterity and also see if I can get some help. If you are like me and don't generally read long winded posts, please at least scroll to my QUESTION at the bottom :) Most of the instructions tell you to create a VM, however, none of them tell you to increase the default VM specs. For win 7 64 it seems you want to increase the RAM to 4096MB and primary partition to 40960MB (40G) I know for a fact 20G is not enough to update windows 7 sp1 to latest. You'll want to do this before anything else because it's more difficult to do after you get started Then I ran into the xen/cirrus video driver issue which causes windows to freeze on the startup screen, found this issue with workaround: https://github.com/QubesOS/qubes-issues/issues/2488 This workaround does the trick, but I think it's important to note a few additional steps, after the last setup reboot and BEFORE YOU SHUTDOWN windows and try to install the windows guest additions. MAKE SURE to enable login without password through the netplwiz tool, it seemed like this was the crucial step in avoiding this issue: https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ Also, users mentioned in that thread the importance of adding more RAM, however, for me it seemed that enabling login without password was the step that avoided putting your VM in a totally unrecoverable BSOD loop. Following the wiki instructions, I then installed the windows tools from the qubes-dom0-current-testing repo (and also updated the qrexec_timeout to 300 seconds) then switching back to the modified instructions for working around the cirrus/xen bug I was able to boot into windows and install the windows tools. This is where I hit my next big stumbling point, during the installation the PV drivers prompt you to reboot. DO NOT REBOOT until the installation finishes, I did eventually see on this page 'Xen PV driver components may display a message box asking for reboot during installation – it’s safe to ignore them and defer the reboot.' Really this needs to be promoted to https://www.qubes-os.org/doc/windows-appvms/ IMO and in big bold letters DO NOT REBOOT until the installation is completed kind of thing. If you reboot before it finishes this is really unrecoverable and it's easier to just blow away the vm and start again... Ok, so now we get to where I'm stuck, my vm is installed, qubes-windows-tools 3.2.2-3 is installed, however as soon as I start the thing, it boots and the display immediately goes away, found this issue: https://github.com/QubesOS/qubes-issues/issues/1896 which matches the behavior I'm seeing, however, this was fixed some time ago, but not totally sure when it was released?? My second, issue, which may actually be causing the first, seems to best be described in this thread: https://groups.google.com/d/topic/qubes-users/4OgwojFK-sI/discussion Specifically I'm having the issue in the last comment, the only way I can get any UI is if I boot with --debug, and when I do, I often see that error linked: 'The GUI agent that runs in the VM 'win7' implements outdated protocol (0:0), and must be updated. After reading through that thread, several people were mentioning that 3.2.2-3 has seemed to make things less stable. What I would like to do, is install the previous version of qubes-windows-tools, but try as I might to manipulate the qubes-dom0-update script into doing so I have not been able to do this, I'm not even sure the older versions are kept in the repos?? QUESTION: Is there a way to install a specific version (whatever was previous to 3.2.2-3) of qubes windows tools? Thanks! Ed -- 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/821726de-f5c1-d6a9-b15e-078e1f9cc56d%40edjusted.com. For more options, visit https://groups.google.com/d/optout.
