does any of you run framebuffer other than vesafb on slackware 10.0 with
2.4.26 kernel ?

I have matox g450 I used matroxfb before on 9.1
I have disabled vesafb which was compiled in the kernel and instead
compiled id matrox framebuffer support. This works for 9.1 and for 10.0
with 2.6.7 kernel.

I also pass the right parameters to the kernel.

Patryk

In <pan.2004.08.27.09.38.57.215886@poczta.onet.pl>, patryk wrote:

> does any of you run framebuffer other than vesafb on slackware 10.0 with
> 2.4.26 kernel ?
>
> I have matox g450 I used matroxfb before on 9.1 I have disabled vesafb
> which was compiled in the kernel and instead compiled id matrox
> framebuffer support. This works for 9.1 and for 10.0 with 2.6.7 kernel.
>
> I also pass the right parameters to the kernel.
>
> Patryk

What difficulties are you having with matroxfb in 2.4? I found it worked
fine.

One thing to look out for is that the matroxfb modeline string is
different in 2.6 versus 2.4, so you can't use the same command line.

So to start in 1024x768x32 framebuffer mode, you would put
'video=matrox:vesa:0x118' in 2.4, and 'video=matroxfb:vesa:0x118' in 2.6.

--
Not to have been a dupe, that will have been my best possesion, my best
deed, to have been a dupe, wishing I wasn't, thinking I wasn't, knowing
I was, not being a dupe of not being a dupe.
--Samuel Beckett, The Unnamable

On Fri, 27 Aug 2004 19:57:12 +0000, lobotomy wrote:

> In <pan.2004.08.27.09.38.57.215886@poczta.onet.pl>, patryk wrote:
> What difficulties are you having with matroxfb in 2.4? I found it worked
> fine.
do you use slackware 10.0, did you recompile 2.4. kernel or do you use
the module matrox or matroxfb

I think my problem has smth to do with udev system org with the kernle


> So to start in 1024x768x32 framebuffer mode, you would put
> 'video=matrox:vesa:0x118' in 2.4, and 'video=matroxfb:vesa:0x118' in 2.6.
yes this is a parto w dmesg, kernel option are ok

Linux version 2.4.26 (root@tree) (gcc version 3.3.4) #6 Mon Jun 14
19:07:27 PDT 2004 Kernel command line: BOOT_IMAGE=LinuxFB ro root=302
video=matrox:vesa:0x118 Initializing CPU#0
Detected 451.026 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 897.84 BogoMIPS
-
Patryk

In <pan.2004.08.27.23.38.09.986686@poczta.onet.pl>, patryk wrote:

> On Fri, 27 Aug 2004 19:57:12 +0000, lobotomy wrote:
>
>> In <pan.2004.08.27.09.38.57.215886@poczta.onet.pl>, patryk wrote: What
>> difficulties are you having with matroxfb in 2.4? I found it worked
>> fine.
> do you use slackware 10.0, did you recompile 2.4. kernel or do you use the
> module matrox or matroxfb
>

I recompiled the kernel with the fb driver compiled in statically, so it
switches to fb console automatically during boot (even if no boot options
are given, it runs in 640x480 fb mode).

> I think my problem has smth to do with udev system org with the kernle

udev won't work with 2.4, and shouldn't start unless the /sys filesystem
is mounted. Since 2.4 doesn't support sysfs, the init scripts won't start
udev when running a 2.4 kernel.

--
Not to have been a dupe, that will have been my best possesion, my best
deed, to have been a dupe, wishing I wasn't, thinking I wasn't, knowing
I was, not being a dupe of not being a dupe.
--Samuel Beckett, The Unnamable

In <pan.2004.08.27.23.38.09.986686@poczta.onet.pl>, patryk wrote:


> do you use slackware 10.0, did you recompile 2.4. kernel or do you use the
> module matrox or matroxfb
>

Oh yeah, it is slackware 10.0

--
Not to have been a dupe, that will have been my best possesion, my best
deed, to have been a dupe, wishing I wasn't, thinking I wasn't, knowing
I was, not being a dupe of not being a dupe.
--Samuel Beckett, The Unnamable

On Sat, 28 Aug 2004 19:04:26 +0000, lobotomy wrote:

> In <pan.2004.08.27.23.38.09.986686@poczta.onet.pl>, patryk wrote:
>
>> On Fri, 27 Aug 2004 19:57:12 +0000, lobotomy wrote:
>>
>>> In <pan.2004.08.27.09.38.57.215886@poczta.onet.pl>, patryk wrote: What
>>> difficulties are you having with matroxfb in 2.4? I found it worked
>>> fine.
>> do you use slackware 10.0, did you recompile 2.4. kernel or do you use the
>> module matrox or matroxfb

now i know what was the problem, the simlink in /boot directory
i must have overwirtten vmlinuz with some kerenl image

Now everything works fine.
BTW have you tried second head tvout ?

Patryk