** Changed in: gdm (Ubuntu Lucid)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: gdm (Ubuntu Lucid)
Status: Triaged => In Progress
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
** Changed in: gdm (Ubuntu Lucid)
Importance: Undecided => High
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop
** Changed in: gdm (Ubuntu Lucid)
Milestone: None => ubuntu-10.04.2
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
de
We should also backport this to lucid.
** Also affects: gdm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: gdm (Ubuntu Lucid)
Status: New => Triaged
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because
I have no idea if this is normal but I do not have a "splash" file in
"/etc/initramfs-tools/conf.d/"
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
@Anouar Mansour: And that's without having the drm modules loaded in
your initramfs? (IE: you've removed the FRAMEBUFFER line from /etc
/initramfs-tools/conf.d/splash and re-run update-initramfs?)
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notific
More info if needed: Running gdm 2.30.5-0ubuntu4
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
Just to confirm, video works on today's build.
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.c
Not sure whether this is sufficient; if not, please cry out and reopen.
gdm (2.30.5-0ubuntu4) maverick; urgency=low
* debian/gdm.upstart: Do not already fire on a framebuffer device. When a
real DRM driver gets loaded later on, X will be started too early to catch
it. This should go a l
Could somebody who feel comfortable on the change to do claim this bug
and upload?
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mail
Dropping the start condition on fb0 seems fine to me; it should help a
lot of people, and doesn't affect boot time on reasonably modern
machines (i. e. with DRM) at all.
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a memb
I've talked with Andy, and he doesn't think that this is related to the
problems they've been tracking down. What we need to do here is to wait
for DRM to be ready before starting X.
Using:
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udevtrigger))
Martin: there can never be any "all video devices are up" case because a
video card can be hotplugged later.
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubun
This bug sounds very like a problem that Andy Whitcroft and Colin Watson
have been tracking as part of their vgafb/efifb work - if I were you, I
would talk to them before taking any action
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification bec
Scott is there any chance you could reply to the previous question?
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
deskto
For merely ignoring framebuffer devices if we have DRM devices, this
would be enough, and more efficient:
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udevtrigger))
However, that would still not fix devices which have two video cards and
X wants to
** Changed in: gdm (Ubuntu Maverick)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
Dell Studio XPS 13 no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Right. So, the underlying problem here appears to be that /dev/fb0,
driven by vesafb, gets tagged as PRIMARY_DEVICE_FOR_DISPLAY=1 and gdm is
starting on fb0 && PRIMARY_DEVICE_FOR_DISPLAY=1. So gdm is starting
before the drm devices are available, and all hell breaks loose.
Reassigning to gdm, as
18 matches
Mail list logo
