Re: XDM cannot start desktop after Xorg upgrade
2013-06-09 07:46, Leslie Jensen skrev: 2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I've disabled XDM for now starting X manually. When I exit X I see this on the console: Thanks /Leslie onStopListening called for active ServerSocket... (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej (xfce4-session:2440): GLib-WARNING **: GError set over the top of a previous GEr ror or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Failed to connect to socket /var/run/dbus/sys tem_bus_socket: Filen eller katalogen finns ej xfce4-session: Querying suspend failed: Failed to connect to socket /var/run/dbu s/system_bus_socket: Filen eller katalogen finns ej xinit: connection to X server lost waiting for X server to shut down xfsettingsd: Fatal IO error 35 (Resursen är t illfälligt otillgänglig) on X server :0.0. .failed to unset mtrr: No such file or directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
XDM cannot start desktop after Xorg upgrade
I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. What happens is that after I've given my password and hit enter, the screen goes black and after a while it returns to the XDM log in dialogue. I've attached the users .xsession-errors and the system xdm.log Disabling XDM and starting X manually works. Of and on logging in via XDM works but there's no pattern to when it does and does not. Thanks /Leslie xdm info (pid 2391): Starting xdm info (pid 2391): Starting X server on :0 X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.1-RELEASE amd64 Current Operating System: FreeBSD bljbsd01.no-ip.org 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 29 January 2013 05:30:35PM Current version of pixman: 0.28.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Jun 8 11:50:02 2013 (==) Using config file: /etc/X11/xorg.conf failed to set mtrr: Invalid argument The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2408): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2396): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2438): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2424): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/GiveConsole xdm info (pid 2468): executing session /usr/local/lib/X11/xdm/Xsession xdm info (pid 2454): sourcing /usr/local/lib/X11/xdm/TakeConsole xdm info (pid 2391): Starting X server on :0 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xdm info (pid 2484): sourcing /usr/local/lib/X11/xdm/Xsetup_0 must specify a background color .xsession-errors Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM cannot start desktop after Xorg upgrade
On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: XDM cannot start desktop after Xorg upgrade
2013-06-08 17:28, Polytropon skrev: On Sat, 08 Jun 2013 12:20:56 +0200, Leslie Jensen wrote: I've been using XDM as login manager for years. Since the latest Xorg upgrade, XDM cannot start XFCE4 as it used to. Strange that this happens after an upgrade. What initalization mechanism do you use for your X session? Do you use the chained approach, i. e., ~/.xsession containing #!/bin/csh source ~/.cshrc exec ~/.xinitrc and all your session startup stuff in ~/xinitrc? (I'm using this approach for many years with XDM successfully.) Disabling XDM and starting X manually works. In this case, ~/.xinitrc will be processed. XDM does use ~/.xsession instead (same content can be used). This seems to indicate that the upgrade did not affect the programs called. I've done like this lrwxr-xr-x 1 user user 9 31 Dec 17:53 .xinitrc@ - .xsession These are the contents of .xsession # LANG=sv_SE.ISO8859-1; export LANG /usr/local/bin/startxfce4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
remote connections to xdm
Hello, I set up xdm on a server (FreeBSD 9)and I can connect to it from any machine on the same local network as the server, but not from computers on different network, for example networks connected via a tunnel. Is there something to be added in /etc/hosts.allow or in the xdm config files to allow connections from specific IP subnets? Thank you in advance. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm and gdm
i run xdm normally. after logging it runs my $HOME/.xsession that starts things like fvwm2 i wanted to run gnome-session once, changed fvwm2 to /usr/local/bin/gnome-sessions after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. with gdm loading gnome works. any ideas? (except: just use gdm please) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm and gdm
On Sat, 21 Jul 2012 19:19:15 +0200 (CEST), Wojciech Puchar wrote: i run xdm normally. after logging it runs my $HOME/.xsession that starts things like fvwm2 i wanted to run gnome-session once, changed fvwm2 to /usr/local/bin/gnome-sessions ^ Is this a typo? According to the Handbook, /usr/local/bin/gnome-session (without trailing 's') should be executed. Source: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html See 6.7.1.2: Installing GNOME. after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). with gdm loading gnome works. Do you have gdm_enable=YES gnome_enable=YES in /etc/rc.conf, and /proc mounted, as suggested in the Handbook? Maybe gdm has some preparations that aren't found by gnome-session when started autonomously. But the Handbook says it works without GDM, so it should work either per .xinitrc (startx command) _and_ also with xdm (and therefore with wdm and others). any ideas? (except: just use gdm please) Just use... computer. :-) -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm and gdm
Is this a typo? According to the Handbook, /usr/local/bin/gnome-session (without trailing 's') should be executed. indeed a typo. thank you. after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). there are imho nowhere. Do you have gdm_enable=YES gnome_enable=YES in /etc/rc.conf, and /proc mounted, as suggested in the Handbook? Maybe gdm has some preparations that aren't found by gnome-session when started autonomously. But the Handbook says it works without gdm is fine and works. the problem is that i wasn't able to my non-gnome .xsession work properly with gdm at all. at the same time i like xdm and want to use, RARELY use it to run gnome. Do you have any data about preparations that gdm do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm and gdm
On Sat, 21 Jul 2012 20:40:44 +0200 (CEST), Wojciech Puchar wrote: after loggin in it just exits. no .xsession-errors is created. no idea where to seek error messages at all. Maybe errors are reported to the 1st virtual terminal where the XDM process outputs its messages to (currently not running xdm, so I can't check). there are imho nowhere. When I do startx, the vitrual terminal from which I issue this command will capture the messages related to X. In case of xdm, I did assume that would be ttyv0 implicitely. Do you have any data about preparations that gdm do? The Handbook mentions /proc to be mounted, but that's not related. The settings gdm_enable=YES gnome_enable=YES in /etc/rc.conf would (if I understand the mechanism correctly) correspond to scripts /usr/local/etc/rc.d/gdm /usr/local/etc/rc.d/gnome respectively. So any possibly relevant preparations should be done by those scripts. I can't check those as I haven't got Gnome installed here. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
SOLVED: xdm and gdm
adding DisplayManager*authName:MIT-MAGIC-COOKIE-1 solves the problem. Do you have any data about preparations that gdm do? The Handbook mentions /proc to be mounted, but that's not related. The settings gdm_enable=YES gnome_enable=YES in /etc/rc.conf would (if I understand the mechanism correctly) correspond to scripts /usr/local/etc/rc.d/gdm /usr/local/etc/rc.d/gnome respectively. So any possibly relevant preparations should be done by those scripts. I can't check those as I haven't got Gnome installed here. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
I am using slim to login which can choose Window Manager by pressing F1 key. Can XDM choose Window Manager when loginning ? Reagrds! - e^(π.i) + 1 = 0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/Understanding-XDM-tp5721476p5724072.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote: I am using slim to login which can choose Window Manager by pressing F1 key. Can XDM choose Window Manager when loginning ? No, xdm cannot do this. But as far as I remember, wdm can -- it has some look feel of the original CDE display manager and it designed to work well with WindowMaker, but it's a very nice replacement for xdm if you need that specific functionality. It's quite lightweight (compared to gdm or kdm) and easily configurable. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
2012/7/4 Polytropon free...@edvax.de: On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote: I am using slim to login which can choose Window Manager by pressing F1 key. Can XDM choose Window Manager when loginning ? No, xdm cannot do this. But as far as I remember, wdm can -- it has some look feel of the original CDE display manager and it designed to work well with WindowMaker, but it's a very nice replacement for xdm if you need that specific functionality. It's quite lightweight (compared to gdm or kdm) and easily configurable. xdm is very simple, it just logs you in and runs a shell script. with default settings the shell script just executes your ~/.xinitrc here is an example how to add shutdown button to xdm http://neilt.org/computing/xdmshutdownbutton.php you can use it as an example to hack your own 'change wm' feature, or just use some xdm replacement that has that. Cheers, Łukasz Gruner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
On Wed, 4 Jul 2012 10:40:05 +0200, uki wrote: 2012/7/4 Polytropon free...@edvax.de: On Tue, 3 Jul 2012 23:27:21 -0700 (PDT), sw2wolf wrote: I am using slim to login which can choose Window Manager by pressing F1 key. Can XDM choose Window Manager when loginning ? No, xdm cannot do this. But as far as I remember, wdm can -- it has some look feel of the original CDE display manager and it designed to work well with WindowMaker, but it's a very nice replacement for xdm if you need that specific functionality. It's quite lightweight (compared to gdm or kdm) and easily configurable. xdm is very simple, it just logs you in and runs a shell script. with default settings the shell script just executes your ~/.xinitrc I always thouzght startx (so xinit) executes ~/.xinitrc, and xdm executes ~/.xession. In fact, I have a cascade for this, so I can use whatever I want. This is .xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc It does simply obtain the settings for the dialog shell (in this case, the C shell, the system's default dialog shell) and continues executing as .xinitrc, just as if it had been called vial startx (so xinit command). And .xinitrc contains the usual stuff, ending in calling the window manager desired: #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc # ... other stuff ... xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms exec wmaker This of course does not taking into account _changing_ the window manager while logging in! here is an example how to add shutdown button to xdm http://neilt.org/computing/xdmshutdownbutton.php you can use it as an example to hack your own 'change wm' feature, or just use some xdm replacement that has that. Interesting extension, thanks! -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
and xdm executes ~/.xession. In fact, I have a cascade xdm file specified in xdm-config default file Xsession try running ~/.xsession otherwise run other defaults. nothing is hardwired. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
On Sun, 24 Jun 2012 22:19:54 +0200 Christian Graulund cutu...@gmail.com wrote: snip The others have answered your questions concerning DM v. WM, but if you are finding XDM annoying to configure, you may possible wish to take a look at slim, x11/slim. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Understanding XDM
Hello Guys, I just install FreeBSD 9, and after compiling Xorg, I started trying to figure out how to install a Window Manager. When Following the handbook, I suggest installing XDM. I want to use something like Openbox, as my window manager, and I can't figure out if Openbox is a replacement for XDM, or something on top of XDM. I now there are alternative to XDM directly like LightDM ect., but the same questions applies to them. So what is the function of XDM (or alternatives), and is it necessary to have to run a WM, or DE for that sake? Thanks Christian G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
On Sun, 24 Jun 2012 22:19:54 +0200, Christian Graulund wrote: Hello Guys, I just install FreeBSD 9, and after compiling Xorg, I started trying to figure out how to install a Window Manager. When Following the handbook, I suggest installing XDM. I want to use something like Openbox, as my window manager, and I can't figure out if Openbox is a replacement for XDM, or something on top of XDM. Not quite. XDM is the X display manager, a GUI replacement for the login mechanism. It initiates the X session for the user and loads his startup file, which calls the desired window manager. I now there are alternative to XDM directly like LightDM ect., but the same questions applies to them. Yes, there are other X display managers like KDM, GDM or WDM. They are designed to work with a specific environment (KDE, Gnome, WindowMaker in this example), but they can be used independently. So what is the function of XDM (or alternatives), and is it necessary to have to run a WM, or DE for that sake? No, it's not neccessary. You can still perform the login the traditional way (text mode console) and then call startx to initiate your X session with the window manager or desktop environment you want. See man xdm for details. Also see your ~/.xinitrc and ~/.xsession files for controlling what to do _after_ successful login, in your example to exec openbox as the last step. Sidenote: I've been using both XDM and WDM with WindowMaker and XFCE (not Xfce -- XFCE means version 3, Xfce means version 4). Works great. I prefer XDM, most secure and easy to use. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Understanding XDM
Christian Graulund writes: I just install FreeBSD 9, and after compiling Xorg, I started trying to figure out how to install a Window Manager. When Following the handbook, I suggest installing XDM. Assuming we're talking about the same xdm ... your first problem is it's not window manager. It's a _display_ manager. The cenonical place to set the window manager seems to be in ~/.xinitrc. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Understanding XDM
On Sun, 24 Jun 2012 22:19:54 +0200, Christian Graulund wrote: Hello Guys, I just install FreeBSD 9, and after compiling Xorg, I started trying to figure out how to install a Window Manager. When Following the handbook, I suggest installing XDM. I want to use something like Openbox, as my window manager, and I can't figure out if Openbox is a replacement for XDM, or something on top of XDM. I now there are alternative to XDM directly like LightDM ect., but the same questions applies to them. So what is the function of XDM (or alternatives), and is it necessary to have to run a WM, or DE for that sake? XDM is not a window manager - it is a display manager. In short it provides a GUI login and then starts your window manager of choice. So if you want a GUI login and a GUI DE, you need both a DM and an WM. I use XDM + Openbox, and it works very well indeed for me. Vastly preferable to some heavyweight like GDM, IMHO. The handbook provides excellent guidance on installing and configuring XDM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, 03 Mar 2011 17:01:10 -0500 John D. Hendrickson and Sara Darnell johnandsa...@cox.net wrote: Hi. I'm a BSD idiot I use [Debian] linux. rc.d question I'm trying to release a project (just below) to the widest possible unix audience. I need a line in /etc/inittab and to have a start/stop in /etc/rc.d, nothing unusual I think. I read many freeBSD rc.d materials and it only convinced me as much as I'd learned: if I'm not running BSD I don't know enough to talk about it :) Usually FreeBSD rc.d scripts are maintained by the port maintainer rather than the upstream project. If you are unclear about it, I would suggest you don't bother. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, 03 Mar 2011 17:01:10 -0500 John D. Hendrickson and Sara Darnell johnandsa...@cox.net wrote: [snip] If anyone would like to quickly comment I'd love to hear why bsd would be a better choice than ubantu (for what audience it is better). Thanks all, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Hi John, same with me as with Chad Perrin. Sadly, I cannot put my issue right and brief at the same time, so please excuse me being verbose. I started with Linux when being in high-school out of frustration of Windows forcing me to do things their way. After switching my entire environment to Suse Linux and after that to a version of RedHat, I quickly found out that I just switched to a different flavour of being forced to do things a certain way. When at university, I tried Gentoo Linux, learned a lot and solved problems my way. Having bought a notebook later on, I decided trying the then very much in vogue Ubuntu with a Xubuntu installation. Although satisfied with the very usable defaults, I was quickly unnerved by not being able to control things. Later, I tried OpenSolaris and FreeBSD and am now using FreeBSD due to the same reasons as Chad Perrin stated: Being a power-user, wanting to control things and (now diverting from Chad's reasons) wanting to use technology (most importantly ZFS) without being impeded for ideological reasons of viral GPLishness. So, same reasons here as with Chad Perrin, safe for an additionally and lately aquired GPL-allergy. @ Chad: Perhaps you might be happier being coerced to use a Linux with a GNU/Linux flavour like Gentoo or ArchLinux. I have never tried the latter, however, with Gentoo you are very much in control. Gentoo effectively forces you to do your own compiling via portage, so be prepared for a very long install. ArchLinux is to my knowledge binary based and might be quicker to install. Both Gentoo and ArchLinux have a reputation to put the user in charge. What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. I was driven over the edge when some network-etc syntax changed without telling me and I lost my network connection as a result. I had something different in mind for the weekend and was just furious - so treat Gentoo with care. Cheers, -- Christopher J. Ruwe TZ GMT + 1 signature.asc Description: PGP signature
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Fri, Mar 04, 2011 at 03:28:10PM +0100, Christopher J. Ruwe wrote: Later, I tried OpenSolaris and FreeBSD and am now using FreeBSD due to the same reasons as Chad Perrin stated: Being a power-user, wanting to control things and (now diverting from Chad's reasons) wanting to use technology (most importantly ZFS) without being impeded for ideological reasons of viral GPLishness. I'd say you diverted from what I satated -- though not from my reasons overall. That is actually among the reasons I prefer FreeBSD, even if I didn't mention it. So, same reasons here as with Chad Perrin, safe for an additionally and lately aquired GPL-allergy. My GPL-allergy has been around since late 2003, but has been growing in strength. 2006 was when it finally got to the point where I stopped using Linux-based systems for my own purposes until some video issues forced me back to it last month. @ Chad: Perhaps you might be happier being coerced to use a Linux with a GNU/Linux flavour like Gentoo or ArchLinux. I have never tried the latter, however, with Gentoo you are very much in control. Gentoo effectively forces you to do your own compiling via portage, so be prepared for a very long install. ArchLinux is to my knowledge binary based and might be quicker to install. Both Gentoo and ArchLinux have a reputation to put the user in charge. I'm considering ArchLinux. I've played with Gentoo in the past (2004ish), and did not much find it to my liking -- mostly because of software stability issues and a community overrun with ricers. What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. I was driven over the edge when some network-etc syntax changed without telling me and I lost my network connection as a result. I had something different in mind for the weekend and was just furious - so treat Gentoo with care. That kind of breakage is among the reasons I didn't like Gentoo. Around that time, Debian was much more stable in practice (even Debian Testing), but things have changed in the Debian world since I last used it for my own purposes five years ago; now, it's prone to breakage as well, evidently. From your description, it sounds like Gentoo wouldn't solve the kinds of problems I'm having with Debian; it would just rearrange the deck chairs on the Titanic. I've heard Arch is a tolerable substitute for FreeBSD when you must use Linux-based systems for some reason. I'm probably going to wipe the system and reinstall this weekend to try to solve my networking issue, and Arch looks like the option I'll try -- though I'll probably check into whether OpenBSD has support for the graphics chipset in this laptop, too (I really doubt it). . . . and then, as soon as the graphics support gets sorted out in FreeBSD, I'll probably wipe again and install FreeBSD. I had FreeBSD installed on it briefly already, and everything about it worked exactly as expected except the graphics, after all. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgptAieZrb8Kp.pgp Description: PGP signature
Re: xdm-options - non-bsd user needs bsd rc.d advice
Readers will surely see more and more people having similar reasons why those who happily use FreeBSD do not want to go back to Linux, or even worse, Windows. I may include myself here, with the special case that I've never been a Windows user, so my mind is clean and healthy and unspoiled of MICROS~1's strange ideas of how things work. :-) On Fri, 4 Mar 2011 15:28:10 +0100, Christopher J. Ruwe c...@cruwe.de wrote: I started with Linux when being in high-school out of frustration of Windows forcing me to do things their way. In my case, it happened in school, simply because of the reason that I needed a versatile typesetting system (text, formulas, graphs) to print to a laser printer. As LaTeX was already available on Linux, I started with Slackware which was a very UNIX-like system (a positive opinion!) at that time. Later on, I did use PTS-Linux (derived from DLD, a german Linux distribution, if I remember correctly), as well as S.u.S.E.-Linux (its formal name at that time). While I found that generic UNIX knowledge was applicable everywhere, Linux knowledge was not, as you could see from file names and locations, procedures, and configuration statements which could not be transferred 1:1 between the systems. When at university, I tried Gentoo Linux, learned a lot and solved problems my way. Having bought a notebook later on, I decided trying the then very much in vogue Ubuntu with a Xubuntu installation. Although satisfied with the very usable defaults, I was quickly unnerved by not being able to control things. University was the time when I found out about FreeBSD. Having generic UNIX knowledge already (Linux, Solaris, IRIX) I could predict (!) where things are on a FreeBSD system, how they act, and what they do. This was my main reason to keep using this system, exlusively as a home desktop since version 4.0, without any disadvantages so far. I doubt that Linux would have delivered the quality I'm looking for: The quality of not being forced to abandon fully functional hardware simply because new defaults tell me I need a plentycore CPU and tenmelonhundred GB of RAM, just to keep doing the same things. As a developer, targetting Linux (as a family of operating systems) is not very easy, as they all do differ in some way. At least there is source code to consult if problems arise, but sometimes you're searching through header files to find out what *foo() is today. :-) What drove me away from Gentoo apart from that GPL-flu was deteriorating quality of system tools. You install what is world in FreeBSD from portage in Gentoo, so when updating your portage, necessary system tools sometimes break. Linux does not differentiate between the system and everything else; even the kernel can be seen as a package on the system. Along with different packaging systems, distributions differ in what packages they use to make their base system (default amount of installation). For developers, FreeBSD is an EXCELLENT operating system as it offers consistency, compatibility and interoperatbility at a good speed ratio (won't run slower after upgrading). The code quality and the availability of good documentation (man pages, handbook, FAQ), even accessible LOCALLY with no Internet connection at hand, makes it a strong partner for DURABLE solutions in software development. A friendly and intelligent community adds to the sum. The sum is SUPERIOR to what I could experience in my career. I know this is a quite general statement and doesn't help the OP in particular, but I thought it would be worth sharing it. I hope it was. :-) -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Fri, Mar 4, 2011 at 9:34 AM, Polytropon free...@edvax.de wrote: While I found that generic UNIX knowledge was applicable everywhere, Linux knowledge was not, as you could see from file names and locations, procedures, and configuration statements which could not be transferred 1:1 between the systems. I find that's true even going between true UNIX systems, like FreeBSD and Solaris. Maybe it was different back in the SunOS days, but modern Solaris has a lot of very Solaris-specific tools that work in opaque ways; for example, you don't edit links to /etc/init.d anymore, you create an XML service description file and use svcadm to manipulate it in some hidden database. There are still BSD-ish tools in Solaris (and GNU tools, too), but Solaris purists will strongly discourage you from using them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm-options - non-bsd user needs bsd rc.d advice
Hi. I'm a BSD idiot I use [Debian] linux. rc.d question I'm trying to release a project (just below) to the widest possible unix audience. I need a line in /etc/inittab and to have a start/stop in /etc/rc.d, nothing unusual I think. I read many freeBSD rc.d materials and it only convinced me as much as I'd learned: if I'm not running BSD I don't know enough to talk about it :) I'm not sure how a real BSD hacker would place a simple start stop. Not where or how, not even after reading the docs. Also I'm not sure the project is good enough to warrant further testing / if the casual user might save time / effort with it. Tell me what you think if you have time! Who doesn't want feedback? http://sourceforge.net/projects/xdm-options/ https://sourceforge.net/projects/xdm-options/ (second has httpS) (xdm sample scripts but complete / round trip. chooser, login, desktop chooser, xdm server: by menu with no hacking required on any unix, saving the casual xdm interested person time in use or setup, is my hope) ... it uses no libs at all If anyone would like to quickly comment I'd love to hear why bsd would be a better choice than ubantu (for what audience it is better). Thanks all, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm-options - non-bsd user needs bsd rc.d advice
On Thu, Mar 03, 2011 at 05:01:10PM -0500, John D. Hendrickson and Sara Darnell wrote: Hi. I'm a BSD idiot I use [Debian] linux. [snip] If anyone would like to quickly comment I'd love to hear why bsd would be a better choice than ubantu (for what audience it is better). FreeBSD is definitely a better choice for *me* than Debian, or (worse yet) Ubuntu. I'm temporarily stuck in a hell of my own making, of sorts, because I installed Debian on a laptop I bought to make up for the fact that I managed to buy a laptop for which FreeBSD does not yet have complete graphics support (Intel HD video). The end result is significant annoyance. Debian, since I used it regularly about half a decade ago, has become increasingly complicated by attempts to guess what users want and provide it. This approach tends to result in making it very difficult to do things differently if you want to. Problems I'm encountering right now mostly center around networking issues -- for some asinine reason, it will connect to my WPA encrypted wireless network at home, but not to an open wireless network at a coffee shop. It makes no reasonable sense. With FreeBSD, it would be a trivial exercise to make it work. Worst-case scenario, I could just change a couple of lines in /etc/rc.d and enter the /etc/rc.d/netif restart command. On Debian, I've tried about half a dozen different approaches to getting it to connect to the coffee shop network, including more than one GUI with a seriously suboptimal interface, with no luck; it just keeps failing to get an IP address. I'm pretty sure there's some kind of automagical DWIMmery going on behind the scenes, trying to guess what I want it to do and doing it without my permission, and getting its guesses *wrong*. The upshot is this: FreeBSD is better for people who like essentially deterministic behavior out of their OSes, where the same input produces the same output, with (little or) no chance of it blowing up in your face or just stubbornly refusing to let you do what you want to do because some developer somewhere set up automagical default management based on what *he* thinks you *really* want to do. Debian to some extent, and Ubuntu to a far greater extent, is for people who don't want to know anything about what the system is doing under the hood, to the extent that if the system doesn't get it right automatically the person will refuse to actually spend any time learning enough about the system to fix the problem. Things are getting positively Microsoftish. In case you couldn't tell, I'm frustrated. I'm beginning to wonder whether having 4:3 resolution stretched out to a 16:9 aspect ratio display might be a lesser evil than using Debian, when it is even more annoying now (relative to FreeBSD) than it was five years ago. tl;dr summary: FreeBSD is power-user friendly. Linux-based systems are getting increasingly dumbed-down user obsequious, to the detriment of people who like being able to customize the system's behavior (or, y'know, actually troubleshoot it at all). -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgp9MT6EerY3q.pgp Description: PGP signature
XDM not showing login screen
Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
doesn't reply to XDMCP requests.
I see the XDMCP packet arriving on my xdm server
harley# tcpdump port 177
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7
All seems to be running ok
harley# ps ax | grep xdm
76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth
/usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg)
76519 ?? Is 0:00.06 xdm: :0 (xdm)
6040 2 S+ 0:00.00 grep xdm
76515 5 I+ 0:00.01 xdm -nodaemon -debug 1
The XDM daemon does not reply with a login screen.
I've commented out the following in my xdm-config file
! DisplayManager.requestPort: 0
following in my Xaccess file
* #any host can get a login window
xdm and X are running, and I see the following in my xdm.log file, even though
I don't get a login screen, the log file indicates incorrect login
SetPrompt(1, NULL, LOGIN_PROMPT_ECHO_OFF(2))
SetPrompt(0, NULL, LOGIN_PROMPT_ECHO_ON(1))
source /usr/local/lib/X11/xdm/Xsetup_0
SetPrompt(0, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
SetPrompt(1, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
pam_msg: PAM_PROMPT_ECHO_ON (2): ' Login:'
SetPrompt(0,Login:, LOGIN_PROMPT_ECHO_ON(1))
RedrawFail('Login incorrect', 0)
dispatching :0
RedrawFail('Login incorrect', 0)
What more can I do to verify why it's not working, and what could be wrong.
Thanks,
Alain
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM not showing login screen
On 31/12/2010 7:07 μ.μ., Alain G. Fabry wrote: Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon doesn't reply to XDMCP requests. I see the XDMCP packet arriving on my xdm server harley# tcpdump port 177 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes 10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7 All seems to be running ok harley# ps ax | grep xdm 76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth /usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg) 76519 ?? Is 0:00.06 xdm: :0 (xdm) 6040 2 S+ 0:00.00 grep xdm 76515 5 I+ 0:00.01 xdm -nodaemon -debug 1 The XDM daemon does not reply with a login screen. I've commented out the following in my xdm-config file ! DisplayManager.requestPort: 0 following in my Xaccess file * #any host can get a login window xdm and X are running, and I see the following in my xdm.log file, even though I don't get a login screen, the log file indicates incorrect login Add a LISTEN line at the end of your Xaccess file, with the specific IP of your server rather then relying on LISTEN * I've had the same when I was setting up my XDMCP lab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM not showing login screen
On Fri, Dec 31, 2010 at 06:07:34PM +0100, Alain G. Fabry wrote:
Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon
doesn't reply to XDMCP requests.
I see the XDMCP packet arriving on my xdm server
harley# tcpdump port 177
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7
All seems to be running ok
harley# ps ax | grep xdm
76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth
/usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg)
76519 ?? Is 0:00.06 xdm: :0 (xdm)
6040 2 S+ 0:00.00 grep xdm
76515 5 I+ 0:00.01 xdm -nodaemon -debug 1
The XDM daemon does not reply with a login screen.
I've commented out the following in my xdm-config file
! DisplayManager.requestPort: 0
following in my Xaccess file
* #any host can get a login window
xdm and X are running, and I see the following in my xdm.log file, even
though I don't get a login screen, the log file indicates incorrect login
SetPrompt(1, NULL, LOGIN_PROMPT_ECHO_OFF(2))
SetPrompt(0, NULL, LOGIN_PROMPT_ECHO_ON(1))
source /usr/local/lib/X11/xdm/Xsetup_0
SetPrompt(0, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
SetPrompt(1, NULL, LOGIN_PROMPT_NOT_SHOWN(0))
pam_msg: PAM_PROMPT_ECHO_ON (2): ' Login:'
SetPrompt(0,Login:, LOGIN_PROMPT_ECHO_ON(1))
RedrawFail('Login incorrect', 0)
dispatching :0
RedrawFail('Login incorrect', 0)
What more can I do to verify why it's not working, and what could be wrong.
Thanks,
Alain
not sure if it helps, I'll just describe my setup.
% grep xdm\ /etc/ttys
ttyv8 /usr/local/bin/xdmxterm off secure
% grep requestPort /usr/local/lib/X11/xdm/xdm-config
!DisplayManager.requestPort:0
% grep -v ^# /usr/local/lib/X11/xdm/Xaccess | uniq -u
aa.bb.cc.dd (these are ip addresses from which
aa.bb.cc.ee I connect to XDM server)
* # any host can get a login window
LISTEN aa.bb.cc.ff (this is the ip address of
the interface on the server
which listens for incoming
connections)
(Obviously using wildcard after specific ip addresses
makes those ip addresses unnecessary, I just
can't decide if I need to let myself access from
anywhere on campus or not).
I connect to the XDM server using
X -query aa.bb.cc.ff
Finally I think x11/xauth must be install on both
sides.
anton
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
Polytropon writes: A small addition: In order to be able to use X with an initialisation file even when not using XDM (i. e. starting X by startx) AND not having to maintain two startup files (.xsession and .xinitrc) AND furthermore incorporating shell settings for the shell of choice (default: the C shell), you can use this approach: Perhaps since I don't run xdm from ttys (having been bit by that in the past), I have for years simply linked one to the other. Works fine, and saves having to remember to update one when the other changes. There are no negatives I know about. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
On Thu, Mar 04, 2010 at 05:57:45PM -0600, Programmer In Training wrote: On 03/04/10 17:43, Warren Block wrote: On Fri, 5 Mar 2010, Polytropon wrote: snip As far as I know, earlier X installations came with the tab window manager - twm. This doesn't seem to be the case anymore. twm is still enabled by default as part of the x11/xorg-apps port. I can confirm that, and I too have problems with XDM despite having 'exec wmaker' in my .xinitrc in my home directory (sometimes XDM will kick me out to the login, sometimes it will just take me to a blank session wherein I can do nothing). I'd like to use XDM and have it start on boot so I'm interested in the outcome of this. If you read the manpage for xdm(1) you will see that the script that is run on login is ~/.xsession Try putting exec wmaker in there. To run xdm from boot, you have to edit /etc/ttys and then: # kill -HUP 1 Look at this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
On 03/05/10 08:46, Frank Shute wrote: snip If you read the manpage for xdm(1) you will see that the script that is run on login is ~/.xsession Try putting exec wmaker in there. To run xdm from boot, you have to edit /etc/ttys and then: # kill -HUP 1 Look at this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html Regards, Thank you kind sir. Now to figure out how to set the ~/.xsession file up automatically upon account creation (not an issue now, but might be later). -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
Re: xorg, xdm, desktop env
On Sat, 06 Mar 2010 00:10:56 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: On 03/05/10 08:46, Frank Shute wrote: snip If you read the manpage for xdm(1) you will see that the script that is run on login is ~/.xsession Try putting exec wmaker in there. To run xdm from boot, you have to edit /etc/ttys and then: # kill -HUP 1 Look at this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html Regards, Thank you kind sir. A small addition: In order to be able to use X with an initialisation file even when not using XDM (i. e. starting X by startx) AND not having to maintain two startup files (.xsession and .xinitrc) AND furthermore incorporating shell settings for the shell of choice (default: the C shell), you can use this approach: ~/.xsession #!/bin/csh source ~/.cshrc exec ~/.xinitrc It incorporates the shell settings and then continues running as .xinitrc - so xdm can pick this up. If you run startx, .xsession isn't used, but .xinitrc is used. So this script contains what you want to automate, e. g. ~/.xinitrc #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc xrandr --fb 1400x1050 xrandr --size 1400x1050 xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms exec wmaker The #!/bin/sh at the beginning isn't needed, according to the documentation. Now to figure out how to set the ~/.xsession file up automatically upon account creation (not an issue now, but might be later). You can use /usr/share/skel for the templates, it will be used by the adduser program. Create dot.xsession in this directory and modify it according to your default settings. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
xorg, xdm, desktop env
Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen, installed xdm. After reboot I see a graphical login window. When entering username and password, it seems to accept it, but immediatly present the graphical login window again. (In console mode (Ctrl-Alt-F1) I can login at the login: prompt with the same username/password). Has FreeSBD somewhere a default environment (in that case why does it not appear after logging in at the XDM graphical window) or do you still need to install a Desktop environment (Gnome, KDE, Xfce) and is it normal that after logging in at the XDM window, you are thrown out again.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
On Thu, 4 Mar 2010 09:30:05 +0100, n dhert ndhert...@gmail.com wrote: Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen, installed xdm. After reboot I see a graphical login window. When entering username and password, it seems to accept it, but immediatly present the graphical login window again. (In console mode (Ctrl-Alt-F1) I can login at the login: prompt with the same username/password). Has FreeSBD somewhere a default environment (in that case why does it not appear after logging in at the XDM graphical window) or do you still need to install a Desktop environment (Gnome, KDE, Xfce) and is it normal that after logging in at the XDM window, you are thrown out again.. As far as I know, earlier X installations came with the tab window manager - twm. This doesn't seem to be the case anymore. Because neither X or FreeBSD itself do include a complete desktop environment (such as KDE, Gnome, Xfce), you need to install it yourself, and then make it available to your user using ~/.xsession or ~/.xinitrc respectively. If those files are not present, a default should be used by X. According to which version of X you have installed, those defaults could launch twm with some xterms (the default is somewhere in /usr/local/lib/X11, ex /usr/X11R6/lib/X11), or just recognize that X program initialisation is missing and then exit - which is still a bit strange, because the X server should run anyway, without programs. Check /var/log/Xorg.0.log for possible errors. What does happen if you don't run xdm, but instead log in with your user account and then run the startx command? -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
On Fri, 5 Mar 2010, Polytropon wrote: On Thu, 4 Mar 2010 09:30:05 +0100, n dhert ndhert...@gmail.com wrote: Installed a fresh FreeBSD-8.0, xorg, configured xorg for my screen, installed xdm. After reboot I see a graphical login window. When entering username and password, it seems to accept it, but immediatly present the graphical login window again. (In console mode (Ctrl-Alt-F1) I can login at the login: prompt with the same username/password). Has FreeSBD somewhere a default environment (in that case why does it not appear after logging in at the XDM graphical window) or do you still need to install a Desktop environment (Gnome, KDE, Xfce) and is it normal that after logging in at the XDM window, you are thrown out again.. As far as I know, earlier X installations came with the tab window manager - twm. This doesn't seem to be the case anymore. twm is still enabled by default as part of the x11/xorg-apps port. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg, xdm, desktop env
On 03/04/10 17:43, Warren Block wrote: On Fri, 5 Mar 2010, Polytropon wrote: snip As far as I know, earlier X installations came with the tab window manager - twm. This doesn't seem to be the case anymore. twm is still enabled by default as part of the x11/xorg-apps port. I can confirm that, and I too have problems with XDM despite having 'exec wmaker' in my .xinitrc in my home directory (sometimes XDM will kick me out to the login, sometimes it will just take me to a blank session wherein I can do nothing). I'd like to use XDM and have it start on boot so I'm interested in the outcome of this. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
Re: Re: xdm and xdmcp
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote: On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote: modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Thanks, this was the correct point. I have added the LISTEN 0.0.0.0 directive in Xaccess file and it works. xdm is perfect for me, I have just tried wdm since I was not able to make xdm work like I wanted. Thanks for the help. Alain Aubord ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm and xdmcp
Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? I have tried almost anything: commenting line about port 0 in xdm-config, modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Any ideas would greatly appreciated, Thanks, -- Alain Aubord ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm and xdmcp
On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote: Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? Yes. I have an entire lab working this way :) I have tried almost anything: commenting line about port 0 in xdm-config, This is needed. modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Same here, I use XDM for login - I don't need anything fancy. About 15 terminals running XFCE through a core2quad machine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm and xdmcp
On Thu, Jan 21, 2010 at 11:30:47PM +0200, Manolis Kiagias wrote: On 21/01/2010 8:54 ??.??., rhin...@postmail.ch wrote: Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? Yes. I have an entire lab working this way :) I have tried almost anything: commenting line about port 0 in xdm-config, This is needed. modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Same here, I use XDM for login - I don't need anything fancy. About 15 terminals running XFCE through a core2quad machine. I'm running xdm on ia64 and connecting from sparc64, both 9.0-current, works fine. I could probably share my xdm config files, if this is useful. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
wdm and xdm problems - related to HAL?
So I got Xorg working with Hal. Wahoo. If I log in from a display manager I encounter some weird stuff. If I am using xdm and I log out of the window manager and then attempt to shut down the computer - by going to tty 0 and typing # halt -p - the disk syncs and then the shutdown freezes. If I am using wdm and I log out of the window manager and want to log back in, it takes my username but does not clear the text field for me to type a password. There is only one regular user on the system. FreeBSD 7.2 release. Blackbox wm. graphics: ATI mobility radeon Xpress 200m, 64MB - 128MB. Display: 1280x800. == Wherever the corpse is, there the vultures will gather. Matthew 24:28 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: wdm and xdm problems - related to HAL?
A little sidenote: On Tue, 10 Nov 2009 14:06:04 -0800 (PST), Neil Short nesh...@yahoo.com wrote: If I am using xdm and I log out of the window manager and then attempt to shut down the computer - by going to tty 0 and typing # halt -p - the disk syncs and then the shutdown freezes. You should use the shutdown command (instead of halt)a to make sure services are stopped correctly. The halt command does not take care of this topic. # shutdown -p now Does the freeze happen if you press the power button (which should initate the mechanism above), too? -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
PAM and xdm woes
Hi, Every time I start xdm I get the following message on ttyv0, xdm: pam_sm_close_session(): no utmp record for :0 Everything seems to work just fine. I can log in, and everything runs as expected, so it's basically just an annoyance, especially since I don't know whether I should be concerned about security. The only things I've changed from the default xdm config are the size and position of the xconsole window xdm launches and the background (instead of the standard vanilla one, I run an xscreensaver hack), and those are changes I've had for about 10 years without any problems. This error message started showing up quite recently. I believe it happened when upgrading to 8.0, but I'm not sure exactly at what point. I've been running 8.0 since BETA1 and I'm now on RC1, and the message, I believe, started appearing some time at or after upgrading from 7.2-RELEASE-p? to 8.0-BETA1. I've run amd64 for about 2 years, but last week I moved back to i386, because I got tired of waiting for a decent 64 bit nVidia driver. The message has been there in the amd64 version and is still there after moving back to i386, so no change there. I've not changed anything in the PAM configuration; I simply don't know how. So, my questions are: 1. Should I be concerned about it? 2. How do I fix it? If you need any more info, please let me know. I'll be happy to post any config files, e.g. xorg.conf or my KERNCONF file (perhaps I've missed something important in the kernel?) Any help appreciated. Sincerely, Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Automated login, X and xdm
Dear list, in order to do something that I haven't done for many years, I'd like to have some suggestions or pointers if I do it right. It's a strange, but still typical idea. :-) Here's the problem: A FreeBSD workstation should run X for a specified user after system startup. If the user logs out, he should not drop to CLI mode; instead, an xdm login should be shown to allow him (or someone else) to log in and use X. In the past, I created the auto-login as follows: First, I create an entry in /etc/gettytab, right after the default: entry; it contains the al= definition for auto-login as explained in man 5 gettytab. The name of the user is USER in this example; in fact, is is a valid username on the system: autologin:\ :al=USER:tc=Pc: Then I change the getty argument from Pc to autologin in /etc/ttys: ttyv0 /usr/libexec/getty autologin cons25l1 on secure This automatically logs in the user USER specified as above. In order to start X when he logs in, I put the following lines in his ~/.login: #!/bin/sh mesg y [ ! -f /tmp/.X0-lock ] startx The user's shell is the C-Shell, so it works. I see the upcoming problem: If a user already started X, then xdm cannot start (as usually done by setting on for xdm in /etc/ttys). My idea would be to do something like this into the user's ~/.login file: #!/bin/sh mesg y # very first start of X at (automatic) login # this line will fail if X is already running, but # start it if not [ ! -f /tmp/.X0-lock ] startx # after leaving X, xdm should be started, but not if # it's already running [ ! -f /tmp/.X0-lock ] sudo xdm # after xdm is started, dialog mode is back, so the # last entry quits any session after exiting from X logout Normally, there would be the following setting to only run xdm, without autologin, in /etc/ttys: ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure But this interferes with the autologin, right? What is the usual way to go? Is there something more elegant? How about exec startx? Thanks for your ideas and time! -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
xdm freezes - 7.2-RELEASE installed
Just installed 7.2-RELEASE. After changing my /etc/ttys to default to xdm and rebooting, my machine opens xdm, but I cannot type or press enter. My keyboard isn't totally unresponsive, however, because I can Ctrl+Alt+F# to another virtual terminal. Any ideas? Thanks, Daniel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
Hi, Daniel Underwood wrote: Just installed 7.2-RELEASE. After changing my /etc/ttys to default to xdm and rebooting, my machine opens xdm, but I cannot type or press enter. My keyboard isn't totally unresponsive, however, because I can Ctrl+Alt+F# to another virtual terminal. Try adding: Option AllowEmptyInput off .. to the ServerLayout section of your xorg.conf, see if that helps. See man xorg.conf too. -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
I don't have an xorg.conf file. When I installed 7.1-RELEASE on this laptop (exact same machine) I didn't need to configure an xorg.conf file. But I'll certainly try your advice. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 2:23 PM, Daniel Underwood djuatde...@gmail.comwrote: Just installed 7.2-RELEASE. After changing my /etc/ttys to default to xdm and rebooting, my machine opens xdm, but I cannot type or press enter. My keyboard isn't totally unresponsive, however, because I can Ctrl+Alt+F# to another virtual terminal. Any ideas? Thanks, Daniel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Could you use your mouse in xdm? I don't know if this is related; but I couldn't get my mouse to work in KDE or XFCE4 until I turned on hal. I added the following to /etc/rc.conf and rebooted: dbus_enable=YES hald_enable=YES Best of luck, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood djuatde...@gmail.comwrote: Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 me too ;-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
Andrew Gould wrote: On Tue, May 5, 2009 at 3:17 PM, Daniel Underwood djuatde...@gmail.comwrote: Yep, that was it! I should have read the Handbook more thoroughly: http://www.freebsd.org/doc/en/books/handbook/x-config.html#AEN6615 me too ;-) Taking this opportunity, allow me to remind to everyone that the Handbook is always work in progress and it is always useful to check again sections that you have already read, as new info is added regularly. This latest addition to the Handbook was in fact inspired by questions and info appearing on this same list :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Wed, 06 May 2009 00:01:47 +0300, Manolis Kiagias son...@otenet.gr wrote: Taking this opportunity, allow me to remind to everyone that the Handbook is always work in progress and it is always useful to check again sections that you have already read, as new info is added regularly. This latest addition to the Handbook was in fact inspired by questions and info appearing on this same list :) A very polite addition of mine: It's always wise to study /usr/ports/UPDATING, a file that explains the reasons when your system suddenly went nuts. :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood djuatde...@gmail.comwrote: I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. It's almost as good as.(wait for it).. and always back up your data. (That one never gets old!) :-) Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
Absolutely! (Sent from my iPhone) On May 5, 2009, at 7:45 PM, Andrew Gould andrewlylego...@gmail.com wrote: On Tue, May 5, 2009 at 6:32 PM, Daniel Underwood djuatde...@gmail.com wrote: I thought /usr/ports/UPDATING is only created when you appraise your ports with a view toward updating. I.e, after a fresh install of 7.2 (not an upgrade from 7.1), I didn't think the UPDATING file would be very helpful. It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. It's almost as good as.(wait for it).. and always back up your data. (That one never gets old!) :-) Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould andrewlylego...@gmail.com wrote: It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. At least according to the history of problems with X that appeared on this list, /usr/ports/UPDATING hasn't received the attention it should. Things like the empty inputs and the crazy DBUS HAL stuff has been mentioned there. I didn't update my X yet, so I will have all this trouble in the future. :-) It's almost as good as.(wait for it).. and always back up your data. Customer: I've just done a new Word document, saved it, then accidentally deleted it. Is there anything you can do to get it back? Tech Support: Sorry, no, the backup isn't run until night time. Customer: Ohh, can we restore it tomorrow, then? :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm freezes - 7.2-RELEASE installed
On Tue, May 5, 2009 at 7:21 PM, Polytropon free...@edvax.de wrote: On Tue, 5 May 2009 18:45:02 -0500, Andrew Gould andrewlylego...@gmail.com wrote: It's good, general advice. There are UPDATING files in various places for various updates, I think, including /usr/src/. At least according to the history of problems with X that appeared on this list, /usr/ports/UPDATING hasn't received the attention it should. Things like the empty inputs and the crazy DBUS HAL stuff has been mentioned there. I didn't update my X yet, so I will have all this trouble in the future. :-) It's almost as good as.(wait for it).. and always back up your data. Customer: I've just done a new Word document, saved it, then accidentally deleted it. Is there anything you can do to get it back? Tech Support: Sorry, no, the backup isn't run until night time. Customer: Ohh, can we restore it tomorrow, then? I'm not sure whether to laugh or cry over this one. ;-) :-) -- 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 freebsd-questions-unsubscr...@freebsd.org
Re: xdm -debug 1 = Nothing left to do, exiting
On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote: On 6.4-stable alpha I cannot get xdm to become a daemon, it exits immediately with empty /var/log/xdm.log. I tried to use -debug option, and this is the output: # xdm -debug 1 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/local/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/local/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/local/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/urandom DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/local/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/local/ lib/X11/xdm/Xwilling Nothing left to do, exiting # Looking at xdm -debug .. logs on the net it seems the next line after the Willing should be creating socket 177 Perhaps xdm exits because it cannot create socket 177? Is that plausible? How can I test this? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED: Re: xdm -debug 1 = Nothing left to do, exiting
On Tue, Feb 17, 2009 at 04:30:49PM +, Anton Shterenlikht wrote: On Fri, Feb 13, 2009 at 10:13:08AM +, Anton Shterenlikht wrote: On 6.4-stable alpha I cannot get xdm to become a daemon, it exits immediately with empty /var/log/xdm.log. I tried to use -debug option, and this is the output: # xdm -debug 1 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/local/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/local/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/local/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/urandom DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/local/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/local/ lib/X11/xdm/Xwilling Nothing left to do, exiting # Looking at xdm -debug .. logs on the net it seems the next line after the Willing should be creating socket 177 Perhaps xdm exits because it cannot create socket 177? Is that plausible? How can I test this? I think the xdm-config file got overwritten during the port upgrade with the default (secure?) settings. I had to comment out the last setting in xdm-config % tail -3 /usr/local/lib/X11/xdm/xdm-config ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 % now seems to be working fine. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SOLVED: Re: xdm -debug 1 = Nothing left to do, exiting
On Tue, 17 Feb 2009, Anton Shterenlikht wrote: I think the xdm-config file got overwritten during the port upgrade with the default (secure?) settings. I had to comment out the last setting in xdm-config % tail -3 /usr/local/lib/X11/xdm/xdm-config ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 % now seems to be working fine. That line is present here, and xdm works. From /etc/ttys and on localhost, anyway, don't have any X terminals. 'xhost +localhost' is in the user .xsession before X startup, but no other changes I can recall. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm -debug 1 = Nothing left to do, exiting
On 6.4-stable alpha I cannot get xdm to become a daemon, it exits immediately with empty /var/log/xdm.log. I tried to use -debug option, and this is the output: # xdm -debug 1 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm.log DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/local/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/local/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/local/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomDevice/DisplayManager.RandomDevice value /dev/urandom DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/local/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/local/ lib/X11/xdm/Xwilling Nothing left to do, exiting # What does this mean? Some misconfiguration? I haven't touched any config files from x 7.3 to 7.4, and I followed the UPDATING. Does ldd shed any light on this problem?: #ldd -av /usr/local/bin/xdm /usr/local/bin/xdm: libXmu.so.6 = /usr/local/lib/libXmu.so.6 (0x160072000) libXt.so.6 = /usr/local/lib/libXt.so.6 (0x1600a4000) libSM.so.6 = /usr/local/lib/libSM.so.6 (0x16012e000) libuuid.so.1 = /usr/local/lib/libuuid.so.1 (0x160148000) libICE.so.6 = /usr/local/lib/libICE.so.6 (0x16016a000) libutil.so.5 = /lib/libutil.so.5 (0x16019e000) libXinerama.so.1 = /usr/local/lib/libXinerama.so.1 (0x1601c) libXext.so.6 = /usr/local/lib/libXext.so.6 (0x1601d4000) libXpm.so.4 = /usr/local/lib/libXpm.so.4 (0x1601fa000) libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) libxcb.so.2 = /usr/local/lib/libxcb.so.2 (0x16036a000) libXau.so.6 = /usr/local/lib/libXau.so.6 (0x16039c000) libpthread-stubs.so.0 = /usr/local/lib/libpthread-stubs.so.0 (0x1603b) libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x1603c2000) libcrypt.so.3 = /lib/libcrypt.so.3 (0x1603d8000) libpam.so.3 = /usr/lib/libpam.so.3 (0x1603ee000) librpcsvc.so.3 = /usr/lib/librpcsvc.so.3 (0x160408000) libc.so.6 = /lib/libc.so.6 (0x160424000) /usr/local/lib/libXmu.so.6: libXt.so.6 = /usr/local/lib/libXt.so.6 (0x1600a4000) libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) libSM.so.6 = /usr/local/lib/libSM.so.6 (0x16012e000) libICE.so.6 = /usr/local/lib/libICE.so.6 (0x16016a000) libXext.so.6 = /usr/local/lib/libXext.so.6 (0x1601d4000) /usr/local/lib/libXt.so.6: libSM.so.6 = /usr/local/lib/libSM.so.6 (0x16012e000) libICE.so.6 = /usr/local/lib/libICE.so.6 (0x16016a000) libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) /usr/local/lib/libSM.so.6: libICE.so.6 = /usr/local/lib/libICE.so.6 (0x16016a000) libuuid.so.1 = /usr/local/lib/libuuid.so.1 (0x160148000) /usr/local/lib/libXinerama.so.1: libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) libXext.so.6 = /usr/local/lib/libXext.so.6 (0x1601d4000) /usr/local/lib/libXext.so.6: libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) libxcb.so.2 = /usr/local/lib/libxcb.so.2 (0x16036a000) libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x1603c2000) libpthread-stubs.so.0 = /usr/local/lib/libpthread-stubs.so.0 (0x1603b) librpcsvc.so.3 = /usr/lib/librpcsvc.so.3 (0x160408000) libXau.so.6 = /usr/local/lib/libXau.so.6 (0x16039c000) /usr/local/lib/libXpm.so.4: libX11.so.6 = /usr/local/lib/libX11.so.6 (0x16022) /usr/local/lib/libX11.so.6: libxcb.so.2 = /usr/local/lib/libxcb.so.2 (0x16036a000) librpcsvc.so.3 = /usr/lib/librpcsvc.so.3 (0x160408000) /usr/local/lib/libxcb.so.2: libXau.so.6 = /usr/local/lib/libXau.so.6 (0x16039c000) libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x1603c2000) libpthread-stubs.so.0 = /usr/local/lib/libpthread-stubs.so.0 (0x1603b) many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
XDM login freezes on boot
AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM login freezes on boot
On Wed, Feb 11, 2009 at 08:32:20PM +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? no, but what I see is that xdm exits immediately. I just cannot get the daemon to run. This is on 6.4-stable alpha with xdm-1.1.8_1 -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM login freezes on boot
On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM login freezes on boot
On Wed, Feb 11, 2009 at 08:49:51PM +1000, Da Rock wrote: On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? I think there is a lack of understanding here of how exactly hal, dbus and xorg are interrelated. There are some pages on freebsd.org, but at least for me these didn't make it any clearer. The man pages aren't helpful either. They tell you how to do things, but there is not much on why. I'd like to have a better idea of 0. how do hal, dbus, xorg-server, xdm and clients interoperate? 1. why do I need hal and dbus? 2. where do I need to run hal and dbus daemons, on the X server side, on the clients side, or on both? In my case these are different systems, I rely on XDMCP). 3. what happens if hal support is not built into xorg-server? 4. why is the issue of auto keyboard and mouse detection still not clear, contrary to the statement in ports/UPDATE? Cleary something changes from 7.3 to 7.4 that gives all sorts of troubles to many people on different systems. If these questions have been answered already please point me to a link. anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM login freezes on boot
On Wed, 11 Feb 2009, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Yes, up until the latest xorg-server update on Sunday (xorg-server-1.5.3_5,1). Now it works great. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XDM login freezes on boot
On Wed, 11 Feb 2009, Da Rock wrote: On Wed, 2009-02-11 at 20:32 +1000, Warren Liddell wrote: AMD64 4gig RAM FreeBSD 7.1 KDE 4.2 I've noticed of late when i have had the misfortune of rebooting this machine due to severre storms and blackouts, when it boots everything loads fine, xdm initates an i get the standard logon screen, however, you cant do anything an the mouse dosent work. To solve this issue i go to console via CTRL + ALT + F1 kill tthe XDM pid an once it comes back up, everything is perfectly fine. Anyone else had this odd occurance ? Sounds like hald is starting after ttys is initiated. There's another thread here mentioning that- never read the answer though. Maybe start hald at the beginning of your rc.conf? Or set a sleep on your tty entry for x? rc.conf just sets variables; it's not order-sensitive. If xorg-server-1.5.3_5,1 along with all the previous patches doesn't fix the problem, then delaying xdm startup might be the way to go. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm doesn't run as daemon
On Fri, Feb 06, 2009 at 09:39:23PM +0100, Roger Olofsson wrote: Anton Shterenlikht skrev: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log # So no xdm daemon. My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1. Any ideas? Hi Anton, Tried detaching it? xdm It terminates straight away # xdm [1] 82938 # [1]Done xdm # with empty /var/log/xdm.log Perhaps I should check which libraries xdm is built with and try to rebuild those? But I think I've done this already. thanks anyway anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm doesn't run as daemon
Anton Shterenlikht skrev: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log # So no xdm daemon. My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1. Any ideas? No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.18/1935 - Release Date: 02/02/09 19:21:00 Hi Anton, Tried detaching it? xdm /R ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm doesn't run as daemon
After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log # So no xdm daemon. My system: FreeBSD 6.4-STABLE alpha, xdm-1.1.8_1. Any ideas? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xdm doesn't run as daemon
Anton Shterenlikht writes: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log Any ideas? 1) May we see /var/log/Xorg.0.log? 2) Does startx work? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xdm doesn't run as daemon
On Thu, Feb 05, 2009 at 08:01:25AM -0500, Robert Huff wrote: Anton Shterenlikht writes: After upgrades of 23-24 Jan 2009 xdm is not working: # xdm # ps ax|grep xdm 75632 p1 S+ 0:00.01 grep xdm # cat /var/log/xdm.log Any ideas? 1) May we see /var/log/Xorg.0.log? 2) Does startx work? This is a headless box, I don't run X server on it. I connect to it via XDMCP and run clients. So I've neither /var/log/Xorg.0.log nor startx on this box. It worked fine until the upgrade. I'm now thoroughtly confused by dbus and hal issues. So in case it matters I run neither hald nor dbus-daemon on this box. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: trouble getting x11 xdm to work
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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]
getting rid of xconsole on xdm
I am in the middle of setting up a new machine and want to get rid of the ^*(*%*@ xconsole on xdm (it doesn't go away on login either)... how? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting rid of xconsole on xdm
On Sat, Nov 24, 2007 at 04:22:48AM -0500, Aryeh Friedman wrote: I am in the middle of setting up a new machine and want to get rid of the ^*(*%*@ xconsole on xdm (it doesn't go away on login either)... how? /usr/local/lib/X11/xdm/Xsetup_0 Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xdm woes
Hi, I recently purchased a new computer (well, purchased the components and put them together). The hardware is ASUS P5B Premium, nVIDIA GeForce 8600 GT, 2-channel JMicron JMB 363 PCIe card, Intel Core2 Quad Q6600, six Samsung HD501LJ CR100-10 HDDs striped using gstripe (used for storage), one Samsung SP1614C SW100-30 HDD used as system disk (/, /usr, /var and /home). I'm running 7.0-BETA3 and Xorg 7.3, with the nv driver that comes with Xorg (nVIDIA's own driver refuses to compile with the message that 7.0 -CURRENT aren't supported. Now for my problem. Everything works like a charm, except for one small annoyance. If I run xdm, everything hangs when I log out. The monitor just turns black and i get no response whatsoever for neither the mouse nor the keyboard. The only thing that works is shutting the computer off (by quickly pushing aqnd releasing the power button, so the OS shuts down using ACPI). This happens every time. No matter what window manager I use. But it only happens when I use xdm. If I start X with startx, it shuts down cleanly and returns to the tty from which I ran startx. The only clue I've been able to find about this is in /var/log/xdm.log (which I'm enclosing). I'd be happy to share my xorg.conf and Xorg.0.log files as well (and any other files that might help solving this too for that matter), but because of their sizes I'll only do that on request. I haven't touched any of the X and xdm resource files excpet xorg.conf. my /var/log/xdm.log looks like this (the last line confuses me): X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-BETA3 i386 Current Operating System: FreeBSD trapper.homedns.org 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Sun Nov 18 02:13:50 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAZLAR i386 Build Date: 20 November 2007 05:09:57PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 20 17:20:57 2007 (==) Using config file: /etc/X11/xorg.conf (II) Module i2c already built-in (II) Module ddc already built-in (II) Module ramdac already built-in The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server stdin:30:1: error: unterminated #if The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Duplicate shape name Using last definition Warning: Multiple doodads named Using first definition Warning: Multiple doodads named Using first definition Warning: Multiple doodads named Using first definition Warning: Multiple doodads named Using first definition Warning: Multiple doodads named Using first definition Warning: Multiple doodads named Using first definition Errors from xkbcomp are not fatal to the X server xdm info (pid 900): Rescanning both config and servers files xdm error (pid 900): Display :0 is being disabled -- Sincerly, Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm woes
pushing aqnd releasing the power button, so the OS shuts down using ACPI). This happens every time. No matter what window manager I use. But it only happens when I use xdm. If I start X with startx, it shuts down cleanly and returns to the tty from which I ran startx. how you start xdm? from ttys or manually? strange - anyway ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm woes
Wojciech Puchar wrote: pushing aqnd releasing the power button, so the OS shuts down using ACPI). This happens every time. No matter what window manager I use. But it only happens when I use xdm. If I start X with startx, it shuts down cleanly and returns to the tty from which I ran startx. how you start xdm? from ttys or manually? strange - anyway I've started it from ttys a few times, but I gave up after a few days. Since then I've tried starting it manually (both with and without the -nodaemon option) every time I've upgraded something related to either the system or X. Last time a few hours ago, just before I wrote my original mail about this, after upgrading xorg-server from 1.4_2,1 to 1.4_3,1. -- Sincerly, Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Thu, Aug 23, 2007 at 12:16:10AM +0400, Boris Samorodov wrote: On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? I've seen something like this after Xorg-6.9 to Xorg-7.1 update. Seems that I succeeded after deletting my old xorg.conf file, creating a new one and fitting it. Yeah, you're right; creating a new one would have been the most logical thing. But at least I learned that the modules have been moved to /usr/local/lib/xorg/modules. I did a wholesale 1,$s/X11R6/local/gp and that failed because the old path was /usr/X11R6/lib/modules. I'll know if this works in the morning localtime. My brain is fried. cheers, gary WBR -- bsam -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xdm fails! can't find pcidata
I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? tia, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Wed, Aug 22, 2007 at 12:11:47PM -0700, Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? tia, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix Could you show us what is your ModulePath set to? (either from xorg.conf or from Xorg.0.log, should be /usr/local/lib/xorg/modules). Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm fails! can't find pcidata
On Wed, 22 Aug 2007 12:11:47 -0700 Gary Kline wrote: I just rebooted my DNS server and now X fails. I'm pretty sure I did everything re the xorg instructions in UPDATING. The error message in /var/lob/Xorg.0.log says exactly:: (II) Loader running on freebsd (II) LoadModule: pcidata (WW) Warning, couldn't open module pcidata (II) UnloadModule: pcidata (EE) Failed to load module pcidata (module does not exist, 0) How can I fix this? I find pcidata deep in the /usr/sys/src.../dev directory. Nothing in my KERNCONF=GENERIC file. Insights, anybody?? I've seen something like this after Xorg-6.9 to Xorg-7.1 update. Seems that I succeeded after deletting my old xorg.conf file, creating a new one and fitting it. WBR -- bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Missing file in 6.2-RELEASE concerning xdm
Hello list, I have written an e-mail on 12. April 2007 in freebsd-questions@freebsd.org and a day later in [EMAIL PROTECTED] concerning a login-problem with a X-Terminal to a FreeBSD-6.2-XDM-Server. The reason for the problem was: the file /usr/X11R6/lib/X11/xdm/Xstartup didn't exist there. I have created an empty Xstartup and now my login-problems are blown away. I swear I didn't deleted this file! It seems that the 6.2-RELEASE don't delivers a Xstartup-file. Could you deliver for the 6.3-RELEASE a Xstartup, please? With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
