[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#347186: marked as done (linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer)

Your message dated Fri, 5 Feb 2010 00:52:14 +0100
with message-id <20100204235214.GA6624@galadriel.inutil.org>
and subject line Re: [linux-2.6] more on bterm
has caused the Debian Bug report #347186,
regarding linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
347186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347186
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.14-7
Severity: important

Sigh, can't get a break with alpha kernel support around here.  After
upgrading to 2.6.14 (from 2.4.27), the Matrox framebuffer no longer works
correctly on my alpha with a Matrox Millenium II.  The matroxfb_base module
loads without error, but gives me corrupt video output only.

Card info from lspci:

0000:00:05.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W [Millennium II]

and lspci -n:

0000:00:05.0 0300: 102b:051b

dmesg output:

matroxfb: Matrox Millennium II (PCI) detected
PInS memtype = 0
matroxfb: 640x480x8bpp (virtual: 640x6553)
matroxfb: framebuffer at 0x9000000, mapped to 0xfffffc8809000000, size 4194304
fb0: MATROX frame buffer device
fb0: initializing hardware


Happy to test potential driver fixes, though due to issues with *other*
hardware in this system I didn't test the framebuffer with any previous 2.6
kernels and can't tell you whether it worked with them.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Gabriele Gorla wrote:
> --- Please enter the report below this line. ---
> 
> I just swapped the millennium II with a ATI RAGE XL (atyfb module).
> bterm still (mis-)behaves exactly the same as with matroxfb.
> 
> I start doubting the bterm problem is an issue with the matroxfb driver.
> 
> As a side note, loading atyfb does not corrupt the screen even if the fbcon module is not loaded.
> The console stays in text mode until the fbcon module is loaded (with matroxfb the console goes 
> in graphics mode immediately producing a garbled display until fbcon is loaded as well)

Alpha is dropped from the set of release architectures for Squeeze. I'm closing this bug. 

Cheers,
        Moritz

--- End Message ---
Reply to: