Re: [qubes-users] Re: EE-PROM of an Lenovo X230
As far as I know, all the RaPi should work for this. If you are looking for cost effective, you can get a RaPi Zero on Sparkfun or Adafruit for around $10. I would expect NewEgg to be pricey. ‐‐‐ Original Message ‐‐‐ On Friday, March 13, 2020 7:48 PM, wrote: > While I have read of others who just plowed though with whatever ch431a they > had, and gotten it to work. I am inclined to look at getting a PI. I am > looking at Newegg, I am guessing I can get the least expensive Raspberry Pi. > I have a few weeks before my Social Security is paid. Most of my extra > money is now tied up in Corona-ing up my pantry and for other prevention > measures. > > Any suggestions of what - which Raspberry Pi to avoid? > > -- > 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/03a1a5ca-5471-4b0b-a621-11a869a95981%40googlegroups.com](https://groups.google.com/d/msgid/qubes-users/03a1a5ca-5471-4b0b-a621-11a869a95981%40googlegroups.com?utm_medium=email_source=footer). -- 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/czUKkyNvkpg1Ww1QB9vTn7DHCqbbn2DVgFN0FrSE0qBv4EnNz_C7JHECxTkaeTFiRBcvXdTgYrc8y2bU3M2I6gRjlqEcUNnVLCe-DbilXsk%3D%40karatronics.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
Thanks for the reply. Your answer flipped a switch in my brain and I checked the fedora issues. The answer was so simple for me. You might try it too. Go into the qube settings for sys-net. Click on the advanced tab and there in the upper right corner you can choose an earlier kernel. Reboot the computer and presto my wireless is working again. Thanks for all the help On Friday, March 13, 2020 at 8:57:58 PM UTC-4, bill...@gmail.com wrote: > > > You might try changing the template for sys-net from fedora to debian. > However, for me, it turns out that the debian template has old firmware for > my wireless device, and so I can't get wireless with it, either. But at > least it's a different error > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/740d6467-e8e4-4be7-8fff-1ae3c27e3369%40googlegroups.com.
Re: [qubes-users] Re: EE-PROM of an Lenovo X230
While I have read of others who just plowed though with whatever ch431a they had, and gotten it to work. I am inclined to look at getting a PI. I am looking at Newegg, I am guessing I can get the least expensive Raspberry Pi. I have a few weeks before my Social Security is paid. Most of my extra money is now tied up in Corona-ing up my pantry and for other prevention measures. Any suggestions of what - which Raspberry Pi to avoid? -- 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/03a1a5ca-5471-4b0b-a621-11a869a95981%40googlegroups.com.
Re: [qubes-users] I need help with IOMMU issues
> A simple search on Google for "Ryzen 7 2700u and Qubes" yields a list of > posts. > > Mike. I'm not seeing much pertinent to my issue. > there's also a IOMMU bios option that needs to be enabled. "should" is > something you and bios makers seem to differ on, and I think they win. ;) I've heard the horror stories of both consumer grade Lenovo hardware and OEM Ryzen Mobile APU support, so I know I'm pretty much screwed over by the BIOS at this point, but I was wondering if I could find any workarounds. The BIOS option I mentioned has the description: AMD SVM Technology: When enabled, a VM software can utilize the additional hardware capabilities provided by Virtual Technology [X] Virtual Technology is [ENABLED/DISABLED] I did install Qubes on a usb from another system, then inserted it into this one, I have seen posts about this. When SVM Technology is enabled and the iommu command line flag is called, the system crashes at autostarting the system VMs, removing it allows it to boot, but as before, no IOMMU, so PVH domains cannot be used. Whenever the SVM Technology is disabled, it crashes whether or not the flag is called. I've read about broken ACPI tables and using command line options to manually assign the hardware to the system, so I was wondering about this sort of workaround. Or is it not possible outside of hypothetically spending a lot of time building a custom coreboot image or something similar? Sidenote: what do I lose if I just concede to run without IOMMU and PVH domains? -- 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/7856234a1136a61679fe2be715f8ecd5.squirrel%40giyzk7o6dcunb2ry.onion.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
You might try changing the template for sys-net from fedora to debian. However, for me, it turns out that the debian template has old firmware for my wireless device, and so I can't get wireless with it, either. But at least it's a different error -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d127017a-bfd2-46bf-9ce1-6bdd0bfa9b4d%40googlegroups.com.
[qubes-users] Re: Dom 0 latest update disabled my wireless device.
> > I did a search on this. There have been a number of folk complaining of > it on the fedora groups. It seems to have been a problem with a recent > kernel update. > It's happened to me, too. On the fedora boards, it is fixed by installing the newest kernel update. My problem is that I don't have an ethernet connection, and rely entirely on wirelss. So... I can't update the kernel because I can't get on the intertubes. I"m going to try one of my old usb wireless devices and see if any of them work... billo > > -- 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/f5cd14a3-460b-49a4-a5bc-45c21fc9d81f%40googlegroups.com.
Re: [qubes-users] Forgot to RTFM and now getting errors in whonix during update? (and deb template "qubes-core-agent-passwordless-root" error)
On 2020-03-13 18:05, Stumpy wrote: I had tried to install bisq on my whonix ws template and for "some reason" (which i later found out when i did read the whonix docs) it wasnt working. I now have the issue that when i try to update i get the following: user@host:~$ sudo apt update && sudo apt upgrade Hit:1 https://packages.riot.im/debian buster InRelease Hit:2 tor+https://deb.debian.org/debian-security buster/updates InRelease Hit:3 https://deb.qubes-os.org/r4.0/vm buster InRelease Hit:4 https://updates.signal.org/desktop/apt xenial InRelease Hit:5 tor+https://deb.whonix.org buster InRelease Hit:6 tor+https://deb.debian.org/debian buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up bisq (1.2.7) ... Adding shortcut to the menu xdg-desktop-menu: No writable system menu directory found. dpkg: error processing package bisq (--configure): installed bisq package post-installation script subprocess returned error exit status 3 Errors were encountered while processing: bisq E: Sub-process /usr/bin/dpkg returned an error code (1) Its not clear to me how i can clean up things and resolve this error? Oh, and a similar but separate issue is on my debian template, i cant figure if i messed something up or not but when i try to install things i am getting an qubes-core-agent-passwordless-root error: user@debian-10:~/QubesIncoming/disp6616$ sudo apt update && sudo apt upgrade && sudo apt install lutris Get:1 http://download.opensuse.org/repositories/home:/strycore/Debian_9.0 ./ InRelease [1,504 B] Hit:2 https://deb.qubes-os.org/r4.0/vm buster InRelease Hit:3 https://deb.debian.org/debian buster InRelease Get:4 http://download.opensuse.org/repositories/home:/strycore/Debian_9.0 ./ Packages [823 B] Hit:5 https://deb.debian.org/debian-security buster/updates InRelease Fetched 2,327 B in 3s (873 B/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 30.3 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 https://deb.qubes-os.org/r4.0/vm buster/main amd64 qubes-core-agent-passwordless-root amd64 4.0.51-1+deb10u1 [30.3 kB] Fetched 30.3 kB in 2s (15.8 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: cabextract curl fluid-soundfont-gm fluid-soundfont-gs gir1.2-gdesktopenums-3.0 gir1.2-gnomedesktop-3.0 lib32gcc1 libc6-i386 libcurl4 libmspack0 mesa-utils p7zip python3-evdev python3-yaml Suggested packages: fluidsynth timidity p7zip-full python-evdev-doc The following packages will be REMOVED: qubes-core-agent-passwordless-root The following NEW packages will be installed: cabextract curl fluid-soundfont-gm fluid-soundfont-gs gir1.2-gdesktopenums-3.0 gir1.2-gnomedesktop-3.0 lib32gcc1 libc6-i386 libcurl4 libmspack0 lutris mesa-utils p7zip python3-evdev python3-yaml 0 upgraded, 15 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 128 MB of archives. After this operation, 174 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://download.opensuse.org/repositories/home:/strycore/Debian_9.0 ./ lutris 0.5.4 [1,778 kB] Get:2 https://deb.debian.org/debian buster/main amd64 libmspack0 amd64 0.10.1-1 [49.9 kB] Get:3 https://deb.debian.org/debian buster/main amd64 cabextract amd64 1.9-1 [35.0 kB] Get:4 https://deb.debian.org/debian-security buster/updates/main amd64 libcurl4 amd64 7.64.0-4+deb10u1 [331 kB] Get:5 https://deb.debian.org/debian-security buster/updates/main amd64 curl amd64 7.64.0-4+deb10u1 [264 kB] Get:6 https://deb.debian.org/debian buster/main amd64 fluid-soundfont-gm all 3.1-5.1 [120 MB] Get:7 https://deb.debian.org/debian buster/main amd64 fluid-soundfont-gs all 3.1-5.1 [2,474 kB] Get:8 https://deb.debian.org/debian buster/main amd64 gir1.2-gdesktopenums-3.0 amd64 3.28.1-1 [8,700 B] Get:9 https://deb.debian.org/debian buster/main amd64 gir1.2-gnomedesktop-3.0 amd64 3.30.2.1-2 [29.7 kB] Get:10 https://deb.debian.org/debian buster/main amd64 libc6-i386 amd64 2.28-10 [2,872 kB] Get:11 https://deb.debian.org/debian buster/main amd64 lib32gcc1 amd64 1:8.3.0-6 [47.9 kB] Get:12 https://deb.debian.org/debian buster/main
[qubes-users] Forgot to RTFM and now getting errors in whonix during update?
I had tried to install bisq on my whonix ws template and for "some reason" (which i later found out when i did read the whonix docs) it wasnt working. I now have the issue that when i try to update i get the following: user@host:~$ sudo apt update && sudo apt upgrade Hit:1 https://packages.riot.im/debian buster InRelease Hit:2 tor+https://deb.debian.org/debian-security buster/updates InRelease Hit:3 https://deb.qubes-os.org/r4.0/vm buster InRelease Hit:4 https://updates.signal.org/desktop/apt xenial InRelease Hit:5 tor+https://deb.whonix.org buster InRelease Hit:6 tor+https://deb.debian.org/debian buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up bisq (1.2.7) ... Adding shortcut to the menu xdg-desktop-menu: No writable system menu directory found. dpkg: error processing package bisq (--configure): installed bisq package post-installation script subprocess returned error exit status 3 Errors were encountered while processing: bisq E: Sub-process /usr/bin/dpkg returned an error code (1) Its not clear to me how i can clean up things and resolve this error? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5683c33f-aee3-d165-9aa3-6ed510e52bdc%40posteo.net.
Re: [qubes-users] Re: EE-PROM of an Lenovo X230
"I haven't found controllers that deliver 5V when flashing" I agree with this halfway. All the CH341As I've personally seen supply 3.3VCC out of the box, but 5V logic. All of the schematics I've seen on the internet show this, so I don't think its just me. The 5V logic levels come from the CH341A which runs off the USB5V rail and is configured for 5VIO. 3.3VCC comes from a separate supply LDO. It is dumb, and I've wondered sometimes if the CH341A was designed to make things worse, though more likely an ad nauseam repetition of a bad design that is super cheap to produce and easy make a quick buck. All the discussions I've seen on the CH341A voltage issues have to do with IO voltage, not VCC. I wouldn't call the IO voltage issue "garbage". It is a legit concern, and only Winbond can say differently. On the X-230, the spec'd max VIH for the Windbond PROM is 3.7V with a 3.3VCC rail. The datasheet doesn't mention 5V IO tolerance. I don't doubt that 5V logic will work in many cases, but the real-world limit is set by physics, process, operating condition, and component skew. For a random PROM in a sufficiently large distribution of PROMs, we have to assume 5V will damage the IO, then your system won't boot, and you would have to change the PROM. It is a dice roll. (BTW, I'm not addressing the CPU IO. I don't have a schematic or CPU specs to know what kind of protection is on that end, but one may be risking that as well.) The RaPi method works well outt of the box @ 3.3VCC and 3.3V Logic using the latest Rasperian. One doesn't even need to connect to the internet. Suitable RaPi are available for $5-$10USD, but that won't give you the Pamona clip. The cheapest Pamona clip I've seen comes bundled with the CH341 for a few bucks, which is kind of funny. At least the RaPi can be used for other cool stuff. I've also read about some people using Arduinos to program BIOS PROMs, though that seemed like more work than a RaPi. > > ‐‐‐ Original Message ‐‐‐ > On Friday, March 13, 2020 8:00 AM, unman un...@thirdeyesecurity.org wrote: > > > On Fri, Mar 13, 2020 at 03:35:05AM +, Mike Karasoff wrote: > > > > > As far as the voltages go, I'm not sure I understand unman's "garbage" > > > comment. The PROMs on your X-230 are 3.3V logic, but the CH341A > > > programmer usually has 5V logic. I've heard that some CH341A are 3.3V, > > > but that seems more because there are several different places in China > > > producing the same board and so its kind of random. > > > I think you can use 5V logic to program these ICs, but you are doing so > > > at your own risk. There is no current limiting resistor on the CH341A > > > board, and some of the CH341A ICs have no label, which indicates a > > > potential "back ally" fab (i.e. counterfeit) that is common with low end > > > Chinese electronics. Point is, you'd be driving you motherboard with a > > > potentially out of spec, using an unknown IC at the wrong voltage, > > > without current protection. This is not necessarily safe for your Mobo, > > > but it might work for you. > > > There is a mod to turn your programmer into a 3.3V device, but it seems > > > the mod doesn't work on newer programmers that don't have labels on the > > > chip. It didn't work for me, and internets reports that it didn't work > > > for others. I used a Raspberry Pi instead : > > > https://tomvanveen.eu/flashing-bios-chip-raspberry-pi/ The trick for the > > > RaPi was the arg "spispeed=512". I connected the Pamona clip included in > > > the CH341A Kit to the RaPi using fly wires, so my CH341A wasn't > > > completely useless, and was actually cheaper than the clip alone. China. > > > > If you look, my comment related to voltages AND chip id. > > On the voltage front, my experience differs from what you have heard. I > > haven't found controllers that deliver 5V when flashing, and I've > > tested some. > > There's some debate about whether the specs include an internal LDO or > > not, depending on your knowledge of Chinese and reading of the spec. > > All I can say is that I've used numerous cheap (and expensive) > > programmers without mishap. (And, to repeat myself, nemeth reports the > > same, as did Cornelius who provided the first schematic.) > > So let's be clear - you are buying a cheap chip of unknown provenance. > > That's the real risk here. > > Some (which? some black ones? Which black ones?) controllers may have > > a voltage issue, which may not even be an issue. > > The second question is the need to identify the chip - with an x230 (and > > most other lenovos I have worked on), you can read and write using any > > of the proferred chip ids, with identical results - Any one should be > > able to confirm this for themselves. > > Pick up a motherboard from ebay, and start practise. gets you experience > > at minimal risk and cost. > > > > You received this message because you are subscribed to the Google Groups > > "qubes-users" group. > >
Re: [qubes-users] Why not make it possible to use a custom key combination for changing the keyboard layout when installing Qubes OS ?
On Tue, Mar 10, 2020 at 11:58:21AM -0700, 'M' via qubes-users wrote: torsdag den 5. marts 2020 kl. 14.19.59 UTC+1 skrev tetra...@danwin1210.me: On Thu, Mar 05, 2020 at 03:33:54AM -0800, A wrote: >When installing Qubes OS, it’s possible to choose between some predetermined key combinations for changing the keyboard layout. > >Why not also make it possible for the user to make his or her own key >combination for changing the keyboard layout when installing Qubes OS ? I still haven't figured out how to change the key combination once the install is complete... You can't. It's made as so as a security measure. This makes no sense to me. The Qubes security model is that dom0 is assumed clean, and if dom0 is compromised the whole machine is compromised. How would making it impossible to change the key combination from dom0 improve security? -- 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/20200313184016.GA2050%40danwin1210.me.
Re: [qubes-users] Q: Using VMs to test networking vcode
On Fri, Mar 13, 2020 at 08:40:25AM +0100, Ulrich Windl wrote: > Hi! > > I have some experince with Xen and PVMs and networking at work. > When I read about qubes I thought it could be great to create some VMs to > test some networking code at home (where I only have one computer). > However as it turned out Xen networking in Qubes is completely different from > what I knew (e.g. I see no bridge devices where the VM NICS are connected to). > So I wonder: Is is (easily) possible to create a few VMs in Qubes OS that see > each other on some virtual IP network? > > Regards, > Ulrich > > Read this? https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200313150857.GB15043%40thirdeyesecurity.org.
Re: [qubes-users] Re: EE-PROM of an Lenovo X230
On Fri, Mar 13, 2020 at 03:35:05AM +, Mike Karasoff wrote: > As far as the voltages go, I'm not sure I understand unman's "garbage" > comment. The PROMs on your X-230 are 3.3V logic, but the CH341A programmer > usually has 5V logic. I've heard that some CH341A are 3.3V, but that seems > more because there are several different places in China producing the same > board and so its kind of random. > > I think you can use 5V logic to program these ICs, but you are doing so at > your own risk. There is no current limiting resistor on the CH341A board, > and some of the CH341A ICs have no label, which indicates a potential "back > ally" fab (i.e. counterfeit) that is common with low end Chinese electronics. > Point is, you'd be driving you motherboard with a potentially out of spec, > using an unknown IC at the wrong voltage, without current protection. This > is not necessarily safe for your Mobo, but it *might* work for you. > > There is a mod to turn your programmer into a 3.3V device, but it seems the > mod doesn't work on newer programmers that don't have labels on the chip. It > didn't work for me, and internets reports that it didn't work for others. I > used a Raspberry Pi instead : > https://tomvanveen.eu/flashing-bios-chip-raspberry-pi/ The trick for the > RaPi was the arg "spispeed=512". I connected the Pamona clip included in the > CH341A Kit to the RaPi using fly wires, so my CH341A wasn't completely > useless, and was actually cheaper than the clip alone. China. > If you look, my comment related to voltages AND chip id. On the voltage front, my experience differs from what you have heard. I haven't found controllers that deliver 5V when flashing, and I've tested some. There's some debate about whether the specs include an internal LDO or not, depending on your knowledge of Chinese and reading of the spec. All I can say is that I've used numerous cheap (and expensive) programmers without mishap. (And, to repeat myself, nemeth reports the same, as did Cornelius who provided the first schematic.) So let's be clear - you are buying a cheap chip of unknown provenance. That's the real risk here. Some (which? some black ones? Which black ones?) controllers may have a voltage issue, which may not even be an issue. The second question is the need to identify the chip - with an x230 (and most other lenovos I have worked on), you can read and write using any of the proferred chip ids, with identical results - Any one should be able to confirm this for themselves. Pick up a motherboard from ebay, and start practise. gets you experience at minimal risk and cost. -- 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/20200313150039.GA15043%40thirdeyesecurity.org.
[qubes-users] Update issue of whonix-15 and debian-10 templates
Hi, all, I am trying to update whonix-ws-15 and whonix-gw-15, but it fails to do anything. All fedora-30 templates, and dom0, are updating just fine. In my Qubes Manager I see an update arrow for both whonix templates gw and ws. Using Qubes Updater it starts disp-mgmt-dvm and than starts the whonix-xx-15 just fine. In my Nyx I but don't see any traffic running. The update seems to finish with a green tick but the green update arrow in the Qubes Manager remains and requires an update. In the Details tab of the Qubes Updater I get only this, I dont see any details as before (or as when updating Fedora-30 template): Updating whonix-gw-15 whonix-gw-15: Once I try to update the whonix templates directly with sudo apt update, I get "14 packages can be upgraded. Run 'apt list --upgradable' to see them." I get a bit similar results for my debian-10 template. After I execute the sudo apt update in debian-10 template, it doesn't show any traffic in the Nyx, it ends with the green tick in the Qubes Updater and it tells me that "1 package can be upgraded. Run 'apt list --upgradable' to see it." The issue started after the latest dom0 update. I tried to even onionize the templates update process but it remains the same. How should I proceed? Is the qubes updater broken for Debian based templates? Should I run sudo apt update && sudo apt dist-upgrade in the related qubes templates? Thank you for help! -- 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/4c8a8518-5830-09b5-c676-997bdf38482f%40mailbox.org.
[qubes-users] CentOS Template: Run with native kernel
Dear all, I tried to run the CentOS template with its own kernel (qvm-prefs vm kernel '') in HVM mode, but so far it refuses to start and I always get the following error: [ 11.073799] blkfront: xvdc: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; [ 11.200124] dracut-pre-trigger[316]: sfdisk: /dev/xvdc: unrecognized partition table type [ 11.201569] dracut-pre-trigger[316]: sfdisk: No partitions found [ 11.202927] dracut-pre-trigger[316]: sfdisk: unrecognized input: type=82,start=2048,size=2097152 [ 11.207577] dracut: FATAL: Qubes: failed to setup partitions on volatile device [ 11.232758] dracut: Refusing to continue Did anyone have the same issue? Thanks & Best Regards David -- 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/c308a146-ee1e-934b-e25b-cae3d6528982%40hackingthe.net. smime.p7s Description: S/MIME Cryptographic Signature
[qubes-users] Re: I need help with IOMMU issues
there's also a IOMMU bios option that needs to be enabled. "should" is something you and bios makers seem to differ on, and I think they win. ;) -- 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/de63d116-1060-4321-923f-6e2a9107b03d%40googlegroups.com.
Re: [qubes-users] I need help with IOMMU issues
On 3/13/20 6:57 AM, missioncha...@secmail.pro wrote: Since Reddit is dead and I found this place I thought I'd try again. I am currently trying to install Qubes OS on a consumer grade Lenovo laptop that was gifted to me recently. The laptop contains a Ryzen 7 2700u APU, and I am certain that everything is in place for IOMMU support, which should fall under the SVM Technology setting in the BIOS. The issue arrives when the system tries to enable AMD-Vi, this is the output of xl dmesg: (XEN) Initing memory sharing. (XEN) IVHD Error: Invalid IO-APIC 0x21 (XEN) AMD-VI: Error initialization (XEN) I/O virtualization disabled (XEN) ENABLING IO-APIC IRQs A simple search on Google for "Ryzen 7 2700u and Qubes" yields a list of posts. Mike. -- 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/ca8d4b55-86a6-c50a-81b2-474eb49cd1a4%40keehan.net.
[qubes-users] Q: Using VMs to test networking vcode
Hi! I have some experince with Xen and PVMs and networking at work. When I read about qubes I thought it could be great to create some VMs to test some networking code at home (where I only have one computer). However as it turned out Xen networking in Qubes is completely different from what I knew (e.g. I see no bridge devices where the VM NICS are connected to). So I wonder: Is is (easily) possible to create a few VMs in Qubes OS that see each other on some virtual IP network? Regards, Ulrich -- 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/5E6B38E902A100037C45%40gwsmtp.uni-regensburg.de.
[qubes-users] I need help with IOMMU issues
Since Reddit is dead and I found this place I thought I'd try again. I am currently trying to install Qubes OS on a consumer grade Lenovo laptop that was gifted to me recently. The laptop contains a Ryzen 7 2700u APU, and I am certain that everything is in place for IOMMU support, which should fall under the SVM Technology setting in the BIOS. The issue arrives when the system tries to enable AMD-Vi, this is the output of xl dmesg: (XEN) Initing memory sharing. (XEN) IVHD Error: Invalid IO-APIC 0x21 (XEN) AMD-VI: Error initialization (XEN) I/O virtualization disabled (XEN) ENABLING IO-APIC IRQs I have already tried a workaround found online for Linux by adding ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 to the command line, but this doesn't fix the issue, and xl dmesg shows this: (XEN) Initing memory sharing. (XEN) IVHD Error: Invalid IO-APIC 0x22 (XEN) AMD-VI: Error initialization (XEN) I/O virtualization disabled (XEN) ENABLING IO-APIC IRQs The error has changed the second line from 0x21 to 0x22 and I lack the expertise to gather information from the results. And this is where I need help, I don't know exactly what to search that hasn't already lead me to my other workaround. -- 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/bee1718d4cbbf37b29483e1c45693d29.squirrel%40giyzk7o6dcunb2ry.onion.
