Wayfire not booting with proprietary nvidia drivers (1080ti)

I tried to run the bootable USB, and selected the proprietary nvidia driver - I have a 1080ti. The booting process ended up in a black screen, and I couldn't access tty. There would be instances where I could see the terminal when trying to access the tty, but this would immidiately go back to being black.

I can boot with the opensource driver. This PC runs just fine with Garuda Dragonized, proprietary driver.

I am a little confused considering that the maintainer of Wayfire is certain that I should be able to boot into Wayfire with a 1080ti provided the version of Wayfire is above ~0.40.

Has anyone booted with proprietary nvidia drivers on Garuda Wayfire? Anyone with a 1000-series nvidia card perhaps? BIOS settings?

Wayfire is based on wayland, which doesn't really get along well with Nvidia. So you cannot compare it with KDE, at least the standard X11 install.

5 Likes

Did you miss the big pop up that told you to post some information or you would not receive help?

1 Like

Did you miss the part where I explicitely stated that I cannot get into tty. Have the courtesy to spend at least half your attention on the issue, rather than blindly attacking my effort.

I know, the statement was to point out that I am able to use other distributions on the same workstation. Providing as much information as possible.

And no, you are wrong on Wayland not working with Nvidia there are several users of wayfire on the wayfire repository that are on single nvidia-gpu rigs.

Presumably you can get into the live session, where you could have grabbed your garuda-inxi to provide more information for the forum helpers to review.

I encourage you to edit your post and remove the insult. I understand you may be frustrated, but this is bad form.

The distribution doesn't matter as much as the display server if you are using Nvidia hardware. If you really want to use Wayland, get a different graphics card.

4 Likes

This really doesn't help me. But thank you.

I will go out on a limb, and say that garuda-inxi won't help one bit on debugging the issue, we need to find a way get me tty or someone with experience needs to tell me exactly what to do. This opinon on top of the ignorance got me frustrated. Please understand that I am really tired of these condescending replyes on Arch communities, especially when it is founded on ignorance. The mod bot is saying I can edit the flagged post, I can't.

Opinion: Pointing out someones lack of attention, and thereby lack of respective intellegence (using the i-word) shouldn't be flagged; vote me down all you want. This is literally the definition of wasting peoples time. I'll admit that we were both offenders. And, I am sorry.

Anyway, here is what you guys really want, it won't help (prove me wrong, if you want to):

System:
Kernel: 5.17.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/vmlinuz-linux-zen
root=UUID=271f832d-09f2-4b21-a369-ae6519f69c12 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3=1 resume=UUID=bef431c9-3bd8-4fcc-9de0-55d0e0864379
systemd.unified_cgroup_hierarchy=1
Desktop: KDE Plasma v: 5.24.4 tk: Qt v: 5.15.3 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 5603
date: 07/28/2020
CPU:
Info: model: AMD Ryzen 7 1700 bits: 64 type: MT MCP arch: Zen
family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001138
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 2704 high: 3053 min/max: 1550/3000 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 2851 2: 2563
3: 2791 4: 2788 5: 2545 6: 2726 7: 2982 8: 2653 9: 2574 10: 2569 11: 2559
12: 2565 13: 3053 14: 2571 15: 2915 16: 2563 bogomips: 95808
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: eVga.com.
driver: nvidia v: 510.54 alternate: nouveau,nvidia_drm pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 07:00.0 chip-ID: 10de:1b06 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 109 s-size: 802x333mm (31.57x13.11")
s-diag: 868mm (34.19")
Monitor-1: DP-2 res: 3440x1440 dpi: 109 size: 800x330mm (31.5x12.99")
diag: 865mm (34.07") modes: N/A
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 510.54 direct render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.1
chip-ID: 10de:10ef class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.3
chip-ID: 1022:1457 class-ID: 0403
Device-3: SAVITECH JDS Labs Element DAC type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-3:2 chip-ID: 262a:1048
class-ID: 0102
Sound Server-1: ALSA v: k5.17.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.49 running: yes
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
IF-ID-2: virbr0 state: down mac: <filter>
RAID:
Supported mdraid levels: raid0
Device-1: md0 maj-min: 9:0 type: mdraid level: raid-0 status: active
size: 849.75 GiB
Info: report: N/A blocks: 891025408 chunk-size: 512k super-blocks: 1.2
Components: Online:
0: sdb1 maj-min: 8:17 size: 425 GiB
1: sdc1 maj-min: 8:33 size: 425 GiB
Drives:
Local Storage: total: 2.54 TiB used: 943.8 GiB (36.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 950 PRO 512GB size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B0QBXX7 temp: 39.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:9 vendor: Samsung model: SSD 960 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 3B7QCXE7
temp: 26.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT525MX300SSD1
size: 489.05 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: R060 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q scheme: GPT
Partition:
ID-1: / raw-size: 121.64 GiB size: 121.64 GiB (100.00%)
used: 98.41 GiB (80.9%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot raw-size: 400 MiB size: 400 MiB (100.00%)
used: 226.1 MiB (56.5%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:8
ID-3: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.5 MiB (26.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /home raw-size: 250.86 GiB size: 250.86 GiB (100.00%)
used: 37.3 GiB (14.9%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-5: /var/log raw-size: 121.64 GiB size: 121.64 GiB (100.00%)
used: 98.41 GiB (80.9%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-6: /var/tmp raw-size: 121.64 GiB size: 121.64 GiB (100.00%)
used: 98.41 GiB (80.9%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: swap-2 type: zram size: 15.62 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.0 C mobo: 32.0 C gpu: nvidia temp: 52 C
Fan Speeds (RPM): cpu: 157 fan-2: 128 fan-3: 145 fan-4: 158 fan-6: 135
gpu: nvidia fan: 31%
Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.25
Info:
Processes: 516 Uptime: 5m wakeups: 0 Memory: 15.62 GiB
used: 5.26 GiB (33.7%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 2242 lib: 543 Shell: fish
v: 3.4.1 running-in: konsole inxi: 3.3.14
Garuda (2.5.6-2):
System install date:     2021-02-16
Last full system update: 2022-04-02 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Timeshift
Failed units:            bluetooth-autoconnect.service

Irrelevant.

The garuda-inxi is a requirement on technical help requests on the Garuda forum. You have been a forum member for quite some time, so you should be well aware of this expectation.

Do not call other users "idiots" in the future on our forum. This is considered a personal attack and is unacceptable on the Garuda forum. That is why your post was flagged by a community member.

Good luck with your issue.

5 Likes

Afaik wayfire currently does not support nvidia

May be the -git does
But you will need to compile it with both wlroots-git.

We provide wayfire version upto a commit that can be built with wlroots version in arch repo

6 Likes

Your compliance to forum posting rules--and your willingness to do so--go a long way here, in "Arch communities," and any forum I've been in going back a long ways.

I couldn't begin to list the large number of experienced Garuda users & forum members (including a number of Archers) willing and able to help anyone here, and not just newcomers. Whether your intelligence feels insulted or not, you are getting off on the wrong foot in this forum.

Nevertheless, welcome to Garuda Linux! May your days be filled with really cool shit. :slight_smile:

3 Likes

You guys are extremely imperative, it is offputting. No empathy provided whatsoever; shame on you.

Obviously I was reporting a bug, and asking for any insight on upcoming nvidia support for Garuda Wayfire.

Some people here are actually willing to help even if I don't comply with the rules all the way, and, fyi, I did give all the relevant information for the issue. I will call it out when people make a dumb comment, don't help if you don't want to; I don't need your help. Please take your moral imperative elsewhere.

We can close this discussion (if you want). @librewish was kind and actually did something productive with his free time contrary to everybody else.

How stupid, it's always the others' fault and I'm an angel :smiley:

So, if you can boot from open source, you can post your garuda-inxi. Didn't find any attack here. Only in your posts.

2 Likes

Uhhh... nope.

If you continue calling others "idiots" or similar pejorative terms in the future you can expect to be disciplined for that by a forum moderator.

You've been flagged and warned several times now, so don't plan on continuing down this path without there being repercussions.

Done.

3 Likes