Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: ajavibp on 2015/04/15, 16:03:13
-
The new Nvidia driver remove some devices to a legacy driver. Take care about upgrade because new legacy drivers is not in the repository right now.
-
Anyone knows a solution for somebody who went in that trap this morning? :-[
Managed to get my desktop back reinstalling noveau driver.
What can i do to get the old nvidia driver reinstalled?
Thanks
ghettoblaster
-
maybe you will find it there:
http://snapshot.debian.org/ (http://snapshot.debian.org/)
or apt-get install <package=version> if the package still exist in the repositories, but may u need to downgrade, or wait till it is fixed.
-
maybe you will find it there:
http://snapshot.debian.org/ (http://snapshot.debian.org/)
No, the needed driver is in debian/unstable.
It was my mistake, to put nvidia-driver 346.59-1.siduction.1 to fixes, i have forgotten, that it breaks the driver for users, who need 340 branch.
At the moment, we remove it from fixes.
-
Solved it by reinstalling following packages from /var/cache/apt/archives using dpkg:
nvidia-driver_340.76-1.siduction.1_amd64.deb
libegl1-nvidia_340.76-1.siduction.1_amd64.deb
libnvidia-eglcore_340.76-1.siduction.1_amd64.deb
xserver-xorg-video-nvidia_340.76-1.siduction.1_amd64.deb
nvidia-kernel-dkms_340.76-1.siduction.1_amd64.deb
nvidia-driver-bin_340.76-1.siduction.1_amd64.deb
nvidia-kernel-common_20141201+1_amd64.deb
nvidia-installer-cleanup_20141201+1_amd64.deb
nvidia-support_20141201+1_amd64.deb
nvidia-vdpau-driver_340.76-1.siduction.1_amd64.deb
nvidia-alternative_340.76-1.siduction.1_amd64.deb
-
Anyone knows a solution for somebody who went in that trap this morning? :-[
Managed to get my desktop back reinstalling noveau driver.
What can i do to get the old nvidia driver reinstalled?
Thanks
ghettoblaster
I've solved removing all nvidia packages and installing the driver from Nvidia web page. I hope the 340 legacy version will soon be in the repositories.
-
Anyone knows a solution for somebody who went in that trap this morning? :-[
Managed to get my desktop back reinstalling noveau driver.
What can i do to get the old nvidia driver reinstalled?
Thanks
ghettoblaster
I've solved removing all nvidia packages and installing the driver from Nvidia web page. I hope the 340 legacy version will soon be in the repositories.
Nice solution for breaking the system, especialy if one is using multiarch.
Pleas don't suggest such crap here to other users.
-
Anyone knows a solution for somebody who went in that trap this morning? :-[
Managed to get my desktop back reinstalling noveau driver.
What can i do to get the old nvidia driver reinstalled?
Thanks
ghettoblaster
I've solved removing all nvidia packages and installing the driver from Nvidia web page. I hope the 340 legacy version will soon be in the repositories.
Nice solution for breaking the system, especialy if one is using multiarch.
Pleas don't suggest such crap here to other users.
:o Sorry!
How can I solve in other way?
-
The eaysyest way, if there are not used apt-get remove/autoremove would be:
dpkg -i /var/cache/apt/archives/*340.76-1.siduction.1*
But after using the f***ing installer, the system is not clean for that.
And then, agaida is builing a nvidia-legacy-340-driver at the moment, if it is ready for working correct, he will upload it.
-
The new driver is uploaded to fixes right now - because i own no sufficient hardware i can't test it - but the driver installs just fine on my intel notebook - kernelmodules are build too without error 8)
one can install the transitional package nvidia-glx-legacy-340xx or install the driver with apt-get install nvidia-legacy-340xx-driver at wish. musca has tested it and says the driver works for him :)
-
First try to install the new driver:
apt-get install nvidia-legacy-340xx-driver libgl1-nvidia-legacy-340xx-glx-i386 libgles1-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgles1-nvidia-legacy-340xx is already the newest version.
libgles2-nvidia-legacy-340xx is already the newest version.
nvidia-legacy-340xx-driver is already the newest version.
libgl1-nvidia-legacy-340xx-glx-i386:i386 is already the newest version.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
libegl1-nvidia-legacy-340xx : Depends: libnvidia-legacy-340xx-eglcore (= 340.76-3) but it is not going to be installed
libgl1-nvidia-legacy-340xx-glx-i386:i386 : Depends: libgl1-nvidia-legacy-340xx-glx:i386 but it is not going to be installed
libgles1-nvidia-legacy-340xx : Depends: libnvidia-legacy-340xx-eglcore (= 340.76-3) but it is not going to be installed
libgles2-nvidia-legacy-340xx : Depends: libnvidia-legacy-340xx-eglcore (= 340.76-3) but it is not going to be installed
nvidia-legacy-340xx-driver : Depends: libgl1-nvidia-legacy-340xx-glx (= 340.76-3) but it is not going to be installed
Depends: nvidia-legacy-340xx-driver-bin (= 340.76-3) but it is not going to be installed
xserver-xorg-video-nvidia-legacy-340xx : Depends: libgl1-nvidia-legacy-340xx-glx (= 340.76-3) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
Using 'apt-get -f install':
The following extra packages will be installed:
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386 libnvidia-legacy-340xx-eglcore
nvidia-legacy-340xx-driver-bin
The following NEW packages will be installed:
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386 libnvidia-legacy-340xx-eglcore
nvidia-legacy-340xx-driver-bin
0 upgraded, 4 newly installed, 0 to remove and 10 not upgraded.
10 not fully installed or removed.
Need to get 0 B/22.2 MB of archives.
After this operation, 130 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
(Reading database ... 329749 files and directories currently installed.)
Preparing to unpack .../libnvidia-legacy-340xx-eglcore_340.76-3_amd64.deb ...
Unpacking libnvidia-legacy-340xx-eglcore:amd64 (340.76-3) ...
dpkg: error processing archive /var/cache/apt/archives/libnvidia-legacy-340xx-eglcore_340.76-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.340.76', which is also in package libnvidia-eglcore:amd64 340.76-1.siduction.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../libgl1-nvidia-legacy-340xx-glx_340.76-3_amd64.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:amd64 (340.76-3) ...
dpkg: error processing archive /var/cache/apt/archives/libgl1-nvidia-legacy-340xx-glx_340.76-3_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.76', which is also in package libgl1-nvidia-glx:amd64 340.76-1.siduction.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../nvidia-legacy-340xx-driver-bin_340.76-3_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver-bin (340.76-3) ...
dpkg: error processing archive /var/cache/apt/archives/nvidia-legacy-340xx-driver-bin_340.76-3_amd64.deb (--unpack):
trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-340.76-key-documentation', which is also in package nvidia-driver-bin 340.76-1.siduction.1
Preparing to unpack .../libgl1-nvidia-legacy-340xx-glx_340.76-3_i386.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:i386 (340.76-3) ...
dpkg: error processing archive /var/cache/apt/archives/libgl1-nvidia-legacy-340xx-glx_340.76-3_i386.deb (--unpack):
trying to overwrite '/usr/lib/i386-linux-gnu/tls/libnvidia-tls.so.340.76', which is also in package libgl1-nvidia-glx:i386 340.76-1.siduction.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libnvidia-legacy-340xx-eglcore_340.76-3_amd64.deb
/var/cache/apt/archives/libgl1-nvidia-legacy-340xx-glx_340.76-3_amd64.deb
/var/cache/apt/archives/nvidia-legacy-340xx-driver-bin_340.76-3_amd64.deb
/var/cache/apt/archives/libgl1-nvidia-legacy-340xx-glx_340.76-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
-
apt-get purge $(dpkg -l | awk '/nvidia/{ print $2 }')
apt-get install nvidia-legacy-340xx-driver
-
The new Nvidia driver remove some devices to a legacy driver. Take care about upgrade because new legacy drivers is not in the repository right now.
Which driver should I choose with this card?
Graphics: Card: NVIDIA GF119 [GeForce GT 610]
Display Server: X.Org 1.16.4 driver: nvidia Resolution: 1920x1200@59.95hz
GLX Renderer: GeForce GT 610/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 340.76
By now I have 340.76-1.siduction.1 which was in fixes... Is there a list with the supported/moved cards?
-
That did the trick:
apt-get purge $(dpkg -l | awk '/nvidia/{ print $2 }')
apt-get install nvidia-legacy-340xx-driver
Thank you very much towo!
8) Keep up the good work, siduction rocks!
apt-cache policy nvidia-legacy-340xx-driver
nvidia-legacy-340xx-driver:
Installed: 340.76-3
Candidate: 340.76-3
Version table:
*** 340.76-3 0
500 http://packages.siduction.org/fixes/ unstable/non-free amd64 Packages
100 /var/lib/dpkg/status
-
apt-get purge $(dpkg -l | awk '/nvidia/{ print $2 }')
apt-get install nvidia-legacy-340xx-driver
Thanks! It works like a charm, even with the new 4.0 kernel.
-
I have just done a new install followed by dist-upgrade and been hit by this. Everything is still at default settings, so debian unstable main contrib no-free and fixes are in the sources list but I get unable to locate package nvidia-legacy-340xx-driver.
Has it been removed?
-
I have just done a new install followed by dist-upgrade and been hit by this. Everything is still at default settings, so debian unstable main contrib no-free and fixes are in the sources list but I get unable to locate package nvidia-legacy-340xx-driver.
Has it been removed?
The 340.76-2 version is in 'extra' repository and 340.76-3 in 'fixed'.
-
Thanks
I also have extra (again default). could not read after 'and' ...
-
Thanks
I also have extra (again default). could not read after 'and' ...
fix it
-
...
Which driver should I choose with this card?
Graphics: Card: NVIDIA GF119 [GeForce GT 610]
Display Server: X.Org 1.16.4 driver: nvidia Resolution: 1920x1200@59.95hz
GLX Renderer: GeForce GT 610/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 340.76
By now I have 340.76-1.siduction.1 which was in fixes... Is there a list with the supported/moved cards?
According to the list I posted already (http://forum.siduction.org/index.php?topic=5449.msg44477#msg44477) the GeForce GT 610 seems to be supported by the newest nvidia driver (i.e. not legacy). But no guarantee ...
-
I still cannot locate the legacy drivers but I think my GTX650 TI should be normal driver anyway.
The normal driver (340.76-1) fails with:
Error! Bad return status for module build on kernel: 4.0.0-towo.1-siduction-amd64 (x86_64)
So probably best re-install and forget about dist-upgrade for a while!
-
I still cannot locate the legacy drivers but I think my GTX650 TI should be normal driver anyway.
The normal driver (340.76-1) fails with:
Error! Bad return status for module build on kernel: 4.0.0-towo.1-siduction-amd64 (x86_64)
So probably best re-install and forget about dist-upgrade for a while!
Use the driver from our fixes repo!
Alternatively you can use the newest driver from our extra/experimental repo.
-
Thanks to all that helped ... I have to admit a bit of a booboo!
Although the default sources file has fixes, extra, etc it does not have contrib and non-free on the end of the lines and I did not notice until now!
All working great now on 346.59 with the exception of extra artifacts around the (awful) text in QupZilla.
Many thanks.
-
hi billium,
perhaps two issues are mixed?
For the awfulness of fonts see http://forum.siduction.org/index.php?topic=5401.0
Fonts can be a site specific or desktop specific problem. Are you using LXQT? Which URL is it?
For the artifacts (driver issue?): no idea but you can try to upload a screenshot of the problem.
which vga card do you use?
greetings
musca
-
Sorted thanks musca .
-
apt-get purge $(dpkg -l | awk '/nvidia/{ print $2 }')
apt-get install nvidia-legacy-340xx-driver
Damit habe ich jetzt wenigstens wieder eine grafische Oberfläche mit der GeForce210 allerdings nur in der Auflösung 1024x768. Wie kann ich das wieder anpassen?
inxi -v3
System: Host: master Kernel: 4.0.0-towo.1-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
Desktop: Xfce 4.10.2 (Gtk 2.24.18) Distro: siduction - xfce
Machine: Mobo: Gigabyte model: P55-UD3 v: x.x Bios: Award v: F3 date: 07/31/2009
CPU: Quad core Intel Core i7 860 (-HT-MCP-) cache: 8192 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 22395
clock speeds: max: 2797 MHz 1: 2797 MHz 2: 2797 MHz 3: 2797 MHz 4: 2797 MHz 5: 2797 MHz
6: 2797 MHz 7: 2797 MHz 8: 2797 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
Display Server: X.org 1.16.4 drivers: fbdev,nouveau (unloaded: vesa)
tty size: 100x37 Advanced Data: N/A for root
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: de00 bus-ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:24:1d:dc:ab:74
Drives: HDD Total Size: 1500.3GB (38.1% used) ID-1: model: WDC_WD5000AADS
ID-2: model: SAMSUNG_HD103SJ
Info: Processes: 213 Uptime: 15 min Memory: 1527.6/7985.5MB
Init: systemd runlevel: 5 Gcc sys: 4.9.2 Client: Shell (bash 4.3.331) inxi: 2.2.18
Edit: Nach mehrmaligem Booten habe ich jetzt plötzlich wieder meine alte Auflösung. Manchmal geschehen noch Zeichen Wunder ... :)
-
So lange Du ständig die Ausgabe von inxi als Root hier postet, wird das sowieso nix.
Und ein dpkg -l | grep nvidia würde mich auch interessieren.
-
So lange Du ständig die Ausgabe von inxi als Root hier postet, wird das sowieso nix.
O.k. o.k. ich mache es nicht mehr wenn es stört .... ???
dpkg -l | grep nvidia
ii glx-alternative-nvidia 0.5.1 amd64 allows the selection of NVIDIA as GLX provider
ii libegl1-nvidia-legacy-340xx:amd64 340.76-4 amd64 NVIDIA binary EGL libraries (340xx legacy version)
ii libgl1-nvidia-legacy-340xx-glx:amd64 340.76-4 amd64 NVIDIA binary OpenGL libraries (340xx legacy version)
ii libnvidia-legacy-340xx-eglcore:amd64 340.76-4 amd64 NVIDIA binary EGL core libraries (340xx legacy version)
ii libnvidia-legacy-340xx-ml1:amd64 340.76-4 amd64 NVIDIA Management Library (NVML) runtime library
ii nvidia-alternative 346.59-1.siduction.1 amd64 allows the selection of NVIDIA as GLX provider
ii nvidia-installer-cleanup 20141201+1 amd64 cleanup after driver installation with the nvidia-installer
ii nvidia-kernel-common 20141201+1 amd64 NVIDIA binary kernel module support files
ii nvidia-legacy-340xx-alternative 340.76-4 amd64 allows the selection of NVIDIA as GLX provider
ii nvidia-legacy-340xx-driver 340.76-4 amd64 NVIDIA metapackage (340xx legacy version)
ii nvidia-legacy-340xx-driver-bin 340.76-4 amd64 NVIDIA driver support binaries (340xx legacy version)
ii nvidia-legacy-340xx-kernel-dkms 340.76-4 amd64 NVIDIA binary kernel module DKMS source (340xx legacy version)
ii nvidia-legacy-340xx-vdpau-driver:amd64 340.76-4 amd64 Video Decode and Presentation API for Unix - NVIDIA driver
ii nvidia-modprobe 340.46-1 amd64 utility to load NVIDIA kernel modules and create device nodes
ii nvidia-settings 340.46-2 amd64 tool for configuring the NVIDIA graphics driver
ii nvidia-support 20141201+1 amd64 NVIDIA binary graphics driver support files
ii xserver-xorg-video-nvidia-legacy-340xx 340.76-4 amd64 NVIDIA binary Xorg driver (340xx legacy version)
Aber wie schon erwähnt - im Moment stimmt wieder alles.
-
O.k. o.k. ich mache es nicht mehr wenn es stört ....

Das hat nix mit stören zu tun, sondern damit, das inxio als root keinen Sinn macht, weil wichtige Angaben fehlen!
Aber wie schon erwähnt - im Moment stimmt wieder alles.
Laut deinem unvollständigen inxi wurde aber nicht der Nvidia-Treiber benutzt!
-
Stimmt du hast Recht:
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
Display Server: X.Org 1.16.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 10.4.2 Direct Rendering: Yes
Darauf habe ich gar nicht geachtet. Ich war einfach nur froh dass es wieder funktioniert hat.
Es ist anscheinend der Nouveau Treiber aktiv der auch installiert ist wie ich jetzt festgestellt habe:
apt-cache policy xserver-xorg-video-nouveau
xserver-xorg-video-nouveau:
Installiert: 1:1.0.11-1
Installationskandidat: 1:1.0.11-1
Versionstabelle:
*** 1:1.0.11-1 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
Beide brauche ich ja wohl nicht. Ich denke mal der Nvidia-legacy Treiber ist die bessere Alternative was man so liest. Wie bekomme ich den aktiv?
-
update-alternatives --config glx
Da brauchts aber auch eine entsprechende xorg.config Schnipsel in /etc/X11/xorg.conf.d.
-
Danke für deine Hilfe.
Vom alten Treiber existiert noch eine 20-nvidia.conf mit folgendem Inhalt:
#
Section "Device"
Identifier "Device 0"
Driver "nvidia"
EndSection
Genügt das?
-
Ja, das reicht.
Und wenn Du denkst, das Alles so funktioniert, wie es soll, dann paste bitte mal
/var/log/Xorg.0.log
-
Klappt nicht so ganz.
update-alternatives --config glx
Es gibt nur eine Alternative in Link-Gruppe glx (die /usr/lib/glx bereitstellt): /usr/lib/mesa-diverted
Nichts zu konfigurieren.
Was habe ich vergessen?
-
apt-get purge nvidia-alternative
dpkg-reconfigure nvidia-legacy-340xx-alternative
-
Irgendwie ist der Wurm drin. Mit der Datei in /etc/X11/xorg.conf.d bekomme ich nur einen blinkenden Cursor. Ohne diese wenigstens ein grafisches System wenn auch nur wieder in der Auflösung 1024x768.
Und ein inxi als user sagt mir:
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
Display Server: X.Org 1.16.4 drivers: fbdev,nouveau (unloaded: vesa) Resolution: 1024x768@76.00hz
GLX Renderer: N/A GLX Version: N/A Direct Rendering: N/A
-
Dein alternatives-system ist kaputt!
nouveau muß normalerweise geblacklistet sein.
Und glx muß richtig umgeschaltet sein.
Und was haben denn die 2 Befehle von vorhin gezeigt?
AM besten wäre vermutlich ein
apt-get purge $(dpkg -l | awk '/nvidia/{ print $2}
apt-get install nvidia-legacy-340xx-driver nvidia-legacy-340xx-alternative
-
Habe alles nochmal neu installiert wie vorgeschlagen leider ohne Erfolg.
Die beiden Befehle ergaben folgendes:
apt-get purge nvidia-alternative
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paket »nvidia-alternative« ist nicht installiert, wird also auch nicht entfernt.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 59 nicht aktualisiert.
root@master:/home/peter#
root@master:/home/peter#
root@master:/home/peter# dpkg-reconfigure nvidia-legacy-340xx-alternative
Trigger für nvidia-legacy-340xx-alternative (340.76-4) werden verarbeitet ...
Trigger für glx-alternative-nvidia (0.5.1) werden verarbeitet ...
update-initramfs: deferring update (trigger activated)
Trigger für libc-bin (2.19-18) werden verarbeitet ...
Trigger für initramfs-tools (0.120) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.0.0-towo.1-siduction-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
Der Befehl
update-alternatives --config glx
gibt mir drei Auswahlmöglichkeiten:
update-alternatives --config glx
Es gibt 2 Auswahlmöglichkeiten für die Alternative glx (welche /usr/lib/glx bereitstellen).
Auswahl Pfad Priorität Status
------------------------------------------------------------
* 0 /usr/lib/nvidia 100 automatischer Modus
1 /usr/lib/mesa-diverted 5 manueller Modus
2 /usr/lib/nvidia 100 manueller Modus
Drücken Sie die Eingabetaste, um die aktuelle Wahl[*] beizubehalten,
oder geben Sie die Auswahlnummer ein:
Es ist allerdings egal was ich auswähle, mit dieser Datei in /etc/X11/xorg.conf.d gibt es kein grafisches System.
-
Ich will das /var/log/Xorg.0.log sehen, von so einem start, ggf. /var/log/Xorg.0.log.1 wenn Du wirde mit nouveau booten willst.
und die ausgabe von
dkms status
wäre nicht uninteressant.
Btw, der IRC wäre das bessere Medium in so einem Fall.
-
dkms status
nvidia-legacy-340xx, 340.76: added
vboxhost, 4.3.26, 3.19.1-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 3.19.2-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 3.19.3-towo.1-siduction-amd64, x86_64: installed
Habe die beiden Log-Dateien umbenannt sonst kann ich sie nicht anhängen.
Bin im Channel falls du mir so besser helfen kannst.
-
dkms status
nvidia-legacy-340xx, 340.76, 4.0.0-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 3.19.1-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 3.19.2-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 3.19.3-towo.1-siduction-amd64, x86_64: installed
vboxhost, 4.3.26, 4.0.0-towo.1-siduction-amd64, x86_64: installed