Comment 10 for bug 581466

Thank you for your suggestion.
But nothing changed, even with this latest kernel.
Just note: if I run

$ dmesg |grep -i matrox
[ 1.289437] matroxfb 0000:03:00.0: PCI INT A -> Link[APC4] -> GSI 19 (level, high) -> IRQ 19
[ 1.289443] matroxfb: Matrox G550 detected
[ 1.390065] matroxfb: MTRR's turned on
[ 1.390087] matroxfb: 800x600x32bpp (virtual: 800x5242)
[ 1.390091] matroxfb: framebuffer at 0xD8000000, mapped to 0xe0a00000, size 33554432
[ 1.440416] fb0: MATROX frame buffer device
[ 22.428639] matroxfb 0000:03:00.0: putting AGP V2 device into 4x mode
[ 24.024542] Modules linked in: mga drm xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE xt_DSCP
ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state nls_iso8859_1 nls_cp437 vfat fat iptable_nat
nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables
x_tables usblp snd_wavefront snd_cs4236 snd_wss_lib snd_opl3_lib snd_intel8x0 snd_ac97_codec
ac97_bus snd_hwdep snd_pcm snd_mpu401 snd_mpu401_uart snd_seq_midi snd_rawmidi snd_seq_midi_event
snd_seq snd_timer snd_seq_device snd ppdev ns558 gameport lp nvidia_agp parport_pc soundcore
snd_page_alloc i2c_nforce2 shpchp agpgart parport usbhid hid ohci1394 ieee1394 3c59x forcedeth mii
pata_amd floppy matroxfb_base matroxfb_DAC1064 matroxfb_accel matroxfb_Ti3026 matroxfb_g450 g450_pll
matroxfb_misc

here I see many matroxfb_* modules are built-in into the kernel. Could I get different results
building these as loadable modules? Notice that directfb docs suggest using matroxfb to be loaded alone.
Elio

Il 24/08/2010 11:25, madbiologist ha scritto:
> Given that you get the same issue with kernel 2.6.34-rc7, I'm wondering
> if some relevant DRM changes made their way into kernel 2.6.33, which
> would then mean that they would have been backported to Lucid. If this
> is the case, then kernel 2.6.36-rc2 should help you. From the
> changelog:
>
> commit c81476df1b4241aefba4ff83a7701b3a926bd7ce
> Author: Ondrej Zary
> Date: Thu Aug 19 14:13:25 2010 -0700
>
> matroxfb: fix incorrect use of memcpy_toio()
>
> Screen is completely corrupted since 2.6.34. Bisection revealed that it's
> caused by commit 6175ddf06b61720 ("x86: Clean up mem*io functions.").
>
> H. Peter Anvin explained that memcpy_toio() does not copy data in 32bit
> chunks anymore on x86.
>
> Signed-off-by: Ondrej Zary
> Cc: Brian Gerst
> Cc: H. Peter Anvin
> Cc: Petr Vandrovec
> Cc: Jean Delvare
> Cc:<email address hidden> [2.6.34.x, 2.6.35.x]
> Signed-off-by: Andrew Morton
> Signed-off-by: Linus Torvalds
>
> A PPA of this kernel is available at http://kernel.ubuntu.com/~kernel-
> ppa/mainline/
>