On 03/17/15 03:57 PM, Harry Putnam wrote:
Harry Putnam <[email protected]> writes:
Following update of an hipster install running as Vbox guest on an OI
(151_9) installation, rebooted to new BE following upgarde, But it
does not bring up X as in the past, so logging into my user at console
and attempting to startx from there I get this error:
Egad.... I seem to have had a hard time spelling upgrade in previous
post.. including in the subject line...
A further note: I retreated to the previous BE and had no problems
with X but thought it might be helpful to post what happens with vbox
drivers on a (non-failed) start of X and then a failed version from
the new BE
,----
| grep vbox /var/log/Xorg.0.log
| (II) LoadModule: "vboxvideo"
| (II) Loading /usr/lib/xorg/modules/drivers/amd64/vboxvideo_drv.so
| (II) Module vboxvideo: vendor="Oracle Corporation"
| (II) VBoxVideo: guest driver for VirtualBox: vbox
`----
Same grep on new BE showing failed starting of X
,----
| root # grep vbox /var/log/Xorg.0.log
| [134517.554] (II) LoadModule: "vboxvideo"
| [134517.554] (II) Loading /usr/lib/xorg/modules/drivers/amd64/vboxvideo_drv.so
| [134517.570] (II) Module vboxvideo: vendor="Oracle Corporation"
| [134517.571] (II) UnloadModule: "vboxvideo"
| [134517.571] (II) Unloading vboxvideo
| [134517.571] (EE) Failed to load module "vboxvideo" (module requirement
mismatch, 0)
`----
The Xorg module ABI is *not* stable or compatible across releases. When you
upgrade to a new Xorg release you must update all modules as well. This happens
automatically for modules provided with the OS, but not for add-ons like
VirtualBox - if you use it's modules, you must install a new version of them
to get support for the new Xorg ABI.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Engineering - http://blogs.oracle.com/alanc
_______________________________________________
openindiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
