From: Sven L. <sve...@wa...> - 2004-04-03 21:49:22
|
On Sat, Apr 03, 2004 at 06:01:03PM +0200, Petr Vandrovec wrote: > On Sat, Apr 03, 2004 at 03:41:18PM +0200, Sven Luther wrote: > > On Sat, Apr 03, 2004 at 02:43:02PM +0200, Johan Gullden wrote: > > > On Sat, 3 Apr 2004 13:51:25 +0200 > > > Johan Gullden <so...@ho...> wrote: > > > > > > > On Sat, 3 Apr 2004 12:49:42 +0200 > > > > Sven Luther <sve...@wa...> wrote: > > > > > > > > > On Sat, Apr 03, 2004 at 12:32:54PM +0200, Johan Gullden wrote: > > > > > > (I am not subscribed to the list, so please CC your replies to me.) > > > > > > > > > > > > Hello, > > > > > > > > > > > > I am having trouble getting my Matrox G450 to work on my pegasos2, > > > > > > after and while booting the console gets weird. It doubles the output with a space of 4 characters, so it's really hard to use it. > > > > > > > > > > > > The kernel I am using is 2.6.4 (gentoo/ppc-development-sources), I have also tried the 2.4 kernel and getting the same problems. > > > > > > > > > > > > my settings from #Graphics support > > > > > > > > > > > > CONFIG_FB=y > > > > > > CONFIG_FB_MATROX=y > > > > > > CONFIG_FB_MATROX_G450=y > > > > > > CONFIG_FB_MATROX_G100=y > > > > > > CONFIG_FB_MATROX_I2C=y > > > > > > > > > > > > I have also tried to use diffrent boot parameters, but with no luck. The output is just a screen filled with colorful pixels. > > > > > > > > > > Johan, could you provide a bit more detail about the screen. You told me > > > > > that you saw like 4 different screens or soemthing such. This kind of > > > > > information, or even a digicam picture of the screen, is essential in > > > > > detecting the problem, and hopefully fixing it. > > > > > > > > > > > > > Ok, there seems to be some missunderstanding, I will take a picture of the console. So you all can se waht I mean. > > > > > > > > > > The pictures are really bad. But you should see what I mean. > > > Pictures are visible at: http://hem.passagen.se/stimp > > > > Nope, i don't understand what the problem is from those picutres, they > > seem rather normal to me. I may be wrong though. > > They are quite normal when using G100 in 2.4.x with weird memory chips. But > it should not happen with 2.6.x which reads setup from ROM. A G450 with 2.6.4 and 2.4.25, i think. > (1) What is pegasos? Is it i386/x86_64/alpha architecture which executes/emulates ROM BIOS, > or is Matrox initialized only by matroxfb? Can you try 'video=matroxfb:init' or 'video=matroxfb:noinit' > options (default value is autodetect whether card was initialized or not; using noinit on > system which did not initialize matrox hardware may lock up PCI bus, so have reset button ready). It is powerpc, using a standard x86 card, where the bios is run by an emulator in the firmware. > (2) If 'video=matroxfb:init' alone will not help, you can try playing with g450_memory_init() function. > It completely relies on PINS data, so if pins data are incorrect (like on GXT130P IBM distributed), > driver will not work without manual tweaking default_pins5() with values your hardware needs. Mmm. > (2a) Do you use card from Matrox, or is it some 3rd party product - either onboard (from f.e. HP) or > bundled with their own firmware (f.e. IBM)? Onboard devices are only in x86 systems, as in onboard > solutions there is usually no EEPROM connected to the graphics chip, and so it is not possible to > find PINS structure. Probably a Matrox board. Friendly, Sven Luther |