[SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

milasch · 2012-03-13 14:55:47

[   627.412] (==) Matched vboxvideo as autoconfigured driver 0
[   627.412] (==) Matched vesa as autoconfigured driver 1
[   627.412] (==) Matched fbdev as autoconfigured driver 2
[   627.412] (==) Assigned the driver to the xf86ConfigLayout
[   627.412] (II) LoadModule: "vboxvideo"
[   627.412] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[   627.413] (II) Module vboxvideo: vendor="Oracle Corporation"
[   627.413] 	compiled for 1.5.99.901, module version = 1.0.1
[   627.413] 	Module class: X.Org Video Driver
[   627.413] 	ABI class: X.Org Video Driver, version 11.0
[   627.413] (EE) module ABI major version (11) doesn't match the server's version (12)
[   627.413] (II) UnloadModule: "vboxvideo"
[   627.413] (II) Unloading vboxvideo
[   627.413] (EE) Failed to load module "vboxvideo" (module requirement mismatch, 0)
[   627.413] (II) LoadModule: "vesa"
[   627.414] (WW) Warning, couldn't open module vesa
[   627.414] (II) UnloadModule: "vesa"
[   627.414] (II) Unloading vesa
[   627.414] (EE) Failed to load module "vesa" (module does not exist, 0)
[   627.414] (II) LoadModule: "fbdev"
[   627.414] (WW) Warning, couldn't open module fbdev
[   627.414] (II) UnloadModule: "fbdev"
[   627.414] (II) Unloading fbdev
[   627.414] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   627.414] (EE) No drivers available.
[   627.414] 
Fatal server error:
[   627.414] no screens found

Just want to confirm. In the meantime I'm downgrading xorg to 1.11.

Last edited by milasch (2012-03-14 19:27:09)

milasch · 2012-03-13 15:06:56

Yup, apparently vboxvideo module isn't compatible with xorg 1.12 yet. So watch out

Last edited by milasch (2012-03-13 15:08:18)

toadicus · 2012-03-13 16:13:17

Noob question: Is there a simple way to downgrade xorg? I've tried downgrade and downgrader and just pacman'ing the old xorg-server package myself, but none of them seem able to deal with the dependencies (xf86-video-* et al) that need to be downgraded as well.

milasch · 2012-03-13 17:11:30

toadicus wrote:

Noob question: Is there a simple way to downgrade xorg? I've tried downgrade and downgrader and just pacman'ing the old xorg-server package myself, but none of them seem able to deal with the dependencies (xf86-video-* et al) that need to be downgraded as well.

I only had to downgrade 3 packages:

[2012-03-13 11:01] Running 'pacman -U xorg-server-common-1.11.4-1-i686.pkg.tar.xz'
[2012-03-13 11:01] upgraded xorg-server-common (1.12.0-1 -> 1.11.4-1)
[2012-03-13 11:02] Running 'pacman -U xf86-input-evdev-2.6.0-4-i686.pkg.tar.xz'
[2012-03-13 11:02] upgraded xf86-input-evdev (2.7.0-1 -> 2.6.0-4)
[2012-03-13 11:02] Running 'pacman -U xorg-server-1.11.4-1-i686.pkg.tar.xz'
[2012-03-13 11:02] upgraded xorg-server (1.12.0-1 -> 1.11.4-1)

Basically:

# cd /var/cache/pacman/pkg
# pacman -U xorg-server-common-1.11.4-1-i686.pkg.tar.xz
# pacman -U xf86-input-evdev-2.6.0-4-i686.pkg.tar.xz
# pacman -U xorg-server-1.11.4-1-i686.pkg.tar.xz

But only if you have those packages available, of course... If you ran pacman -Scc you cleaned your cache and you'd have to look for them.

stevepa · 2012-03-13 22:30:09

milasch wrote:

toadicus wrote:
Noob question: Is there a simple way to downgrade xorg? I've tried downgrade and downgrader and just pacman'ing the old xorg-server package myself, but none of them seem able to deal with the dependencies (xf86-video-* et al) that need to be downgraded as well.
I only had to downgrade 3 packages:
[2012-03-13 11:01] Running 'pacman -U xorg-server-common-1.11.4-1-i686.pkg.tar.xz'
[2012-03-13 11:01] upgraded xorg-server-common (1.12.0-1 -> 1.11.4-1)
[2012-03-13 11:02] Running 'pacman -U xf86-input-evdev-2.6.0-4-i686.pkg.tar.xz'
[2012-03-13 11:02] upgraded xf86-input-evdev (2.7.0-1 -> 2.6.0-4)
[2012-03-13 11:02] Running 'pacman -U xorg-server-1.11.4-1-i686.pkg.tar.xz'
[2012-03-13 11:02] upgraded xorg-server (1.12.0-1 -> 1.11.4-1)
Basically:
# cd /var/cache/pacman/pkg
# pacman -U xorg-server-common-1.11.4-1-i686.pkg.tar.xz
# pacman -U xf86-input-evdev-2.6.0-4-i686.pkg.tar.xz
# pacman -U xorg-server-1.11.4-1-i686.pkg.tar.xz
But only if you have those packages available, of course... If you ran pacman -Scc you cleaned your cache and you'd have to look for them.

Newbie here also on virtualbox. Performing these three pacman -U's did it for me.

I guess I am glad this happened, because I need to an easy introduction to fixing things that fail because of incompatible upgrades.

I guess in a business's production environment (not me), then the pacman -Syu would be done on an identical test machine, then if that worked, the same thing would happen on the production machine. Just rambling...

take it easy
steve.

Last edited by stevepa (2012-03-13 22:46:55)

whoop · 2012-03-14 00:31:40

When I update xorg-server to the latest version I can't get gdm or gnome-shell running on any VirtualBox guest anymore.
Output is:
gdm-binary[576]: WARNING: GdmDisplay: display lasted 0.074494 seconds
.....

maximum number of X display failures reached: check X server log for errors

Is there something I can do, before I file a bugreport?
Maybe someone know a workaround I am missing...

Last edited by whoop (2012-03-14 00:51:26)

whoop · 2012-03-14 00:51:09

sorry I overlooked this issue being discussed allready....

whoop · 2012-03-14 00:53:08

I noticed this as well... So what should we de (aside from downgrading). Wait, bugreport, something else?
should this have displayed a dependency issue on pacman -Syu?

Last edited by whoop (2012-03-14 00:56:34)

ewaller · 2012-03-14 02:13:59

Moderator: Merged threads (posts 6 & 7)

milasch · 2012-03-14 02:15:17

stevepa wrote:

Newbie here also on virtualbox. Performing these three pacman -U's did it for me.
I guess I am glad this happened, because I need to an easy introduction to fixing things that fail because of incompatible upgrades.
I guess in a business's production environment (not me), then the pacman -Syu would be done on an identical test machine, then if that worked, the same thing would happen on the production machine. Just rambling...
take it easy
steve.

Excellent reading material for you my friend: https://bbs.archlinux.org/viewtopic.php?id=57205

I have subscribed to the announcement list to see if it helps me avoid breaking my system. Well, and if you're behind virtualbox, snapshots would be a great feature to try things out.

milasch · 2012-03-14 02:20:32

whoop wrote:

I noticed this as well... So what should we de (aside from downgrading). Wait, bugreport, something else?
should this have displayed a dependency issue on pacman -Syu?

I'm sure you can notify or look if this issue has been notified already on virtualbox.org.

Anyhow, I wouldn't be desperate since I'm pretty sure they're aware xorg 1.12 has been released and they have to work on their modules to bring it back to compatibility, but you never know.

pklingem · 2012-03-14 03:58:57

it appears I picked an inopportune time to install arch as a VirtualBox guest as I had no choice of Xorg versions to install. Is it fair to say that my options are to figure out how to downgrade Xorg to 1.11 (despite 1.12 being the initial installation version), or to wait until VirtualBox updates vboxvideo to support 1.12?

BlackIkeEagle · 2012-03-14 07:14:48

if you are so unlukky as pklingem you can use the xorg111 repository voilo keeps because catalyst is also not yet supporting xorg 1.12

edit your pacman.conf and add this before the other repositories

[xorg111]
Server = http://catalyst.apocalypsus.net/repo/xorg111/$arch

if you do a pacman -Syu with this you will see notifications about xorg-server xorg-server-common and xf86-input-evdev being newer than available in the repositories

install all of those with pacman -S xf86-input-evdev xorg-server xorg-server-common [and maybe more if you have more]

brebs · 2012-03-14 09:24:33

Upgrade to virtualbox 4.1.10

added support for X.Org Server 1.12

milasch · 2012-03-14 13:37:57

brebs wrote:

Upgrade to virtualbox 4.1.10
added support for X.Org Server 1.12

And upgrade your https://www.archlinux.org/packages/?nam … -additions, as well as https://www.archlinux.org/packages/?sor … =&limit=50

Last edited by milasch (2012-03-14 13:40:37)

stevepa · 2012-03-14 13:39:05

After upgrading Virtualbox and pacman -Syu today, everything works!

stevepa · 2012-03-14 13:46:44

milasch wrote:

stevepa wrote:
Newbie here also on virtualbox. Performing these three pacman -U's did it for me.
I guess I am glad this happened, because I need to an easy introduction to fixing things that fail because of incompatible upgrades.
I guess in a business's production environment (not me), then the pacman -Syu would be done on an identical test machine, then if that worked, the same thing would happen on the production machine. Just rambling...
take it easy
steve.
Excellent reading material for you my friend: https://bbs.archlinux.org/viewtopic.php?id=57205
I have subscribed to the announcement list to see if it helps me avoid breaking my system. Well, and if you're behind virtualbox, snapshots would be a great feature to try things out.

Thanks for those links.

I really should use snapshots before any upgrade.

On my non-VB box, I am still suffering throught that 30sec boot delay, somehow caused by loading modules, starting about a month ago. The delay appears harmless but I look forward to when that is fixed upstream. I have not tried to downgrade packages to working versions yet.

thanks
steve.

pklingem · 2012-03-14 18:50:10

as of today:

pacman -Syu

solved my problem

xzy3186 · 2012-03-15 04:30:58

I have upgraded all the packages listed in #15 but after startx I still had the same error messages as before (the same as #1). I checked the package version of virtualbox-archlinux-additions and virtualbox-archlinux-mudules which are indeed 4.1.10. After downgrading xorg from 1.12 to 1.11, the startx works again. Does anybody know what might be the problem?

wonder · 2012-03-15 08:32:47

xzy3186 wrote:

I have upgraded all the packages listed in #15 but after startx I still had the same error messages as before (the same as #1). I checked the package version of virtualbox-archlinux-additions and virtualbox-archlinux-mudules which are indeed 4.1.10. After downgrading xorg from 1.12 to 1.11, the startx works again. Does anybody know what might be the problem?

maybe you really have some old stalled files used my virtualbox method instalation for guest using ./VBox..run ? Check out the path for vboxvideo.so in Xorg.0.log and run pacman -Qo on it.

Nha · 2012-03-15 09:38:46

I don't get why I see vboxvideo being loaded or being attempted to load in other people their Xorg logs as this is not the case here... It always used the vesa driver, no mention of vboxvideo in the Xorg log nor the dmesg log.

I'm still stuck on a silly resolution on my Arch VM, a 4:3 resolution is quite annoying on a 16:9 screen

Using virtualbox 4.1.10 on a win7 host, using the 4.1.10 archlinux guest additions and modules packages.

Last edited by Nha (2012-03-15 09:39:11)

xzy3186 · 2012-03-15 10:15:24

wonder wrote:

xzy3186 wrote:
I have upgraded all the packages listed in #15 but after startx I still had the same error messages as before (the same as #1). I checked the package version of virtualbox-archlinux-additions and virtualbox-archlinux-mudules which are indeed 4.1.10. After downgrading xorg from 1.12 to 1.11, the startx works again. Does anybody know what might be the problem?
maybe you really have some old stalled files used my virtualbox method instalation for guest using ./VBox..run ? Check out the path for vboxvideo.so in Xorg.0.log and run pacman -Qo on it.

Great! you are right! I installed guest addition by running something like "./VBox...run" long time ago, which left a file called vboxvideo_drv.so in my system. This is exactly the file screwing up my system. After removing it by hand, everything work well. Thank you very much.

Arch Linux

#1 2012-03-13 14:55:47

[SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#2 2012-03-13 15:06:56

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#3 2012-03-13 16:13:17

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#4 2012-03-13 17:11:30

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#5 2012-03-13 22:30:09

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#6 2012-03-14 00:31:40

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#7 2012-03-14 00:51:09

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#8 2012-03-14 00:53:08

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#9 2012-03-14 02:13:59

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#10 2012-03-14 02:15:17

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#11 2012-03-14 02:20:32

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#12 2012-03-14 03:58:57

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#13 2012-03-14 07:14:48

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#14 2012-03-14 09:24:33

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#15 2012-03-14 13:37:57

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#16 2012-03-14 13:39:05

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#17 2012-03-14 13:46:44

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#18 2012-03-14 18:50:10

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#19 2012-03-15 04:30:58

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#20 2012-03-15 08:32:47

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#21 2012-03-15 09:38:46

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

#22 2012-03-15 10:15:24

Re: [SOLVED] Xorg 1.11.4-1 upgrading to 1.12.0-1 brings vboxvideo incom...

Board footer