This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
grub2 - 1.99~rc1-1ubuntu1 fixes problem and confirmed with removal of
workaround. Thanks Colin!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Bo
** Branch linked: lp:ubuntu/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Boot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug was fixed in the package grub2 - 1.99~rc1-1ubuntu1
---
grub2 (1.99~rc1-1ubuntu1) natty; urgency=low
* Resynchronise with Debian. Remaining changes:
- Adjust for default Ubuntu boot options ("quiet splash").
- Default to hiding the menu; holding down Shift at boot w
Same bug here,
2.6.37-12-generic (64) nvidia 260.1926
black screen on graphic loading and locking of devices
no warning or errors in xorg log
I have a 1200x800 video resolution, playing with vga modes gave no results.
Best regards
David
--
You received this bug notification because you are a me
** Branch linked: lp:~ubuntu-core-dev/ubuntu/natty/grub2/natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Boot
--
ubuntu-bugs mailing list
At the recent platform rally, we determined that this is happening
because GRUB is failing to get EDID information (1024x600) due to an
internal logic bug, and as a result is using VBE Flat Panel information
(1024x768), which exceeds the size of the screen; this is more or less
readable in GRUB, bu
FWIW, GRUB doesn't do anything to pipes itself, relying on the VBE BIOS
to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Boot
--
ubuntu
Appears that we hit a pipe underrun during initialisation when the
display does not appear. Previously this has been triggered by poor
teardown of the pipes for reconfiguring:
- PIPEBSTAT: 0x8202 (status: FIFO_UNDERRUN VSYNC_INT_STATUS
VBLANK_INT_STATUS)
+ PIPEBSTAT: 0x00
Attaching intel_reg_dumper dumps per apw request.
This one is for kernel-11 and grub 1.99~20101126.
This combination works.
** Attachment added: "intel_reg_dumper kernel-11 & grub 1.99~20101126"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1785337/+files/ird_k11_g20
Attaching intel_reg_dumper dumps per apw request.
This one is for kernel-11 and grub2 1.99~201104
This combination fails.
** Attachment added: "intel_reg_dumper kernel-11 grub2 1.99~201104"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1785336/+files/ird_k11_g20110104
Also can anyone who has not yet tested with 2.6.37-12 kernels please
retest there and confirm that the kernel update there does not resolve
things. There are two fixes in there for black screens over the
previous kernels.
--
You received this bug notification because you are a member of Ubuntu
B
If your issue is that you get normal just a black screen, and if
downgrading just grub restores your graphics (as per comment #22) this
implies that grub is leaving the graphics card in a state that the
kernel cannot recover from. To diagnose this we need to get the output
of intel_reg_dumper in b
Downgrading GRUB may help, but GRUB is deliberately doing more work with
video than it used to be - it doesn't necessarily mean it's actually a
GRUB bug.
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
No need to go back to 1.98-1ubuntu9.
Downgrading grub2, grub-common, grub-pc to 1.99~20101126-1ubuntu2 is
sufficient. pre Alpha1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme
Grub was the problem for me as well.
Downgrading grub-common and grub-pc from 1.99~20101221-1ubuntu2 to
1.98-1ubuntu9 solved it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[
Bug description at top of page lists an order of events. Mine is
slightly different:
1. Boot process starts
2. Display turns off -- goes to power down state as if computer is off
3. Drum sounds are heard -- boot has ended
4. Keyboard is operational as NUMLOCK key toggles the light
5. Can't
I am also getting a black screen with i945gme since yesterday morning.
Though for me it affects all kernels I have installed (so not sure if it
is the same problem). Only way to get to KDM is to add "nomodeset" or
"acpi=off" to grub, but then I can only use the screen in 800x600.
--
You received
kernel-2.6.37-11 also works
but after upgrading only grub2, the system hits the original problem (drum
heard, dark screen)
** Attachment added: "dmesg after upgrading grub2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1774163/+files/dmesg-grub2upgrade.out
--
You
He narrowed it down to grub being updated where the problems started by
starting with a stock alpha 1 install, installing 2.6.37-11-generic and
verifying it worked correctly, then just updating grub.
** Also affects: grub (Ubuntu)
Importance: Undecided
Status: New
--
You received this
So i915 didn't load on 2.6.37-3, on 2.6.35-5.13 you got a crash which is
bug #676963 and was fixed on 2.6.37-5.14 and 2.6.37-7 appears to work.
One thing all 3 had in common is that vesafb did not get loaded at all.
One small thing I noticed in the earlier dmesg's was that vesafb was
trying to use
kern.log with 2.6.37-7 working system
Here are the other results:
2.6.37-3-generic: login screen, no high res
2.6.37-5-generic: login screen, no high res
2.6.37-7-generic: works! Classic Desktop works; 1024x600, 800x600, 640x480 all
recognized by system.
** Attachment added: "kern.log with 2.6.
I have had this for awhile also,with Nvidia 7600gs and repo nvidia-
current driver , what I found is if I edit the line in
/boot/grub/grub.cfg that reads set gfxpayload=$linux_gfx_mode to set
gfxpayload=1920x1080 (my normal res ) I can boot normally . this has
persisted for the last several kernel
@Stenten: done and it doesn't fix the problem. I've also tried the following
with no success:
1. Remove splash
2. Remove quiet
3. Remove vt.handoff=7
4. Remove set gfxpayload=$linux_gfx_mode
5. Added vesafb.sucks=1 (per Sarvatt)
I'm going to install natty Alpha-1 and see how it breaks from there.
Could you please try editing /etc/default/grub [1] and add the line
"GRUB_GFXPAYLOAD_LINUX=text"? Then run sudo update-grub in a terminal
and reboot. Thank you.
[1] gksudo gedit /etc/default/grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Tags added: regression-release
** Tags removed: regression-potential
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i
RE: Can you still boot into the 2.6.37-9 kernel if you select it in
grub?
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Boot
--
ubuntu-b
Can you still boot into the 2.6.37-9 kernel if you select it in grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693093
Title:
[i945gme] 2.6.37-10.24: Black Screen on Boot
--
ubuntu-bugs mailin
Well I can't figure it out. There's an Oops in the rc6 kernel in
plymouth, but that's not in the -10 kernel, and there's also no good
reason (that I can find) that rc5 would also be affected if -9 wasn't.
Either way, all the information has been provided, so I'll mark it ready
for a member of the
RE: 1) I noticed you have vt.handoff=7 in the kernel command line. Have
you had problems with VT switching? Does it work if you remove that
parameter? Can you switch to a different TTY and run 'startx' and get a
graphical desktop?
vt.handoff=7 was already there. I did not add it.
Have never had pr
Mainline 2.6.37-020637rc5-generic has same problem. Attached Xorg.0.log.
** Attachment added: "Xorg.0.log for 2.6.37-020637rc5-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1773049/+files/Xorg.0.log-2.6.37-020637rc5-generic
--
You received this bug notifica
Mainline 2.6.37-020637rc5-generic has same problem. Attached dmesg.
** Attachment added: "dmesg for 2.6.37-020637rc5-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1773048/+files/dmesg-2.6.37-020637rc5-generic.out
--
You received this bug notification becaus
Mainline 2.6.37-020637rc6-generic has same problem. Attached Xorg.0.log.
** Attachment added: "Xorg.0.log for 2.6.37-020637rc6-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1773046/+files/Xorg.0.log-2.6.37-020637rc6-generic
--
You received this bug notifica
Mainline 2.6.37-020637rc6-generic has same problem. Attached dmesg.
** Attachment added: "dmesg for 2.6.37-020637rc6-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693093/+attachment/1773045/+files/dmesg-2.6.37-020637rc6-generic.out
--
You received this bug notification becaus
34 matches
Mail list logo
