[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
** Tags added: needs-kernel-logs needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to life when X
starts
Baokai Lei, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
Confirmed on a Radeon 4850 after upgrading to Ubuntu 12.10 with kernel
3.5.0-25-generic. The vt_handoff workaround fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to life when X
starts
To manage
The same problem on Radeon HD6310 (E-300 APU) on Lenovo Thinkpad X121e.
Using Ubuntu 12.10. Display is off since the point after grub.
vt_handoff workaround did help. However, display still turns off, but
then returns in less than a second, so that I can see plymouth.
BTW, I have the same
same problem with radeon HD4800 on 12.10 (without fglrx that can't be
used )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to
I've now installed the proprietary fglrx driver, reinstated the
vt.handoff=7 in /etc/grub.d/10_linux and then did a Sudo update-
grub.
Upon booting with the current Ubuntu 3.5.0-17-28 kernel, I didn't have a
black screen anymore. Other than that, there's next to none difference
between booting
I've read that already. However, as I already said, there is *no* difference,
if vt.handoff is enabled or not.
I've disabled vt.handoff now, as per above, and booting is very smooth:
- Grub boot menu appears (with customised background image)
- after making a selection (or waiting until the boot
Okay. Although I can't see any difference between booting with vt.handoff=7 and
the 3.6 mainline kernel, which I did before, and booting now with a current 3.5
Ubuntu kernel and vt.handoff turned off - no screen flickering or anything with
the latter.
Thus I don't quite see the point of this
http://askubuntu.com/questions/32999/what-is-vt-handoff-7-parameter-in-
grub-cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back
Anything left to do here?
Or should I mark this as fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to life when X
starts
not fixed.. the previous one is just a quick workaround.
the vt.handoff is a cool feature so it would be better to keep it, also not
disabled because it always worked in the past.
It allows a smooth transition from grub to plymouth splashscreen without any
screen flickering :)
--
You received
Anything else for me to try out?
I've been thinking... It could be that the bug appeared because of an update to
the video drivers in the xorg-edgers repository I'm using.
Some Ubuntu-specific modification to the kernel, which isn't present in the
mainline kernel, doesn't go well with the
One last thing to check would be to see if this bug exists in the v3.2
kernel[0]. If it does, we can investigate further into X.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Shouldn't I rather try the Ubuntu-specific version of the kernel, rather than
the mainline version?
As we've seen before, no version of the mainline kernel I've tried has the bug.
The latest version of the Ubuntu-specific 3.2 kernel is 3.2.0-32.51:
Yes, sorry. Please test the Ubuntu 3.2 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to life when X
starts
To manage
Just tried the 3.2.0-32.51 Ubuntu kernel. Even there it's the same black
screen during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub,
I don't think it is X or kernel related... the black screen appears after grub
so when the framebuffer is opened.
I bet on grub v2.0 that doesn't handle vt.handoff=7 in a proper way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In fact with this I can see plymouth and VTs:
sed -i 's/set vt_handoff=vt.handoff=7/set vt_handoff=/g' /etc/grub.d/10_linux
update-grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Can you follow the Boot options instructions on the following wiki to
enable additional output on boot:
https://wiki.ubuntu.com/DebuggingKernelBoot
As mentioned on the wiki, it would be great if you can attach a log file
which may have captured any messages you see. If you are unable to
capture
@Lucazade
I've tried out what you suggested, so I launched a root Kwrite by
entering in the Run dialog:
kdesu kwrite
I opened /etc/grub.d/10_linux and replaced the line:
set vt_handoff=vt.handoff=7
with:
set vt_handoff=
I also opened /etc/default/grub and changed the gfxpayload to
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the LightDM login screen appears.
I'm using a Radeon HD 6850 with the
Can you test the first 3.4 based kernel:
https://launchpad.net/ubuntu/+source/linux/3.4.0-1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub,
Just looked, and kernel 3.4.0-1.2 has builds avaiable. Should I take that one
instead?
https://launchpad.net/ubuntu/+source/linux/3.4.0-1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Do you have a downloadable version of that kernel?
Further down on the page, under Builds, it says Failed to build for amd64
(and for all other platforms, too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tried out kernel 3.4.0-1.2 now, and the bug is even there.
Now this is getting uncanny.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub,
So does the bug not exist in v3.5.0-14.15 ?
https://launchpad.net/ubuntu/+source/linux/3.5.0-14.15/+build/3768740
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the LightDM login screen appears.
I'm using a Radeon HD 6850 with the
I just downloaded and installed the 14.15 kernel and tried it out. Good thing I
did, because it also has the bug.
I *thought* I had installed 14.15 before the upgrade, where the boot screen had
still worked fine, but it seems I'm mistaken there.
I went further back to kernel 13.14, but it has
Perhaps I should also mention that I've now tried out the just released
mainline kernel 3.6.0 final.
Like all other mainline kernels I've tried, it *doesn't* have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It does appear this bug is due to an Ubuntu specific change, since none
of the upstream kernels have this bug. The key is to identify the last
kernel that did not have this bug, and the first kernel that did. That
will allow us to bisect down to the commit that introduced the
regression.
I tried out all three kernels listed above: 10.10, 5.5 and 1.1. Surprisingly
enough, all three have the black screen bug.
What to do next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
@Baokai Lei,
I would like to perform a kernel bisect to identify the commit that
caused this regression. Can you confirm the 3.5.0-15.21[0] does not
have the bug? If that is the case, there are very few changes to bisect
between 3.5.0-15.21 and 3.5.0-15.22.
[0]
Tried out the .21 kernel, but it already has the black screen bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the
Tested the .20 kernel now, and it's already there as well.
Will continue further down.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back
Testing 3.5.0-14.19, already there, too.
How far back does this reach?
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the
Running 3.5.0-14.18... Guess who's there? Our friend, the bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the LightDM
Yes, it's in .17 as well. Only one more to go now.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back to life, and the LightDM login screen
Already there in .16 as well.
Looks like a commit between .15 and .16 caused the bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays no signal. When booting ends and X
starts up, the screen comes back
Could it be a bug in Grub 2.0? Maybe not correctly patched against vt.handoff=7?
Because if I temporary remove the grub_gfx_payload option from grub
everything work ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, it's not a Grub bug. I initially wasn't using any grub_gfx_payload
option, but the bug was the same, in Grub 1.99 as well as in Grub 2.00.
Then I added it, and while the resolution of the Grub menu changed
properly, it nothing about the black screen bug.
It's a kernel regression. I've now
Can you test two additional kernels? Can you test upstream v3.5.3[0]
and v3.5.4[1]? I'd like to confirm the regression was introduced in
v3.5.4.
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.3-quantal/
[1]
I've installed and tested now both mainline kernels, 3.5.3 and 3.5.4.
Both kernels work fine and display the bootscreen as they should.
To check back, I've booted into 3.5.0-15.23 again, and yes, the black
screen during boot is still the very same there.
--
You received this bug notification
I've taken a look at the mainline kernel index to get the next 3.5 kernel after
3.5.4 for testing - however, there is no next 3.5 kernel.
The kernel following 3.5.4 is 3.6-rc1.
As none of the mainline kernels exhibits the bug, apparently one of the
modifications that Ubuntu did to the mainline
Can you test the latest Quantal image in the -proposed repository?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug
I'm already using proposed, so I just reloaded the software list and installed
the new kernel 3.5.0-16.24 which it offered.
On reboot though, it sadly exhibited the same black screen bug as before with
.23, no change there.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
**
same here with a Radeon HD3000 and with a Mobility Radeon 7500
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to life when X
starts
To manage
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black (no signal) after Grub, comes back to
Using the kernel 3.6 rc7 from the mainline now.
The bootscreen works fine, so the bug is fixed here :D
I've installed the kernel manually now. Is there a way to add a
Launchpad repository for the kernel, so you always have the latest
kernel installed, without having to do it manually?
** Changed
those kernel are vanilla.. without any ubuntu patches. I would not use them if
not for testing.
I hope the issue is going to be fixed in stock 3.5 with a backport.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd like to perform a reverse bisect to figure out which commit upstream
fixes this regression. It would be very helpful to know the last kernel
that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for
the first kernel version
I've downloaded all three rcs you listed, installed rc1, rebooted... and lookit
there, already rc1 works fine and has the bug fixed :D
Now that was quick. No need anymore for the other two.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
55 matches
Mail list logo
