No, the driver is installed and running, check you get output from nvidia-smi
Have you tried switching to Wayland and check the inxi -GSaz output?
You need to see a) DVI-D-I is connected to the Nvidia card and b) the nvidia gpu in use.
Also check your system BIOS, is the Grapics set to auto, if so try switching to the Nvidia GPU.
Switched to wayland:
The inxi -GSaz output has changed. The GeForce graphic card is listed now as Device-2. And DVI-D-1 is active.
System:
Kernel: 7.1.4-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: initrd=\opensuse-tumbleweed\7.1.4-1-default\initrd-969aada52a60b07eb558984ef561fd2a419a4e3c
root=UUID=e37cc230-6a91-43bc-a1d5-55ac93f96eca splash=silent
resume=/dev/disk/by-uuid/151c4fb2-6c22-4907-9800-69df79ddc063
mitigations=auto quiet security=selinux selinux=1
rd.driver.blacklist=nouveau
Desktop: KDE Plasma v: 6.7.3 tk: Qt v: N/A info: frameworks v: 6.28.0
wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
Tumbleweed 20260729
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Lenovo
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0380
Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI
driver: nvidia v: 580.159.03 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: legacy-active (EOL~2028-09-xx) arch: Pascal
code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: DVI-D-1 empty: DP-4, DP-5, DP-6, HDMI-A-4 bus-ID: 01:00.0
chip-ID: 10de:1c03 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: vesa alternate: fbdev,intel,nouveau,nv dri: iris
gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DVI-D-1 model: Acer V223W serial: <filter> built: 2012 res:
mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 640x480
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 580.159.03
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1060
6GB/PCIe/SSE2 memory: 5.86 GiB display-ID: :1.0
API: Vulkan v: 1.4.350 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1060 6GB driver: nvidia v: 580.159.03 device-ID: 10de:1c03
surfaces: N/A device: 1 type: integrated-gpu name: Intel UHD Graphics 630
(CFL GT2) driver: mesa intel v: 26.1.5 device-ID: 8086:3e92 surfaces: N/A
device: 2 type: cpu name: llvmpipe (LLVM 22.1.8 256 bits)
driver: mesa llvmpipe v: 26.1.5 (LLVM 22.1.8) device-ID: 10005:0000
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandrAnd wine>Astrolog now starts without the bad messages from before.
Probaly this solved the problem.
Thank you to both of you. Would would I be without the help in this forum!
It’s weird. It worked yesterday. Even when I was on my Laptop in the evening, I switched to wayland there, and it worked there, too.
But now I’m again on my PC, logged in on wayland, and the old problem occurs. The same warnings when I start Astrolog via wine. The same behaviour.
Although inxi -GSaz shows the same enhanced output as yesterday with the GeFOrce card listed as device-2. Or do you see any other difference?
System:
Kernel: 7.1.4-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.1.1 clocksource: tsc
avail: hpet,acpi_pm
parameters: initrd=\opensuse-tumbleweed\7.1.4-1-default\initrd-969aada52a60b07eb558984ef561fd2a419a4e3c
root=UUID=e37cc230-6a91-43bc-a1d5-55ac93f96eca splash=silent
resume=/dev/disk/by-uuid/151c4fb2-6c22-4907-9800-69df79ddc063 mitigations=auto quiet
security=selinux selinux=1 rd.driver.blacklist=nouveau
Console: pty pts/1 DM: SDDM Distro: openSUSE Tumbleweed 20260729
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Lenovo driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: none empty: DP-1, DP-2, DP-3,
HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0380
Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI driver: nvidia
v: 580.159.03 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: legacy-active (EOL~2028-09-xx) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: DVI-D-1 empty: DP-4, DP-5, DP-6, HDMI-A-4 bus-ID: 01:00.0 chip-ID: 10de:1c03
class-ID: 0300
Display: unspecified server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia unloaded: vesa
alternate: fbdev,intel,nouveau,nv dri: iris gpu: nvidia,nvidia-nvswitch tty: 108x28
Monitor-1: DVI-D-1 model: Acer V223W serial: <filter> built: 2012 res: 1680x1050 dpi: 90
gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050
min: 640x480
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: iris device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia
inactive: wayland,x11,device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: mesa v: 26.1.5 note: console (EGL sourced)
renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2, Mesa Intel UHD Graphics 630 (CFL GT2),
llvmpipe (LLVM 22.1.8 256 bits)
API: Vulkan v: 1.4.350 layers: 3 device: 0 type: discrete-gpu name: NVIDIA GeForce GTX 1060
6GB driver: nvidia v: 580.159.03 device-ID: 10de:1c03 surfaces: N/A device: 1
type: integrated-gpu name: Intel UHD Graphics 630 (CFL GT2) driver: mesa intel v: 26.1.5
device-ID: 8086:3e92 surfaces: N/A device: 2 type: cpu name: llvmpipe (LLVM 22.1.8 256 bits)
driver: mesa llvmpipe v: 26.1.5 (LLVM 22.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
gpu: nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Actually I would prefer to get it running on X11, instead of wayland, because some things behave differently with wayland. But first of all I would be happy if it works at all.
On the Laptop, though, it everything seems to be okay with wine and astrolog on wayland.
OK, after understanding the difference between X11 and wayland, I must admit that it’s obviously better to stick with wayland. So I will adapt.
Thank you for the likes. But the problem isn’t solved yet, as described in my second-to-last post.
The only other solution I would suggest is Flatpak and bottles…
This is the 64bit version running on Tumbleweed (GNOME/Wayland)…
But it worked already for a few hours. Why doesn’t it work now?
And how did you install Astrolog with flatpak? Is it possible to do this with a local file?
The sources come in a zip file and simply need to be extracted. So why should it be necessary to use a installer like flatpak?
Or do you mean installing wine with flatpak, not astrolog?
@Jaizkibel Yes, I use the flatpak com.usebottles.bottles installed as my user, then used the 64bit version of Astrolog.
Okay, I did flatpak install com.usebottles.bottles. Then some file ware installed, among others 2 winehq files. After that I came to the idea to remove the wine packages that I once installed with zypper, to avoid a double. Maybe I should have done this beforehand. But now ther’s no wine command anymore. How do I use the bottle now to start Astrolog?
Ah, I found it in the start menu. Let’s see if I can dig through it.
There should be an icon to run bottles, create a new bottle use the sys-wine-11. I then copied the extracted Astrolog log folder down into ~/.var/app/com.usebottles.bottles/data/bottles/bottles/Astrolog/drive_c/Program Files directory.
Then you can create a shortcut to it, then add as a desktop app in the menu system (.local/share/applications) to run from there.
For a start it seems to work. I need to watch it on a long-term how it will behave.
This appears a bit complicated to me. How to create a shortcut? I can right-click on the window title. Then “More Actions” >> “Set Window Shortcut”. Is this what you mean? It asks for a key or a key combination.
In the Program section “+ Add Shortcuts”
Browse to the location you have the ast80win64 folder, then select Astrolog.exe and add, then in the dropdown select add desktop entry etc…
Cool. It looks good now.
If there are no further answers from me, you can consider this as solved.
Thanks again for your help.
