Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Dec 2015 21:05:57 -0600
From:      John Aten <welcome.to.eye.o.rama@gmail.com>
To:        erwin.pacua@gmail.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Mouse & Keyboard not working in Virtual Box VM
Message-ID:  <2607C7BB-43F7-429F-B311-924A797CE185@gmail.com>
In-Reply-To: <n42s3d$ujr$1@ger.gmane.org>
References:  <010EFC12-FD25-4A04-B042-9B0C95478C03@gmail.com> <n42s3d$ujr$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Dec 6, 2015, at 8:49 PM, Erwin Pacua wrote:

> John Aten wrote:
>=20
>> Hello all,
>>=20
>> I am completely new to FreeBSD. I recently downloaded the FreeBSD
>> 10.2-RELEASE virtual machine image for Virtual Box. I am running =
Virtual
>> Box 4.3.30 on Mac OSX 10.6.8. (There are newer versions of Virtual =
Box,
>> which require a newer version of OSX than I am running, thus I =
haven't
>> been able to upgrade) Everything seemed to go well, until I tried to =
get a
>> window manager working. I installed the Enlightenment desktop in my
>> regular user account, but when it starts the mouse and keyboard do =
not
>> work. The same happens in whatever basic window manager comes up in =
the
>> root account.
>>=20
>> The X log says that since 'hotplugging' is on, these devices will be
>> disabled:
>>=20
>> [   429.942] (**) |-->Input Device "Mouse0"
>> [   429.943] (WW) Hotplugging is on, devices using drivers 'kbd', =
'mouse'
>> [   or 'vmmouse' will be disabled. 429.943] (WW) Disabling Mouse0
>> [   432.737] (II) config/devd: adding input device (null) =
(/dev/sysmouse)
>> [   432.737] (II) LoadModule: "mouse"
>> [   432.738] (II) Loading =
/usr/local/lib/xorg/modules/input/mouse_drv.so
>> [   432.742] (II) Module mouse: vendor=3D"X.Org Foundation"
>> [   432.742] (II) UnloadModule: "mouse"
>> [   432.742] (II) Unloading mouse
>> [   432.742] (EE) Failed to load module "mouse" (module requirement
>> [   mismatch, 0) 432.743] (EE) No input driver matching `mouse'
>> [   432.777] (II) config/devd: adding input device Mouse (/dev/psm0)
>> [   432.777] (II) LoadModule: "mouse"
>> [   432.778] (II) Loading =
/usr/local/lib/xorg/modules/input/mouse_drv.so
>> [   432.779] (II) Module mouse: vendor=3D"X.Org Foundation"
>> [   432.779] (II) UnloadModule: "mouse"
>> [   432.779] (II) Unloading mouse
>> [   432.779] (EE) Failed to load module "mouse" (module requirement
>> [   mismatch, 0) 432.779] (EE) No input driver matching `mouse'
>> [   429.942] (**) |-->Input Device "Keyboard0"
>> [   429.943] (WW) Disabling Keyboard0
>>=20
>> I have found several articles and forum threads that deal with this, =
and
>> similar issues, but none of the fixes seem to work, and many involve =
other
>> issues that I am not having.
>>=20
>> I installed the virtualbox guest additions from ports, and from =
looking at
>> various sources around the internet, I placed the following in =
rc.conf:
>>=20
>> ifconfig_em0=3D"DHCP"
>>=20
>> vboxguest_enable=3D"YES"
>> vboxservice_enable=3D"YES"
>>=20
>> mouse_enable=3D"YES"
>>=20
>> hald_enable=3D"YES"
>> dbus_enable=3D"YES"
>>=20
>> It appears I do not have hald installed; when I run `service hald =
start`,
>> I get an error that says hald does not exist. I read somewhere that =
hald
>> is deprecated, anyway, so I'm not sure that getting it running is the
>> answer. Before I read that, though, I did add the suggested
>> /usr/local/etc/hal/fdi/policy called 90-vboxguest.fdi file =
recommended
>> from here:
>> =
http://technologytales.com/2014/03/02/installing-freebsd-in-a-virtualbox-v=
irtual-machine/
>> .
>>=20
>> I don't know if maybe I have a problem with the guest additions =
install; I
>> don't see how this would produce the problem, but I do get the =
following
>> warnings in /var/log/messages:
>>=20
>> Dec  4 22:31:06  kernel: ACPI APIC Table: <VBOX   VBOXAPIC>
>> Dec  4 22:31:06  kernel: acpi0: <VBOX VBOXXSDT> on motherboard
>> Dec  4 22:31:06  kernel: cd0: <VBOX CD-ROM 1.0> Removable CD-ROM SCSI
>> device
>> Dec  4 22:31:06  kernel: ada0: <VBOX HARDDISK 1.0> ATA-6 device
>> Dec  4 22:31:06  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
>> Dec  4 22:31:07  root: /etc/rc: WARNING: failed to start vboxservice
>> Dec  5 06:49:29  kernel: ACPI APIC Table: <VBOX   VBOXAPIC>
>> Dec  5 06:49:29  kernel: acpi0: <VBOX VBOXXSDT> on motherboard
>> Dec  5 06:49:29  kernel: cd0: <VBOX CD-ROM 1.0> Removable CD-ROM SCSI
>> device
>> Dec  5 06:49:29  kernel: ada0: <VBOX HARDDISK 1.0> ATA-6 device
>> Dec  5 06:49:29  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
>> Dec  5 06:49:31  root: /etc/rc: WARNING: failed to start vboxservice
>> Dec  5 07:27:14  kernel: ACPI APIC Table: <VBOX   VBOXAPIC>
>> Dec  5 07:27:14  kernel: acpi0: <VBOX VBOXXSDT> on motherboard
>> Dec  5 07:27:14  kernel: cd0: <VBOX CD-ROM 1.0> Removable CD-ROM SCSI
>> device
>> Dec  5 07:27:14  kernel: ada0: <VBOX HARDDISK 1.0> ATA-6 device
>> Dec  5 07:27:14  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
>> Dec  5 07:27:16  root: /etc/rc: WARNING: failed to start vboxservice
>> Dec  5 07:33:31  kernel: ACPI APIC Table: <VBOX   VBOXAPIC>
>> Dec  5 07:33:31  kernel: acpi0: <VBOX VBOXXSDT> on motherboard
>> Dec  5 07:33:31  kernel: cd0: <VBOX CD-ROM 1.0> Removable CD-ROM SCSI
>> device
>> Dec  5 07:33:31  kernel: ada0: <VBOX HARDDISK 1.0> ATA-6 device
>> Dec  5 07:33:31  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
>> Dec  5 07:33:33  root: /etc/rc: WARNING: failed to start vboxservice
>> Dec  5 18:04:52  kernel: ACPI APIC Table: <VBOX   VBOXAPIC>
>> Dec  5 18:04:52  kernel: acpi0: <VBOX VBOXXSDT> on motherboard
>> Dec  5 18:04:52  kernel: cd0: <VBOX CD-ROM 1.0> Removable CD-ROM SCSI
>> device
>> Dec  5 18:04:52  kernel: ada0: <VBOX HARDDISK 1.0> ATA-6 device
>> Dec  5 18:04:52  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
>> Dec  5 18:04:55  root: /etc/rc: WARNING: failed to start vboxservice
>>=20
>> After installing Enlightenment, I ran X -configure, and also added =
some
>> lines to xorg.conf in accordance with suggestions from the internet. =
My
>> current xorg.conf (I added both "AutoAddDevices" lines, and the =
entire
>> ServerFlags section):
>>=20
>> Section "ServerLayout"
>> Identifier     "X.org Configured"
>> Screen      0  "Screen0" 0 0
>> InputDevice    "Mouse0" "CorePointer"
>> InputDevice    "Keyboard0" "CoreKeyboard"
>> Option	"AutoAddDevices" "False"
>> EndSection
>>=20
>> Section "ServerFlags"
>> Option "AutoAddDevices" "False"
>> EndSection
>>=20
>> Section "Files"
>> ModulePath   "/usr/local/lib/xorg/modules"
>> FontPath     "/usr/local/share/fonts/misc/"
>> FontPath     "/usr/local/share/fonts/TTF/"
>> FontPath     "/usr/local/share/fonts/OTF/"
>> FontPath     "/usr/local/share/fonts/Type1/"
>> FontPath     "/usr/local/share/fonts/100dpi/"
>> FontPath     "/usr/local/share/fonts/75dpi/"
>> EndSection
>>=20
>> Section "Module"
>> Load  "glx"
>> EndSection
>>=20
>> Section "InputDevice"
>> Identifier  "Keyboard0"
>> Driver      "kbd"
>> EndSection
>>=20
>> Section "InputDevice"
>> Identifier  "Mouse0"
>> Driver      "vboxmouse"
>> EndSection
>>=20
>> Section "Monitor"
>> Identifier   "Monitor0"
>> VendorName   "Monitor Vendor"
>> ModelName    "Monitor Model"
>> EndSection
>>=20
>> Section "Device"
>>        ### Available Driver options are:-
>>        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
>>        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
>>        ### <percent>: "<f>%"
>>        ### [arg]: arg optional
>> Identifier  "Card0"
>> Driver      "vboxvideo"
>> BusID       "PCI:0:2:0"
>> EndSection
>>=20
>> Section "Screen"
>> Identifier "Screen0"
>> Device     "Card0"
>> Monitor    "Monitor0"
>> SubSection "Display"
>> Viewport   0 0
>> Depth     1
>> EndSubSection
>> SubSection "Display"
>> Viewport   0 0
>> Depth     4
>> EndSubSection
>> SubSection "Display"
>> Viewport   0 0
>> Depth     8
>> EndSubSection
>> SubSection "Display"
>> Viewport   0 0
>> Depth     15
>> EndSubSection
>> SubSection "Display"
>> Viewport   0 0
>> Depth     16
>> EndSubSection
>> SubSection "Display"
>> Viewport   0 0
>> Depth     24
>> EndSubSection
>> EndSection
>>=20
>> I am pretty sure that this is all that I have altered in the course =
of
>> working on this problem, but it is easy to lose track. It seems that =
I
>> have to somehow turn 'hotplugging' off, but I have not been able to =
find
>> out how to successfully do this, and I have no idea what to do next. =
I
>> would very much appreciate any insight on this problem.
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions To
>> unsubscribe, send any mail to =
"freebsd-questions-unsubscribe@freebsd.org"
>=20
>> Option	"AutoAddDevices" "False"
> PCBSD is working fine without this line
>=20
>> Dec  4 22:31:06  kernel: KLD vboxguest.ko: depends on kernel - not
>> available or version mismatch
> how about reinstalling virtualbox-ose-additions which provides =
vboxguest.=20
> Then unload/reload the module back, or restart?
>=20
>> mouse_enable=3D"YES"
> it's moused. I don't have that line and mouse under X is working fine,=20=

> though.
>=20
> output of
> pkg info | grep 'xf86-input-'=20
> would be helpful.
>=20
> Hope it helps.

I would love to provide the output of pkg info | grep 'xf86-input-' , =
but unfortunately I  totally destroyed the vm I was working in. When I =
first tried to install guest additions from ports, I got an error that =
said the source code was unavailable. When I got the source through SVN, =
I messed up and got a different version than the one I was running. I =
then installed the guest additions, so it appears that this messed =
things up somehow, unless I made some other error. I followed Colin =
House's suggestion to buildworld & buildkernel, following the =
instructions in the handbook, but somehow messed everything up; after =
that the VM wouldn't boot at all, so I decided to just start over.=20

Thanks for the help, in any case; I haven't had a chance to get the new =
vm up and running, but if I have the same problem I'll be back!

John=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2607C7BB-43F7-429F-B311-924A797CE185>