Re: [qubes-devel] NVIDIA RTX 20XX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Mar 14, 2020 at 10:52:09AM +0100, Marek Marczykowski-Górecki wrote: > On Sat, Mar 14, 2020 at 02:15:15AM -0700, Me wrote: > > Kernel 5.6 latest(2) > > > > dom0: sudo lspci -vv > > 45:00.0 Network controller: Intel Corporation Wireless-AC

Re: [qubes-devel] NVIDIA RTX 20XX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Mar 14, 2020 at 02:15:15AM -0700, Me wrote: > Kernel 5.6 latest(2) > > dom0: sudo lspci -vv > 45:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) > Subsystem: Bigfoot Networks, Inc. Device 1550 > Control: I/O-

Re: [qubes-devel] NVIDIA RTX 20XX

A little note for ease following things, you can refer your kernel version with respect to 5.6-rc4.1 or 5.6-rc4.2, which are respectively, first release(first non working build) and second release (second working build). Thank you :) On 2020-03-14 10:15, Me wrote: > Kernel 5.6 latest(2) > >

Re: [qubes-devel] NVIDIA RTX 20XX

Kernel 5.6 latest(2) dom0: sudo lspci -vv 45:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Subsystem: Bigfoot Networks, Inc. Device 1550 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- sys-net: sudo lspci -vv

Re: [qubes-devel] NVIDIA RTX 20XX

I've remove it before installing the last one, but I will reinstall it in the morning and provide allnecessary logs.(2:30 am here) thank you -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving

Re: [qubes-devel] NVIDIA RTX 20XX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 13, 2020 at 05:58:26PM -0700, Me wrote: > Yes. The latest one works fine(the new one compiled tonight). > Sure: > in dom0: sudo lspci -v > > 45:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) > Subsystem:

Re: [qubes-devel] NVIDIA RTX 20XX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 13, 2020 at 03:55:30PM -0700, Me wrote: > It works now. Both, the graphic card and wi-fi. > I have no words to thank you enough. Ok, so the patch for 5.6 seems broken. Can you post some more info about the system? Specifically: in

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-13 23:55, Me wrote: > It works now. Both, the graphic card and wi-fi. > I have no words to thank you enough. > You are welcome. Don't hesitate to give us feedback if anything is working wrong. Best -- You received this message because you are subscribed to the Google Groups

Re: [qubes-devel] NVIDIA RTX 20XX

It works now. Both, the graphic card and wi-fi. I have no words to thank you enough. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [qubes-devel] NVIDIA RTX 20XX

Thank you. I will give a try now On Friday, 13 March 2020 18:35:30 UTC-4, Frédéric Pierret wrote: > > > > On 2020-03-13 20:57, Marek Marczykowski-Górecki wrote: > > > Frédéric, can you build a kernel with that upstream commit reverted and > > original patch applied? > > The kernel is built and

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-13 20:57, Marek Marczykowski-Górecki wrote: > Frédéric, can you build a kernel with that upstream commit reverted and > original patch applied? The kernel is built and available on my mirror as a second release or 5.6-rc4 on my mirror. The branch is also updated on github to see

Re: [qubes-devel] NVIDIA RTX 20XX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 13, 2020 at 08:40:58PM +0100, Frédéric Pierret wrote: > The patch is in upstream for 5.6. The issue would be only under R4.0 with > older Xen. > > That's the reason of his question. I let Marek correct me if I'm wrong. That's correct,

Re: [qubes-devel] NVIDIA RTX 20XX

The patch is in upstream for 5.6. The issue would be only under R4.0 with older Xen. That's the reason of his question. I let Marek correct me if I'm wrong. Best, Le 13 mars 2020 19:19:32 GMT+01:00, Me a écrit : >I believe I found the issue. The patch:

Re: [qubes-devel] NVIDIA RTX 20XX

I believe I found the issue. The patch: 0014-xen-pciback-add-attribute-to-allow-MSI-enable-flag-w.patch is not found on your branch. According to Marek. this patch is essential for pass-trough. I will try to add it and re compile the kernel now. Thank you On Thursday, 5 March 2020 11:41:28 UTC-5,

Re: [qubes-devel] NVIDIA RTX 20XX

I really cannot find any solution for wifi, neither for ethernet. I was trying to install a completely new operating system (ubuntu). I guess I need to wait until the next kernel 5.6 is available in final the version and it is uploaded in qubes repo. I've been tried with 4.0 as well, no luck at

Re: [qubes-devel] NVIDIA RTX 20XX

the kernel is the issue again. I'm using a intel wireless ac 9260. I will try to recompile the kernel by myself using the old configuration from earliest kernel...I will also try to get the fedora 32 updates over dom0 fc31(basically to update the fc31 to 32 under dom0) and their compiled

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-05 16:53, Ovidiu wrote: > you made my day! It works perfectly now. no public issues. I forget to > disable the old dom0 repo. A small issue:))) I have no wireless connection > now but If running in VM the RC kernel, what you can test is to run only 5.6-rc4 in dom0 and use any

Re: [qubes-devel] NVIDIA RTX 20XX

you made my day! It works perfectly now. no public issues. I forget to disable the old dom0 repo. A small issue:))) I have no wireless connection now but I will sort it somehow. once again, thank you -- You received this message because you are subscribed to the Google Groups

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-05 16:37, Ovidiu wrote: > Thank you for your patience. It works but for some reasons it verifies a > different version of kernel: Not sure it's related. I suggest to: 1) restart your update VM for cleaning stuff (here I'm seeing sys-firewall) 2) ensure clean too by appending

Re: [qubes-devel] NVIDIA RTX 20XX

Thank you for your patience. It works but for some reasons it verifies a different version of kernel: [test@dom0 Downloads]$ sudo qubes-dom0-update kernel-latest kernel-latest-devel --nogpgcheck Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Fedora 31 -

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-05 16:13, Ovidiu wrote: > Is the repo file correct? > > [notset-dom0-unstable] > name = Notset Repository > #baseurl = > https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 > This should

Re: [qubes-devel] NVIDIA RTX 20XX

Is the repo file correct? [notset-dom0-unstable] name = Notset Repository #baseurl = https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 enabled = 1 metadata_expire = 7d gpgcheck = 1 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-notset I don't know what are the deps for kernel

Re: [qubes-devel] NVIDIA RTX 20XX

[notset-dom0-unstable] name = Notset Repository #baseurl = https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 enabled = 1 metadata_expire = 7d gpgcheck = 1 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-notset result: Using sys-firewall as UpdateVM to download updates for

Re: [qubes-devel] NVIDIA RTX 20XX

Don't use metalink. Use baseurl. Metalink is not generated and will be not (no other mirror than mine). On 2020-03-05 15:40, Ovidiu wrote: > I've made a new file: notset.repo > > It looks like: > [notset-dom0-unstable] > name = Notset Repository > #baseurl = >

Re: [qubes-devel] NVIDIA RTX 20XX

repomd.xml.metalink I mean -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit

Re: [qubes-devel] NVIDIA RTX 20XX

the respond.xml.metalink file doesn't exists -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on

Re: [qubes-devel] NVIDIA RTX 20XX

same result: Notset Repository 286 B/s | 162 B 00:00 Error: Failed to download metadata for repo 'notset-dom0-unstable': Cannot prepare internal mirrorlist: Status code: 404 for

Re: [qubes-devel] NVIDIA RTX 20XX

I've made a new file: notset.repo It looks like: [notset-dom0-unstable] name = Notset Repository #baseurl = https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 metalink = https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31/repodata/repomd.xml.metalink

Re: [qubes-devel] NVIDIA RTX 20XX

Look at my second response: """ BTW, you can simply use baseurl: baseurl = https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 """ On 2020-03-05 15:34, Ovidiu wrote: > something is wrong: > > Qubes Dom0 Repository (unstable)    380  B/s | 162  B 00:00    >

Re: [qubes-devel] NVIDIA RTX 20XX

something is wrong: Qubes Dom0 Repository (unstable)380 B/s | 162 B 00:00 Error: Failed to download metadata for repo 'qubes-dom0-unstable': Cannot prepare internal mirrorlist: Status code: 404 for

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-05 14:55, Frédéric Pierret wrote: > Yes or clone the current .repo file and adapt names. > > WARNING: This 'unstable' repo is very unstable/dev packages content. Don't > update your system with this repo :). Basically, this 'unstable' serves me > for installing and testing devel

Re: [qubes-devel] NVIDIA RTX 20XX

Yes or clone the current .repo file and adapt names. WARNING: This 'unstable' repo is very unstable/dev packages content. Don't update your system with this repo :). Basically, this 'unstable' serves me for installing and testing devel branches for Qubes. So some packages are broken. But here,

Re: [qubes-devel] NVIDIA RTX 20XX

Wow. Million thanks. So basically I need to replace the baseurl: https://yum.qubes-os.org/r$releasever/current/dom0/fc31 with https://mirror.notset.fr/qubes/repo/notset/yum/r4.1/unstable/dom0/fc31 and metalink: https://yum.qubes-os.org/r$releasever/current/dom0/fc31/repodata/repomd.xml.metalink

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-05 13:40, Ovidiu wrote: > no luck using > > 1. dom0:   qubes-dom0-update gcc kernel-devel kmod kernel-headers; > (qubes-dom0-update --enablerepo=qubes-dom0-unstable if using newer kernel) > > > 2. appvm:  download NVIDIA-Linux-375.20-install.run (any appvm) > 3. dom0:   qvm-run

Re: [qubes-devel] NVIDIA RTX 20XX

no luck using 1. dom0: qubes-dom0-update gcc kernel-devel kmod kernel-headers; (qubes-dom0-update --enablerepo=qubes-dom0-unstable if using newer kernel) 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > NVIDIA.run;

Re: [qubes-devel] NVIDIA RTX 20XX

Hi again, I've made a new attempt today, using the negativo17 repo. the results are better then before. I didn't get the blur screen anymore, but it remains stuck before opening the lightdm. kernel.log: https://pastebin.com/sjpV8ZF7 xorg.log: https://pastebin.com/RTu9LH2A xsession-errors:

Re: [qubes-devel] NVIDIA RTX 20XX

Thank you. I have no sensitive information in this file since this system is for testing purpose only. Here is the file(files actually, I have xsession-errors and xsession-errors.old) xsession-errors: https://pastebin.com/VyQj9S5E xsession-errors.old: https://pastebin.com/s5Yh88Sa Once again,

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-04 14:14, Ovidiu wrote: > hello again and I'm sorry for the delay. is the nouveau log the same with > xorg log? or where can I find it? All X related logs are location in ~/.xsession-errors. Be careful with this file. There is sensitive informations like VM names etc because

Re: [qubes-devel] NVIDIA RTX 20XX

hello again and I'm sorry for the delay. is the nouveau log the same with xorg log? or where can I find it? thanks -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: [qubes-devel] NVIDIA RTX 20XX

The relevant parts are probably the 'nouveau' logs. I would say that you should submit it to upstream through bugzilla too. Attach you log file to it. Maybe they would have an idea of what's going on. On 2020-03-03 18:07, Ovidiu wrote: > Finally managed to get the log(bling because I didn't see

Re: [qubes-devel] NVIDIA RTX 20XX

Finally managed to get the log(bling because I didn't see anything on display)/ Here is the kernel log: *https://pastebin.com/YwQrMePB* Thank you -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-03 17:30, Ovidiu wrote: > it is not actually freezing, a distorted image appear with small characters > (like the display was broken) but when I press ctrl alt f12, something is > moving I would say that if it's not freezing or kernel oops is not occurring that's certainly

Re: [qubes-devel] NVIDIA RTX 20XX

it is not actually freezing, a distorted image appear with small characters (like the display was broken) but when I press ctrl alt f12, something is moving on display. However, I will follow your steps and upload the kernel log as soon as I get back home. thank you for your help!!! -- You

Re: [qubes-devel] NVIDIA RTX 20XX

On 2020-03-03 16:19, Ovidiu wrote: > Stupid question - Where can I find the kernel logs? Ideally, I would suggest you to first add to your kernel cmdline in grub: "... rhgb quiet loglevel=8 and systemd.log_level=debug". Then, in a dom0 terminal, you can do something like 'dmesg > kernel.log'.

Re: [qubes-devel] NVIDIA RTX 20XX

Stupid question - Where can I find the kernel logs? -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this

Re: [qubes-devel] NVIDIA RTX 20XX

Right, so method 1, rpmfusion: Freshly installed qubes 41(20200214): dom0: sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing -y && sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest kernel-latest-devel gedit -y && sudo reboot (gedit package to edit

Re: [qubes-devel] NVIDIA RTX 20XX

I will install 4.1 now and compile and install the latest kernel directly from kernel.org. I will keep you posted. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: [qubes-devel] NVIDIA RTX 20XX

Unfortunately I don't have the Qubes on PC anymore so I cannot provide the logs, but I will re install it later today and provide it. I will use qubes 4.1 fc 31 and use both methods(nvidia and rpmfusion). Apart of that, I believe indeed it's a kernel issue. I had fedora 31, installed in my

Re: [qubes-devel] NVIDIA RTX 20XX

Hi, I should have replied to this thread. Current kernel-latest 5.5.6 on Qubes repos is integrating the patch as it is in upstream. It's the same for latest kernel 5.4.23. So there is no more kernel freeze/oops. On 2020-03-03 11:16, Lipan Ovidiu wrote: > I've been tried your method but without

Re: [qubes-devel] NVIDIA RTX 20XX

I've been tried your method but without success. After reboot, the display freezes. I must mention I didn't tried under legacy since my laptop doesn't support it. I have an AW area 51M rtx 2080. I also tried to install the property driver, the installation was successful, no errors, but

Re: [qubes-devel] NVIDIA RTX 20XX

Hi, Without too much intrusion into your dom0, just download the rpms manually, check the signature if you want and copy the rpms into your dom0 then use dnf to install rpm. Else, I will provide you repo file latter. Best, Frédéric Le 8 février 2020 17:42:23 GMT+01:00, Ralph Alexander Bariz

Re: [qubes-devel] NVIDIA RTX 20XX

for manual installation of the rpm packages I lack the information of which are the ones to install Am Samstag, 8. Februar 2020 17:35:56 UTC+1 schrieb Ralph Alexander Bariz: > > sorry, if I'm acting stupid. coming from debian world, there I probably > would figure it out myself. also do not

Re: [qubes-devel] NVIDIA RTX 20XX

sorry, if I'm acting stupid. coming from debian world, there I probably would figure it out myself. also do not really find anything to that Am Samstag, 8. Februar 2020 17:26:05 UTC+1 schrieb Ralph Alexander Bariz: > > well, trying to test it but I'm actually hanging at... how the hell do I >

Re: [qubes-devel] NVIDIA RTX 20XX

well, trying to test it but I'm actually hanging at... how the hell do I add your repo without modifying my qubes-dom0.repo manually any way? if not, your repo does not contain thiy metalink stuff Am Montag, 27. Januar 2020 01:02:32 UTC+1 schrieb Frédéric Pierret: > > Hi, > > We debugged this

Re: [qubes-devel] NVIDIA RTX 20XX

Hi, We debugged this problem with Marek and found a simple temporary workaround: https://mirror.notset.fr/qubes/repo/notset/yum/r4.0/unstable/dom0/fc25/rpm/ If you want to try and tell us it solves the problem on your side too, you can find the built kernel with this path on my mirror:

Re: [qubes-devel] NVIDIA RTX 20XX

Hi, Thank you for your feedback. I just tested under R4.1 in development and I succeeded to have a kernel log thanks to Marek and few hacks in dom0. Here is the bug report: https://bugzilla.kernel.org/show_bug.cgi?id=206299 FYI, I tried few months ago to build NVIDIA module under Qubes but I

[qubes-devel] NVIDIA RTX 20XX

Have the same problem with a rtx 2070. My temporary solution is to put a cheap gpu into my pc(nvidia geforce 710) into the second pci port and cut of the power of the 2070 when using qubes. the problem is simple. The included nouveau driver does not support it. You could install the properitary

[qubes-devel] NVIDIA RTX 20XX

Hi, Does anyone succeeded to have a working/non-crashing system with a nvidia RTX 20XX, specifically 2080TI in my case? Currently having instant reboot issues on Qubes 4.0 whereas on Windows it currently works pretty well so I don't expect having GPU hardware issue. Thank you in advance,