From: Johan G. <so...@ho...> - 2004-04-03 10:32:35
|
(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. I haven't tried to use X, I want to get my console working first. Thanks in advance /Johan Gullden |
From: Sven L. <sve...@wa...> - 2004-04-03 10:49:55
|
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. Friendly, Sven Luther |
From: Johan G. <so...@ho...> - 2004-04-03 11:51:04
|
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. /Johan Gullden |
From: Johan G. <so...@ho...> - 2004-04-03 12:42:58
|
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 /Johan Gullden |
From: Sven L. <sve...@wa...> - 2004-04-03 13:41:26
|
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. Friendly, Sven Luther |
From: Jean D. <kh...@li...> - 2004-04-03 14:36:39
|
Hi Sven, > > 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. Really? Take a look again. I can clearly see that the text is garbled all over the place. For example "Bringing eth0h0p..." should read "Bringing eth0 up...", "Setting defeflt gateway..." should read "Setting default gateway..." and so on. You will also notice that the broken characters are not randomly located. They are placed on two-char wide columns. Something like 12 valid columns, 2 broken ones, 12 valid, 2 broken, and so on, if it helps. -- Jean Delvare http://www.ensicaen.ismra.fr/~delvare/ |
From: Johan G. <so...@ho...> - 2004-04-03 14:42:50
|
On Sat, 3 Apr 2004 15:41:18 +0200 Sven Luther <sve...@wa...> wrote: > > > > > > 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. > Ok, if you look at the second picture from the bottom you can read "Setting DNS d dainname to useseet..." "Bringing eth0h0p..." "Setting defeflt gateway..." etc. It should not be this werid text the first should be "Setting DNS domainname to usernet" and the loginpromt should be. "This is jonix.unsernet (Linux ppc 2.6.4-pegasos0)" And on the last picture you see the "[ ok ]" mark as "[ ok ] ]" This is maybe a diffrent problem, i don't know, have never had this before. Read the text on the pictures, and you will see. /Johan Gullden |
From: Sven L. <sve...@wa...> - 2004-04-03 15:03:18
|
On Sat, Apr 03, 2004 at 04:43:10PM +0200, Johan Gullden wrote: > On Sat, 3 Apr 2004 15:41:18 +0200 > Sven Luther <sve...@wa...> wrote: > > > > > > > > > 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. > > > > Ok, if you look at the second picture from the bottom you can read > > "Setting DNS d dainname to useseet..." > "Bringing eth0h0p..." > "Setting defeflt gateway..." > > etc. It should not be this werid text the first should be > > "Setting DNS domainname to usernet" > > and the loginpromt should be. > > "This is jonix.unsernet (Linux ppc 2.6.4-pegasos0)" > > And on the last picture you see the "[ ok ]" mark as "[ ok ] ]" > > This is maybe a diffrent problem, i don't know, have never had > this before. Read the text on the pictures, and you will see. Yeah, but this is not a problem with the setting up of the video mode, as i first thought it was, but probably either a problem with fbcon or text acceleration on matroxfb, or a problem with text encoding or something such. You don't use some strange (UTF8 for example) text encodings ? Can you try this with another graphic card ? Or maybe put the kernel online so someone else can test it with another graphic card ? Friendly, Sven Luther |
From: Petr V. <van...@vc...> - 2004-04-03 16:01:09
|
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. So I have couple of questions: (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). (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. (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. (3) You can try 'video=matroxfb:sdram'. But I do not think that g450/g550 portion of driver honors this option - as I said, it completely relies on on pins... (4) Otherwise I have no further idea. Problem is definitely caused by wrong memory type, mctlwtst* or memmisc/memrdbk value. Best regards, Petr Vandrovec van...@vc... |
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 |
From: Petr V. <van...@vc...> - 2004-04-03 16:09:46
|
On Sat, Apr 03, 2004 at 04:43:10PM +0200, Johan Gullden wrote: > On Sat, 3 Apr 2004 15:41:18 +0200 > Sven Luther <sve...@wa...> wrote: > > > > > > > > > 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. > > > > Ok, if you look at the second picture from the bottom you can read > > "Setting DNS d dainname to useseet..." > "Bringing eth0h0p..." > "Setting defeflt gateway..." > > etc. It should not be this werid text the first should be > > "Setting DNS domainname to usernet" > > and the loginpromt should be. > > "This is jonix.unsernet (Linux ppc 2.6.4-pegasos0)" Ah, now I see that it is PPC... With card from Matrox? If you'll look at matroxfb_read_pins(), you'll find that driver reads framebuffer base address and enables BIOS at that address - it is solution recommended by Matrox if BIOS is disabled on device. You should probably instrument parse_bios() to make sure that it finds what one would expect. Region is uncacheable, so there should be no problem on CPU side, and on hardware side mga chips are designed to have all four memory regions overlapped, and their behavior is specced for such configurations. But if your card comes with firmware from IBM, you'll have to ask IBM. Unless their firmwares conform to memory layout Matrox itself uses. Petr |
From: Geert U. <ge...@li...> - 2004-04-03 19:11:28
|
On Sat, 3 Apr 2004, Petr Vandrovec wrote: > On Sat, Apr 03, 2004 at 04:43:10PM +0200, Johan Gullden wrote: > > On Sat, 3 Apr 2004 15:41:18 +0200 > > Sven Luther <sve...@wa...> wrote: > > > > > > > > > > > > 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. > > > > > > > Ok, if you look at the second picture from the bottom you can read > > > > "Setting DNS d dainname to useseet..." > > "Bringing eth0h0p..." > > "Setting defeflt gateway..." > > > > etc. It should not be this werid text the first should be > > > > "Setting DNS domainname to usernet" > > > > and the loginpromt should be. > > > > "This is jonix.unsernet (Linux ppc 2.6.4-pegasos0)" > > Ah, now I see that it is PPC... With card from Matrox? Pegasos is a relatively new CHRP PPC box. IIRC, its firmware has a PC BIOS emulator. > If you'll look at matroxfb_read_pins(), you'll find that driver reads framebuffer > base address and enables BIOS at that address - it is solution recommended > by Matrox if BIOS is disabled on device. You should probably instrument > parse_bios() to make sure that it finds what one would expect. Region is > uncacheable, so there should be no problem on CPU side, and on hardware side > mga chips are designed to have all four memory regions overlapped, and their > behavior is specced for such configurations. > > But if your card comes with firmware from IBM, you'll have to ask IBM. Unless > their firmwares conform to memory layout Matrox itself uses. Since Pegasos is not an IBM system, he's most probably using a standard Matrox card. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |