should be based on this, what package are you missing?

KKyle Gospo should be based on this, what package are you missing?

V

vertigo.red•12/30/23, 7:27 PM

nvidia-smi

K

Kyle GospoOP•12/30/23, 7:27 PM

that is defintiely there, it's part of our test to make sure nvidia is working

K

Kyle GospoOP•12/30/23, 7:27 PM

can you run

rpm-ostree status

rpm-ostree status

for me?

KKyle Gospo can you run `rpm-ostree status` for me?

V

vertigo.red•12/30/23, 7:30 PM

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia:latest
                   Digest: sha256:221a67232517b911612198097ed5b33a7354e1483d2982b0881851e9b3ac445d
                  Version: 39.20231229.0 (2023-12-29T17:32:53Z)
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid

  ostree-image-signed:docker://ghcr.io/ublue-os/kinoite-asus-nvidia:latest
                   Digest: sha256:21149572e4d33f70e62e878311fe93c44bd8e786d0697ae8d060964241d275b6
                  Version: 39.20231230.0 (2023-12-30T16:21:36Z)
      RemovedBasePackages: firefox firefox-langpacks 121.0-2.fc39
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid
                   Pinned: yes

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia:latest
                   Digest: sha256:221a67232517b911612198097ed5b33a7354e1483d2982b0881851e9b3ac445d
                  Version: 39.20231229.0 (2023-12-29T17:32:53Z)
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid

  ostree-image-signed:docker://ghcr.io/ublue-os/kinoite-asus-nvidia:latest
                   Digest: sha256:21149572e4d33f70e62e878311fe93c44bd8e786d0697ae8d060964241d275b6
                  Version: 39.20231230.0 (2023-12-30T16:21:36Z)
      RemovedBasePackages: firefox firefox-langpacks 121.0-2.fc39
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid
                   Pinned: yes

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia:latest
                   Digest: sha256:221a67232517b911612198097ed5b33a7354e1483d2982b0881851e9b3ac445d
                  Version: 39.20231229.0 (2023-12-29T17:32:53Z)
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid

  ostree-image-signed:docker://ghcr.io/ublue-os/kinoite-asus-nvidia:latest
                   Digest: sha256:21149572e4d33f70e62e878311fe93c44bd8e786d0697ae8d060964241d275b6
                  Version: 39.20231230.0 (2023-12-30T16:21:36Z)
      RemovedBasePackages: firefox firefox-langpacks 121.0-2.fc39
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid
                   Pinned: yes

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia:latest
                   Digest: sha256:221a67232517b911612198097ed5b33a7354e1483d2982b0881851e9b3ac445d
                  Version: 39.20231229.0 (2023-12-29T17:32:53Z)
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid

  ostree-image-signed:docker://ghcr.io/ublue-os/kinoite-asus-nvidia:latest
                   Digest: sha256:21149572e4d33f70e62e878311fe93c44bd8e786d0697ae8d060964241d275b6
                  Version: 39.20231230.0 (2023-12-30T16:21:36Z)
      RemovedBasePackages: firefox firefox-langpacks 121.0-2.fc39
          LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
                           virt-manager waydroid
                   Pinned: yes

V

vertigo.red•12/30/23, 7:31 PM

Checked system monitor right now. No nvidia dGPU information.

V

vertigo.red•12/30/23, 7:33 PM

And back when I used openSUSE TW, there were nvidia basic driver + cuda. Basic driver showed nothing for system monitor too, but when I searched for nvidia-smi, it said it was in CUDA package. So I installed it and system monitor started showing nvidia dGPU info.

K

Kyle GospoOP•12/30/23, 7:33 PM

can you share the name of the package you installed?

K

Kyle GospoOP•12/30/23, 7:33 PM

I'll take a look at ublue/nvidia and see what's up

KKyle Gospo can you share the name of the package you installed?

V

vertigo.red•12/30/23, 7:40 PM

nvidia-compute-utils-G06-545.29.06-18.1.x86_64

nvidia-compute-utils-G06-545.29.06-18.1.x86_64

And repo if matters: https://download.nvidia.com/opensuse/tumbleweed/x86_64/

V

vertigo.red•12/30/23, 7:41 PM

Probably, not even CUDA but some compute thing...

Ccpuccino Brightness doesnt seem to be working now on legion? Im on testing

K

Kyle GospoOP•12/30/23, 8:46 PM

latest update should fix that

Hheri today, discord decided to just not work at all

H

heri•12/30/23, 8:56 PM

@KyleGospo not sure if you can help me with this, but yet again today I can't use discord on my laptop it refuses to load up no matter what client I try

Hheri @KyleGospo not sure if you can help me with this, but yet again today I can't us...

K

Kyle GospoOP•12/30/23, 8:59 PM

run it from the terminal, get any logs out of it?

K

Kyle GospoOP•12/30/23, 8:59 PM

flatpak run com.discordapp.Discord

flatpak run com.discordapp.Discord

KKyle Gospo `flatpak run com.discordapp.Discord`

H

heri•12/30/23, 9:04 PM

Seems like SSL failures prevent it from updating or starting or running

H

heri•12/30/23, 9:05 PM

-202 ERR_CERT_AUTHORITY_INVALID

H

heri•12/30/23, 9:06 PM

blackbox: 2023-12-30T21:05:38.893Z 28 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 20000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703970261569 with error: ERR_CERT_AUTHORITY_INVALID
blackbox: 2023-12-30T21:05:38.899Z 29 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T21:05:38.893Z 28 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 20000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703970261569 with error: ERR_CERT_AUTHORITY_INVALID
blackbox: 2023-12-30T21:05:38.899Z 29 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T21:05:38.893Z 28 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 20000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703970261569 with error: ERR_CERT_AUTHORITY_INVALID
blackbox: 2023-12-30T21:05:38.899Z 29 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T21:05:38.893Z 28 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 20000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703970261569 with error: ERR_CERT_AUTHORITY_INVALID
blackbox: 2023-12-30T21:05:38.899Z 29 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

Hheri Seems like SSL failures prevent it from updating or starting or running

K

Kyle GospoOP•12/30/23, 9:09 PM

is your timezone correct?

K

Kyle GospoOP•12/30/23, 9:11 PM

5:38 don't look right to me

KKyle Gospo is your timezone correct?

H

heri•12/30/23, 9:14 PM

Let me check

H

heri•12/30/23, 9:15 PM

Yeah it's correct

H

heri•12/30/23, 9:15 PM

It's 4:15 for me

KKyle Gospo 5:38 don't look right to me

H

heri•12/30/23, 9:15 PM

Not sure where it's getting 5:38 from Because my timezone is correct in settings

Hheri Not sure where it's getting 5:38 from Because my timezone is correct in settings

H

HikariKnight•12/30/23, 9:26 PM

double check if its right in the bios

HHikariKnight double check if its right in the bios

H

heri•12/30/23, 9:27 PM

I don't know what you mean by that

H

HikariKnight•12/30/23, 9:28 PM

check if the clock in bios/uefi is correct

HHikariKnight check if the clock in bios/uefi is correct

H

heri•12/30/23, 9:43 PM

Not sure how it helps the situation, but yes the time is correct

H

HikariKnight•12/30/23, 9:44 PM

just wanted to check since bios time can be wrong and if ntp doesnt work then the bios clock will dictate the time

Hheri Not sure how it helps the situation, but yes the time is correct

H

HikariKnight•12/30/23, 9:45 PM

can you check if systemd-timesyncd.service is running?

systemctl status systemd-timesyncd.service

systemctl status systemd-timesyncd.service

HHikariKnight can you check if systemd-timesyncd.service is running? `systemctl status systemd...

H

heri•12/30/23, 9:46 PM

It's disabled

Hheri It's disabled

H

HikariKnight•12/30/23, 9:47 PM

sudo systemctl enable --now systemd-timesyncd.service

sudo systemctl enable --now systemd-timesyncd.service

it will enable syncing of the time with an ntp server so it will grab the time online

H

heri•12/30/23, 9:48 PM

ok

H

HikariKnight•12/30/23, 9:48 PM

should fix your wrong time and also should hopefully fix the ssl issue with discord flatpak

H

heri•12/30/23, 9:55 PM

Do I need to reboot for it to apply properly?

H

HikariKnight•12/30/23, 9:56 PM

should sync immediately, but you can reboot to be sure

H

HikariKnight•12/30/23, 9:56 PM

you can check with the status command again

H

HikariKnight•12/30/23, 9:56 PM

HHikariKnight you can check with the status command again

H

heri•12/30/23, 9:56 PM

It says it's running but discord still fails to run

H

heri•12/30/23, 9:57 PM

Same cert errors

H

HikariKnight•12/30/23, 9:57 PM

what does it say on the status line for systemd-timesyncd

HHikariKnight what does it say on the status line for systemd-timesyncd

H

heri•12/30/23, 9:57 PM

Fym

H

HikariKnight•12/30/23, 9:57 PM

fym?

Hheri It says it's running but discord still fails to run

H

heri•12/30/23, 9:58 PM

Like I said, The status command says it's active and running

H

HikariKnight•12/30/23, 9:58 PM

H

HikariKnight•12/30/23, 9:58 PM

this line

H

HikariKnight•12/30/23, 9:59 PM

and the actual log part

HHikariKnight Click to see attachment

H

heri•12/30/23, 10:01 PM

Ah, it says it's contacted 0.fedora.pool.ntp.org

H

HikariKnight•12/30/23, 10:01 PM

ok and what does the log say?

HHikariKnight ok and what does the log say?

H

heri•12/30/23, 10:02 PM

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

H

HikariKnight•12/30/23, 10:03 PM

yeah so it should have set the time for you then

should be based on this, what package are you missing?

Similar Threads

Similar Threads

Similar Threads