[qubes-users] Upgrading from fedora 26->29, one issue and a step-by-step of my experience
The Qubes documentation for fedora template upgrades is excellent and I only had one issue not covered by it during my upgrade process. I encountered an error that stated I didn't have fedora29 rpmfusion free and nonfree signing keys imported while executing: [user@fedora-29 ~]$ sudo dnf --releasever=29 --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync I checked /etc/pki/rpm-gpg and sure enough, they were missing, I remember looking and it had automatically added fedora 25-28, but not 29. I imported the keys with the following commands: [user@fedora-29-1 rpm-gpg]$ sudo rpm --import 'https://rpmfusion.org/keys?action=AttachFile=get=RPM-GPG-KEY-rpmfusion-free-fedora-29' [user@fedora-29-1 rpm-gpg]$ sudo rpm --import 'https://rpmfusion.org/keys?action=AttachFile=get=RPM-GPG-KEY-rpmfusion-nonfree-fedora-29' Is there a better way of doing this that I should have done for the key imports? If multiple others have had this issue and it's not a one-off to me, I'll happily add it to the upgrade docs at the bottom, or on the qubes-community github. I figured I'd document this here and on my blog at least. Blog with my step-by step upgrade details: https://fiascoaverted.blogspot.com/2019/02/upgrading-qubes-to-latest-fedora-29.html -- 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/a06e11b7-a796-402d-af13-da9e7a4853d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Thinkpad X1 Carbon Gen6 suspend/resume issues
On Saturday, October 27, 2018 at 5:57:43 AM UTC-7, tfm...@googlemail.com wrote: > To be more precise regarding the wifi and USB issues: > > One following issues can occur after suspend: > > - All USB devices disappear from sys-usb, wifi is not working anymore. This > can be fixed by restarting both sys-usb and sys-net. > > - Directly after suspending, the speaker plays a loud, short melody (sounds a > bit like the game-over-sound of an 80s computer game ^^). I guess this is > some kind of diagnostic code? The LED shows sleep but the fan might keep > running when it was running while suspending. The system cannot be woken up > by opening the lid or pressing the power button. > > The interesting part is: Either of these issues only seems to appear when a > win7 HVM is running. > > With only linux appvms running, I can close/open the lid 10 times (not that > big of a sample, but still) without issues. > > With a win7 HVM running, one of the issues happens everytime. > > I don't have any other HVMs. But I guess this isn't predicated on win7 > specifically. Did you try the suspend/resume fix that DJB documented here: https://groups.google.com/d/msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ It requires recompiling the kernel, but took me about 2 hours in total from reading, to understanding, to doing this in total on the same machine. It has worked for several of us (don't know anyone that it didn't work for). I have read that BIOS 1.31 should fix suspend/resume issues, but haven't tried it yet. I haven't run a win7hvm or tried thermal issue fixes either. -- 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/db0a40ea-0813-4540-989e-2df8a69e9af0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: X1 Carbon again; Qubes DSDT override?
On Tuesday, September 4, 2018 at 10:01:08 PM UTC-7, aqeel...@gmail.com wrote:
> On Wednesday, 1 August 2018 12:04:13 UTC+10, D. J. Bernstein wrote:
> > I finally decided to resort to patching the kernel. Suspend now seems to
> > work normally in several tests on a Lenovo X1 ThinkPad Carbon 6th
> > generation under Qubes R4.0. The idea of the patch is to do
> >
> >if (sleep_state == ACPI_STATE_S3) {
> > *sleep_type_a = 5;
> > *sleep_type_b = 5;
> > return_ACPI_STATUS(AE_OK);
> >}
> >
> > near the top of acpi_get_sleep_type_data() (right after the "Validate
> > parameters" part) in linux/drivers/acpi/acpica/hwxface.c. This has the
> > same effect as the DSDT patches running around for this laptop: telling
> > the kernel that the laptop supports S3 state (which the hardware _does_
> > support---the starting problem is that the BIOS fails to announce this),
> > and more specifically that S3 is hardware sleep type 5.
> >
> > Of course, simply adding the lines above wouldn't be appropriate for
> > non-laptops, or laptops where S3 is another hardware sleep type. The
> > actual patch is instead triggered by
> >
> >* DMI reporting this laptop, or
> >* "acpi_force_s3=5" on the kernel command line (so users have a
> > relatively easy way to handle newer laptops with the same problem).
> >
> > If this patch survives more tests and review (I'm not a Linux kernel
> > expert) then it should be suitable for upstream adoption. I've attached
> > the patch, and some notes on how I compiled a patched kernel for Qubes
> > R4.0.
> >
> > Beyond the patch, I've put
> >
> >mem_sleep_default=deep
> >
> > into my /boot/efi/EFI/qubes/xen.cfg on the kernel= line for the patched
> > kernel, to tell the kernel to use S3 for suspend---otherwise it uses
> > s2idle. The importance of S3 vs. s2idle for this laptop is different on
> > Qubes from vanilla Linux: there are many reports of s2idle consuming
> > more power than S3 on vanilla Linux, but Qubes seems unique in s2idle
> > not waking up at all. I don't see a serious argument for s2idle when S3
> > is supported, so I'm not sure why mem_sleep_default prefers s2idle over
> > S3; even if there's a reason for this, maybe there would be general
> > interest in a second patch that disables s2idle on this laptop.
> >
> > ---Dan
>
> Hi Dan,
>
> I followed kernel-compile-notes.txt twice. The first time failed, the second
> time worked a charm with minor changes to the method. These are my notes on
> the experience.
>
> Before I proceed, I note that the current version of the qubes-linux-kernel
> git on stable-4.14 is 4.14.67-1. This is the version of the kernel that I
> have compiled and applied your patch to.
>
> The first (failed) attempted, I was on a fresh install of Qubes R4.0, kernel
> 4.14.18-1. Compiling the kernel seemed to work, as did installing. Upon boot
> and unlocking my hard-drive the system never seemed to get anywhere on the
> loading. Upon pressing escape I noticed I was being spammed with a `dracut`
> error before eventually it dropped to an emergency shell. A more forward
> thinking me would have written down the error message. I simply reinstalled
> Qubes R4.0 fresh to start over.
>
> The second (successful) attempt was after I had updated dom0. I was running
> kernel 4.14.57-2. I knew that this was an earlier version than the one I was
> going to compile so it wasn't going to be an issue (as you've described in
> your excellent notes). I doubt updating dom0 had anything to do with the
> success of this attempt, instead I did two things differently to your notes:
>
> 1. I ran the following command twice, superfluous I presume:
>
>make verify-sources
>
> 2. I ran the following command in dom0 after installing:
>
>dom0 $ sudo dracut -f "/boot/efi/EFI/qubes/initramfs-$version.img"
> "$version"
>
> Paying special attention that the variable $version was expanded correctly.
>
> After adding the kernel parameter:
>mem_sleep_default=deep
> to the appropriate line in /boot/efi/EFI/qubes/xen.cfg - again as you've
> described.
>
> To conclude, I can confirm that your patch works for version 4.14.67-1 of the
> qubes-linux-kernel too. That is, standby and wake from standby work as
> intended and the command:
>dmesg | grep ACPI | grep supports
> yields:
>ACPI: (supports S0 S3 S5)
> on my Carbon X1 Gen 6, i7 8550U.
>
> However, perhaps unrelated, I have noticed the CPU doesn't turbo boost.
> Running the following command in dom0:
>xenpm get-cpufreq-states
> shows that only 13 / 16 P-States are usable with P0, P1, P3 (the turbo
> states) clearly as the ones that aren't available.
>
> Regards,
> Aqeel
Dan's notes worked perfectly for me once I remembered to enable thunderbolt
assist. Thanks djb!
--
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
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
I'm going to try seeing what drivers are loaded and if any of those are the cause. https://www.qubes-os.org/doc/wireless-troubleshooting/ Blacklisting the two wifi drivers as per the above did not fix 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/ce07b19b-b7ed-4bc1-bea3-a4e10161b28f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
On Tuesday, April 17, 2018 at 1:34:34 AM UTC-7, bbrr...@gmail.com wrote: > On Monday, April 16, 2018 at 11:14:43 PM UTC+1, fiasc...@gmail.com wrote: > > Summary: Install worked reasonably well and it boots with EFI into the > > installed Qubes 4.0 nicely. There are a few issues to resolve. > > > > 1. I have the model with a touch screen and I haven't debugged how to make > > it work yet (I'll get to that and post back what worked). > > > > 2. Suspend/resume doesn't work and I have to do a hard reset. A few times > > (not all) I had to hard reset twice to get it to reboot properly. > > > > 3. HCL reports no TPM, but I have a dTPM 2.0. > > > > It's booting with UEFI smoothly. I haven't tested the mic, camera, or ports > > except USB for storage yet. I'll update once I find fixes for the above. If > > anyone could point me in the right direction for the suspend freezing > > issue, let me know. I tried shutting down all VMs, including service VMs > > after reading this, > > https://groups.google.com/d/msg/qubes-users/81t26xq4MEI/HrfDEcjeAgAJ but > > the problem persisted didn't change anything. > > Might be worth flashing to most recent BIOS. (I did that straight away on my > T480 so I'm not sure if that contributed to suspend eventually working well) Tried that before anything else. -- 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/9722a448-34a1-405f-b4eb-751e603b226c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - Thinkpad X1 Carbon 5th gen - Qubes 4.0-rc3
On Friday, December 15, 2017 at 4:54:19 PM UTC-8, Marek Marczykowski-Górecki wrote: > Hi, > > I have some initial comments about Qubes 4.0rc3 on Lenovo Thinkpad X1 > Carbon 5th gen. I'll dig further into issues listed below. But for now I > wouldn't call it "works out of the box", unfortunately :/ > > - EFI installer do not boot - gets back into grub instantly, /noexitboot >/mapbs do not help > - legacy mode install works fine (although I've noticed small graphics >glithes once or twice) > - at next boot grub is horribly slow (you can see drawing each char) > - system starts with default kernel (4.9.56) > - trackpoint/touchpad do not work: > > psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 > psmouse serio1: issuing reconnect request > psmouse serio1: synaptics: queried max coordinates: x [..5678], y > [..4758] > psmouse serio1: synaptics: queried min coordinates: x [1266..], y > [1094..] > > - suspend: hang on suspend (green light flash quickly) > > Next step: upgrade dom0 (only!) kernel to 4.14.6 > (https://github.com/QubesOS/qubes-linux-kernel/pull/13). You need to > build it yourself, there is no > binary package available, yet. > > Then add iwlmvm and iwlwifi to /rw/config/suspend-module-backlist in sys-net > > - this fixed suspend issue, wireless also works after suspend > - touchpad/trackpoint still do not work > > Other issues: > - https://github.com/QubesOS/qubes-issues/issues/3108 > > > Untested: > - mic > - camera > - ethernet > - thunderbolt (and do not plan to) > - WiGig (does it even have Linux support?) > - bluetooth > - NFC > - fingerprint reader (do not plan to test) > > Attached hardware info. > > -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? Did you (or anyone else) ever figure out how to fix the suspend/resume issues? I'm seeing that issue on my X1 Carbon 6th gen (qubes 4.0). Install worked smoothly with EFI. My HCL post: https://groups.google.com/forum/#!topic/qubes-users/QrG7uUZsSZY -- 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/2b3bec5c-4eed-4482-bff1-03a476379134%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0
Summary: Install worked reasonably well and it boots with EFI into the installed Qubes 4.0 nicely. There are a few issues to resolve. 1. I have the model with a touch screen and I haven't debugged how to make it work yet (I'll get to that and post back what worked). 2. Suspend/resume doesn't work and I have to do a hard reset. A few times (not all) I had to hard reset twice to get it to reboot properly. 3. HCL reports no TPM, but I have a dTPM 2.0. It's booting with UEFI smoothly. I haven't tested the mic, camera, or ports except USB for storage yet. I'll update once I find fixes for the above. If anyone could point me in the right direction for the suspend freezing issue, let me know. I tried shutting down all VMs, including service VMs after reading this, https://groups.google.com/d/msg/qubes-users/81t26xq4MEI/HrfDEcjeAgAJ but the problem persisted didn't change anything. -- 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/9fb2385b-c7fe-40e4-9a1d-e1e670894c8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20KH002JUS-20180416-115836.yml Description: Binary data
[qubes-users] Re: New Lenovo X1 Carbon 6th Gen Compatability
On Thursday, February 8, 2018 at 10:19:11 AM UTC-8, John Pacific wrote: > Hello! > > The new X1 Carbon 6th gen will be released soon(tm)! > I was wondering if anyone had planned on trying to install Qubes on it and > reporting back here. > > It has the following hardware: > > 8th Generation Intel® Core i7-8650U with vPro® > Integrated Intel® UHD Graphics 620 > 16GB LPDDR3 2133 MHz > 1TB SSD OPAL PCIe TLC > dTPM 2.0 > (Apparently, some FIDO device?) > Intel Wireless-AC 8265 2x2 AC > > I was thinking about buying it and using it for work (with Qubes), but I > cannot justify nearly $3,000 for an experiment. > > > If any of you have tried it out or intend to try it out, please let me know! > > > Thanks, > > John Pacific Trying it out now. Works with EFI booting out of the box. Never booted into Windows other than to test that it turned on and touchscreen worked. Currenlty figuring out why the following is showing: 1. Freezes on resume from suspend. Tried shutting down all VMs and it still happens, so I suspect it's not the same fix as: https://groups.google.com/forum/#!topic/qubes-users/81t26xq4MEI 2. HCL script says no TPM, but I definitely have a TPM. 3. Touchscreen isn't working. I haven't put any time into figuring this out yet. Install was easy. Setup was otherwise easy. I currently have it set on UEFI only, disabling CSM (Compatibility Support Mode) -- 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/608f0ea6-7848-4e0f-8cb8-9dac3bcf9078%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
