[qubes-users] Re: Qubes on the Surface Laptop 3 15" Business Edition (Intel 10th Gen)

[dylanger]

Could this be related to 10th gen support not being present in Qube's 
Stable 4.x kernel included with the installation media?

On Wednesday, December 11, 2019 at 5:21:16 PM UTC+11, 
dyla...@onedefence.com wrote:
>
> Fedora 31 Workstation boots perfectly with 
> modprobe.blacklist=intel_lpss_pci added to CMDLINE
>
> If Fedora Boots, it has to be something I can add.
>
> On Wednesday, December 11, 2019 at 5:02:59 PM UTC+11, 
> dyla...@onedefence.com wrote:
>>
>> Hey Guys,
>>
>> I've recently purchased the MS Surface Laptop 3 15" Business Edition.
>>
>> I've set ANACONDA up to be verbose (Commenting out noexitboot & mapbs)
>>
>> I get the following error:
>> IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a 
>> report. Then try booting with the 'noapic' option
>>
>> However upon adding apic_verbosity=debug I don't seem to get any logging 
>> out of it.
>>
>> When adding noapic, I can see it bring dom0 up, then the device appears 
>> to reboot then hang at the UEFI Logo Screen, I'm sure this has something to 
>> do with noapic disabling ACPI (And thererfore the screen/iGPU?)
>>
>> It should be noted this Laptop is running the Intel 10th Generation 
>> i7-1065G7.
>>
>> I've tried disabling UEFI RS (Runtime Services) still seem to get the 
>> same result.
>>
>> Any help would be greatly appricated, I understood I'd need to compile a 
>> dom0 Kernel with the Surface ACPI Patches, however I expected it to at 
>> least let me install, it seems I may need to compile these ACPI Patches 
>> into the Installer ISO in order to boot ANACONDA.
>>
>> For Reference ACPI Patches: 
>> https://github.com/archseer/arch-linux-surface
>>
>> I've also tried adding `modprobe.blacklist=intel_lpss_pci` to CMDLINE.
>>
>> Cheers!
>>
>

-- 
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/5a775444-af21-4f8d-bd25-ef0dc5b14165%40googlegroups.com.

[qubes-users] Re: Qubes on the Surface Laptop 3 15" Business Edition (Intel 10th Gen)

[dylanger]

Fedora 31 Workstation boots perfectly with 
modprobe.blacklist=intel_lpss_pci added to CMDLINE

If Fedora Boots, it has to be something I can add.

On Wednesday, December 11, 2019 at 5:02:59 PM UTC+11, 
dyla...@onedefence.com wrote:
>
> Hey Guys,
>
> I've recently purchased the MS Surface Laptop 3 15" Business Edition.
>
> I've set ANACONDA up to be verbose (Commenting out noexitboot & mapbs)
>
> I get the following error:
> IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a 
> report. Then try booting with the 'noapic' option
>
> However upon adding apic_verbosity=debug I don't seem to get any logging 
> out of it.
>
> When adding noapic, I can see it bring dom0 up, then the device appears to 
> reboot then hang at the UEFI Logo Screen, I'm sure this has something to do 
> with noapic disabling ACPI (And thererfore the screen/iGPU?)
>
> It should be noted this Laptop is running the Intel 10th Generation 
> i7-1065G7.
>
> I've tried disabling UEFI RS (Runtime Services) still seem to get the same 
> result.
>
> Any help would be greatly appricated, I understood I'd need to compile a 
> dom0 Kernel with the Surface ACPI Patches, however I expected it to at 
> least let me install, it seems I may need to compile these ACPI Patches 
> into the Installer ISO in order to boot ANACONDA.
>
> For Reference ACPI Patches: https://github.com/archseer/arch-linux-surface
>
> I've also tried adding `modprobe.blacklist=intel_lpss_pci` to CMDLINE.
>
> Cheers!
>

-- 
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/3f88cb4a-f5f3-45f8-a97f-a5044e9dc827%40googlegroups.com.

[qubes-users] X Startup Failed

[Master Node]

Hi I am in some big time need of help here, I have been playing with qubes for 
a few years now but recently put it onto my alienware laptop, this laptop had 2 
gpus in it, unfortunately I put it on my lap for 15 minutes and fired the one 
gpu, I had both gpus taken out by a professional as to limit the risk of 
breaking anything, qubes worked perfect on this laptop in legacy mode before 
hand everything besides wifi card worked.

Now I am doing a reinstall of qubes and getting everything to work untill it 
hits the X startup failed aborting install. I have tired to add this work 
around to the boot loader at grub screen with tab 

'nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off'

I add it at the end of the text not sure if that matters but it does not do 
anything different for me, everything in BIOS has been double checked and 
played around with for hours, I would love to run this laptop with qubes and I 
dont care how much it takes to make this happen so if you know some serious 
stuff about qubes and would like to help or get paid to help me here there 
please reach out to me and we can go from there.

-- 
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/81e23e20-121a-4772-892f-247e658d00d2%40googlegroups.com.

Re: [qubes-users] unsupported hardware detected with the installation of qubes 4.0.1, and 4.0.2-rc2

[Steve Coleman]

On 2019-12-10 10:26, rickey wrote:

Good morning Everyone,
I have installed previously Qubes 3.2.1 on a Dell small form factor 
desktop pc, and lenovo x120e, and I was able to use them.
When I tried to install the Qubes versions mentioned above on the same 
hardware, it is showing the message into the attached screenshot. If I 
proceed despite it, I cannot finish the installation of the thinkpad, 
and Dell's doesn't allow Tor to start.


You have two separate problems here apparently, and not really enough 
detail for us to go by to help much.


- For the Lenovo x120e I would start by checking your BIOS version to 
see if you are up to date. You can find that information here:


https://pcsupport.lenovo.com/si/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x120e/downloads/driver-list/component?name=BIOS%2FUEFI

If you are not up to date then download the bootable CD version, reflash 
your bios to the latest and try again. You also may have to play with 
the UEFI settings to be able to continue the installation, if its 
rebooting that isn't working. You have not told us what error you are 
getting or where in the install process it stops working. There are no 
x120e's in the HCL list yet but somebody might have some experience with 
something similar.



- For the Dell, we don't even know what system model you have yet. Are 
you talking about the whonix system for Tor? Have the whonix service 
VM's been started?  What VM logs are available? We need more information 
in order to be able to help.


Note: Since you have two separate system problems I would suggest 
splitting this email thread into two separate threads so the people 
familiar with each kind of system can focus better on that particular 
issue. We will try to help if we can.





--
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/4add3ef3-3249-4206-8f0e-8bc292071314%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e6f1682d-55a3-fd73-69a6-f14f1db3091a%40jhuapl.edu.

[qubes-users] HCL - Dell XPS 13 9365 (2-in-1)

['Banana Hawaii' via qubes-users]

HCL Submission:

Install required tweaking BIOS settings:
- change SATA Operation from "RAID On" to "AHCI"
- disable secure boot
- disable Intel SpeedStep
(based on 
https://groups.google.com/forum/#!msg/qubes-users/lyE5iUQ-TXw/p8LJMI15CQAJ )

Boot is slow (4min) and VM start is also slow (90s). Cause? 
RAM/CPU/settings/...? I don't know how to troubleshoot. I will try if given 
instructions. In any case, still very workable with some patience.

All else A-OK. Trackpad, wifi and even touchscreen worked without tweaking 
after successful install.

-- 
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/OYm6k2BwAfO4kUeR_DwqK26F6Eh5axdlrIUKN9FnJbZxol0v62l0DV7VY1hY0poYwWPcnCwjlx4ukRmP4iII_9y2F7s4D9ioySC6JRMazVg%3D%40protonmail.com.


Qubes-HCL-Dell_Inc_-XPS_13_9365-20191210.yml
Description: application/yaml

Re: [qubes-users] Has anybody gotten increased scrutiny at an international checkpoint because of having qubes installed?

[duc01k]

billol...@gmail.com:
> 
> 
>>
>> Is there actually anyone working on the hidden OS option for the 
>> linux? Would be very much appreciated. 
>>
>>
> 
> Hah. I actually did something like this by accident the first time I 
> installed Qubes.  I had KDE neon installed, and I couldn't get it to dual 
> boot correctly.  It turned out that the order in which I installed the OSes 
> made a difference.  
> 
> In any case, my laptop has two drives -- a 256G SSD and a 1 TB conventional 
> hard drive.  I got frustrated trying to get it to work, so simply installed 
> one OS on the SSD and one on the hard drive, each with it's own MBR, UEFI 
> setup and grub.  So, if you turned the machine on, it defaulted to booting 
> into KDE neon, and booted from the hard drive.  If I wanted to boot from 
> Qubes, I had to frantically hit the escape key and choose to boot from the 
> MBR on the SSD in the BIOS/startup menu.
> 
> I thought it was kind of cool, but decided I was wasting disk space so 
> deleted everything when rc2 came out and just use Qubes now -- though I 
> wish KDE worked better...
> 
> billo
> 

If you're travelling to the US, then there's /some/ good news:

https://www.eff.org/deeplinks/2019/11/federal-judge-issues-historic-opinion-digital-privacy-border

-- 
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/8a8dd6e6-2e95-34d6-5743-e4aaa958d79b%40disroot.org.

Re: [qubes-users] sys-net keeps dying

[tetrahedra via qubes-users]

On Thu, Dec 05, 2019 at 03:05:42PM +, Claudia wrote:

I am wondering if it would make sense to re-create sys-net from scratch.
Could it be that this is something from fedora-29 that is not working
well with fedora-30?


Did you keep the fedora 29 template installed? If so, I think you 
could just change the template back to 29 for sys-net and see if that 
fixes it. If not, perhaps you could downgrade it, or try explicitly 
installing the fedora 29 template.


No, I just deleted the fedora-29 template recently, not realising it
might be the root of the issue :/




There doesn't seem to be much documentation on how to do this. One post
suggests you just create a new VM and call it sys-net:
https://www.reddit.com/r/Qubes/comments/amvkz3/how_to_create_net_and_firewall_again_with_default/efpl5i2/


However that doesn't seem right, isn't something extra needed to get
the NetworkManager wifi menu widget set up?



Not that I know of. As far as I know, system tray icons are just like 
a regular window, in that any VM can create them without any special 
configuration, and they're colored according to the VM. So when you 
start NetworkManager it should just appear in the tray.


I don't know anything about that guide, but it may be worth trying. 
You can create a new VM called sys-net2 or whatever so you don't have 
to overwrite your existing sys-net. Then just create a temporary AppVM 
with sys-net2 as its NetVM to test it.


I did create sys-net2 and NetworkManager started automatically (no
configuration needed!) and connected to wifi.

However, when I try to configure sys-firewall to use sys-net2 instead of
sys-net for networking, I get the error:
ERROR Basic tab: Failed to access 'netvm' property

I have sys-net2 set up in HVM mode, with "provides network" checked in
the Advanced tab, the NICs configured in Devices, etc.

Other than that the only option I can think of is to debug your 
current sys-net and fix whatever is causing it to crash. Check 
/var/log/qubes, /var/log/xen, and `xl dmesg`.


I did find some relevant log entries, but I'm not sure how to interpret
them. I will post to the relevant Github issue about this:
https://github.com/QubesOS/qubes-issues/issues/4658

--
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/20191210081042.GA4088%40danwin1210.me.