| Summary: | x11-driver-video-qxl-0.0.17-3.mga3 ABI mismatch | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Chris Mayo <aklhfex> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | adamw, stormi-mageia, thierry.vignaud, tmb |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Chris Mayo
2013-05-24 21:51:42 CEST
Manuel Hiebel
2013-05-24 23:15:07 CEST
CC:
(none) =>
thierry.vignaud, tmb This is because this driver failed to rebuild with new X.org server 1.13 last year. And its distributor (Red Hat) failed to make any new release since... Today, I've made it to compile on Cauldron with X.org server 1.14: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/SRPMS/core/updates_testing/x11-driver-video-qxl-0.1.1-0.20130312gita474a71.mga4.src.rpm I'm currently pushing it for Mageia 3, build against X.org server 1.13 (in the "Core Updates Testing" medium) You can: - either select a different video card type for this VM - or pick a different driver in XFdrake (such as vesa or fbdev) - or try the updated package once it lands on your favorite mirror (should be OK by tomorrow) (it's named x11-driver-video-qxl-0.1.1-0.20130312gita474a71.mga3) In the later case, you'll have to enable the "Core Updates Testing" medium. eg: MEDIA="Core Updates Testing" urpmi.update --no-ignore $MEDIA urpmi.update $MEDIA urpmi x11-driver-video-qxl urpmi.update --ignore $MEDIA I would like if you could report if this updated driver works. Thanks Keywords:
(none) =>
NEEDINFO A shorter way to install: urpmi.update "Core Updates Testing" urpmi --media "Core Updates Testing" x11-driver-video-qxl Thanks for the suggestions. I tried x11-driver-video-qxl-0.1.1-0.20130312gita474a71.mga3. It fixes the ABI mismatch but now gives another error: [ 5.260] (II) LoadModule: "qxl" [ 5.260] (II) Loading /usr/lib64/xorg/modules/drivers/qxl_drv.so [ 5.260] (EE) Failed to load /usr/lib64/xorg/modules/drivers/qxl_drv.so: /usr/lib64/xorg/modules/drivers/qxl_drv.so: undefined symbol: qxl_enter_vt_kms [ 5.260] (II) UnloadModule: "qxl" [ 5.260] (II) Unloading qxl [ 5.260] (EE) Failed to load module "qxl" (loader failed, 7) I'm pushing an updated driver: x11-driver-video-qxl-0.1.1-0.20130514git77a1594.1.mga3 Can you test it once it lands on your favorite mirror (should be OK by tomorrow)? qxl-0.1.1-0.20130514git77a1594.1.mga3 gives me same error as Comment 3.
Manuel Hiebel
2013-06-08 16:51:36 CEST
Keywords:
NEEDINFO =>
(none) So, I just installed Mageia 3 from the 64-bit DVD to test something unrelated, and X failed to start at all. From Xorg.0.log, X detects that I'm running in a KVM with a qxl adapter and tries to load the qxl driver, but it is not present, and so it just bails.
There's no x11-driver-video-qxl package installed or, apparently, available from the stock repos ("Core Release", "Nonfree Release").
FWIW there has been an official 0.1.1 release now, and that's what Fedora 20 is using...CC:
(none) =>
adamw It's not included in the DVD but it's available from the full mirrors if you add them from MCC. I've just altered x11-driver-video so that it pulls qxl too. Thanks for the report. 0.1.1 already is in Cauldron. cool, I'll try and find a bit of time at some point to check a future mageia 4 test build and make sure it works OOTB in fedora virt-manager. Thierry, is the package in updates/testing an update candidate? CC:
(none) =>
stormi No since it fails in comment #5 Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |