Messages in this thread | | | From | "Petr Vandrovec" <> | Date | Thu, 19 Jun 2003 14:06:42 +0200 | Subject | Re: [2.5.72-mm1] Matroxfb behaves buggy |
| |
On 19 Jun 03 at 13:49, Kimmo Sundqvist wrote: > I tried both MATROX_G450 and MATROX_G100 drivers, first G450 and then G100. I > find it odd that both are configured, since selecting G450 hides G100 in > "make menuconfig", so I have all the time assumed it is disabled when it's > hidden. Might the problem be caused by including both? I'll go and see, but > I think it's not the only problem. > > What's the difference between them? .config help ought to tell this briefly.
As far as I can tell, it is as clear as it could be... First option is named 'G100/G200/G400/G450/G550' support, while second is named 'G100/G200/G400'.
> When 2.4.20 switches to 1280x1024, the screen goes black with 2.5.72, then > some seconds pass and 1. vertical dark gray lines appear, and 2. some dark > blue areas between them. Some seconds pass and X comes up as if nothing was > wrong. > > I logged in to the console as root, not seeing anything. The TFT display > reported 640x480@60Hz in it's menu. I typed "fbset 1280x1024" for my custom > 1280x1024@60Hz mode. Oddly, X display appeared at 1280x1024 resolution, mode > parameters being something between the fbset and X modes, but I could do > nothing, so I pushed the reset button.
fbset is not supported on 2.5.x kernels for setting console resolution. If you want same environment you had in 2.4.x, get patch from ftp://platan.vc.cvut.cz/pub/linux/matrox-latest.
> syslog had a screenful of "^@^@^@^@^@^@^@^@^@^@^@" between time before the > lockup and next boot, as did kern.log
No surprise... But I doubt that it is matroxfb's problem. Petr
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |