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

[Linux-fbdev-users] framebuffer on 4 MegaHertz FPGA

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

Dear Friends,   

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 started testing the generic vga16fb.c framebuffer.The basic 
intialization seems to happen perfectly.The problem comes in 
take_over_console,where framebuffer takes over the dummy console.In the 
take over console,at first step he is calling fbcon_startup which is 
getting screen base ,X and Y coordinates and clearing that location.This 
happens fine.This function is called for after some timer interval and 
hence we can say that it will be called repeatedly.The problem is that 
we cann't put any printk in between as it adversely affects the 
flow(This we found after testing vga16fb.c rigorously on intel as well 
as on our FPGA).We traversed the source code and also through object 
dumps and found that nothing is wrong.The system seems to be hung after 
some time(It is able to clear the screen).We came to this conclusion 
after giving a run and waiting for 6 hours.

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.


Regards,
Suresh Chandra Mannava.

-- 
Suresh Chandra Mannava		
Software Engineer, Cornet Technology India, Chennai.
CSE, Research Student, Vellore Institute of Technology - India.
Email: mannava(at)vit.ac.in, Mobile: +919884278813

Re: [Linux-fbdev-users] radeon/2.6.5-rc1-mm1 sets strange frequencies

[James S. <jsi...@in...>]

> After booting 2.6.5-rc1-mm1 with this command-line:
> 
> kernel /vmlinuz-265rc1mm1 root=/dev/hda3 video=radeonfb:1600x1200-32@75 acpi=force
> 
> I get a warning on my monitor:
> 
> fH 271.5 kHz
> fV 217.2 Hz

I haven't seen that before :-/ The kernel isn't generating that. I just 
looked threw the code.

> That is obviously not what I meant by 1600x1200-32@75.
> 
> fbset -V tells me:
> 
> Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
> (C) Copyright 1995-1999 by Geert Uytterhoeven
> 
> 
> mode "1600x1200-75"
>     # D: 202.511 MHz, H: 93.755 kHz, V: 75.004 Hz
>     geometry 1600 1200 1600 1200 32
>     timings 4938 304 64 46 1 192 3
>     hsync high
>     vsync high
>     rgba 8/16,8/8,8/0,0/0
> endmode

This looks right.


> Obviously, it's bad that I define what video-mode I want and radeonfb
> starts changing that to bogus values. The monitor is an Eizo F931,
> connected via a Rose Electronics Vista KVM.

What is you want exactly?

[Linux-fbdev-users] radeon/2.6.5-rc1-mm1 sets strange frequencies

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

[this was meant to go to linux-kernel and fbdev-users at the same time,
but I made a typo. sorry]

After booting 2.6.5-rc1-mm1 with this command-line:

kernel /vmlinuz-265rc1mm1 root=/dev/hda3 video=radeonfb:1600x1200-32@75 acpi=force

I get a warning on my monitor:

fH 271.5 kHz
fV 217.2 Hz

That is obviously not what I meant by 1600x1200-32@75.

fbset -V tells me:

Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven


mode "1600x1200-75"
    # D: 202.511 MHz, H: 93.755 kHz, V: 75.004 Hz
    geometry 1600 1200 1600 1200 32
    timings 4938 304 64 46 1 192 3
    hsync high
    vsync high
    rgba 8/16,8/8,8/0,0/0
endmode

dmesg:

Console: switching to colour frame buffer device 133x54
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
radeonfb: Monitor 1 type CRT found
radeonfb: ATI Radeon QD  DDR SGRAM 64 MB

lspci:
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
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (2000ns min), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at a000 [size=256]
        Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
                Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
                Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

.config:

CONFIG_FB=y
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y

Obviously, it's bad that I define what video-mode I want and radeonfb
starts changing that to bogus values. The monitor is an Eizo F931,
connected via a Rose Electronics Vista KVM.

Any hints on solving this?

Thanks,
Jurriaan
-- 
Thesaurus (n): ancient reptile with excellent vocabulary.
Debian (Unstable) GNU/Linux 2.6.4-rc1-mm2 3940 bogomips load av: 0.00 0.00 0.00

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[James S. <jsi...@in...>]

> > I have the specs and the hardware. 
> 
> Any news on that ? Did you manage to rescue the specs from your damaged
> harddisk ? 

Not yet. I managed last night to finish the install on my system. 

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

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

On Mon, Mar 08, 2004 at 07:14:02PM +0000, James Simmons wrote:
> 
> > On Fri, Feb 27, 2004 at 05:36:22PM +0000, James Simmons wrote:
> > > 
> > > Its a endian issue. Been there :-( The voodoo card needs to be set to big 
> > > endian access.
> > 
> > Any hint on how to do that ? I have neither voodoo specs, nor access to
> > the hardware, still i would very much like to have it working.
> 
> I have the specs and the hardware. 

Any news on that ? Did you manage to rescue the specs from your damaged
harddisk ? 

Friendly,

Sven Luther

RE: [Linux-fbdev-users] Frambeffer to TV troubles

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

That is correct... Had it worked immediately, I'd not have bothered to
post ;-)

With the adjusted pixel clock, I am able to select between 640x480x16bpp
and 800x600x16bpp (perhaps others) using the vesa modes, without
trouble.  The weirdest thing was that fbset would change the patterns on
the TV, so I thought it was working. It looks like everything was
changing except the pixel clock...

=09

-----Original Message-----
From: Geert Uytterhoeven [mailto:ge...@li...]=20
Sent: Tuesday, March 09, 2004 5:17 AM
To: Hihn, Jason
Cc: lin...@li...
Subject: Re: [Linux-fbdev-users] Frambeffer to TV troubles

On Mon, 8 Mar 2004, Hihn, Jason wrote:
> I've got a ATI Graphics Expression+ PC2TV (ATI MACH64/Rage II GT) and
I
> finally got TV out to work. The perplexing thing was it's boot up and
> you could see output on the TV (using composite out), but when asked
for
> a video mode  it's lose it after that. I played around with fbset,
> getting the monitor to do all kinds of funky things, but never a
> picture.  (I was playing with resolutions and timings) Oh, and I was
> using the Vesa driver
>
>
>
> Then I went into include/linux/fb.h and made the default videomode's
> timings as I wanted: 20330, 128, 32, 32, 8, 128, 5 (NTSC) which
worked!
> Now I use mode 0x311 and I can get a picture. It seems that the
pixclock
> is hardcoded to some non-NTSC compatible values.

So if you pass these values using fbset, it doesn't work?

Strange...

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] Frambeffer to TV troubles

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

On Mon, 8 Mar 2004, Hihn, Jason wrote:
> I've got a ATI Graphics Expression+ PC2TV (ATI MACH64/Rage II GT) and I
> finally got TV out to work. The perplexing thing was it's boot up and
> you could see output on the TV (using composite out), but when asked for
> a video mode  it's lose it after that. I played around with fbset,
> getting the monitor to do all kinds of funky things, but never a
> picture.  (I was playing with resolutions and timings) Oh, and I was
> using the Vesa driver
>
>
>
> Then I went into include/linux/fb.h and made the default videomode's
> timings as I wanted: 20330, 128, 32, 32, 8, 128, 5 (NTSC) which worked!
> Now I use mode 0x311 and I can get a picture. It seems that the pixclock
> is hardcoded to some non-NTSC compatible values.

So if you pass these values using fbset, it doesn't work?

Strange...

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

[Linux-fbdev-users] Frambeffer to TV troubles

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

I've got a ATI Graphics Expression+ PC2TV (ATI MACH64/Rage II GT) and I
finally got TV out to work. The perplexing thing was it's boot up and
you could see output on the TV (using composite out), but when asked for
a video mode  it's lose it after that. I played around with fbset,
getting the monitor to do all kinds of funky things, but never a
picture.  (I was playing with resolutions and timings) Oh, and I was
using the Vesa driver

=20

Then I went into include/linux/fb.h and made the default videomode's
timings as I wanted: 20330, 128, 32, 32, 8, 128, 5 (NTSC) which worked!
Now I use mode 0x311 and I can get a picture. It seems that the pixclock
is hardcoded to some non-NTSC compatible values.=20

=20

I quickly tried to get the ATI driver working, but I never succeeded.
The Vesa driver works, but to try a new setting, I have to re-compile
and reboot.

=20

But I'd like to have it easier to do, I feel that I hacked it up and
that I'm doing something wrong. Can anyone give me some pointers? I'd
like to see my screen in 768x576 resolution, but there is no vesa mode
for that.

=20

Thanks

=20

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[James S. <jsi...@in...>]

> On Fri, Feb 27, 2004 at 05:36:22PM +0000, James Simmons wrote:
> > 
> > Its a endian issue. Been there :-( The voodoo card needs to be set to big 
> > endian access.
> 
> Any hint on how to do that ? I have neither voodoo specs, nor access to
> the hardware, still i would very much like to have it working.

I have the specs and the hardware. 

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

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

On Mon, Mar 08, 2004 at 05:44:17PM +0000, James Simmons wrote:
> 
> I have the specs on my hard drive that just crashed. I plan to recover the 
> data this week. It is possible to fix.

Ok, thanks.

Friendly,

Sven Luther

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[James S. <jsi...@in...>]

I have the specs on my hard drive that just crashed. I plan to recover the 
data this week. It is possible to fix.


On Mon, 8 Mar 2004, Sven Luther wrote:

> On Fri, Feb 27, 2004 at 05:36:22PM +0000, James Simmons wrote:
> > 
> > Its a endian issue. Been there :-( The voodoo card needs to be set to big 
> > endian access.
> 
> Any hint on how to do that ? I have neither voodoo specs, nor access to
> the hardware, still i would very much like to have it working.
> 
> Friendly,
> 
> Sven Luther
> 

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

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

On Fri, Feb 27, 2004 at 05:36:22PM +0000, James Simmons wrote:
> 
> Its a endian issue. Been there :-( The voodoo card needs to be set to big 
> endian access.

Any hint on how to do that ? I have neither voodoo specs, nor access to
the hardware, still i would very much like to have it working.

Friendly,

Sven Luther

Re: [Linux-fbdev-users] Problems with aty128fb and 2.6.xx

[Witold F. <wi...@po...>]

On Fri, Feb 27, 2004 at 05:40:36PM +0000, James Simmons wrote:
> 
> > Hello,
> > Aty128fb in 2.6.3 and earlier doesn't work as it should for me.
> > First, when CONFIG_VESA=Y I cannot load module aty128fb.
> 
> You can load the module. You need to use the con2fb utility to map the 
> consoles to that framebuffer device.
> 
> > Second, if VESA support is not compiled in I got black screen when switch
> > to another console. I used to use mode 1024x768-75. (128x76)
> 
> ??? What is your config like? What do you mean by switching to another 
> console.

I'm sorry to bother you, it's OK now.
Framebuffer was set by:
for i in 1 2 3 4 5 6 7 8; do
	/usr/bin/open -c $i -- /usr/bin/fbset -fb /dev/fb/0 -depth 16 1024x768-75
done

Adding -w resolves problems.

> > Third, it is still slow.
> 
> Its unaccelerated. It needs hardware acceleration.

ATI 128 Rage Pro has hardware acceleration. What else is required?
-- 
Witold Filipczyk tohu-bohu
<wi...@po...>

Re: [Linux-fbdev-users] Problems with aty128fb and 2.6.xx

[Witold F. <wi...@po...>]

On Fri, Feb 27, 2004 at 05:40:36PM +0000, James Simmons wrote:
> 
> > Hello,
> > Aty128fb in 2.6.3 and earlier doesn't work as it should for me.
> > First, when CONFIG_VESA=Y I cannot load module aty128fb.
> 
> You can load the module. You need to use the con2fb utility to map the 
> consoles to that framebuffer device.
> 
> > Second, if VESA support is not compiled in I got black screen when switch
> > to another console. I used to use mode 1024x768-75. (128x76)
> 
> ??? What is your config like? What do you mean by switching to another 
> console.

ALT-F2, ALT-F3

Config in attachment.

> 
> 
> > Third, it is still slow.
> 
> Its unaccelerated. It needs hardware acceleration.

-- 
Witold Filipczyk tohu-bohu
<wi...@po...>

Re: [Linux-fbdev-users] Problems with aty128fb and 2.6.xx

[James S. <jsi...@in...>]

> Hello,
> Aty128fb in 2.6.3 and earlier doesn't work as it should for me.
> First, when CONFIG_VESA=Y I cannot load module aty128fb.

You can load the module. You need to use the con2fb utility to map the 
consoles to that framebuffer device.

> Second, if VESA support is not compiled in I got black screen when switch
> to another console. I used to use mode 1024x768-75. (128x76)

??? What is your config like? What do you mean by switching to another 
console.


> Third, it is still slow.

Its unaccelerated. It needs hardware acceleration.

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[James S. <jsi...@in...>]

Its a endian issue. Been there :-( The voodoo card needs to be set to big 
endian access.



On Tue, 27 Feb 2024, Mikael Karlsson wrote:

> 
> 
> On Fri, 27 Feb 2004, Sven Luther wrote:
> 
> > On Tue, Feb 27, 2024 at 08:22:25AM +0100, Mikael Karlsson wrote:
> > > Hello...
> > >
> > > I got trouble to get the fbdev driver to work with XFree86 on my Pegasos
> > > with A Voodoo4 card.  I get corrupt colors in colordepth ove 8bits.   I
> > > tried to set the settings with fbset and so on. Is there anyway to get
> > > this thing to work with 16bpp?
> >
> > These problems extend when using the X server with the fbdev driver,
> > right ?
> 
> Yes  they do.   I get very wired colors in X.  It looks like rainbow
> colors over the screen. In 8bpp modes it looks good and no corrupt colors.
> I also tried the tdfx driver and it hangs in color depth over 8bpp.
> 
> 
> /Mikael Karlsson
> 
> 
> 
> >
> > Friendly,
> >
> > Sven Luther
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Linux-fbdev-users mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> >
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> 

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[Mikael K. <lis...@hj...>]

On Fri, 27 Feb 2004, Sven Luther wrote:

> On Tue, Feb 27, 2024 at 08:22:25AM +0100, Mikael Karlsson wrote:
> > Hello...
> >
> > I got trouble to get the fbdev driver to work with XFree86 on my Pegasos
> > with A Voodoo4 card.  I get corrupt colors in colordepth ove 8bits.   I
> > tried to set the settings with fbset and so on. Is there anyway to get
> > this thing to work with 16bpp?
>
> These problems extend when using the X server with the fbdev driver,
> right ?

Yes  they do.   I get very wired colors in X.  It looks like rainbow
colors over the screen. In 8bpp modes it looks good and no corrupt colors.
I also tried the tdfx driver and it hangs in color depth over 8bpp.


/Mikael Karlsson



>
> Friendly,
>
> Sven Luther
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>

Re: [Linux-fbdev-users] Voodoo4 4500 AGP on PPC

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

On Tue, Feb 27, 2024 at 08:22:25AM +0100, Mikael Karlsson wrote:
> Hello...
> 
> I got trouble to get the fbdev driver to work with XFree86 on my Pegasos
> with A Voodoo4 card.  I get corrupt colors in colordepth ove 8bits.   I
> tried to set the settings with fbset and so on. Is there anyway to get
> this thing to work with 16bpp?

These problems extend when using the X server with the fbdev driver,
right ? 

Friendly,

Sven Luther

[Linux-fbdev-users] Voodoo4 4500 AGP on PPC

[Mikael K. <lis...@hj...>]

Hello...

I got trouble to get the fbdev driver to work with XFree86 on my Pegasos
with A Voodoo4 card.  I get corrupt colors in colordepth ove 8bits.   I
tried to set the settings with fbset and so on. Is there anyway to get
this thing to work with 16bpp?


/Mikael Karlsson

[Linux-fbdev-users] Problems with aty128fb and 2.6.xx

[Witold F. <wi...@po...>]

Hello,
Aty128fb in 2.6.3 and earlier doesn't work as it should for me.
First, when CONFIG_VESA=Y I cannot load module aty128fb.
Second, if VESA support is not compiled in I got black screen when switch
to another console. I used to use mode 1024x768-75. (128x76)

On 2.4 it works fine in both cases.
Third, it is still slow.

How can I help to fix these problems?
-- 
Witold Filipczyk tohu-bohu
<wi...@po...>

[Linux-fbdev-users] Scrambled output with new radeonfb driver

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

Hi all,

I decided to give a try to the new radeonfb driver (Linux 2.6.3-rc3) on
my new Radeon 9200-based graphics card ("Ya" if that matters). The
driver works overall good and could detect the correct DFP size with no
parameter given, which is more than the Linux 2.4 driver was able to do.

However, at the moment the driver is initialized, I got scambled output
in the upper left hand corner of my screen. I've taken a snapshot of it
using my webcam, available here:
http://jdelvare.net1.nerim.net/radeonfb/radeonfb.jpeg

Is it a known problem? Is there some parameter I can pass to the driver
to prevent the problem? Or do I just have to live with it?

It doesn't seem to cause trouble otherwise, so this is in no way a
critical problem, but I'm a curious guy.

Thanks.

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

[Linux-fbdev-users] radeon mobility U1

[Samy C. <sa...@fr...>]

hello
vesafb is OK but I can't have framebuffer working for this chip (radeon 
IGP320M) on presario900 with radeon driver.
I tried both methods: compiled with module and inside the kernel (2.4.24 
and 2.6.2)
my grub option is "video=radeon:1024x768" I elso tried 
"video=radeonfb:1024x768"
I elso tried to follow the infos (kernel patch) from 
http://www.cse.buffalo.edu/~cd9/radeonfb.html
but nothing to do: still 80col, no linux bitmap and dmesg doesn't give 
any clue to radeonfb...

Any advices/clues?
cheers

Re: [Linux-fbdev-users] Support for Radeon Mobility 9000 in 2.6

[Michael G. <mi...@it...>]

On Tue, 13 Jan 2004 18:41:25 +0000 (GMT)
James Simmons <jsi...@in...> wrote:

> 
> Instead of modules can you buiold everything into your kernel and let me 
> know if you still have a problem.
> 
> 
I haven't tried this yet, but I got it partly working with this patch.

	http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1-rc1/2.6.1-rc1-mm1/broken-out/radeon-line-length-fix.patch

Partly means, after patching a vanilla 2.6.1 with the above patch, the framebuffer works after insmodding the radeonfb module but:

	* Color depth 16 gives me a green or blue background
	* Color depth 24 gives "ioctl FBIOPUT_VSCREENINFO: Invalid argument"
	* Switching from X to console blanks it. fbset -depth <other depth> brings it back
          again

/Michael

[Linux-fbdev-users] Latest FBDev patch

[Kilian C. <kil...@cr...>]

Hi all,

First of all, my problem : I have a Dell D800 laptop (the problem is not
here ^_^), with a wide 1920x1200 screen, and I'd like to run a
framebuffer console in this mode, with a 2.6.x kernel. The video card is
a nVidia GeForce4 Ti 4200 Go, and
my X server uses the following modeline :
"1920x1200" 162 1920 1968 2160 2176 1200 1201 1204 1206 +hsync +vsync


Then , my experiments.
I tried to use :
- vesafb driver, from vanilla 2.6.1 : it runs ok in 1600x1200 (with
vertical black bars, each side of the screen), since 1920x1200 is not a
'standard' VESA mode. I think it would be possible to add this 16:10
mode in modedb.c, or whatever vesafb uses, but I'm not experienced
enough too really do it.
- rivafb driver, from vanilla 2.6.1 : does not detect any framebuffer
device at all, and run in plain old 80x25. Not what I want.

So, I just tried the latest FBDev patch from James Simmons :
- no change with vesafb, since I don't know which code I could put in
the vga= kernel option
- rivafb gives me no ouput at all : after decompressing the kernel
image, when it usually switch to fb mode, the screen remains blank, with
only two small colored dots, flashing middle left and up right of the
screen. Not very usable. :)

So I'd like to know :
- is this video card supported by the rivafb driver ?
- is it possible to add the 1920x1200 mode, for vesafb to use it ?
- how can I help to add support for this configuration ?

TIA,

-- 
Kilian CAVALOTTI | GPGKeyId: 0xD657340C
BOFH excuse #148:
Insert coin for new game

Re: [Linux-fbdev-users] Support for Radeon Mobility 9000 in 2.6

[James S. <jsi...@in...>]

Instead of modules can you buiold everything into your kernel and let me 
know if you still have a problem.


On Wed, 7 Jan 2004, Michael Guntsche wrote:

> Hi,
> 
> I have been running 2.4.2* with radeonfb on my Radeon Mobility 9000 on
> an Acer TravelMate 800LCi without a problem.
> But after switching to 2.6 the framebuffer no longer works.
> 
> 	* The driver in vanilla 2.6 gives me distorted output.
> 	* The driver from Ben's tree (penguinppc rsync) gives me distorted
>           output too.
> 	* James latest fbdev.diff gives no output at all. (Only the backlight
>           stays on)
> 
> Here is part of the syslog after inserting the module (patched with
> fbdev.diff).
> 
> modprobe radeonfb:
> 
> 
> Jan  6 10:43:21 localhost kernel: radeonfb_pci_register BEGIN
> Jan  6 10:43:21 localhost kernel: radeonfb: probed DDR SGRAM 65536k
> videoram
> Jan  6 10:43:21 localhost kernel: radeonfb: Invalid ROM signature 0
> should be 0xaa55
> Jan  6 10:43:21 localhost kernel: radeonfb: Used default PLL infos
> Jan  6 10:43:21 localhost kernel: radeonfb: Reference=27.00 MHz
> (RefDiv=67) Memory=166.00 Mhz, System=166.00 MHz
> Jan  6 10:43:21 localhost kernel: Starting monitor auto detection...
> Jan  6 10:43:21 localhost kernel: Non-DDC laptop panel detected
> Jan  6 10:43:21 localhost kernel: radeonfb: Monitor 1 type LCD found
> Jan  6 10:43:21 localhost kernel: radeonfb: Monitor 2 type no found
> Jan  6 10:43:21 localhost kernel: Guessing panel info...
> Jan  6 10:43:21 localhost kernel: radeonfb: Asssuming panel size 1400x1050
> Jan  6 10:43:21 localhost kernel: radeonfb: Power Management enabled for Mobility chipsets
> Jan  6 10:43:21 localhost kernel: radeonfb: ATI Radeon Lf  DDR SGRAM 64 MB
> Jan  6 10:43:21 localhost kernel: radeonfb_pci_register END
> 
> modprobe fbcon:
> The screen blanks afterwards, but the machine still runs.
> 
> Jan  6 13:11:00 localhost kernel: hStart = 664, hEnd = 760, hTotal = 800
> Jan  6 13:11:00 localhost kernel: vStart = 409, vEnd = 411, vTotal = 450
> Jan  6 13:11:00 localhost kernel: h_total_disp = 0x4f0063^I  hsync_strt_wid = 0x8c0292
> Jan  6 13:11:00 localhost kernel: v_total_disp = 0x18f01c1^I vsync_strt_wid = 0x820198
> Jan  6 13:11:00 localhost kernel: pixclock = 39729
> Jan  6 13:11:00 localhost kernel: freq = 2517
> Jan  6 13:11:00 localhost kernel: post div = 0x8                        
> Jan  6 13:11:00 localhost kernel: fb_div = 0x1f4
> Jan  6 13:11:00 localhost kernel: ppll_div_3 = 0x301f4 
> Jan  6 13:11:00 localhost kernel: lvds_gen_cntl: 003dffa5               
> Jan  6 13:11:00 localhost kernel: Console: switching to colour frame buffer device 80x25
> 
> Can someone tell me if radeonfb in 2.6 should work with my card right
> now, or if this is a known problem?
> 
> Thanks in advance,
> Michael Guntsche 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Linux-fbdev-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
>