|
Bugzilla – Full Text Bug Listing |
| Summary: | Recent upgrade causes maximum 640x480 screen resolution on Virtualbox 4.3.24 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Forgotten User A9YPvv3rEp <forgotten_A9YPvv3rEp> |
| Component: | X.Org | Assignee: | E-mail List <xorg-maintainer-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | wbauer |
| Version: | 201502* | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Virtualbox configuration xml for a previously working VM. | ||
That's because the driver in the virtualbox-guest-x11 package is incompatible to the latest xorg-x11-server. I submitted a fixed package a week ago, but unfortunately Tumbleweed hasn't been published again since then. https://build.opensuse.org/request/show/288020 You could install the virtualbox-guest packages from the Virtualization repo as a workaround: http://download.opensuse.org/repositories/Virtualization/openSUSE_Tumbleweed/ FYI, a new Tumbleweed snapshot has been published today, which contains the fixed package. So it should work now again. Just tried a fresh install using "openSUSE-Tumbleweed-NET-x86_64-Snapshot20150309-Media.iso" downloaded just now which is newer than the one available to download on 2015-03-09 as detailed below. (so I guess a delay between release date and publishing) However the the warning about "Your computer does not fulfill all requirements for a graphical installation..." still happens. I am not convinced the problem is fixed. (In reply to Tim Nicholson from comment #3) > However the the warning about "Your computer does not fulfill all > requirements for a graphical installation..." still happens. > > I am not convinced the problem is fixed. The main point of your bugreport is about the vboxvideo driver not working in the installed system, i.e. that you only get 640x480 because fbdev is used instead, and this is fixed. At least it works here with yesterday's Tumbleweed updates. Regarding the installer: I can reproduce the problem here. The vboxvideo driver seems to be missing completely from the NET medium, the Xorg.0.log contains this: Failed to load module "vboxvideo" (module does not exist, 0) No idea whether this was part of earlier installation medias, but I think the graphical installer should start even without vboxvideo (using fbdev or vesa). And I can reproduce this on real hardware as well by specifying "nomodeset" on the kernel command line when booting from the NET iso (tried on an nvidia system: normally "modesetting" is used and works, with "nomodeset" Xorg fails to start and I only get the text-based installer). Anyway, this is a completely different problem IMHO (and not even related to VirtualBox), and you should probably file a new bug report about it, if it is still reproducible with the next snapshot. > Regarding the installer: I can reproduce the problem here. The vboxvideo
> driver seems to be missing completely from the NET medium, the Xorg.0.log
> contains this:
> Failed to load module "vboxvideo" (module does not exist, 0)
>
> No idea whether this was part of earlier installation medias,
The behaviour is the same for both current DVD and NET installers, and one of them (and I'm not sure which I used for the initial install) certainly started with a graphical installer when I first performed an install.
Since the 640x480 limitation, and the installer X message both related to a similar issue, and both arrived at the same time, I thought it a resonable, and quick, check of restored functionality to see if the installer behaviour had reverted, which as I reported it has not.
However, as you say the issue for an installed system does seem to have been resolved. Updating and rebooting the previous, limited, installation now provides a working driver and full res screen.
So it seems like there is a secondary issue with the installation media as you suggest, although I'm not quite clear what you are saying is the issue, is it that the installer fails to fall back to a fbdev/vesa driver but instead drops straight back to text? I notice they are not options under f3 Video mode, but then nor are they for 13.2 and that boots into a graphical installer OK.
Why wait for another snapshot before reporting it? It seems to have been in at least two already.
(In reply to Tim Nicholson from comment #5) > The behaviour is the same for both current DVD and NET installers, and one > of them (and I'm not sure which I used for the initial install) certainly > started with a graphical installer when I first performed an install. It certainly worked when I last tried the NET installer (inside VirtualBox) as well. But that was some time ago already. > Since the 640x480 limitation, and the installer X message both related to a > similar issue, and both arrived at the same time, I thought it a resonable, > and quick, check of restored functionality to see if the installer behaviour > had reverted, which as I reported it has not. I too thought at first this might be the same issue, i.e. vboxvideo not working. But apparently it isn't, as vboxvideo is not even part of the installation medium. And again, the graphical installer should start without it as well (or if it fails for some reason). > However, as you say the issue for an installed system does seem to have been > resolved. Updating and rebooting the previous, limited, installation now > provides a working driver and full res screen. Thanks for confirming! ;-) > So it seems like there is a secondary issue with the installation media as > you suggest, although I'm not quite clear what you are saying is the issue, > is it that the installer fails to fall back to a fbdev/vesa driver but > instead drops straight back to text? I notice they are not options under f3 > Video mode, but then nor are they for 13.2 and that boots into a graphical > installer OK. Yes, something seems to be wrong with fbdev on the installation medium. It seems to work fine in an installed system though, otherwise Xorg would have failed to start completely and not just give you a 640x480 resolution when vboxvideo was not working. > Why wait for another snapshot before reporting it? It seems to have been in > at least two already. I don't know. I haven't tried the last two snapshots' installation medias. This was just a suggestion though. There might just be incompatible/old packages on the installation medium or something like that, which maybe would resolve itself in the next snapshot. You can of course report it right now as well, if you want to. |
Created attachment 625912 [details] Virtualbox configuration xml for a previously working VM. After a recent upgrade only a 640x480 screen resolution is available. In System Settings->Display and Monitor->Display configuration:- instead of the usual "VBOX0 VBOX Monitor" one now gets "Default" and now resolution option other than 640x480. Also if trying a fresh install from "openSUSE-Tumbleweed-NET-x86_64-Snapshot20150227-Media.iso" only a curses installer is presented with a message about inadequate hardware or unable to start X11. Installation will proceed but again only a 640x480 desktop can be achieved. OpenSUSE 13.2 is continuing to work fine on the same host.