kernel-packages team mailing list archive

[Launchpad Bug Tracker <919888@xxxxxxxxxxxxxxxxxx>]

[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/919888

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

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919888/+subscriptions