Having trouble getting the box to boot at all with Lucid + xorg-edgers,
as xserver-xorg-video-intel requires mode switching enabled in the
kernel but leaving nomodeset=1 off the options line makes the machine
boot into a video mode that its monitor doesn't support (probably
related to bug 522488).
Same old freeze while using remote desktop viewer.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
Brian: after the last freeze, I accidentally rebooted into your patched
kernel (2.6.31-50-generic) and ran it for a while with the same packages
as in comment #200, and it also froze while I was using remote desktop
viewer. So it looks like even that kernel's horrible GUI sloth doesn't
actually
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'
$ dpkg --status $pkgs | grep Version | uniq uname -rv
Version: 2.4.14-1ubuntu1
Version: 2:2.9.0-1ubuntu2.2~gomyhr1~clipsolids~karmic
Now using Karmic with Jaunty's kernel.
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'; dpkg --status $pkgs | grep Version | uniq
uname -rv
Version: 1:2.4.11-2+karmic3
Version:
It died, but not exactly the same way: this time, there was a sudden
burst of disk activity during which everything went black, then no
response to mouse or keyboard. I've attached Xorg.0.log retrieved via
ssh before I rebooted; looks like X has crashed and then failed on
restart.
** Attachment
20 hours freeze free - I'm prepared to call it stable.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
OK, here I am back in Karmic, and just making sure we're all using the
same stuff:
$ pkgs='libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg'; sudo apt-get install $pkgs /dev/null dpkg
Karmic froze. Now testing Jaunty.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg | grep Version | uniqow...@owner-desktop:~$ dpkg
--status libdrm-dev libdlibdrm-nouveau1 libdrm-nouveau1-dbg libdrm2
I haven't yet seen the familiar freeze, but I've also not really had the
opportunity to work with that box for very long at a stretch, so I'm not
prepared to swear it's stable yet.
--
[i845g] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
xserver-xorg-video-intel-dbg | grep Version | uniq
Version: 2.4.11-0jaunty2
Version: 2:2.7.0-jaunty2
$ uname -rv
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
Now trying your new libdrm with the old driver:
$ dv=2:2.6.3-0ubuntu9; sudo apt-get install xserver-xorg-video-intel=$dv
xserver-xorg-video-intel-dbg=$dv
$ dpkg --status libdrm-dev libdrm-intel1 libdrm-intel1-dbg libdrm-nouveau1
libdrm-nouveau1-dbg libdrm2 libdrm2-dbg xserver-xorg-video-intel
Just to clarify: I've had text console switching misbehaviour both times
I've tried driver version 2:2.7.0-jaunty1. It's not a complete X freeze:
the keyboard stays responsive, I can see the monitor turning its
backlight off and on as I attempt to switch screens, and the monitor's
OSD reports
$ echo deb http://ppa.launchpad.net/brian-rogers/graphics-testing/ubuntu jaunty
main | sudo tee -a /etc/apt/sources.list.d/brian-rogers.list
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 311bdf2d
$ sudo apt-get update
$ sudo apt-get install libdrm-dev libdrm-intel1
12:2.7.0 and friends listed above just froze while looking at a Flash-
based web site, so I guess we're still looking at a driver issue, not a
mesa or libdrm2 one.
I don't have a Jaunty installer disc or any blanks here, but will burn
one before coming to work tomorrow if you think running an
In the meantime, I will grit my teeth, knees and elbows and persist with
testing linux-image-2.6.31-50-generic with a ppa-purged Karmic.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a
Couldn't bear working with linux-image-2.6.31-50-generic any longer. Now
running a fresh Jaunty installation. Will report any freezes.
If there's somebody else whose freeze experience matches mine wrt driver
versions in use, it would be good to put your hand up, as I won't have
access to these
After noticing in Xorg.0.log that 2.8.0 used UXA by default while 2.7.0
was picking EXA, I added
Option AccelMethod UXA
to the Device section in xorg.conf and reinstalled 2.7.0. This has
fixed the early freeze reported in comment #138. I will be working with
this box for the next couple of
2.7.0 just froze in the usual way, while scrolling a remote VNC window
with vinaigre.
I hadn't added your ppa to my sources.list.d; I've just been downloading
and dpkg --installing xserver-xorg-video-intel .debs. So I've just done
sudo apt-get update
sudo dpkg --force-depends --remove
OK, assuming may impair performance in certain specific scenarios
means the same thing as makes the entire desktop experience
unresponsive enough to be intolerable except for debugging purposes it
appears that your patched kernel is working as intended :-)
Will report freezes if any occur.
--
OK, I'll test that idea. There did seem to be a stability improvement
going from the stock xserver-xorg-video-intel to your
7:2.8.99.901-5-g57fc09c version, so I'll start again with that and the
libdrm2 and mesa stuff from your ppa:
$ echo deb
Got the usual freeze while scrolling a Firefox tab. Now testing:
kernel: 2.6.31-19-generic
libgl1-mesa-dri, libgl1-mesa-glx, libglu1-mesa, libosmesa6, mesa-utils:
1:7.4.1-1ubuntu6+karmic
libdrm2: 1:2.4.11-2+karmic3
xserver-xorg-video-intel: 12:2.7.0
What are the chances of a workaround kernel
These boxes are all booting with nomodeset=1 kernel parameters and
1024x768 forced in xorg.conf anyway, per bug 522488.
12:2.7.0 is a doozy! Freezes in the customary fashion before even making
it to the desktop (these boxes are all set to auto-login) on four tries
out of five so far, 15 seconds
After more than 24 hours of stable running on this box,
7:2.8.0-8-g12c5aec froze while attempting to use gdebi to install
7:2.8.0-27-g926c7e7. It also froze once while attempting to launch gedit
on another identical box (I'm trying to set up a batch of elderly school
computers for cost-recovery
Mouse cursor moves, but clicks are ignored and keyboard is locked up
(caps/num lock produce no change in status LEDs, ctrl-alt-Fn doesn't
work). Disk activity continues. If a freeze is going to happen, it will
most often be right when an app is in the process of opening a new
window. I'm using
I've just installed 11:2.8.0, and if it freezes I will watch the desktop
clock for a minute and let you know.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the
I now have two of these boxes on the same bench, both with 11:2.8.0
installed. The one I'm using to try to get today's work done is running
sshd, and the other one is running top on it via ssh. I have pressed
Murphy's Law into service to help these boxes freeze if they're going to
freeze, by also
Thanks, Murphy. Love your work.
11:2.8.0 froze while using Firefox to compose a Gmail. As usual the
mouse cursor remained movable (though stuck in the I-beam shape from the
compose window, this time) but no response to clicks or keyboard. The
desktop clock didn't update. The top listing on the
2.8.99.901-5-g57fc09c just froze, right as gdebi was about to install
2.8.99.901-16-g7e7db7a :-(
Rebooted, installing 2.8.99.901-16-g7e7db7a now.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you
2.8.99.901-16-g7e7db7a froze fairly quickly, as expected (playing Klondike,
fwiw).
Now trying 2.8.0-47-ge903b3e.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is
2.8.0-47-ge903b3e froze. Trying 2.8.0-8-g12c5aec.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
No freeze so far with 2.8.0-8-g12c5aec. Have to go now; will leave this
machine running and check it again in ~12 hours.
--
[i845G] Karmic stops responding a few minutes after log in
https://bugs.launchpad.net/bugs/456902
You received this bug notification because you are a member of Ubuntu-X,
Acer SK20 here.
00:02.0 VGA compatible controller: Intel Corporation
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
kernel: Linux version 2.6.31-19-generic (bui...@palmer) (gcc version
4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC
2010 (Ubuntu
*** This bug is a duplicate of bug 391215 ***
https://bugs.launchpad.net/bugs/391215
As far as I've been able to determine by experiment, the Karmic kernels
completely ignore the vga= option, and rely on EDID to work out what
resolution to use. For those of us unfortunate enough to own
*** This bug is a duplicate of bug 391215 ***
https://bugs.launchpad.net/bugs/391215
Whoops, sorry, missed duplicate status. Cross-posting a link and
additional info.
--
[Karmic] kernel = 2.6.30-10 with vga=791 tty consoles not accessible and not
showing dmesg.
As described in my careless post to a duplicate bug report at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391705/comments/10
this happens to me as well. Acer SK20, Intel 845 graphics so I don't
think it's just an nVidia issue.
The following lines from dmesg (attached) are interesting:
37 matches
Mail list logo
