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

Re: [Linux-fbdev-users] rivafb question

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

On Thu, 7 Feb 2002, Alix Marchandise-Franquet wrote:
> I hope this is the right place to ask this question, if not can you please
> direct me to the appropriate newsgroup/mailing-list?
> 
> I am trying to use the rivafb driver with an nvidia Geforce 2MX card.
> I have a 2.4.16 kernel which I recompiled with rivafb.
> When I boot my machine, I see the penguin which goes away after a while.

If you see the penguin, you're using a frame buffer device.

> I don't think I am really using the framebuffer driver since with other
> framebuffer drivers and cards the penguin stayed there and the font got
> smaller. Also, nano-x, when compiled with the framebuffer setting
> doesn't run (but it runs fine when built and run with X11).
> 
> In the instructions for the vesafb driver, there are lines to add in
> lilo.conf, I don't know what these are for rivafb.
> 
> So my questions are:
> 1) How can I know that I am using rivafb?

cat /proc/fb

> 2) What needs to go in lilo.conf when using rivafb?

I guess nothing (autoprobing), unless you want to use a different video mode
than the default.

> 3) I couldn't find any real info on rivafb, where would it be?

Rivafb uses the standard video mode database, so please read
linux/Documentation/fb/modedb.txt.

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] rivafb question

[Alix Marchandise-F. <al...@ci...>]

Hello,

I hope this is the right place to ask this question, if not can you please
direct me to the appropriate newsgroup/mailing-list?

I am trying to use the rivafb driver with an nvidia Geforce 2MX card.
I have a 2.4.16 kernel which I recompiled with rivafb.
When I boot my machine, I see the penguin which goes away after a while.
I don't think I am really using the framebuffer driver since with other
framebuffer drivers and cards the penguin stayed there and the font got
smaller. Also, nano-x, when compiled with the framebuffer setting
doesn't run (but it runs fine when built and run with X11).

In the instructions for the vesafb driver, there are lines to add in
lilo.conf, I don't know what these are for rivafb.

So my questions are:
1) How can I know that I am using rivafb?
2) What needs to go in lilo.conf when using rivafb?
3) I couldn't find any real info on rivafb, where would it be?

Thank you very much

-alix

Re: [Linux-fbdev-users] tuning a set of fbdev timings

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

On Thu, Jan 24, 2002 at 09:21:35PM -0500, Brian J. Murrell wrote:
> On Thu, Jan 24, 2002 at 09:23:48PM +0100, Jurriaan on Alpha wrote:
> > When you start X,
> 
> You lost me.  Start X?  This is framebuffer mode timings I am doing
> here.
> 
> > and run xfig,
> 
> xfig?  As in:
> 
I must have been daydreaming. Try xvidtune.

Good luck,
Jurriaan
-- 
Mine alone is the country of my soul
        Marc Chagall
GNU/Linux 2.4.18-pre7 on Debian/Alpha 64-bits 990 bogomips load:0.25 0.35 0.17

Re: [Linux-fbdev-users] tuning a set of fbdev timings

[Brian J. M. <85e...@in...>]

On Thu, Jan 24, 2002 at 09:23:48PM +0100, Jurriaan on Alpha wrote:
> When you start X,

You lost me.  Start X?  This is framebuffer mode timings I am doing
here.

> and run xfig,

xfig?  As in:

  Xfig is an X Window System tool for creating basic vector graphics,
  including bezier curves, lines, rulers and more.  The resulting
  graphics can be saved, printed on PostScript printers or converted to
  a variety of other formats (e.g., X11 bitmaps, Encapsulated
  PostScript, LaTeX).
  
  You should install xfig if you need a simple program to create vector
  graphics.

> you can see what values change when you
> adapt certain values. Perhaps that helps?

I'm afraid not.  Does xfig somehow help one figure out framebuffer
mode timings?

b.

-- 
Brian J. Murrell

Re: [Linux-fbdev-users] tuning a set of fbdev timings

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

On Thu, Jan 24, 2002 at 02:51:26PM -0500, Brian J. Murrell wrote:
> I have a set of timings for the Linux FB that I want to tune a bit,
> but don't really want to start from scratch designing a new set of
> timings.  The fb.modes entry:
> 
> #
> #  From the teletux (teletux.sf.net) project's syncfb
> #
> #       640x480, 59.94 Hz, Non-Interlaced (25.175 MHz dotclock)
> #       
> #                               Horizontal      Vertical
> #       Resolution              640             480
> #       Scan Frequency          31.469 kHz      59.94 Hz
> #       Sync Width              3.813 us        0.064 ms
> #                               12 chars        2 lines
> #       Front Porch             0.636 us        0.318  ms
> #                               2 chars         10 lines
> #       Back Porch              1.907 us        1.048  ms
> #                               6 chars         33 lines
> #       Active Time             25.422 us       15.253 ms
> #                               80 chars        480 lines
> #       Blank Time              6.356 us        1.430 ms
> #                               20 chars        45 lines
> #       Polarity                negative        negative
> #
> 
> mode "640x480-NTSC-TV"
>     # D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz
>     geometry 640 480 640 480 16
>     timings 39722 48 16 33 10 96 2
> endmode
> 
> The problem is that on my Matrox G400, the picture is not wide enough
> and thusly leaves black bars on the sides.  I want to stretch the
> picture to the edges of the screen.  How hard/simple would this be to
> do?  Any hints on which values to tweak?
> 
When you start X, and run xfig, you can see what values change when you
adapt certain values. Perhaps that helps?

Good luck,
Jurriaan
-- 
Our tricorders don't recognize it, but it sure packs a wallop.
	Chakotay - Startrek Voyager
GNU/Linux 2.4.18-pre6 on Debian/Alpha 64-bits 988 bogomips load:1.15 1.31 1.09

[Linux-fbdev-users] tuning a set of fbdev timings

[Brian J. M. <508...@in...>]

I have a set of timings for the Linux FB that I want to tune a bit,
but don't really want to start from scratch designing a new set of
timings.  The fb.modes entry:

#
#  From the teletux (teletux.sf.net) project's syncfb
#
#       640x480, 59.94 Hz, Non-Interlaced (25.175 MHz dotclock)
#       
#                               Horizontal      Vertical
#       Resolution              640             480
#       Scan Frequency          31.469 kHz      59.94 Hz
#       Sync Width              3.813 us        0.064 ms
#                               12 chars        2 lines
#       Front Porch             0.636 us        0.318  ms
#                               2 chars         10 lines
#       Back Porch              1.907 us        1.048  ms
#                               6 chars         33 lines
#       Active Time             25.422 us       15.253 ms
#                               80 chars        480 lines
#       Blank Time              6.356 us        1.430 ms
#                               20 chars        45 lines
#       Polarity                negative        negative
#

mode "640x480-NTSC-TV"
    # D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz
    geometry 640 480 640 480 16
    timings 39722 48 16 33 10 96 2
endmode

The problem is that on my Matrox G400, the picture is not wide enough
and thusly leaves black bars on the sides.  I want to stretch the
picture to the edges of the screen.  How hard/simple would this be to
do?  Any hints on which values to tweak?

b.

-- 
Brian J. Murrell

[Linux-fbdev-users] Console at 800x480 Resolution?

[Patrick A K. <kir...@cs...>]

Hello,

I love having a higher resolution terminal straight from boot.  I have
a Toshiba Libretto 100CT that can do 800x480 resolution in X, but I'm
wondering if it could also be set to that resolution from the lilo.conf
"vga= " setting.  It has a NeoMagic graphics.

I've had good luck with vga=784 (640x480), and can even use 0x03 and
0x305 (but the screen is larger than my monitor will let me see - right
margin and lower margin are out of reach).  I know the unit could do it
if I could just find the  right setting number.

Others have found undocumented settings for resolutions like  1400x1050
(vga=830), so it must be possible, but again, this is not documented 
anywhere and that user just happened on it by pure accident.

Could anyone please help me figure out the  right setting number or maybe
tell me how I might extrapolate the setting  number from other data?

Thanks very much!

pK.

-- 
Patrick A. Kirchner
Linux Advocate, CNE, MCSE+I, A+, Network+
---

Re: [Linux-fbdev-users] Cursor

[Brad D. <br...@ne...>]

On Wed, 2002-01-09 at 11:06, Johan Henriksson wrote:
> Hi
>=20
> I am developing a program that uses the framebuffer.
> I have two questions I hope someone can answer:
>=20
> 1. How do I change the cursor that is used by the framebuffer.

AFAIK, this can only be done via vesafb or by driver specific commands.

> 2. When a driver is "accelerated" what can be accelerated?=20
>      Bitblit op? HW cursor? Paning?

It depends on the driver.  You'll have to look at the 'struct
display_switch' in the driver to see what functions are accelerated for
which color depth.

I haven't really looked over the code much in some time, so take my info
with an appropriate sized grain of salt.

Brad Douglas
br...@ne...

[Linux-fbdev-users] Cursor

[Johan H. <joh...@br...>]

Hi

I am developing a program that uses the framebuffer.
I have two questions I hope someone can answer:

1. How do I change the cursor that is used by the framebuffer.
2. When a driver is "accelerated" what can be accelerated?=20
     Bitblit op? HW cursor? Paning?

Regards

JH

Re: [Linux-fbdev-users] Possible problems with VESA Framebuffer

[Brad D. <br...@ne...>]

On Wed, 2002-01-09 at 09:31, Fent, Lee wrote:
> Can anyone tell me if the i810 chipset's built in video system is VESA 2.=
0
> compliant?  I'm having trouble getting a framebuffer to work with it unde=
r
> 2.4.x.

Lee,

The i810 chipset has no memory on the card -- it uses system memory.=20
This is why you are unable to use vesafb.

An i810 driver does exist somewhere.  I've seen it cross my path before.

Brad Douglas
br...@ne...

[Linux-fbdev-users] Possible problems with VESA Framebuffer

[Fent, L. <lee...@es...>]

Can anyone tell me if the i810 chipset's built in video system is VESA 2.0
compliant?  I'm having trouble getting a framebuffer to work with it under
2.4.x.

Thanks,
Lee

Re: [Linux-fbdev-users] fbdev info

[daniel s. <l5g...@ho...>]

James

Thanks for the reply. Where can I find more information about supported
video cards for fbdev? Do you know if any cards with DVI output are
supported?

Regards,
Daniel


>From: James Simmons <jsi...@tr...>
>To: daniel sheltraw <l5g...@ho...>
>CC: lin...@li...
>Subject: Re: [Linux-fbdev-users] fbdev info
>Date: Tue, 8 Jan 2002 19:41:54 -0800 (PST)
>
>
> > Hello fbdev list
> >
> > It seems that there has not been any updates to the linux-fbdev.org
> > home page since October 2000. Has the fbdev home been moved elsewhere?
>
>Nope. Same home page. Its just not a very dynamic site.
>
>


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

Re: [Linux-fbdev-users] fbdev info

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

> Hello fbdev list
> 
> It seems that there has not been any updates to the linux-fbdev.org
> home page since October 2000. Has the fbdev home been moved elsewhere?

Nope. Same home page. Its just not a very dynamic site.

[Linux-fbdev-users] fbdev info

[daniel s. <l5g...@ho...>]

Hello fbdev list

It seems that there has not been any updates to the linux-fbdev.org
home page since October 2000. Has the fbdev home been moved elsewhere?

Thanks,
Daniel



_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

[Linux-fbdev-users] access to framebuffer from remote login (maybe rtfm)

[Dirk J. <di...@xs...>]

Hi all. I am trying to start fbtv from an ssh to a pc with
the tv card inside. So far this doesn't work. 

Is this possible? I searched this mailinglist archive, read
the fb howto but didn't see what I needed. Maybe this is so
obvious that I just for overlook it. 

Thanks, 

Dirk

[Linux-fbdev-users] Multihead Framebuffer wierdness...

[David R. <da...@ma...>]

Hi folks,

I have an Apple Powermac 9500 running Yellowdoglinux 2.1 with a 2.4 
kernel. I have managed to get my Voodoo 2/3000 and and ATI Mach64 
card to work together in X Windows, however I can not get them past 8 
bit. I am using XFree86 4.10 with modes from fbset -x in the 
XF86Config-4.

The Voodoo card is /dev/fb0 and the ati is fb1. I have 
video=tdfx:noaccel,atyfb:noaccel in my kernel args on bootup, as 
acceleration is not supported...

I have been unable to use "map:01" to have consoles on each screen. 
Also, when I boot with the ATY as console and with noaccel it is 
unusable... jumping screen makes it unreadable.

When I use fbset at console I can set the voodoo up to 32 bit, and if 
I boot with the ati as console I can set it up to 24 bit.

If you need more details please ask!

TIA,

dAVE

[Linux-fbdev-users] voodoo 5 framebuffer (on Alpha) @ high pixclocks

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

I'm having trouble getting my voodoo 4500 pci working correctly on my
Alpha (kernel 2.4.17pre2).

If I use the stock-kernel, and specify
'video=tdfx:1600x1200-16@75,nohwcursor', my Eizo F930 switches off.
XFree works perfectly in 1600x1200-16@80.

If comment out this part:

#if 0
  if(freq > i->max_pixclock/2) {
    freq = freq > i->max_pixclock ? i->max_pixclock : freq;
    reg.dacmode |= DACMODE_2X;
    reg.vidcfg  |= VIDCFG_2X;
  }
#endif

it works, but I have a feeling I'm running out-of-spec now. 

So I downloaded the latest patch, 3dfx-20010507, and it doesn't work at
all. The system boots, but the screen stays black. I enabled debugging,


udf: registering filesystem
fb: tdfxfb_probe: PCI memory enabled. name=Voodoo 5 noinit=1
fb: tdfxfb_probe: fb: Voodoo 5 memory = 65536K
fb: tdfxfb_switch_con: start with fb Voodoo 5 pdsp=fffffc00001fc280 dsp=fffffc0000b13800 prevcon=-1 con=0
fb: tdfxfb_switch_con: start with fb Voodoo 5 pdsp=fffffc0000b13800 dsp=fffffc0000b13800 prevcon=0 con=0
fb: do_set_par: wrregs: vidcfg:04040483,dacmode:00000001,vidpll:00006114,freq:0003170f
Console: switching to colour frame buffer device 133x54
fb0: 3Dfx Voodoo 5 frame buffer device, 65536K @ 0x18000000
pty: 256 Unix98 ptys configured

and nothing looks wrong there. In fact, the vidcfg / dacmode values are
exactly the same as for the standard kernel, except for DACMODE_2X and
VIDCFG_2X.

If I comment out the DACMODE_2X/VIDCFG_2X part in the 20010507-driver,
the kernel crashes on boot.

Any hints on how to proceed? I've sent mail to the maintainers already,
BTW. No reaction so far, but it's only been 2 days or so.

Thanks,
Jurriaan
-- 
Linux hackers are funny people: They count the time in patchlevels.
	Gerd Knorr
GNU/Linux 2.4.17-pre2 on Debian/Alpha 64-bits 990 bogomips load:0.00 0.03 0.04

Re: [Linux-fbdev-users] ThinClient Configuration Issues

[Michael P. <mi...@wi...>]

Arrg.. I THOUGHT they were in the body.. 
Here are the logs..

bash-2.05$ cat /usr/xterminal/var/log/XFree86.0.log
The -bpp option is no longer supported.
        Use -depth to set the color depth, and use -fbbpp if you really
        need to force a non-default framebuffer (hardware) pixel format.

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XF...@XF... and patches submitted
to fi...@XF....  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.1.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: xx August 2001
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/FAQ)
Build Operating System: Linux 2.4.7 i686 [ELF]
Module Loader present
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Nov 19 21:17:26 2001
(==) Using config file: "/etc/X11/XF86Config-4"
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "VESA Framebuffer"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc101"
(**) XKB: model: "pc101"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Generic Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/75dpi/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/Type1" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/Speedo" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/75dpi" does not exist.
        Entry deleted from font path.
(**) FontPath set to 
"tcp/192.168.1.80:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/100dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(WW) Cannot open APM
(II) Module ABI versions:
        XFree86 ANSI C Emulation: 0.1
        XFree86 Video Driver: 0.4
        XFree86 XInput driver : 0.2
        XFree86 Server Extension : 0.1
        XFree86 Font Renderer : 0.2
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Font Renderer
        ABI class: XFree86 Font Renderer, version 0.2
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 0.1.0
        ABI class: XFree86 Video Driver, version 0.4
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,1250 card 0000,0000 rev 01 class 06,00,00
hdr 00
(II) PCI: 00:07:0: chip 8086,7000 card 0000,0000 rev 01 class 06,01,00
hdr 80
(II) PCI: 00:07:1: chip 8086,7010 card 0000,0000 rev 00 class 01,01,80
hdr 00
(II) PCI: 00:0f:0: chip 1013,00ac card 0000,0000 rev 00 class 03,00,00
hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: "scanpci"
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 0.1.0
        ABI class: XFree86 Video Driver, version 0.4
(II) UnloadModule: "scanpci"
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 0 I/O range:
        [0] -1 0        0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus -1 I/O range:
(II) Bus -1 non-prefetchable memory range:
(II) Bus -1 prefetchable memory range:
(--) PCI:*(0:15:0) Cirrus Logic GD5436 rev 0, Mem @ 0x40000000/24, BIOS
@ 
0x000c0000/15
(II) Addressable bus resource ranges are
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
        [1] -1 0        0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
        [0] -1 0        0xffe00000 - 0xffffffff (0x200000) MX[B](B)
        [1] -1 0        0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [2] -1 0        0x000f0000 - 0x000fffff (0x10000) MX[B]
        [3] -1 0        0x000c0000 - 0x000effff (0x30000) MX[B]
        [4] -1 0        0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [5] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [6] -1 0        0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
        [0] -1 0        0x000c0000 - 0x000c7fff (0x8000) MX[B](B)
        [1] -1 0        0x40000000 - 0x40ffffff (0x1000000) MX[B](B)
        [2] -1 0        0x00001000 - 0x0000100f (0x10) IX[B]
(II) Active PCI resource ranges after removing overlaps:
        [0] -1 0        0x000c0000 - 0x000c7fff (0x8000) MX[B](B)
        [1] -1 0        0x40000000 - 0x40ffffff (0x1000000) MX[B](B)
        [2] -1 0        0x00001000 - 0x0000100f (0x10) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
        [0] -1 0        0xffe00000 - 0xffffffff (0x200000) MX[B](B)
        [1] -1 0        0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [2] -1 0        0x000f0000 - 0x000fffff (0x10000) MX[B]
        [3] -1 0        0x000c0000 - 0x000c7fff (0x8000) MX[B]
        [4] -1 0        0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [5] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [6] -1 0        0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
        [0] -1 0        0xffe00000 - 0xffffffff (0x200000) MX[B](B)
        [1] -1 0        0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
        [2] -1 0        0x000f0000 - 0x000fffff (0x10000) MX[B]
        [3] -1 0        0x000c0000 - 0x000c7fff (0x8000) MX[B]
        [4] -1 0        0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [5] -1 0        0x000c0000 - 0x000c7fff (0x8000) MX[B](B)
        [6] -1 0        0x40000000 - 0x40ffffff (0x1000000) MX[B](B)
        [7] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [8] -1 0        0x00000000 - 0x000000ff (0x100) IX[B]
        [9] -1 0        0x00001000 - 0x0000100f (0x10) IX[B]
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Video Driver, version 0.4
(II) LoadModule: "GLcore"
(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
(II) Module GLcore: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Server Extension, version 0.1
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Server Extension
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a
(II) Module dri: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/X11R6/lib/modules/linux/libdrm.a
(II) Module drm: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Server Extension
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension FontCache
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 ANSI C Emulation, version 0.1
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.a
(II) Module glx: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Reloading /usr/X11R6/lib/modules/extensions/libGLcore.a
(II) Loading extension GLX
(II) LoadModule: "pex5"
(II) Loading /usr/X11R6/lib/modules/extensions/libpex5.a
(II) Module pex5: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Server Extension
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension X3D-PEX
(II) LoadModule: "record"
(II) Loading /usr/X11R6/lib/modules/extensions/librecord.a
(II) Module record: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.13.0
        Module class: XFree86 Server Extension
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension RECORD
(II) LoadModule: "xie"
(II) Loading /usr/X11R6/lib/modules/extensions/libxie.a
(II) Module xie: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Server Extension
        ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension XIE
(II) LoadModule: "bitmap"
(II) Reloading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Loading font Bitmap
(II) LoadModule: "freetype"
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a
(II) Module freetype: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.1.9
        Module class: XFree86 Font Renderer
        ABI class: XFree86 Font Renderer, version 0.2
(II) Loading font FreeType
(II) LoadModule: "speedo"
(II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a
(II) Module speedo: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Font Renderer
        ABI class: XFree86 Font Renderer, version 0.2
(II) Loading font Speedo
(II) LoadModule: "type1"
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 Font Renderer
        ABI class: XFree86 Font Renderer, version 0.2
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "vbe"
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Video Driver, version 0.4
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 Video Driver, version 0.4
(II) LoadModule: "fbdev"
(II) Loading /usr/X11R6/lib/modules/drivers/fbdev_drv.o
(II) Module fbdev: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 0.1.0
        ABI class: XFree86 Video Driver, version 0.4
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        Module class: XFree86 XInput Driver
        ABI class: XFree86 XInput driver, version 0.2
(II) FBDev: driver for framebuffer: fbdev, afb
(II) Primary Device is: PCI 00:0f:0
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 0.0.2
        ABI class: XFree86 Video Driver, version 0.4
(II) FBDev(0): using default device
(II) Running in FRAMEBUFFER Mode
(**) FBDev(0): Depth 16, (--) framebuffer bpp 16
(==) FBDev(0): RGB weight 565
(==) FBDev(0): Default visual is TrueColor
(==) FBDev(0): Using gamma correction (1.0, 1.0, 1.0)
(II) FBDev(0): Hardware: CLgen (vidmem: 1024k)
(II) FBDev(0): Checking Modes against framebuffer device...
(II) FBDev(0):  mode "640x480" ok
(II) FBDev(0): Checking Modes against monitor...
(--) FBDev(0): Virtual size is 640x480 (pitch 640)
(**) FBDev(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz),
31.5 
kHz, 60.0 Hz
(II) FBDev(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492
525 
-hsync -vsync
(==) FBDev(0): DPI set to (75, 75)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Reloading /usr/X11R6/lib/modules/libfb.a
(**) FBDev(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/X11R6/lib/modules/libshadow.a
(II) Module shadow: vendor="The XFree86 Project"
        compiled for 4.1.0.1, module version = 1.0.0
        ABI class: XFree86 ANSI C Emulation, version 0.1
(==) FBDev(0): Backing store disabled
(**) Option "dpms"
(**) FBDev(0): DPMS enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "MouseSystems"
(**) Generic Mouse: Protocol: "MouseSystems"
(**) Option "CorePointer"
(**) Generic Mouse: Core Pointer
(**) Option "Device" "/dev/gpmdata"
(==) Generic Mouse: Buttons: 3
(**) Option "Emulate3Buttons" "true"
(**) Generic Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Generic Mouse: ZAxisMapping: buttons 4 and 5
(**) Option "BaudRate" "9600"
(**) Generic Mouse: BaudRate: 9600
(II) XINPUT: Adding extended input device "Generic Mouse" (type: MOUSE)
(WW) Cannot open APM



bash-2.05$ xdpyinfo
name of display:    thinclient1.wizard.ca:0.0
version number:    11.0
vendor string:    The XFree86 Project, Inc
vendor release number:    40100001
XFree86 version: 4.1.0.1
maximum request size:  4194300 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x160000f, revert to PointerRoot
number of extensions:    28
    BIG-REQUESTS
    DOUBLE-BUFFER
    DPMS
    Extended-Visual-Information
    FontCache
    GLX
    LBX
    MIT-SCREEN-SAVER
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    RECORD
    RENDER
    SECURITY
    SGI-GLX
    SHAPE
    SYNC
    TOG-CUP
    XC-APPGROUP
    XC-MISC
    XFree86-Bigfont
    XFree86-DGA
    XFree86-Misc
    XFree86-VidModeExtension
    XIE
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    640x480 pixels (217x163 millimeters)
  resolution:    75x75 dots per inch
  depths (7):    16, 1, 4, 8, 15, 24, 32
  root window id:    0x2e
  depth of root window:    16 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x20
  default number of colormap cells:    64
  preallocated pixels:    black 0, white 65535
  options:    backing-store NO, save-unders NO
  largest cursor:    640x480
  current input event mask:    0xf84033
    KeyPressMask             KeyReleaseMask           EnterWindowMask
    LeaveWindowMask          KeymapStateMask
SubstructureNotifyMask
    SubstructureRedirectMask FocusChangeMask          PropertyChangeMask
    ColormapChangeMask
  number of visuals:    2
  default visual id:  0x22
  visual:
    visual id:    0x22
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x23
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    8 bits



On Tue, 2001-11-20 at 04:06, Geert Uytterhoeven wrote:
> On 19 Nov 2001, Michael Peddemors wrote:
> > Well I have a lot of them :)
> > Tried working them out myself, and finally gave in and trying the list..
> >
> > First of all.. I have an issue where I want to support many types of
> > Video cards with a single kernel..
> >
> > SO I compiled in all of the framebuffer hardwares into the kernel, and
> > also included the generic VESA VGA driver as well, thinking that it
> > would try the other hardwares, and fallback to VESA if it didn't find
> > any other hardwares..
> 
> That's correct for drivers that use the resource management system.
> 
> Note that there are still some drivers that don't use the resource management
> system, so you can get conflicts between vgafb/vesafg and each of these
> drivers.
> 
> > ThinClient logs attached..
> 
> No attachment found?
> 
> 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 mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users
> 
> 
-- 
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada

Re: [Linux-fbdev-users] ThinClient Configuration Issues

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

On 19 Nov 2001, Michael Peddemors wrote:
> Well I have a lot of them :)
> Tried working them out myself, and finally gave in and trying the list..
>
> First of all.. I have an issue where I want to support many types of
> Video cards with a single kernel..
>
> SO I compiled in all of the framebuffer hardwares into the kernel, and
> also included the generic VESA VGA driver as well, thinking that it
> would try the other hardwares, and fallback to VESA if it didn't find
> any other hardwares..

That's correct for drivers that use the resource management system.

Note that there are still some drivers that don't use the resource management
system, so you can get conflicts between vgafb/vesafg and each of these
drivers.

> ThinClient logs attached..

No attachment found?

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] ThinClient Configuration Issues

[Michael P. <mi...@wi...>]

Well I have a lot of them :)
Tried working them out myself, and finally gave in and trying the list..

First of all.. I have an issue where I want to support many types of
Video cards with a single kernel..

SO I compiled in all of the framebuffer hardwares into the kernel, and
also included the generic VESA VGA driver as well, thinking that it
would try the other hardwares, and fallback to VESA if it didn't find
any other hardwares..

(I am not sure if that is working correctly, but..)

Anyways, I have my thinclient booting up and it SEEMS to be in -depth 16

But I also see an entry where the significant bits are only 8 bits...
(see below)

My problem is that no matter what I seem to do I am getting only 256
color on the X display...

Thinclient is calling xdm on the host via
X -query <hostname>

ThinClient logs attached..

Any ThinClient experts with good configs to help out here?

-- 
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada

Re: [Linux-fbdev-users] matroxfb framebuffer

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

On Sat, Nov 17, 2001 at 07:24:37AM +0700, Bill Thompson wrote:
> Hi,
> 
> When my system boots, it comes up using vgafb. 
> How can I change this to use matroxfb?

If you have only one VGA device in your box, do not compile
vgafb. 

If you have more than one VGA device, and they are all Matroxes,
do not compile vgafb.

If you have more than one VGA device, and only some of them are
Matroxes, you must make Matrox your secondary device, as vgafb 
does handle only primary devices.

You can also disable vgafb at boottime by using
video=vga16:off, but I strongly recommend you to remove
vgafb from your kernel completely.
			Best regards,
				Petr Vandrovec
				van...@vc...

[Linux-fbdev-users] matroxfb framebuffer

[Bill T. <bi...@sa...>]

Hi,

When my system boots, it comes up using vgafb. 
How can I change this to use matroxfb?

Bill

Mandrake 8.1
XFree86 4.1.0-21mdk
Matrox G400 w/32MB SDRAM
-- 
"Quando Omni Flunkus Moritati"
(When all else fails, play dead!)

[Linux-fbdev-users] atyfb on a X21?

[jakeR <ja...@as...>]

hey there, can someone please tell me how to get my fb device working on an IBM
X21 notebook? i tried many arguments, but all result in a blank screen. 

i tried lots of stuff like:

video=atyfb:1024x768-8@60
video=atyfb,1024x768

and lots of other combinations. 

also, is this driver faster than the vesa driver? i can get that to work. 

thanks,

jake

Re: [Linux-fbdev-users] Problem with rivafb + NVdriver

[<R....@ir...>]

Dear Wolfram,

Thanks for the information. That explains the problem.
The advantage of using rivafb over vesafb is that it is
a lot faster, but I guess I have no choice. Hope eventually
Nvidia will either release their source, or ensure that their
drivers work with rivafb,

Regards,
Roger 
ro...@ma...

On Tue, Nov 13, 2001 at 06:06:03AM -0500, R....@ir... wrote:
> 
> I  wonder if you  can help with a problem  concerning  rivafb which is
> compiled  into the linux kernel (2.4.12).  On  my system (P3, 733 MHz,
> GA660+  graphics card with  RIVA  TNT2 chipset)  this  Riva fb  driver
> appears to be  incompatible with the   RIVA TNT2 (kernel/GLX)  drivers
> (v.1.0-1541) supplied by NVIDIA. What happens is that I get a complete
> system freeze on attempting to leave X, or to reboot/close down. This
> does not occur when rivafb is used in conjunction with the "nv" driver
> that is part  of XFree86 (v.4.1.0); nor does  it occur if I use vesafb
> with  the  NVIDIA kernel/GLX   "NVdriver";   but only when  rivafb  is
> combined with NVdriver. Because  of the freeze this combination (which
> is obviously desireable) is not really viable at the moment...
> 
> I will be very grateful if anyone can assist,

The rivafb and the NVdriver are simply not compatible, as they try
to access the same piece of hardware independently. Contact
Andy Ritger <AR...@nv...> for more information (he
recommends to use the "standard" vesafb instead).
-- 
Mit freundlichen Gruessen / Yours sincerely

Wolfram Schlich  *  E-Mail: wo...@sc...  *  ICQ: UIN 35713642
Postal: Berghof, D-56626 Andernach-Kell  *  Phone: +49-(0)2636-941194

Re: [Linux-fbdev-users] Problem with rivafb + NVdriver

[Wolfram S. <wo...@sc...>]

On Tue, Nov 13, 2001 at 06:06:03AM -0500, R....@ir... wrote:
> 
> I  wonder if you  can help with a problem  concerning  rivafb which is
> compiled  into the linux kernel (2.4.12).  On  my system (P3, 733 MHz,
> GA660+  graphics card with  RIVA  TNT2 chipset)  this  Riva fb  driver
> appears to be  incompatible with the   RIVA TNT2 (kernel/GLX)  drivers
> (v.1.0-1541) supplied by NVIDIA. What happens is that I get a complete
> system freeze on attempting to leave X, or to reboot/close down. This
> does not occur when rivafb is used in conjunction with the "nv" driver
> that is part  of XFree86 (v.4.1.0); nor does  it occur if I use vesafb
> with  the  NVIDIA kernel/GLX   "NVdriver";   but only when  rivafb  is
> combined with NVdriver. Because  of the freeze this combination (which
> is obviously desireable) is not really viable at the moment...
> 
> I will be very grateful if anyone can assist,

The rivafb and the NVdriver are simply not compatible, as they try
to access the same piece of hardware independently. Contact
Andy Ritger <AR...@nv...> for more information (he
recommends to use the "standard" vesafb instead).
-- 
Mit freundlichen Gruessen / Yours sincerely

Wolfram Schlich  *  E-Mail: wo...@sc...  *  ICQ: UIN 35713642
Postal: Berghof, D-56626 Andernach-Kell  *  Phone: +49-(0)2636-941194