lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: xserver-xorg-video-intel (Ubuntu Lucid)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
whi
Since kernel updates improved the situation, I'm closing the main task
and leaving a Lucid task. I suspect this is really a kernel drm bug so
perhaps this should be filed against the kernel instead.
** Also affects: xserver-xorg-video-intel (Ubuntu Lucid)
Importance: Undecided
Status: N
Hello Chris,
I agree that this is not a showstopper.
I think that the problem is not only the memory copying from Plymouth to X but
also the correct X init.
I do not understand why it really ignores the xorg.conf settings.
For the present situation, that is better, I believe that the kernel upg
Thanks for that video; I've now got a much better idea of what's
happening.
So, it looks like there's a problem with copying the framebuffer from
plymouth to X. That looks ugly, but isn't particularly concerning.
Thanks.
I probably won't look into this in the next week, given the priority,
but i
Hello,
here is a video about the boot process:
http://www.youtube.com/watch?v=L9atdI5qnIQ
Attached are again dmesg-debug.log and Xorg.0.log
Daniel
On 04/09/2010 08:18 AM, Chris Halse Rogers wrote:
> Ok. Can you please boot, adding the kernel option “drm.debug=0x04”
> after “quiet splash” on th
Hello,
Atached you have the files requested and my xorg.conf
However the system set the resolution to 1024x768 as xvidtune output shows:
n...@marauder:~$ xvidtune
Vendor: Monitor Vendor, Model: Monitor Model
Num hsync: 1, Num vsync: 1
hsync range 0: 49.30 - 49.30
vsync range 0: 59.90 - 59.90
Ok. Can you please boot, adding the kernel option “drm.debug=0x04”
after “quiet splash” on the kernel boot line? That will make the intel
kernel module print what it's doing to dmesg. Could you boot like this,
run “dmesg > dmesg-debug.log” from a terminal, and attach this file, and
the matching
Hello Chris,
The incorrect display still persist.
In the moment when X and GDM start the Plymouth purple boot screen is
stretched in top left corner, then the image is corrupted in horizontal
repeating bars. Then the default GDM background appears and everything
gos back to normal... well excep
But the incorrect display during boot is still present with 2.6.32-19?
--
[gm45] Often freezes before GDM login screen appears
https://bugs.launchpad.net/bugs/528026
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu
Hello,
I can confirm that with 2.6.32-19 bug #535640 does not reproduce the
anymore.
Daniel
--
[gm45] Often freezes before GDM login screen appears
https://bugs.launchpad.net/bugs/528026
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Hi Bryce,
I have done a workaround for this. I have created a /etc/X11/xorg.conf starting
from 'Xorg -configure' output.
It solved partially the problem (no more crash at startup).
Still at shutdown the Ubuntu purple screen is displayed only at top-left corner
in about 1/4 of the screen.
I have
** Summary changed:
- Often freezes before GDM login screen appears
+ [gm45] Often freezes before GDM login screen appears
--
[gm45] Often freezes before GDM login screen appears
https://bugs.launchpad.net/bugs/528026
You received this bug notification because you are a member of Ubuntu-X,
wh
12 matches
Mail list logo
