Xfree86 version 4.01

Xfree86 version 4.01

[John Grimes]

Decided to try Xfree86 version 4 again (it had been a few
months).  Recompiled, fixed up XF86Config and amazingly I now have 24 bit
color, 1280x1024, r128 accelerated X.  It is decidely faster than Xpmac
and its a great start.

But I want more :)

For some reason I can not get any other mode to work
(i.e. 640x480,1024x768, 800x600).  If any would fail I would expect it to
be 1280x1024 not the smaller modes.  I have no modelines defined, just
letting XF86 decided which modes to use.  Any ideas why the defaults don't
work?

Next is getting multiple monitors (Xinema) to work.  I know there has
been
discussion of this on the list.

First how do I find out the bus address of my internal video?  It doesn't
show up in /proc/pci although it is in /proc/fb.  This is on a
highly upgraded powercenter.

Also, I seem to have not saved it as I had thought, but does anyone have
an example XF86Config file for multiple monitors?

Congrats to the people who have worked on this, it is definetely an
improvement.

							john





On Mon, 24 Jul 2000, Peter R. Wood wrote:

>
> Regarding my last message, please Cc: any replies to me, as I am receiving
> in digest mode. Thanks.
>
> Peter
>
> --
> Peter R. Wood          pwood@gordon.edu
> Computer Science       | Lightning    |
> Gordon College         | Samurai      |
> Wenham, MA             | Action!!!!!! |
>
>
>

--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michael Schmitz]

> For some reason I can not get any other mode to work
> (i.e. 640x480,1024x768, 800x600).  If any would fail I would expect it to
> be 1280x1024 not the smaller modes.  I have no modelines defined, just
> letting XF86 decided which modes to use.  Any ideas why the defaults don't
> work?

The default does work, and it's the only one that works. Missing any mode
lines, XFree queries the kernel frame buffer driver for the current mode
line (at least it does that for Mach64 which heavily uses the fbdevhw
module) and uses that.

Try setting the console video mode to a variety of other modes you'd like
to use in X (man vmode), then run fbset -x on each mode (this prints
the XFree mode definition that corresponds to the current video mode) and
append the output to a file. When done, edit the modes in that file to
give each a unique meaningful name, and include these mode definitions in
/etc/X11/XF86Config.

> Next is getting multiple monitors (Xinema) to work.  I know there has
> been
> discussion of this on the list.

Xinerama, and you'll need multiple video cards for this as I don't think
any kernel or user space driver knows how to drive f.e. the LCD and VGA
out at the same time, with different displays on it.

> First how do I find out the bus address of my internal video?  It doesn't
> show up in /proc/pci although it is in /proc/fb.  This is on a
> highly upgraded powercenter.

lspci -vv should show your PCI video device.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[John Grimes]

Mike,
	Will trying using fbset to create the modelines, that would
certainly explain why only 1280x1024 works.
	Yes i have 2 video cards, I have the pci rage128gl and the
internal (platinum I think) video that comes with all powercenters.  An
lspci does not show the internal video.  Could this be a kernel build
config issue?  I thought I included support for the internal apple
video.  I off course have this working in the MacOS.
				Thanks,
				John


On Mon, 24 Jul 2000, Michael Schmitz wrote:

> > For some reason I can not get any other mode to work
> > (i.e. 640x480,1024x768, 800x600).  If any would fail I would expect it to
> > be 1280x1024 not the smaller modes.  I have no modelines defined, just
> > letting XF86 decided which modes to use.  Any ideas why the defaults don't
> > work?
>
> The default does work, and it's the only one that works. Missing any mode
> lines, XFree queries the kernel frame buffer driver for the current mode
> line (at least it does that for Mach64 which heavily uses the fbdevhw
> module) and uses that.
>
> Try setting the console video mode to a variety of other modes you'd like
> to use in X (man vmode), then run fbset -x on each mode (this prints
> the XFree mode definition that corresponds to the current video mode) and
> append the output to a file. When done, edit the modes in that file to
> give each a unique meaningful name, and include these mode definitions in
> /etc/X11/XF86Config.
>
> > Next is getting multiple monitors (Xinema) to work.  I know there has
> > been
> > discussion of this on the list.
>
> Xinerama, and you'll need multiple video cards for this as I don't think
> any kernel or user space driver knows how to drive f.e. the LCD and VGA
> out at the same time, with different displays on it.
>
> > First how do I find out the bus address of my internal video?  It doesn't
> > show up in /proc/pci although it is in /proc/fb.  This is on a
> > highly upgraded powercenter.
>
> lspci -vv should show your PCI video device.
>
> 	Michael
>

--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michael Schmitz]

> 	Yes i have 2 video cards, I have the pci rage128gl and the
> internal (platinum I think) video that comes with all powercenters.  An
> lspci does not show the internal video.  Could this be a kernel build
> config issue?  I thought I included support for the internal apple
> video.  I off course have this working in the MacOS.

This probably means Apple didn't assign the platinum chip a separare bus
ID and function code. I couldn't find any trace of PCI code in platinumfb
so I guess you need to use fbdev there which should fall back to opening
/dev/fb? devices if no bus ID is known.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michel Dänzer]

John Grimes wrote:

> For some reason I can not get any other mode to work (i.e. 640x480,1024x768,
> 800x600).  If any would fail I would expect it to be 1280x1024 not the
> smaller modes.  I have no modelines defined, just letting XF86 decided which
> modes to use.  Any ideas why the defaults don't work?

Look at the log. There should be a reason for every rejected mode.


> First how do I find out the bus address of my internal video?  It doesn't
> show up in /proc/pci although it is in /proc/fb.  This is on a highly
> upgraded powercenter.

If it's not in /proc/pci, the server probably doesn't bother about it either,
so you shouldn't have to care.

> Also, I seem to have not saved it as I had thought, but does anyone have
> an example XF86Config file for multiple monitors?

You have to add Device and Screen (and maybe Monitor) Sections for the
internal video (I suppose it needs the fbdev driver?). And then you have to
add a Layout Section, something like this:

Section "ServerLayout"
    Identifier	"Main Layout"
    Screen	"Screen 1"
    Screen	"Screen 2" RightOf "Screen 1"
    InputDevice	"Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
EndSection


Good luck,

Michel


--
Nice little planet you've got there. Shame if anything were to happen to it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[John Grimes]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 2013 bytes --]


On Mon, 24 Jul 2000, Michel [iso-8859-1] Dänzer wrote:

> John Grimes wrote:
>
> > For some reason I can not get any other mode to work (i.e. 640x480,1024x768,
> > 800x600).  If any would fail I would expect it to be 1280x1024 not the
> > smaller modes.  I have no modelines defined, just letting XF86 decided which
> > modes to use.  Any ideas why the defaults don't work?
>
> Look at the log. There should be a reason for every rejected mode.

There aren't any rejected modes.  I think the suggestion taht I use fbset
to create modelines is right on.

>
>
> > First how do I find out the bus address of my internal video?  It doesn't
> > show up in /proc/pci although it is in /proc/fb.  This is on a highly
> > upgraded powercenter.
>
> If it's not in /proc/pci, the server probably doesn't bother about it either,
> so you shouldn't have to care.
>
> > Also, I seem to have not saved it as I had thought, but does anyone have
> > an example XF86Config file for multiple monitors?
>

ahh, i think i see now.  By defining a fb device the fbdev driver will
figure it wou, unlike the r128 driver which wanted a bus id.  Will give it
a try, how do I do fbset -x to see the modelines on the second monitor?


> You have to add Device and Screen (and maybe Monitor) Sections for the
> internal video (I suppose it needs the fbdev driver?). And then you have to
> add a Layout Section, something like this:
>
> Section "ServerLayout"
>     Identifier	"Main Layout"
>     Screen	"Screen 1"
>     Screen	"Screen 2" RightOf "Screen 1"
>     InputDevice	"Mouse1" "CorePointer"
>     InputDevice "Keyboard1" "CoreKeyboard"
> EndSection
>
>
> Good luck,
>
> Michel
>
>
>


				thanks a lot,
				john

--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michel Dänzer]

John Grimes wrote:

> > > For some reason I can not get any other mode to work (i.e.
> > > 640x480,1024x768, 800x600).  If any would fail I would expect it to be
> > > 1280x1024 not the smaller modes.  I have no modelines defined, just
> > > letting XF86 decided which modes to use.  Any ideas why the defaults
> > > don't work?
> >
> > Look at the log. There should be a reason for every rejected mode.
>
> There aren't any rejected modes.

How exactly do they not work then?

> I think the suggestion taht I use fbset to create modelines is right on.

Try it, but I think if that was the problem your modes would get rejected. Do
you use Option "UseFBDev"?


> > > First how do I find out the bus address of my internal video?  It
> > > doesn't show up in /proc/pci although it is in /proc/fb.  This is on a
> > > highly upgraded powercenter.
> >
> > If it's not in /proc/pci, the server probably doesn't bother about it
> > either, so you shouldn't have to care.
>
> ahh, i think i see now.  By defining a fb device the fbdev driver will
> figure it wou,

Yes. If the internal video isn't the default framebuffer device (where the
initial console comes up on), you'll have to add

	Option	"fbdev" "/dev/fb1"

in its Device Section though.

> unlike the r128 driver which wanted a bus id.

Actually, the bus ID is needed there because the higher level PCI code of the
X server will deactivate the chip otherwise. :)

(it can't determine the connection between the PCI and framebuffer devices
automatically)


> how do I do fbset -x to see the modelines on the second monitor?

There's an fbset option to select the framebuffer device, the second monitor
is probably /dev/fb1 .


Michel


--
UNIX is like Sex:
If you don't know it, you don't miss it. But if you know it, you'll need it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[John Grimes]

>
> > > > For some reason I can not get any other mode to work (i.e.
> > > > 640x480,1024x768, 800x600).  If any would fail I would expect it to be
> > > > 1280x1024 not the smaller modes.  I have no modelines defined, just
> > > > letting XF86 decided which modes to use.  Any ideas why the defaults
> > > > don't work?
> > >
> > > Look at the log. There should be a reason for every rejected mode.
> >
> > There aren't any rejected modes.
>
> How exactly do they not work then?
>
> > I think the suggestion taht I use fbset to create modelines is right on.
>
> Try it, but I think if that was the problem your modes would get rejected. Do
> you use Option "UseFBDev"?

Your right, didn't work.  I still can use only 1280x1024, the other modes
are definetely screwed up when I cycle through them although I am using
modelines taken from fbset -x.  So I don't know what's wrong.  Some modes
are rejected but all of these should be rejected (1600x1200, ...)  It
definetely s finding modes it thinks are OK (or using my modelines) but it
isn't working.



>
>
> > > > First how do I find out the bus address of my internal video?  It
> > > > doesn't show up in /proc/pci although it is in /proc/fb.  This is on a
> > > > highly upgraded powercenter.
> > >
> > > If it's not in /proc/pci, the server probably doesn't bother about it
> > > either, so you shouldn't have to care.
> >
> > ahh, i think i see now.  By defining a fb device the fbdev driver will
> > figure it wou,
>
> Yes. If the internal video isn't the default framebuffer device (where the
> initial console comes up on), you'll have to add
>
> 	Option	"fbdev" "/dev/fb1"
>
yup, this was exactly what I needed, unfortunately althought i definetely
is finding this monitor it is not working either.  However I suspect this
is a monitor config issue and will keep working on it (or maybe try
another monitor).



> in its Device Section though.
>
> > unlike the r128 driver which wanted a bus id.
>
> Actually, the bus ID is needed there because the higher level PCI code of the
> X server will deactivate the chip otherwise. :)
>
> (it can't determine the connection between the PCI and framebuffer devices
> automatically)
>
>
> > how do I do fbset -x to see the modelines on the second monitor?
>
> There's an fbset option to select the framebuffer device, the second monitor
> is probably /dev/fb1 .

yup, found this is in the man page last night.

					thanks,
					john

PS As per earlier discussions of random lockups in linux that I thought
was related to either the frame buffer, X, or some people suggested sound
I was still getting this lockup wth XF864.01 (but it never happens if I am
not in my X console) However, I recompiled my kernel last night 2.2.17
from 2.2.14 so we shall see if that works out.




>
>
> Michel
>
>
>





--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michel Dänzer]

John Grimes wrote:

> > > > > For some reason I can not get any other mode to work (i.e.
> > > > > 640x480,1024x768, 800x600).  If any would fail I would expect it to
> > > > > be 1280x1024 not the smaller modes.  I have no modelines defined,
> > > > > just letting XF86 decided which modes to use.  Any ideas why the
> > > > > defaults don't work?
> > > >
> > > > Look at the log. There should be a reason for every rejected mode.
> > >
> > > There aren't any rejected modes.
> >
> > How exactly do they not work then?
> >
> > > I think the suggestion taht I use fbset to create modelines is right on.
> >
> > Try it, but I think if that was the problem your modes would get rejected.
> > Do you use Option "UseFBDev"?
>
> Your right, didn't work.  I still can use only 1280x1024, the other modes
> are definetely screwed up when I cycle through them although I am using
> modelines taken from fbset -x.  So I don't know what's wrong.  Some modes
> are rejected but all of these should be rejected (1600x1200, ...)  It
> definetely s finding modes it thinks are OK (or using my modelines) but it
> isn't working.

So it looks like that bug still isn't fixed.

Ani, Ben, Kostas, Kevin: Any reason the r128 driver can't use fbdevhw to set
up modes? (like glint)


> > If the internal video isn't the default framebuffer device (where the
> > initial console comes up on), you'll have to add
> >
> >       Option  "fbdev" "/dev/fb1"
> >
> yup, this was exactly what I needed, unfortunately althought i definetely
> is finding this monitor it is not working either.  However I suspect this
> is a monitor config issue and will keep working on it (or maybe try
> another monitor).

Does the console work there? If yes, just don't specify any modelines and it
will use the console mode.

And beware: With Xinerama, all screens must have the same depth...


Michel


--
The three Rs of Microsoft support: Retry, Reboot, Reinstall.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[John Grimes]

>
> Does the console work there? If yes, just don't specify any modelines and it
> will use the console mode.


Nope, console doesn't work for the 2nd monitor so suspect a config issue
on my side.  Will continue to work on.  Although how would I even get to
the 2nd monitor on the console, will moving the mouse get me there?  Or is
it higher console numbers?

Although I should add the console does work for the main r128 driven
monitor and using fbset I can change modes.

>
> And beware: With Xinerama, all screens must have the same depth...
>
yup, knew that, X is so painful with colors anyway I wouldn't even know
how some one could do this otherwise (imagine an 8 bit with a 32 bit
monitor, what would happen with taht color map when it swicthed windows :)


				thanks,
				John

>
> Michel
>
>
>

--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michel Dänzer]

John Grimes wrote:
>
> >
> > Does the console work there? If yes, just don't specify any modelines and
> > it will use the console mode.
>
> Nope, console doesn't work for the 2nd monitor so suspect a config issue
> on my side.  Will continue to work on.  Although how would I even get to
> the 2nd monitor on the console, will moving the mouse get me there?  Or is
> it higher console numbers?

First of all, you have to boot the kernel with a second video= paramater for
the internal video (offb may pick it up automatically, don't know).

There are 2 possibilities:

Either also add something like video=map:000111 as a kernel parameter.
Meaning:                                 ^^^
First three virtual consoles on first monitor (fb0)
                                            ^^^
The remaing three on the second one (fb1)

I hope you get the idea...


Or, you can change the mapping between consoles and fbs with a script called
fb2conmap or similar. It's in the Debian fbset package, let's hope it's also
in LinuxPPC...


Michel


--
Pauli's exclusive, Heisenberg's uncertain, and Schroedinger just waves.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Benjamin Herrenschmidt]

>
>So it looks like that bug still isn't fixed.
>
>Ani, Ben, Kostas, Kevin: Any reason the r128 driver can't use fbdevhw to set
>up modes? (like glint)
>
>
>> > If the internal video isn't the default framebuffer device (where the
>> > initial console comes up on), you'll have to add
>> >
>> >       Option  "fbdev" "/dev/fb1"
>> >
>> yup, this was exactly what I needed, unfortunately althought i definetely
>> is finding this monitor it is not working either.  However I suspect this
>> is a monitor config issue and will keep working on it (or maybe try
>> another monitor).
>
>Does the console work there? If yes, just don't specify any modelines and it
>will use the console mode.
>
>And beware: With Xinerama, all screens must have the same depth...

I didn't follow the thread from the beginning, so I may have missed
something. The r128 driver on top of fbdev works nicely for me and all
machines I've tested so far (g4 and Pismo). Note however that the stock
XF4.0.1 don't have the patch to probe PLL values from the card and may be
working with incorrect hard-coded values.

I think Franz Sirl RPMs do have the probe code.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michael Schmitz]

> I didn't follow the thread from the beginning, so I may have missed
> something. The r128 driver on top of fbdev works nicely for me and all
> machines I've tested so far (g4 and Pismo). Note however that the stock

The problem was with platinumfb not aty128 IIRC. aty128 worked fine for
him.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[John Grimes]

Depends what proble we are talking about.

I have been unable to get anything but 1280x1024 to work correctly for
r128.  The others are deifnetely not be probed correctly but it sounds
like I need a patch which I shall apply and will magically be better :)

For platinumfb I have had no luck either, but I suspect that is just that
I don't have things configed correctly (also will try another monitor
although it works in mac).

				john



On Tue, 25 Jul 2000, Michael Schmitz wrote:

>
> > I didn't follow the thread from the beginning, so I may have missed
> > something. The r128 driver on top of fbdev works nicely for me and all
> > machines I've tested so far (g4 and Pismo). Note however that the stock
>
> The problem was with platinumfb not aty128 IIRC. aty128 worked fine for
> him.
>
> 	Michael
>
>
>

--
           John Grimes - Mission Planner for Chandra X-Ray Telescope
Phone 	(H) 617-591-1393	(W) 617-496-7663	(Fax) 617-495-7356
Email 	me@johngrimes.com	Web	http://www.johngrimes.com
Pager	1-800-473-6312 		Alphanumeric  4736312@mobilecomm.net)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Xfree86 version 4.01

[Michael Schmitz]

> Depends what proble we are talking about.
>
> I have been unable to get anything but 1280x1024 to work correctly for
> r128.  The others are deifnetely not be probed correctly but it sounds
> like I need a patch which I shall apply and will magically be better :)

Ok, can you please set the console to 1024x768 or 800x600 before starting
X, then start the X server with the default mode used? Just to sort out
whether it's a problem in the kernel aty128fb driver (which should be
setting the mode on behalf of X in the default mode case) or X itself.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

RE: Xfree86 version 4.01

[tjw4]

>===== Original Message From John Grimes <jpgrimes@johngrimes.dyndns.org>
=====
<snip>
>Next is getting multiple monitors (Xinema) to work.  I know there has
>been
>discussion of this on the list.
>
>First how do I find out the bus address of my internal video?  It doesn't
>show up in /proc/pci although it is in /proc/fb.  This is on a
>highly upgraded powercenter.
>
>Also, I seem to have not saved it as I had thought, but does anyone have
>an example XF86Config file for multiple monitors?
>

Could someone who has gotten dual-headed support working post a FAQ of some
sort about it?  I'm interested in getting it working on my Pismo, but will
more than likely need some help with it.  Thanks.

Tim


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/