Re: X client without X server
You can remove leaf ports using pkg_cutleaves once everything is installed. You can even remove pkg_cutleaves with pkg_cutleaves if you don't want it anymore. On Wed, Jul 3, 2013 at 11:44 PM, Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: Hi, Just my 2¢ worth on this. Sure, one always wants to keep overhead low. But the days of limited RAM, small hard drives, etc...are long since behind us. My concern is when portupgrade -a. The more ports on the system, the more likely the upgrade will fail. So I'd prefer to have as little unused ports as possible. Not to mention that security wise, having unused ports sitting there is not too good. Best regards, Olivier ___ 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 -- Christopher J. Umina ch...@uminac.com 781 354 0535 ___ 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: X client without X server
Hi, Is there a way to install an X client without automatically install an X server? I don't use emacs, but you can quickly check, prior to installing, what other ports will be required, e.g. do make -C /usr/ports/ search name=emacs-24 After doing my homework, it seems that it happened only some years ago. I have some very old systems, that I have been upgrading again and again, without reconstructing from scratch; the old systems are carrying xorg-server along. On the newer machines that I installed, there is only X clients, no X servers. So the problem was only an old problem, I apologize for disturbing. Best regards, Olivier ___ 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: X client without X server
Date: Wed, 3 Jul 2013 10:55:48 +0700 (ICT) From: Olivier Nicole olivier.nic...@cs.ait.ac.th To: freebsd-questions@freebsd.org Subject: X client without X server Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. Is there a way to install xterm and only the libraries that are needed to run xterm? TIA, Olivier I've been doing this for years. What's the problem? Just install xterm, or whatever you need. All the necessary libs will be pulled in, e.g.: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. Anton ___ 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: X client without X server
Anton, On Wed, Jul 3, 2013 at 5:47 PM, Anton Shterenlikht me...@bris.ac.uk wrote: Date: Wed, 3 Jul 2013 10:55:48 +0700 (ICT) From: Olivier Nicole olivier.nic...@cs.ait.ac.th To: freebsd-questions@freebsd.org Subject: X client without X server Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. Is there a way to install xterm and only the libraries that are needed to run xterm? TIA, Olivier I've been doing this for years. What's the problem? Just install xterm, or whatever you need. All the necessary libs will be pulled in, e.g.: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But for some reason, xorg-server gets installed too. And tons of fonts, and ... It could be emacs, or cvsup, these are the 3 X Window clients I install. Best regards, Olivier ___ 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: X client without X server
On Wed, 3 Jul 2013 11:47:16 +0100 (BST), Anton Shterenlikht wrote: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But one of its dependencies might. -- 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: X client without X server
On Wed, Jul 3, 2013 at 6:03 PM, Polytropon free...@edvax.de wrote: On Wed, 3 Jul 2013 11:47:16 +0100 (BST), Anton Shterenlikht wrote: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But one of its dependencies might. That make no sense, xterm may (and certainly does) depend on the same libraries as the X server, but there is no way xterm depends on X server itself. I can manually remove X server and the fonts and xclac... and the system is still running very well (and updating without trying to reinstall X server...) Best regards, Olivier ___ 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: X client without X server
On Wed, 3 Jul 2013 18:07:11 +0700, Olivier Nicole wrote: On Wed, Jul 3, 2013 at 6:03 PM, Polytropon free...@edvax.de wrote: On Wed, 3 Jul 2013 11:47:16 +0100 (BST), Anton Shterenlikht wrote: [...] Obviously xterm does not depend on xorg-server. But one of its dependencies might. That make no sense, xterm may (and certainly does) depend on the same libraries as the X server, but there is no way xterm depends on X server itself. That's what I would imagine too. But who knows what's going on in the strange realm of build dependencies and run dependencies... :-) I can manually remove X server and the fonts and xclac... and the system is still running very well (and updating without trying to reinstall X server...) That should even work without a warning (as the libs for xterm would be kept, and those required by the X server _only_ could safely be removed). In case such a procedure is needed more often, a local patch could be added to the respective port that would remove the unneeded parts in the post-install phase. -- 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: X client without X server
From olivier2...@gmail.com Wed Jul 3 13:09:25 2013 Anton, On Wed, Jul 3, 2013 at 5:47 PM, Anton Shterenlikht me...@bris.ac.uk wrote: Date: Wed, 3 Jul 2013 10:55:48 +0700 (ICT) From: Olivier Nicole olivier.nic...@cs.ait.ac.th To: freebsd-questions@freebsd.org Subject: X client without X server Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. Is there a way to install xterm and only the libraries that are needed to run xterm? TIA, Olivier I've been doing this for years. What's the problem? Just install xterm, or whatever you need. All the necessary libs will be pulled in, e.g.: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But for some reason, xorg-server gets installed too. And tons of fonts, and ... It could be emacs, or cvsup, these are the 3 X Window clients I install. I don't use emacs, but you can quickly check, prior to installing, what other ports will be required, e.g. do make -C /usr/ports/ search name=emacs-24 You might be familiar with this already, but if not, the B-deps are those ports which are required to build your port, and R-deps are required to run your port. For emacs-24, both the default and the devel branches, you see that they depend on xorg-fonts-truetype-7.7_1 and lots of other libs, but not on xorg-server. net/cvsup has a lot fewer dependencies, again no xorg-server. In general X server is only required by the ports running on the graphical side - screen, mouse, kbd, etc., e.g.: $ pkg info -xr xorg-server xorg-server-1.7.7_8,1: xf86-input-keyboard-1.7.0 xf86-input-mouse-1.9.0 xf86-video-vesa-2.3.2 nvidia-driver-310.44_1 $ So I'd say something is wrong with your installation if xorg-server is being pulled in when you build emacs, xterm or cvsup. Post the output from pkg info -aq. Maybe this will give us a hint. Anton ___ 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: X client without X server
From: Anton Shterenlikht me...@bris.ac.uk To: me...@bristol.ac.uk; olivier2...@gmail.com Cc: o...@cs.ait.ac.th; freebsd-questions@freebsd.org Sent: Wednesday, July 3, 2013 9:17 AM Subject: Re: X client without X server From olivier2...@gmail.com Wed Jul 3 13:09:25 2013 Anton, On Wed, Jul 3, 2013 at 5:47 PM, Anton Shterenlikht me...@bris.ac.uk wrote: Date: Wed, 3 Jul 2013 10:55:48 +0700 (ICT) From: Olivier Nicole olivier.nic...@cs.ait.ac.th To: freebsd-questions@freebsd.org Subject: X client without X server Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. Is there a way to install xterm and only the libraries that are needed to run xterm? TIA, Olivier I've been doing this for years. What's the problem? Just install xterm, or whatever you need. All the necessary libs will be pulled in, e.g.: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But for some reason, xorg-server gets installed too. And tons of fonts, and ... It could be emacs, or cvsup, these are the 3 X Window clients I install. I don't use emacs, but you can quickly check, prior to installing, what other ports will be required, e.g. do make -C /usr/ports/ search name=emacs-24 You might be familiar with this already, but if not, the B-deps are those ports which are required to build your port, and R-deps are required to run your port. For emacs-24, both the default and the devel branches, you see that they depend on xorg-fonts-truetype-7.7_1 and lots of other libs, but not on xorg-server. net/cvsup has a lot fewer dependencies, again no xorg-server. In general X server is only required by the ports running on the graphical side - screen, mouse, kbd, etc., e.g.: $ pkg info -xr xorg-server xorg-server-1.7.7_8,1: xf86-input-keyboard-1.7.0 xf86-input-mouse-1.9.0 xf86-video-vesa-2.3.2 nvidia-driver-310.44_1 $ So I'd say something is wrong with your installation if xorg-server is being pulled in when you build emacs, xterm or cvsup. Post the output from pkg info -aq. Maybe this will give us a hint. Anton ___ 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 Just my 2¢ worth on this. Sure, one always wants to keep overhead low. But the days of limited RAM, small hard drives, etc...are long since behind us. I remember in 1994 when and IT consultant came in and built a Novell server for us with a whopping 1 GB hard drive. And back then how we thought with a 1 GB hard drive we'd never run out of space. Well these days one could easily run out of space with such a small hard drive. But with today's systems having 2 or 3 TB drives and GB's of RAM, something as trivial as X-Server should not be a problem. If you don't need it, don't run it. But to worry about the space it takes up is kind of a moot point these days. And like some of the other replies mentioned, xterm may not require it, but one of xterm's dependencies may. I run Asterisk routinely on my systems and I'm always amazed at how installing one port requires no less than 38 other ports to be installed as well. ___ 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: X client without X server
On Jul 2, 2013, at 8:55 PM, Olivier Nicole wrote: Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. If you never run emacs in X11 mode, but instead run emacs within the XTerm, might I suggest that you look into the emacs-nox11 package (/usr/ports/editors/emacs-nox11). This should cut down on the number of dependencies significantly, but if you run emacs directly as an X11 program, then emacs-nox11 will not provide that functionality -- so this suggestion is [again] only helpful if you're used to just running emacs in the XTerm. On the vim side of things, I tend to shoot for vim-lite instead of vim. Same reason, fewer dependencies. Is there a way to install xterm and only the libraries that are needed to run xterm? You could always go the binary package route. force-install the binary package, then do an ldd on xterm to find out what's missing. Then compare what's missing to the packing-list's @pkgdep entries (/var/db/pkg/xterm*/+CONTENTS for non-pkgng systems; for pkgng systems, [guessing] pkg info -dx xterm) -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: X client without X server
Hello, It is usually not about disk space (though that is also not exactly free and unlimited either), but about compilation/update delays, ease of management, additional security risks, additional ways to fail for the system as a whole, etc. Not to mention simple elegance. Best wishes Eugene -Original Message- From: Bill Tillman Sent: Wednesday, July 03, 2013 7:26 PM To: freebsd-questions@freebsd.org Subject: Re: X client without X server Just my 2¢ worth on this. Sure, one always wants to keep overhead low. But the days of limited RAM, small hard drives, etc...are long since behind us. I remember in 1994 when and IT consultant came in and built a Novell server for us with a whopping 1 GB hard drive. And back then how we thought with a 1 GB hard drive we'd never run out of space. Well these days one could easily run out of space with such a small hard drive. But with today's systems having 2 or 3 TB drives and GB's of RAM, something as trivial as X-Server should not be a problem. If you don't need it, don't run it. But to worry about the space it takes up is kind of a moot point these days. And like some of the other replies mentioned, xterm may not require it, but one of xterm's dependencies may. I run Asterisk routinely on my systems and I'm always amazed at how installing one port requires no less than 38 other ports to be installed as well. ___ 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: X client without X server
Date: Wed, 3 Jul 2013 08:26:09 -0700 (PDT) From: Bill Tillman btillma...@yahoo.com Subject: Re: X client without X server xterm may not require it [xorg-server], but one of xterm's dependencies may. This is simply not true. xterm does not require xorg-server. I know because for years I've been using a setup where the X server and the clients live on different computers. There is certainly no xorg-server installed on the clients computer. So, if the OP says that in his setup xterm requires xorg-server, then something is clearly wrong with that setup and it's a good idea to fix it. This might be but a simptom of a larger problem, who knows. If it were me, I'd certainly want to get to the bottom of this. Anton ___ 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: X client without X server
On 07/03/13 16:26, Bill Tillman wrote: [Vast snip.] Just my 2¢ worth on this. Sure, one always wants to keep overhead low. But the days of limited RAM, small hard drives, etc...are long since behind us. I remember in 1994 when and IT consultant came in and built a Novell server for us with a whopping 1 GB hard drive. And back then how we thought with a 1 GB hard drive we'd never run out of space. Well these days one could easily run out of space with such a small hard drive. But with today's systems having 2 or 3 TB drives and GB's of RAM, something as trivial as X-Server should not be a problem. If you don't need it, don't run it. But to worry about the space it takes up is kind of a moot point these days. And like some of the other replies mentioned, xterm may not require it, but one of xterm's dependencies may. I run Asterisk routinely on my systems and I'm always amazed at how installing one port requires no less than 38 other ports to be installed as well. There's another reason beside space for not wanting to install a port unless it's definitely needed, especially on any machine that is world facing - security. If a port is installed but unused it might aid an attacker who gets part way into a system to get further privileges. If it's not installed it definitely can't be used for that. I apply the same principle to the base system on world visible servers - if it's not used and there's a src.conf option to remove it, it gets removed. As the old sysadmin joke goes: Yes, I'm paranoid. But am I paranoid enough? -- In the dungeons of Mordor, Sauron bred Orcs with LOLcats to create a new race of servants. Called Uruk-Oh-Hai in the Black Speech, they were cruel and delighted in torturing spelling and grammar. _Lord of the Rings 2.0, the Web Edition_ ___ 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: X client without X server
Hi, Just my 2¢ worth on this. Sure, one always wants to keep overhead low. But the days of limited RAM, small hard drives, etc...are long since behind us. My concern is when portupgrade -a. The more ports on the system, the more likely the upgrade will fail. So I'd prefer to have as little unused ports as possible. Not to mention that security wise, having unused ports sitting there is not too good. Best regards, Olivier ___ 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
X client without X server
Hi, Is there a way to install an X client without automatically install an X server? On all my systems, I throw xterm and emacs, as the primary tools I use for management, but the display is always remote, I never, ever, run X on the machine, but still it install X server, fonts and a lot of useless junk like xcalc. Is there a way to install xterm and only the libraries that are needed to run xterm? TIA, Olivier ___ 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
stop and start X server in FreeBSD 9.0
Hello: I configured FreeBSD 9.0 RELEASE with X starting automatically at boot. I use kdm3 login manager, and it works. I would like to make changes to xorg.conf and test the effects. How can I stop X in a terminal temporarily? If I kill kdm it is restarted immediately. In openSUSE I could do this by switchiong runlevels but I learned that FreeBSD has no runlevels. Thanks, Istvan ___ 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: stop and start X server in FreeBSD 9.0
On Tue, 02 Oct 2012 15:33:50 +0200, Istvan Gabor wrote: Hello: I configured FreeBSD 9.0 RELEASE with X starting automatically at boot. I use kdm3 login manager, and it works. I would like to make changes to xorg.conf and test the effects. How can I stop X in a terminal temporarily? If I kill kdm it is restarted immediately. For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. If you are happy with your settings, re-enable KDE (kdm) by the corresponding /etc/rc.conf entry. In openSUSE I could do this by switchiong runlevels but I learned that FreeBSD has no runlevels. Yes, FreeBSD uses the rc.d mechanism (see man 8 rc for details). -- 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: stop and start X server in FreeBSD 9.0
On Tuesday 02 October 2012 14:49:54 Polytropon wrote: For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. The OP is using kdm3 which is normally managed through /etc/ttys instead of an rc script. To stop kdm3: * edit /etc/ttys, find the line 'ttyv8 /usr/local/bin/kdm xterm on secure' and changie on to off * kill -1 1 * killall kdm-bin To restart * edit /etc/ttys and change off back to on for kdm * kill -1 1 But it isn't necessary to do all this just to pick up changes in xorg.conf. Just make your desired changes to xorg.conf, then log out of kde and switch to a console as root and killall kdm-bin. This will stop and start X as well as kdm. You can do all this from a terminal window in your kde session but I prefer to logout cleanly instead of having the rug pulled from under my feet which has sometimes corruptedf my kdmrc file. -- Mike Clarke ___ 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: stop and start X server in FreeBSD 9.0
Polytropon, Mike, Thank for your answers. 2012. október 2. 17:29 napon Mike Clarke jmc-freeb...@milibyte.co.uk írta: On Tuesday 02 October 2012 14:49:54 Polytropon wrote: For the desired test scenario, I'd suggest to disable KDE (kdm) startup in /etc/rc.conf, and finally stop the related service (from /usr/local/etc/rc.d probably). Then you can easily use the startx command to start an X session from a user's VT, test your settings, terminate the session, and you'll be back in text mode. The OP is using kdm3 which is normally managed through /etc/ttys instead of an rc script. To stop kdm3: * edit /etc/ttys, find the line 'ttyv8 /usr/local/bin/kdm xterm on secure' and changie on to off I did this one before. I hoped I could make it without editing ttys every time. * kill -1 1 * killall kdm-bin Thanks for pointing out which program has to be killed. To restart * edit /etc/ttys and change off back to on for kdm * kill -1 1 But it isn't necessary to do all this just to pick up changes in xorg.conf. Just make your desired changes to xorg.conf, then log out of kde and switch to a console as root and killall kdm-bin. This will stop and start X as well as kdm. You can do all this from a terminal window in your kde session but I prefer to logout cleanly instead of having the rug pulled from under my feet which has sometimes corruptedf my kdmrc file. I guess this is the way to go. Thanks! Istvan ___ 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
X server already running on display :0
I have a problem that I do not understand. At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist I have not knowingly made any changes to this machine. Any suggestions? Thanks /Leslie ___ 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: X server already running on display :0
At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get copying files instead of installing packages isn't bright idea, unless you copy complete /usr/local tree. ___ 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: X server already running on display :0
2012-07-21 18:42, Wojciech Puchar skrev: At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get copying files instead of installing packages isn't bright idea, unless you copy complete /usr/local tree. ___ 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 understand that, but I needed to approach the problem some way to get some information. ___ 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: X server already running on display :0
Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist this is an answer i think ___ 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: X server already running on display :0
On Sat, 21 Jul 2012 18:24:26 +0200, Leslie Jensen wrote: I have a problem that I do not understand. At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. This means your ~/.xinitrc contains a call to launch Xfce 4, typically the last command, prefixed by exec, in that file. It seems you don't have Xfce 4 installed. Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist I have not knowingly made any changes to this machine. It's not sufficient to copy just this start script (out of the Xfce 4 software package). You need to _completely_ install it, including all dependencies. You can use pkg_add -r to do this, or use the xfce metaport per make install. Any suggestions? Just install Xfce 4 in one of the usual ways. -- 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
SV: Re: X server already running on display :0
True! I copied this file as well and now xfce starts as usual. /Leslie Wojciech Puchar woj...@wojtek.tensor.gdynia.pl skrev: Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist this is an answer i think ___ 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: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com wrote: My assumption still is: Not _every_ keyboard manufacturer does code the layout into the USB identification. If you tell me I'm wrong with this assumption, I'll be happy. :-) Folks are supposed to use a different product ID for different devices, so you can uniquely identify them. I can't promise that every vendor handles this perfectly, any more than folks always ensured that PCI ids uniquely identified a specific hardware version, but one should blame the vendor for being brain-damaged in such cases; it isn't a fault of the USB standard If someone manufactures a single type of keyboard -- using only one type of ASIC, one PCB/keyswitch layout, one kind of housing, etc. -- I'd say it is very much open to interpretation whether snapping on a different collection of keycaps makes it into a different product. Even if the manufacturer tried to cover for the possibility, e.g. by providing a jumper on the PCB which is supposed to be set according to the installed set of keycaps, there will still be cases where an end user replaces or rearranges the keycaps to change the layout and doesn't change the jumper setting. ___ 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: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com, 2011-11-09 22:10 (+0100): How would HAL know that the keyboard had a Swedish layout? No such information is sent through USB or PS/2 when you attach a keyboard. True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. I'm sorry I was unclear. I meant the USB device doesn't say what physical keyboard layout it has in any standardized way. There is nothing in the USB protocol about it. The product ID code might tell you something if you have a large database and the USB product ID is indeed different between two physical layouts. It might not be. For instance, while ANSI keyboards and ISO keyboards are bound to have different USB product IDs because of actually physical differences in the number of keys, the only thing that differs between, say, a German keyboard and a Swedish keyboard of the same model is what is printed on the keycaps. A vendor might see these as the same USB product ID. -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: X server and xinit works excellent....almost.
Samuel Magnusson samuel.magnuss...@bredband.net, 2011-11-09 21:52 (+0100): Because with HAL and DBUS enabled this InputDevice section is bypassed unless I also specify Option AutoAddDevices false. Which I understand gives the same result as not enabling HAL and DBUS in the first place. If you don't enable HAL and DBUS, you're using an X server compiled with HAL and DBUS support and you haven't set AutoAddDevices to false you won't get any input devices at all: no working mouse, no working keyboard. At least, this was my experience after an upgrade long ago. Quite frustrating. I learned about the AutoAddDevices first and later rebuilt my X server without HAL or DBUS support. -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: X server and xinit works excellent....almost.
Samuel Magnusson samuel.magnuss...@bredband.net, 2011-11-10 00:49 (+0100): Michael Cardell Widerkrantz wrote 2011-11-09 21:02: What new style XML method? I'm referring to what Polytropon said about all the new stuff required by X. As I understood him he was talking about the XML-files to give directions to HAL Ah! HAL! Good riddance! Perhaps you can file a Problem Report (PR) with a suggested text? I suggest you add the text to the handbook since I assume the X.org project won't touch manual pages for the ancient X servers we use in FreeBSD. As I understand you, the man-pages from Xorg that are in FreeBSD are not allowed to be altered unless the Xorg project do it themselves, I'm sure they can be altered in FreeBSD. I just thought it might be better to add the text to the handbook. Or both. Anyway, I wasn't aware that the FreeBSD X server was ancient and different from any other. :) We're a few versions behind the X.org bleeding edge since modern servers require kernel changes. Modern X.org servers require Kernel-based Mode Setting (KMS) and Graphics Execution Manager (GEM) and udev support. While it's likely there could be some udev glue on top of devd I don't know if someone is working on it. Warner, perhaps? KMS and GEM, mainly for the intel drivers, are being worked on: http://wiki.freebsd.org/Intel_GPU Also a good beginners tutorial on the fonts would be good, because as I understand it there is also an old and a new way with the core fonts and the font server, some methods belonging to one and some to the other. That's true. You can start by reading my blog post about it: http://hack.org/mc/blog/xfonter.html It's in Swedish, I'm afraid, but both your name and the fact that you were talking about a Swedish keyboard earlier makes me think you can cope with that. But if I do produce something, where should I send the PR and text? See the send-pr(1) manual page. Failing that, use: http://www.freebsd.org/send-pr.html -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: X server and xinit works excellent....almost.
Polytropon free...@edvax.de, 2011-11-10 01:30 (+0100): Now as it (almost?) works on FreeBSD, it's already deprecated by new Linux concepts such as udev, upower and other usomethings. Maybe they become available as interfaces on FreeBSD too, but my fear is... as soon as they are usable, there's already something else obsoleting them right away. :-( By then I'm sure Linux distributions have moved on to the Wayland Display System. Times like these I wish I had the time to bring back MGR from the dead: http://hack.org/mc/mgr/ -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: X server and xinit works excellent....almost.
2011-11-09 21:52, Samuel Magnusson skrev: When I first installed Xorg I began by following the handbook, which means that I unwittingly did this to my poor rc.conf: hald_enable=YES dbus_enable=YES That meant that I would HAVE to go into the XML-stuff (to get swedish keys) If all you want is a swdish keyboard layout then put this in your ~/.xinitrc setxkbmap se ___ 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: X server and xinit works excellent....almost.
On Nov 10, 2011, at 2:25 AM, Michael Cardell Widerkrantz wrote: True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. I'm sorry I was unclear. I meant the USB device doesn't say what physical keyboard layout it has in any standardized way. There is nothing in the USB protocol about it. That's fairly said-- you'd have to query a database of vendor+product ids and see whether you can determine that a particular keyboard is for a given country and/or language. If you don't find a match, there isn't a good way of identifying the region of the device just via USB protocol. The product ID code might tell you something if you have a large database and the USB product ID is indeed different between two physical layouts. It might not be. For instance, while ANSI keyboards and ISO keyboards are bound to have different USB product IDs because of actually physical differences in the number of keys, the only thing that differs between, say, a German keyboard and a Swedish keyboard of the same model is what is printed on the keycaps. A vendor might see these as the same USB product ID. Different keycaps means a different product SKU, at least. If they use the same USB product ID, then you're going to have to define a keymap file / xmodmap / etc to associate the scan codes with the right character that's printed on the keycaps. FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. To my mind, though, that's a fallback for when you have a KVM or a PS/2-to-USB converter or suchlike in the way that prevents the device from being correctly recognized. Regards, -- -Chuck ___ 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: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com, 2011-11-10 20:12 (+0100): Different keycaps means a different product SKU, at least. If they use the same USB product ID Yes. I think this is a quite common scenario. FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. Certainly. To my mind, though, that's a fallback for when you have a KVM or a PS/2-to-USB converter or suchlike in the way that prevents the device from being correctly recognized. Or when you have, say, a keyboard that physically is an ANSI keyboard (one less physical key compared to ISO keyboards) but still want, say, a Swedish keymap or, indeed, your very own keymap, unlike any other. Like me when I'm using one of my Happy Hacking Keyboards. Topre switches FTW! -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: X server and xinit works excellent....almost.
On Thu, Nov 10, 2011 at 11:12 AM, Chuck Swiger cswi...@mac.com wrote: FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. I thought I'd mention that OS X takes an interesting approach to this. When you plug in a keyboard it doesn't recognize, it does a little dance where it tells you to press certain keys (e.g., Press the key to the right of the left Shift key, with a little graphic to help you understand which key it means) and from the results it infers the layout. ___ 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: DBUS + kvm breaks X server (was: X server and xinit works excellent....almost.)
On Wed, Nov 9, 2011 at 11:56 AM, Warren Block wbl...@wonkity.com wrote: Are the keyboard and mouse USB devices? A KVM should not disconnect them on switching, but maybe it does. In my experience, most inexpensive USB KVMs work by disconnecting the keyboard/mouse from one system and reconnecting them to the other. They rely on the OS's USB hotplug support to do the right thing. On Windows systems this is pretty obvious because you hear the ba-DUMP sound effect it makes when it detects a new USB device. ___ 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: X server and xinit works excellent....almost.
On Nov 10, 2011, at 3:57 PM, David Brodbeck wrote: On Thu, Nov 10, 2011 at 11:12 AM, Chuck Swiger cswi...@mac.com wrote: FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. I thought I'd mention that OS X takes an interesting approach to this. When you plug in a keyboard it doesn't recognize, it does a little dance where it tells you to press certain keys (e.g., Press the key to the right of the left Shift key, with a little graphic to help you understand which key it means) and from the results it infers the layout. Indeed, yes-- that's KeyboardTypeSection, part of Setup Assistant.app used to perform initial configuration of a new system. While I think it makes a good example, I don't want to evangelize stuff from $REALJOB too strongly. :-) Regards, -- -Chuck ___ 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: X server and xinit works excellent....almost.
Thanks guys, that was really helpful! I now also installed the nVidia driver and it works well. The reason I didn't use it in the first place was that I had read that the old Geforce 2-card wasn't supported by the nVidia rivers anymore. And that nouveau (as replacement for nv) should be used instead. (But that was on a Gentoo Linux page when I tried that OS shortly before FreeBSD and thought it was the same with the drivers. Apparently I was wrong... I made a minimal install of Xorg and only downloaded nouveau. ) The zoom works just fine now for all resolutions supported. So I guess my driver issue is solved. I got the zap to work also, but first only by using the setxkbmap command in .xinitrc. Which made me remember that I had the exact same problem with my swedish keyboardmappings the very first time I started X. I just couldn't get it to work and nearly gave up before I tried the setxkbmap method and put them into .xinitrc, which saved me. Although I had put the exact same rules and layout options in xorg.conf and double checked the format and spelling hundreds of times. The problem was still there now: when I commented it out in .xinitrc I got the US keyboard in xterm in spite of the xorg.conf settings. It seemed like the X server just ignored all my keyboard options in xorg.config. Which it also did! (As I also colud confirm from the logfile) The thing that really made it was the Option AutoAddDevice off, which I had failed to notice. I realize that it was too long since I looked into the handbook, because it is in clear text there. Sorry for that! But since this autodetection seems to be the standard for Xorg now and it is so important issue to get things working, maybe it should be put in a highlighted box with Important! written on it. The thing is that I was also using other documentation and guides, like the manpages or books of maybe a couple of years old. This issue is not mentioned and the InputDevices sections in xorg.conf is just supposed to work. A not outdated example of unclarity: the man page xorg.conf(5) freshly installed with my system says: Option AutoAddDevices boolean If this option is disabled, then no devices will be added from HAL events. Enabled by default. It doesn't warn that if it is NOT disabled the InputDevice sections won't work at all. And no devices will be added sounds like a bad thing, so you rather leave this option enabled... And then in the INPUTDEVICE SECTION: Recent X servers employ input hotplugging to add input devices, with the HAL backend being the default backend for X servers since 1.4. It is usually not necessary to provide InputDevice sections in the xorg.conf if hotplugging is enabled. I smile when I read such things, because usually not neceesary to provide is a funny way to express not able to provide. :) It should be clearly stated that theese are two conflicting options and that autoconfiguration overrides manual entries. I think it always should be the reverse, but thats no big deal as long as it is very clear how to enforce the manual choices on the system. Of course it is logical that you can't have both, but I can assure you as a newbie with all that you have to learn that this detail is easy to miss. And when autoconfiguration overrides then you are lost without knowing why , because everything seems correctly configured except it doesn't work. Now I'm curious: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? Thanks again for the help! ___ 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: X server and xinit works excellent....almost.
Samuel Magnusson wrote 2011-11-09 12:06: Now I'm curious: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? Well don't bother answering, because I understand it from reading the handbook. It is clear to me now, it was just to much new info for my brain to handle earlier.. :) Now my original questions 3-4 still remain unsolved. This works for me: X :0 -terminate Ctrl-Alt-F1 xterm -display :0 Ctrl-Alt-F9 exit xterm.. which brings me back to the first console. But this doesn't work: X :0 -terminate vt4 Ctrl-Alt-F1 (doesn't respond) Ctrl-Alt-Backspace (doesn't respond) ssh-login from my laptop works so I can start a xterm -display :0 from there. But even if I can focus the xterm-window with the mouse the keyboard doesn't respond so I can't write any commands. If I kill -9 the X server and the login process on vt4 the processes disappears from the list but I am still not taken back to vt0 and the system hangs except for my ssh-login that still works. I have to shutdown or reboot from there. Any clue why? Is my command X :0 vt4 wrong or not supposed to work? ___ 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: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 12:06:37 +0100, Samuel Magnusson wrote: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? I hope not! :-) As far as I understood the _current_ mechanism, the precedence is 1st xorg.conf, 2nd XML stuff, 3rd autodetect. You have X without HAL and DBUS? Use xorg.conf because this has worked for many years to centralize X configuration. You have X with HAL and DBUS, but don't want to use it? Reflect this choice in xorg.conf and continue with previous settings. You have X with HAL and DBUS, but some things aren't detected properly? Dive into the fun of XML and enter your settings in the appropriate files, whichever they currently may be. :-) There _are_ things that cannot be autodetected, and HAL needs to be configured to notice a localization deviation from the standard, which is en_US. That's what you are going to use the XML stuff for. In case you're _not_ using HAL with X, you have to make the settings in xorg.conf, like this: Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayoutde Option XkbOptions terminate:ctrl_alt_bksp EndSection Note that putting the Zap key into this file seems to be more comfortable than putting it into some obscure XML files scattered across the file system. And completely independent from all those options, you still can _always_ use [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc in your X initialization file (usually ~/.xinitrc). This does _not_ say anything about what might become current when HAL is fully out of support (as it is already considered deprecated in Linux). And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? Can you tell me _how_ anything in software is supposed to know what characters are printed on the key caps of the keyboard? I'm not sure keyboard vendors do code localization variants into their USB identification numbers... This makes me assume the following: It's not possible to determine the localized layout of a keyboard. Just imagine I pop the german keycaps from my IBM model M keyboard and put a set of swedish caps on, would the system notice that change? :-) -- 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: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 13:19:44 +0100, Samuel Magnusson wrote: This works for me: X :0 -terminate Ctrl-Alt-F1 xterm -display :0 Ctrl-Alt-F9 exit xterm.. which brings me back to the first console. But this doesn't work: X :0 -terminate vt4 Ctrl-Alt-F1 (doesn't respond) Ctrl-Alt-Backspace (doesn't respond) Do you have ``Option DontVTSwitch false'' in xorg.conf? Any clue why? Is my command X :0 vt4 wrong or not supposed to work? What is the correct notation for the terminal device to start it on? Maybe ttyv4 (as in /etc/ttys)? -- 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
DBUS + kvm breaks X server (was: X server and xinit works excellent....almost.)
Since this has been mentioned, I though I'd take the opportunity ... Polytropon writes: You have X without HAL and DBUS? Use xorg.conf because this has worked for many years to centralize X configuration. You have X with HAL and DBUS, but don't want to use it? Reflect this choice in xorg.conf and continue with previous settings. You have X with HAL and DBUS, but some things aren't detected properly? Dive into the fun of XML and enter your settings in the appropriate files, whichever they currently may be. :-) I have two systems - one Windows, one FreeBSD - that share monitor, keyboard, and mouse via a kvm. FreeBSD had both HAL and DBUS installed and activated in rc.conf. Scenario: I'm working on the FreeBSD system, and switch to the WIndows system (push the button on the kvm) everything's fine. But when I switch back, I an now sitting at the Xdm prompt; I'm guessing this means X has crashed. I experimented a little and discovered if I disable DBUS after initial boot, this no longer happens. (It makes some other things unhappy, but I can live with that.) Anyone have anyideas what might be happening and how to unbreak this? 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: DBUS + kvm breaks X server (was: X server and xinit works excellent....almost.)
On Wed, 9 Nov 2011, Robert Huff wrote: I have two systems - one Windows, one FreeBSD - that share monitor, keyboard, and mouse via a kvm. FreeBSD had both HAL and DBUS installed and activated in rc.conf. Scenario: I'm working on the FreeBSD system, and switch to the WIndows system (push the button on the kvm) everything's fine. But when I switch back, I an now sitting at the Xdm prompt; I'm guessing this means X has crashed. I experimented a little and discovered if I disable DBUS after initial boot, this no longer happens. (It makes some other things unhappy, but I can live with that.) Anyone have anyideas what might be happening and how to unbreak this? Are the keyboard and mouse USB devices? A KVM should not disconnect them on switching, but maybe it does. Try it without HAL by adding Option AutoAddDevices Off to ServerLayout in xorg.conf. ___ 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: X server and xinit works excellent....almost.
Samuel Magnusson samuel.magnuss...@bredband.net, 2011-11-09 12:06 (+0100): Which made me remember that I had the exact same problem with my swedish keyboardmappings the very first time I started X. I just couldn't get it to work and nearly gave up before I tried the setxkbmap method and put them into .xinitrc, which saved me. Although I had put the exact same rules and layout options in xorg.conf and double checked the format and spelling hundreds of times. The problem was still there now: when I commented it out in .xinitrc I got the US keyboard in xterm in spite of the xorg.conf settings. XKB is a bit of a mystery compared to good old xmodmap. A while ago I tried to understand it. The result is a small guide on how you can use XKB to define your own keyboard mapping and load it without having to be root. I used my own version of a Swedish keyboard on a Happy Hacking Keyboard as an example: http://hack.org/mc/writings/xkb.html The thing that really made it was the Option AutoAddDevice off, which I had failed to notice. Yes, this is really important, especially if you don't want that dreadful HAL on your system. Considering that the default is on and HAL isn't a dependency for the X server, many users were surprised when they didn't have any working mouse nor keyboard! I don't use HAL and it seems even the X.org project has moved away from HAL even if such modern X.org X servers are not yet in ports. It doesn't warn that if it is NOT disabled the InputDevice sections won't work at all. And no devices will be added sounds like a bad thing, so you rather leave this option enabled... Perhaps you can file a Problem Report (PR) with a suggested text? I suggest you add the text to the handbook since I assume the X.org project won't touch manual pages for the ancient X servers we use in FreeBSD. Now I'm curious: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? What new style XML method? AFAIK the more modern X.org X servers uses the Linux udev instead of HAL. Those servers are not yet available on FreeBSD but presumably it would be possible to use devd for the same purpose. And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? How would HAL know that the keyboard had a Swedish layout? No such information is sent through USB or PS/2 when you attach a keyboard. This is up to your own language settings, either with what you have entered in the form of setxkbmap or xkbcomp in your .xinitrc/.xsession or your settings in the desktop environment of your choice. -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ 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: DBUS + kvm breaks X server (was: X server and xinit works excellent....almost.)
On Wed, 9 Nov 2011 14:02:07 -0500 Robert Huff articulated: Since this has been mentioned, I though I'd take the opportunity ... Polytropon writes: You have X without HAL and DBUS? Use xorg.conf because this has worked for many years to centralize X configuration. You have X with HAL and DBUS, but don't want to use it? Reflect this choice in xorg.conf and continue with previous settings. You have X with HAL and DBUS, but some things aren't detected properly? Dive into the fun of XML and enter your settings in the appropriate files, whichever they currently may be. :-) I have two systems - one Windows, one FreeBSD - that share monitor, keyboard, and mouse via a kvm. FreeBSD had both HAL and DBUS installed and activated in rc.conf. Scenario: I'm working on the FreeBSD system, and switch to the WIndows system (push the button on the kvm) everything's fine. But when I switch back, I an now sitting at the Xdm prompt; I'm guessing this means X has crashed. I experimented a little and discovered if I disable DBUS after initial boot, this no longer happens. (It makes some other things unhappy, but I can live with that.) Anyone have anyideas what might be happening and how to unbreak this? I have virtually the same setup. A wireless keyboard/mouse that transmits to a USB device. The Windows systems activates virtually instantaneously; however, the FreeBSD system hangs for five seconds or more before it becomes responsive. Other than that, I have not noticed any problems (yet). Both HAL and DBUS are activated via the rc.conf file and I have not made any special modifications to the system config files. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the Reply-To header. http://www.catb.org/~esr/faqs/smart-questions.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: X server and xinit works excellent....almost.
Polytropon wrote 2011-11-09 19:15: On Wed, 09 Nov 2011 12:06:37 +0100, Samuel Magnusson wrote: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? I hope not! :-) As far as I understood the _current_ mechanism, the precedence is 1st xorg.conf, 2nd XML stuff, 3rd autodetect. You have X without HAL and DBUS? Use xorg.conf because this has worked for many years to centralize X configuration. You have X with HAL and DBUS, but don't want to use it? Reflect this choice in xorg.conf and continue with previous settings. You have X with HAL and DBUS, but some things aren't detected properly? Dive into the fun of XML and enter your settings in the appropriate files, whichever they currently may be. :-) There _are_ things that cannot be autodetected, and HAL needs to be configured to notice a localization deviation from the standard, which is en_US. That's what you are going to use the XML stuff for. I like that precedence list, because the old way seems much clearer and simpler to me. If autodetection only does half the detecting and then lays the burden of a new and more complicated manual configuration, then not much is gained. And why on earth could they not just have left what needed to be manually configured in the xorg.conf and make it override the HAL default mode? That would be the logical and easy way, in my inexperienced opinion. So as I understand it from my mistakes this precedence list is only true under certain circumstances, and I fell in a nice little devilish newbie-trap. :) When I first installed Xorg I began by following the handbook, which means that I unwittingly did this to my poor rc.conf: hald_enable=YES dbus_enable=YES That meant that I would HAVE to go into the XML-stuff (to get swedish keys) , because I could configure the InputDevice section until blue in my face (which I also did), and still nothing would happen witht the keyboard layout. Because with HAL and DBUS enabled this InputDevice section is bypassed unless I also specify Option AutoAddDevices false. Which I understand gives the same result as not enabling HAL and DBUS in the first place. Its just an unnecessary circle, first enabling, then disabling. I have to give cred to the FreeBSD handbook because it is actually quite correct and clear on this point (as no other text I found was) and tells what to do if wanting to do it the old way. But for some reason that I cannot recall now, I didn't understand it right away and strayed away from the handbook to among other things the X.org website and the man pages and other introductory books, which doesn't warn about this at all. It just assumes that xorg.conf sections works as usual. But it didn't to my hald-enabled system. I never returned to the handbook, because I stumbled on the working method with setxkbmap which did override the HAL default layout. I left it as a big question mark to maybe get back to it later. When I started this thread I had no idea that my problem with zap could be related to the same keyboard problem I had encountered earlier. ...so I'm learning. :) Can you tell me _how_ anything in software is supposed to know what characters are printed on the key caps of the keyboard? I'm not sure keyboard vendors do code localization variants into their USB identification numbers... No I can't. :) I realized the unprobability of this when hitting the send button. And your comment is also a good argument for keeping the simpler keyboard configuration in xorg.conf, isn't it? Couldn't autodetection of the keyboard work together with xorg.conf just like when giving the command X -configure and /root/xorg.config.new is created? For example that detected my monitor, my graphics card and my installed drivers, and it put those as entrys in the file so it is easy to edit and add options if necessary. HAL could just put pc105 into the normal InputDevice section and let me fill in the Layout... What is there more than pc105 to autodetect then that I would need HAL to make my life easier? I guess these are decisions to be made by X.org though, and not by me.. I just wonder. :) Anyway, can you stand one more just curious-question from me? When I used the vesa and nouveau drivers they were automatically kldloaded when the X server read the xorg.conf file. But the nVidia driver I have to kldload manually because otherwise the X server doesn't find it. Of course I will put it in loader.conf, but is it normal? Should it not be loaded authomatically as the others? ___ 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: X server and xinit works excellent....almost.
Hi-- On Nov 9, 2011, at 12:02 PM, Michael Cardell Widerkrantz wrote: And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? How would HAL know that the keyboard had a Swedish layout? No such information is sent through USB or PS/2 when you attach a keyboard. True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. For example, see: http://www.linux-usb.org/usb.ids At the moment, I happen to be using a: Apple Pro Keyboard: Product ID: 0x020b Vendor ID: 0x05ac (Apple Inc.) Version: 4.20 Speed: Up to 12 Mb/sec Manufacturer: Mitsumi Electric Location ID: 0x3d111300 / 6 Current Available (mA): 250 Current Required (mA): 50 ...and this database would correctly let the system know that I'm using US layout: 020b Pro Keyboard [Mitsumi, A1048/US layout] If you figure out that a Logitech Tangentbord K120 (or an Apple MC184S) is connected, then you've got a Swiss keyboard, and so forth. Regards, -- -Chuck ___ 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: X server and xinit works excellent....almost.
Michael Cardell Widerkrantz wrote 2011-11-09 21:02: Samuel Magnussonsamuel.magnuss...@bredband.net, 2011-11-09 12:06 (+0100): Now I'm curious: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? What new style XML method? AFAIK the more modern X.org X servers uses the Linux udev instead of HAL. Those servers are not yet available on FreeBSD but presumably it would be possible to use devd for the same purpose. I'm referring to what Polytropon said about all the new stuff required by X. As I understood him he was talking about the XML-files to give directions to HAL, and he used quotes so I think he meant supposedly new, or just newer than the classic configuration file but already the old new, as he seem to agree with you that HAL is on it's way out and should be avoided if possible. /Perhaps you can file a Problem Report (PR) with a suggested text? I suggest you add the text to the handbook since /I /assume the X.org project won't touch manual pages for the ancient X servers we use in FreeBSD. / As I understand you, the man-pages from Xorg that are in FreeBSD are not allowed to be altered unless the Xorg project do it themselves, and they won't do it because they have other more current things to do than updating deprecated documents? If so, maybe if just asked they would allow some modifications be done to it? Anyway, I wasn't aware that the FreeBSD X server was ancient and different from any other. :) But I'm a rookie so far.. I was actually thinking when struggling with this that I should learn this X keyboard configuration thoroughly and try to write a beginners tutorial, fail-safe and step by step to help avoiding these traps as I would know whats difficult to understand for a beginner. But I will have to learn a bit more first in that case so I'm not just easy to understand but also correct. I'll study your guide, thanks for the link! Also a good beginners tutorial on the fonts would be good, because as I understand it there is also an old and a new way with the core fonts and the font server, some methods belonging to one and some to the other. And migrating from Windows and Mac might be discouraging if there isn't a working desktop with visible text at least within an hour or two after installation. :) But if I do produce something, where should I send the PR and text? Cheers /Samuel ___ 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: X server and xinit works excellent....almost.
On Thu, 10 Nov 2011 00:49:19 +0100, Samuel Magnusson wrote: Michael Cardell Widerkrantz wrote 2011-11-09 21:02: Samuel Magnussonsamuel.magnuss...@bredband.net, 2011-11-09 12:06 (+0100): Now I'm curious: Is it then so that in the new style Xorg the XML-method will override HAL, and this is the new default way of providing opitons that formerly were in the InputDevice sections in xorg.conf? What new style XML method? AFAIK the more modern X.org X servers uses the Linux udev instead of HAL. Those servers are not yet available on FreeBSD but presumably it would be possible to use devd for the same purpose. I'm referring to what Polytropon said about all the new stuff required by X. As I understood him he was talking about the XML-files to give directions to HAL, and he used quotes so I think he meant supposedly new, or just newer than the classic configuration file but already the old new, as he seem to agree with you that HAL is on it's way out and should be avoided if possible. Depends. If you are using a normal US keyboard and don't have any deviant needs, HAL autodetection of devices should work fine. And as it is X's default configuration, you could even omit xorg.conf if X detects your GPU and display properly. The problems start when you do something not-normal. In such cases, it seems that you better leave HAL and DBUS out of your system, if you don't see any use for them. In that case, the old-fashioned configuration methods should do what you want: centralized settings for X in xorg.conf. Setup once, then use. Anyway, I wasn't aware that the FreeBSD X server was ancient and different from any other. :) There is some delay in porting X's new features from Linux to FreeBSD. Linux is the platform that mostly drives that development. Some parts used by X and by desktop environments are specific to Linux. HAL was initally meant to be a kind of plugin system to get independent from the OS, but it didn't get that far. Now as it (almost?) works on FreeBSD, it's already deprecated by new Linux concepts such as udev, upower and other usomethings. Maybe they become available as interfaces on FreeBSD too, but my fear is... as soon as they are usable, there's already something else obsoleting them right away. :-( Those Linux developments often serve functionalities that have been present in FreeBSD for many years. One of the often cited things is automounting. FreeBSD's automounter amd, in combination with devd, can already automount things independently from desktop environments. It could do that already 5 years ago. This setup can also handle webcams and USB mass storage. The question is: How to interface that with a desktop environment? Those IDE's development is also mainly driven on Linux. An example is Xfce which lost some functionality on FreeBSD because those parts have been rewritten with Linux-only back-ends in mind. Maybe other things will follow, maybe Gnome 3? Who knows... And migrating from Windows and Mac might be discouraging if there isn't a working desktop with visible text at least within an hour or two after installation. :) No problem in that, see FreeSBIE - all what you said, plus you don't need to install anything. :-) -- 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: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 13:10:20 -0800, Chuck Swiger wrote: Hi-- On Nov 9, 2011, at 12:02 PM, Michael Cardell Widerkrantz wrote: And should HAL have discovered my swedish keyboard automatically in the first place, so there was something going wrong there? How would HAL know that the keyboard had a Swedish layout? No such information is sent through USB or PS/2 when you attach a keyboard. True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. Can - I think it's not standard to do so. For example, see: http://www.linux-usb.org/usb.ids Just checked, and the exception is right here: I'm using a Sun USB keyboard + mouse, 0x0430 = Sun Microsystems, Inc. is correct, but 0x100e = 24.1 LCD Monitor v4 / FID-638 Mouse seems to be nonsense. It's a mouse, _infront_ of a 24 monitor, but that's an EIZO CRT. :-) In this regards, it's also strange how FreeBSD could forget USB information it once had. On my old 5.x system, I got dmesg lines like that: ukbd0: Sun Microsystems Type 6 USB keyboard, rev 1.00/1.02, addr 3, iclass 3/1 ums0: Sun Microsystems Type 6 USB mouse, rev 1.00/1.02, addr 2, iclass 3/1 But since 7.0 (6.0 hasn't been introduced to my home system), I get ukbd0: vendor 0x0430 product 0x0005, class 0/0, rev 1.00/1.02, addr 3 on uhub1 ums0: vendor 0x0430 product 0x0100, class 0/0, rev 1.00/1.02, addr 2 on uhub1 Note that the corresponding file in the source tree containing the USB devices still has the proper data! And I haven't changed things on hardware side. But maybe this is because the USB subsystem has had many changes... Now that I have a type 7 keyboard, the USB information still is not useful: % usbconfig -u 1 -a 3 dump_info ugen1.3: Sun USB Keyboard vendor 0x0430 at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON % usbconfig -u 1 -a 2 dump_info ugen1.2: product 0x100e vendor 0x0430 at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE % dmesg | grep ^u[km] ukbd1: vendor 0x0430 Sun USB Keyboard, class 0/0, rev 2.00/1.05, addr 3 on usbus1 ums0: vendor 0x0430 product 0x0100, class 0/0, rev 1.00/1.02, addr 4 on usbus1 ums0: 3 buttons and [XY] coordinates ID=0 You can also see that dmesg logs different data (0x100e vs. 0x0100). At the moment, I happen to be using a: Apple Pro Keyboard: Product ID: 0x020b Vendor ID: 0x05ac (Apple Inc.) Version: 4.20 Speed: Up to 12 Mb/sec Manufacturer: Mitsumi Electric Location ID: 0x3d111300 / 6 Current Available (mA): 250 Current Required (mA): 50 ...and this database would correctly let the system know that I'm using US layout: 020b Pro Keyboard [Mitsumi, A1048/US layout] If you figure out that a Logitech Tangentbord K120 (or an Apple MC184S) is connected, then you've got a Swiss keyboard, and so forth. This is fine as long as you're going to keep that language settings. However, there are users who need a non-US language on a US keyboard layout - or vice versa. In such a case, the autodetection doesn't help. Your example with Apple hardware corresponds to my experience. I also have an older Mac keyboard which works fine on FreeBSD, including proper device identification. My assumption still is: Not _every_ keyboard manufacturer does code the layout into the USB identification. If you tell me I'm wrong with this assumption, I'll be happy. :-) -- 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: X server and xinit works excellent....almost.
Polytropon wrote 2011-11-09 19:19: On Wed, 09 Nov 2011 13:19:44 +0100, Samuel Magnusson wrote: This works for me: X :0 -terminate Ctrl-Alt-F1 xterm -display :0 Ctrl-Alt-F9 exit xterm.. which brings me back to the first console. But this doesn't work: X :0 -terminate vt4 Ctrl-Alt-F1 (doesn't respond) Ctrl-Alt-Backspace (doesn't respond) Do you have ``Option DontVTSwitch false'' in xorg.conf? No I haven't, so I tried it now for completeness sake. But there was no difference. It shouldn't be needed, and VTSwitching works just fine as long as I don't try to choose a virtual terminal to start it in. I tried putting the option there and it is no difference, the computer hangs on the display, and when viewing sockstat -4 from the remote login I could see an awful lot of dbus and hal activity. Since those 'fellas' were the cause of so many of my woes I disenabled them :) , rebooted and tried again. At first no difference except that when I killed the server I was no longer stuck with the black screen and visually returned to tty0. I was not given back the console though and the login was still hanged. Any clue why? Is my command X :0 vt4 wrong or not supposed to work? What is the correct notation for the terminal device to start it on? Maybe ttyv4 (as in /etc/ttys)? Nope. Even if I no longer trust the Xorg man page to 100%, it clearly states vtXX as the notation to use for the option. And when viewing the log it clearly says that it start up the server in vt4 and it doesn't protest but goes on a good while before it stops. Interesting is that it stops without any error message. It is right after reading the keyboardsettings from xorg.conf, the first informational line after that: (II) XINPUT: Adding extended input device Keyboard0 (type: KEYBOARD) Then the file ends. ___ 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: X server and xinit works excellent....almost.
Polytropon skrev 2011-11-10 01:30: On Thu, 10 Nov 2011 00:49:19 +0100, Samuel Magnusson wrote: And migrating from Windows and Mac might be discouraging if there isn't a working desktop with visible text at least within an hour or two after installation. :) No problem in that, see FreeSBIE - all what you said, plus you don't need to install anything. :-) Haha, ok, then its just me that wanted to NOT install a readybuildt desktop, just for learning more about the architechture by trying to install everything manually. I'll have to suffer the consequences of my own decisions... without complaining, which I am not by the way. Thanks for the overview! (And never mind the autoloading question, i found it out in the logfile. Nothing important just a wrong searchpath it seemed. I also succeeded with the vtXX option several times. It was after disabling hal and dbus, but I'm not sure it's because of that, as now it does not function again. It seems unstable at least. But I don't know if I care that much anyway.. ) ___ 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: X server and xinit works excellent....almost.
On Nov 9, 2011, at 5:01 PM, Polytropon wrote: In this regards, it's also strange how FreeBSD could forget USB information it once had. On my old 5.x system, I got dmesg lines like that: ukbd0: Sun Microsystems Type 6 USB keyboard, rev 1.00/1.02, addr 3, iclass 3/1 ums0: Sun Microsystems Type 6 USB mouse, rev 1.00/1.02, addr 2, iclass 3/1 A USB standard device descriptor includes iManufacturer and iProduct fields, which are likely the source of the strings displayed above. I guess the new USB stack doesn't bother to display them. Now that I have a type 7 keyboard, the USB information still is not useful: % usbconfig -u 1 -a 3 dump_info ugen1.3: Sun USB Keyboard vendor 0x0430 at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON % usbconfig -u 1 -a 2 dump_info ugen1.2: product 0x100e vendor 0x0430 at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE % dmesg | grep ^u[km] ukbd1: vendor 0x0430 Sun USB Keyboard, class 0/0, rev 2.00/1.05, addr 3 on usbus1 ums0: vendor 0x0430 product 0x0100, class 0/0, rev 1.00/1.02, addr 4 on usbus1 ums0: 3 buttons and [XY] coordinates ID=0 You can also see that dmesg logs different data (0x100e vs. 0x0100). The 0x0100 is for the mouse; the 0x100e is probably a USB hub, perhaps within the keyboard if the mouse attaches to the keyboard, although the database suggests it was a USB hub within a monitor. If you figure out that a Logitech Tangentbord K120 (or an Apple MC184S) is connected, then you've got a Swiss keyboard, and so forth. This is fine as long as you're going to keep that language settings. However, there are users who need a non-US language on a US keyboard layout - or vice versa. In such a case, the autodetection doesn't help. The idea is that autodetection provides a suggested default, at least if it can identify a country for the input devices which are connected to the system. But users should be able to set up their own language preferences, which might be different from the system default and from other user's settings. Your example with Apple hardware corresponds to my experience. I also have an older Mac keyboard which works fine on FreeBSD, including proper device identification. My assumption still is: Not _every_ keyboard manufacturer does code the layout into the USB identification. If you tell me I'm wrong with this assumption, I'll be happy. :-) Folks are supposed to use a different product ID for different devices, so you can uniquely identify them. I can't promise that every vendor handles this perfectly, any more than folks always ensured that PCI ids uniquely identified a specific hardware version, but one should blame the vendor for being brain-damaged in such cases; it isn't a fault of the USB standard Regards, -- -Chuck ___ 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011, Samuel Magnusson wrote: 1. I can?t zap the server with Ctrl-Alt-Backspace. Nothing at all happens. I have checked that it isn't disabled in xorg.conf, and even tried to put in the reverse boolean value there. Not that I couldn't live without zapping, but...when I know about it that it should be there and it is taken fom me I feel an URGE to get the zap! Zapping is still allowed by default, but a key combination is not assigned. That can be done in .xinitrc or .xsession: setxkbmap -option terminate:ctrl_alt_bksp It can also be done in xorg.conf: Section InputDevice Identifier Keyboard0 Driver kbd Option XkbOptions terminate:ctrl_alt_bksp EndSection 2. Not surprisingly I was also unable to use the Ctrl-Alt-Keypad+/- for zooming between the different resolution modes. But then I remembered that I had changed configuration from vesa driver to nouveau (with some patch that I downloaded according to instructions in ports). When I switched back to vesa it worked! Still no zapping though, and no higher resolution than 1024x768. vesa is very limited, only supporting standard modes up to 1024x768 or 1280x1024. Some vendors add other modes, but they aren't common. nouveau is an open driver for the very closed Nvidia hardware. The closed Nvidia drivers (x11/nvidia-driver*) are supposed to work quite well. ___ 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011 08:14:48 -0700 (MST), Warren Block wrote: On Tue, 8 Nov 2011, Samuel Magnusson wrote: 1. I can?t zap the server with Ctrl-Alt-Backspace. Nothing at all happens. I have checked that it isn't disabled in xorg.conf, and even tried to put in the reverse boolean value there. Not that I couldn't live without zapping, but...when I know about it that it should be there and it is taken fom me I feel an URGE to get the zap! Zapping is still allowed by default, but a key combination is not assigned. That can be done in .xinitrc or .xsession: setxkbmap -option terminate:ctrl_alt_bksp It can also be done in xorg.conf: Section InputDevice Identifier Keyboard0 Driver kbd Option XkbOptions terminate:ctrl_alt_bksp EndSection There is a 3rd option, especially useful when X is run with DBUS and HAL (the default configuration, as well as the package configuration), and it involves fun with XML. :-) File /usr/local/etc/hal/fdi/policy/x11-input.fdi ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp/merge /match /device /deviceinfo And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option DontZap off'' in the ServerFlags section. So, as you're already dealing with xorg.conf, use Warren's suggestion, as it works independently of all the new things required by X, and also conforms to the concept of concentrating X's configuration in one configuration file (rather than scattering settings across the file system). vesa is very limited, only supporting standard modes up to 1024x768 or 1280x1024. Some vendors add other modes, but they aren't common. nouveau is an open driver for the very closed Nvidia hardware. The closed Nvidia drivers (x11/nvidia-driver*) are supposed to work quite well. I'm using nvidia-driver here which works better than nouveau and nv (the one that comes with X.org); I haven't tested VESA as in most cases, it's _not_ what one wants. -- 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011, Polytropon wrote: And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option DontZap off'' in the ServerFlags section. For at least the most recent Xorg, it's not needed. Can't recall whether it is for the one before that. ___ 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011, Warren Block wrote: On Tue, 8 Nov 2011, Polytropon wrote: And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option DontZap off'' in the ServerFlags section. For at least the most recent Xorg, it's not needed. Can't recall whether it is for the one before that. Nope, just tested and I'm wrong. DontZap Off is needed with X.Org X Server 1.7.7. Sorry about that. I recommend adding the option to ServerLayout and doing away with the extra complication of a ServerFlags section. ___ 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011 13:33:55 -0700 (MST), Warren Block wrote: On Tue, 8 Nov 2011, Warren Block wrote: On Tue, 8 Nov 2011, Polytropon wrote: And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option DontZap off'' in the ServerFlags section. For at least the most recent Xorg, it's not needed. Can't recall whether it is for the one before that. Nope, just tested and I'm wrong. DontZap Off is needed with X.Org X Server 1.7.7. Sorry about that. I recommend adding the option to ServerLayout and doing away with the extra complication of a ServerFlags section. Good suggestion, the Handbook should be changed according to that if it really works (and is, in my opinion, easier). My statement regarding the xorg.conf _and_ XML fun wasn't a personal experience and testing (xorg-server-1.7.7_2,1 here), but the Handbook said so: http://www.freebsd.org/doc/handbook/x-config.html It's mentioned directly beneath the XML fun in 6.4.2. There's also a ServerLayout _or_ ServerFlags statement for the ``Option AutoAddDevices false'' setting, right before the XML fun for setting a localized keyboard begins... :-) -- 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: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011, Polytropon wrote: On Tue, 8 Nov 2011 13:33:55 -0700 (MST), Warren Block wrote: On Tue, 8 Nov 2011, Warren Block wrote: On Tue, 8 Nov 2011, Polytropon wrote: And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option DontZap off'' in the ServerFlags section. For at least the most recent Xorg, it's not needed. Can't recall whether it is for the one before that. Nope, just tested and I'm wrong. DontZap Off is needed with X.Org X Server 1.7.7. Sorry about that. I recommend adding the option to ServerLayout and doing away with the extra complication of a ServerFlags section. Good suggestion, the Handbook should be changed according to that if it really works (and is, in my opinion, easier). It's already in there, right before Option DontZap Off. ___ 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
X server and xinit works excellent....almost.
Hi everyone! I'm quite new to BSD and installed it on my old Pentium to try to learn the unixverse from bottom up. My first aim is not just getting the system running for surfing the web or something, not even to be productive, but to understand why and how it runs.(Or else, why it runs not?:) And that, of course, brings me here to write my first query. This (foolish?) wish to understand may also explain why I bother to be curious about something that may be of little, if any, practical concern since my X server display runs well with twm and awesome so far... except for some minor anomalies. My antique system is: Pentium 4, Geforce 2 MM/MX, with (not so antique) FreeBSD-8,2-Release, Xorg - fresh update from ports a couple of days ago (latest version of todays but don't remember the version nr) (...Eh..yes that means that my Pentium is sleeping for the moment and I'm writing this from my laptop with, ehm.. Window...something.) Now the 4 different reasons for my unhappiness: 1. I can´t zap the server with Ctrl-Alt-Backspace. Nothing at all happens. I have checked that it isn't disabled in xorg.conf, and even tried to put in the reverse boolean value there. Not that I couldn't live without zapping, but...when I know about it that it should be there and it is taken fom me I feel an URGE to get the zap! 2. Not surprisingly I was also unable to use the Ctrl-Alt-Keypad+/- for zooming between the different resolution modes. But then I remembered that I had changed configuration from vesa driver to nouveau (with some patch that I downloaded according to instructions in ports). When I switched back to vesa it worked! Still no zapping though, and no higher resolution than 1024x768. I therefore would like to get it to work with the nouveau also. (And to Zap them both! ;) Or are there other ways, using alternative drivers perhaps? (beside upgrading graphics card...) 3. When I started the X server manually, and just giving the vtXX option (without starting any client) the system went black and didn't respond. I couldn't zap it (as you know), but I couldn't even resort to the console with Ctrl-Alt-F1 (or any Fn) which otherwise works normally. I had to resort to hardware reset and boot from single user mode. This problem is not present if I just start the server with X :0 and let it choose the tty by itself. Then it works fine to go Ctrl-Alt-F1 and start xterm -display:0 with full functionality. Experimenting with this I discovered that if I started the first way, with option vtXX and the system went black, I actually still could reach the server from my laptop and ssh-login, and start xterm from there. Well in xterm I could just type exit and the X server went down smoothely. 4. Also xinit behaves strangely on my system. It works perfectly with my .xinitrc-script, so that is not the problem. But when I wanted to just start an xterm without a window manager, like xinit xterm [options] it should, according to the book, ignore .xinitrc and go for the options given to it. But it doesn't!! Instead it ignores my wish for a naked xterm (I'm pervert, I know..) and starts up twm in all it's glory as if reading .xinitrc was a craving it couldn't resist (like mine for zap). I had to change the name of .xinitrc so it couldn't find the beauty for it to obey. Then it gave me my xterm. But still no good, because it also tries to start it's own default xterm in the upper left corner. And that one xterm behaves sickly, the cursor is just flimmering and if I type in something it immediately disappears, as if someone was leaning on the backspace. The other xterm (the one that I asked for) has no prompt and while I can write things in there and press return, xterm behaves like it was a text editor simply moving the cursor to next line as if it didn't just receive a command. There is one command though that it responds to, and that is: exit. It wants to go home. This is a funny problem. I guess it is not important, because when used for what it is mostly supposed to do - reading .xinitrc - the program works excellently. But still... I guess 1-2 could be a problem with drivers, 3-4 with X and xinit, but what do I know? Help is very much appreciated! (Well, I guess I don't NEED your help as in *URGENT* and needing food, or even as in needing a screwdriver, because when I get the zap and zoom and naked xinitiated xterm and the tty of my choice, I plan to never or very seldom use them. But I sure WANT your help. And maybe there is some hidden functionality here that is lacking and will show itself a problem later on when trying heavier wms and desktops) I wish you a nice day! /Samuel ___ 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
XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0
Updating ports and source of my FreeBSD 9.0-CURRENT/amd64 host, equipted with a AMD/ATi HD4830 graphics board driven by X11 xf86-video-ati driver (which has been recently update as far as I saw), resulted this morning in an 'un-login-able' box. I see the xdm-login requester, but after successfully login, I see for a second the desktop (windowmaker), but X11 immediately dies and resets to the xdm requester again. Login from another box and examining the ~/.xsession-errors shows only this entry: --- foo.bar.org being added to access control list XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0 after 29 requests (29 known processed) with 0 events remaining. wmaker warning: got signal 15 - exiting... --- Recompiling xdm and xorg-server ( I did this desperately in the first place) didn't help very much. I do not dare to update all the other boxes in my lab, since I suspect a similar problem since they have all the same or similar hardware (AMD graphics hardware, running X11, running FreeBSD 9.0-CURRENT/amd64). What to do? What changed? Regards, Oliver ___ 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: XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0
on 26/03/2011 11:10 O. Hartmann said the following: Updating ports and source of my FreeBSD 9.0-CURRENT/amd64 host, equipted with a AMD/ATi HD4830 graphics board driven by X11 xf86-video-ati driver (which has been recently update as far as I saw), resulted this morning in an 'un-login-able' box. I see the xdm-login requester, but after successfully login, I see for a second the desktop (windowmaker), but X11 immediately dies and resets to the xdm requester again. Are you subscribed to our x11 list? It's quite low volume. Please see recent messages in its archive, perhaps they could help you. -- Andriy Gapon ___ 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: X server crashes on exit
I use the default install and I don't know what driver to get or how to build it.. but surely if you have the wrong drivers X will not start rather than not stop? X will start, but odd things will happen (such as your mouse not working, distorted resolutions, etc). Installing the Xorg meta-packages will install a bunch of 'default' graphics drivers, such as nv. These drivers are used if the proper driver for your card are not installed. -- Glen Barber 570.328.0318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server crashes on exit
Kevin, As the problem only occurs after I exit X the log file isn't very helpful as to what happens after. The last line is (II) Mouse0: SetupAuto: protocol is SysMouse However it seems to be cycling through various resolution modes before starting, but no errors/warnings except for these lines (II) VESA(0): Total Memory: 495 64KB banks (31680kB) (II) VESA(0): Monitor0: Using hsync range of 30.00-62.00 kHz (II) VESA(0): Monitor0: Using vrefresh range of 55.00-75.00 Hz (II) VESA(0): Monitor0: Using maximum pixel clock of 100.00 MHz (WW) VESA(0): Unable to estimate virtual size (II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 3.0 (II) VESA(0): VESA VBE Total Mem: 31680 kB (II) VESA(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS (II) VESA(0): VESA VBE OEM Software Rev: 2.0 (II) VESA(0): VESA VBE OEM Vendor: S3 Garphics Incorporated. (II) VESA(0): VESA VBE OEM Product: VBE 3.0 (II) VESA(0): VESA VBE OEM Product Rev: Rev 0.0 (WW) VESA(0): Failed to set write-combining range (0xe000,0x1ef) (II) VESA(0): virtual address = 0x28964000, physical address = 0xe000, size = 32440320 (==) VESA(0): Write-combining range (0x0,0x1000) was already clear This last line is repeated about 200 times throughtout the file. Glen, It is an onboard graphics, some sort of VIA chipset. scanpci gives this pci bus 0x cardnum 0x00 function 0x00: vendor 0x1106 device 0x3116 VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge pci bus 0x cardnum 0x01 function 0x00: vendor 0x1106 device 0xb091 VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] pci bus 0x cardnum 0x11 function 0x00: vendor 0x1106 device 0x3177 VIA Technologies, Inc. VT8235 ISA Bridge pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x5333 device 0x8d04 S3 Inc. VT8375 [ProSavage8 KM266/KL266] I use the default install and I don't know what driver to get or how to build it.. but surely if you have the wrong drivers X will not start rather than not stop? Any suggestions? Herman On Fri, Sep 26, 2008 at 4:53 AM, Kevin Kinsey [EMAIL PROTECTED] wrote: Have you looked at the logfiles? (/var/log/Xorg.$n.log) Kevin Kinsey -- Let your conscience be your guide. -- Pope ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server crashes on exit
In case this helps anybody, I fixed the 2 min startup by adding my machine's hostname to /etc/hosts, and the crash problem is fixed by installing the latest xf86-video-savage port. I wonder why the sysinstall doesnt know how to figure this out when installing and build the prot for me? Well anyway that was a good introduction to FreeBSD. On Fri, Sep 26, 2008 at 1:43 AM, Glen Barber [EMAIL PROTECTED]wrote: No, a 2 minute startup of Xorg is not normal. What kind of video card? Do you have the proper drivers for your video card installed? I've noticed on several flavors of Linux with my particular card (nVidia Geforce 8600 or something) that if I do not have the correct nVidia drivers, exiting X results in a system lockup. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X server crashes on exit
Hi, I installed 7.0 from the CD with X. Now this is the first time I ever used FreeBSD or X, I know a bit from linux but I usually use command line only. So when the system finished installing I logged in and typed startx. First time it took over 2 mins (is this normal) but eventually worked, and loaded 3 green terminals and a small clock in the corner. I don't know what this is and the mouse was not working so I tried to exit with the ctrl+alt+backspace but screen went black and the entire system hung - I know this as my remote session aborted and the keyboard led stopped responding too - still no response after 30 mins. I realise that i need a window manager so I tried to install gnome from CD. However it is the same problem and the system hung when I tried to quit back to command line mode. After hours on google I found how to fix the mouse and decide to try building fluxbox wm from the ports. Before starting the X, I ran Xorg -configure and echo exec startfluxbox .xinitrc. So now it starts up properly and works well but still I cannot exit the X. This is a big problem because the machine has no case so I must bend down and touch the reset pins with a penknife :P Also as the disks are not unmounted there are errors and one of the times my user account was deleted, so I had to reinstall the whole system. As I said I have never configure or install an X windows system before, and I was googling for ages. Could anyone give me some idea of how to diagnose and fix this problem? Thanks Herman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server crashes on exit
No, a 2 minute startup of Xorg is not normal. What kind of video card? Do you have the proper drivers for your video card installed? I've noticed on several flavors of Linux with my particular card (nVidia Geforce 8600 or something) that if I do not have the correct nVidia drivers, exiting X results in a system lockup. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server crashes on exit
I should note on my last message, that I specified Linux because some don't install the proper drivers by default. With FreeBSD + Xserver on this box, it was always a habit for me to compile the drivers -- so I never noticed if I would experience this undesired behavior in *BSD. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server crashes on exit
Herman Te wrote: Hi, I installed 7.0 from the CD with X. Now this is the first time I ever used FreeBSD or X, I know a bit from linux but I usually use command line only. So when the system finished installing I logged in and typed startx. First time it took over 2 mins (is this normal) but eventually worked, and loaded 3 green terminals and a small clock in the corner. I don't know what this is and the mouse was not working so I tried to exit with the ctrl+alt+backspace but screen went black and the entire system hung - I know this as my remote session aborted and the keyboard led stopped responding too - still no response after 30 mins. I realise that i need a window manager so I tried to install gnome from CD. However it is the same problem and the system hung when I tried to quit back to command line mode. After hours on google I found how to fix the mouse and decide to try building fluxbox wm from the ports. Before starting the X, I ran Xorg -configure and echo exec startfluxbox .xinitrc. So now it starts up properly and works well but still I cannot exit the X. This is a big problem because the machine has no case so I must bend down and touch the reset pins with a penknife :P Also as the disks are not unmounted there are errors and one of the times my user account was deleted, so I had to reinstall the whole system. As I said I have never configure or install an X windows system before, and I was googling for ages. Could anyone give me some idea of how to diagnose and fix this problem? Thanks Herman Have you looked at the logfiles? (/var/log/Xorg.$n.log) Kevin Kinsey -- Let your conscience be your guide. -- Pope ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kpersonalizer: cannot connect to X server
williamkow schrieb: I am newbie, recently I have installed FreeBSD 6.2-Stable, and manage to configure and display the x window manager (X11) using command startx. and then i run command startkde and I received error message (kpersonalizer: cannot connect to X server) However, if i run command kdm, then it prompt for login screen. I am wondering the command startkde is not correct way to call KDE. please advise me. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] startkde should be fine also... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kpersonalizer: cannot connect to X server
On Thu, 2007-11-29 at 21:25 +0100, Tino Engel wrote: williamkow schrieb: I am newbie, recently I have installed FreeBSD 6.2-Stable, and manage to configure and display the x window manager (X11) using command startx. and then i run command startkde and I received error message (kpersonalizer: cannot connect to X server) However, if i run command kdm, then it prompt for login screen. I am wondering the command startkde is not correct way to call KDE. please advise me. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] startkde should be fine also... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I thought X had to be fully running to start another desktop on top of it, and that was done by xinit. Hence having to put startkde in .xinitrc. I think from the situation you're describing that you're correct, it ought to be running, but try putting startkde in the .xinitrc file and then just running startx. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kpersonalizer: cannot connect to X server
I am newbie, recently I have installed FreeBSD 6.2-Stable, and manage to configure and display the x window manager (X11) using command startx. and then i run command startkde and I received error message (kpersonalizer: cannot connect to X server) However, if i run command kdm, then it prompt for login screen. I am wondering the command startkde is not correct way to call KDE. please advise me. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kpersonalizer: cannot connect to X server
El día Thursday, November 29, 2007 a las 03:19:51PM +0800, williamkow escribió: I am newbie, recently I have installed FreeBSD 6.2-Stable, and manage to configure and display the x window manager (X11) using command startx. and then i run command startkde and I received error message (kpersonalizer: cannot connect to X server) However, if i run command kdm, then it prompt for login screen. I am wondering the command startkde is not correct way to call KDE. please advise me. Thank you. Do in your HOME directory and without having X11 up: $ echo exec startkde ~/.xinitrc $ startx matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gnome X server error
Hi, I got this error message with startx and gnome-session, after i upgrade gnome2 and all my FreeBSD 5.4 ports: [EMAIL PROTECTED] root]$ startx xauth: creating new authority file /root/.serverauth.15016 X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 5.4 i386 [ELF] Current Operating System: FreeBSD h4x0r.Dr_Death 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 03 February 2007 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: Fri Feb 16 17:25:58 2007 (==) Using config file: /etc/X11/xorg.conf _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/AAHS Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/AAHS, removing from list! _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/AGA Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/AGA, removing from list! _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/FS Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/FS, removing from list! _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/Kasr Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/Kasr, removing from list! _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/MCS Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/MCS, removing from list! _FontTransOpen: Unable to Parse address X11BASE/lib/X11/fonts/PORTNAME/Shmookh Could not init font path element X11BASE/lib/X11/fonts/PORTNAME/Shmookh, removing from list! (gnome-session:15039): GLib-GObject-WARNING **: IA__g_object_get_valist: object class `GnomeProgram' has no property named `goption-context' Bonobo-ERROR **: file bonobo-ui-init-gtk.c: line 87 (add_gtk_arg_callback): assertion failed: (init_info != NULL) aborting... (process:15043): Gnome-CRITICAL (recursed) **: gnome_program_get_app_version: assertion `program-_priv-state = APP_PREINIT_DONE' failed aborting... Multiple segmentation faults occurred; can't display error dialog waiting for X server to shut down FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. [EMAIL PROTECTED] root]$ gnome-session (gnome-session:15045): Gtk-WARNING **: cannot open display: [EMAIL PROTECTED] root]$ nothing clear in google. Best Regards, Dr.Death == The Best Security Is Knowledge -- ___ Get your free email from http://bsdmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to connect to remote X server using X -query
Christian Walther [EMAIL PROTECTED] writes: I'm on $ uname -a FreeBSD pixie.alashan.dyndns.org 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #1: Thu Nov 16 17:15:03 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIXIE i386 running $ pkg_info|grep ^xorg-server xorg-server-6.9.0_5 X.Org X server and related programs I set up two of my machines in my network to allow remote logins via xdm and gdm. Both are Linux machines, one is a current Ubuntu release running gdm, the other one a decent Debian/testing running xdm. I'd like to connect to both machines using the command $ X -query ip -fp tcp/ip:7100 The X-Server starts, but it justs sits there, displaying the default background. After a certain period of time the server is restarted, without any error message on the console or in /var/log/Xorg.0.log I checked the xdm/gdm configuration a couple of times, but I can use any other none FreeBSD-host in my network to successfully connect to the Display Manager on both machines. I even checked this with a NetBSD machine. I browsed through the manual and the FAQs, but I didn't find any section that gave me a clue of what is going on. There is no Firewall configured on my FreeBSD machine, and there is no security level set: # sysctl -h kern.securelevel kern.securelevel: -1 X runs just fine when being executed locally, either via startx or via /etc/ttys using xdm. Did I miss something? Hmm. It looks okay so far, but I haven't used this kind of environment in years (so take that with a grain of salt). I would try debugging through the init file (.xinitrc, if the user has one) -- perhaps putting some checkpoints in that script which will write out to local files. -- 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]
Unable to connect to remote X server using X -query
Hi there, I'm on $ uname -a FreeBSD pixie.alashan.dyndns.org 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #1: Thu Nov 16 17:15:03 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIXIE i386 running $ pkg_info|grep ^xorg-server xorg-server-6.9.0_5 X.Org X server and related programs I set up two of my machines in my network to allow remote logins via xdm and gdm. Both are Linux machines, one is a current Ubuntu release running gdm, the other one a decent Debian/testing running xdm. I'd like to connect to both machines using the command $ X -query ip -fp tcp/ip:7100 The X-Server starts, but it justs sits there, displaying the default background. After a certain period of time the server is restarted, without any error message on the console or in /var/log/Xorg.0.log I checked the xdm/gdm configuration a couple of times, but I can use any other none FreeBSD-host in my network to successfully connect to the Display Manager on both machines. I even checked this with a NetBSD machine. I browsed through the manual and the FAQs, but I didn't find any section that gave me a clue of what is going on. There is no Firewall configured on my FreeBSD machine, and there is no security level set: # sysctl -h kern.securelevel kern.securelevel: -1 X runs just fine when being executed locally, either via startx or via /etc/ttys using xdm. Did I miss something? Regards Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login and sound
I'm not sure if sending uncompressed audio data over the network is such a good idea. I know that it works, but what actually happens is that you use a Windows machine to connect to a FreeBSD machine, just to send audio signals back to the Windows host (including all the graphics stuff required to display the applications windows). I'd recommend installing sshd for Xming (if it is available, I'm not familiar with Xming). Install xmms for Xming, too. Know, start your X session as usual, and afterwards ssh (back) to your Xming host. Launch XMMS... What happens is that xmms runs on the Xming machine completely (CPU time is consumed to process audio files, these are sent to the local sound device). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login and sound
Christian Walther wrote: I'm not sure if sending uncompressed audio data over the network is such a good idea. Are you sure that esd does not compress the data? By the way, esd can be used with any audio application. It can emulate a real soundcard. Example follows. On the server (where your real sound card is located): esd -promiscuous -tcp -pubic -port 1500 On the client: esddsp -v -s 192.168.0.13:1500 mpg123 something.mp3 The mpg123 program does not need to have ESD support. The esddsp program creates a fake pcm device before starting mpg123. Best, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login and sound
Nagy László Zsolt wrote: Christian Walther wrote: I'm not sure if sending uncompressed audio data over the network is such a good idea. Are you sure that esd does not compress the data? By the way, esd can be used with any audio application. It can emulate a real soundcard. Example follows. On the server (where your real sound card is located): esd -promiscuous -tcp -pubic -port 1500 On the client: esddsp -v -s 192.168.0.13:1500 mpg123 something.mp3 The mpg123 program does not need to have ESD support. The esddsp program creates a fake pcm device before starting mpg123. Best, Laszlo Why not just use the -C flag with ssh and port forward the port using ssh as well (-L ...)? The only problem would be with sharing the soundcard/port, since I'm not sure if only one user can connect and use esd at one time. However, this can be setup per-user given a little foreknowledge and planning. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X server remote login and sound
Dear mailing list, First of all, thanks you for the thread X server remote login I read it and configured a FreeBSD as follows: # cd /usr/ports/x11/xorg make install clean # cd /usr/ports/x11/wdm make install clean # cd /usr/ports/x11-wm/fluxbox-devel make install clean Then I configured according to: http://www.damnsmallbsd.org/~helio/#GUI After that I fired up wdm, installed Xming from Sourceforge on a windows machine, fired up XLaunch and hey presto remote FreeBSD desktop! Now the follow-up question. How do I squeeze sound through? I want vlc running on the FreeBSD desktop to play sound on the Xming:ed Windows machine. Grateful for any input on the matter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login and sound
Dear mailing list, First of all, thanks you for the thread X server remote login I read it and configured a FreeBSD as follows: # cd /usr/ports/x11/xorg make install clean # cd /usr/ports/x11/wdm make install clean # cd /usr/ports/x11-wm/fluxbox-devel make install clean Then I configured according to: http://www.damnsmallbsd.org/~helio/#GUI After that I fired up wdm, installed Xming from Sourceforge on a windows machine, fired up XLaunch and hey presto remote FreeBSD desktop! Now the follow-up question. How do I squeeze sound through? I want vlc running on the FreeBSD desktop to play sound on the Xming:ed Windows machine. Grateful for any input on the matter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Roger, Not sure if the sound will work via a session from windows, but here is the info that I used to run thin client desktops with sound. First thing you need is a network sound daemon. I used esd, a bit old, but is does have support for other apps. I then set a esd to run in public mode on the server, 'esd --public --nobeeps' ( check man esd for more options ). Once the sound daemon is running, login to the machine, fire up vlc. You should then be able to set the audio output in vlc options to the ip of the machine that is launching the remote session. This did the trick for me. On the other hand if you just want audio, I recommend xmms. It supports many audio formats. It also has the advantage of not needing the additional overhead that vlc does for video. xmms has a plugin for esd that you will need to use to get the audio to work with your window session. Hope this helps, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
On 11 Dec Steve Franks wrote: 2) edit the .Xaccess file in the location specified for xdm in the handbook, add a LISTEN * line. I'll have to look it up in the handbook yet. I hope I will find in there how to prevent xdm from listening to the outside world. I only want to allow my local network to connect to each other. -- http://nagual.nl/ --- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 +++ Solaris 10 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
dick hoogendijk wrote: On 09 Dec Tony Shadwick wrote: On the xserver, if you want it to happen automatically, you would put startx in your .login file. So if you wanted that flag passed, you would place startx -listen_tcp in your .login file. On the client side, you're running an x-client, I presume that gets started from /etc/rc.conf. There's probably something like xorg_enable=YES, and xorg_flags=blah, and you would put it in your xorg_flags statement. Xserver/Xclient side is still a bit confusing to me. What happens is, when I logon to a solaris machine I get a login screen on which I also can logon to remote machines graphicaly. I can even chose from a list there, because these remote machines broadcast themselves? All solaris machines are seen; my FreeBSD machines are not. The latter I want changed, so I can chose to logon to a FreeBSD (remote) machine from my solaris desktop machine. Hope this will clear things up a bit. As another user pointed out; what you're looking for is xdm. xdm is xorg's remote login screen, for lack of a better description; it's what will allow you to directly login to X from other stations, rather than via shell/startx. You might want to take a look at alternatives too - I use kdm, which is KDE's implementation of xdm, allowing you a little easier and a little more control over the login screen/appearence via KDE''s graphical configuration setup, but functionally the same as xdm. -- Nathan Vidican [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
dick hoogendijk wrote: On 09 Dec Tony Shadwick wrote: On the xserver, if you want it to happen automatically, you would put startx in your .login file. So if you wanted that flag passed, you would place startx -listen_tcp in your .login file. On the client side, you're running an x-client, I presume that gets started from /etc/rc.conf. There's probably something like xorg_enable=YES, and xorg_flags=blah, and you would put it in your xorg_flags statement. Xserver/Xclient side is still a bit confusing to me. What happens is, when I logon to a solaris machine I get a login screen on which I also can logon to remote machines graphicaly. I can even chose from a list there, because these remote machines broadcast themselves? All solaris machines are seen; my FreeBSD machines are not. The latter I want changed, so I can chose to logon to a FreeBSD (remote) machine from my solaris desktop machine. Hope this will clear things up a bit. As another user pointed out; what you're looking for is xdm. xdm is xorg's remote login screen, for lack of a better description; it's what will allow you to directly login to X from other stations, rather than via shell/startx. You might want to take a look at alternatives too - I use kdm, which is KDE's implementation of xdm, allowing you a little easier and a little more control over the login screen/appearence via KDE''s graphical configuration setup, but functionally the same as xdm. -- Nathan Vidican [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Not sure if this issue has been resolved, but I found that the 'Xstartup' file is missing from the xorg install of xdm ( /usr/X11R6/lib/X11/xdm ). I found I needed this file to get xdm to properly login. If not, xdm will not allow remote connection to connect. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
I'm a noob myself, but I just did this, so: 1) edit etc/ttys, so the 8th one has xdm and change the no to yes in the second to last field (test by rebooting, should go to an x login, after a slight pasue) ctrl-alt-fn will still get you back to the text terminals. 2) edit the .Xaccess file in the location specified for xdm in the handbook, add a LISTEN * line. 3) edit the xdm-config file, and uncomment that last line that says xdm shouldn't look outside. 4) We use Xming and OpenSSH to connect from windows - configure Xming for the ssh login method, and tell it to run a program, namely gnome-seesion, xfce4-session, or xterm depending on how much X you want. I'll send you my Xming launcher file if you like. Thoughts - make sure you can run startx normally on the machine, and logon once with raw ssh so it can do the key thing and store it - doesn't seem to work from Xming that first time. I'm aauming you are connecting from windows. On another freebsd box, one would assume it's easier thanconfiguring xming. best, Steve On 12/9/06, dick hoogendijk [EMAIL PROTECTED] wrote: I run solaris and FreeBSD. In solaris I can login on a remote machine with an X session. I can't see my freebsd machine though. I have no idea where the config to make this possible resides on FreeBSD. I guess X runs without broadcasting itself on fbsd. How can I change this? -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ Solaris 10 6/06 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X server remote login
I run solaris and FreeBSD. In solaris I can login on a remote machine with an X session. I can't see my freebsd machine though. I have no idea where the config to make this possible resides on FreeBSD. I guess X runs without broadcasting itself on fbsd. How can I change this? -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ Solaris 10 6/06 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
By default in FreeBSD X doesn't listen for TCP requests. To change this do: startx -listen_tcp -Derek At 01:14 PM 12/9/2006, dick hoogendijk wrote: I run solaris and FreeBSD. In solaris I can login on a remote machine with an X session. I can't see my freebsd machine though. I have no idea where the config to make this possible resides on FreeBSD. I guess X runs without broadcasting itself on fbsd. How can I change this? -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ Solaris 10 6/06 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
On Sat, 2006-12-09 at 21:54, Derek Ragona wrote: By default in FreeBSD X doesn't listen for TCP requests. To change this do: startx -listen_tcp Thank you. But can this be made permanent somewhere? I guess the tcp port (6000?) should be made inaccessible to the outside world. -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ Solaris 10 6/06 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X server remote login
I have to apologize, as I've never had x11 start automatically for me anyplace. That said, you need to understand that the server/client relationship for X11 is backwards to what you might expect. The display, keyboard, and mouse are at the x-server side, and the machine you connect to is the X-client. On the xserver, if you want it to happen automatically, you would put startx in your .login file. So if you wanted that flag passed, you would place startx -listen_tcp in your .login file. On the client side, you're running an x-client, I presume that gets started from /etc/rc.conf. There's probably something like xorg_enable=YES, and xorg_flags=blah, and you would put it in your xorg_flags statement. dick hoogendijk wrote: On Sat, 2006-12-09 at 21:54, Derek Ragona wrote: By default in FreeBSD X doesn't listen for TCP requests. To change this do: startx -listen_tcp Thank you. But can this be made permanent somewhere? I guess the tcp port (6000?) should be made inaccessible to the outside world. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nubie can't connect to X-Server
Hello, I'm a newbie trying to install FreeBSD 6.1 on a Dell Inspiron 3800 laptop. I've been reading along in The Complete FreeBSD as I did the install but had a problem when it came to the Configuring X section. Mainly, on the Post Install Configuration menu, there is no option to configure XFree86? After searching, I booted up my machine and got to a prompt, however, when I startkde, I get a constantly scrolling message that reads Cannot connect to the X server. Any suggestions? Thanks everyone for your help. -Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nubie can't connect to X-Server
Assuming you loaded all the X stuff and servers, first run either: xorgcfg or xorgconfig Both are in /usr/X11R6/bin -Derek At 08:07 AM 5/17/2006, Joshua Larkin wrote: Hello, I'm a newbie trying to install FreeBSD 6.1 on a Dell Inspiron 3800 laptop. I've been reading along in The Complete FreeBSD as I did the install but had a problem when it came to the Configuring X section. Mainly, on the Post Install Configuration menu, there is no option to configure XFree86? After searching, I booted up my machine and got to a prompt, however, when I startkde, I get a constantly scrolling message that reads Cannot connect to the X server. Any suggestions? Thanks everyone for your help. -Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Nubie can't connect to X-Server
Thanks for the help, I'll try it when I get home from work tonight. - Josh -Original Message- From: Derek Ragona [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 17, 2006 9:18 AM To: Joshua Larkin; freebsd-questions@freebsd.org Subject: Re: Nubie can't connect to X-Server Assuming you loaded all the X stuff and servers, first run either: xorgcfg or xorgconfig Both are in /usr/X11R6/bin -Derek At 08:07 AM 5/17/2006, Joshua Larkin wrote: Hello, I'm a newbie trying to install FreeBSD 6.1 on a Dell Inspiron 3800 laptop. I've been reading along in The Complete FreeBSD as I did the install but had a problem when it came to the Configuring X section. Mainly, on the Post Install Configuration menu, there is no option to configure XFree86? After searching, I booted up my machine and got to a prompt, however, when I startkde, I get a constantly scrolling message that reads Cannot connect to the X server. Any suggestions? Thanks everyone for your help. -Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by http://www.mailscanner.info/ MailScanner, and is believed to be clean. MailScanner thanks transtec Computers http://www.transtec.co.uk/ for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
x server abort
hi, these days I encountered some problem with my xorg 6.8 server. What I remember now is that after I upgrade my apps by portmanager -u, somehow the X server failed during the launch of some apps, like bzflag and vmd. I checked the xorg.log file, and the only thing I got is: [snip] (WW) fcntl(10, O_ASYNC): Inappropriate ioctl for device *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. [snip] not so much to debug. I am running 6.0-STABLE and all my xorg installation are current as checked by portmanager. The only old install is xorg-fontserver-6.8.2, which has a newer version as 6.8.2_1, thx!! TFC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Restarting X server within KDE?
Many years ago, I ran fvwm2 under Solaris. It actually had a menu option set up whereby you could restart the X server without all your X clients dying. I really wanted this the other week when KDE went weird on me and the mouse pointer disappeared. (After only two months! With this sort of unreliability, open source will never be ready for Joe Consumer.) How does one restart the X server without it killing all the clients? - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restarting X server within KDE?
In the last episode (Jul 26), David Gerard said: Many years ago, I ran fvwm2 under Solaris. It actually had a menu option set up whereby you could restart the X server without all your X clients dying. I really wanted this the other week when KDE went weird on me and the mouse pointer disappeared. (After only two months! With this sort of unreliability, open source will never be ready for Joe Consumer.) How does one restart the X server without it killing all the clients? That's not possible. More likely is that your fvwm2 menu option simply restarted fvwm2 itself. Many window managers have this option plus a couple other launch twm/blackbox/olwm etc entries to shuffle between different window managers. Depending on how you launched KDE, you might be able to just kill it and restart it. If you exec it at the bottom of your .xinitrc though, you would have to have kde reexec itself (since exiting kde would also exit X). I don't know if kde has that option, though. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Setting Up a X Server
Hello everyone; I am looking for information on how to setup a remote X server. This is my setup: Internet. | FreeBSD Gateway (Running Xorg) | 8 Port hub Wireless Base Station | 6 machines, Various Operating Systems What I wish to be able to do is setup the 6 client machines to be able to access the X server running on the gateway. I have looked at the gdm configuration manager, and it allows a option for remote connections, but I am unsure of the exact procedure I would use to connect to this from one of the client systems. The one I am mostly concerned with is my FreeBSD laptop. Do I need to create some 'virtual screens' to enable more than one X session to be run on the machine at once? I have also tried acomplising this using Xvnc, however when I try to start the server I get the error message: [EMAIL PROTECTED] /usr/local/bin/Xvnc Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. I still wish the local X server to be able to be run, so I am unsure how I can proceed. I hope someone can help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to X Server on a FreeBSD Box
On Sun, Apr 17, 2005 at 02:40:15PM +0100, Chris Hodgins wrote: On 4/17/05, Soheil Hassas Yeganeh [EMAIL PROTECTED] wrote: Hi, I start an X server on my FreeBSD box. I want to run some remote X applications from my fedora core 2. So, I have ssh to the fedora box and typed gedit. But it says : (gedit:12438): Gtk-WARNING **: cannot open display: After I had export DISPLAY=freebsdboxip:0.0 it says again: (gedit:12438): Gtk-WARNING **: cannot open display: But I can run freebsd application from my fedora core 2. What is the problem? If you are using ssh anyway, you can tell ssh to do X11 forwarding. Read the man page first as there is some slight security risks involved depending on the way your machine is used. Try this: --- $ ssh -X [EMAIL PROTECTED] With versions of openssh newer than 3.8, you probably want -Y instead of -X. Password: enter password hostname$ xterm --- Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 pgpWXZ9suaRZj.pgp Description: PGP signature
Re: Setting Up a X Server
Mick Walker wrote on Wednesday 20 April 2005 11:06 in the group list.freebsd.questions: Hello everyone; I am looking for information on how to setup a remote X server. This is my setup: Internet. | FreeBSD Gateway (Running Xorg) | 8 Port hub Wireless Base Station | 6 machines, Various Operating Systems What I wish to be able to do is setup the 6 client machines to be able to access the X server running on the gateway. I have looked at the gdm configuration manager, and it allows a option for remote connections, but I am unsure of the exact procedure I would use to connect to this from one of the client systems. The one I am mostly concerned with is my FreeBSD laptop. Do I need to create some 'virtual screens' to enable more than one X session to be run on the machine at once? I have also tried acomplising this using Xvnc, however when I try to start the server I get the error message: [EMAIL PROTECTED] /usr/local/bin/Xvnc Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. I still wish the local X server to be able to be run, so I am unsure how I can proceed. I hope someone can help. You have to startup more than one Xvnc server. I use the wrapper: # vncserver :1 # vncserver :2 etc Then start on the client machine the remote desktop connection It is included in the KDE desktop You can connect to vncservername:1 and vncservername:2 etc... I just tested this and my 100 Mhz pentium got very busy :-) -- Key-ID = A6581435 E-mail address is valid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connecting to X Server on a FreeBSD Box
Hi, I start an X server on my FreeBSD box. I want to run some remote X applications from my fedora core 2. So, I have ssh to the fedora box and typed gedit. But it says : (gedit:12438): Gtk-WARNING **: cannot open display: After I had export DISPLAY=freebsdboxip:0.0 it says again: (gedit:12438): Gtk-WARNING **: cannot open display: But I can run freebsd application from my fedora core 2. What is the problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to X Server on a FreeBSD Box
Soheil Hassas Yeganeh wrote: Hi, I start an X server on my FreeBSD box. I want to run some remote X applications from my fedora core 2. So, I have ssh to the fedora box and typed gedit. But it says : (gedit:12438): Gtk-WARNING **: cannot open display: After I had export DISPLAY=freebsdboxip:0.0 it says again: (gedit:12438): Gtk-WARNING **: cannot open display: But I can run freebsd application from my fedora core 2. What is the problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Try 'xhost +' on your FreeBSD box, then ssh to your FC2 box. Does that help? Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to X Server on a FreeBSD Box
On 4/17/05, Soheil Hassas Yeganeh [EMAIL PROTECTED] wrote: Hi, I start an X server on my FreeBSD box. I want to run some remote X applications from my fedora core 2. So, I have ssh to the fedora box and typed gedit. But it says : (gedit:12438): Gtk-WARNING **: cannot open display: After I had export DISPLAY=freebsdboxip:0.0 it says again: (gedit:12438): Gtk-WARNING **: cannot open display: But I can run freebsd application from my fedora core 2. What is the problem? If you are using ssh anyway, you can tell ssh to do X11 forwarding. Read the man page first as there is some slight security risks involved depending on the way your machine is used. Try this: --- $ ssh -X [EMAIL PROTECTED] Password: enter password hostname$ xterm --- Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
