Opened a new bug for 13.04 #112
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
(after LUKS install)
To manage
Tomas: It's probably best to open a new bug for it, however please
make sure it includes at least the following:
Can you confirm exactly what your setup is:
Is this under KVM - if so what host and what video card config
What image exactly did you use as the install?
Were you using
This bug is back with 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
(after LUKS install)
To manage
** Branch linked: lp:ubuntu/quantal-proposed/linux-lowlatency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
This bug was fixed in the package linux - 3.5.0-16.24
---
linux (3.5.0-16.24) quantal-proposed; urgency=low
[ Andy Whitcroft ]
* SAUCE: ata_piix: add a disable_driver option
- LP: #994870
[ Christian König ]
* (pre-stable) drm/radeon: make 64bit fences more robust v3
Testing today (on a Xen guest) showed that the X crash on unity startup
seems to be resolved. On the KVM side at least startup works, while I
get occasional crashed that look similar to the initial crash (maybe
that is a result of a slower machine trying to cope with llvm-pipe). But
in the light
@Dmitrijs, I don't have it in a PPA or elsewhere right now because I am
not really happy with the current results. Due to the delay between
releasing and reacquiring the framebuffer, X rarely gets up and I saw
the VTs be stuck, too (had to ssh in and restart lightdm). The best
work-around right
Stefan, can we please just get the cirrus drm driver disabled in the
quantal kernel until this is resolved? Currently it adds nothing but
bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Steve, that is not correct. Actually the cirrus driver + modeset X
driver is the only way not to have X crash as soon as unity starts.
Though I must admit that it would at least put the users of KVM and Xen
into the same pain.
--
You received this bug notification because you are a member of
Dmitrijs, if you want to play around:
http://people.canonical.com/~smb/lp1038055/ (you have been warned ;))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise
Unsigned hand-crafted debs of linux kernel =) /me like!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
(after LUKS
So asking around, grub (even in Precise) passes mode 0x70 (which happens
to be efifb) as a generic framebuffer setup and the usage of efifb is
more in a generic way than EFI. For real hw grub uses an internal VBE
driver. The reason we never had any issues was that without the cirrus
DRM driver
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
(after LUKS install)
To manage notifications
** Tags removed: rls-q-incomming
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
@ Stefan is there a PPA where I can test the patch? That would be great,
as I am one of the affected people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise
Question is why is a kvm VM considered an EFI capable system (gfx). This
sounded to be only MAC. Of course as a secondary issue we have the
unsolved problem of replacing a framebuffer device which is not (rumors
speak of issues) synchronizing the release and re-acquiring of
resources.
--
You
Not sure this is really meant to be, but it seems the efifb is
initialized because grub passes this VGA type to the kernel. When I
uncomment the line in /etc/default/grub that sets GRUB_TERMINAL=console,
then the efifb driver is not loaded. There is a early error message that
video mode could not
The efifb initialization by grub is deliberate, to try to provide
flicker-free boot on efi-capable systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise
It really is the problem of remove_conflicting_framebuffers() returning
before the removed fb's driver has released its resources. As it is
visible below efifb seems to take quite a while (sometimes?).
[0.189597] efifb: probing for efifb
[0.189597] efifb: framebuffer region reserved
[
So maybe some interaction with plymouth? Unfortunately it is not really
consistent in behaviour. This morning I got the usual lightdm ok and
switch to vt shows corruption. Then I played with some config options:
remove splash and vt_handoff resulted in lightdm ok and vt ok (though high
And right now even unity desktop came up with the default options.
Switching from desktop to VT works and back. Apport reported a (likely
previous) X crash which I let create bug #1046204. Does this miracle
happen to others, too (after fiddling with the boot options like above)?
--
You received
Stefan
I can reproduce this issue fairly reliably using the scripts that I
wrote for testing ubuntu server on iscsi root.
I don't have to fiddle with the boot options at-all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
James, I can also reproduce it most of the time just by booting. It just is not
always consistent. After the two good reboot runs I did shut down the guest
and then start it again which brought things back to failing and this time
removing quiet vt_handoff does not work either. In this case
Hm, I think that might be missing hint. I have a ssh server running to
log in that way (using the nomodeset and the vt could be installed in
the broken state). And I stumbled into the working state again.
Comparing the xorg.log files I found that when things work, the cirrus
module seems to have
Still not exactly sure how this races, though some things are a bit odd here.
Generally the approach to replace the EFI FB console looks like what i915 would
do, too. Using remove_conflicting_framebuffers() the EFI FB gets removed. Then
in cirrus_driver_load() it first request the resources for
The cirrus driver is build out of the CONFIG_DRM_CIRRUS_QEMU
configuration option which is new in Quantal. It may well be worth
bashing it off for the moment. That said another bug on this issue
claims to have fixes for the X server for this: LP#1039648. Perhaps
someone could test the packages
Andy,
On Tue, Sep 04, 2012 at 05:09:28PM -, Andy Whitcroft wrote:
The cirrus driver is build out of the CONFIG_DRM_CIRRUS_QEMU
configuration option which is new in Quantal. It may well be worth
bashing it off for the moment. That said another bug on this issue
claims to have fixes for
I wonder whether that is to some degree related to the doings of the x
driver, too. When there still was a clash, I got a drm'ed console as the
fallback of lightdm not starting (slightly unusable because it chooses
quite a high resolution). I can confirm now that lightdm comes up
readable but the
No, this has *nothing* to do with X. This is breaking the console way
before X would ever start - it's preventing *plymouth* from running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
I'm seeing this without LUKS as well (server install using the 2012-09-01 iso);
first reboot after install fails
(stick at the text mode purple screen with 0-1 dot lit); using an LVM (but no
luks) install.
It did boot after about the 3rd try on one vm, and the 2nd try on the other vm,
but I can
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
If you are comfortable with
Also, this has been added to the kernel team hot list for review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
As a work-around, you may be able to blacklist the cirrus kernel module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus
On Tue, Aug 28, 2012 at 07:09:14PM -, Joseph Salisbury wrote:
As a work-around, you may be able to blacklist the cirrus kernel module.
Given that KVM is the dominant use case for the cirrus driver, can I suggest
that this be done in the kernel package itself by not building the broken
driver
plymouth itself doesn't seem to be doing anything wrong; it just doesn't
have a usable video device. So this is a bug in the kernel cirrus
driver.
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v',
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038055
Title:
graphics fail to initialise correctly, in kvm with cirrus graphics
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
Using:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/
linux-headers-3.6.0-030600rc3-generic_3.6.0-030600rc3.201208221735_amd64.deb
linux-headers-3.6.0-030600rc3_3.6.0-030600rc3.201208221735_all.deb
Steve, if you can could you please test it in your VM as well... cause I
don't feel like triggering full git bisect against precise - quantal
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm. So I just installed http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.6-rc3-quantal/linux-
image-3.6.0-030600rc3-generic_3.6.0-030600rc3.201208221735_amd64.deb and
it worked fine for me.
$ cat /proc/fb
0 EFI VGA
$
The cirrus drm fb driver doesn't get mentioned in dmesg at all.
--
You
Whoops, I didn't have linux-image-extra installed. Once I install this
(bringing in the cirrus drm driver again), it breaks in the same way.
So yes, I confirm Dmitrijs's result.
Is this cirrus drm driver new? Perhaps it should be disabled in the
package for now?
--
You received this bug
42 matches
Mail list logo
