I have the kernel downloaded, but it takes 40 minutes to compile of my Dell Laptop, so I will get back on my success of the new kernel compile and install. So in the mean time please visit my blog on kernel compiling you can find here:
Well sorry to say, the kernel compile blows up after 8 minutes, only says FAILED and does not complete. There will not be any kernel 3.13-rc1 testing for me tonight. It is important for me to hear if you got it to compile or not or if you got it installed from the kernel head repo.
On 11/22/2013 08:16 PM, jdmcdaniel3 wrote:
> Well sorry to say, the kernel compile blows up after 8 minutes, only
> says FAILED and does not complete. There will not be any kernel
> 3.13-rc1 testing for me tonight. It is important for me to hear if you
> got it to compile or not or if you got it installed from the kernel head
Anything more than FAILED?
The configuration combination of
CONFIG_SYSTEM_TRUSTED_KEYRING is not set
is reported to fail. The latter one would come from the old configuration, and
if you select the default options, you would get the latter.
The time between release of 3.12 and 3.13-rc1 was nearly 3 weeks, which is
almost one week longer than usual. Linus was traveling without good network
connections, and did not want to do the big merge under those conditions.
On 11/23/2013 10:26 AM, jdmcdaniel3 wrote:
> After the modification, it went about 40 minutes and failed again, with
> these last entries.
> LD drivers/net/wireless/built-in.o
> LD drivers/net/built-in.o
> LD drivers/built-in.o
> So, still not compiling for me.
Why no error messages? Are you using a script to build? What do you see if you
issue a simple “make” in the kernel source directory?
So taking your lead, I used my Turbo Mode compile and fixed the one issue you told us about and kernel 3.13-rc1 has compiled and is running right now on my Dell Laptop. I did not get VirtualBox 4.3.2 to work however, here is the error I get:
On 11/23/2013 04:16 PM, jdmcdaniel3 wrote:
> make: *** [/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.o] Error 1
> make: *** [module/tmp/vbox.0] Error 2
> make: *** [vboxdrv] Error 2
> Does this VB compile error mean anything to you?
The errors from make are seldom meaningful. The real error was likely issued
from gcc, but that doesn’t show in your listing. For me,
…/r0drv/memobj-r0drv.o compiled with no errors or warnings. One other thing I
probably do differently from you. Whenever I get a new release of VB, I cd to
/usr/share/virtualbox/src/, do a “chown <my_user>:user -R vboxhost”, then “cd
vboxhost”, and “make && sudo make install” from there. That way I do not ever
need to go through the log files that the official install script makes. For me,
having all the output from the build step right on my screen is better.
So I have compiled and loaded kernel 13.3-rc2. OpenSUSE 13.1 came up just fine however, VirtualBox will not install for me into the new kernel, so I must revert back to kernel 3.12.2, also just released.
On 11/30/2013 05:36 PM, jdmcdaniel3 wrote:
> So I have compiled and loaded kernel 13.3-rc2. OpenSUSE 13.1 came up
> just fine however, VirtualBox will not install for me into the new
> kernel, so I must revert back to kernel 3.12.2, also just released.
Oracle just released VBox 4.3.4. One of the changes was a fix for compilation
errors with kernel 3.13. It works for me.