kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Jonas Schwabe, 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 <replace-with-bug-number>

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.

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
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/539582

Title:
  1039:6351 VT Consoles 1-6 only display a flickering screen with
  vga16fb

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: plymouth

  What I expected:
  A shiny new bootscreen...

  What I got instead:
  I'm not sure if this is really a plymouth related problem, but I guess it is the best package to report this bug.
  While booting I only see a black screen with white stripes flickering on it, in fact they are moving from the left side of the screen to the right one.
  When the system is fully booted up I am able to switch to TTY7 with a working X Server, TTY1 - 6 also display a similar flickering screen!
  I am using the VESA driver with a SIS mirage 3+ graphics device due to lack of a supported Lucid driver. I will try to get a better driver maybe that would work.
  Bootscreen and all TTY were working on Karmic.

  WORKAROUND: In Lucid, adding "set gfxpayload=keep" to
  /etc/grub.d/00_header

  WORKAROUND: In Precise, use recordfail=1 instead.

  WORKAROUND: In releases prior to Precise, "intelfb.blacklist=1" fixes
  the issue without blacklisting vga16fb.

  ---
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  jonas      1618 F.... pulseaudio
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=9aed2f57-ebf6-4fbb-a737-18d3b83bdd4d
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120729.1)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
   Bus 001 Device 002: ID 5986:0200 Acer, Inc OrbiCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: wortmann M7x0S
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=54b60849-a0eb-468d-a863-30fae122eaf3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-6-generic N/A
   linux-backports-modules-3.5.0-6-generic  N/A
   linux-firmware                           1.87
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-6-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/01/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: 1234567890
  dmi.board.name: M7x0S
  dmi.board.vendor: wortmann
  dmi.board.version: Bottom
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SiS
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/01/2009:svnwortmann:pnM7x0S:pvrRev.A1:rvnwortmann:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A:
  dmi.product.name: M7x0S
  dmi.product.version: Rev. A1
  dmi.sys.vendor: wortmann

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