On Mon, May 03, 2010 at 02:58:15AM -, Ernesto Manriquez wrote:
I still have this around, with Lucid release.
That's not possible. This bug is specific to the interaction between
nouveau DRM and plymouth, and in the final Lucid release, plymouth does not
use the DRM backend on nouveau. You
I still have this around, with Lucid release. This bitter bug has also
bitten me with Fedora 12 and Fedora 13 Alpha, under AMD64. With Lucid,
I'm using the official CDs.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You
I confirm the issue is fixed after an upgrade!
Many thanks guys!
Keep up the good work :)
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is
live CD 16-Apr-2010 I check. With my hardware (LCD (DVI) 'n' TV (DVI-
VGA) have booting good.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm still noticing this issue with current-build live CD / Install
Ubuntu option from grub menu - http://cdimage.ubuntu.com/daily-
live/current/ 16-Apr-2010 08:30 695M Desktop CD for PC (Intel x86)
computers (standard download)
Will it take time to reach the current-build ?
Thanks
--
System
** Attachment added: Console error message, maybe not related to this bug
http://launchpadlibrarian.net/44496480/Screenshot-Supermicro.png
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification
plymouth 0.8.2-1 is included on the daily CDs for April 16. If you are
still having problems, it's not the same bug as this one.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you
** Branch linked: lp:ubuntu/plymouth
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
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 plymouth - 0.8.2-1
---
plymouth (0.8.2-1) lucid; urgency=low
[ Steve Langasek ]
* New upstream release.
* debian/plymouth.plymouth-stop.upstart: trust the new kdm to stop plymouth
for us, too. LP: #540177.
* plymouth needs to depend on
Beta2 LiveCD (and fresh install)
I also get this ; the system becomes unresponsive at 4 red dots.
Booting to a recovery console and replacing nouveau with nvidia-current
fixed the problem for me.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
** Also affects: plymouth (Ubuntu Lucid)
Importance: Medium
Status: Triaged
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This may be a kernel bug; tracked in bug #539655.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I just nominated this for Lucid because it prevents the beta 1 or beta2
install disks from proceeding beyond the initial screen with the dots.
Kind of ironic, since the purpose of plymouth was to provide a smooth
boot experience.
Anyway, if this is not fixed for the release, Ubuntu is going to
Alt+SysReq+K is a workaround though.
** Attachment added: dmidecode.txt
http://launchpadlibrarian.net/43865894/dmidecode.txt
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you
** Attachment added: lspci.txt
http://launchpadlibrarian.net/43865938/lspci.txt
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this bug too when trying to boot Lucid beta 2 from the
Live CD. Having two monitors connected to a Nvidia card hangs the boot
process exactly as described. There is no hang when only one monitor is
plugged in.
--
System fails to boot with plymouth installed (nouveau driver with 1
Possible upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=23813
** Bug watch added: freedesktop.org Bugzilla #23813
http://bugs.freedesktop.org/show_bug.cgi?id=23813
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
With dual VGA card I'm able to successfully install Ubuntu 10.04 beta2
with the following procedure:
* Install Ubuntu 9.10 32/64-bit
* Update /etc/apt/source.list, Find Karmic, Replace with Lucid
* sudo apt-get update
* sudo apt-get install
Other changes I did:
* In Ubuntu 9.10 have installed
I believe I may also be experiencing this bug, with a brand-new install
of Lucid beta-2. The title certainly matches my problem.
lspci shows:
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200]
(rev a1)
...this card has one DVI and one VGA output. When both outputs are
I am also facing this issue. Thinkpad W700 with NVidia FX3700M. The boot
on the laptop with LVDS LCD screen is fine. Boot with laptop attached to
a dock with 2 monitors (VGA and DVI-D) hangs with plymouth running. I
can work around the issue by booting in recovery mode or without
splash parameter
I am also facing this issue. Thinkpad W700 with NVidia FX3700M. The boot on the
laptop with LVDS LCD screen is fine. Boot with laptop attached to a dock with 2
monitors (VGA and DVI-D) hangs with no key presses acknowledged.
I can work around the issue by booting in recovery mode or without
I am experiencing this issue and I found plymouthd process running when it
should not be (at least it shuts down on my Aspire One netbook when GDM starts
up).
The plymouthd process is so stuck that it is not possible for gdb to attach to
it. It is not possible to kill plymouthd process with
After digging further I see that sometimes plymouthd does not receive
quit command, but when it does, it hangs with the following:
(me sends quit command):
read(6, Q\2, 2) = 2
read(6, \1, 1)= 1
read(6, \0, 1)= 1
getsockopt(6,
fd 11 is /dev/dri/card0.
So, plymouth sends some ioctl to the gfx card and then decides to hang
completely.
Alt+SysRq+K on the plymouth terminal kills plymouthd and it allows gdm startup.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
For me it works with the Ubuntu text theme, but the system hangs with
the Ubuntu logo theme...
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same as Ruben, only the logo theme hangs the system.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The ubuntu-logo and ubuntu-text themes are very different; if ubuntu-
text works, and ubuntu-logo does not, that implies a fault with the
renderer.
Could you try one of the other graphical themes (e.g. plymouth-theme-
spinfinity) and see whether it works or fails with that
** Changed in:
The theme plymouth-theme-spinfinity also breaks booting.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Triaged
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just wanted to say: This bug is fixed for me now (not sure why).
Although the resolution of Plymouth changes while booting and it doesn't
quite look right I get successfully to the login.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
Still broken for me.
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Experiencing this bug with a Sony Vaio VGN-FE41Z which has an LVDS
internal monitor and an external DVI-D connected via the docking
station. During start-up output is mirrored to the external monitor.
The display 'stops' with the plymouth splash screen and the message
Press C to cancel checking
I have the same problem. Can t booting live cd Ubuntu 10.04 beta1 when 1
display. But problem was began earlier( alpha3 10.04), when i update kernel
from 2.6.32-15 to 2.6.32-16, after reboot i had picture 1024 768 in the left
high corner my display(22 inch 1680 1050) (i had nvidia driver at
I've been able to reproduce this here on a test machine.
** Changed in: plymouth (Ubuntu)
Importance: Undecided = Medium
** Changed in: plymouth (Ubuntu)
Status: New = Triaged
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
psierra, please file a separate bug report for your issue.
** Summary changed:
- System fails to boot with plymouth installed
+ System fails to boot with plymouth installed (nouveau driver with 1 display)
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
35 matches
Mail list logo
