Your message dated Wed, 22 Aug 2018 12:43:45 +0200 with message-id <[email protected]> and subject line Re: addendum has caused the Debian Bug report #906194, regarding virtualbox: fails to install backported VB on Stretch 9.5 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 906194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906194 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virtualbox Version: 5.2.16-dfsg-3~bpo9+2 Severity: important Dear Maintainer, I tried and install VirtualBox on a clean installation of Stretch 9.5, from Stretch-backports, following the instructions given in Debian Wiki. During the installation I got the following warning: "... Loading new virtualbox-5.2.16 DKMS files... Building for 4.9.0-7-686-pae Building initial module for 4.9.0-7-686-pae Error! Bad return status for module build on kernel: 4.9.0-7-686-pae (i686) Consult /var/lib/dkms/virtualbox/5.2.16/build/make.log for more information. Setting up fakeroot (1.21-3.1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up virtualbox (5.2.16-dfsg-3~bpo9+2) ... vboxweb.service is a disabled or a static unit, not starting it. Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details. invoke-rc.d: initscript virtualbox, action "restart" failed. ● virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-14 20:18:01 CEST; 38ms ago Docs: man:systemd-sysv-generator(8) Process: 2983 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) .... " The file /var/.../make.log indicated above is attached. Note that I could install successfully VB on a precedent installation of Stretch 9.4, from the given backport at that time. My (very elementary) knowledge of Linux environment does not allow me to understand the cause of the problem. Thanks for your attention -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-7-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii iproute2 4.9.0-1+deb9u1 ii libc6 2.24-11+deb9u3 ii libcurl3-gnutls 7.52.1-5+deb9u6 ii libdevmapper1.02.1 2:1.02.137-2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgsoap10 2.8.35-4+deb9u1 ii libpng16-16 1.6.28-1 ii libpython3.5 3.5.3-1 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libssl1.1 1.1.0f-3+deb9u2 ii libstdc++6 6.3.0-18+deb9u1 ii libvncserver1 0.9.11+dfsg-1+deb9u1 ii libx11-6 2:1.6.4-3 ii libxcursor1 1:1.1.14-1+deb9u1 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libxmu6 2:1.1.2-2 ii libxt6 1:1.1.5-1 ii procps 2:3.3.12-3+deb9u1 ii python3 3.5.3-1 ii python3.5 3.5.3-1 ii virtualbox-dkms [virtualbox-modules] 5.2.16-dfsg-3~bpo9+2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5opengl5 5.7.1+dfsg-3+b1 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii virtualbox-qt 5.2.16-dfsg-3~bpo9+2 Versions of packages virtualbox suggests: pn vde2 <none> pn virtualbox-guest-additions-iso <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, 16 Aug 2018 21:04:16 +0200 "G. Cabrele" <[email protected]> wrote: > Following the alternative way of downloading from Oracle, as indicated > in Debian Wiki guide, > the installation process ended with: > "vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find > out why." > and dmesg tells: > "[43186.988394] vboxdrv: Requires SSE2 (cpuid(0).EDX=0x383fbff)". > > Effectively my CPU features SSE, but not SSE2. Could be that the problem ? > Do the recent releases of VBox require SSE2 ? > since I could install vers. 1.30 on Stretch 9.4, can I install that on 9.5 ? > That seems to be the same problem that > prevents me from installing the most recent version of KDE desktop. > Which other package is requiring SSE2, and why that is not clearly > indicated ? > Regards > Hello G. Please open a single bug report, with one single problem, explaining your version of virtualbox *before* and *after* the upgrade, because this bug report is contradictory and difficult to parse in many parts, e.g. "since I could install vers. 1.30 on Stretch 9.4, can I install that on 9.5 ?" I don't understand what 1.30 means "Do the recent releases of VBox require SSE2 ?" yes, since a while I would say "That seems to be the same problem that prevents me from installing the most recent version of KDE desktop." I don't know honestly, but SSE2 is required since lots of years probably, and I think at least since Stretch 9, so I don't understand how could your system work until today... Did you try to downgrade vbox to see if it works? G.
--- End Message ---
