Try disable DRI in following way (create/edit xorg.conf file):
Section Module
...
Disabledri
...
EndSection
Try also disable AIGLX. Unfortunately this is only workaround.
--
VIA KM400: Black screen after boot, no text console possible
Just to note that I seem to be suffering from the same issue, however I
have found if I boot with the livecd (which works) and then restart (NOT
Shutdown) the system will boot normally. I don't no if this will be of
any help, or if others can confirm.
--
VIA KM400: Black screen after boot, no
Just tested rebooting from livecd, and I still get the black screen on
booting the normal install. So this doesn't work for my hardware,
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a
I've got the same problem here on an Acer Aspire 1353XC Laptop with
Beta1, but the Live CD (well, on a USB stick) installer worked OK aside
from corrupted graphics during the bootsplash. So what is the
difference between the Live CD boot and the normal install boot, that
means the Live CD works
I (the original reporter) can confirm the observed behavior by Jon Welsh
(#26). I'm typing this response on a version 2.6.32-16 kernel-based
lucid, booted from a USB stick. The same kernel version, when booted
from hard disk after an upgrade from karmic (see original description)
doesn't work at
Small addition, the virtual terminals cannot be used by me from within
the live cd environment, the screen that is shown is corrupt.
Furthermore, I actually used the Xubuntu live cd instead of the Ubuntu
live cd.
--
VIA KM400: Black screen after boot, no text console possible
It was basically just trial and error. You might try under clocking your
cpu just in case (might not actually help). Even in verbose mode (i.e,
without quiet and splash for the kernel command line), the final message
I see is the one from fsck.
I have tried blindly firing away C+A+D after the
I had noticed that pressing ctrl+alt+del at some magic moment after the
fsck message takes me to gdm. I managed to scrape through today and get
some logs.
The mouse was not detected (PS/2).
Looks like there is some issue with drm... I saw messages to that effect in
dmesg and xorg.0.log. I have
Xorg.0.log
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/41810110/Xorg.0.log
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
daemon.log
** Attachment added: daemon.log
http://launchpadlibrarian.net/41810154/daemon.log
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
syslog
** Attachment added: syslog
http://launchpadlibrarian.net/41810189/syslog
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I could not run apport-collect for adding comments #19 to #22 for
reasons mentioned in comment #10.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Gokul: That's brilliant! Any ballpark idea at what point in the boot
process CAD works?
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can also confirm this. I have a VIA CX700 graphic kernel 2.6.32-16.
One thing I found is if I install Lubuntu 2.6.32-16 the graphics are
normal, then install Ubuntu-desktop it still runs good. But if I
uninstall Lubuntu-desktop I get the black screen again. I can also
confirm plugging external
This is sounding very similar to the problems I'm encountering in bug
499399. I can't boot a Lucid install unless I use the Karmic kernel. If
I try a Lucid kernel (or other Ubuntu mainline kernel = 2.6.32) I get
boot messages like those in Paul van Genderen's message above, stopping
at the same
Kernel 2.6.32-17-generic shows the same symptom as described by Robert
Moerland and gokul. This is probably a kernel problem as this also
occurs on a commandline-only installation. Steve Langasek is right that
this doesn't have to do with Plymouth. Removing that merely adds errors
to the boot
Just for the sake of completeness: also kernel 2.6.32-16-generic shows
the same symptoms, as originally described, on my machine. Install of
daily image from day 18.03.2010.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this
I can confirm it's a regression in 2.6.32. Kernel 2.6.31 works well (tested
with 2.6.31.12).
I hit this bug when I boot into single mode (recovery mode). Text cursor in top
left corner appears instead of recovery menu. Combination (CTRL) + Alt + Fx
doesn't work, I have to restart using Ctrl +
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Marked to triaged again; was changed to confirmed by mistake according
to a message received:
From: Nicholas Christian Langkjær Ipsen
To: Charlie Kravetz
Subject: Oops...
Date: Mon, 15 Mar 2010 08:25:59 -
Could you please mark Bug518623 as triaged again? I was an idiot and
marked it down
The last boot up message that could be seen in the recovery mode is the fsck
output from util-linux-ng. Appears to hang sometime after that.
Is there someway by which I can confirm the exact process that leads to this?
(note that every time I try something, it hangs and I have to 'hard reboot'
just for the sake of completeness: also kernel 2.6.32-16-generic shows
the same symptoms, as originally described, on my machine
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of
I tried to append to the information here but I got an error:
apport-cli -u 518623
Error connecting to Launchpad: 'NoneType' object has no attribute 'makefile'
You can reset the credentials by removing the file
/home/su/.cache/apport/launchpad.credentials
rm: cannot remove
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: linux (Ubuntu)
And I unfortunately also cannot use lucid with kernel 2.6.32-15-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Update: situation is unchanged after an update to kernel
2.6.32-14-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Update: situation is unchanged after an update to kernel
2.6.32-13-generic.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yes, karmic kernel 2.6.31-14-generic works just fine.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The symptoms you describe aren't attributable to plymouth. Sounds like
you have a kernel problem.
** Package changed: plymouth (Ubuntu) = linux (Ubuntu)
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification
After some research on launchpad, it seems more likely to be a bug in
Plymouth than in xserver-xorg-video-openchrome. Moreover, I've
completely removed Xorg and I still can't log in on a TTY
** Package changed: xserver-xorg-video-openchrome (Ubuntu) = plymouth
(Ubuntu)
** Description changed:
Could you test booting with older kernel. I got also black screen after
update to lucid. Older kernel works for me.
--
VIA KM400: Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38872373/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38872374/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38872375/Dependencies.txt
**
32 matches
Mail list logo
