[arch-general] vbox - X won't start -> no screens -> "vboxvideo" (module requirement mismatch, 0)
Guys, I don't know if this is the new xorg sever upgrade or what, but after updates, X will not start on my archlinux guest in vitrualbox. I have reinstalled virtualbox-archlinux-additions (4.1.8-2) and still no joy. I get the following when trying startx: X.Org X Server 1.12.0 Release Date: 2012-03-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.9-1-ARCH i686 Current Operating System: Linux tdepv 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:10:44 UTC 2012 i686 Kernel command line: root=/dev/disk/by-uuid/ed9a0dc2-64b7-4e14-884c-bec2ad12f8d1 ro vga=0x31a Build Date: 05 March 2012 06:02:28AM Current version of pixman: 0.24.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 12 17:12:10 2012 (==) Using config directory: "/etc/X11/xorg.conf.d" (EE) module ABI major version (11) doesn't match the server's version (12) Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. So looking at Xorg.0.log I get: [ 51.021] (EE) module ABI major version (11) doesn't match the server's version (12) [ 51.028] (EE) Failed to load module "vboxvideo" (module requirement mismatch, 0) [ 51.037] (EE) Failed to load module "vesa" (module does not exist, 0) [ 51.050] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 51.050] (EE) No drivers available. I have vboxvideo.so in /usr/lib/xorg/modules/drivers/, so I'm a bit stumped on the mismatch. Does this mean I have to install another version of virtualbox or what? -- David C. Rankin, J.D.,P.E.
ma, 2012-03-12 kello 17:18 -0500, David C. Rankin kirjoitti:
I have vboxvideo.so in /usr/lib/xorg/modules/drivers/, so I'm a bit stumped on the mismatch. Does this mean I have to install another version of virtualbox or what?
I would say you need to recompile the virtualbox package, so that the driver gets built for version Xorg 1.12, instead of 1.11. Then just install the compiled virtualbox-archlinux-additions package. You might want to read this. https://wiki.archlinux.org/index.php/ABS_-_The_Arch_Build_System
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/12/2012 05:37 PM, Jesse Juhani Jaara wrote:
I would say you need to recompile the virtualbox package, so that the driver gets built for version Xorg 1.12, instead of 1.11. Then just install the compiled virtualbox-archlinux-additions package. You might want to read this. https://wiki.archlinux.org/index.php/ABS_-_The_Arch_Build_System
Thanks Jesse, I'm familiar with ABS, and I can build a new vbox (from AUR PUEL licensed ver.) or virtualbox-archlinux-additions, but what I was hoping to learn was exactly what broke. If I understand you correctly, it was the update within virtual box of Xorg 1.11 -> 1.12 that left the guest unable to start X due to the vboxvideo.so not being compatible with 1.12. With that information, then and knowing the vboxvideo.so was provided by virtualbox-archlinux-additions (courtesy of pacman), it looks like virtualbox-archlinux-additions needs to be rebuilt based on the new X. The question then becomes, if the new X breaks vboxvideo.so, what is it that triggers the packager to know it's broken and needs rebuilding? User reports? Some kind of automated ldd check? Just curious and trying to learn... - -- David C. Rankin, J.D.,P.E.
ma, 2012-03-12 kello 21:52 -0500, David C. Rankin kirjoitti:
If I understand you correctly, it was the update within virtual box of Xorg 1.11 -> 1.12 that left the guest unable to start X due to the vboxvideo.so not being compatible with 1.12. Yes that is the driver cimpiled for xorg 1.11 API I did a svn checkout with a support for 1.12. [1]Here is the compile driver for 1.12. It may or may not work. Decompres it to /usr/lib/xorg/modules/drivers/vboxvideo.so
what is it that triggers the packager to know it's broken and needs rebuilding? User reports? Some kind of automated ldd check? Just curious and trying to learn... User reports unless the packager him/herself notices that first
This are bad news, since I've got less time and much work to set up several Linux installs to my needs. So I'll stop upgrading Arch Linux for a while. - Ralf [spinymouse@archlinux ~]$ pacman -Qi xorg-server Name : xorg-server Version : 1.11.4-1 [spinymouse@archlinux ~]$ sudo pacman -Syu Targets (48): acpid-2.0.14-2 freetype2-2.4.9-1 glproto-1.4.15-1 grep-2.11-2 gstreamer0.10-0.10.36-1 gstreamer0.10-bad-0.10.23-1 gstreamer0.10-bad-plugins-0.10.23-1 gstreamer0.10-base-0.10.36-1 gstreamer0.10-base-plugins-0.10.36-1 gstreamer0.10-good-0.10.31-1 gstreamer0.10-good-plugins-0.10.31-1 gstreamer0.10-ugly-0.10.19-1 gstreamer0.10-ugly-plugins-0.10.19-1 imagemagick-6.7.6.0-1 inputproto-2.2-1 kdebase-runtime-4.8.1-2 lib32-libglapi-8.0.1-1 lib32-libpciaccess-0.13-1 lib32-libx11-1.4.99.1-1 lib32-libxcb-1.8.1-1 lib32-libxi-1.6.0-1 lib32-mesa-8.0.1-1 libgig-3.3.0-2 libglapi-8.0.1-2 libpciaccess-0.13-1 libtiff-4.0.1-1 libx11-1.4.99.1-1 libxcb-1.8.1-1 libxft-2.3.0-2 libxi-1.6.0-1 libxt-1.1.2-2 linuxsampler-1.0.0-2 man-pages-3.37-1 mesa-8.0.1-2 mpfr-3.1.0.p7-1 openssl-1.0.0.h-1 poppler-0.18.4-1 poppler-glib-0.18.4-1 thunar-1.2.3-5 virtualbox-4.1.10-1 virtualbox-additions-4.1.10-1 virtualbox-modules-4.1.10-1 virtualbox-source-4.1.10-1 xcb-proto-1.7-2 xf86-input-evdev-2.7.0-1 xf86-video-nv-2.1.18-5 xorg-server-1.12.0-1 xorg-server-common-1.12.0-1
This only applys to VB guest systems your host systems can have 1.12
On Wed, 2012-03-14 at 20:36 +0200, Jesse Jaara wrote:
This only applys to VB guest systems your host systems can have 1.12
:D Thank you, guest here is M$. I haven't read it carefully enough. On Wed, 2012-03-14 at 19:42 +0100, Lukáš Jirkovský wrote:
… and meanwhile virtualbox has been updated to 4.1.10 which, according to the release notes, supports xorg-server 1.12
:) - Ralf
On 14 March 2012 19:29, Ralf Mardorf
This are bad news, since I've got less time and much work to set up several Linux installs to my needs. So I'll stop upgrading Arch Linux for a while.
- Ralf
… and meanwhile virtualbox has been updated to 4.1.10 which, according to the release notes, supports xorg-server 1.12
On 03/13/2012 12:37 AM, Jesse Juhani Jaara wrote:
ma, 2012-03-12 kello 17:18 -0500, David C. Rankin kirjoitti:
I have vboxvideo.so in /usr/lib/xorg/modules/drivers/, so I'm a bit stumped on the mismatch. Does this mean I have to install another version of virtualbox or what?
I would say you need to recompile the virtualbox package, so that the driver gets built for version Xorg 1.12, instead of 1.11. Then just install the compiled virtualbox-archlinux-additions package. You might want to read this. https://wiki.archlinux.org/index.php/ABS_-_The_Arch_Build_System
vboc additions do not work with x-server 1.12 -- Ionuț
participants (6)
-
David C. Rankin
-
Ionut Biru
-
Jesse Jaara
-
Jesse Juhani Jaara
-
Lukáš Jirkovský
-
Ralf Mardorf