X...

X...

[Alex deVries]

On Sat, 28 Feb 1998 ralf@uni-koblenz.de wrote:
> On Fri, Feb 27, 1998 at 07:17:28PM -0500, Alex deVries wrote:
> > Miguel?  What's up with X exactly?  Are you short on hw specs?
> It's more that days tend to have only 48 hours ...

Oh.  Uh, any parts that I can help out on?  I appear to have a weekend
free now.

- Alex

X

[Joe Berens]

Hello,

I have compiled X on my Indy running linux following the directions found
at http://honk.physik.uni-konstanz.de/~agx/mipslinux/x/x.html.  When i to
startx it seems to start X but no x ever shows up.  From
/var/log/xdm-errrors:

XFree86 Version 4.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 6400)
Release Date: 1 July 2000
        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)
Operating System: Linux 2.1.100 mips [ELF] 
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 15 11:32:55 2000
(==) Using config file: "/etc/X11/XF86Config"
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (??) unknown.
(==) ServerLayout "simple layout"
(**) |-->Screen "Screen 1" (0)
(**) |   |-->Monitor "SGI GDM17e11"
(**) |   |-->Device "Newport Graphics"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
        Entry deleted from font path.
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(--) using VT number 7

(EE) No OS PCI support available
(II) v4l driver for Video4Linux
(II) Newport: driver for Newport Graphics Card: XL
(**) Newport(0): Depth 8, (--) framebuffer bpp 8
(==) Newport(0): Default visual is PseudoColor
(==) Newport(0): Using gamma correction (1.0, 1.0, 1.0)
xdm error (pid 4268): Hung in XOpenDisplay(:0), aborting
xdm error (pid 4268): server open failed for :0, giving up
xdm error (pid 4265): Display :0 cannot be opened

Any help?

Thank you,

Joe



___________________________________

Joe Berens
SGI Customer Support Center
Operating Systems Group
Phone: 800-800-4744, Direct: 651-683-3254
Email: jberens@sgi.com

___________________________________

Re: X

[Guido Guenther]

On Thu, Nov 16, 2000 at 03:10:53PM -0600, Joe Berens wrote:
> Hello,
> 
> I have compiled X on my Indy running linux following the directions found
> at http://honk.physik.uni-konstanz.de/~agx/mipslinux/x/x.html.  When i to
> startx it seems to start X but no x ever shows up.  From
> /var/log/xdm-errrors:
> 
[..snip..] 
> Operating System: Linux 2.1.100 mips [ELF] 
> xdm error (pid 4268): Hung in XOpenDisplay(:0), aborting
> xdm error (pid 4268): server open failed for :0, giving up
> xdm error (pid 4265): Display :0 cannot be opened
I've never seen this kind of error before but the kernel you're using is
ancient, probably switching to a more recent one helps (2.2.16 and
2.4.0-test9 work fine for me). What version of glibc are you using? If
it is as old as your kernel you won't get anything to work.( I'm using
2.0.6-5lm here).
Regards,
 -- Guido

X

[George Gensure,,,]

When I build X, in the execution of several key programs for 
installation, like xkbcomp, and in the execution of nearly all the base 
X utilities, like xdm, I receive a bus error.  Does anyone have any idea 
how to build to avoid this problem?  I'm building on an r5000 Indy.

George
werkt@csh.rit.edu

Re: X

[Guido Guenther]

On Thu, Apr 19, 2001 at 02:37:29AM -0400, George Gensure,,, wrote:
> When I build X, in the execution of several key programs for 
> installation, like xkbcomp, and in the execution of nearly all the base 
> X utilities, like xdm, I receive a bus error.  Does anyone have any idea 
> how to build to avoid this problem?  I'm building on an r5000 Indy.
What toolchain/glibc are you using? 
 -- Guido

X

[Daniel Provin]

Hi there

Is there any program that usualy change the XF86Config file?
cause everytime I change my XF86Config and start X it go back to the
original

thanks
Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X

[Ray Olszewski]

At 01:24 PM 9/25/02 -0300, you wrote:
>Hi there
>
>Is there any program that usualy change the XF86Config file?
>cause everytime I change my XF86Config and start X it go back to the
>original


Depends a bit on the distro, but I can't think of any common app that would 
rewrite XF86Config *every* time you start X.

Perhaps you'd benefit from telling us the details?

1. What distro and version?

2. How do you start X? (startx, xdm, something else)?

3. What version of X? (At least on some distros, X 4.x.x uses a config file 
called XF86Config-4, not the older XF86Config used with X 3.x.x. Might you 
be editing the wrong file?)

4. What changes are you making (or trying to make)? Might you be making a 
change that does not work? And how are you making the changes -- editing 
XF86Config in vi, using xf86config, something else?

5. Exactly what do you mean by "it go back to the original"? Examples of 
what you *might* mean are:

         A. the changes in XF86Config do not show up in the way X starts.
         B. after starting X, you open XF86Config again, and the changes 
you made are lost.
         C. The same as B, plus the XF86Config file has an old timestamp, 
not a recent one.

In cases B and C, if you edit the XF86Config file, save it, close your 
editor, restart your editor, and open XF86Config again (without starting X 
in the meantime), do you see the changes you made?


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X

[pa3gcu]

On Wednesday 25 September 2002 16:59, Ray Olszewski wrote:
> At 01:24 PM 9/25/02 -0300, you wrote:
> >Hi there
> >
> >Is there any program that usualy change the XF86Config file?
> >cause everytime I change my XF86Config and start X it go back to the
> >original
>
> Depends a bit on the distro, but I can't think of any common app that would
> rewrite XF86Config *every* time you start X.
>
> Perhaps you'd benefit from telling us the details?
>
> 1. What distro and version?
>
> 2. How do you start X? (startx, xdm, something else)?
>
> 3. What version of X? (At least on some distros, X 4.x.x uses a config file
> called XF86Config-4, not the older XF86Config used with X 3.x.x. Might you
> be editing the wrong file?)

If i may point out that XFre86-4.x.x "does" use XF86Config, it will use it as 
default "if" no XF86Config-4 is found.
I use XFree86-4.2.0 on one machine here and i "dont" have a -4 file.
It is documented and it was decided to make XFree86-4.x.x look for both files 
to make it backwards compatable.

Another handy hint is that XFree86-4.x.x now writes a complete log of every 
boot into /var/log called XFree86.0.log (if .0 is found then it will be .1) 
and so on.
You can see what config file is used in that log file + so much more than the 
old way of capturing its output at starttime.
(But i dont think i needed to tell Ray that) i just wanted to make a point of 
the "-4" thing.

The rest of the excelant stuff snipped.

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: X

[Daniel Provin]

I already solved my problem. The thing was that I was writing on the
XF86Config instead of the XF86Config-4

thanks
Daniel Provin
Lixux User #191271
EEL LABMETRO UFSC

On Wed, 25 Sep 2002, Ray Olszewski wrote:

> At 01:24 PM 9/25/02 -0300, you wrote:
> >Hi there
> >
> >Is there any program that usualy change the XF86Config file?
> >cause everytime I change my XF86Config and start X it go back to the
> >original
>
>
> Depends a bit on the distro, but I can't think of any common app that would
> rewrite XF86Config *every* time you start X.
>
> Perhaps you'd benefit from telling us the details?
>
> 1. What distro and version?
>
> 2. How do you start X? (startx, xdm, something else)?
>
> 3. What version of X? (At least on some distros, X 4.x.x uses a config file
> called XF86Config-4, not the older XF86Config used with X 3.x.x. Might you
> be editing the wrong file?)
>
> 4. What changes are you making (or trying to make)? Might you be making a
> change that does not work? And how are you making the changes -- editing
> XF86Config in vi, using xf86config, something else?
>
> 5. Exactly what do you mean by "it go back to the original"? Examples of
> what you *might* mean are:
>
>          A. the changes in XF86Config do not show up in the way X starts.
>          B. after starting X, you open XF86Config again, and the changes
> you made are lost.
>          C. The same as B, plus the XF86Config file has an old timestamp,
> not a recent one.
>
> In cases B and C, if you edit the XF86Config file, save it, close your
> editor, restart your editor, and open XF86Config again (without starting X
> in the meantime), do you see the changes you made?
>
>
> --
> -------------------------------------------"Never tell me the odds!"--------
> Ray Olszewski					-- Han Solo
> Palo Alto, California, USA			  ray@comarre.com
> -------------------------------------------------------------------------------
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

x

[IT Clown]

Hi all

Im new to iptables when i configure iptables X server wont
load i have the following in my iptables file:

*filter
:INPUT DROP [0.0]
:OUTPUT DROP [0.0]
:FROWARD DROP [0.0]

-A OUTPUT -p tcp -dport 0:80 -j ACCEPT


Any idea why x server wont load?

Regards
__________________________________________________________________________
http://www.webmail.co.za/dialup Webmail ISP - Cool Connection, Cool Price

Re: x

[Antony Stone]

On Saturday 27 March 2004 4:15 pm, IT Clown wrote:

> Hi all
>
> Im new to iptables when i configure iptables X server wont
> load i have the following in my iptables file:
>
> :INPUT DROP [0.0]
> :OUTPUT DROP [0.0]
> :FROWARD DROP [0.0]
>
> -A OUTPUT -p tcp -dport 0:80 -j ACCEPT

Please don't retype rules when posting to the list (I can tell from your typos 
that you have).   Copy and paste instead.   If we don't see *exactly* what is 
running on your machine, we can't offer accurate advice.

> Any idea why x server wont load?

Yes.   X needs to talk to itself over the loopback interface lo.

I suspect in fact that nothing which requires a network connection is going to 
work with the above ruleset (typos ignored), since you have no rule allowing 
replies in, for the packets which you do allow out....

I suggest you add some LOGging rules to your setup so that when things don't 
work, you can see what is trying to happen, and being blocked.

For example:

iptables -A OUTPUT -j LOG
iptables -A INPUT -j LOG

These will show you what sort of packets are trying to get out or in, just 
before they get DROPped by your default policy.

In order to solve the problem, I recommend allowing all packets to/from 
interface lo:

iptables -I INPUT -i lo -j ACCEPT
iptables -I OUTPUT -o lo -j ACCEPT

Regards,

Antony.

-- 
There are two possible outcomes:

 If the result confirms the hypothesis, then you've made a measurement.
 If the result is contrary to the hypothesis, then you've made a discovery.

 - Enrico Fermi

                                                     Please reply to the list;
                                                           please don't CC me.

x

[engage]

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list