** Tags added: kernel-key-gfxpayload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605614
Title:
[ATI] GPU lockup with gfxpayload=keep
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Also affects: grub2 (Ubuntu Maverick)
Importance: Undecided
Status: Fix Released
** Also affects: linux (Ubuntu Maverick)
Importance: Undecided
Status: New
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification
I'm closing the Maverick linux kernel task for now as grub2 switched
back to default to gfxpayload=text for Maverick. However, we do want to
keep the linux task open for Natty. Thanks.
** Changed in: linux (Ubuntu Maverick)
Status: New = Won't Fix
--
[ATI] GPU lockup with
** Branch linked: lp:~ubuntu-core-dev/ubuntu/maverick/grub2/maverick
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package grub2 - 1.98+20100804-4ubuntu1
---
grub2 (1.98+20100804-4ubuntu1) maverick; urgency=low
* Resynchronise with Debian. Remaining changes:
- Adjust for default Ubuntu boot options (quiet splash).
- Default to hiding the menu; holding down
** Branch linked: lp:ubuntu/grub2
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Still having the same startup problems. Just did the last Maverick Meerkat
partial upgrade. Then I tried to reinstall VMWare Tools, but it failed. On
reboot I got a black sccreen. Then I restarted aagain and got the reboot menu.
there I was able to adjust gfxpayload=text and boot up the latest
This is still happening for me on 2.6.35-12.17 ; just get a black screen,
removing the set gfxpayload and I'm back in business.
(Hd4350 on i7)
Dave
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of
This here is with 2.6.35-12.17 and set gfxpayload=keep. At first boot
I get some garbage when X starts (on both my monitors) but after a
reboot X starts up fine. Here is some kernel log from the first
unsuccessful boot:
Jul 30 09:19:48 vorlon kernel: [ 21.819264] [ cut here
I have just installed the new 2.6.35-12.17 kernel. It is now hit and
miss as to whether I can boot to a graphical desktop. I sometimes get
corruption at shutdown. The weird thing is that if I get corruption at
shutdown, it will boot to gdm, yet when the ubuntu logo is displayed at
shutdown, the
I am able to boot now with 2.6.35-11 kernel, but I do get a moment of
screen corruption when the ubuntu splash is supposed to be displayed (
it is not) and then a normal procession to gdm login screen.
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received
We believe that this may be fixed by updates in the latest Maverick
kernel. Could you test that (it should work with lucid userspace).
Please test and report back here. Thanks.
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification
** Tags removed: kernel-candidate
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've checked linux-image-2.6.35-11-generic 2.6.35-11.16 and with set
gfxpayload=keep my box boots again into X. If only bug 605843 would get
fixed soon too, then I could use this kernel and gfxpayload=keep.
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You
I appear to have the same problem with my plain vanilla Compaq C700
laptop (Celeron 560 processor, integrated graphics), except for the
small oddity that the boot process stalls with two side-by-side static
Ubuntu logos displayed in the top half of the screen, rather than having
an entirely dark
** Tags added: kj-triage
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
no image on the monitor after booting Maverick with a newly inserted ATI Radeon
HD 3450.
cannot switch to the text consoles
I'm going to try some workarounds and post back.
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because
Have them same Issue using Maverick Meerkat and 2.6.35.x kernel in
VmWare Fusion Virtual Box 3.1.0 . I have attached the latest 1oo syslog
lines. I can startup Ubuntu MM using set gfxpayload=text instead of set
gfxpayload=keep , but loading is still slow. And of course I would
prefer a more
Have them same Issue using Maverick Meerkat and 2.6.35.x kernel in
VmWare Fusion Virtual Box 3.1.0 . I have attached the latest 100 syslog
lines. I can startup Ubuntu MM using set gfxpayload=text instead of set
gfxpayload=keep , but loading is still slow. And of course I would
prefer a more
Also happens for me; upgrade from Lucid - Radeon HD4350 on an ASRock
P55M Pro
Dave
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I'd like to give the kernel guys an opportunity to debug this; we did
expect some problems switching from VESA to native, but we were never
going to shake them out without giving it a try. I expect it's possible
to blacklist cards from gfxpayload=keep with a bit of work, although I'd
like to save
Nate, it's interesting that you're seeing this in a VM. Perhaps you
could file a separate bug for that, and extract the syslog from that
boot attempt and attach it?
(It may be the same type of issue, but this will probably be driver-
specific to some extent, so I'd like to keep instances for
In addition to comment #4
When I try to use 'set gfxpayload=keep' after my screen goes bad I can get a
terminal with ctl-alt-f2 and login and reboot.
On f1 I get this [drm_radeon_cs_ioctl] *ERROR* Faild to schedult IB! followed
by a bunch of similar messages. In logs I have this:
log
Would it be a bad idea for me to edit /etc/grub.d/10_linux to change:
# Use a simple linear framebuffer appropriate to the platform if support
# for it is known to be built into the kernel. We need it to be built-in
# rather than modular, as otherwise early output from the kernel won't
#
# Use a simple linear framebuffer appropriate to the platform if support
# for it is known to be built into the kernel. We need it to be built-in
# rather than modular, as otherwise early output from the kernel won't
# work.
Sorry I made an error in my cut and paste
if [
It would be far simpler to add this line to /etc/default/grub:
GRUB_GFXPAYLOAD_LINUX=text
Doing that is fine to get things going again for you - it would be good
if you could be available to revert that once the kernel folks have a
candidate fix to test, though.
--
[ATI] GPU lockup with
Colin,
2 questions:
1) How do it extract the syslog?
2) I assume you want the the log with the GRUB that works, not the one
that doesn't.
--
[ATI] GPU lockup with gfxpayload=keep
https://bugs.launchpad.net/bugs/605614
You received this bug notification because you are a member of Ubuntu
Bugs,
On Thu, Jul 15, 2010 at 07:45:11PM -, Nate Muench wrote:
1) How do it extract the syslog?
Assuming that it doesn't lock up so badly that it can't write to the
syslog, then you should just be able to boot again with 'set
gfxpayload=text' and then look back in the syslog to the previous boot
One more stupid question:
Where would this syslog be located?
Also I want to make a note on the VM I'm using. It's being used on
VMware Workstation 7.1 which have my own personal flavor of open-vm-
tools (located here:
https://launchpad.net/~n-muench/+archive/ppa/+packages), since the
packages
29 matches
Mail list logo
