[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
[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/518623 Title: [KM400] Black screen after boot, no text console possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/518623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
Robert Moerland, 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/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Description changed: Binary package hint: xserver-xorg-video-openchrome I have upgraded my Xubuntu karmic installation to lucid to test the alpha release of lucid. After the upgrade, which went smoothly, I rebooted the machine. I expected to see the GDM login screen eventually, but all I got was a completely black screen. Even the backlight of the LCD panel of my laptop was off. Pressing the (CTRL+)ALT+Fx key combinations did not (visibly) result in a change to the virtual terminal that corresponds to the F-key pressed. When I rebooted to use the recovery mode/single mode, I found that I couldn't get a text console even then. I was able to log in via SSH, which works perfectly and allowed me to run apport-cli from this machine. Furthermore, I could get a full graphical desktop by using vnc4server on this laptop and a vnc viewer on another machine, which confirms that the install is basically working. Therefore, I'm guessing that it has to do with the X server or driver, also because I've had some graphics-related trouble with this particular chipset that is inside my laptop before (VIA KM400).Still, it also might be due to this new boot splash method ubuntu is apparently using, but I'm not sure. (EDIT: changed 'Affects' to plymouth package. Have removed Xorg but still no TTYs) + + WORKAROUND: blacklist both viafb and vga16fb. ProblemType: Bug Architecture: i386 Date: Mon Feb 8 01:52:00 2010 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer,Inc. Aspire 1350 Package: xserver-xorg-video-openchrome 1:0.2.904+svn812-1ubuntu1 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcCmdLine: root=UUID=0be270a0-14a2-49d0-ad75-8db20bca2efa ro splash ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US:en ProcVersionSignature: Ubuntu 2.6.32-12.17-generic RelatedPackageVersions: xserver-xorg 1:7.5+1ubuntu2 libgl1-mesa-glx 7.7-0ubuntu8 libdrm2 2.4.17-0ubuntu2 xserver-xorg-video-intel N/A SourcePackage: xserver-xorg-video-openchrome Uname: Linux 2.6.32-12-generic i686 dmi.bios.date: 11/20/2003 dmi.bios.vendor: Acer dmi.bios.version: 3A23 dmi.board.name: Aspire 1350 dmi.board.vendor: Acer,Inc. dmi.board.version: Rev.A dmi.chassis.asset.tag: dmi.chassis.type: 10 dmi.chassis.vendor: Acer,Inc. dmi.chassis.version: 3A23 dmi.modalias: dmi:bvnAcer:bvr3A23:bd11/20/2003:svnAcer,Inc.:pnAspire1350:pvr3A23:rvnAcer,Inc.:rnAspire1350:rvrRev.A:cvnAcer,Inc.:ct10:cvr3A23: dmi.product.name: Aspire 1350 dmi.product.version: 3A23 dmi.sys.vendor: Acer,Inc. system: distro: Ubuntu architecture: i686kernel: 2.6.32-12-generic ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Attachment removed: "info.tbz2"
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
update: In mavreick beta, there is no bug. I have removed viafb from the blacklist. Splash screen at boot and shutdown/restart are also working. Not sure if some earlier update to lucid had already fixed it. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
There is the same issue on a desktop computer with "VIA Technologies. CN896/VN896/P4M900 [Chrome 9 HC]"... 9.10 -> 10.4 upgrage (lucid lynx with kernel 2.6.32-22) has been done, and after grub computer freezes... No CLI by Ctrl-Alt-F1/F2/F?.. No GDM (GNOME/LXDE)... Just reboot by Ctrl-Alt-Del... 10.4 (lucid) kernel 2.6.32-22 does not work... But 9.10 (karmic) kernels -- 2.6.31.* -- works... # lspci | grep VGA 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
My vga16fb problem may be the same one from bug 538893 comment #1, at least in that the garbage I see in text mode seems to be influenced by what was on the screen in X. And yes, that's a different bug. Blacklisting vga16fb is not necessary as long as X works: I get a brief period of garbage between vga16fb and X kicking in, but X works just fine. It's viafb that is the real problem here, because X (xserver-xorg- video-openchrome) does not reset things back to a usable state. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
With the workaround from comment #37 (blacklisting viafb), my boot process completes without freezing [mentioned in my earlier comments]. [I realize that the following may not be related to this bug. But I have mentioned it just in case]: After the boot, I have to do a Ctrl+Alt+Del to get to gdm [not at random]--- otherwise the monitor (HP M900) displays a message "Invalid Scanning Frequency" and I can see scan lines in the screen(this happens with and without an xorg.conf). After the ctrl+alt+del gdm comes up at the right resolution if an xorg.conf is in place (a low res screen otherwise). At present: 1) with neither the karmic kernel (2.6.31-19) nor the lucid kernel (2.6.32-20), Xorg is able to set my monitor resolution correct. I need to have a customized xorg.conf. 2) with karmic kernel (2.6.31-19), gdm is reached without the ctrl+alt+del quirk. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
No, the upstream changes in viafb won't help the problem you are experiencing and it is unknown whether viafb and/or openchrome (which should not rely on the output configuration to be correct) will ever be fixed as this would require an amount of documentation that is not yet released by VIA, especially for older IGPs like CLE266. However you can likely make it work with some module parameters as described in viafb.txt: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/fb/viafb.txt;h=f3e046a6a987a685910bafc171c2cc9cf243df1b;hb=HEAD If you also hit some acceleration bugs that where fixed in 2.6.33 you can use viafb_accel=0 This bug is similiar/identical to this one I think https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-via/+bug/538430 I do not object blacklisting viafb for this release as there exists also an even more serious problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539020 However blacklisting vga16fb sounds like a bad idea but that's not something I work on. (but even balcklisting it wouldn't be that much of a problem but it really should simply work) Perhaps it would be a good idea to do one seperate bugreport only for the vga16fb bug which gives a more verbose description of what the screen looks like? -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
Confirming workaround by Marien Zwart. After blacklisting both viafb and vga16fb, I can boot kernel 2.6.32.20 and can use my laptop normally. Don't know if there are any (major) drawbacks involved with blacklisting these modules. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
As mentioned on the duplicate I just filed: adding "blacklist viafb" and "blacklist vga16fb" to /etc/modprobe.d/blacklist.conf makes things work here. Karmic's kernel (2.6.31-20-generic) also works, but that is because viafb is not loaded there by default, not because viafb works. If I stop gdm and "sudo modprobe viafb" the panel turns off (I'm assuming this is the exact same bug triggering). There are some changes in the current upstream kernel's viafb. It's possible those help, but I have not gotten around to trying yet. Would it make sense to blacklist viafb for now, at least on this chipset? Fixing this is a bit of a hassle because neither X nor the console work with this bug present. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
A have same problem with ubuntu 10.4 (2.6.32-20-generic), but kernel 2.6.31-20-generic works fine. I tried change driver to "vesa" or disabled module dri, glx, but that didn't have any effect. Now, I have to boot with old kernel. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
Same bug for me -- laptop Fujitsu Siemens Amilo Pro v2010, graphics card: VIA PN800 or PN880 (don't remember which one; I doubt it's important here), kernel 2.6.23-16-generic. Laptop hangs after fsck with completely black screen. Interstingly, when I boot into my old Ubuntu 8.10 and immediately reboot to 10.04 -- it _always_ works. And it does not matter if it's hard reboot or soft. With hard reboot it works if I don't make long break between power down and turing on again. This is strange, as if RAM fading out effects had some influence here? (using uninitalized state? Just guessing...). -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
Hardware: Laptop: MiTac 8615P with chipset: VIA VN896 Software:Ubuntu 10.04, the latest release. Video driver: 1:0.2.904+svn827-1 My laptop freeze while booting, only a black screen is all I can see. The Ubuntu boot logo appears the left-down corner of the screen, so probably the resolution is much bigger than required. If an external monitor is connected to my laptop the system stand up well, but only the external monitor works properly nevertheless the laptop screen stills black. Using Debian 6 testing squeeze alpha 1 (wherein the kernel is also 2.6.32 and video driver) works fine via LiveCD without problems. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
update: On my installation, with the latest packages, 1. with kernel 2.6.32-18-generic, the boot still freezes after fsck message 2. with kernel 2.6.31-19-generic, I get gdm and gnome desktop at low resolution (800x600) and only other mode shown by xrandr was 640x480. I manually added a monitor section to provide the horizontal and vertical sync (from values I got off the net) and configured a modeline for 1280x1024. (using cvt) with this: * Using the custom xorg.conf, now xrandr (also the "monitors" menu item under system->preferences->monitors) shows a lot more mode options and I have configured it to use 1280x1024. * Even after the custom xorg.conf, kernel 2.6.32-18-generic, still freezes. * Plymouth splash is not seen at boot or shutdown/restart. -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
Adding: Section "Module" Disable "dri" EndSection to my xorg.conf file didn't make a difference, neither did adding 'Disable "glx"'. I also tried removing the xorg.conf file altogether, but also that didn't have any visible effect. @Bartosz: your involvement in this bug, does that mean you suspect the openchrome driver to be related to this? -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
** Summary changed: - VIA KM400: Black screen after boot, no text console possible + [KM400] Black screen after boot, no text console possible -- [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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
