[qubes-users] Re: Deleting a user created template VM, using dom0
There is an open issue discussion concerning incomplete template delation: https://github.com/QubesOS/qubes-issues/issues/5948 Possibly that might help somewhat. -- 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/a8942e74-f08f-4a49-966a-7f84d4c1d9d7o%40googlegroups.com.
Re: [qubes-users] Guide to installing Qubes on System76 Darter Pro
The solution outlined in step 5 above actually works fine -- the inconsistent results were because I'd failed to remove an earlier unsuccessful approach that sometimes interfered with the script. -- 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/d79a2681-073b-42ba-dc75-7401e6f6eac8%40gmail.com.
[qubes-users] Re: HCL - intel NUC10i7FNK
在 2020年7月20日星期一 UTC+8上午8:47:49，Ludovic Bellier写道：
>
> The intel NUC 10 works great with Qubes-OS 4.0 but need some settings,
> see below.
>
..
Thanks for the guidance!
I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0. I
hope I can get answers from you.
I Set legecy mode, security booting off, use USB stick to install OS.
The following warning maseges is displayed when booting.
"WARN anaconda:
/usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
add_option is deprecated and will be removed in pykickstart-3. Use
add_argument instead.
op.add.option("--minlen",type="int")
..
WARN anaconda.stdout:Not asking for VNC because we don't have a network
..
WARN anaconda:X startup failed: Xorg exited with status 1
WARN anaconda.stdout:X startup failed,aborting installation
ERR anaconda.stdout:X startup failed, aboting installation"
Do I miss setting something in bios or do I need to install the OS with DVD?
Thanks a lot!
--
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/a709b456-1db7-4ff3-9fad-ca41213f6787o%40googlegroups.com.
[qubes-users] Android Studio 4.x unusable on Qubes due to qubes windowing system (maybe)
After moving from Android Studio 4.0.1, I noticed that all submenus open like you see in the image, with a little color between them. Looks like Android Studio/Intellij Idea opens them in a different way in this new version, so Qubes treats them differently, maybe considering them as little windows. Because of this, the autocomplete feature (very essential) isn't work. Please see the video of the autocomplete/autoimport (alt enter) not working https://drive.google.com/file/d/1t8fcEGdsDX1v5zEk2fHqRib9eQpeDLg0/view?usp=sharing Anyone knows how to solve this? I cannot downgrade Android Studio My qubes is Qubes 4.0.1 Image of how it opens the submenus now: https://i.stack.imgur.com/spvc7.jpg (this submenu works, but the ones in the video do not) There's an already open issue here: https://github.com/QubesOS/qubes-issues/issues/3982 but nothing about fixing 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/7e577d5f-fa96-43ad-8860-c40343912887n%40googlegroups.com.
Re: [qubes-users] Whonix configuration
E: > Greetings, > > > I had a question about configuring the Whonix network connection. It > has to do with a possible timer associated with an exterior facing IP > address. How can a exiting IP become static. On several occasions, > websites log out a user for changing the IP address. Somehow, it's > associated with a timer. Would that be the network timer at the bottom > of the network tab in qubes settings? No. Tor periodically changes exit nodes for a site if there is no activity. If you must use a site like that and want to remain anonymous, the only solution might be VPN over Tor, but it's easy to shoot yourself in the foot by purchasing VPN access in a way that can be tied back to your identity. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/18ccbf6a-453d-4dd6-3d39-731a963ace9d%40danwin1210.me.
Re: [qubes-users] Re: YouTube Sound & Video
Pmonf: > An update: I found this which appeared to describe my problem: > https://www.qubes-os.org/doc/intel-igfx-troubleshooting/ > > I checked /var/log/Xorg.0.log and found the "reverting to software > rendering" line. I then followed the recommended fix for EFI by adding " > i915.preliminary_hw_support=1" to the xen.cfg file. I then rebooted but the > boot failed. Since the drive was encrypted I could see no way to get back > to change xen.cfg back to the original. So I used a live LM 19.2 stick to > see if I could access the file from it. It did ask for my encrypt password > but would not access the drive. I finally had to re-install the Qubes OS. > No loss, except the time involved. But I can still not watch videos. Good troubleshooting steps. That i915 is a bit dated though, so I suspect you have some other Intel video driver related issue. Further review the Xorg.0.log file prior to the line about software rendering, and see if you can locate a reason for it being unable to use hardware acceleration. There may also be clues in dom0's "sudo journalctl -b" log. PS You should have been able to edit xen.cfg using your method, but without decrypting. For future reference at least, it's located under /boot/efi/EFI/qubes. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/b61c84a9-2a59-f21f-c36e-e5bd9b5cc878%40danwin1210.me.
[qubes-users] VESA for RTX 2070 Super crashes before installation
Hi, I've decided to go on an adventure and attempt to get Qubes OS running with the newer RTX 20XX cards. At this point I have hit a bit of a roadblock and would like to get some input from the kind folks that have attempted this journey as well. The nouveau driver included in 4.0.3 does not detect the RTX 2070 super that I have in my system. Some Qubes OS user (Frederik) seems to have more success with his 2080Ti, but I did notice that he mentioned R4.1. I assume he has built his own version of Qubes OS which likely includes a newer version of nouveau. But I decided, well let's attempt dropping down to good ol' VESA in an attempt to get a bootable system and worry about the drivers later. The X Server for installation will not start, even when dropping down to VESA support. After a bit of debugging, I have narrowed it down to the following error: [ 5697.883] (II) VESA(0): initializing int10 [ 5697.885] (EE) VESA(0): V_BIOS address 0xSOMEHEXADDRESS out of range I forgot which address it was exactly but I will replicate it if it's of importance. A broken VESA kinda has me by suprise here. I'm dropped in an anaconda rescue shell (TTY2) and I am wondering what my possibilities here are. 1. Is it possible to install a newer version of nouveau in this shell and attempt to X with nouveau? 2. Should I just compile the latest Qubes OS? 3. Should I stick in an older GFX card with working VESA support in an attempt to get to a bootable system and install driver then? -- 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/31b5323c-b048-4d3b-bc7e-57537ea4f886o%40googlegroups.com.
Re: [qubes-users] Whonix configuration
On 7/24/20 9:41 PM, 'awokd' via qubes-users wrote: E: Greetings, I had a question about configuring the Whonix network connection. It has to do with a possible timer associated with an exterior facing IP address. How can a exiting IP become static. On several occasions, websites log out a user for changing the IP address. Somehow, it's associated with a timer. Would that be the network timer at the bottom of the network tab in qubes settings? No. Tor periodically changes exit nodes for a site if there is no activity. If you must use a site like that and want to remain anonymous, the only solution might be VPN over Tor, but it's easy to shoot yourself in the foot by purchasing VPN access in a way that can be tied back to your identity. It is not only the purchase that can make your foot hurt, you still connect to your VPN provider with your public IP from your ISP. That can be dangerous also depending on what you want to do and or your threat model. This can be mitigated by connecting to your VPN provider through the TOR network, that way you can arrive at your VPN provider anonymous. Qubes makes this easy to do. So you can keep yourself completely anonymous but you have to follow the right protocols and you have to be very careful not to make mistakes. Qubes does provide you with an environment that makes it easier not to make mistakes but the the buck stops with you. -- 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/6eb63f57-f87d-5c3f-64c6-8960a87eccbb%40ak47.co.za.
Re: [qubes-users] wired problems with 4 screens and 2 graphics boards: ps/2 mouse and kbd lock up, machine still running, but not usable.
ludwig jaffe: > I disabled hyper-threading, and the box feels more stable. > But I am not sure if it was the problem. > > On Tuesday, July 21, 2020 at 1:35:01 PM UTC, ludwig jaffe wrote: >> >> Hi, the machine still crashed, so I need to give it a long memtest >> to see if it has any loose bits, but ECC memory should protect against >> such. >> Other suggestions? >> >> >> >> On Monday, July 20, 2020 at 6:36:24 AM UTC, ludwig jaffe wrote: >>> >>> So thanks for the tip, I have now put videoram min to 36000 and overhead >>> to 0. >>> Lets see if the machine still bugs around. >>> >>> BTW, any thoughts on fighting the ME using qubes, so no more >>> complete disassembly of laptops, de-soldering flash chips, >>> soldering some small circuits to the south bridge and so on. All 4 monitors on the same graphics card is a good idea. You might also try a different DE than XFCE. I'm basing that on some past posts here, so don't have any specific recommendations on ones that better handle multiple displays. Disabling ME is specific to your hardware, and not really Qubes related per se. Only recommendation there is to carefully shop for Qubes compatible hardware that comes with ME already as disabled as possible, or older AMD hardware that doesn't have one. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/e10b89a9-8c5b-197f-72c0-350e664ec101%40danwin1210.me.
Re: [qubes-users] Re: YouTube Sound & Video
Thanks for the help. I don't know what I am looking at but here is the whole ball of wax down to the software rendering line: cat Xorg.0.log [ 159.890] X.Org X Server 1.19.3 Release Date: 2017-03-15 [ 159.890] X Protocol Version 11, Revision 0 [ 159.890] Build Operating System: 4.9.3-200.fc25.x86_64 [ 159.890] Current Operating System: Linux dom0 4.19.128-1.pvops.qubes.x86_64 #1 SMP Sun Jun 28 06:19:18 UTC 2020 x86_64 [ 159.890] Kernel command line: root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-cc9a361d-df73-48c7-bccb-e6f389932480 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb quiet rd.qubes.hide_all_usb plymouth.ignore-serial-consoles [ 159.890] Build Date: 15 March 2017 06:37:12PM [ 159.890] Build ID: xorg-x11-server 1.19.3-1.fc25 [ 159.890] Current version of pixman: 0.34.0 [ 159.890] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 159.890] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 159.890] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 24 15:40:39 2020 [ 159.891] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 159.891] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 159.893] (==) No Layout section. Using the first Screen section. [ 159.893] (==) No screen section available. Using defaults. [ 159.893] (**) |-->Screen "Default Screen Section" (0) [ 159.893] (**) | |-->Monitor "" [ 159.893] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 159.893] (==) Automatically adding devices [ 159.893] (==) Automatically enabling devices [ 159.893] (==) Automatically adding GPU devices [ 159.894] (==) Automatically binding GPU devices [ 159.894] (==) Max clients allowed: 256, resource mask: 0x1f [ 159.894] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [ 159.894] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 159.894] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 159.894] (II) Loader magic: 0x825e00 [ 159.894] (II) Module ABI versions: [ 159.894] X.Org ANSI C Emulation: 0.4 [ 159.894] X.Org Video Driver: 23.0 [ 159.894] X.Org XInput driver : 24.1 [ 159.894] X.Org Server Extension : 10.0 [ 159.895] (++) using VT number 1 [ 159.895] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 159.897] (--) PCI:*(0:0:2:0) 8086:9b41:17aa:5079 rev 2, Mem @ 0xb000/16777216, 0xa000/268435456, I/O @ 0x3000/64, BIOS @ 0x/131072 [ 159.898] (II) LoadModule: "glx" [ 159.898] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 159.911] (II) Module glx: vendor="X.Org Foundation" [ 159.911] compiled for 1.19.3, module version = 1.0.0 [ 159.911] ABI class: X.Org Server Extension, version 10.0 [ 159.911] (==) Matched intel as autoconfigured driver 0 [ 159.911] (==) Matched modesetting as autoconfigured driver 1 [ 159.911] (==) Matched fbdev as autoconfigured driver 2 [ 159.911] (==) Matched vesa as autoconfigured driver 3 [ 159.911] (==) Assigned the driver to the xf86ConfigLayout [ 159.911] (II) LoadModule: "intel" [ 159.911] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 159.914] (II) Module intel: vendor="X.Org Foundation" [ 159.914] compiled for 1.19.3, module version = 2.99.917 [ 159.914] Module class: X.Org Video Driver [ 159.914] ABI class: X.Org Video Driver, version 23.0 [ 159.914] (II) LoadModule: "modesetting" [ 159.914] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 159.915] (II) Module modesetting: vendor="X.Org Foundation" [ 159.915] compiled for 1.19.3, module version = 1.19.3 [ 159.915] Module class: X.Org Video Driver [ 159.915] ABI class: X.Org Video Driver, version 23.0 [ 159.915] (II) LoadModule: "fbdev" [ 159.915] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 159.917] (II) Module fbdev: vendor="X.Org Foundation" [ 159.917] compiled for 1.18.99.901, module version = 0.4.3 [ 159.917] Module class: X.Org Video Driver [ 159.917] ABI class: X.Org Video Driver, version 23.0 [ 159.917] (II) LoadModule: "vesa" [ 159.917] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 159.917] (II) Module vesa: vendor="X.Org Foundation" [ 159.917] compiled for 1.18.99.901, module version = 2.3.2 [ 159.917] Module class: X.Org Video Driver [ 159.917] ABI class: X.Org Video Driver, version 23.0 [ 159.917] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815,
Re: [qubes-users] Re: YouTube Sound & Video
Pmonf: > Thanks for the help. I don't know what I am looking at but here is the > whole ball of wax down to the software rendering line: cat Xorg.0.log > [ 159.890] > X.Org X Server 1.19.3 > Release Date: 2017-03-15 > [ 159.890] X Protocol Version 11, Revision 0 > [ 159.890] Build Operating System: 4.9.3-200.fc25.x86_64 > [ 159.890] Current Operating System: Linux dom0 > 4.19.128-1.pvops.qubes.x86_64 #1 SMP Sun Jun 28 06:19:18 UTC 2020 x86_64 > [ 159.890] Kernel command line: root=/dev/mapper/qubes_dom0-root > rd.luks.uuid=luks-cc9a361d-df73-48c7-bccb-e6f389932480 > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 > rhgb quiet rd.qubes.hide_all_usb plymouth.ignore-serial-consoles > [ 159.890] Build Date: 15 March 2017 06:37:12PM > [ 159.890] Build ID: xorg-x11-server 1.19.3-1.fc25 > [ 159.890] Current version of pixman: 0.34.0 > [ 159.890] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 159.890] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 159.890] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 24 > 15:40:39 2020 > [ 159.891] (==) Using config directory: "/etc/X11/xorg.conf.d" > [ 159.891] (==) Using system config directory "/usr/share/X11/xorg.conf.d" > [ 159.893] (==) No Layout section. Using the first Screen section. > [ 159.893] (==) No screen section available. Using defaults. > [ 159.893] (**) |-->Screen "Default Screen Section" (0) > [ 159.893] (**) | |-->Monitor "" > [ 159.893] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 159.893] (==) Automatically adding devices > [ 159.893] (==) Automatically enabling devices > [ 159.893] (==) Automatically adding GPU devices > [ 159.894] (==) Automatically binding GPU devices > [ 159.894] (==) Max clients allowed: 256, resource mask: 0x1f > [ 159.894] (==) FontPath set to: > catalogue:/etc/X11/fontpath.d, > built-ins > [ 159.894] (==) ModulePath set to "/usr/lib64/xorg/modules" > [ 159.894] (II) The server relies on udev to provide the list of input > devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 159.894] (II) Loader magic: 0x825e00 > [ 159.894] (II) Module ABI versions: > [ 159.894] X.Org ANSI C Emulation: 0.4 > [ 159.894] X.Org Video Driver: 23.0 > [ 159.894] X.Org XInput driver : 24.1 > [ 159.894] X.Org Server Extension : 10.0 > [ 159.895] (++) using VT number 1 > > [ 159.895] (II) systemd-logind: logind integration requires -keeptty and > -keeptty was not provided, disabling logind integration > [ 159.897] (--) PCI:*(0:0:2:0) 8086:9b41:17aa:5079 rev 2, Mem @ > 0xb000/16777216, 0xa000/268435456, I/O @ 0x3000/64, BIOS @ > 0x/131072 > [ 159.898] (II) LoadModule: "glx" > [ 159.898] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so > [ 159.911] (II) Module glx: vendor="X.Org Foundation" > [ 159.911] compiled for 1.19.3, module version = 1.0.0 > [ 159.911] ABI class: X.Org Server Extension, version 10.0 > [ 159.911] (==) Matched intel as autoconfigured driver 0 > [ 159.911] (==) Matched modesetting as autoconfigured driver 1 > [ 159.911] (==) Matched fbdev as autoconfigured driver 2 > [ 159.911] (==) Matched vesa as autoconfigured driver 3 > [ 159.911] (==) Assigned the driver to the xf86ConfigLayout > [ 159.911] (II) LoadModule: "intel" > [ 159.911] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so > [ 159.914] (II) Module intel: vendor="X.Org Foundation" > [ 159.914] compiled for 1.19.3, module version = 2.99.917 > [ 159.914] Module class: X.Org Video Driver > [ 159.914] ABI class: X.Org Video Driver, version 23.0 > [ 159.914] (II) LoadModule: "modesetting" > [ 159.914] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so > [ 159.915] (II) Module modesetting: vendor="X.Org Foundation" > [ 159.915] compiled for 1.19.3, module version = 1.19.3 > [ 159.915] Module class: X.Org Video Driver > [ 159.915] ABI class: X.Org Video Driver, version 23.0 > [ 159.915] (II) LoadModule: "fbdev" > [ 159.915] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so > [ 159.917] (II) Module fbdev: vendor="X.Org Foundation" > [ 159.917] compiled for 1.18.99.901, module version = 0.4.3 > [ 159.917] Module class: X.Org Video Driver > [ 159.917] ABI class: X.Org Video Driver, version 23.0 > [ 159.917] (II) LoadModule: "vesa" > [ 159.917] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so > [ 159.917] (II) Module vesa: vendor="X.Org Foundation" > [ 159.917] compiled for 1.18.99.901, module version = 2.3.2 > [ 159.917] Module class:
Re: [qubes-users] Re: HCL - Intel NUC10i7FNK
Thank you ! I realy need it! :)
在2020年7月25日星期六 UTC+8 上午2:01:26 写道：
> On 7/24/20 5:51 PM, Zhao Jx wrote:
>
>
> 在 2020年4月14日星期二 UTC+8上午2:07:16，Max Andersen写道：
>>
>> Hi everyone,
>>
>> NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a Qubes
>> installation and takes up zero space.
>>
>> Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to 5.5.13-1
>> and got my 4K monitor working. no wifi. wifi device flapping for a few
>> minutes, then stop. Hoping for some upgrades at some point.
>>
>> Runs current-testing repo.
>>
>> Sincerely
>>
>> Max
>>
>
> Thanks for the post!
> I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0. I
> hope I can get answers from you.
> I Set legecy mode, security booting off, use USB stick to install OS.
> The following warning maseges is displayed when installing.
> "WARN anaconda:
> /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
>
> add_option is deprecated and will be removed in pykickstart-3. Use
> add_argument instead.
>op.add.option("--minlen",type="int")
> ..
> WARN anaconda.stdout:Not asking for VNC because we don't have a network
> ..
> WARN anaconda:X startup failed: Xorg exited with status 1
> WARN anaconda.stdout:X startup failed,aborting installation
> ERR anaconda.stdout:X startup failed, aboting installation"
>
> Do I miss setting something in bios or do I need to install the OS with
> DVD?
> Thanks a lot!
>
>
> I recently moved to Xubuntu on this device, since QubesOS suddenly would
> not boot anymore. Just hung and my 4K support dissapeared suddenly a few
> weeks prior to that.
>
> I am sorry it's such a hassle. Kali, Ubuntu, etc. has no issues with
> wireless so it seems to be Qubes specific.
>
> Good luck. You will need it.
>
> Sincerely
>
> Max
>
>
>
--
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/03ff0760-3c59-42d9-bddc-fe5d830230a1n%40googlegroups.com.
[qubes-users] Re: HCL - Intel NUC10i7FNK
在 2020年4月14日星期二 UTC+8上午2:07:16，Max Andersen写道：
>
> Hi everyone,
>
> NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a Qubes
> installation and takes up zero space.
>
> Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to 5.5.13-1 and
> got my 4K monitor working. no wifi. wifi device flapping for a few minutes,
> then stop. Hoping for some upgrades at some point.
>
> Runs current-testing repo.
>
> Sincerely
>
> Max
>
Thanks for the post!
I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0. I
hope I can get answers from you.
I Set legecy mode, security booting off, use USB stick to install OS.
The following warning maseges is displayed when installing.
"WARN anaconda:
/usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
add_option is deprecated and will be removed in pykickstart-3. Use
add_argument instead.
op.add.option("--minlen",type="int")
..
WARN anaconda.stdout:Not asking for VNC because we don't have a network
..
WARN anaconda:X startup failed: Xorg exited with status 1
WARN anaconda.stdout:X startup failed,aborting installation
ERR anaconda.stdout:X startup failed, aboting installation"
Do I miss setting something in bios or do I need to install the OS with DVD?
Thanks a lot!
--
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/47110b8b-4a18-40a0-831d-424d48afd99ao%40googlegroups.com.
Re: [qubes-users] Re: HCL - Intel NUC10i7FNK
On 7/24/20 5:51 PM, Zhao Jx wrote:
>
> 在 2020年4月14日星期二 UTC+8上午2:07:16，Max Andersen写道：
>
> Hi everyone,
>
> NUC's are promising. 64GB memory with 1TB NVMe is acceptable for a
> Qubes installation and takes up zero space.
>
> Got 800x600 with the 4.19 kernel. no wifi. Upgraded kernel to
> 5.5.13-1 and got my 4K monitor working. no wifi. wifi device
> flapping for a few minutes, then stop. Hoping for some upgrades at
> some point.
>
> Runs current-testing repo.
>
> Sincerely
>
> Max
>
>
> Thanks for the post!
> I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0.
> I hope I can get answers from you.
> I Set legecy mode, security booting off, use USB stick to install OS.
> The following warning maseges is displayed when installing.
> "WARN anaconda:
> /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
> add_option is deprecated and will be removed in pykickstart-3. Use
> add_argument instead.
> op.add.option("--minlen",type="int")
> ..
> WARN anaconda.stdout:Not asking for VNC because we don't have a network
> ..
> WARN anaconda:X startup failed: Xorg exited with status 1
> WARN anaconda.stdout:X startup failed,aborting installation
> ERR anaconda.stdout:X startup failed, aboting installation"
>
> Do I miss setting something in bios or do I need to install the OS
> with DVD?
> Thanks a lot!
I recently moved to Xubuntu on this device, since QubesOS suddenly would
not boot anymore. Just hung and my 4K support dissapeared suddenly a few
weeks prior to that.
I am sorry it's such a hassle. Kali, Ubuntu, etc. has no issues with
wireless so it seems to be Qubes specific.
Good luck. You will need it.
Sincerely
Max
--
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/2811d5dc-afc0-64b9-87e3-12b35c5fae94%40militant.dk.
