Re: trouble getting x11 xdm to work

2008-11-12 Thread Lowell Gilbert
Fbsd1 [EMAIL PROTECTED] writes:

 My /etc/ttys looks like this

  ttyv6   /usr/libexec/getty Pc cons25  on  secure
  ttyv7   /usr/libexec/getty Pc cons25  on  secure
  #ttyv8  /usr/local/bin/xdm -nodaemon  xterm   off secure
  #ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on  secure

 The init: getty repeating too quickly on port /dev/ttyv8 msg has stopped.

Right.  Because you're no longer trying to run a getty on that port.

 When I start xdm from root command line nothing happens. NO error log
 msgs, nothing. 

Does it return to the command prompt?  Respond with xdm: not found?
Just hang there?  What *does* it do?

F1 thru F12 just issue the freebsd console logon
 prompt.

Really?  The standard /etc/ttys file doesn't include  entries for
ttyv9-ttyv12.  That means F9-F12 shouldn't let you change to them.  Are
you sure that you can really change to them, or is it possible that
you're still looking at ttyv7 without knowing it?

 My understanding is when /etc/ttys contains this statement

 ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on  secure

 followed by a kill -HUP 1 command to reread tyys file the following
 should happen.

 F1 thru F8 virtual consoles work as normal (ie: freebsd console logon
 prompt). F9 thru F12 virtual consoles will show the xdm logon screen.

No.  F1 through F7 virtual consoles will be regular consoles, and F8
will be the xdm login screen.

 To make xdm the system default logon method have to add
 xdm_enable=YES to /etc/rc.conf and reboot. Then only the xdm logon
 screen will be seen on all virtual consoles F1 thru F12. A
 ctrl+alt+backspace key sequence is the only way to force a return to
 the freebsd console logon prompt for the Fx virtual console being
 used.

No.  Not unless you've written your own script to handle the xdm_enable
variable, which doesn't seem to exist anywhere else in the system.
Unless you've written the script for it as well, I wouldn't expect it to
work.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Mel
On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:


  Still getting error msg
  init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second


You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is 
hammering at it.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Lowell Gilbert
Fbsd1 [EMAIL PROTECTED] writes:

 Mel wrote:
 On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:


 Still getting error msg
 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second


 You first need to get rid of that. xdm can't open /dev/ttyv8 while
 getty is hammering at it.

 I turned that off all ready before running xdm from root command line.

Since you're still getting that error message, you obviously didn't
succeed at turning off the getty.  If you're not getting that message
any more, what symptoms *do* you see?

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Polytropon
On Tue, 11 Nov 2008 19:48:51 +0800, Fbsd1 [EMAIL PROTECTED] wrote:
 Startx works ok so not xorg problem. Next question is are the xdm 
 configuration files suppose to work as delivered by the port install AS IS?
 As a default config demo?

Ha - xdm configuration files memory flash ahead! :-)

Go check them. They are located in /usr/local/lib/X11/xdm. I have
two modified files:

lrwxr-xr-x  1 root  wheel  23 Mar 18  2008 Xresources@ - 
/etc/X11/xdm/Xresources
lrwxr-xr-x  1 root  wheel  23 Mar 18  2008 xdm-config@ - 
/etc/X11/xdm/xdm-config

(It's in /etc for custom lazyness, but you can make changes to the
files in the original xdm directory if you want.)

But I think you didn't change these files, so everything should still
be the standard settings... so I need to say, this would not
be the source of the problem...

If I just knew how I solved the problem you're describing... I
really had this once, and I think the solution was very simple,
allthough it wasn't obvious, and maybe had nothing to do with X...

After all, the obervation indicate that X isn't started
correctly for xdm, but what surprises me is that X is started
correctly from a regular user's account...

Mysterious...
VEB Mysteron Merkwürdigkeitenwerk Karl-Marx-Stadt... :-)



-- 
Polytropon
From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Fbsd1
Next question is are the xdm 
configuration files suppose to work as delivered by the port install AS IS?

As a default config demo?


Yes. When I said 'range', I did mean range. Not 2 possibilities. Missing 
libraries, tainted environment, typos, tied up resources, tight security 
settings, existing pid file, xdm not being xdm but an aliased command or 
shell script sooner up in the path - that's just from the top of my head.





I installed xorg as a package. Then installed xfce package. Made no 
config changes to xorg or the xdm config files. At this point i suspect 
the port of xorg as not being configured correctly. That the default xdm 
config files have statement error causing xdm not to function.


So the big question is has anybody installed the release 7.1 package 
version of xorg and was able to get xdm to function without any config 
file changes?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Fbsd1

Mel wrote:

On Tuesday 11 November 2008 00:56:29 Fbsd1 wrote:

Polytropon wrote:

On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote:

Also created the .xsessions file in the users home directory.

The file is ~/.xsession, without an s at the end. I assume
that csh is your login shell. Put these in your ~/.xsession:


#!/bin/csh
source ~/.cshrc
exec ~/.xinitrc

This sources your individual user setting from .cshrc and the
executes .xinitrc (trivial, isn't it?) to control how the startuo
of your xsession will go.

Make sure both files (.xinitrc and .xsession) are +x attribute.


Keep getting this console error message hundreds of times

init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second

Hey, I saw this one... but I'm not sure how I solved it. Is your
/etc/hosts and hostname set correctly? I think it was something
like this, something I would never had put in any combination
with X...


By the way, in order to try if xdm is working correctly it can be
started directly by the command xdm anytime.

I had ~/.xsession spelled correctly in the directory. Just typo error in
email. Changed the contents of ~/.xsession as you posted. Still no joy.
/etc/hosts file is correct.

Running release 7.0. When i enter xdm on command line of root nothing
happens. ps ax command shows no xdm running.

Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second


That's why. xdm can't get the display. Set on to off in /etc/ttys for ttyv8, 
kill -HUP 1 and if the message does not stop, reboot the machine. Then start 
by running xdm from the command line (as root) and 
inspect /var/log/Xorg.0.log if no screen comes up.





I all ready did that (run xdm from the command line) getting no 
/var/log/xdm.log. Inspecting Xorg.0.log shows nothing related to xdm.


When issuing the xdm command from root and then doing (ps ax command) I 
do not see xdm listed.


What am i to see happen from running xdm from the root command line?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Mel
On Tuesday 11 November 2008 12:48:51 Fbsd1 wrote:
 Mel wrote:
  On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote:
  Mel wrote:
  On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
  Still getting error msg
  init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
  second
 
  You first need to get rid of that. xdm can't open /dev/ttyv8 while
  getty is hammering at it.
 
  I turned that off all ready before running xdm from root command line.
 
  What does xdm -debug 1 turn up? You said nothing related to xdm
  in /var/log/Xorg.0.log, but it would still be helpful to see the last
  lines of the file, so we know why X quit. And since Xorg.0.log isn't
  timestamped, check if the last modification time of the file corresponds
  with the last time you ran the command. This will determine if xdm
  actually gets to the stage of starting the X server or gives up sooner.
  You may also want to set the -error option (see man xdm) and check if
  anything useful is written there.
  With current information, the possible causes range from errors in a
  configuration file xdm reads on start up to X display problems.

 Startx works ok so not xorg problem.

And you know this why? This may come as a surprise, but startx does different 
things then xdm. Even having a DISPLAY environment variable set to a 
non-existing resource, would stop X from starting.

 Next question is are the xdm 
 configuration files suppose to work as delivered by the port install AS IS?
 As a default config demo?

Yes. When I said 'range', I did mean range. Not 2 possibilities. Missing 
libraries, tainted environment, typos, tied up resources, tight security 
settings, existing pid file, xdm not being xdm but an aliased command or 
shell script sooner up in the path - that's just from the top of my head.


-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Fbsd1

Mel wrote:

On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote:

Mel wrote:

On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:

Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
second

You first need to get rid of that. xdm can't open /dev/ttyv8 while getty
is hammering at it.

I turned that off all ready before running xdm from root command line.


What does xdm -debug 1 turn up? You said nothing related to xdm 
in /var/log/Xorg.0.log, but it would still be helpful to see the last lines 
of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, 
check if the last modification time of the file corresponds with the last 
time you ran the command. This will determine if xdm actually gets to the 
stage of starting the X server or gives up sooner.
You may also want to set the -error option (see man xdm) and check if anything 
useful is written there.
With current information, the possible causes range from errors in a 
configuration file xdm reads on start up to X display problems.




Startx works ok so not xorg problem. Next question is are the xdm 
configuration files suppose to work as delivered by the port install AS IS?

As a default config demo?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Mel
On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote:
 Mel wrote:
  On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:
  Still getting error msg
  init: getty repeating too quickly on port /dev/ttyv8, sleeping 30
  second
 
  You first need to get rid of that. xdm can't open /dev/ttyv8 while getty
  is hammering at it.

 I turned that off all ready before running xdm from root command line.

What does xdm -debug 1 turn up? You said nothing related to xdm 
in /var/log/Xorg.0.log, but it would still be helpful to see the last lines 
of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, 
check if the last modification time of the file corresponds with the last 
time you ran the command. This will determine if xdm actually gets to the 
stage of starting the X server or gives up sooner.
You may also want to set the -error option (see man xdm) and check if anything 
useful is written there.
With current information, the possible causes range from errors in a 
configuration file xdm reads on start up to X display problems.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Fbsd1

Mel wrote:

On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote:



Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second



You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is 
hammering at it.



I turned that off all ready before running xdm from root command line.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-11 Thread Karsten Rothemund
On Tue, Nov 11, 2008 at 11:01:44AM -0500, Lowell Gilbert wrote:
 Fbsd1 [EMAIL PROTECTED] writes:
 
Hello,

sorry, but I didn't follow the whole thread.

  Mel wrote:
  You first need to get rid of that. xdm can't open /dev/ttyv8 while
  getty is hammering at it.
 
  I turned that off all ready before running xdm from root command line.
 

in /etc/ttys I think, right? By default (in my /etc/ttys) on ttyv8 there
is an xdm-Daemon configured I think:

ttyv6   /usr/libexec/getty Pc cons25  on  secure
ttyv7   /usr/libexec/getty Pc cons25  on  secure
#ttyv8  /usr/local/bin/xdm -nodaemon  xterm   off secure
ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on  secure

(I changed it to on because I want to start xdm at boot). 


 Since you're still getting that error message, you obviously didn't
 succeed at turning off the getty.  If you're not getting that message
 any more, what symptoms *do* you see?
 
Is there a getty (or something else) configured in your /etc/ttys?

Ciao,

Karsten

-- 

Karsten Rothemund [EMAIL PROTECTED] /\
PGP-Key: 0x7019CAA5   \ /
Fingerprint: E752 C759 B9B2 2057 E42F  \  ASCII Ribbon Campaign
 50EE 47AC A7CE 7019 CAA5 / \ Against HTML Mail and News


pgpTRsGz9L0Ds.pgp
Description: PGP signature


Re: trouble getting x11 xdm to work

2008-11-11 Thread Fbsd1


My /etc/ttys looks like this

 ttyv6   /usr/libexec/getty Pc cons25  on  secure
 ttyv7   /usr/libexec/getty Pc cons25  on  secure
 #ttyv8  /usr/local/bin/xdm -nodaemon  xterm   off secure
 #ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on  secure

The init: getty repeating too quickly on port /dev/ttyv8 msg has stopped.

When I start xdm from root command line nothing happens. NO error log 
msgs, nothing. F1 thru F12 just issue the freebsd console logon prompt.



My understanding is when /etc/ttys contains this statement

ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on  secure

followed by a kill -HUP 1 command to reread tyys file the following 
should happen.


F1 thru F8 virtual consoles work as normal (ie: freebsd console logon 
prompt). F9 thru F12 virtual consoles will show the xdm logon screen.


To make xdm the system default logon method have to add xdm_enable=YES 
to /etc/rc.conf and reboot. Then only the xdm logon screen will be seen 
on all virtual consoles F1 thru F12. A ctrl+alt+backspace key sequence 
is the only way to force a return to the freebsd console logon prompt 
for the Fx virtual console being used.


Is this the correct interpretation of how xdm is designed to function??

I can not find in man xdm or xorg website or handbook an explanation of 
how it's suppose work.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


trouble getting x11 xdm to work

2008-11-10 Thread Fbsd1
logging in at command line works and startx works. Now want to use x11 
xdm to control logins for virtual terminals 9+


Followed handbook instructions 5.6.2 Using XDM doing this
ttyv8   /usr/local/bin/xdm -nodaemon  xterm   on secure

Then kill -HUP 1 to reread the file.

Also created the .xsessions file in the users home directory.

Keep getting this console error message hundreds of times

init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-10 Thread Polytropon
On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote:
 Also created the .xsessions file in the users home directory.

The file is ~/.xsession, without an s at the end. I assume
that csh is your login shell. Put these in your ~/.xsession:


#!/bin/csh
source ~/.cshrc
exec ~/.xinitrc

This sources your individual user setting from .cshrc and the
executes .xinitrc (trivial, isn't it?) to control how the startuo
of your xsession will go.

Make sure both files (.xinitrc and .xsession) are +x attribute.


 Keep getting this console error message hundreds of times
 
 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second

Hey, I saw this one... but I'm not sure how I solved it. Is your
/etc/hosts and hostname set correctly? I think it was something
like this, something I would never had put in any combination
with X...


By the way, in order to try if xdm is working correctly it can be
started directly by the command xdm anytime.



-- 
Polytropon
From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-10 Thread Fbsd1

Polytropon wrote:

On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote:

Also created the .xsessions file in the users home directory.


The file is ~/.xsession, without an s at the end. I assume
that csh is your login shell. Put these in your ~/.xsession:


#!/bin/csh
source ~/.cshrc
exec ~/.xinitrc

This sources your individual user setting from .cshrc and the
executes .xinitrc (trivial, isn't it?) to control how the startuo
of your xsession will go.

Make sure both files (.xinitrc and .xsession) are +x attribute.



Keep getting this console error message hundreds of times

init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second


Hey, I saw this one... but I'm not sure how I solved it. Is your
/etc/hosts and hostname set correctly? I think it was something
like this, something I would never had put in any combination
with X...


By the way, in order to try if xdm is working correctly it can be
started directly by the command xdm anytime.






I had ~/.xsession spelled correctly in the directory. Just typo error in 
email. Changed the contents of ~/.xsession as you posted. Still no joy.

/etc/hosts file is correct.

Running release 7.0. When i enter xdm on command line of root nothing 
happens. ps ax command shows no xdm running.


Still getting error msg
init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: trouble getting x11 xdm to work

2008-11-10 Thread Mel
On Tuesday 11 November 2008 00:56:29 Fbsd1 wrote:
 Polytropon wrote:
  On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote:
  Also created the .xsessions file in the users home directory.
 
  The file is ~/.xsession, without an s at the end. I assume
  that csh is your login shell. Put these in your ~/.xsession:
 
 
  #!/bin/csh
  source ~/.cshrc
  exec ~/.xinitrc
 
  This sources your individual user setting from .cshrc and the
  executes .xinitrc (trivial, isn't it?) to control how the startuo
  of your xsession will go.
 
  Make sure both files (.xinitrc and .xsession) are +x attribute.
 
  Keep getting this console error message hundreds of times
 
  init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second
 
  Hey, I saw this one... but I'm not sure how I solved it. Is your
  /etc/hosts and hostname set correctly? I think it was something
  like this, something I would never had put in any combination
  with X...
 
 
  By the way, in order to try if xdm is working correctly it can be
  started directly by the command xdm anytime.

 I had ~/.xsession spelled correctly in the directory. Just typo error in
 email. Changed the contents of ~/.xsession as you posted. Still no joy.
 /etc/hosts file is correct.

 Running release 7.0. When i enter xdm on command line of root nothing
 happens. ps ax command shows no xdm running.

 Still getting error msg
 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second

That's why. xdm can't get the display. Set on to off in /etc/ttys for ttyv8, 
kill -HUP 1 and if the message does not stop, reboot the machine. Then start 
by running xdm from the command line (as root) and 
inspect /var/log/Xorg.0.log if no screen comes up.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]