Display blacks out during boot, then only upper half is used after the boot, on GMA600 (psb_gfx)

[Masahiro Sekiguchi]

When I boot my PC, the display blacks out immediately after the GRUB screen, and nothing appears afterwards. If I press Ctrl-Alt-F1 when the boot completes (i.e., when the disk access stops), the text console screen appears and shows a login prompt as expected (in the PC's native resolution). And after I see teh text console, I can press Ctrl-Alt-F7 to show the graphical login screen, but on the display the *lower half* of the graphical login screen appears on the upper half of the physical display, and the lower half of the dispay is just black. The Ctrl-Alt-F7 works only after seeing the text console; if I pressed Ctrl-Alt-F7 immediately after the boot completion (without pressing Ctrl-Alt-F1), nothing happens on the display.

When I typed a user ID and password on the half-trimmed graphical screen, I can login to the graphical desktop, but the lower half of the display is still black, and the upper half of the dispay appears showing *both* upper and lower halves of the logical screen, overwriting each other in parts in a redraw order. And if I can manage to logout, the display shows the login screen correctly (after a gray transition screen).

The above behaviour is observed when booting from a system installed to the disk drive using the Live CD. Booting the Live CD itself does not cause the black out; it causes upper-half phenomenon only. The graphical boot screen first shows up using entire display. It is later broken with several kernel error messages, but the slowly brinking dots under the ubuntu logo are visible during the entire boot process. After completion of the boot, some broken graphical screen (intended for asking "Try ubuntu" or "Insall") appears on the upper half of the display, leaving some kernel error messages on the lower half of the display. If I can manage to choose "Try ubuntu" on the broken screen, the tryout desktop appears correctly using entire display. (So, I could install ubuntu to the disk drive.)

If I entirely disable plymouth on the installed system (i.e., remove all /etc/init/plymouth*.conf files as suggested in pages found by google search), the blackout-during-and-after-boot behaviour persists, but the first graphical screen I see after boot, then Ctrl-Alt-F1 then Ctrl-Alt-F7 appears correctly using entire display, so I don't need an extra login-logout cycle on a broken screen. That's my current workaround...

I'm using Fujitsu Lifebook TH40D, a "hybrid of note and tablet" PC. It has Atom Z670 with SM35 Express chipset, providing GMA 600 graphics subsystem.

I trid Live CD media of 12.04 LTS (Precise angolin) alpha 1. The installed system's behaviour persists after "apt-get dist-upgrade" today (2012-01-22 Japan time).

P.S., I'm exciting to see the poulsbo support in ubuntu comes to very close to production use, and is very likely to be integrated in the official ubuntu distribution soon. I appreciate GMA500 team. Hope this report help improving the psb_gfx driver.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-10-generic 3.2.0-10.17
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.91-0ubuntu1
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 1527 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xffaf4000 irq 41'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:80862881,80860101,00100000 HDA:10ec0269,10cf1000,00100100'
   Controls : 13
   Simple ctrls : 8
Date: Sun Jan 22 11:33:52 2012
HibernationDevice: RESUME=UUID=8316ea9b-fd3b-4fda-aac6-0da766a298db
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
MachineType: FUJITSU FMVT40D
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=174e7d4f-aee7-44e2-b813-891b69ca2823 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-10-generic N/A
 linux-backports-modules-3.2.0-10-generic N/A
 linux-firmware 1.67
SourcePackage: linux
StagingDrivers: psb_gfx
UpgradeStatus: Upgraded to precise on 2012-01-21 (0 days ago)
dmi.bios.date: 07/06/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNBB1B
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd07/06/2011:svnFUJITSU:pnFMVT40D:pvr:rvnFUJITSU:rnFJNBB1B:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: FMVT40D
dmi.sys.vendor: FUJITSU

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

I did apt-get update then apt-get upgrade as suggested. The issue persists.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

I used apt-get to upgrade to kernel 3.2.0-11. No significant changes regarding this issue.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

The 3.2.0-12 kernel is worse. After upgraded to 3.2.0-12, my system appears broken seriously. When booting, the display blacks out after GRUB screen, as before, and disk access continues for a while, then the PC reboots. I have to use GRUB to choose the 3.2.0-11 kernel so that I can use the PC.

[Masahiro Sekiguchi (sekiguchi328)]

Today I run apt-get update; apt-get upgrade; apt-get dist-upgrade. The kernel was not upgraded, i.e., it is 3.2.0-12. When I rebooted the system with the 3.2.0-12 kernel, I noticed that the behaviour is exactly as described in the original Bug Description. So, I guess I was wrong. The 3.2.0-12 is not worse than the 3.2.0-11. I'm not sure what caused the degrade on 2012-01-29 upgrade.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

I upgraded to 3.2.0.12-21 kernel. No significant improvements were observed.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

Upgraded to the 3.2.0-15.24 kernel. The problem persists.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

As I reported in the comment #12 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919888/comments/12 I already upgraded to the version and it didn't change the problematic behaviour.

[Masahiro Sekiguchi (sekiguchi328)]

psb_gfx.ko is loaded and active on my PC. The native display resolution is 1024x600. This is a note just to make things sure.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

I apt-get dist-upgrade'd the system. The kernel is now 3.2.0-17.26. The issue persists. No significant changes are observed.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

As I wrote in #17, my system is already upgraded to 3.2.0-17.26 kernel and the issue persists.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Masahiro Sekiguchi (sekiguchi328)]

Upgraded to 3.2.0-17.27. Nothing has changed.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc5 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc5'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/

[Masahiro Sekiguchi (sekiguchi328)]

Hi, Joseph, Thank you for your suggestion. I tried to to follow your instruction, and replaced the 'needs-upstream-testing' tag with 'kernel-unable-to-test-upstream' tag, but I'm not sure this is a correct choice. Please keep reading.

I downloaded and tested the "v3.3-rc4-precise" kernel but rc5, because my ATOM Z670 does not support 64 bit and no *_i386.deb files are in the "http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/".

The 3.3 rc4 kernel booted, but the black out behaviour persisted. Worse, Ctrl-Alt-F7/F1 workaround didn't work on the 3.3 rc4 kernel. The console was totally unusable. I needed to login through ssh. I also noticed that X server was not running.

I'm not sure, however, that this means the bug persists in the 3.3 rc4 mainline kernel. I looked in /lib/modules/3.3.0-030300rc4-generic directory for psb_gfx.ko driver, but I couldn't. I examined the dmesg, and there were no messages from drm nor plymouth. The PCI device 0000:00:02.0, that should be the GMA600, didn't seem getting any device driver attached.

I believe the 3.3 rc4 mainline kernel package didn't come with psb_gfx driver at all, and that's the reason it didn't work. I concluded that I couldn't perform the requested testing, so I put 'kernel-unable-to-test-upstream' tag but 'kernel-bug-exists-upstream'.

Please let me know if there are anything else I can test.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

I believe this could be a duplicate of bug 944929

[Rikard Lindström (ornotermes)]

Hi,

I think this is two bugs.
1. Black screen on boot (duplicate of #944929)
2. Both halfs of X i drawn on the upper half of the display on boot.

I myself is only affected by the second part part of the bug.

After boot the top half of the display shows picture, both the upper and bottom part draws over each other. The bottom part of the display still show plymouth.
A workaround at boot time is to restart lightdm from rc.local.

After suspend the computer about the 1/4 bottom of the display don't redraw, either in X or console (grey in X, black in console). Restarting X makes no good. Suspend is pretty much useless because i have to reboot the computer after having it suspended.

I tried mainline 3.4rc3, but it does not seem to have the psb_gfx module.

The device is a MSI Windpad 100W and it use gma500.

[penalvch (penalvch)]

Masahiro Sekiguchi, 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 just make a comment to this?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]