Just installed and updated 12.3 64bit, I installed gcc/make/kernel-dev. Downloaded and installed newest virtualbox 64bit rpm. Running /etc/init.d/vboxdrv setup fails. The /var/log/vbox-install .log doesn’t help. It looks like Chinese to me. Anyone know what failed?
Makefile:184: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /usr/src/linux modules
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
Did you install the kernel sources and such? I normally suggest you take the following action:
Open YaST / Software / Software Management - Select the View Button on the top left and pick Patterns. Now, you will see several Patterns listed and you want to select:
Development
[X] Base Development
[X] Linux Kernel Development
[X] C/C++ Development
Then Press the Accept button on the bottom right and allow these applications to install. I have been able to install and run VirtualBox 4.2.8 (Downloaded directly from Oracle) in openSUSE 12.3 without issue after following my own advice.
You don’t say why you installed the developer tools along with VBox. I have 12.3 running within VBox, but on a OSX host. The developer tools are only required if you want to build the guest additions manually. You may need to add the openSUSE Virtualization repo so you can install the latest virtualbox-guest-kmp-desktop packages to work with the 12.3 kernel.
Additionally, you can’t compile anything without the kernel-source package.
Newer kernel should still be installed using “zypper up” in this case; what may happen is that -devel packages get updated, so old kernel does not more have matching -devel package. I do not remember which packages are subject to multiversioning by default.
If new kernel was not installed, something went wrong.
“zypper up” will only update to a package from the same vendor as the installed package. This means that it will not cross between openSUSE ( e.g. distribution, factory, and openSUSE Build Service – e.g. repositories/Kernel:/). To change vendors use “zypper dup --from”. But unless you are updating multiple installations, it is generally easier to use YaST for kernel updates.
From man zypper
update (up) [options] [packagename] ...
Update installed packages with newer versions, where possible.
This command will not update packages which would require change of package vendor unless the vendor is
specified in /etc/zypp/vendors.d, or which would require manual resolution of problems with dependen-
cies. Such non-installable updates will then be listed in separate section of the summary as "The fol-
lowing package updates will NOT be installed:".
To update individual packages, specify one or more package names. You can use the '*' and '?' wildcard
characters in the package names to specify multiple packages matching the pattern.
On 03/11/2013 12:36 PM, 67GTA wrote:
>
> I didn’t run “zypper dup”, so it was probably using factory kernel, and
> 12.3 kernel-dev. I will wait and do a “zypper dup” after release day.
If your repos are set to the 12.3 URLs, then you can zypper dup now. After RC2
comes GM (for Gold Master). That was set last Friday, and is the “final”
material for the release. The time between GM and the release is time for the
mirrors to catch up in time for the formal announcement.