kernel-packages team mailing list archive

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

topolinix, 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-rc5

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

** Tags added: bios-outdated-1009 needs-upstream-testing

** Changed in: linux (Ubuntu)
       Status: Confirmed => 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/581466

Title:
  matroxfb causes corruption in both virtual consoles and xorg

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Loading matroxfb causes corruption in virtual consoles (ctrl+f1 up to ctrl+f6). Framebuffer is loaded with settings 800x600x32bpp (mode 0x115) as reported by dmesg, fbcon is loaded but characters in virtual consoles are unreadable, when I type something i just see some random pixels (located far away from the expected prompt), and also unreadable is the output of each command I launch. The only way to read what is shown on the screen is switching to xorg (ctrl+f7), then switching back to the virtual console, then the text is fixed; but, unfortunately, typing new characters brings the same result as before.
  Also, the framebuffer is needed in order to enable tv-out on my matrox g550 via libdirectfb used by mplayer (device `-vo dfbmga'). Well, when I run `mplayer -vo dfbmga myfile.ext' then I can see the clip on my tv but the whole desktop gets corrupted showing random colors. Everything turns back to normal activity when I quit mplayer. This feature worked until a couple of weeks ago, in my good old hardy heron installation, when I watched movies on my tv while using desktop apps. (I must admit, I actually don't know if this bug is due to matroxfb or libdirectfb or mplayer).
  Further, loading matroxfb makes gdm unable to show the login screen at 1280x1024 (it was able when no framebuffer was loaded). I tried this without xorg.conf file and gdm caused the monitor to go blank, showing an `unsupported frequency' alert. Then I created a xorg.conf file and set two resolutions in the same `modelines' statement: 1280x960 and 1280x1024; now gdm shows login at 1280x960 (the screen is still at 1280x1024 anyway, so I have to move my mouse in order to see it all), while xorg, which is loaded after login, is able to set 1280x1024.
  I report this here and I will soon check a newer kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-22-generic 2.6.32-22.33
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  topolinik   1776 F.... pulseaudio
   /dev/snd/pcmC0D0p:   topolinik   1776 F...m pulseaudio
  CRDA: Error: [Errno 2] Nessun file o directory
  Card0.Amixer.info:
   Card hw:0 'nForce2'/'NVidia nForce2 with ALC650E at irq 22'
     Mixer name	: 'Realtek ALC650E'
     Components	: 'AC97a:414c4722'
     Controls      : 50
     Simple ctrls  : 33
  Card1.Amixer.info:
   Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
     Mixer name	: ''
     Components	: ''
     Controls      : 0
     Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Sun May 16 22:23:50 2010
  HibernationDevice: RESUME=UUID=ea6d2b9c-13b1-407b-8814-fdcd79f2ddc8
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
   
   eth1      no wireless extensions.
  MachineType: ASUSTeK Computer INC. A7N8X
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=e688872f-be02-48b3-9bea-b5060fd9b6c2 ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=it_IT.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34
  RfKill:
   
  SourcePackage: linux
  dmi.bios.date: 09/14/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A7N8X Deluxe ACPI BIOS Rev 1008
  dmi.board.name: A7N8X
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: REV 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufactture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA7N8XDeluxeACPIBIOSRev1008:bd09/14/2004:svnASUSTeKComputerINC.:pnA7N8X:pvrREV1.xx:rvnASUSTeKComputerINC.:rnA7N8X:rvrREV1.xx:cvnChassisManufactture:ct3:cvrChassisVersion:
  dmi.product.name: A7N8X
  dmi.product.version: REV 1.xx
  dmi.sys.vendor: ASUSTeK Computer INC.

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