Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: clubex on 2018/12/24, 12:53:19
-
I've not done any investigating for the moment (It's Xmas eve and no time) but reverting to the previous kernel was a temp solution for me.
inxi -a
CPU: Quad Core AMD Phenom II X4 945 (-MCP-) speed/min/max: 800/800/3000 MHz
Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 Up: 15m Mem: 1488.6/7980.7 MiB (18.7%)
Storage: 465.76 GiB (47.7% used) Procs: 186 Shell: bash 4.4.23 inxi: 3.0.29
-
You forgot an important part (video), and the output of the failed modules
06:54:35 AM-Mon Dec 24-[piper@x1] $ inxi -c0SGx
System: Host: x1 Kernel: 4.20.0-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: KDE Plasma 5.14.3
Distro: siduction 18.3.0 Paint It Black - kde - (201812140049) base: Debian GNU/Linux buster/sid
Graphics: Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: eVga.com. driver: nvidia v: 415.25 bus ID: 01:00.0
Display: x11 server: X.Org 1.20.3 driver: nvidia unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 415.25 direct render: Yes
06:59:06 AM-Mon Dec 24-[piper@x1] $
-
I cannot confirm here. 4.20 starts and loads all neccessary modules flawlessly...
Greetings
df8oe
-
kernel 4.20 is not working for me
peter@peter-mate:~$ inxi -c0SGx
System:
Host: peter-mate Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64
compiler: gcc v: 8.2.0 Desktop: MATE 1.20.3
Distro: siduction 18.3.0 Patience - mate - (201811041851)
base: Debian GNU/Linux buster/sid
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0
Device-2: NVIDIA GM107 [GeForce GTX 750] vendor: ZOTAC driver: nvidia v: 390.87
bus ID: 01:00.0
Display: x11 server: X.Org 1.20.3 driver: modesetting,nvidia unloaded: nouveau,vesa
resolution: 1440x900~60Hz
OpenGL: renderer: GeForce GTX 750/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87
direct render: Yes
Selecting previously unselected package linux-headers-4.20.0-towo.1-siduction-amd64.
(Reading database ... 248349 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.20.0-towo.1-siduction-amd64_4.20-1_amd64.deb ...
Unpacking linux-headers-4.20.0-towo.1-siduction-amd64 (4.20-1) ...
Selecting previously unselected package linux-image-4.20.0-towo.1-siduction-amd64.
Preparing to unpack .../linux-image-4.20.0-towo.1-siduction-amd64_4.20-1_amd64.deb ...
Unpacking linux-image-4.20.0-towo.1-siduction-amd64 (4.20-1) ...
Preparing to unpack .../linux-headers-siduction-amd64_4.20-1_amd64.deb ...
Unpacking linux-headers-siduction-amd64 (4.20-1) over (4.19-33) ...
Preparing to unpack .../linux-image-siduction-amd64_4.20-1_amd64.deb ...
Unpacking linux-image-siduction-amd64 (4.20-1) over (4.19-33) ...
Setting up linux-headers-4.20.0-towo.1-siduction-amd64 (4.20-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.20.0-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/390.87/build/make.log for more information.
Setting up linux-image-4.20.0-towo.1-siduction-amd64 (4.20-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.12-towo.1-siduction-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.12-towo.1-siduction-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.20.0-towo.1-siduction-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.20.0-towo.1-siduction-amd64
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.20.0-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/390.87/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-towo.1-siduction-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/patience/theme.txt
Found linux image: /boot/vmlinuz-4.20.0-towo.1-siduction-amd64
Found initrd image: /boot/initrd.img-4.20.0-towo.1-siduction-amd64
Found linux image: /boot/vmlinuz-4.19.12-towo.1-siduction-amd64
Found initrd image: /boot/initrd.img-4.19.12-towo.1-siduction-amd64
Found linux image: /boot/vmlinuz-4.19.11-towo.2-siduction-amd64
Found initrd image: /boot/initrd.img-4.19.11-towo.2-siduction-amd64
hope the information helps
-
kernel 4.20 is not working for me
What does that mean in concrete terms? Because of nvidia, or rather this version of nvidia?
You have a GF GTX750, take nouveau!
4.20 starts and loads all neccessary modules flawlessly...
Same here (GF710, nouveau).
-
I have the same issue, looks like when I take a look at the /var/lib/dkms/nvidia-current/390.87/build/make.log I see the following error at the start of the file
DKMS make.log for nvidia-current-390.87 for kernel 4.20.0-towo.1-siduction-amd64 (x86_64)
Mon Dec 24 12:42:28 EST 2018
make V=1 -C /lib/modules/4.20.0-towo.1-siduction-amd64/build M=/var/lib/dkms/nvidia-curr$
make[1]: Entering directory '/usr/src/linux-headers-4.20.0-towo.1-siduction-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing."$
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
and at the bottom of the make.log
make[1]: *** [Makefile:1578: _module_/var/lib/dkms/nvidia-current/390.87/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.20.0-towo.1-siduction-amd64'
make: *** [Makefile:79: modules] Error 2
-
For supported Nvidia GPUs you could install nvidia 415.25 (http://rglinuxtech.com/?p=2464), if you have to...
-
I have the same issue, looks like when I take a look at the /var/lib/dkms/nvidia-current/390.87/build/make.log I see the following error ...
Yes, it is the same with driver ver. 396.54. It appears we have to go with ver 415.23 or .25, to use kernel 4.20.
-
~# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● clamav-daemon.service loaded failed failed Clam AntiVirus userspace daemon
● systemd-modules-load.service loaded failed failed Load Kernel Modules
● virtualbox.service loaded failed failed LSB: VirtualBox Linux kernel module
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
3 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
so systemd-modules-load was loaded but failed
~# systemctl status systemd-modules-load
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-12-24 20:28:29 GMT; 2min 46s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 702 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 702 (code=exited, status=1/FAILURE)
Dec 24 20:28:29 westfield systemd-modules-load[702]: modprobe: ERROR: could not insert 'nvidia': Operation not permitted
Dec 24 20:28:29 westfield systemd-modules-load[702]: modprobe: FATAL: Module nvidia-current-modeset not found in directory /lib/modules/4.20.0-towo.1-siduction-amd64
Dec 24 20:28:29 westfield systemd-modules-load[702]: modprobe: ERROR: ../libkmod/libkmod-module.c:979 command_do() Error running install command for nvidia_modeset
Dec 24 20:28:29 westfield systemd-modules-load[702]: modprobe: ERROR: could not insert 'nvidia_modeset': Operation not permitted
Dec 24 20:28:29 westfield systemd-modules-load[702]: modprobe: FATAL: Module nvidia-current-drm not found in directory /lib/modules/4.20.0-towo.1-siduction-amd64
Dec 24 20:28:29 westfield systemd-modules-load[702]: Error running install command for nvidia_drm
Dec 24 20:28:29 westfield systemd-modules-load[702]: Failed to insert 'nvidia_drm': Operation not permitted
Dec 24 20:28:29 westfield systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 20:28:29 westfield systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Dec 24 20:28:29 westfield systemd[1]: Failed to start Load Kernel Modules.
And the modules are indeed missing. So I'm presuming that nvidia hasn't yet caught up with kernal 4.20.0
It's a long time since I needed the advantages of the nvidia kernel so, for me, it's been easily solved by going "back" to nouveau.
ps please excuse any typos as I'm a little drunk. Happy Xmas all.
-
I have the same issue, looks like when I take a look at the /var/lib/dkms/nvidia-current/390.87/build/make.log I see the following error ...
Yes, it is the same with driver ver. 396.54. It appears we have to go with ver 415.23 or .25, to use kernel 4.20.
I was hoping for new drivers for better DXVK and steamplay options but ... I dont think either of those are in experimental yet.
-
towo:Defiant> LANG=C apt policy nvidia-driver
nvidia-driver:
Installed: (none)
Candidate: 415.25-0.siduction.2
Version table:
415.25-0.siduction.2 600
600 http://packages.siduction.org/extra experimental/non-free amd64 Packages
410.78-2 300
300 http://deb.debian.org/debian experimental/non-free amd64 Packages
390.87-5 500
500 http://deb.debian.org/debian unstable/non-free amd64 Packages
500 http://incoming.debian.org/debian-buildd buildd-unstable/non-free amd64 Packages
390.87-4 500
500 http://deb.debian.org/debian testing/non-free amd64 Packages
-
Is it possible that nvidia kicked off support for many graphic cards like Quadro 4000 in new 415.25-0 driver?
-
Quadro 4000 is GF100 (Fermi) based as well as GeForce 400 series. The last driver version is 396.18.
Purge nvidia and use nouveau!
-
df8oe, da Du ja Deutscher bist...kann natürlich sein, daß irgendwann irgendwer den 396er oder 340er patcht...bis zum nächsten Kernel oder xorg. Ich jedenfalls bin das ewige Hinterhergepatche bei/für nvidia leid, fahre nur noch nouveau (GF710). Aktueller Kernel ist mir weit wichtiger (ich spiele nicht).
Eine höhere GPU-Temperatur und höheren Verbrauch solltest Du freilich im Auge behalten, zumindest bei einem Notebook.
-
towo:Defiant> LANG=C apt policy nvidia-driver
nvidia-driver:
Installed: (none)
Candidate: 415.25-0.siduction.2
.
.
.
Vielen Dank, towo!
-
Hmm, ascheinend stehe ich gerade auf dem Schlauch.
Kann mal jmand mir Dummerchen auf die Schnelle verraten wie ich den 415er für meine große Kiste installiert kriege?
Er wird zwar erkannt, die sources.lists stimmen wohl auch aber ich kriege ihn nicht installiert.
Grüße
Reiner
-
towo:Defiant> LANG=C apt policy nvidia-driver
nvidia-driver:
Installed: (none)
Candidate: 415.25-0.siduction.2
Version table:
415.25-0.siduction.2 600
600 http://packages.siduction.org/extra experimental/non-free amd64 Packages
410.78-2 300
300 http://deb.debian.org/debian experimental/non-free amd64 Packages
390.87-5 500
500 http://deb.debian.org/debian unstable/non-free amd64 Packages
500 http://incoming.debian.org/debian-buildd buildd-unstable/non-free amd64 Packages
390.87-4 500
500 http://deb.debian.org/debian testing/non-free amd64 Packages
thank you towo, I added the repo, and and did an apt install nvidia-driver -t experimental, and that seems to have done the trick.
-
I also do not use nvidia-drivers (because I do not have Nvidia graphics) but some of my friends do. And they all are now kicked off because "planned obsolescence" by Nvidia kicked off their GPU from support.
They all do not play but they use 3D functions in CAD applications. I do not have looked at nouveau for 2...3 years and I will test if nouveau does support 3D functionability that e.g. freecad and KiCad do use. If so: go to shredder nvidia-drivers! If not: go to shredder Nvidia graphics with "builtin software planned obsolescence" and let a better hardware provider come in!
-
Ok, now here it is installing too.
Thanks @terroreek, I had forgot the "t"
regards
Reiner
-
@axt:
nouveau ist absolut unbenutzbar. So gut wie alle Anwendungen stürzen nach kurzer Zeit ab mit Fehlern im Log wie diesen:
nouveau: kernel rejected pushbuf: Datei oder Verzeichnis nicht gefunden
nouveau: ch41: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch41: buf 00000000 00000002 00000004 00000004 00000000
kontact: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Zusicherung »kref« nicht erfüllt.
Received signal 6
#0 0x7f338849d36e <unknown>
#1 0x7f338849d480 <unknown>
#2 0x7f338849dab7 <unknown>
#3 0x7f338fe048e0 <unknown>
#4 0x7f338fe0485b gsignal
#5 0x7f338fdef535 abort
#6 0x7f338fdef40f <unknown>
#7 0x7f338fdfd0a2 __assert_fail
#8 0x7f3372ada59f nouveau_pushbuf_data
#9 0x7f3372ada503 nouveau_pushbuf_data
#10 0x7f3372ada62f <unknown>
#11 0x7f3372adaa7f <unknown>
#12 0x7f3372adb670 nouveau_pushbuf_kick
#13 0x7f3371b37906 <unknown>
#14 0x7f3371c7cbdf <unknown>
#15 0x7f3371802210 <unknown>
#16 0x7f3372aab993 <unknown>
#17 0x7f33795d8156 <unknown>
#18 0x7f339077c78b QOpenGLContext::swapBuffers()
#19 0x7f3390a0e1b4 QPlatformBackingStore::composeAndFlush()
#20 0x7f337946dec4 <unknown>
#21 0x7f3390d1aae3 <unknown>
#22 0x7f3390d1c57b <unknown>
#23 0x7f3390d1d882 <unknown>
#24 0x7f3390d1da19 <unknown>
#25 0x7f3390d34ae5 QWidgetPrivate::syncBackingStore()
#26 0x7f3390d4c8f8 QWidget::event()
#27 0x7f3390e52ed4 QMainWindow::event()
#28 0x7f339146f55b KMainWindow::event()
#29 0x7f33914b8585 KXmlGuiWindow::event()
#30 0x7f3390d0e491 QApplicationPrivate::notify_helper()
#31 0x7f3390d15ad0 QApplication::notify()
#32 0x7f3390398039 QCoreApplication::notifyInternal2()
#33 0x7f339039b02b QCoreApplicationPrivate::sendPostedEvents()
#34 0x7f33903ea6e3 <unknown>
#35 0x7f338df99c3e g_main_context_dispatch
#36 0x7f338df99ed8 <unknown>
#37 0x7f338df99f6c g_main_context_iteration
#38 0x7f33903e9d13 QEventDispatcherGlib::processEvents()
#39 0x7f33794df851 <unknown>
#40 0x7f3390396d0b QEventLoop::exec()
#41 0x7f339039ee82 QCoreApplication::exec()
#42 0x55628b8bd738 <unknown>
#43 0x7f338fdf109b __libc_start_main
#44 0x55628b8bde4a _start
r8: 0000000000000000 r9: 00007fffe3f6d8e0 r10: 0000000000000008 r11: 0000000000000246
r12: 00007f3372add052 r13: 00007f3372add068 r14: 00000000000002d3 r15: 0000000000000003
di: 0000000000000002 si: 00007fffe3f6d8e0 bp: 00007f3372b1d1d2 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f338fe0485b sp: 00007fffe3f6d8e0
ip: 00007f338fe0485b efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
...also bleibt für meine Freunde nur auf den neuesten Kernel zu verzichten. Oder die Patchorgie zu starten. Oder sich nach einer Grafikkarte mit 3D-Funktion, die NICHT von Nvidia kommt und die mit einem quelloffenen Treiber läuft umzusehen...
-
Eine Frage:
Weiß jemand ob das nvidia Problem auch den legacy Treiber (aktuell 340.107-3) betrifft?
-
So gut wie alle Anwendungen stürzen nach kurzer Zeit ab
nouveau kann durch Nvidias Blockadepolitik gar nicht sämtliche in Hardware mögliche Funktionen nutzen. D.h. aber nicht, es sei "absolut unbenutzbar".
Wer entsprechendes braucht, bspw. OGL für CAD, ist nach meinem Dafürhalten bei siduction mit ununterbrochen nötigen Anpassungen nicht wirklich richtig. Allein bei den UU-ntoten habe ich über 11 Jahre nvidia hochgehalten, die wissen aber auch nichts von aktuellen Kerneln (so einzelne nicht gerade Mainline verwenden o.ä.) oder überhaupt aktueller Software.
Für die Programme, die diesbzgl. Probleme bereiten (können), habe ich für mich einen Workaround (https://axebase.net/blog/2018/12/09/falkon-chromium-freezes-glitches/) gefunden, zuerst durchgeführt auf dem von mir im Laden genutzten Notebook mit siduction und - 3x darfst Du raten - einer von Dir indirekt angesprochenen Radeon. Ohne den ist Falkon sofort nach Start eingefroren.
-
Richtig - das geht. Nur laufen dann die CAD-Programme nicht mehr, da sie genau diese Funktionen brauchen.
Und bei den betreffende Leuten ist sehr viel Software auf OGL angewiesen.
Ich habe hier eine Intel-Grafik - die benötigt weder einen closed-source-Treiber noch ist OGL instabil...
-
harley-peter, man könnte ja mal in ein Changelog sehen oder es schlicht selbst ausprobieren.
Nachdem, was ich seit Bestehen von nvidia-(legacy-)340 ständig und insbesondere in den letzten anderthalb Jahren selbst erlebt habe, sage ich einfach mal nein (das ist ja der Grund für mich für eine 710er mit nouveau gewesen).
-
Ich sage nur, scheiß auf Nvidia.
towo:Defiant> inxi -G
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu
v: kernel
Display: x11 server: X.Org 1.20.3 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0 4.20.0-towo.1-siduction-amd64 LLVM 7.0.1)
v: 4.5 Mesa 19.0.0-devel
Wie ruhig und entspannt doch das Leben sein kann.
-
@towo: full ack.
-
Now we have successfully adopted the thread in German. I'll summarize in English:
- nvidia 415.25-0.siduction.2 runs with Kernel 4.20
- nvidia 340.x doesn't know about anything yet.
- Nvidia is evil.
- nouveau, some say so, others say so.
- towo has given up and bought a Radeon.
:-D
-
Maybe this don't belong here but subject is failed kernel modules. Anyway I don't get virtual box to work on this kernel.
System:
Host: vilde-T420 Kernel: 4.20.0-towo.1-siduction-amd64 x86_64 bits: 64
Desktop: Xfce 4.12.4
Distro: siduction 18.1.0 Patience - xfce - (201712310104)
Machine:
Type: Laptop System: LENOVO product: 4180G73 v: ThinkPad T420
serial: <filter>
Mobo: LENOVO model: 4180G73 serial: <filter> UEFI: LENOVO
v: 83ET78WW (1.48 ) date: 01/21/2016
Battery:
ID-1: BAT0 charge: 23.6 Wh condition: 23.9/56.2 Wh (43%)
ID-2: BAT1 charge: 61.0 Wh condition: 61.8/93.2 Wh (66%)
CPU:
Topology: Dual Core model: Intel Core i5-2540M bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 797 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 797 2: 797
3: 797 4: 797
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
Display: x11 server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.1
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Sound Server: ALSA v: k4.20.0-towo.1-siduction-amd64
Network:
Device-1: Intel 82579LM Gigabit Network driver: e1000e
IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
IF: wlp3s0 state: down mac: <filter>
IF-ID-1: wwp0s29u1u4i6 state: down mac: <filter>
Drives:
Local Storage: total: 260.84 GiB used: 141.24 GiB (54.1%)
ID-1: /dev/sda vendor: Intel model: SSDSC2BW120H6 size: 111.79 GiB
ID-2: /dev/sdb vendor: Intel model: SSDSA2BW160G3L size: 149.05 GiB
Partition:
ID-1: / size: 85.40 GiB used: 69.31 GiB (81.2%) fs: ext4 dev: /dev/sda4
ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): cpu: 3221
Info:
Processes: 167 Uptime: 7m Memory: 7.68 GiB used: 880.4 MiB (11.2%)
Shell: bash inxi: 3.0.29
-
vilde, purge virtualbox* and take the original in current version 6.0.0 (https://download.virtualbox.org/virtualbox/6.0.0/) (or 6.0.1 (https://www.virtualbox.org/wiki/Testbuilds) testbuild like me)!
Changelog 6.0.x (https://www.virtualbox.org/wiki/Changelog-6.0) ("Linux hosts: support Linux 4.20")
-
All I have to say is, when I watch porn with the nouveau drivers, every 6-7 minutes my computer completely freezes, its so bad I have to do a hard reboot
After I install the nvidia drivers, I have hair on my palm and am happy.
In all seriousness the nouveau drivers have come a long way, they don't lock up my computer anymore (good for at least a week, longest I tested recently, yes, the lockup was bad when it happened)
but, for gaming, your all out of your minds :P
Even very old games like half-life2 suck using nouveau, I have tried it and three of my grandkids, ages, 16, 18, 20 (next month), theirs just such a huge difference, although they prefer windows or xbox, playstation for games, they get linux when they visit me and they don't mind ;)
-
vilde, purge virtualbox* and take the original in current version 6.0.0 (https://download.virtualbox.org/virtualbox/6.0.0/) (or 6.0.1 (https://www.virtualbox.org/wiki/Testbuilds) testbuild like me)!
Changelog 6.0.x (https://www.virtualbox.org/wiki/Changelog-6.0) ("Linux hosts: support Linux 4.20")
I can't install that, not working, probably I don't know how, but installing the 6.0.0 version with .deb is not working. I need Virtual Box, so I have to go back to older kernel for the moment
-
@vilde,
here Oracle virtualbox installation works like before.
# LANG=C less /etc/apt/sources.list.d/virtualbox.list
# Oracle Virtualbox
# https://www.virtualbox.org/wiki/Linux_Downloads
# wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | apt-key add -
# deb http://download.virtualbox.org/virtualbox/debian stretch contrib
deb http://download.virtualbox.org/virtualbox/debian bionic contrib
# LANG=C apt-cache search virtualbox | grep -i oracle
virtualbox-5.1 - Oracle VM VirtualBox
virtualbox-5.2 - Oracle VM VirtualBox
virtualbox-6.0 - Oracle VM VirtualBox
# LANG=C apt install virtualbox-6.0 -s
Reading package lists... Done
Building dependency tree
Reading state information... Done
virtualbox-6.0 is already the newest version (6.0.0-127566~Ubuntu~bionic).
...
-
I can't install that
Completely inadequate information. What did you do exactly? What were the results? So you can get targeted support.
Cut. Execute:
apt purge virtualbox*
wget https://download.virtualbox.org/virtualbox/6.0.0/VirtualBox-6.0.0-127566-Linux_amd64.run
sh VirtualBox*.run
For uninstalling:
sh VirtualBox*.run uninstall
You have to take care of updates yourself.
samoht, Bionic packages may or may not work. Packages for Ubuntu in debian sid are not a good idea.
-
I can't install that
Completely inadequate information. What did you do exactly? What were the results? So you can get targeted support.
Cut. Execute:
apt purge virtualbox*
wget https://download.virtualbox.org/virtualbox/6.0.0/VirtualBox-6.0.0-127566-Linux_amd64.run
sh VirtualBox*.run
For uninstalling:
sh VirtualBox*.run uninstall
You have to take care of updates yourself.
samoht, Bionic packages may or may not work. Packages for Ubuntu in debian sid are not a good idea.
Sorry and thank you for your help axt but: that's not the way I want to install things on my every day laptop with siduction, if I can't install it with apt, or maybe dpkg, then I don't install.
-
@axt,
using ubuntu/bionic virtualbox packages has already been discussed, so what? Look at
https://forum.siduction.org/index.php?topic=7338.0 (https://forum.siduction.org/index.php?topic=7338.0)
All I wanted to say is: At this vey moment virtualbox is installable and fully functional in sid.
Greetings,
Tom
-
First off Happy New Year to all! For the very reasons of having to jump through these constant changes I think kvm might be time to try? :-\
-
using ubuntu/bionic virtualbox packages has already been discussed, so what? Look at
If you had read the thread completely, you would have seen, that I also wrote there. So I know it...
The best statement in that thread is:
Unstable-User sollten sich zu helfen wissen, wenn nicht - ok, die Gefahr besteht, dass diese Nutzergruppe dann auch nicht mit siduction an sich glücklich wird.
That's my opinion, too.
-
Still happens
-
What's supposed to have changed? Not the kernel has to change (current is 4.20.0-towo.3-siduction from last night.). There are no new versions of nvidia or vbox 5.2.x.
Btw., kernel 5.0-rc1 has been published (...breaks nvidia and VMware (http://rglinuxtech.com/?p=2469) - the eternal song). New year - new main number. ;)
-
The situation is now:
vbox 6.x is compatible with kernel 4.20
nvidia 415.25 and 410.93 are even.
Now you can think yourself, what to do.
Maybe legacy 390.xx will get a update, only nvidia is knowing.
For vbox 5.2.x are patches in the wild, you are fre to use them.
-
vbox 6.x is compatible with kernel 4.20
As described. Works perfectly.
-
so... is there a fix or not? Do I have to uninstall Virtualbox? I can go without it for a while, I guess, but I'd like to have it soon.
And what about the Nvidia Bullshit? How does one fix that?
I'd like to be able to update my computer without worrying my ass off every time
-
I think if you want to do that you have to leave Nvidia graphics cards - as towo alreadystated...
-
I think if you want to do that you have to leave Nvidia graphics cards - as towo alreadystated...
No, you haven't, but you have to use the newest cards, no legacy ones.
-
Of course you are right. But I by myself love Linux because it does not have builtin "planned obsolescense". Taking cards from Nvidia bring this back in a unsatisfyable way. Nvidia tells you when you have to buy a new one.
-
That's why i was saying, make yoursel comfortable and use graphics hardware, which is using free drivers, that come inline with kernel.
If you want Nvidia for some reason, live with the planed obsolence on their products.
-
so... is there a fix or not? Do I have to uninstall Virtualbox? I can go without it for a while, I guess, but I'd like to have it soon.
Maybe you missed (as I am) that the bionic-version of oracle virtualbox 6 works with an up-to-date system?
-
That's why i was saying, make yoursel comfortable and use graphics hardware, which is using free drivers, that come inline with kernel.
If you want Nvidia for some reason, live with the planed obsolence on their products.
That's true towo, I agree, but that's valid only if you are in the position to choose hardware, I can't afford to buy a new laptop because it happens to be a nvidia graphics hardware inside the one I have. As for the moment my nvidia card in my multimeda-computer is working, when it doesn't anymore I have to find a way to solve that. Change computer, change os or whatever?
About VB, I did have to install the bionic-version because I need VB
-
I have learnt that I have to look at these aspects BEFORE I buy any hardware. I never would leave Linux because of plannend obsolescanse of commercial drivers. I always would change the impacted hardware 8)
-
inxi -GGraphics: Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nouveau v: kernel
Display: server: X.org 1.20.3 driver: nouveau tty: 122x30
Message: Advanced graphics data unavailable in console for root.
Nvidia says driver 410.93 is suitable for my card and yet since kernel 4.20.0 and /systemd/udev update it no longer installs. Towo says 415.25 should install and yet it doesn't. Any attempt at installing any nvidia driver produces exactly what I posted when I opened this thread. There are many bug reports concerning systemd and udev 240.x so I'm not the only one. Something is wrong here and it all stems from moving to the 4.20.xx kernel and maybe systemd/udev update.
-
"it doesn't" is saying zero!
So no one can or will help you.
-
Nvidia says driver 410.93 is suitable for my card and yet since kernel 4.20.0 and /systemd/udev update it no longer installs. Towo says 415.25 should install and yet it doesn't. Any attempt at installing any nvidia driver produces exactly what I posted when I opened this thread. There are many bug reports concerning systemd and udev 240.x so I'm not the only one. Something is wrong here and it all stems from moving to the 4.20.xx kernel and maybe systemd/udev update.
Please try this (make sure you are fully upgraded by dist-upgrade)
apt purge nvidia. (don't forget the period!!)
echo deb http://deb.debian.org/debian/ experimental main contrib non-free | tee -a /etc/apt/sources.list.d/debian.list
echo deb http://packages.siduction.org/extra experimental main contrib non-free | tee -a /etc/apt/sources.list.d/debian.list
apt update; apt install nvidia-driver nvidia-driver-libs nvidia-settings nvidia-kernel-dkms vulkan-utils -t experimental --install-recommends --assume-yes
If this fails, post the WHOLE output.
-
Thanks piper: I just tried your suggestion but unfortunately it failed with the same outcome as my first post in this thread (I'm OP). I had already tried doing the install in this way (except for the recommends part) many times before, especially after each kernel and/or systemd/udev upgrade. At each the nvidia modules failed to load.
When you say "output" which output would you like? My apologies I'm afraid it will have to wait until tomorrow before I can reply.
-
The output of the nvidia install in command line
I just built a fresh iso for myself with nvidia drivers included with no problems also.
-
piper: thanks for your help
Yesterday your script ran to a conculsion although on reboot the nvidia modules failed to load.
This morning things are completely different.
I piped the the output of your installation script to a text file. The CLI stopped with this output
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
E: Package 'nvidia-driver' has no installation candidate
the output of the text file read
Reading package lists...
Building dependency tree...
Reading state information...
Package nvidia-driver is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
nvidia-driver-bin nvidia-persistenced
So istead of using nvidia-driver I tried the installation using nvidia-driver-bin and nvidia-persistenced with following output
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nvidia-driver-bin : Depends: nvidia-alternative (= 390.87-6) but it is not going to be installed
Depends: libnvidia-ml1 (>= 319) but it is not going to be installed
Recommends: nvidia-driver but it is not installable
nvidia-persistenced : Depends: libnvidia-cfg1 but it is not going to be installed or
libnvidia-cfg1-any
Any insights you might have wil be gratefully received.
-
Can I see the FULL output of
apt policy
and
dpkg --list nvidia*
-
apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://download.virtualbox.org/virtualbox/debian stretch/contrib amd64 Packages
release o=Oracle Corporation,n=stretch,l=Oracle Corporation,c=contrib,b=amd64
origin download.virtualbox.org
500 http://packages.siduction.org/fixes unstable/contrib amd64 Packages
release o=Siduction,a=unstable,n=unstable,c=contrib,b=amd64
origin packages.siduction.org
500 http://packages.siduction.org/fixes unstable/main amd64 Packages
release o=Siduction,a=unstable,n=unstable,c=main,b=amd64
origin packages.siduction.org
500 http://packages.siduction.org/extra unstable/main amd64 Packages
release o=Siduction,n=unstable,c=main,b=amd64
origin packages.siduction.org
500 http://ftp.uni-stuttgart.de/siduction/fixes unstable/contrib amd64 Packages
release o=Siduction,a=unstable,n=unstable,c=contrib,b=amd64
origin ftp.uni-stuttgart.de
500 http://ftp.uni-stuttgart.de/siduction/fixes unstable/main amd64 Packages
release o=Siduction,a=unstable,n=unstable,c=main,b=amd64
origin ftp.uni-stuttgart.de
1 http://ftp.uni-stuttgart.de/siduction/extra experimental/non-free amd64 Packages
release o=Siduction,n=experimental,c=non-free,b=amd64
origin ftp.uni-stuttgart.de
500 http://ftp.uni-stuttgart.de/siduction/extra unstable/main amd64 Packages
release o=Siduction,n=unstable,c=main,b=amd64
origin ftp.uni-stuttgart.de
500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
release o=Opera Software AS,a=stable,n=stable,l=The Opera web browser,c=non-free,b=amd64
origin deb.opera.com
500 https://download.videolan.org/pub/debian/stable Packages
release o=videolan,a=stable,n=stable,l=videolan,c=
origin download.videolan.org
1 http://packages.siduction.org/extra experimental/non-free amd64 Packages
release o=Siduction,n=experimental,c=non-free,b=amd64
origin packages.siduction.org
1 http://packages.siduction.org/extra experimental/contrib amd64 Packages
release o=Siduction,n=experimental,c=contrib,b=amd64
origin packages.siduction.org
1 http://packages.siduction.org/extra experimental/main amd64 Packages
release o=Siduction,n=experimental,c=main,b=amd64
origin packages.siduction.org
1 http://deb.debian.org/debian experimental/non-free amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=amd64
origin deb.debian.org
1 http://deb.debian.org/debian experimental/contrib amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=contrib,b=amd64
origin deb.debian.org
1 http://deb.debian.org/debian experimental/main amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
origin deb.debian.org
1 http://httpredir.debian.org/debian experimental/main amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
origin httpredir.debian.org
1 http://httpredir.debian.org/debian experimental/contrib amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=contrib,b=amd64
origin httpredir.debian.org
1 http://httpredir.debian.org/debian experimental/non-free amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=amd64
origin httpredir.debian.org
500 http://httpredir.debian.org/debian unstable/non-free amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64
origin httpredir.debian.org
500 http://httpredir.debian.org/debian unstable/contrib amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64
origin httpredir.debian.org
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin httpredir.debian.org
Pinned packages:
nvidia-driver -> 415.25-0.siduction.2 with priority -30000
nvidia-driver -> 410.93-1 with priority -30000
nvidia-driver -> 390.87-6 with priority -30000
glx-diversions -> 0.9.0 with priority -30000
xserver-xorg-video-nvidia -> 415.25-0.siduction.2 with priority -30000
xserver-xorg-video-nvidia -> 410.93-1 with priority -30000
xserver-xorg-video-nvidia -> 390.87-6 with priority -30000
The latter part looks strange as i don't remember pinning any packages let alone anything to do with nvidia.
I'll be back soon with the output of dpkg --list nvidia* as I can only use one and the same machine for the tests. Thanks again piper.
-
My apologies for the delay I was going to apply dpkg --list nvidia* after installing nividia-driver but I forgot that since this morning i can't.
dpkg --list nvidia* gives
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================-============-============-=================================
un nvidia-alternative <none> <none> (no description available)
-
This, is a fucking mess and haven't been upgraded in 6 years (2013) not sure why your using it.
https://download.videolan.org/debian/stable/
Why not just do
apt install vlc
This and the pinned packages are probably screwing you to some extent
My opinion, start from scratch with a clean source list
If you used
apt purge nvidia.
You need the period !!
nvidia-alternative should not be showing period, I tested this, this is what gets removed and it does not show for me using dpkg --list nvidia*
http://paste.debian.net/hidden/84bd300b/
-
Well i cleaned up my sources.list, removed the pinning and fixed the presence of nvidia-alternative in the policy list. Reinstalled nvidia-driver and rebooted. But again the modules failed to load.
As I said I don't really need the nvidia drivers and my machine works OK. I've spent far too much of my time on this problem so I'm calling it a day. Thanks for your help piper. All I can say is the nvidia drivers worked and since the new kernel or the systemd upgrade they don't.