Description of problem:
Firstboot of Fedora 19 Alpha RC2 (xfce spin) is shown correctly, but after confirmation error is shown (and X won't start):
[drm:qxl_pci_probe] *ERROR* qxl too old, doesn't support client_monitors_config, use xf86-video-qxl in user mode
Steps to Reproduce:
1. Boot Fedora 19 Alpha RC2 XFCE
2. Do the default installation
Thanks for the bug report. The error in dmesg is normal when using F-19 on a non F-19 host. the kms driver needs some features only available in F-19 qemu / spice.
But after that X should start normally using the user space qxl driver.
Can you collect Xorg.0.log and attach it here please?
Created attachment 734653 [details]
Xorg log file
(In reply to comment #2)
> Created attachment 734653 [details]
> Xorg log file
Nothing really interesting there. Do you perhaps get a segfault logged to dmesg ?
Maybe this will be helpful, found in /var/log/messages:
[2.907262] qxl: probe of 0000:00:02.0 failed with error -22
It's also happening in F19 Alpha RC4, XFCE after installation. After switching to VGA in virt-manager, it works. I got a lot "qxl_surface_create: Bad bpp: 1" in Xorg log.
I have the same problem.
But running the release version of F19 under F19.
[ 0.537334] [drm:qxl_pci_probe] *ERROR* qxl too old, doesn't support client_monitors_config, use xf86-video-qxl in user mode
[ 0.537573] qxl: probe of 0000:00:02.0 failed with error -22
A workaround is to start with "nomodeset" in the kernel command line, which forces no loading of qxl.ko, which in turn means the old user space only driver will be used by Xorg.
As an additional hint, in my case the system don't run Xorg. It only runs in console mode, because X is not needed her.
As mentioned in Comment #1, the error message is normal in certain cases but shouldn't cause any problems. Frank, it sounds like you are saying your VM isn't even using an x server, so the error messages are harmless.
Is anyone still seeing x server crashes or failures with an up to date F19? If so, please also try the qxl update here:
And report back.
I assume this is fixed with the latest f19 update, so closing.