Xfree86 4.0

Xfree86 4.0

[James B. Parker]

I downloaded the source code to Xfree86 4.0 and built/installed it.
Everything seemed to go well.  Now my Xserver is unable to start.

Two observations:

_first_
It asks for a file call libqt.0.2 or something like that (I know the libqt
part is correct).  Although this problem may have cleared up after I built
it a second time, I tried to reinstall KDE from a rpm (thinking this may
solve the second issue) and a message was displayed requesting the above
mentioned file.

_second_
When I try to start the server (xinit, startx, X) there is a fatal error:
no screens

So what is libqt# and how do I remedy this issue and what is the story with
the screens?  I am unfamiliar with screens and the need for them in Xserver.

Anyway, any info is appreciated!
James B. Parker

Mac G3 266mhz beige rev. 2


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

Re: Xfree86 4.0

[Nelson Abramson]

"James B. Parker" wrote:

> _first_
> It asks for a file call libqt.0.2 or something like that (I know the libqt
> part is correct).  Although this problem may have cleared up after I built
> it a second time, I tried to reinstall KDE from a rpm (thinking this may
> solve the second issue) and a message was displayed requesting the above
> mentioned file.

I would assume that libqt (probably libqt.so.2 or something like that) is part
of the qt developement package..

According to rpmfind.net, libqt.so.2 is provided by the qt package, you
probably also want the qt-devel package.

> _second_
> When I try to start the server (xinit, startx, X) there is a fatal error:
> no screens

What is the fatal error?  I don't think this would be related to the libqt, as
qt is a kde package for graphics, and shouldn't be related to the X server
working/not working (AFAIK).

What is the fatal error?

HTH
--Nelson Abramson

--
Shouldn't people be arrested and persecuted for engaging in their
constitutional rights?  http://www.opendvd.org


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

Re: Xfree86 4.0

[James B. Parker]

<snip> from pogtal@erols.com on 3/13/00 1:55 PM

> "James B. Parker" wrote:
>
>> _first_
>> It asks for a file call libqt.0.2 or something like that (I know the libqt
>> part is correct).  Although this problem may have cleared up after I built
>> it a second time, I tried to reinstall KDE from a rpm (thinking this may
>> solve the second issue) and a message was displayed requesting the above
>> mentioned file.
>
> I would assume that libqt (probably libqt.so.2 or something like that) is part
> of the qt developement package..
>
> According to rpmfind.net, libqt.so.2 is provided by the qt package, you
> probably also want the qt-devel package.

I was a little incorrect.  It is looking for liqt.so.1 and I have libqt.so.2
in my libs folder.  But I will install the qt dev package and see what
happens.

>
>> _second_
>> When I try to start the server (xinit, startx, X) there is a fatal error:
>> no screens
>
> What is the fatal error?  I don't think this would be related to the libqt, as
> qt is a kde package for graphics, and shouldn't be related to the X server
> working/not working (AFAIK).
>
> What is the fatal error?

>> no screens
no screens

James


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

Re: Xfree86 4.0

[Michael Schmitz]

> I downloaded the source code to Xfree86 4.0 and built/installed it.
> Everything seemed to go well.  Now my Xserver is unable to start.

You'll need to create a new XF86Config (XFree86 -configure should, in
theory, do that).
Depending on your kind of video hardware, XFree 4.0 will just not work at
this time. I spent the last few days debugging the X server on my Lombard
and almost trashed my installation in the process. It seems with the new
XFree release, the X server on PPC finally became equally unstable as the
Intel one :-)

I'll sit back and wait for specific patches to try (on top of cleaning up
the mess that my latest test left, backing up my system, and creating an
emergency boot zip).

	Michael

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

Re: Xfree86 4.0

[James B. Parker]

<snip> from schmitz@mail.biophys.uni-duesseldorf.de on 3/13/00 1:59 PM

> You'll need to create a new XF86Config (XFree86 -configure should, in
> theory, do that).
> Depending on your kind of video hardware, XFree 4.0 will just not work at
> this time. I spent the last few days debugging the X server on my Lombard
> and almost trashed my installation in the process. It seems with the new
> XFree release, the X server on PPC finally became equally unstable as the
> Intel one :-)
> Michael
>
>

Actually, I do have a XF86Config file.  After the build/install I ran
Xconfigurator (it finally recognized 6mb of vram) and then just skipped the
test section.

BTW, my video hardware is the basic rage pro found in rev. 2 G3's.  I am
pretty sure Xconfig recognized the chip.  My main problem now is just
solving the "no screens" issue.

So what are screens and where are they located?

James

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

Re: Xfree86 4.0

[phandel]

On Mon, 13 Mar 2000, James B. Parker wrote:

> Actually, I do have a XF86Config file.  After the build/install I ran
> Xconfigurator (it finally recognized 6mb of vram) and then just skipped the
> test section.

Xconfigurator & Xautoconfig will not create an XF86Config file that
XFree86 4.0 can use.  Check out one of Kostas' examples, or send me a note
and I'll send you mine.


Thanks,
Peter


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

Re: Xfree86 4.0

[Michael Schmitz]

> > Actually, I do have a XF86Config file.  After the build/install I ran
> > Xconfigurator (it finally recognized 6mb of vram) and then just skipped the
> > test section.
>
> Xconfigurator & Xautoconfig will not create an XF86Config file that
> XFree86 4.0 can use.  Check out one of Kostas' examples, or send me a note
> and I'll send you mine.

Please post an URL for Kostas' example files :-) I'd also like to compare
my hand-edited config with something known to work on LinuxPPC.

	Michael


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