[qubes-users] Re: HCL - intel NUC10i7FNK
Ok, I just found small solution for stable display without artifacts and
blackouts. But I think hardware rendering is still of. May be I´ll get a
hint here.
For making it stable I found following solution:
https://github.com/QubesOS/qubes-issues/issues/6311
Stephan Hagen schrieb am Mittwoch, 20. Januar 2021 um 17:19:19 UTC+1:
> Hello all,
>
> I got it running on Intel NUC10FNH and use already latest kernel and
> network is up and find.
> Can you give me a hint what you want to tell with
> " - check GPU driver provides a better resolution (>= full HD display), "
>
> I have already 4k resolution but only software rendering.
> My xorg.0.log told me: AIGLX error: Calling driver entry point failed.
> ...reverting to software rendering."
> I can not find what I have to change. Graphics is lousy.
> In my EFI - Boot settings at xen.cfg is already (without my changes)
> options "iommo=no-igfx" and kernel "i915.alpha_support=1" like described
>
> May be somebody can help me to fix my graphic.
>
> Thank you
> Stephan
>
>
> Ludovic Bellier schrieb am Sonntag, 26. Juli 2020 um 18:47:02 UTC+2:
>
>> [Note: sorry for not replying directly to the original thread, but I
>> wasn't yet registered to the mailing-list, so I can't do a reply with my
>> MUA]
>>
>> Original copy-paste mail from zhaojx88 (see :
>> https://groups.google.com/d/msg/qubes-users/vRKrs5ZIg9c/WUepmWP9BwAJ):
>>
>> > 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!
>>
>> zhaojx88,
>>
>> you got a *network error*, so may be, you should follow my steps
>> with a USB Network Interface Controller (aka USB ethernet), because the
>> internal ethernet card isn't recognized by the default 4.9 linux kernel.
>>
>> My BIOS setting:
>>
>> Boot (section)
>>
>> Secure BootDisabled
>>
>> UEFI BootEnabled
>>
>> Legacy BootEnabled
>>
>> > Secure Boot (sub-section)
>>
>> System ModeUser
>>
>> Secure Boot Disabled
>>
>> Not Active (title)
>>
>> Secure Boot Mode Standard
>>
>> > Boot Priority
>>
>> UEFI Boot x (i.e. checked)
>>
>> Legacy Boot x (i.e. checked)
>>
>> USBx (i.e. checked)
>>
>> I used the 4.0.3 ISO from https://www.qubes-os.org/downloads/ on a
>> USB storage stick. On boot I used the F10 key for choosing the *UEFI*
>> USB device stick. And I installed Qubes-OS on my SSD with the help of
>> the Qubes-OS documentation.
>>
>> Note also than my first 4GB USB stick was too small for the iso,
>> finally I used a 32GB stick (but 8GB will be fine).
>>
>> If this doesn't resolve your problem, give more information (BIOS
>> screenshots, when you got the above error message, ...)
>>
>> --
>>
>> Ludovic
>>
>>
--
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/1c2f6bcf-6062-42e6-b6c0-7ab5c97ab04an%40googlegroups.com.
Re: [qubes-users] system-config-printer gives different results in template and VM
On Wed, Jan 20, 2021 at 11:43 AM unman wrote: > On Wed, Jan 20, 2021 at 11:03:43AM -0300, Franz wrote: > > On Tue, Jan 19, 2021 at 11:20 PM unman > wrote: > > > > > On Tue, Jan 19, 2021 at 11:25:47AM -0300, Franz wrote: > > > > Hello, > > > > > > > > if I write system-config-printer in the debian template I get the > > > expected > > > > GUI to config the printer and everything works as expected. > > > > > > > > If I write the same in the VM depending from the template, I get: > > > > Printing service not available. Start the service on this computer or > > > > connect to another server. > > > > If I click on start the service, nothing happens. > > > > > > > > After many years using Qubes, the template and the VM depending from > the > > > > template always behaved in the same way. I cannot understand why the > > > > template works and the VM does not. > > > > > > > > To be sure, I tried on two different VMs depending from the same > template > > > > an none works > > > > Best > > > > Franz > > > > > > > > > > You don't have cups/cupsd enabled in the qube: enable it on Services > tab > > > of GUI or using `qvm-service` > > > > > > > > Many thanks Unman, but why does the template not give the same error? > > > > I understand this kind of problem should be fixed in the template, not in > > the VM that depends on the template. > > > > But if the template works, how may I fix something that already works? > > best > > Franz > > By default Debian will enable services (and start them) after > installation. This is a problem for templates, which is why there is > specific advice about installing services in to Debian templates. > By contrast Fedora does not automatically start services. > > Many thanks Unman, I tried to start cups using Qubes manager GUI and now even the VM works and this survives reboot. No way I could have thought it alone. There are many services which can be enabled or disabled in an template > based qube. cups is just one of them. > That said, I'm puzzled as to why cups *is* running in your template - it > doesn't seem to be in my Debian 10. > Well I suspect that cups is running in my template Debian 10. In fact if I digit system-config-printer it starts the printer GUI without errors. -- 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/CAPzH-qAfSLvkHFi6nmZ__MRGHFv17tWk8Tso7PSarZ2u%3DBnajQ%40mail.gmail.com.
[qubes-users] Re: HCL - intel NUC10i7FNK
Hello all,
I got it running on Intel NUC10FNH and use already latest kernel and
network is up and find.
Can you give me a hint what you want to tell with
" - check GPU driver provides a better resolution (>= full HD display), "
I have already 4k resolution but only software rendering.
My xorg.0.log told me: AIGLX error: Calling driver entry point failed.
...reverting to software rendering."
I can not find what I have to change. Graphics is lousy.
In my EFI - Boot settings at xen.cfg is already (without my changes)
options "iommo=no-igfx" and kernel "i915.alpha_support=1" like described
May be somebody can help me to fix my graphic.
Thank you
Stephan
Ludovic Bellier schrieb am Sonntag, 26. Juli 2020 um 18:47:02 UTC+2:
> [Note: sorry for not replying directly to the original thread, but I
> wasn't yet registered to the mailing-list, so I can't do a reply with my
> MUA]
>
> Original copy-paste mail from zhaojx88 (see :
> https://groups.google.com/d/msg/qubes-users/vRKrs5ZIg9c/WUepmWP9BwAJ):
>
> > 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!
>
> zhaojx88,
>
> you got a *network error*, so may be, you should follow my steps
> with a USB Network Interface Controller (aka USB ethernet), because the
> internal ethernet card isn't recognized by the default 4.9 linux kernel.
>
> My BIOS setting:
>
> Boot (section)
>
> Secure BootDisabled
>
> UEFI BootEnabled
>
> Legacy BootEnabled
>
> > Secure Boot (sub-section)
>
> System ModeUser
>
> Secure Boot Disabled
>
> Not Active (title)
>
> Secure Boot Mode Standard
>
> > Boot Priority
>
> UEFI Boot x (i.e. checked)
>
> Legacy Boot x (i.e. checked)
>
> USBx (i.e. checked)
>
> I used the 4.0.3 ISO from https://www.qubes-os.org/downloads/ on a
> USB storage stick. On boot I used the F10 key for choosing the *UEFI*
> USB device stick. And I installed Qubes-OS on my SSD with the help of
> the Qubes-OS documentation.
>
> Note also than my first 4GB USB stick was too small for the iso,
> finally I used a 32GB stick (but 8GB will be fine).
>
> If this doesn't resolve your problem, give more information (BIOS
> screenshots, when you got the above error message, ...)
>
> --
>
> Ludovic
>
>
--
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/aa263dca-ce6e-429d-bf4a-8edf9fecd393n%40googlegroups.com.
[qubes-users] Problems setting /etc/hosts
Hi, Hopefully I'm doing something silly here. I want to add a couple of entries into my /etc/hosts file in a specific VM. The instructions here are nice and clear: https://www.qubes-os.org/doc/config-files/ except... that doesn't work. I've added the following to my /rw/config/rc.local : echo '127.0.0.1 example.com' >> /etc/hosts And after a VM restart my /etc/hosts is unchanged. Also, as an aside, is it odd that rc.local is owned by root, if it's something that's expected to be changed per-VM? What am I missing? Thanks! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f8c17e62-8c94-4106-8933-8a77b4c8ea4an%40googlegroups.com.
Re: [qubes-users] Problems setting /etc/hosts
mgla...@gmail.com: Hi, Hopefully I'm doing something silly here. I want to add a couple of entries into my /etc/hosts file in a specific VM. The instructions here are nice and clear: https://www.qubes-os.org/doc/config-files/ except... that doesn't work. I've added the following to my /rw/config/rc.local : echo '127.0.0.1 example.com' >> /etc/hosts And after a VM restart my /etc/hosts is unchanged. Might have to add "sudo" in front of that echo. Also, double-check that rc.local is set as executable and in proper script format. Does it work if you run it yourself from the command line? Also, as an aside, is it odd that rc.local is owned by root, if it's something that's expected to be changed per-VM? No, because it's only the root account that belongs to the VM. -- - 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/4722e568-8182-17ab-4366-61a600ad914a%40danwin1210.me.
Re: [qubes-users] Problems setting /etc/hosts
On Wed, Jan 20, 2021 at 10:34:14PM +, 'awokd' via qubes-users wrote: > mgla...@gmail.com: > > Hi, > > > > Hopefully I'm doing something silly here. > > > > I want to add a couple of entries into my /etc/hosts file in a specific VM. > > The instructions here are nice and > > clear: https://www.qubes-os.org/doc/config-files/ except... that doesn't > > work. > > > > I've added the following to my /rw/config/rc.local : > > echo '127.0.0.1 example.com' >> /etc/hosts > > And after a VM restart my /etc/hosts is unchanged. > > Might have to add "sudo" in front of that echo. Also, double-check that > rc.local is set as executable and in proper script format. Does it work if > you run it yourself from the command line? > > > Also, as an aside, is it odd that rc.local is owned by root, if it's > > something that's expected to be changed per-VM? > > No, because it's only the root account that belongs to the VM. > I do this with a (fairly) extensive list , and block dns. I keep the entries in a file in /rw/config/hosts, and then in rc.local: cat /rw/config/hosts >> etc/hosts Doesn't need sudo for that - and the file should be in proper format and executable already, (but always worth checking). Works for me. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210121011901.GA3868%40thirdeyesecurity.org.
Re: [qubes-users] issues with i3, xrandr and keyboard
On 1/19/21 6:27 PM, 'qtpie' via qubes-users wrote: Hi, A few questions about using Qubes with i3. I think the idea behind i3 is great, but getting everything to work is a bit of a struggle. I'm using the i3 window manager with Qubes in a multi-monitor setup. The laptop monitor is 1920x1080, the external monitor is 2560x1440. To enable the second monitor I do $ xrandr --output eDP1 --auto --right-of DP1 --output DP1 --auto. The issue I keep running in to is that about half of the time, my mouse will not work on the the external monitor on the rightmost quarter and lowest quarter (approximately). The pointer will move there, but clicks are not registered. It is as if the mousedriver sees the second monitor as 1920x1080 instead of its actual resolution. The status bar is displayed on both monitors. Hi, This can be fixed by increasing the dom0 Qubes GUI video memory [1]. [1] https://www.qubes-os.org/doc/gui-configuration/#video-ram-adjustment-for-high-resolution-displays Cheers, Patrik I have read much of what there is to read on xrandr and tried many options, like switching monitor postitions, scaling, panning, positioning, but to to avail, the issue keeps returning. I have tried comparing the output of $ xrandr -q, but there is no difference between working and error situations. - Does anyone have a comparable setup and what xrandr command do you use? - Is there an alternative to using xrandr under i3? Also, how do you change your keyboard settings under i3/Fedora/Qubes? I want to use the us-altgr-intl keymap. Under i3 when I do $ localectl set-keymap us-altgr-intl in a qube vm terminal, this has no effect in applications. The right alt key instead remains used to open menu's (altgr+f for File, altgr+e for Edit, etc.) If I could use altgr-intl and retain that functionality that would actually be great. thanks! qtpie -- 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/61ca04d6-f41b-acf4-efb8-ce58f1136487%40gmail.com.
[qubes-users] Desktop suggestion
Hello, A Desktop suggestion with various independent USB controllers, an open source firmware, at least 32gb RAM and possibly a nerfable microprocessor to disable ME or equivalent. No gaming, no hyper speed. Just working well with Qubes. Well it seems basic requirements, but I doubt it is easy. Three years ago Taiidan suggested an ASUS KCMA-D8, keeping in mind the above requirements. See this thread: https://groups.google.com/g/qubes-users/c/MEMdWdsht5k But three years passed and possibly even the above board or the processor changed, or something better had been released. Things change, even Taiidan disappeared from this email list. Best Franz -- 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/CAPzH-qCyCPaFAoGyQQPYwzgPfi1n_vmC4TEcKM%3DpCL8W3mbttw%40mail.gmail.com.
Re: [qubes-users] system-config-printer gives different results in template and VM
On Wed, Jan 20, 2021 at 11:03:43AM -0300, Franz wrote: > On Tue, Jan 19, 2021 at 11:20 PM unman wrote: > > > On Tue, Jan 19, 2021 at 11:25:47AM -0300, Franz wrote: > > > Hello, > > > > > > if I write system-config-printer in the debian template I get the > > expected > > > GUI to config the printer and everything works as expected. > > > > > > If I write the same in the VM depending from the template, I get: > > > Printing service not available. Start the service on this computer or > > > connect to another server. > > > If I click on start the service, nothing happens. > > > > > > After many years using Qubes, the template and the VM depending from the > > > template always behaved in the same way. I cannot understand why the > > > template works and the VM does not. > > > > > > To be sure, I tried on two different VMs depending from the same template > > > an none works > > > Best > > > Franz > > > > > > > You don't have cups/cupsd enabled in the qube: enable it on Services tab > > of GUI or using `qvm-service` > > > > > Many thanks Unman, but why does the template not give the same error? > > I understand this kind of problem should be fixed in the template, not in > the VM that depends on the template. > > But if the template works, how may I fix something that already works? > best > Franz By default Debian will enable services (and start them) after installation. This is a problem for templates, which is why there is specific advice about installing services in to Debian templates. By contrast Fedora does not automatically start services. There are many services which can be enabled or disabled in an template based qube. cups is just one of them. That said, I'm puzzled as to why cups *is* running in your template - it doesn't seem to be in my Debian 10. -- 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/20210120144346.GA930%40thirdeyesecurity.org.
Re: [qubes-users] system-config-printer gives different results in template and VM
On Tue, Jan 19, 2021 at 11:20 PM unman wrote: > On Tue, Jan 19, 2021 at 11:25:47AM -0300, Franz wrote: > > Hello, > > > > if I write system-config-printer in the debian template I get the > expected > > GUI to config the printer and everything works as expected. > > > > If I write the same in the VM depending from the template, I get: > > Printing service not available. Start the service on this computer or > > connect to another server. > > If I click on start the service, nothing happens. > > > > After many years using Qubes, the template and the VM depending from the > > template always behaved in the same way. I cannot understand why the > > template works and the VM does not. > > > > To be sure, I tried on two different VMs depending from the same template > > an none works > > Best > > Franz > > > > You don't have cups/cupsd enabled in the qube: enable it on Services tab > of GUI or using `qvm-service` > > Many thanks Unman, but why does the template not give the same error? I understand this kind of problem should be fixed in the template, not in the VM that depends on the template. But if the template works, how may I fix something that already works? best Franz -- 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/CAPzH-qCjO6j1U5xUTUk57LxR2Vry7dxzVLMETBH81mLcWTug5Q%40mail.gmail.com.
