Re: [qubes-users] Qubes' onion service is 404
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/03/2019 6.48 AM, 'qubeslover' via qubes-users wrote: > > Hello, Qubes' onion service has not been working for 48 hours. What > is going on? Is it going to be fixed anytime soon? > > Thanks > Hello, We're aware of the problem and are currently looking into it. Apologies for any inconvenience. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlyXD90ACgkQ203TvDlQ MDDjxw/9Htbku2Mcj64/MWOvpLBlLL3aJvJ0gZ676IY7dFF8eM1v2G+KMAyEE+ve ZKQqtXUabG6MCWWuDZJN7+bnGWxBmfxJpysFeFOnUKNdgFdr0bn+IMbC7R6j0SwT wnnatMuxdS5/Oy2EGMPQ0+8eKuGxYcBoTsbDdh6gUJYd9cQ+Eojax37MAF2diEmo D0pC7BhTodAWXlzhFz/7cWARS0vecxtDie5qNoSQn+QvitEvwGXHU2LK4+mim7XC h6C4s0U7UVSA/n/jyW2x7fvGdtMxIeq5mGAnTsEWXzGPyF5ivO761XAy0qWtKkfZ SrE3w8doA+XORms7iPdC+19qItNReGYeX4V6XN21k8LpaSBOQm9ZuL10aKQl24Nh wUJAQGzgVdSrHyc86O/KcdlvoZnE81YFe3el7fIzzT42gFljTDYTiBGByk7yoHu6 BStuCpEeMNo0dhNctvN3f4S5fuGDB8exQjZJDhnOK7u9gDs6n8pSnuAQiK1Faj5o gp02L6cAVLFZuP6LpIurDmEc1EYL47nBL8AyK0xxCqak1PbwzN+XsaUQq6bmTOiZ 8jzADRpOn2UY8ag/+uvlGeOCV5surhmvNxNp+eNn7F1iL7pLJfiwMYo5BkgKw7OU m9PKbkEoFNoWDCggH9r/O+qHq799uwLPhnalgAaJPsdSakJt7Eo= =WkQ9 -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 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/04d8341e-da1b-d4bb-1bc1-18bd5f1a5465%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 Update breaks sys-usb widget
On 3/24/19 7:21 AM, preill...@gmail.com wrote: On 3/23/19 7:28 AM, ronp...@riseup.net wrote: Qubes 4.0.1. Following a recent dom0 update my sys-usb widget is partially broken; 1/ devices show in the widget when plugged into usb port but are not removed when unplugged from the port. 2/ Plugged in devices can be attached to VM's via widget but there's now no indication (other the qvm-block in dom0) that they are attached. 3/ Unable to detach usb device from VM's via the widget (although I can do this from dom0). To check that I hadn't done something stupid and thereby broken the widget I did the following procedure. 1. Reinstalled laptop with 4.0.1 from qubes website. 2. Tested sys-usb widget - It worked perfectly. 3. Updated Dom0 and tested widget - It worked perfectly. 4. Rebooted laptop - tested widget, but its now broken - same diagnosis as described above It seems that a dom0 update has broken the widget? Does anyone else have this problem? Yes, I have the same problem, and find the applet useful. Used to work well. Peter Yes it was broken in -current 3-4 weeks ago. There have been many reports and half a dozen duplicate issues on github... major snaffu. A new version is in testing now and appears to work well - thanks Marta! If you can't wait, I fixed my -current using: qubes-dom0-update --action='' --enablerepo=qubes-dom0-current-testing qubes-desktop-linux-manager I put the verbose flag on on my second try as the first was skipped due to missing dependencies, but there appeared to be none, and it worked the second time. Eric -- 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/d79a443c-e430-6b9b-2c64-6840056bd599%40asar.biz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Blank Screen Trying To Install
On 2019-03-24 02:41, Yushatak wrote: > On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: >> When I boot the Qubes installation media (I dd'd it to a USB stick per the >> instructions on the site) it initializes Xen, then the kernel starts booting >> (Linux penguins, etc.), and then it goes to a black screen and there's no >> activity. F1 does nothing. My hardware is a laptop with an i7 8700K and an >> Nvidia 1060, so it smelled like nouveau driver problems to me. However, >> normally one works around that by editing the kernel line in grub with >> nouveau.modeset=0 and I have no grub! I decided to try editing the grub.conf >> in the isolinux directory of the ISO by extracting the iso, editing, then >> regenerating the ISO. Someone on IRC was nice enough to provide me a log >> from the official build of the ISO so I used the proper switches/etc.. I >> booted that in a VM to make sure it was OK as a sanity check, then wrote >> that to the USB stick (which takes like 26 minutes, it's USB 2.. not fun) >> and it stopped booting after attaching the USB stick as a SCSI device, not >> even quite getting to the black screen. AFAIK my hardware requires a 4.18 kernel and from what they said on IRC there's nothing newer than 4.14 in Qubes anyway, but since it tries to boot I don't know. I throw myself upon your mercy, Qubes community/developers. > > Nobody has a single thought? Might the solution be putting your BIOS into Legacy mode? https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU In my case switching the HDD from AHCI mode to IDE mode seemed to get past this blank screen and got me to the install screen. -- 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/24cf72d48db8b557b2f0832dfdcfbc13%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installing software..
On 3/24/19 2:27 AM, unman wrote: On Sat, Mar 23, 2019 at 06:31:07PM +, Jon deps wrote: On 3/19/19 4:59 PM, Steven Walker wrote: I am still pretty new to Qubes. I have managed to create a new qube, but I want to install some software for use with this qube. I have read that it has to be installed to the template and not the actual qube. As the template has no actual network connection, how do I go about this? Using 4.0.1, Fedora 29 Any help greatly appeciated. Steve pretty sure, there are different ways to skin the cat, though the Templates are designed to obtain access indirectly, that is what the "salt" stuff is they talk about it seems by default to be setup to use sys-whonix-14 to install updates , somewhat magically you can actually change the netvm without shutting down the templates generally it's bad form to give the templates direct access, though may you might want to once in while in order to troubleshoot something , etc .testing it the morning , you should be able to install non updates without Direct access for me Templates aren't worth backing up , I'm not worried about my system melting down much . and anyway its going to be best to fresh install , which is easy-ist in Qubes, which is one of the beauties of the technology hence, I clone for other reasons one word of advice is keep a paper list of custom packages you install so when it goes to Fedora-30 you install fresh and then add back fresh packages , your files will persist, my problem what few files I have end up spread out over 10 App Qubes It's only if you selected the "update over Whonix" option on install that you get updating using sys-whonix qube. It's not the default. Salt doesnt have anything to do with the "indirect" access - the access is using qubes-rpc to the UpdateProxy - the proxy to use is set in /etc/qubes-rpc/policy/qubes.UpdateProxy. You can change the proxy to use by editing that file. You *can* use salt to install software in to the templates. If you do this then you need only maintain the salt formula and you can easily recreate a template, without having to keep a paper list. That's an ideal way of using salt to configure your systems. I think I'm stuck at mere mortal qube user level forever :) https://groups.google.com/forum/#!topic/qubes-users/F_TB7Zzseeo PS: for some reason I am able to $sudo dnf install foosoftware in Fedora-29 though I have no "direct" netvm for the Template , though I recall in the pastallowing netvm access for packages I wanted to install, or maybe when I was trying to install a VPN to the template, gave up and installed it in the AppVM I guess There is a 3rd trick to discern whats custom installed IIRC , though maybe it was more for Debian than Fedora if one searches the usergroup fwiww -- 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/050cc6d6-c3bb-cb7b-f381-2ff445ebf14d%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Blank Screen Trying To Install
On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote: > When I boot the Qubes installation media (I dd'd it to a USB stick per the > instructions on the site) it initializes Xen, then the kernel starts booting > (Linux penguins, etc.), and then it goes to a black screen and there's no > activity. F1 does nothing. My hardware is a laptop with an i7 8700K and an > Nvidia 1060, so it smelled like nouveau driver problems to me. However, > normally one works around that by editing the kernel line in grub with > nouveau.modeset=0 and I have no grub! I decided to try editing the grub.conf > in the isolinux directory of the ISO by extracting the iso, editing, then > regenerating the ISO. Someone on IRC was nice enough to provide me a log from > the official build of the ISO so I used the proper switches/etc.. I booted > that in a VM to make sure it was OK as a sanity check, then wrote that to the > USB stick (which takes like 26 minutes, it's USB 2.. not fun) and it stopped > booting after attaching the USB stick as a SCSI device, not even quite > getting to the black screen. AFAIK my hardware requires a 4.18 kernel and > from what they said on IRC there's nothing newer than 4.14 in Qubes anyway, > but since it tries to boot I don't know. I throw myself upon your mercy, > Qubes community/developers. Nobody has a single thought? -- 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/a57ddeb4-1cff-4070-b37d-4643e2ee17c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Installing software..
On Sat, Mar 23, 2019 at 06:31:07PM +, Jon deps wrote: > On 3/19/19 4:59 PM, Steven Walker wrote: > > I am still pretty new to Qubes. I have managed to create a new qube, but I > > want to install some software for use with this qube. I have read that it > > has to be installed to the template and not the actual qube. As the > > template has no actual network connection, how do I go about this? > > > > Using 4.0.1, Fedora 29 > > > > Any help greatly appeciated. > > > > Steve > > > > pretty sure, there are different ways to skin the cat, though > > > the Templates are designed to obtain access indirectly, that is what the > "salt" stuff is they talk about it seems by default to be setup to use > sys-whonix-14 to install updates , somewhat magically > > you can actually change the netvm without shutting down the templates > > generally it's bad form to give the templates direct access, though may > you might want to once in while in order to troubleshoot something , etc > .testing it the morning , you should be able to install non updates > without Direct access > > > > for me Templates aren't worth backing up , I'm not worried about my > system melting down much . and anyway its going to be best to fresh > install , which is easy-ist in Qubes, which is one of the beauties of the > technology > > hence, I clone for other reasons > > one word of advice is keep a paper list of custom packages you install > so when it goes to Fedora-30 you install fresh and then add back fresh > packages , your files will persist, > > > my problem what few files I have end up spread out over 10 App Qubes > It's only if you selected the "update over Whonix" option on install that you get updating using sys-whonix qube. It's not the default. Salt doesnt have anything to do with the "indirect" access - the access is using qubes-rpc to the UpdateProxy - the proxy to use is set in /etc/qubes-rpc/policy/qubes.UpdateProxy. You can change the proxy to use by editing that file. You *can* use salt to install software in to the templates. If you do this then you need only maintain the salt formula and you can easily recreate a template, without having to keep a paper list. That's an ideal way of using salt to configure your systems. -- 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/20190324022714.q3dwlyogduwbsohn%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Shrinking a private volume
On Sat, Mar 23, 2019 at 01:59:27PM +0100, onw7two99 wrote: > Hello Chris, > > thank you once again for your feedback. > > On 3/23/19 11:31 AM, Chris Laprise wrote: > > On 3/23/19 5:34 AM, onw7two99 wrote: > >> I run sudo fstrim -av from within the AppVM (as root) but I haven't > >> notive any change. > > > > The difference doesn't show until you shutdown the vm for the second > > time (the current .old volume gets deleted). Also the Qubes disk > > widget and Qubes Manager take some time to report the new values. But > > running fstrim may not make any difference if you haven't been > > deleting many files. > > if I run ls -lah /var/lib/qubes/appvms/ the size listed is the > "thick provisioned", is there a way to show the "real" file size in dom0 > whch should be the used size which is reported from within the AppVM > when using "df -h" ? > > > >> Is there a way to move this private disk to the new storage-qube? > > > > Yes, you can use the 'mv' command while the two vms are not running. > > Keep in mind this can erase the existing private image of the > > new/destination vm unless you rename that first (but it won't be > > accessible after renaming it, unless you run 'qvm-block attach'). > > I tried to mount the private.img from the old appvm to the new one, but > I think I don't have the correct syntax. > > I tried: > > qvm-block attach :private.img > qvm-block attach /var/lib/qubes/appvms//private.img > > How can I attach a private.img from one AppVM to another? Maybe even > once in read/write and in another scenario read only. > > This could be usefull for doing forensics on an AppVM or clam av scans etc. > > >> Neither in the AppVM nor in dom0 I see something like LVM, but as far as > >> I remember LVM was available in Qubes (I think have looked into it 1 or > >> 2 years ago. > > > > Since you have -cow.img files in /var/lib/qubes/appvms, your system > > seems to have been installed with one of the non-LVM options. This > > could be either Ext4 (rather limited) or Btrfs (flexible). Looking at > > the output of the 'mount' command in dom0 will tell you which. > > Stupid me, I wasn't aware that I installed Qubes without LVM ... why > should I do so? > > The only reason to fix this is likely to reinstall Qubes with LVM, but > what happens if I restore my old AppVMs from the non-LVM-setup? > Can you give some more details about the private.img vs private-cow.img > vs private-cow.img.old > > >From the Qubes docs > https://www.qubes-os.org/doc/template-implementation/ I learned that the > root.cow.img will hold the differences (from the appVM perspective) to > root.img (the root image of the template which is read only). > > Still I haven't understand what the private.cow.img and > private.cow.img.old do. > > Is there some more information regarding this topic? > We're all working on the assumption that you have Qubes 4.0 - can you confirm that? You can see what size is actually used on disk by using s flag to ls: so 'ls -lsS' will show you the apparent size and the actual size. In 3.2, to attach a private.img try: qvm-block -A dom0:/var/. -- 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/20190324021744.hzd3lgkenlsmn57m%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kernel 4.20 Can’t find
Hi, With qubes-dom0-update , I can’t find the kernel 4.20 version with the current or current testing or even the unstable. The further I can go is the 4.19. Is there something wrong in what I’m doing? Best Regards Aly Abdellatif -- 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/B92D4E03-407B-42F6-8E0A-F9D7830071F3%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: i3 support?
W dniu sobota, 23 marca 2019 21:11:49 UTC+1 użytkownik Stumpy napisał: > I have been considering looking into i3 on my qubes box but was > wondering about support in the future. As there appears to be a bit of a > learning curve i wanted to check before diving in. > > w/ v3 i was using kde then, as support seemed to wan, i switched over to > xfce which is admittedly lighter but doest seem to be as feature rich. > > is there any "official" stance on i3 now and going on into the future? There is an i3 package in main Qubes repo and it does work fine. I use i3 as my daily DE in Qubes and couldn't be happier with 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/556bb34f-c889-4274-84cb-83b5c79c11ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installing software..
PS...thanks for the correcting me! -- 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/4efaf472-68d8-44b2-bec1-ed54b948c86a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 Update breaks sys-usb widget
On 3/23/19 7:28 AM, ronp...@riseup.net wrote: > Qubes 4.0.1. > Following a recent dom0 update my sys-usb widget is partially broken; 1/ > devices show in the widget when plugged into usb port but are not > removed when unplugged from the port. 2/ Plugged in devices can be > attached to VM's via widget but there's now no indication (other the > qvm-block in dom0) that they are attached. 3/ Unable to detach usb > device from VM's via the widget (although I can do this from dom0). > > To check that I hadn't done something stupid and thereby broken the > widget I did the following procedure. > > 1. Reinstalled laptop with 4.0.1 from qubes website. > 2. Tested sys-usb widget - It worked perfectly. > 3. Updated Dom0 and tested widget - It worked perfectly. > 4. Rebooted laptop - tested widget, but its now broken - same diagnosis > as described above > > It seems that a dom0 update has broken the widget? > Does anyone else have this problem? > Yes, I have the same problem, and find the applet useful. Used to work well. Peter -- 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/366193a6-6428-a1fa-4238-a65435e105be%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] i3 support?
I have been considering looking into i3 on my qubes box but was wondering about support in the future. As there appears to be a bit of a learning curve i wanted to check before diving in. w/ v3 i was using kde then, as support seemed to wan, i switched over to xfce which is admittedly lighter but doest seem to be as feature rich. is there any "official" stance on i3 now and going on into the future? -- 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/0233f4d0-f166-6144-8edf-b466d3fc69bb%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] ongoing qubes manager work?
On 3/20/19 10:23 AM, unman wrote: On Sun, Mar 17, 2019 at 08:16:13AM -0400, Stumpy wrote: I seem to remember someone continuing work on the qubes manager, beyond bug fixes, but I cant find the post. I looked on github but it wasnt clear to me how much work was continuing with the qmanager. I find it really useful and assume others do as well as when 4.0 came i think quite a few people requested that it be put back. Anyway. I just wanted to find out if there is any ongoing work, especially regarding interface tweaks. I have what I admit is probably too many VMs but at the same time I use all of them and prefer not to change my work flow. One of the caveats is that there isnt much way to organize VMs in the interface apart from sorting. I'd love to have something like a customizable/collapsible tree of VMs among other things. Unfortuately my programming skills never got past "hello world" but i'd be happy to test out any work that someone might be doing. I don't think there was any serious work put in here. The intention was to drop QM from 4.0, and replace it with current widgets. There was some pressure to reinstate it and that was done. Other than the collapsible tree display, what else would you like to see? I don't use QM, and (without wanting to go over old ground) think it was a mistake bringing it back. Well i can see how some might want to kill it, but I really found it useful for "visualizing" the status of various vms all in one place as i run quite a few (in one place i can see what appvms are not using their respective updated templates, which templates have updates available, can see how much disk is being used, state, mem etc. Really its just the quick n easy being able to see, and occasionally interact with, interface. I am reasonably comfortable with a terminal but in my work flow the qm has its place, and for newbies that want "alittle bit more" its good (yes, best for the newbiest to just use the widgets but i still think there is value when they (I) want to see alittle bit mroe w/o devling into the terminal). Anyway, at the moment I'd just like a few teaks like the collapsible trees and a few more views to be available like say remaining space per appvm, % of drive space being used, % mem being used etc - perhaps some xentop-like features. I have to use a win machine at work, and while I am not a fan i do like tools like things like the systools process explorer and think qm could potentially show some things like that as well. IMHO :) -- 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/f4659297-9f0f-9f64-a81a-7b6a7f6db46c%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL report Dell OptiPlex 990 (3.2->4.0-rc3 update)
On Tuesday, January 30, 2018 at 9:51:12 AM UTC-6, steve.coleman wrote: > Just upgraded from 3.2 to 4.0-rc3. Working just fine. > > Steve Coleman Never mind. Found svc tag in doc you posted. It says it's a mini-tower. Thx. -- 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/49bff118-6cb5-4b62-908a-dee0fd7f0142%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] coreboot on modern hardware?
Spent several hours yesterday trying to track down what I would need to do to install coreboot on all of my computers, starting with my Qubes box: a Levnovo Thinkpad T480. The bottom line from what I can tell is that if you have an Intel CPU made since 2008 (any that have Boot Guard) or an AMD CPU made since 2013 (any that have PSP), you are out of luck. Libreboot spells this out in their docs. I'm not sure if that is because of coreboot itself or something specific to Libreboot. I was stuck by how they seemed perfectly fine walling themselves off from the present and the future. I could find nothing indicating that anyone had even tried, much less succeeded, in installing coreboot on a T480 and everything I did find was for much older hardware. I read through the coreboot docs where they just wave their hands at the end of the build process and say "now go flash". I also read through the heads docs, which say more or less the same thing. Hackaday has an article on the horrors of installing coreboot on a Toshiba laptop. Not only do they neglect to say which model they used, at the end of the article they had it working. The gist is that the information that's out there is out of date, incomplete, misleading, and sometimes just incompetent. I'm hoping that someone here has first-hand knowledge and can advise me (and others who read this). Thanks, John Smiley -- 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/91b65a9e-15d1-49a6-a828-13cc2c5b486b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Installing software..
On 3/19/19 4:59 PM, Steven Walker wrote: I am still pretty new to Qubes. I have managed to create a new qube, but I want to install some software for use with this qube. I have read that it has to be installed to the template and not the actual qube. As the template has no actual network connection, how do I go about this? Using 4.0.1, Fedora 29 Any help greatly appeciated. Steve pretty sure, there are different ways to skin the cat, though the Templates are designed to obtain access indirectly, that is what the "salt" stuff is they talk about it seems by default to be setup to use sys-whonix-14 to install updates , somewhat magically you can actually change the netvm without shutting down the templates generally it's bad form to give the templates direct access, though may you might want to once in while in order to troubleshoot something , etc .testing it the morning , you should be able to install non updates without Direct access for me Templates aren't worth backing up , I'm not worried about my system melting down much . and anyway its going to be best to fresh install , which is easy-ist in Qubes, which is one of the beauties of the technology hence, I clone for other reasons one word of advice is keep a paper list of custom packages you install so when it goes to Fedora-30 you install fresh and then add back fresh packages , your files will persist, my problem what few files I have end up spread out over 10 App Qubes -- 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/49bdea1a-d524-7089-ded3-2440f9fe884e%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
i could update amdgpu package to 18.0.1 using FC27 Updates, but the behavior with newer kernels is the same. the odd thing is with newer kernels that Xorg's starting two times at the same time: 1. Xorg.0.log >> [63.475] (II) AMDGPU(0): mem size init: gart size :b7c6e000 vram size: s:1ff2e8000 visible:f2e8000 2. 38.953] (II) AMDGPU(0): mem size init: gart size :b7c6e000 vram size: s:1fe316000 visible:e316000 the second one probing for Monitor goes on and failed with: [62.958] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [62.958] (WW) glamor: Failed to allocate 22x22 FBO due to GL_OUT_OF_MEMORY. [62.958] (WW) glamor: Expect reduced performance. at the end. please see attachments. -- 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/454d44dd-bb43-4f3f-8a4f-7ba8da973601%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [63.411] X.Org X Server 1.19.3 Release Date: 2017-03-15 [63.411] X Protocol Version 11, Revision 0 [63.411] Build Operating System: 4.9.3-200.fc25.x86_64 [63.411] Current Operating System: Linux dom0 5.0.2-1.pvops.qubes.x86_64 #1 SMP Thu Mar 21 05:52:58 UTC 2019 x86_64 [63.411] Kernel command line: root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-0dc31baf-2c25-4b70-9f0e-549a4da60935 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap acpi_backlight=vendor add_efi_memmap radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dpm=1 amdgpu.dc=1 plymouth.ignore-serial-consoles rhgb quiet [63.411] Build Date: 15 March 2017 06:37:12PM [63.411] Build ID: xorg-x11-server 1.19.3-1.fc25 [63.411] Current version of pixman: 0.34.0 [63.411]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [63.411] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [63.411] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 23 18:27:35 2019 [63.412] (==) Using config directory: "/etc/X11/xorg.conf.d" [63.412] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [63.412] (==) No Layout section. Using the first Screen section. [63.412] (==) No screen section available. Using defaults. [63.412] (**) |-->Screen "Default Screen Section" (0) [63.412] (**) | |-->Monitor "" [63.412] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [63.412] (**) | |-->Device "Sapphire NITRO+ RX 590" [63.412] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [63.412] (==) Automatically adding devices [63.412] (==) Automatically enabling devices [63.412] (==) Automatically adding GPU devices [63.412] (==) Automatically binding GPU devices [63.412] (==) Max clients allowed: 256, resource mask: 0x1f [63.412] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [63.412] (==) ModulePath set to "/usr/lib64/xorg/modules" [63.412] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [63.412] (II) Loader magic: 0x825e00 [63.412] (II) Module ABI versions: [63.412]X.Org ANSI C Emulation: 0.4 [63.412]X.Org Video Driver: 23.0 [63.412]X.Org XInput driver : 24.1 [63.412]X.Org Server Extension : 10.0 [63.413] (++) using VT number 1 [63.413] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [63.414] (II) xfree86: Adding drm device (/dev/dri/card0) [63.425] (--) PCI:*(0:1:0:0) 1002:67df:1da2:e366 rev 225, Mem @ 0xc000/268435456, 0xd000/2097152, 0xdfe0/262144, I/O @ 0xe000/256, BIOS @ 0x/131072 [63.425] (II) LoadModule: "glx" [63.425] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [63.428] (II) Module glx: vendor="X.Org Foundation" [63.428]compiled for 1.19.3, module version = 1.0.0 [63.428]ABI class: X.Org Server Extension, version 10.0 [63.428] (II) LoadModule: "amdgpu" [63.428] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so [63.429] (II) Module amdgpu: vendor="X.Org Foundation" [63.429]compiled for 1.19.6, module version = 18.0.1 [63.429]Module class: X.Org Video Driver [63.429]ABI class: X.Org Video Driver,
[qubes-users] Re: Dom0 Update breaks sys-usb widget
On 3/23/19 11:28 AM, ronpunz-sgozh3hwpm2stnjn9+b...@public.gmane.org wrote: Qubes 4.0.1. Following a recent dom0 update my sys-usb widget is partially broken; 1/ devices show in the widget when plugged into usb port but are not removed when unplugged from the port. 2/ Plugged in devices can be attached to VM's via widget but there's now no indication (other the qvm-block in dom0) that they are attached. 3/ Unable to detach usb device from VM's via the widget (although I can do this from dom0). To check that I hadn't done something stupid and thereby broken the widget I did the following procedure. 1. Reinstalled laptop with 4.0.1 from qubes website. 2. Tested sys-usb widget - It worked perfectly. 3. Updated Dom0 and tested widget - It worked perfectly. 4. Rebooted laptop - tested widget, but its now broken - same diagnosis as described above It seems that a dom0 update has broken the widget? Does anyone else have this problem? And you don't want to use the terminal eg qvm-usb attach sys-usb:2-10 etc? afaik the widget has never been reliable, and faster for me just to do it in a terminal than expect the widget to 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/fa9adca4-c90d-bee6-adb4-5b1c7ef83234%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL report Dell OptiPlex 990 (3.2->4.0-rc3 update)
On Tuesday, January 30, 2018 at 9:51:12 AM UTC-6, steve.coleman wrote: > Just upgraded from 3.2 to 4.0-rc3. Working just fine. > > Steve Coleman Steve, what format (min-tower, desktop, SFF) is your Opti 990? Lots on used market but there can be subtle diffs between same model format. Thanks. Kasey -- 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/76a239e0-d9d5-493f-91ee-67f3acd9cecd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Compiling kernel modules
Hi there, I am trying to connect my qubes box via wifi - but I cannot compile any kernel module for my wifi cards (on both fedora 26 and 29). The compilation fails at the first object file: [user@sys-usb rtl8821AU]$ make make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.14.103-1.pvops.qubes.x86_64/build M=/home/user/rtl8821AU modules make[1]: Entering directory '/usr/lib/modules/4.14.103-1.pvops.qubes.x86_64/build' make[2]: *** No rule to make target '/home/user/rtl8821AU/core/rtw_cmd.o', needed by '/home/user/rtl8821AU/8821au.o'. Stop. make[1]: *** [Makefile:1535: _module_/home/user/rtl8821AU] Error 2 make[1]: Leaving directory '/usr/lib/modules/4.14.103-1.pvops.qubes.x86_64/build' make: *** [Makefile:2003: modules] Error 2 but the source file for that object file is there: [user@sys-usb rtl8821AU]$ ls /home/user/rtl8821AU/core/rtw_cmd.c /home/user/rtl8821AU/core/rtw_cmd.c I have installed the headers: sudo dnf install make automake gcc gcc-c++ kernel-devel This looks like it must be something silly - but I really cannot find anything. I have installed the I have also tried the kernel modules that are already in the system for the two cards that I have bought (tp-link AC600 Archer T2UH and Edimax EW-7811UTC) - but no result, i.e. /proc/net/dev does not show anything, I am doing it in sys-usb - so that the access to the device is a sure thing. The Edimax one explicitly lists Linux as supported but the instructions still require compiling a kernel module. -- Zbigniew Lukasiak https://medium.com/@zby http://brudnopis.blogspot.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 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/CAGL_UUtNizZdziLdrpJ7HhpPn5_NoRyH9SCOdKV1gaQhTPXBPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
On Saturday, March 23, 2019 at 7:44:52 AM UTC+1, Foppe de Haan wrote: > On Friday, March 22, 2019 at 11:41:12 PM UTC, CooSee wrote: > > how to compile rpms on Qubes - maybe i can use the current available > > xorg-x11-drv-amdgpu and mybe xorg and mesa too. > if you want to play around with this, it's probably easier to change the > fedora (updates?) distro from fc25 to fc29 in /etc/yum.repos.d/, input the > correct signing key, and try installing the new xorg-x11-drv-amdgpu using > qubes-dom0-update. > > > after login with new kernels, the desktop is loading just for 1 sec. > > > there must be an error in the system, because i also tried KDE and Awesome > > - same behaviour, e.g. Lightdm backround is scrambled with glitches at > > login screen and it always kicks me back to login screen - using Dual > > Monitor Setup. > yeah, sounds like there's a driver issue > > 4.14.103 is working fine, but only with ' amdgpu.dpm=0 ' <<< is this bad > > for the device ? > why did you try that option, specifically? phoronix guide? anyway, as he > writes, it's not harmful, it just won't game very well. ;) the amdgpu.dpm=0 option with 4.14 kernel is necessary, because without it the screen goes black and the fans are starting to blow up! on all kernels, amdgpu is always loaded, no difference. i updated the pci.ids file for better detection. changed yum.repos.d and tried, but: qubes-dom0-update Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Last metadata expiration check: 0:36:18 ago on Sat Mar 23 12:43:25 2019. Error: Problem: The operation would result in removing the following protected packages: dnf, systemd, systemd-udev (try to add '--skip-broken' to skip uninstallable packages) with --skip-broken the same answer >> The operation would result in removing the following protected packages: dnf, systemd, systemd-udev installing xorg-x11-drv-amdgpu from fc29 won't work because it depends on newer version of xorg >> xserver-abi (videodrv-24) and todo so it would brake the system and uninstall dnf!? this is awful - that's why i never liked RPM based distros - it's PITA handling with packages. is some one so kind and compile the newest version of xorg-x11-drv-amdgpu for FC25 and make it also officially available for all the users with newer AMD Graphics? i noticed that the 'amd_iommu_v2' driver is loaded too, but even though, kernel 4.14.103 can handle the desktop but newer kernels not, somehow. i tried to blacklist to try without - but didn't work at all - it's always loading besides amdgpu module! dmesg says >> AMD_IOMMUV2 funktionality not available on this system. thx for your efford :-) -- 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/38975fad-7c1f-45c5-91d7-e6219766eace%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Using screen via dp alt mode
> On Friday, March 22, 2019 at 11:42:56 AM UTC-5, wzrd73 wrote: > > > Hallo, > > is there a way to use an additional screen via dp alt mode (usb-c) in Qubes > > 4? > > I'd like to attach an Asus Zen Screen to my laptop. The screen only has a > > usb-c port. My laptop has usb-a und usb-c and hdmi ports. > > There are usb-c to hdmi adapters, but as far as I know they don't work in > > the other direction. > > I'm driving a monitor from my usb-c port (although the cable converts it to > HDMI). I would start with looking at the output of xrandr. On my computer, I > see a listing for DP1. > > If you install arandr in dom0 you'll get an easier to use interface. > > Jon > > My output of xrandr: [User@dom0 ~]$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 190mm 1920x1080 60.00*+ 40.00 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1280x960 60.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 HDMI1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Message on the screen, when I connect it: "Your device does not support DP Alt mode, please install the latest driver and try again." The device shows up as: sys-usb:2-4.1 - Realtek_BillBoard_Device_123..FGH sys-usb:3-3.2 - DisplayLink_MB16AC_821.M0419 -- 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/jox1f6EfEPnV6fSwpi5cHqACNkfG3aZ0nFG3GZ7nCG7aBv6gz7AD6tev3r2ChcemSz6foQfWxSiEOrrsytQZJh_Pb1vamVksF0Y6d0VIJ-Y%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Using screen via dp alt mode
On Friday, March 22, 2019 at 11:42:56 AM UTC-5, wzrd73 wrote: > Hallo, > > is there a way to use an additional screen via dp alt mode (usb-c) in Qubes 4? > > I'd like to attach an Asus Zen Screen to my laptop. The screen only has a > usb-c port. My laptop has usb-a und usb-c and hdmi ports. > > There are usb-c to hdmi adapters, but as far as I know they don't work in the > other direction. I'm driving a monitor from my usb-c port (although the cable converts it to HDMI). I would start with looking at the output of xrandr. On my computer, I see a listing for DP1. If you install arandr in dom0 you'll get an easier to use interface. Jon -- 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/3e6fc535-6802-4818-b466-04918d8e65c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Shrinking a private volume
Hello Chris, thank you once again for your feedback. On 3/23/19 11:31 AM, Chris Laprise wrote: > On 3/23/19 5:34 AM, onw7two99 wrote: >> I run sudo fstrim -av from within the AppVM (as root) but I haven't >> notive any change. > > The difference doesn't show until you shutdown the vm for the second > time (the current .old volume gets deleted). Also the Qubes disk > widget and Qubes Manager take some time to report the new values. But > running fstrim may not make any difference if you haven't been > deleting many files. if I run ls -lah /var/lib/qubes/appvms/ the size listed is the "thick provisioned", is there a way to show the "real" file size in dom0 whch should be the used size which is reported from within the AppVM when using "df -h" ? >> Is there a way to move this private disk to the new storage-qube? > > Yes, you can use the 'mv' command while the two vms are not running. > Keep in mind this can erase the existing private image of the > new/destination vm unless you rename that first (but it won't be > accessible after renaming it, unless you run 'qvm-block attach'). I tried to mount the private.img from the old appvm to the new one, but I think I don't have the correct syntax. I tried: qvm-block attach :private.img qvm-block attach /var/lib/qubes/appvms//private.img How can I attach a private.img from one AppVM to another? Maybe even once in read/write and in another scenario read only. This could be usefull for doing forensics on an AppVM or clam av scans etc. >> Neither in the AppVM nor in dom0 I see something like LVM, but as far as >> I remember LVM was available in Qubes (I think have looked into it 1 or >> 2 years ago. > > Since you have -cow.img files in /var/lib/qubes/appvms, your system > seems to have been installed with one of the non-LVM options. This > could be either Ext4 (rather limited) or Btrfs (flexible). Looking at > the output of the 'mount' command in dom0 will tell you which. Stupid me, I wasn't aware that I installed Qubes without LVM ... why should I do so? The only reason to fix this is likely to reinstall Qubes with LVM, but what happens if I restore my old AppVMs from the non-LVM-setup? Can you give some more details about the private.img vs private-cow.img vs private-cow.img.old >From the Qubes docs https://www.qubes-os.org/doc/template-implementation/ I learned that the root.cow.img will hold the differences (from the appVM perspective) to root.img (the root image of the template which is read only). Still I haven't understand what the private.cow.img and private.cow.img.old do. Is there some more information regarding this topic? - O -- 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/75368c21-ba56-e565-6cf1-fef15a3924b8%40gmail.com. For more options, visit https://groups.google.com/d/optout. pEpkey.asc Description: application/pgp-keys
[qubes-users] Qubes' onion service is 404
Hello, Qubes' onion service has not been working for 48 hours. What is going on? Is it going to be fixed anytime soon? Thanks -- 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/pEMPmm-_WoHdMRftXIqySmjOr1t3Z8kosMFpgo7ykJznb4_bVt_jU8XFLSoa1T-eo9lZVU8zhvnMwPdYdmCwSWKoaGSB_S-J7eBzo_Mb1mg%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 Debian Packages Question
Thanks for the explanation! -- 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/9081d3d8-f5ad-8a86-a35c-fe6b69ef9e51%40go-bailey.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Dom0 Update breaks sys-usb widget
Qubes 4.0.1. Following a recent dom0 update my sys-usb widget is partially broken; 1/ devices show in the widget when plugged into usb port but are not removed when unplugged from the port. 2/ Plugged in devices can be attached to VM's via widget but there's now no indication (other the qvm-block in dom0) that they are attached. 3/ Unable to detach usb device from VM's via the widget (although I can do this from dom0). To check that I hadn't done something stupid and thereby broken the widget I did the following procedure. 1. Reinstalled laptop with 4.0.1 from qubes website. 2. Tested sys-usb widget - It worked perfectly. 3. Updated Dom0 and tested widget - It worked perfectly. 4. Rebooted laptop - tested widget, but its now broken - same diagnosis as described above It seems that a dom0 update has broken the widget? Does anyone else have this problem? -- 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/af90a3037a8792c924b7858f36929eb2%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Shrinking a private volume
On 3/23/19 5:34 AM, onw7two99 wrote: Hello Brendan On 2/28/19 3:14 AM, brendan.h...@gmail.com wrote: I’ve found it necessary sometimes to sudo fstrim -av from inside the VM in order for the dom0 lvm thin provisioned volumes to return the unallocated space back to the pool. This doesn’t shrink the volume but it does tell the system that it doesn’t need to store anything there for that VM currently so other VMs can use the space. Welcome to thin provisioning! I run sudo fstrim -av from within the AppVM (as root) but I haven't notive any change. The difference doesn't show until you shutdown the vm for the second time (the current .old volume gets deleted). Also the Qubes disk widget and Qubes Manager take some time to report the new values. But running fstrim may not make any difference if you haven't been deleting many files. The AppVM has currently a 145GB private disk attached, from which 91GB is used, 44GB is free. I would like to move this data to another storage qube, but I have only 58GB available (df -h) in dom0. Therefore I thought that I can someone move the private disk of "storage-qube-old" to "storage-qube-new". I have looked into /var/lib/qubes/appvms/storage-qube-old and see 3 private images: private-cow.img -> 147 GB private-cow.img.old -> 147 GB private-cow.img -> 147 GB Is there a way to move this private disk to the new storage-qube? Yes, you can use the 'mv' command while the two vms are not running. Keep in mind this can erase the existing private image of the new/destination vm unless you rename that first (but it won't be accessible after renaming it, unless you run 'qvm-block attach'). Also keep in mind that any problems the old vm had arising from anything in /rw or /home will be carried over to the new vm. Slightly offtopic: I haven't understand at which layer thin provisioning works in Qubes. Neither in the AppVM nor in dom0 I see something like LVM, but as far as I remember LVM was available in Qubes (I think have looked into it 1 or 2 years ago. Since you have -cow.img files in /var/lib/qubes/appvms, your system seems to have been installed with one of the non-LVM options. This could be either Ext4 (rather limited) or Btrfs (flexible). Looking at the output of the 'mount' command in dom0 will tell you which. -- 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 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/1f38cbf1-482c-2c57-55a7-0108af8632f7%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] sys-usb based on fedora-29-minimal >> what am I missing?
Hello Qubes Community, I have been trying to get sys-usb working using a fedora-29-minimal template Unfortunately it will not work, even after installing all packages which "should" be enough to get sys-usb working (Link https://www.qubes-os.org/doc/templates/fedora-minimal/). If I use the default fedora-28 (fat template) for sys-usb, everything is working and I can attach my external harddrive to an AppVM. If I use my custom build template for sys-usb, other USB devices work, but I can't attach a harddrive to another AppVM, from the GUI it looks like the drive is attached, but it is not shown in nautilus in the target-AppVM, where I can then click on it and mount it. Any idea what I am missing or how I can proceed troubleshooting? As all my VMs are based on custom build templates (fedora-29-minimal) I don't want to have the fat fedora-28 template only because sys-usb will not work. To reproduce the problem: this is how I build my sys-vm-Template from scratch (fedora-29-minimal) which I am using for sys-net, sys-firewall and sys-usb (it it would work). Hint: You might need to change the wifi drivers if you are using another wifi card modell. "iwl6000g2a-firmware" is for my lenovo x230. --- --- --- 8< --- --- --- --- --- --- --- 8< --- --- --- # script to build a sys-vm template based on fedora-29-minimal # the base template which is used to build my own sys-template template=fedora-29-minimal #my custom made template for sys-vms: systemplate=t-fedora-29-sys # get fedora-29-minimal template (only needs to be done once) sudo qubes-dom0-update qubes-template-$template #remove an old template (if it exists) qvm-kill $systemplate qvm-remove -f $systemplate #clone template qvm-clone $template $systemplate # update template qvm-run --auto --user root --pass-io --no-gui $systemplate \ 'dnf update -y' # install a missing package for fedora-29-minimal # without it, gui-apps will not start qvm-run --auto --user root --pass-io --no-gui $systemplate \ 'dnf install -y # Install required packages for Sys-VMs qvm-run --auto --user root --pass-io --no-gui $systemplate \ 'dnf -y install e2fsprogs qubes-core-agent-qrexec \ qubes-core-agent-systemd qubes-core-agent-networking polkit \ qubes-core-agent-network-manager notification-daemon \ qubes-core-agent-dom0-updates qubes-usb-proxy \ iwl6000g2a-firmware qubes-input-proxy-sender iproute iputils \ NetworkManager-openvpn NetworkManager-openvpn-gnome \ NetworkManager-wwan NetworkManager-wifi \ network-manager-applet qubes-core-agent-passwordless-root' # Optional packages you might want to install in the sys-template: qvm-run --auto --user root --pass-io --no-gui $systemplate \ 'dnf -y install nano less pciutils xclip' # Set new template as template for sys-vms qvm-shutdown --all --wait --timeout 120 qvm-prefs --set sys-usb template $systemplate qvm-prefs --set sys-net template $systemplate qvm-prefs --set sys-firewall template $systemplate qvm-prefs --set sys-vpn template $systemplate qvm-start sys-firewall sys-usb --- --- --- 8< --- --- --- --- --- --- --- 8< --- --- --- - O. -- 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/0d79f831-dca6-3bec-138f-7b33663cd8ea%40gmail.com. For more options, visit https://groups.google.com/d/optout. pEpkey.asc Description: application/pgp-keys
Re: [qubes-users] Shrinking a private volume
Hello Brendan On 2/28/19 3:14 AM, brendan.h...@gmail.com wrote: > I’ve found it necessary sometimes to sudo fstrim -av from inside the VM in > order for the dom0 lvm thin provisioned volumes to return the unallocated > space back to the pool. > This doesn’t shrink the volume but it does tell the system that it doesn’t > need to store anything there for that VM currently so other VMs can use the > space. > Welcome to thin provisioning! I run sudo fstrim -av from within the AppVM (as root) but I haven't notive any change. The AppVM has currently a 145GB private disk attached, from which 91GB is used, 44GB is free. I would like to move this data to another storage qube, but I have only 58GB available (df -h) in dom0. Therefore I thought that I can someone move the private disk of "storage-qube-old" to "storage-qube-new". I have looked into /var/lib/qubes/appvms/storage-qube-old and see 3 private images: private-cow.img -> 147 GB private-cow.img.old -> 147 GB private-cow.img -> 147 GB Is there a way to move this private disk to the new storage-qube? Slightly offtopic: I haven't understand at which layer thin provisioning works in Qubes. Neither in the AppVM nor in dom0 I see something like LVM, but as far as I remember LVM was available in Qubes (I think have looked into it 1 or 2 years ago. - O -- 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/80198411-b1f9-c56d-3151-4ccf86cf6e90%40gmail.com. For more options, visit https://groups.google.com/d/optout. pEpkey.asc Description: application/pgp-keys
Re: [qubes-users] Re: qvm-usb not functioning
On Sat, Mar 23, 2019 at 3:23 AM unman wrote:
>
> On Fri, Mar 22, 2019 at 06:32:07AM -0700, Zbigniew Łukasiak wrote:
> > On Friday, December 1, 2017 at 12:58:59 PM UTC+1, awokd wrote:
> > > On Fri, December 1, 2017 05:50, Drew White wrote:
> > > > On Tuesday, 21 November 2017 06:45:02 UTC+11, awokd wrote:
> > > >> On Mon, November 20, 2017 02:32, Drew White wrote:
> > > >> > Hi folks, sys-usb still isn't functioning and allowing me to attach a
> > > >> > device.
> > > >> >
> > > >> > help please?
> > >
> > > Let's start over. Describe your Qubes version, the USB device you are
> > > trying to attach, which USB controllers you have assigned to sys-usb or
> > > dom0, and the output of commands you use when attaching.
> >
> > I have a similar problem - qvm-usb retuns an empty list.
> >
> > [root@dom0 zby]# qvm-usb
> > BACKEND:DEVID DESCRIPTION USED BY
> > [root@dom0 zby]# lsusb
> > Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
> > Bus 001 Device 011: ID 148f:761a Ralink Technology, Corp.
> > Bus 001 Device 004: ID 03f0:0641 Hewlett-Packard
> > Bus 001 Device 003: ID 413c:2111 Dell Computer Corp.
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> >
> > This is Qubes 4.0
> >
> > I tried the recoding suggestion - I added "ID_SERIAL=`echo ${ID_SERIAL} |
> > iconv -t ASCII//TRANSLIT`" in /usr/lib/qubes/udev-usb-add-change and then
> > removed and put back the device - but that did not change the result.
> >
> >
> >
> > Cheers,
> > Zbigniew
> >
>
> What's the USB device you are trying to attach?
This time I needed the wifi card (Ralink) - but this is not the first
time I had this problem.
> I'm assuming you chose not to create a sys-usb.
Yes - and after someone on irc advised me to create it - that fixed
the problem. Maybe this is a documentation problem - apparently
sys-usb is kind of obligatory now.
Cheers,
Zbigniew
--
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/CAGL_UUvou106_6-7MWksmRXNrH577c4msL-PwNKLX4FGsgQMEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
On Friday, March 22, 2019 at 11:41:12 PM UTC, CooSee wrote: > how to compile rpms on Qubes - maybe i can use the current available > xorg-x11-drv-amdgpu and mybe xorg and mesa too. if you want to play around with this, it's probably easier to change the fedora (updates?) distro from fc25 to fc29 in /etc/yum.repos.d/, input the correct signing key, and try installing the new xorg-x11-drv-amdgpu using qubes-dom0-update. > after login with new kernels, the desktop is loading just for 1 sec. > there must be an error in the system, because i also tried KDE and Awesome - > same behaviour, e.g. Lightdm backround is scrambled with glitches at login > screen and it always kicks me back to login screen - using Dual Monitor Setup. yeah, sounds like there's a driver issue > 4.14.103 is working fine, but only with ' amdgpu.dpm=0 ' <<< is this bad for > the device ? why did you try that option, specifically? phoronix guide? anyway, as he writes, it's not harmful, it just won't game very well. ;) -- 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/2753e7d6-d4aa-4e7c-b2bc-8f41bbe7a690%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: all new kernels are unusable with amdgpu - Sapphire Nitro + RX590
On Saturday, March 23, 2019 at 2:18:52 AM UTC, CooSee wrote: > i found this Error in Xorg.0.log - only with newer Kernel. > > [ 123.712] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage > [ 123.719] (WW) glamor: Failed to allocate 200x200 FBO due to > GL_OUT_OF_MEMORY. > [ 123.719] (WW) glamor: Expect reduced performance. > > why 4.14.103-1 Kernel can handle the login and newer Kernels not ? > > thx is there a difference in which driver it loads (lspci -nnk | grep -i vga -A 3)? -- 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/d5babfee-f2f7-4f9a-8694-84a2a7dcd5fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
