Software :: Missing Autoconf.h In Vbox Install Log
Jul 3, 2010
I have a distro-neutral VirtualBox shell install: VirtualBox-xxx.run
you type: sh VirtualBox-xxx.run install
this goes through but the screen says "could not compile the kernel module vboxdrv.ko, see the install log"
the install log in /var/log says this:
test -e include/linux/autoconf.h -a -e include/config/auto.conf
echo " ERROR KErnel configuration is invalid
echo " include/linux/autoconf.h or include/config/auto.conf are missing
echo " run 'make oldconfig && make prepare' on kernel src to fix it"
ok, I've left out a bunch of stuff but, NO these 2 files are NOT missing. I have all the required compile-type packages and the source and headers. Under /usr/src there are :
1: /linux-2.6.31.12-0.2
2: /linux-2.6.31.12-0.2-obj
3: /linux/obj
4: linux
num 4 is a symbolic which points to 1:. num 3 has a sub-dir /i386/default which links to the /default in 2:
the supposed missing files are in sub-dir in 2:
This is what I did. I changed num 4: to point to 2:, deleted all the vbox stuff and re-tried install - still same result.
I reset num 4: to point to 1: and did the "make oldconfig && make prepare". This put new sub-dir entries under 1: with the 2 files in correct sub-dirs. Delete vbox and try re-install - still same result.
Some things I left out of the error log at the start show that the install's use of "make" relates to both dirs 1: and 2: so even with both having the files the install is still barfing.
Perhaps related to this, at the log end there are errors about the /tmp/vbox and some SUPdrv.c files.
I looked in the forums and there are suggestions wrt errors about these missing files that the fault lies with kernels 2.6.33 which puts these missing files in a different named sub-dir - /generated. Well as you see above, kernel is a 2.6.31
There's supposed to be a command line option for the shell install where you add " -- xxxxx " where xxxxx is extra instructions. I tried to put definitive pointers to the sub-dirs involved there but not successful.
I am running Ubuntu 10.04 (the guest) in VBox 3.2.4 which is running in Vista (in a dual core AMD Athlon). Ubuntu works okay except the screen size is one-quarter of the space available on the 22" widescreen monitor. I read that installing BoxAdditions_3.2.4_62467 can solve the problem. When I run the terminal command (using the appropriate file) sudo sh ./VBoxLinuxAdditions-amd64.run I get an error message --> sh: Can't open .VBoxLinuxAdditions-amd64.run
I have recently installed virtual box on fc14 using add /remove software . However so far i have not been able to install any OS on that. I put the OS CD the cdrom and click on start virtual machine..it gives following errors ..
I have followed the instructions given there but all in vain...
Code: [root@Fedora Raman]# /etc/sysconfig/modules/VirtualBox-OSE.modules ERROR: modinfo: could not find module vboxdrv ERROR: modinfo: could not find module vboxnetflt ERROR: modinfo: could not find module vboxnetadp
I am running Ubuntu 10.04 in VBOX on a Windows 7 host. I have a Nvidia Geforce 9600 gt graphics card. I would really like to get Compiz Fusion desktop effects working on it. Is this possible? I have read some threads where people have ultimately found out that the VBox guest addition drivers are not compatible. How can I determine if mine is going to work?
I Just loaded 11.2 64 bit, initially the kernel was "default", however, after I installed my Nvidia drivers it changed to desktop, I'm not sure I understand? In GRUB my screen lists it as desktop. Is "default" somewhere? Was it replaced? Things seem to be working alright in most cases although I'm having inordinate problems with "virtual Box" and Vmware server. In Vbox the kernel module won't start.
My box is centos 5.5 x64, and how to upgrade autoconf 2.59-12 to 2.61? When I install nabi, I got this message.
Quote:
[root@localhost nabi-0.99.7]# make cd . && /bin/sh /_work/nabi/nabi-0.99.7/missing --run autoconf aclocal.m4:20: warning: this file was generated for autoconf 2.61. You have another version of autoconf. It may work, but is not guaranteed to.
I just installed a test Natty VirtualBox server from the "mini" iso. After doing that the normal boot always ends with a blank screen and cannot login. The recovery boot option does work normally. After much digging around and various tests I found that the "splash quiet" boot options cause this issue.
I removed them from the /etc/defaults/grub file and ran update-grub. Next boot the login screen came up after as normal. It seems when the splash flashes that purple screen with the Ubuntu 11.04 message it is breaking something and does not get back out of some graphics mode.
This is in a VirtualBox window and I noticed that vesa framebuffers seem to be used by default in grub now. I never had this issue in previous releases and I'm just wondering if others have seen this and if there is a better fix than disabling splash. I don't mind having it disabled as this is a server install anyway and I'm fine with seeing debug messages during boot. If other have seen this then perhaps it needs to be logged as a bug?
When I run the command: "sudo apt-get install build essential autconf automake libxmu -dev" I go the following error: "E: Package autoconf has no installation candidate" In the cd-rom there is no any autconf package.
I have a conexant modem and i want to make it work(just for fun, i have DSL). The linuxant driver works but i want full 56k. I tried ubuntu [URL]... How to/Conexant and there was alink for some Dell driver. I've compiled and installed the Dell successfully but when i run
When creating the binary rpm for autoconf from a source, the test for "autom4te" gives "FAILED (tools.at:134)", while the rest of the test give "OK". This prevents the binary from being built successfully. How can I build the binary? I am using RHEL 5.
After doing make I have the following questions? How can I see that the build is with debug information? What shall I do to build the release version? Can I have the release version in one directory and the debug version in another? I mean, when I change from debug to release, make will not overwrite the debug version.
I have an asus pc, and its network hardware is not recognized by debian, the drivers are not even in the list provided during the installation process. I managed to download them from another pc, but if i try to make them and install them, i'm stucked because Make is not installed on debian (nor is sudo).So i need a connection to install the drivers that provide me a co0nnections..
I have just newly installed Ubuntu10.10 on my laptop and am attempting to install VirtualBox 3.2.10. Everything has been going fine until I run the apt-get install command. The results are as follows:
I am trying to install this particular Debian-based distro in VirtualBox, but upon trying to install it, I get the massage
Code: This kernel requires an x86-64 CPU, but only detected an i646 CPU.The host system is 64 Natty, with i5-M460. What am I missing? I thought everything is 64 bit in front of me...
Am trying to install PHP by running the "configure" command but saw 2 WARNINGS about not having defined "datarootdir".Looking into this further here I found that there is a change since Autoconf 2.60, the datarootdir variable is introduced and it should have been defined in the "Makefile.in" file.Guess PHP.net didn't do this properly?
I did it, I don't know exactly what I did, but OpenSuse 11.4 only boots to CLI when I fire it up using vbox 4.0.10. I was not able to attached a screenshot, I got an error saying that I did not have sufficient rights or something.
I have Vbox 4.0.4_OSE installed on my 11.4/KDE4.7 Laptop with Win7 and WinXP VMs installed. Generally runs well, although the Win7 VM seems to lock up on occasion if I ignore it for too long. Compared to having to reboot to Win7 to do the few things still stuck on Windoze, it is a GREAT solution.
Question: I have seen several forum items related to difficulty with dual boot systems and the installation of Win7SP1, regarding SP1s checking the MBR for the Win7 boot loader. Has anyone done a SP1 update to a VM on Vbox? It is sort of unclear what SP1 might see in the VM disk container associated with the VM. Since the initial load process for a new VM is time consuming, I thought I would ask first before blowing up my otherwise working Vbox system and then having to reload from scratch.
I keep losing my keyboard in Virtualbox. I "fix" it be reverting back to the host and then switching to the VM and it will be back. Googling brought up others having similar issues with Ubuntu, but no solution that I saw.My host is Jessie and client is Wheezy, both with Xfce. The mouse works just fine.
Can use a WIN XP appliance (from my old PCLinuxOS) as guest there without any issues.
Added a second guest - Jessie 8.0 KDE 64 bit. Works, but no seamless display, mouse issue ...
So added inside guest:
non-X11 guest utilities + X11 guest utilities from the repositories
(These utilities are meant to be run inside the the virtual machine. They provide closer integration ...)
I simply don't know, how to run those utilities ...
What I get is
Code: Select all# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● virtualbox-guest-utils.service loaded failed failed LSB: VirtualBox Linux Additions ● virtualbox-guest-x11.service loaded failed failed LSB: VirtualBox Linux X11 Additions
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.
2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
launching vBox lately pops-up this; but if I allow it to go ahead, I get this.. : the window has no end (!), no scroll bars nor any further info. If I first uninstall in Yast, will I lose all of my machines? Up until now these periodic updates have been a breeze, only sometimes needing a vbox setup afterwards to tweak the kernel
I have been trying to run my vmachines in virtualbox with no success so I decided to install upgraded packages for upgraded kernel, this means to install them from Virtualization-kernel-HEAD repo.The error is about that known issue where the kernel module can't start.
I'm using Ubuntu 9.10 and recently installed Virtualbox PUEL edition that I downloaded from the Virtual box website. So I installed a virtual windows XP and it works fine. However, when the virtual XP is running, my computer can't go to hibernate when I click the hibernate button.The screen just turns black for several seconds and then brings me back to the login screen. When I shut down the virtual xp, the computer can go to hibernate the normal way.Why is it that running the virtual machine prevents my pc from hibernating?Is there a setting to enable hibernation while the virtual machine is running?
I put vbox on my wife's Dell Inspiron 6000 to play Netflix but the video won't play. After buffering it says there's an "internet connection problem". From what I've read that means the connection is too slow. Netflix works fine on my wired desktop (also Lucid+vbox) and on the same laptop booting into Windows (not VM). So I'm thinking there's a problem with vbox slowing the connection between the laptop's wireless and the VM?
I don't know if it will help with Netflix but 2D video acceleration is grayed out on vbox. Strangely, the 3D acceleration is fine and I can select it. If this is due to an unsupported video driver, can I change it?
I went to the Kodak website to see if I can download Kodak ESP 3200 series for Ubuntu, but it only has them for windows and MAC is there a way around this other than using VBOX?
Ok, so i just got fedora 12 all set up in Virtual Box and got the guest additions and stuff so i can have max screen res. I went to set up compiz following this site (google Using Compiz on Fedora 12 as Linux Guest in VirtualBox) installed dkms, rebooted and now after it loads the bar at the bottom that says fedora 12, it gives a blank black screen with a solid white line at the top like a c prompt curser. Whats the deal here? did dkms break my install or something? Its on a vm so no big loss but id still like to know.