linux-fbdev-users — Generic mailing list for users of frame buffers

Re: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm-inversescreen on'

[Jean D. <kh...@li...>]

> There is a i2c interface between the card and the monitor that tells
> it what the monitor's capabilities are. If your monitor can't do it,
> it won't let you, because you can damage hardware that way.

It's a Hyundai Q17, capable of 1280x1024@75. But the docs say that 60Hz
is recommended so maybe that's what it says to the Radeon board over the
I2C bus.

After all, it's a TFT display, maybe it doesn't really care about the
frequency?

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Re: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Jurriaan <thu...@xs...>]

From: Hihn, Jason <Jas...@ve...>
Date: Tue, Apr 06, 2004 at 12:10:12PM -0400
> I D/L the 2.6.5 kernel,
> And in drivers/video/console/ you want to look at fbcon.c
> It has some cool functions: fbcon_invert_region, fbcon_putc[s], and
> fbcon_erase

yes, but (*)

> 
> It sounds like for the drawn area, everything is working right. It's
> only the overhang on the line that is not working right - its getting
> filled with blue.

correct

> 
> What happens on another manufacturer's card? The reason I ask that is I
> saw no special stuff with the ATI card drivers. I think all of linux may
> have this problem.

* my matrox framebuffer has never had this problem, so the 'general'
routines in fbcon.c should be OK. Also, I don't remember this from tdfx
(Voodoo 4500) framebuffer testing.

> 
> Can others out there on this list with 2.6 try -inverse?
> 

At the moment, I only have Ati and Matrox cards, Ati has the problem,
Matrox doesn't. I also tested with a 8x16 font, instead of my regular
12x22 font, but that didn't make any difference.

Kind regards,
Jurriaan
-- 
"Bother", said Pooh, as he scrambled his partition table.
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6062 bogomips 0.54 0.29

RE: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm-inversescreen on'

[Hihn, J. <Jas...@ve...>]

There is a i2c interface between the card and the monitor that tells it
what the monitor's capabilities are. If your monitor can't do it, it
won't let you, because you can damage hardware that way.

15bit I think dates back to some [matrox?] cards, circa 1995. No one
else really had/supported that.=20

-----Original Message-----
From: Jean Delvare [mailto:kh...@li...]=20
Sent: Tuesday, April 06, 2004 12:13 PM
To: lin...@li...
Subject: Re: [Linux-fbdev-users] radeonfb: strange blue lines after
'setterm-inversescreen on'

> This is a step in the right direction:
>=20
> 1600x1200-8@75: ok
> 1600x1200-16@75: blue screen
> 1600x1200-24@75: 'no mode found' in dmesg?
> 1600x1200-32@75: blue screen

Just tried, same here (Radeon 9200 Ya). If I ask for 15-bit I get 16, if
I ask for 24 I get 8. 8 is OK WRT blue background, 16 and 32 are not.

BTW, how do you get 75Hz vertical refresh? I just can't. Whatever I ask
through lilo, I end up with 60Hz (both fbset and the screen's OSD
agree).

Thanks.

--=20
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Linux-fbdev-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users

Re: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Jean D. <kh...@li...>]

> This is a step in the right direction:
> 
> 1600x1200-8@75: ok
> 1600x1200-16@75: blue screen
> 1600x1200-24@75: 'no mode found' in dmesg?
> 1600x1200-32@75: blue screen

Just tried, same here (Radeon 9200 Ya). If I ask for 15-bit I get 16, if
I ask for 24 I get 8. 8 is OK WRT blue background, 16 and 32 are not.

BTW, how do you get 75Hz vertical refresh? I just can't. Whatever I ask
through lilo, I end up with 60Hz (both fbset and the screen's OSD
agree).

Thanks.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

RE: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Hihn, J. <Jas...@ve...>]

I D/L the 2.6.5 kernel,
And in drivers/video/console/ you want to look at fbcon.c
It has some cool functions: fbcon_invert_region, fbcon_putc[s], and
fbcon_erase

It sounds like for the drawn area, everything is working right. It's
only the overhang on the line that is not working right - its getting
filled with blue.

What happens on another manufacturer's card? The reason I ask that is I
saw no special stuff with the ATI card drivers. I think all of linux may
have this problem.

Can others out there on this list with 2.6 try -inverse?


-----Original Message-----
From: Jurriaan [mailto:thu...@xs...]=20
Sent: Monday, April 05, 2004 2:38 PM
To: Hihn, Jason
Cc: lin...@li...
Subject: Re: [Linux-fbdev-users] radeonfb: strange blue lines after
'setterm -inversescreen on'

From: Hihn, Jason <Jas...@ve...>
Date: Mon, Apr 05, 2004 at 02:46:43PM -0400

[sorry for remailing this private mail to the list again, but I hope
others will chime in]

> I don't know the 2.6 kernel tree, but I'd suspect radeonfb.c

unfortunately, that file doesn't exist in 2.6, which proves your first
point :-)

>=20
> The low-level pixel get/set routines probably have a simple bit shift
> (<< >>) or mask (& |) error. "-inverse" was probably not taken into
> account when the code was written so the math is a little off. As far
as
> I know, linux treats 24b as the same as 32, so maybe that's why your
24b
> isn't working, no one bothered to code it because you have to align on
> 4-byte boundaries  anyway (no one packs 3 bytes adjacent to 3 bytes,
> because it is too much work, you'd have to move then shift, and it
gets
> messy and slow.). So someone would have written for 24, but in the end
> called it 32, so it's that extra byte that isn't being handled right.
>=20
> I could probably fix it, if I had a radeon card and a 2.6 kernel and
> some time. Sorry.

I've since found out that the 24-bits is disallowed on purpose.

drivers/video/aty/radeon_base.c:
static int radeonfb_check_var (struct fb_var_screeninfo *var, struct
fb_info *info)
{
		case 17 ... 24:
#if 0 /* Doesn't seem to work */
			v.bits_per_pixel =3D 24;
			break;
#endif		=09
			return -EINVAL;

I'm willing to send a radeon-card to somebody who is willing to invest
some time and install a 2.6 kernel. You perhaps?

A quick look through the radeon source doesn't show me any bit shift or
masks - all I see is using the acceleration engine, which is kind of
mumbo-jumbo for the un-initiated.

Could you perhaps point at certain routines that would be prime
suspects?

Thanks,
Jurriaan
--=20
A seminar on Time Travel will be held two weeks ago.
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6062 bogomips 0.06 0.39


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Linux-fbdev-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users

Re: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Jurriaan <thu...@xs...>]

From: Hihn, Jason <Jas...@ve...>
Date: Mon, Apr 05, 2004 at 02:46:43PM -0400

[sorry for remailing this private mail to the list again, but I hope
others will chime in]

> I don't know the 2.6 kernel tree, but I'd suspect radeonfb.c

unfortunately, that file doesn't exist in 2.6, which proves your first
point :-)

> 
> The low-level pixel get/set routines probably have a simple bit shift
> (<< >>) or mask (& |) error. "-inverse" was probably not taken into
> account when the code was written so the math is a little off. As far as
> I know, linux treats 24b as the same as 32, so maybe that's why your 24b
> isn't working, no one bothered to code it because you have to align on
> 4-byte boundaries  anyway (no one packs 3 bytes adjacent to 3 bytes,
> because it is too much work, you'd have to move then shift, and it gets
> messy and slow.). So someone would have written for 24, but in the end
> called it 32, so it's that extra byte that isn't being handled right.
> 
> I could probably fix it, if I had a radeon card and a 2.6 kernel and
> some time. Sorry.

I've since found out that the 24-bits is disallowed on purpose.

drivers/video/aty/radeon_base.c:
static int radeonfb_check_var (struct fb_var_screeninfo *var, struct fb_info *info)
{
		case 17 ... 24:
#if 0 /* Doesn't seem to work */
			v.bits_per_pixel = 24;
			break;
#endif			
			return -EINVAL;

I'm willing to send a radeon-card to somebody who is willing to invest
some time and install a 2.6 kernel. You perhaps?

A quick look through the radeon source doesn't show me any bit shift or
masks - all I see is using the acceleration engine, which is kind of
mumbo-jumbo for the un-initiated.

Could you perhaps point at certain routines that would be prime
suspects?

Thanks,
Jurriaan
-- 
A seminar on Time Travel will be held two weeks ago.
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6062 bogomips 0.06 0.39

RE: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Hihn, J. <Jas...@ve...>]

I don't know the 2.6 kernel tree, but I'd suspect radeonfb.c

The low-level pixel get/set routines probably have a simple bit shift
(<< >>) or mask (& |) error. "-inverse" was probably not taken into
account when the code was written so the math is a little off. As far as
I know, linux treats 24b as the same as 32, so maybe that's why your 24b
isn't working, no one bothered to code it because you have to align on
4-byte boundaries  anyway (no one packs 3 bytes adjacent to 3 bytes,
because it is too much work, you'd have to move then shift, and it gets
messy and slow.). So someone would have written for 24, but in the end
called it 32, so it's that extra byte that isn't being handled right.

I could probably fix it, if I had a radeon card and a 2.6 kernel and
some time. Sorry.

-----Original Message-----
From: Jurriaan [mailto:thu...@xs...]=20
Sent: Monday, April 05, 2004 1:30 PM
To: Hihn, Jason
Cc: lin...@li...
Subject: Re: [Linux-fbdev-users] radeonfb: strange blue lines after
'setterm -inversescreen on'

From: Hihn, Jason <Jas...@ve...>
Date: Mon, Apr 05, 2004 at 01:34:16PM -0400
> Just a guess... I'm not in 2.6, but it looks like the math to do the
> inverse screen is only using 24 bits, not 32. What is it like in
24bpp?
> Visually:
> *** (inverse mask)
> aRGB =3D 00 00 00 FF
>  ^^^ (normal mask)
> So it looks like there may be some 24/32 bit shifting going awry when
> -inversescreen is set.
>=20
This is a step in the right direction:

1600x1200-8@75: ok
1600x1200-16@75: blue screen
1600x1200-24@75: 'no mode found' in dmesg?
1600x1200-32@75: blue screen

apropos 24 bits:

Kernel command line: root=3D/dev/hda3 video=3Dradeonfb:1600x1200-24@75
acpi=3Dforce

radeonfb_pci_register BEGIN
radeonfb: probed DDR SGRAM 65536k videoram
radeonfb: mapped 16384k videoram
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=3D27.00 MHz (RefDiv=3D60) Memory=3D166.00 Mhz,
System=3D166.00 MHz
radeonfb: No connector info table detected
Starting monitor auto detection...
radeonfb: I2C (port 1) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: Monitor 1 type CRT found
radeonfb: ATI Radeon QD  DDR SGRAM 64 MB
radeonfb_pci_register END
Starting balanced_irq
ikconfig 0.7 with /proc/config*
Installing knfsd (copyright (C) 1996 ok...@mo...).
udf: registering filesystem
Limiting direct PCI/PCI transfers.
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU] (supports C1)
ACPI: Processor [CPU1] (supports C1)
ACPI: Thermal Zone [THRM] (28 C)
hStart =3D 664, hEnd =3D 760, hTotal =3D 800
vStart =3D 491, vEnd =3D 493, vTotal =3D 525
h_total_disp =3D 0x4f0063    hsync_strt_wid =3D 0x8c02a2
v_total_disp =3D 0x1df020c           vsync_strt_wid =3D 0x8201ea
pixclock =3D 39721
freq =3D 2517
post div =3D 0x3
fb_div =3D 0x1bf
ppll_div_3 =3D 0x301bf
lvds_gen_cntl: 00000000
Console: switching to colour frame buffer device 53x21

Well, b*gger. Did I mention I use the 12x22 font from sun?

Anyway, going to 8 bits color-depth solves my problem, but I'd rather
watch some photo's in at least 16-bit color depth. What part of the
driver is suspect?

Thanks,
Jurriaan

> If I boot linux-2.6.5, with a radeonfb framebuffer 1600x1200-32@75, I
> get white letters on a black background. Fine. If I issue the command
> setterm -inversescreen on, I get black letters on a white background.
>=20
> So far so good.
>=20
> Now if I press enter, I get a new line with black letters on a white
> background, but everything after the cursor is blue.
>=20
> Switching consoles (alt-f2, alt-f1) removes the blue line.
> Issuing 'clear' gives an entire blue screen after the cursor (so a
small
> part, the prompt, stays black-on-white).
>=20
> This is with a radeon 9000 and with a radeon 7000, so it must be
> something in general. Incidentally, blue is also the color the
overscan
> area gets.
>=20
> This has been happening on all 2.6.x kernels going back months.
>=20
--=20
Someone's stained
Someone's gained
Us or was it them?
	The men they couldn't hang - Rosettes
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6062 bogomips 0.52 0.19


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Linux-fbdev-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users

Re: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Jurriaan <thu...@xs...>]

From: Hihn, Jason <Jas...@ve...>
Date: Mon, Apr 05, 2004 at 01:34:16PM -0400
> Just a guess... I'm not in 2.6, but it looks like the math to do the
> inverse screen is only using 24 bits, not 32. What is it like in 24bpp?
> Visually:
> *** (inverse mask)
> aRGB = 00 00 00 FF
>  ^^^ (normal mask)
> So it looks like there may be some 24/32 bit shifting going awry when
> -inversescreen is set.
> 
This is a step in the right direction:

1600x1200-8@75: ok
1600x1200-16@75: blue screen
1600x1200-24@75: 'no mode found' in dmesg?
1600x1200-32@75: blue screen

apropos 24 bits:

Kernel command line: root=/dev/hda3 video=radeonfb:1600x1200-24@75 acpi=force

radeonfb_pci_register BEGIN
radeonfb: probed DDR SGRAM 65536k videoram
radeonfb: mapped 16384k videoram
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz
radeonfb: No connector info table detected
Starting monitor auto detection...
radeonfb: I2C (port 1) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: I2C (port 2) ... not found
radeonfb: I2C (port 3) ... not found
radeonfb: I2C (port 4) ... not found
radeonfb: Monitor 1 type CRT found
radeonfb: ATI Radeon QD  DDR SGRAM 64 MB
radeonfb_pci_register END
Starting balanced_irq
ikconfig 0.7 with /proc/config*
Installing knfsd (copyright (C) 1996 ok...@mo...).
udf: registering filesystem
Limiting direct PCI/PCI transfers.
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU] (supports C1)
ACPI: Processor [CPU1] (supports C1)
ACPI: Thermal Zone [THRM] (28 C)
hStart = 664, hEnd = 760, hTotal = 800
vStart = 491, vEnd = 493, vTotal = 525
h_total_disp = 0x4f0063    hsync_strt_wid = 0x8c02a2
v_total_disp = 0x1df020c           vsync_strt_wid = 0x8201ea
pixclock = 39721
freq = 2517
post div = 0x3
fb_div = 0x1bf
ppll_div_3 = 0x301bf
lvds_gen_cntl: 00000000
Console: switching to colour frame buffer device 53x21

Well, b*gger. Did I mention I use the 12x22 font from sun?

Anyway, going to 8 bits color-depth solves my problem, but I'd rather
watch some photo's in at least 16-bit color depth. What part of the
driver is suspect?

Thanks,
Jurriaan

> If I boot linux-2.6.5, with a radeonfb framebuffer 1600x1200-32@75, I
> get white letters on a black background. Fine. If I issue the command
> setterm -inversescreen on, I get black letters on a white background.
> 
> So far so good.
> 
> Now if I press enter, I get a new line with black letters on a white
> background, but everything after the cursor is blue.
> 
> Switching consoles (alt-f2, alt-f1) removes the blue line.
> Issuing 'clear' gives an entire blue screen after the cursor (so a small
> part, the prompt, stays black-on-white).
> 
> This is with a radeon 9000 and with a radeon 7000, so it must be
> something in general. Incidentally, blue is also the color the overscan
> area gets.
> 
> This has been happening on all 2.6.x kernels going back months.
> 
-- 
Someone's stained
Someone's gained
Us or was it them?
	The men they couldn't hang - Rosettes
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6062 bogomips 0.52 0.19

RE: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Hihn, J. <Jas...@ve...>]

Just a guess... I'm not in 2.6, but it looks like the math to do the
inverse screen is only using 24 bits, not 32. What is it like in 24bpp?
Visually:
*** (inverse mask)
aRGB =3D 00 00 00 FF
 ^^^ (normal mask)
So it looks like there may be some 24/32 bit shifting going awry when
-inversescreen is set.

Dunno.

-----Original Message-----
From: Jurriaan [mailto:thu...@xs...]=20
Sent: Monday, April 05, 2004 12:23 PM
To: lin...@li...
Subject: [Linux-fbdev-users] radeonfb: strange blue lines after 'setterm
-inversescreen on'

If I boot linux-2.6.5, with a radeonfb framebuffer 1600x1200-32@75, I
get white letters on a black background. Fine. If I issue the command
setterm -inversescreen on, I get black letters on a white background.

So far so good.

Now if I press enter, I get a new line with black letters on a white
background, but everything after the cursor is blue.

Switching consoles (alt-f2, alt-f1) removes the blue line.
Issuing 'clear' gives an entire blue screen after the cursor (so a small
part, the prompt, stays black-on-white).

This is with a radeon 9000 and with a radeon 7000, so it must be
something in general. Incidentally, blue is also the color the overscan
area gets.

This has been happening on all 2.6.x kernels going back months.

Is there something obvious I can check? A newer and better radeonfb
driver to download somewhere?

Thanks,
Jurriaan
--=20
The reason that lightning doesn't strike twice in the same place is that
the
same place isn't there the second time.
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6356 bogomips 0.30 0.13


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Linux-fbdev-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users

[Linux-fbdev-users] radeonfb: strange blue lines after 'setterm -inversescreen on'

[Jurriaan <thu...@xs...>]

If I boot linux-2.6.5, with a radeonfb framebuffer 1600x1200-32@75, I
get white letters on a black background. Fine. If I issue the command
setterm -inversescreen on, I get black letters on a white background.

So far so good.

Now if I press enter, I get a new line with black letters on a white
background, but everything after the cursor is blue.

Switching consoles (alt-f2, alt-f1) removes the blue line.
Issuing 'clear' gives an entire blue screen after the cursor (so a small
part, the prompt, stays black-on-white).

This is with a radeon 9000 and with a radeon 7000, so it must be
something in general. Incidentally, blue is also the color the overscan
area gets.

This has been happening on all 2.6.x kernels going back months.

Is there something obvious I can check? A newer and better radeonfb
driver to download somewhere?

Thanks,
Jurriaan
-- 
The reason that lightning doesn't strike twice in the same place is that the
same place isn't there the second time.
Debian (Unstable) GNU/Linux 2.6.5-rc3-mm3 2x6356 bogomips 0.30 0.13

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Sven L. <sve...@wa...>]

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

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Geert U. <ge...@li...>]

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

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Petr V. <van...@vc...>]

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

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Petr V. <van...@vc...>]

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...

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Sven L. <sve...@wa...>]

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

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Johan G. <so...@ho...>]

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

Re: [Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Jean D. <kh...@li...>]

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/

[Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Sven L. <sve...@wa...>]

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

[Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Johan G. <so...@ho...>]

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

[Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Johan G. <so...@ho...>]

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

[Linux-fbdev-users] Re: Matrox Millenium G450 AGP

[Sven L. <sve...@wa...>]

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

[Linux-fbdev-users] Matrox Millenium G450 AGP

[Johan G. <so...@ho...>]

(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

[Linux-fbdev-users] framebuffer on ATI Rage XL(PCI)

[Suresh C. M. <Ma...@Ga...>]

Dear Friends,
I am not able to initialize atyfb for my ATI Rage XL PCI on  p4 with 
kernel 2.4.20. After kernel booting starts screen in becoming blank with 
random dots(mostly green and white) specifying redhat init() OK's.
where as vga16fb is working properly. I tried loading as a module still 
same problem persist.
Does any body initialized atyfb framebuffer for ATI Rage XL.
Please send your .config and autoconf.h if you are successful.

I request your help regarding this.


Regards,
Suresh

[Linux-fbdev-users] Radeon 7000 problems with kernels after 2.6.3

[Jurriaan <thu...@xs...>]

On recent kernel (2.6.4 and later) my Radeon 7000 doesn't display
anything. My Eizo monitor warns me of really incompatible frequencies
(fV 217.2 Hz, fH 271.5 kHz). fbset returns normal values, by the way.

I've found out that this chunk in patch-2.6.4, applying to
drivers/video/aty/radeon_base.c, causes my problems:

@@ -1329,6 +1320,16 @@
         * not sure which model starts having FP2_GEN_CNTL, I assume anything more
         * recent than an r(v)100...
         */
+#if 0
+       /* XXX I had reports of flicker happening with the cinema display
+        * on TMDS1 that seem to be fixed if I also forbit odd dividers in
+        * this case. This could just be a bandwidth calculation issue, I
+        * haven't implemented the bandwidth code yet, but in the meantime,
+        * forcing uses_dvo to 1 fixes it and shouln't have bad side effects,
+        * I haven't seen a case were were absolutely needed an odd PLL
+        * divider. I'll find a better fix once I have more infos on the
+        * real cause of the problem.
+        */
        while (rinfo->has_CRTC2) {
                u32 fp2_gen_cntl = INREG(FP2_GEN_CNTL);
                u32 disp_output_cntl;
@@ -1362,6 +1363,9 @@
                uses_dvo = 1;
                break;
        }
+#else
+       uses_dvo = 1;
+#endif
        if (freq > rinfo->pll.ppll_max)
                freq = rinfo->pll.ppll_max;
        if (freq*12 < rinfo->pll.ppll_min)

If I change that #if 0 to #if 1, I get a normal image. This is with the
following video-card:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Radeon 7000/Radeon
        Flags: bus master, stepping, 66Mhz, medium devsel, latency 64, IRQ 16
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        I/O ports at a000 [size=256]
        Memory at e5000000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2


I've seen other messages about problems with radeonfb. Can other people
confirm this problem, and confirm that removing this chunk fixes the
problem?


Kind regards,
Jurriaan
-- 
Don't like these taglines? Steal your own...
Debian (Unstable) GNU/Linux 2.6.5-rc2-mm3 3940 bogomips 0.18 0.28

[Linux-fbdev-users] Re: [Linux-fbdev-devel] framebuffer on 4 MegaHertz FPGA

[Geert U. <ge...@li...>]

On Sat, 20 Mar 2004, Suresh Chandra Mannava wrote:
> We are facing the problem of initializing the framebuffer for the below
> system.
> We are porting Xfree86 on to a new 32bit RISC processor. We have test
> FPGA system running at 4 Mega Hertz (Bogomips 0.16) on kernel 2.4.7.
> proposed system(ASIC) runs on ~300Mhz.
>
> My main concern is does Xfree86 can be tested on 2.6Mhz FPGA?
> What is the minimum clock speed required to run X?

> Our test system supports 2GB of RAM and it consists of PCI ATI Rage XL
> Graphics card.

> We think that speed might be a problem.We need to findout first whether
> we will be able to run a framebuffer driver at 4 MHZ.Since framebuffer
> does pixel by pixel access,we think it will take a lot of time and
> anything can happen in between.We are now not in a position to predict
> what is happening.Please give your points on whether the framebuffer
> will work at such a low speed.
>
> I request your suggestions on feasibility of initializing framebuffer
> and testing X on the above system.

Since X was developed in mid-1980s (using unaccelerated graphics hardware) it
can definitely run on such slow CPU. Ater all your graphics card is quite fast.

And fbdev was developed on m68k machines, running on 16-50 MHz CPUs with
unaccelerated graphics hardware as well.

Of course you don't want to try GNOME and KDE, but simple things like twm and
xterm should be usable.

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