[qubes-users] FATAL PAGE FAULT [error_code=0002]
Hi everybody i’m trying to install your OS on my device but when i try to start your .iso (that i was installed on a pendrive using rufus and FAT32 system and DD option) from my BIOS (through press f12 becausei have a dell), i have a fatal error. I think that the official error message is the following: *** Panic on CPU 0: FATAL PAGE FAULT [error_code=0002] Faulting linear address: *** Can somebody help me? I’m not a veteran user… -- 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/fab7a150-2b07-42b3-a958-5e14f688c7afn%40googlegroups.com.
[qubes-users] Re: Getting wifi working on a new machine in qubes 4.0.3 and 4.0.4-rc1
PS I just checked lspci from terminal in sys-net - it is definitely showing the device, which it lists as follows 00.08.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) -- 9831*2^1441403+1 is prime, >400k digits -- 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/CAK3jUKqnDsjOZAARt3swF-iK2BYDSWJoD_HmP%2BkiWKaotuQFKA%40mail.gmail.com.
[qubes-users] Getting wifi working on a new machine in qubes 4.0.3 and 4.0.4-rc1
Hi, I am having difficulty getting my wifi working, and have tried in both r 4.0.3 and 4.0.4-rc1. I also tried in the live disks of Fedora versions 25 and 32. It does not work in 25, but is fine in 32. I checked the devices of sys-net, and the Intel network controllwer is being passed across OK. It must be the right device because everything else on the motherboard is AMD ;) Am I confused or what? I had imagined that if the device is being passed through to sys-net, then the drivers would have to be in sys-net? And I also thought that if the standard Fedora 32 contained the drivers for this wifi device then the qubes template would? Am I making too many assumptions there? Any ideas what I need to try to do next to get this working? Warmly R~~ -- 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/CAK3jUKqMy2JO25JFvTuaYHCB4cij2h%3D-zm_%3DaZdKaxF%3D5Q5YZw%40mail.gmail.com.
Re: [qubes-users] Qubes Awesome WM - Gaps not working
On 11/25/20 12:15 PM, Hayden Llowarch wrote: Hi All, Has anyone got gaps work on the awesome window manager? I have tried beautiful.useless_gaps = 5 In the rc.lua file And Themes.useless_gaps = 5 In the themes.lua file Everything I’ve read says this should work, but its not? It's probably an awesome 4 feature [1]. The dom0 version is still 3.5. [1] https://github.com/awesomeWM/awesome/pull/279 -- 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/953f34dd-3c37-8afb-3ed5-451bac8ef06e%40hackingthe.net. smime.p7s Description: S/MIME Cryptographic Signature
[qubes-users] installing non-free graphics drivers in dom0 (?)
I need to use xrandr to make the edges of my Qubes screen visible in the TV I am using as an HDMI monitor, and this works fine on Knoppix and LinuxMint. I have not been able to get xrandr to set --output at all on Qubes 4, Fedora 25, and Fedora 32. Research on other forums shows this is likely because Knoppix and LinuxMint both include nonfree graphics drivers, and apparently Fedora does not (at least not by default) I do recall seeing a note some time ago to the effect that AMDGPU can be problematic but I had hoped that that was no longer so much the case. On a Debian like system the command would be apt install firmware-linux-nonfree What would the equivalent be on dom0? Providing that the firmware from the manufacturer is not malicious, are there any other risks that I should be aware of? Or is this something that is not possible to do and I should therefore buy a more suitable monitor? The graphics is provided by a very recent AMD Radeon enabled combined CPU/GPU, but the drivers included in the late 2019 Knoppix work so they clearly do not need to any more recent than that. Background: I am using an early flat-panel TV as a monitor. Like many TV's of its time when used as a monitor the edges of the picture are hidden. Sufficient of the edges are missing that a top or bottom bar (top like on qubes, bottom like on Mint) are not very usable. I have to guess where the button I want is. The commands I use to fix the picture size use xrandr and work on the Debian-based distros but not on Fedora, including the most recent qubes versions. Glad for any tips R~~ -- 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/CAK3jUKph4Muj2BCRhKn_X6SBZAqUdGE3Yac2ECf6A8W5a8V_yw%40mail.gmail.com.
Re: [qubes-users] overscan issue & using xrandr in dom0
On 11/22/20 4:20 PM, River~~ wrote: > I have tried > > HDMI-A-0 (as that is what it is on LinuxMint) > HDMI > HDMI0 > HDMI-0 > HDMI-0-0 > HDMI1 > HDMI-1 > HDMI-1-0 > HDMI-1-1 What says 'xrandr --listmonitors'? -- 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/b6c21ec1-0fce-cc91-6214-2a8e60b72e41%40riseup.net. OpenPGP_0x141310D8E3ED08A5.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] Are "smart" monitors/TVs a security issue?
Hi all In the days of CRT monitors one way the security of a computer system could be compromised non-intrusively (ie without amending the installed code) was by picking up the radio-frequency leakage from the tube in the monitor. This could only be done from near by, but where possible it enabled the spy to see what was on the screen -- almost everything that you typed (aprt from passwords that were blanked or starred out). This was a remote form of shoulder surfing, where someone looks over your shoulder in an environent like an internet cafe. Nowadays we do not have to worry about CRT monitors. But TVs are increasingly delivered with their own internet connection, making it easy to watch You-Tube (etc) without needing a separate computer or phone. Clearly there is a computer inside which can be hacked, and if so a remote shoulder surfing attack would be very possible. Is the same true of monitors and of TVs that do not have an apparent internet link? The digital tech to draw a picture from the input is unlikely to be done by traditional electronics, but being all digital is likely done by a miniporcessor of some kind in all digital displays. To put my question in the most provocative way on this forum: if there much point securing the OS when the monitor might be an easier target for those out to (umm) monitor our reading and our keystrokes? This thught has only just come to me, and I wonder if there is already some available mitigation? Any ideas? Or am I being overly cautious? R~~ Any ideas? -- 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/CAK3jUKoDK8kX2jhx3J-m%3D-%3DrRdVxpX7uaJCa5emwpXdSm-CWxg%40mail.gmail.com.
[qubes-users] Re: overscan issue & using xrandr in dom0
On 22/11/2020, River~~ wrote: > hi all > > I have recently migrated my Qubes to an new desktop computer from my > laptop. Because I have not yet bought a suitable monitor I am using a > TV as an HDMI monitor, and am having the common difficulty that the > picture is bigger than the display area. This is called overscan. > > The HDMI TV is old enough that it does not have a setting for use with > PCs, nor a "normal" or "just scan" option. That means I need to adjust > the issue from the computer end. > > On LinuxMint I can sort this using xrandr, and I had imagined this > would be easy on Qubes, but no such luck :( > > The command that works on Mint fails on Qubes, because I have been > unable to guess what the --output name is for my display, and the > xrandr -properties command simply refers to the plugged in monitor as > 'default', or as 'Screen 0', but neither of those works as a name. > > I have tried > > HDMI-A-0 (as that is what it is on LinuxMint) > HDMI > HDMI0 > HDMI-0 > HDMI-0-0 > HDMI1 > HDMI-1 > HDMI-1-0 > HDMI-1-1 > > and a similar list (grasping at straws here) > > VGA > VGA0 > VGA-0 > ...etc > > The computer has an AMD CPU with a built in GPU, and on LinuxMint is > was easy to ask xrandr to list the three display connectors. I cannot > find the relevant command on dom0. I can't find any docs on the Fedora > site, though I can't say I really know my way around that. > > Is it Qubes, somehow hiding the display connector names? Is it that I > just need to invoke some different magic command in dom0 to get xrandr > to divulge the list of relevant names? > > Or is it that dom0 is already running wayland and I need a different > command entirely? > > I had assumed that it would be straightforward, as I understand that > Fedora in general has better graphics hardware compatibility than > Mint/Ubuntu/Debian (though I may be out of date on that). > > I am not sure what other info I can give to help you to help me. > > Should I post the output from lspci? and if so, as produced on > LinuxMint or as produced from Qubes? > > Be grateful for any suggestions. > > Final comments: > > If I can't fix this then Qubes is not really usable till I can afford > a newer monitor -- but that involves spending the money I had > earmarked to upgrade the new machine's memory to 32Gb from 8Gb. > > I am glad I still have the laptop installation, which works but it is > a bit laborious as it only has 8Gb memory and is not upgradeable. > > -- > 9831*2^1441403+1 is prime, >400k digits > -- 9831*2^1441403+1 is prime, >400k digits -- 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/CAK3jUKpxxhA3YjsBm8aFecg4a26uoCKnqtnJcwYCTOC1vgHBJw%40mail.gmail.com.
[qubes-users] Re: HCA reports - some advice please
On 22/11/2020, River~~ wrote: > hi I have got a new computer working, and it is a model new to Qubes > not just. (Guess who got it cheap on an early bird reduction on > kickstarter then :) > > So, I am going to send in the HCA report. I have produced the .yml > file. It contains some FIXME items. I am unclear: is it up to e to fix > them, or are they a note to whoever processes the report before > posting to the HCA page? > > If I have to edit them, what do I use for the "short" items? Am I > reasonably free to abbreviate? > > I am thinking of including the cpio files, but do not want to share a > serial number that they contain. WOuld those files be useful to others > if I edited them so that the serial number reads "Redacted"? > > Finally, the manufacturer's name shown in the .yml is different from > the name they used on kickstarter. Would it help, or would it cause > confusion, if I added at the end of their name "t/a MinisForum"? > > WArmly > R~~ > -- 9831*2^1441403+1 is prime, >400k digits -- 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/CAK3jUKqWAU%3D%2B0qVK%2BzEpM7zB17XzuYCAFkttqmB%2B9hZW1sg8cg%40mail.gmail.com.
Re: [qubes-users] HCA reports - some advice please
On 11/23/20 1:42 PM, Steve Coleman wrote: On Mon, Nov 23, 2020 at 2:31 PM Andrew David Wong wrote: On 11/23/20 10:06 AM, Steve Coleman wrote: On Mon, Nov 23, 2020 at 9:33 AM Andrew David Wong wrote: I have a question about the HCL process and page display that I have been wondering about. I was for the longest time copying and pasting the HCL web page into a spreadsheet just so I could sort and delete out all the old information, as I was looking to replace my desktop system with something more up to date. I can't tell you how many times in the last three years I copied the HCL to this spreadsheet, and when my old desktop finally died I had to give up hope and just bought a new system sight unseen that was not on the list and I just hoped for the best. Fortunately, it worked out Ok. As it is right now it is difficult and getting increasingly harder to find just the latest hardware on the list as it seems that by the time something appears on the list it is no longer even available for purchase. Remember that these are almost all reports voluntarily submitted by users. If it's mostly old hardware, that's because few people with new hardware are submitting reports for that hardware. Agreed. But it is certainly possible to make this more of a discussion on how to give back to the community. The Qubes patriotic thing to do is to submit your successes so others can follow without so much fear and hesitation. We can't force anyone to submit reports, and we usually can't get new hardware to generate reports on ourselves. No, but a well-placed note/request at the end of the Qubes install process could go a long way to actually encourage them to submit the report to help others. The "how you can help" could also suggest this as a way to give back which is easy even for novices who were just introduced to Qubes. Make it a badge of honor. In fact, one could encourage people with questions to include a report link/ID where the fundamentals of their basic machine configuration would be available online for the experts to better understand the problem. Not everyone would necessarily want to give their anonymity away, but for some questions, this link could provide some valuable information about the hardware that would be easy to share. Good ideas! I've opened an issue for this: https://github.com/QubesOS/qubes-issues/issues/6231 I've already implemented the documentation suggestions (as well as some similar ones inspired by your suggestions). For details, see the issue. Though, to be fair, the reports from the mailing list haven't been added in a while, so that might also be part of it. Very true, unfortunately. I submitted my "Dell XPS 8930" but it has not shown up yet. With 8 cores and 64GB of memory, it is already out of production but it is still available through other retailers. Somebody who is looking for a new beefy desktop may not see this on the HCL until it is no longer available anywhere. That is the same boat I was in when my desktop up and died and I had no choice but to draw straws and pick one almost at random. Yes, there were other *very old* XPS's on the HCL and some did *not* work properly, but based on the hardware in this one I figured it might just work. Unfortunately, this only has a "firmware TPM" that is disabled in BIOS when using the legacy boot settings and there is no header on the motherboard to even add a physical TPM. I may just dabble with the idea of a qubes auditable software-based vTPM (qTPM) and see if I can find a way to make something work for the contributor's packages. Not sure about that yet, but it's an idea that might even allow for locking down the boot partition by making it read-only until after a successful boot/login. Evil maids can't change what they can't edit. We've decided to recruit an additional HCL maintainer to get reports from the mailing list onto the website more quickly. I've sent a message to these lists about it. However, there are LOTS of machines that you could only find on eBay and many/most lack sufficient memory, BIOS, or current chipset support for the current Qubes R4.x system being developed. Old systems on the HCL are seemingly never updated, so you can't tell which ones are still working and which ones have retired years ago. There are many items on that list even in the wrong categories (e.g. DIY System boards in the Desktop section when there is a separate section just for those) and I see no defined process by which to help change that. My question is this: What would it take to get a set of simple filter options on that HCL webpage? This open issue is very similar to what you're asking: https://github.com/QubesOS/qubes-issues/issues/3795 I've just opened two PRs (linked to this issue) that make the HCL tables sortable. However, some rows break on sorting. Please see the issue comments for more details and an image showing exactly how it breaks. If you can help with this, please
[qubes-users] Seeking an additional HCL maintainer
Dear Qubes Community, As many of you know, the Hardware Compatibility List (HCL) [1] is an important resource for users when deciding on which hardware to get for Qubes. Currently, our system for adding new entries to this list is basically as follows: Users voluntarily generate HCL reports [2], then send them to the qubes-users mailing list. Our HCL maintainer then periodically collects these reports from qubes-users, performs any necessary cleanup and processing, then submits them in a PR to the HCL repo [3]. Users are also free to submit their reports in PRs directly to the HCL repo, and we're always looking for ways to improve this system and all aspects of the HCL. Our current HCL maintainer is Chris (tasket), but the project could benefit from an additional HCL maintainer to help out and share the load. This would allow us to get reports from the mailing list onto the website more quickly and perhaps help make other improvements to the HCL. Chris can provide further details about what's involved in this role. If you'd like to volunteer for this role, please let us know by replying to this thread or directly to me. Thank you! [1] https://www.qubes-os.org/hcl/ [2] https://www.qubes-os.org/doc/hcl/#generating-and-submitting-new-reports [3] https://github.com/QubesOS/qubes-hcl -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -- 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/cc28adcf-885c-5bb9-f760-c062724d9cd4%40qubes-os.org. OpenPGP_0xBC211FCEE9C54C53.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] Qubes Awesome WM - Gaps not working
Hi All, Has anyone got gaps work on the awesome window manager? I have tried beautiful.useless_gaps = 5 In the rc.lua file And Themes.useless_gaps = 5 In the themes.lua file Everything I’ve read says this should work, but its not? Thanks H -- 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/03CBBB97-E474-4B7C-895F-3DEFB29BC8D8%40gmail.com.
[qubes-users] HCL - HP Probook 450 G7
To whom it may concern: The HP Probook 450 G7 is not compatible with QubesOS 4.0. Last week I tried to install QubesOS 4.0.3 onto a new HP laptop model Probook 450 G7. It failed in the following ways: 1. The touchpad didn’t work during the install process or after install 2. It ran extremely slow (just dragging the mouse across the screen had obvious lag). I confirmed that VTx and Vtd were enabled in BIOS). 3. After install, it did not detect my wireless card With some work, it may be possible to fix the drivers for the wireless card and the touchpad. And maybe somehow optimize virtualization. But at that point, I gave up and installed xubuntu on this machine which resolved all 3x issues above. Unfortunately, I cannot run `qubes-hcl-report` on this machine, but I do want this entry to be added to the Hardware Compatibility list so that nobody else attempts to purchase this laptop with the hopes to run QubesOS on 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20201125101519.GA14779%40mail.michaelaltfield.net.
