[qubes-users] Re: TPM: Device not found (Lenovo P51, Qubes 4.x)
Actually, it looks like the excellent Trammell Hudson is on the case: https://github.com/osresearch/safeboot/issues/21 On Wednesday, January 27, 2021 at 11:10:23 PM UTC-6 Liam D. Gray wrote: > Dave, did you ever get TPM working on your P51? > > I have the same exact model of P51 (20HHCTO1WW) and I love it. It's loaded > up with 32GB RAM and 1TB NVMe SSD. But I was hoping to use it with Qubes > and TPM. > > Sounds like Qubes didn't (and still doesn't?) support TPM 2.0: > https://www.slideshare.net/PiotrKrl/qubes-os-and-tpm-20 > > I'm a firmware developer myself, though so far not on PCs yet. I'm > wondering if integrating support for TPM 2.0 is beyond my ability or more a > matter of the very capable core maintainers being occupied with > higher-priority stuff. If it's the latter, perhaps I could try it... > > Best, > Liam > On Saturday, February 3, 2018 at 1:31:35 PM UTC-6 Dave C wrote: > >> I'm having trouble finding TPM troubleshooting tips. Any pointers? >> >> I've installed 4.x RC4 on a Lenovo thinkpad P51. The HCL (attached) shows >> >> TPM: Device not found >> >> In the bios, TPM 2.0 is enabled. >> >> Thanks in advance. -Dave >> >> -- 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/c32ccd2a-b4fc-4176-bb25-52331a67f1c2n%40googlegroups.com.
[qubes-users] Re: TPM: Device not found (Lenovo P51, Qubes 4.x)
Dave, did you ever get TPM working on your P51? I have the same exact model of P51 (20HHCTO1WW) and I love it. It's loaded up with 32GB RAM and 1TB NVMe SSD. But I was hoping to use it with Qubes and TPM. Sounds like Qubes didn't (and still doesn't?) support TPM 2.0: https://www.slideshare.net/PiotrKrl/qubes-os-and-tpm-20 I'm a firmware developer myself, though so far not on PCs yet. I'm wondering if integrating support for TPM 2.0 is beyond my ability or more a matter of the very capable core maintainers being occupied with higher-priority stuff. If it's the latter, perhaps I could try it... Best, Liam On Saturday, February 3, 2018 at 1:31:35 PM UTC-6 Dave C wrote: > I'm having trouble finding TPM troubleshooting tips. Any pointers? > > I've installed 4.x RC4 on a Lenovo thinkpad P51. The HCL (attached) shows > > TPM: Device not found > > In the bios, TPM 2.0 is enabled. > > Thanks in advance. -Dave > > -- 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/5b46e13d-5a9d-4f61-ad0b-9d951da3728an%40googlegroups.com.
[qubes-users] Subscribe
Subscribe -- 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/CAAPp40XOa4rwKykepUGh4niYHvGgjObtdz6SdVtANMSJDkO%3DCA%40mail.gmail.com.
Re: [qubes-users] Exported Volume Error.
On Thu, 28 Jan 2021 00:31:16 + Rusty Bird wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >'Stuart Perkins' via qubes-users: >> Ok, now I'm afraid to turn off my computer or even stop any Debian template >> based VM's... > >Don't panic, it's just a bug* in qubes-core-dom0-4.0.56. Your VM data >is still okay. > >> Here is what happened. >> >> I was going to do a general update on Dom0 and my Debian-10 and >> Fedora-32 templates. >> >> As is my habit, I deleted the older clones of those template VM's >> and was creating new clones with qvm-clone from a Dom0 command >> window. >> >> While attempting to create a new clone of the Debian-10 template, it >> halted with an error: >> >> file pool cannot export dirty volumes. >> >> Searching for that issue suggested I start the template VM and exit >> it cleanly...although I don't have a recollection of a "dirty" exit >> (crash, kill etc...). >> >> I went to start the template with qvm-start and it won't, giving the >> error: >> >> file pool cannot start a VM with an exported volume. >> >> How in the world do I recover from this? > >If you restart your computer (or only qubesd), it will drop the >lingering export lock and you'll be able to start the original >template again, etc. > >Rusty I figured that out, eventually...after some sweat. I rely on this machine way too much. All critical data was backed up, but I was not looking forward to a reinstall and the time it would take out of my "way-too-busy" week. Aside: I found out the command line "qvm-clone" will NOT work. That is what left it in this state. Oddly enough, using the Qubes Manager gui it succeeds in the clone...but leaves it where you can't start the template to do the update until you reboot again. Just FYI. In my install I chose NOT to do the LVM as it adds an unnecessary layer of complexity to a laptop, which is already an encrypted installation. I want to add additional drive space ONCE, and do that with just formatting the second drive and symbolic links from the appvm directory to the "too large for my ssd" drives. SSD is 260G. Hard drive is 2TB. Like most Qubes users, I work the crap out of my machine...a coreboot Lenovo T420i. Now that I'm up to 5.4.88, is this fixed? Stuart -- 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/20210127200238.161d72d0%40yahoo.com.
Re: [qubes-users] Exported Volume Error.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 'Stuart Perkins' via qubes-users: > Ok, now I'm afraid to turn off my computer or even stop any Debian template > based VM's... Don't panic, it's just a bug* in qubes-core-dom0-4.0.56. Your VM data is still okay. > Here is what happened. > > I was going to do a general update on Dom0 and my Debian-10 and > Fedora-32 templates. > > As is my habit, I deleted the older clones of those template VM's > and was creating new clones with qvm-clone from a Dom0 command > window. > > While attempting to create a new clone of the Debian-10 template, it > halted with an error: > > file pool cannot export dirty volumes. > > Searching for that issue suggested I start the template VM and exit > it cleanly...although I don't have a recollection of a "dirty" exit > (crash, kill etc...). > > I went to start the template with qvm-start and it won't, giving the > error: > > file pool cannot start a VM with an exported volume. > > How in the world do I recover from this? If you restart your computer (or only qubesd), it will drop the lingering export lock and you'll be able to start the original template again, etc. Rusty * https://github.com/QubesOS/qubes-core-admin/commit/0eb95044dd937857581a22c13a692eff5d92c70b#r46447802 -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmASBdNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0 QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv Kt/aMxAAhvLLYX/P41rPlt2dc+Apt1IJ+TsEYfY8QPLxgmbihLPAstFTizD6bFKR MHaoHNdGuVESxx4NHUT4QINhNf8u42H1uhq3oyjyEEaXBg1BTdijoTq6lboE7/PS aQ9x/6+qpuM4yF7sfdKcKCLI65NveWzlI9BllBi14/on5Qyp/+xbWZHu8ZQ6M/AW Sk7XkjpbxcIJiyO94dCLSJthEgvhUoYa42WJI9vuaH3Mi//8PVVJ4siY4GtCCEP6 8d2rcJOo2F9t1MW3cs1K4cxDgk+0F93dsH6/QkN54AJb1hZC9Kmr+J0+Rplge1qU M8VWOfXVzJLaWuQmEDFM3PXQiXdwYsgsl/rf54Kb7TwL9n86k9cUYkzysYjEjByQ x0nq0KbXYX2ORG5OlAXYKUbvqYEj+xjaN2NU/fXhJ1S5r8ONjY2z5XnRA7wEB56L RFWIsSV8+cUXGICRmQDqlHW3jutWz8LSpOYHRLGqXLf7MK4pw1X31WaVEySKcuTE D8obLteR7Zv0C0malWBWDRdsNokpZKzNPmlKupnGlZDcAmP/f2kKlMe63EwhEXoL gGrb6EeB/cOGaHpbQDNntGD/3AjXcdtNRq3gGHUjCjzb0QQcAbQ3I6bf1zEQrLYV 61p4/y/6qWXi1pUtMyXF+bC/LweGJ84LFxDstlnEittImdsRk0w= =HY+/ -END PGP SIGNATURE- -- 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/20210128003116.GA1131%40mutt.
Re: [qubes-users] Re: [PATCH v5.10] drm/i915/userptr: detect un-GUP-able pages early
On 1/25/21 12:05 PM, donoban wrote: > Hi, > > Is this patch included in last 5.10 kernel release? Last time I tried to > boot it I had a lot of graphic artifacts. If the patch is included I > could try again. No, but this patch has been superseded by the latest intel xorg driver. To try it, just enable the current-testing repo and upgrade xorg-x11-drv-intel to at least v2.99.917-49.20210126. sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing --action=upgrade xorg-x11-drv-intel Discussion: https://github.com/QubesOS/qubes-issues/issues/6356#issuecomment-765952048 > > Regards. > -- Sincerely, Jinoh Kang -- 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/9236869a-ba06-32d4-75c6-adb99c1ec270%40gmail.com.
[qubes-users] Exported Volume Error.
Ok, now I'm afraid to turn off my computer or even stop any Debian template based VM's... Here is what happened. I was going to do a general update on Dom0 and my Debian-10 and Fedora-32 templates. As is my habit, I deleted the older clones of those template VM's and was creating new clones with qvm-clone from a Dom0 command window. While attempting to create a new clone of the Debian-10 template, it halted with an error: file pool cannot export dirty volumes. Searching for that issue suggested I start the template VM and exit it cleanly...although I don't have a recollection of a "dirty" exit (crash, kill etc...). I went to start the template with qvm-start and it won't, giving the error: file pool cannot start a VM with an exported volume. How in the world do I recover from this? Stuart -- 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/20210127123934.562adad4%40yahoo.com.
Re: [qubes-users] HCL - Thinkpad T430s (i5-3320M)
Do you think it makes a difference if it's T430s or T430 with exact same hardware specifications? Thanks On Friday, October 18, 2013 at 11:16:33 PM UTC+2 Axon wrote: > On 10/16/13 06:51, cprise wrote: > > It definitely should be green. The issues I'm having would be present on > > any of the other systems in the HCL... software-only features/bugs (like > > updates working only from the CLI, not the GUI). > > > > > > OK, it's green now. > > -- 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/dadded91-3a6f-4bdc-afc0-601b43881c5en%40googlegroups.com.
[qubes-users] Re: Updating a new installation
sure, just open a terminal in dom0 and run 'sudo qubes-dom0-update --clean' On Wednesday, January 27, 2021 at 6:44:30 AM UTC Shawn Creighton wrote: > What is the quickest and most secure way to update the entire system > including Dom0 on the first boot of a new install? I've noticed that it > takes awhile for the updates to populate to the qubes updater when first > connected to the net even though there are obviously updates available. Is > there a way to expedite the process? > -- 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/a9da50f8-7a7b-4d4b-ba8e-44bf000f1a48n%40googlegroups.com.
