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
Re: X breaks sound
On Tue, 2013-05-14 at 21:20 +0100, Anton Shterenlikht wrote: Briefly, the sound works fine until X starts. As soon as X starts, sound doesn't work until a reboot. Assumed pulseaudio should be installed, this likely is the culprit, if so, remove it. Hth, Ralf no, I haven't got it installed. 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 breaks sound
On Tue, 2013-05-14 at 21:20 +0100, Anton Shterenlikht wrote: Briefly, the sound works fine until X starts. As soon as X starts, sound doesn't work until a reboot. Assumed pulseaudio should be installed, this likely is the culprit, if so, remove it. Hth, Ralf ___ 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 libraries missing
On Sat, 28 Jan 2012 08:15:27 +0100 Bernt Hansson b...@bananmonarki.se wrote: 2012-01-28 08:06, Adam Vande More skrev: On Sat, Jan 28, 2012 at 12:28 AM, Bernt Hanssonb...@bananmonarki.se wrote: Hello list! Trying to update multimedia/audacious-plugins to some other version 3x. The problem seems to be ! multimedia/audacious-plugins (audacious-plugins-2.5.4_2) (X libraries missing) The error is: Entering directory aosd. In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory Successfully generated dependencies. Successfully compiled aosd.c (plugin). Successfully compiled aosd_osd.c (plugin). Successfully compiled aosd_style.c (plugin). Successfully compiled aosd_trigger.c (plugin). Successfully compiled aosd_ui.c (plugin). Successfully compiled aosd_cfg.c (plugin). In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '** XCompositeCreateRegionFromBord**erClip' Failed to compile ghosd.c (plugin)! gmake[5]: *** [ghosd.plugin.o] Error 1 gmake[4]: *** [all] Error 2 gmake[3]: *** [subdirs] Error 1 gmake[2]: *** [all] Error 2 gmake[1]: *** [subdirs] Error 1 gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120128-**26744-6ymwm0-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=audacious-**plugins-2.5.4_2 UPGRADE_PORT_VER=2.5.4_2 make DEPENDS_TARGET=package ** Fix the problem and try again. But I have xorg libraries installed, xorg-libraries-7.5.1 /usr/ports/x11/libXcomposite Did not work! You also need x11/libXfixes. Save yourself some headaches and just do portmaster libX. That'll make sure all of them are up-to-date. Did you recently upgrade your xorg-server? If so, updating libX* and xf86* is a *must*. HTH Conrad == Building for libXcomposite-0.4.3,1 make all-recursive Making all in src CC Xcomposite.lo In file included from xcompositeint.h:53, from Xcomposite.c:45: ../include/X11/extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory In file included from xcompositeint.h:53, from Xcomposite.c:45: ../include/X11/extensions/Xcomposite.h:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'XCompositeCreateRegionFromBorderClip' Xcomposite.c:319: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'XCompositeCreateRegionFromBorderClip' *** Error code 1 Stop in /usr/home/bernt/disk8/ports/x11/libXcomposite/work/libXcomposite-0.4.3/src. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/x11/libXcomposite/work/libXcomposite-0.4.3. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/x11/libXcomposite/work/libXcomposite-0.4.3. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/x11/libXcomposite ___ 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 -- Conrad J. Sabatier conr...@cox.net ___ 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 libraries missing
2012-01-28 10:31, Conrad J. Sabatier skrev: On Sat, 28 Jan 2012 08:15:27 +0100 Bernt Hanssonb...@bananmonarki.se wrote: 2012-01-28 08:06, Adam Vande More skrev: On Sat, Jan 28, 2012 at 12:28 AM, Bernt Hanssonb...@bananmonarki.se wrote: Hello list! Trying to update multimedia/audacious-plugins to some other version 3x. The problem seems to be ! multimedia/audacious-plugins (audacious-plugins-2.5.4_2) (X libraries missing) The error is: Entering directory aosd. In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory Successfully generated dependencies. Successfully compiled aosd.c (plugin). Successfully compiled aosd_osd.c (plugin). Successfully compiled aosd_style.c (plugin). Successfully compiled aosd_trigger.c (plugin). Successfully compiled aosd_ui.c (plugin). Successfully compiled aosd_cfg.c (plugin). In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '** XCompositeCreateRegionFromBord**erClip' Failed to compile ghosd.c (plugin)! gmake[5]: *** [ghosd.plugin.o] Error 1 gmake[4]: *** [all] Error 2 gmake[3]: *** [subdirs] Error 1 gmake[2]: *** [all] Error 2 gmake[1]: *** [subdirs] Error 1 gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120128-**26744-6ymwm0-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=audacious-**plugins-2.5.4_2 UPGRADE_PORT_VER=2.5.4_2 make DEPENDS_TARGET=package ** Fix the problem and try again. But I have xorg libraries installed, xorg-libraries-7.5.1 /usr/ports/x11/libXcomposite Did not work! You also need x11/libXfixes. Save yourself some headaches and just do portmaster libX. That'll make sure all of them are up-to-date. Did you recently upgrade your xorg-server? If so, updating libX* and xf86* is a *must*. Thank's for the reply. I got frustrated and did a pkg_delete \* Now I can't build any port, tried python cc -c -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -DNDEBUG -O2 -pipe -fno-strict-aliasing -I. -IInclude -I./../Include -fPIC -DPy_BUILD_CORE -o Modules/python.o ./../Modules/python.c cc -pthread -Wl,--export-dynamic -o python Modules/python.o -L. -lpython2.7 -lutil -lm cc -c -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -DNDEBUG -O2 -pipe -fno-strict-aliasing -I. -IInclude -I./../Include -DPy_BUILD_CORE -o Modules/python.o ./../Modules/python.c install -o root -g wheel -m 444 ./../Tools/gdb/libpython.py python-gdb.py [: not foundthis error pops up with any port ã²çW?: not foundsame with this one install: 1: Syntax error: word unexpected (expecting )) install: 5: Syntax error: Error in command substitution *** Error code 2 1 error *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python27. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python27. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python. I get the same error after a portsnap 20120128 15:30 CET ___ 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 libraries missing
On Sat, 28 Jan 2012 15:36:35 +0100 Bernt Hansson b...@bananmonarki.se wrote: 2012-01-28 10:31, Conrad J. Sabatier skrev: On Sat, 28 Jan 2012 08:15:27 +0100 Bernt Hanssonb...@bananmonarki.se wrote: 2012-01-28 08:06, Adam Vande More skrev: On Sat, Jan 28, 2012 at 12:28 AM, Bernt Hanssonb...@bananmonarki.se wrote: Hello list! Trying to update multimedia/audacious-plugins to some other version 3x. The problem seems to be ! multimedia/audacious-plugins (audacious-plugins-2.5.4_2) (X libraries missing) The error is: Entering directory aosd. In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory Successfully generated dependencies. Successfully compiled aosd.c (plugin). Successfully compiled aosd_osd.c (plugin). Successfully compiled aosd_style.c (plugin). Successfully compiled aosd_trigger.c (plugin). Successfully compiled aosd_ui.c (plugin). Successfully compiled aosd_cfg.c (plugin). In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '** XCompositeCreateRegionFromBord**erClip' Failed to compile ghosd.c (plugin)! gmake[5]: *** [ghosd.plugin.o] Error 1 gmake[4]: *** [all] Error 2 gmake[3]: *** [subdirs] Error 1 gmake[2]: *** [all] Error 2 gmake[1]: *** [subdirs] Error 1 gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120128-**26744-6ymwm0-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=audacious-**plugins-2.5.4_2 UPGRADE_PORT_VER=2.5.4_2 make DEPENDS_TARGET=package ** Fix the problem and try again. But I have xorg libraries installed, xorg-libraries-7.5.1 /usr/ports/x11/libXcomposite Did not work! You also need x11/libXfixes. Save yourself some headaches and just do portmaster libX. That'll make sure all of them are up-to-date. Did you recently upgrade your xorg-server? If so, updating libX* and xf86* is a *must*. Thank's for the reply. I got frustrated and did a pkg_delete \* That's just a wee tad on the drastic side, isn't it? You must have been quite beside yourself at the time. :-) Now I can't build any port, tried python cc -c -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -DNDEBUG -O2 -pipe -fno-strict-aliasing -I. -IInclude -I./../Include -fPIC -DPy_BUILD_CORE -o Modules/python.o ./../Modules/python.c cc -pthread -Wl,--export-dynamic -o python Modules/python.o -L. -lpython2.7 -lutil -lm cc -c -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -DNDEBUG -O2 -pipe -fno-strict-aliasing -I. -IInclude -I./../Include -DPy_BUILD_CORE -o Modules/python.o ./../Modules/python.c install -o root -g wheel -m 444 ./../Tools/gdb/libpython.py python-gdb.py [: not foundthis error pops up with any port ã²çW?: not foundsame with this one install: 1: Syntax error: word unexpected (expecting )) install: 5: Syntax error: Error in command substitution *** Error code 2 1 error *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python27. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python27. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/lang/python. I get the same error after a portsnap 20120128 15:30 CET Looks like either you've somehow managed to bork up your /bin directory, or you're lacking /bin in your PATH. Just what exactly have you been up to lately, young man? :-) No, seriously, '[' *should* be found under /bin. It's actually a hard link to 'test' in the same directory. If it's missing, you can recreate it (provided that 'test' still exists). (As root, of course): cd /bin ln test [ Hopefully, that should get you back on track. HTH, Conrad -- Conrad J. Sabatier conr...@cox.net ___ 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 libraries missing
2012-01-28 16:13, Conrad J. Sabatier skrev: Thank's for the reply. I got frustrated and did a pkg_delete \* That's just a wee tad on the drastic side, isn't it? Well, frustration craves drastic measures. You must have been quite beside yourself at the time. :-) It was friday! Looks like either you've somehow managed to bork up your /bin directory, or you're lacking /bin in your PATH. Just what exactly have you been up to lately, young man? :-) Well, to much it seems. No, seriously, '[' *should* be found under /bin. It's actually a hard link to 'test' in the same directory. If it's missing, you can recreate it (provided that 'test' still exists). (As root, of course): cd /bin ln test [ Hopefully, that should get you back on track. I'm back on track. Did some pkg_add -r program Now it seems to work again, at least portupgrade -aiR Thank you Conrad for your help. Have a nice weekend. ___ 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 libraries missing
On Sat, Jan 28, 2012 at 12:28 AM, Bernt Hansson b...@bananmonarki.se wrote: Hello list! Trying to update multimedia/audacious-plugins to some other version 3x. The problem seems to be ! multimedia/audacious-plugins (audacious-plugins-2.5.4_2) (X libraries missing) The error is: Entering directory aosd. In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory Successfully generated dependencies. Successfully compiled aosd.c (plugin). Successfully compiled aosd_osd.c (plugin). Successfully compiled aosd_style.c (plugin). Successfully compiled aosd_trigger.c (plugin). Successfully compiled aosd_ui.c (plugin). Successfully compiled aosd_cfg.c (plugin). In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:49:35: error: X11/extensions/Xfixes.h: No such file or directory In file included from ghosd.c:21: /usr/local/include/X11/**extensions/Xcomposite.h:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '** XCompositeCreateRegionFromBord**erClip' Failed to compile ghosd.c (plugin)! gmake[5]: *** [ghosd.plugin.o] Error 1 gmake[4]: *** [all] Error 2 gmake[3]: *** [subdirs] Error 1 gmake[2]: *** [all] Error 2 gmake[1]: *** [subdirs] Error 1 gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**multimedia/audacious-plugins. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120128-**26744-6ymwm0-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=audacious-**plugins-2.5.4_2 UPGRADE_PORT_VER=2.5.4_2 make DEPENDS_TARGET=package ** Fix the problem and try again. But I have xorg libraries installed, xorg-libraries-7.5.1 /usr/ports/x11/libXcomposite -- Adam Vande More ___ 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: 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
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: 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
Re: X on Xterminals but not on console
It is not so clear .. My problem is: My FreeBSD is a VMware Virtual machine, for 2 years. When connecting to that machine via vSphere client, I get a KDM login window and via Ctrl-Alt-F1 can switch to a console prompt Well, that *was* possible .. Since the last reboot, Ctrl-Alt-F1 (F2, .. F8) doesn't do anything anymore... Can't understand why, it always worked in the past? I have an Tektronix X-terminal, the software running on it allows me to enter my freesbd-machine hostname, then gives me a KDM login window. If my 'console' login (via VMware's vSphere) could be made NOT be a KDM graphical login, and my Xterminal still giving me a KDM login, this would be a workarround (no need to do Ctrl-Alt-F1 on Xterminal), [ and even a better solution, since I do never need graphical environment when connecting to the console ] How can I make the login different for console and other logins? OR: HOW can I solve the Ctrl-Alt-F1 problem? The setup in my Freebsd is: I have in /etc/rc.conf hald_enable=YES dbus_enable=YES I have an /etc/X11/xorg.conf file /etc/ttys has: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure (see below for other parts) at boot this starts a /usr/local/bin/kdm script the hald and dbus deamons are runnng ($ ps -jaxw | grep hald ..) /usr/local/bin/kdm is a shell script first running /usr/local/bin/genkdmconf with config files from /usr/local/share/config/kdm directory but is is unclear if (and how) I can make a difference there between the console and an X-terminal somewhere -- # more /etc/ttys ... # $FreeBSD: src/etc/etc.amd64/ttys,v 1.18.2.1.6.1 2010/12/21 17:09:25 kensmith Exp $ ... console noneunknown off secure # ttyv0 /usr/libexec/getty Pc cons25 on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc cons25 on secure ttyv2 /usr/libexec/getty Pc cons25 on secure ttyv3 /usr/libexec/getty Pc cons25 on secure ttyv4 /usr/libexec/getty Pc cons25 on secure ttyv5 /usr/libexec/getty Pc cons25 on secure ttyv6 /usr/libexec/getty Pc cons25 on secure ttyv7 /usr/libexec/getty Pc cons25 on secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.9600 dialup off secure ttyu1 /usr/libexec/getty std.9600 dialup off secure ttyu2 /usr/libexec/getty std.9600 dialup off secure ttyu3 /usr/libexec/getty std.9600 dialup off secure # Dumb console dcons /usr/libexec/getty std.9600 vt100 off secure # Pseudo terminals ttyp0 nonenetwork ttyp1 nonenetwork ... ttySv nonenetwork - 2011/10/5 David Brodbeck g...@gull.us On Wed, Oct 5, 2011 at 10:59 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, October 05, 2011 a las 12:10:47PM -0400, Lowell Gilbert escribió: n dhert ndhert...@gmail.com writes: FreeBSD-8.2 with Xorg: Is there a way one can specify that your never have X on the console (just the login: prompt) but still have X on any other X-windows termnal (an KDM login window) and graphical environment Sure. It's all in how you configure KDM. In xdm it's set up in the access file; I wouldn't be surprised if kdm were the same. You have login: on console, login, create a file ~/.xinitrc with the lines: twm xterm and then you just say: startx and X11 will come up; ofc you could remove software or create some dirty xorg.conf file which X11 will not let come up; Couldn't you just remove execute permission for the X server binaries? People using X terminals will only be running X clients, since the server will be their terminal. In fact, i think you only need a server installed at all in this situation for dependency reasons. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X on Xterminals but not on console
El día Thursday, October 06, 2011 a las 11:04:33AM +0200, n dhert escribió: It is not so clear .. My problem is: My FreeBSD is a VMware Virtual machine, for 2 years. When connecting to that machine via vSphere client, I get a KDM login window and via Ctrl-Alt-F1 can switch to a console prompt Well, that *was* possible .. Since the last reboot, Ctrl-Alt-F1 (F2, .. F8) doesn't do anything anymore... Can't understand why, it always worked in the past? Try: Ctrl-Alt-SPACE and while Ctrl-ALt still down F1 matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
I tried that already yesterday, with disastreous results: keyboard and mouse completely locked. Closed vsphere and started again, connect to freebsd machine: black window, no reaction to any keyboard of mouse .. 2011/10/6 Matthias Apitz g...@unixarea.de El día Thursday, October 06, 2011 a las 11:04:33AM +0200, n dhert escribió: It is not so clear .. My problem is: My FreeBSD is a VMware Virtual machine, for 2 years. When connecting to that machine via vSphere client, I get a KDM login window and via Ctrl-Alt-F1 can switch to a console prompt Well, that *was* possible .. Since the last reboot, Ctrl-Alt-F1 (F2, .. F8) doesn't do anything anymore... Can't understand why, it always worked in the past? Try: Ctrl-Alt-SPACE and while Ctrl-ALt still down F1 matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
El día Thursday, October 06, 2011 a las 11:51:22AM +0200, n dhert escribió: I tried that already yesterday, with disastreous results: keyboard and mouse completely locked. Closed vsphere and started again, connect to freebsd machine: black window, no reaction to any keyboard of mouse .. Sorry to hear this. I have tested it with VMware 7.x running on my Win7 laptop and FreeBSD 9-CUR (r220692) in a VM. It worked fine for me. File a bug report against vSphere. HIH matthias PS: Please dont top-post -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
Are you sure it is a vSphere problem? I'm not sure: I have used it for 2 years without problem, only with the last reboot (for security update -p3 of FreeBSD 8.2) I got into problems. I update packages every week, maybe something changed in the X packages (I do read /ussr/ports/UPDATING always before updating, can't remember something would have to be done before upgrading) 2011/10/6 Matthias Apitz g...@unixarea.de El día Thursday, October 06, 2011 a las 11:51:22AM +0200, n dhert escribió: I tried that already yesterday, with disastreous results: keyboard and mouse completely locked. Closed vsphere and started again, connect to freebsd machine: black window, no reaction to any keyboard of mouse .. Sorry to hear this. I have tested it with VMware 7.x running on my Win7 laptop and FreeBSD 9-CUR (r220692) in a VM. It worked fine for me. File a bug report against vSphere. HIH matthias PS: Please dont top-post -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
El día Thursday, October 06, 2011 a las 01:15:04PM +0200, n dhert escribió: Are you sure it is a vSphere problem? I'm not sure: I have used it for 2 years without problem, only with the last reboot (for security update -p3 of FreeBSD 8.2) I got into problems. I update packages every week, maybe something changed in the X packages (I do read /ussr/ports/UPDATING always before updating, can't remember something would have to be done before upgrading) (Note: I will from now ignore all top posted questions.) You can watch with xev(1) if the F1 key stroke gets delivered to the X11 server. In my case it is only delivered when I do Ctrl-Alt-Space before. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
(sorry for top posting, but your private address always comes in To: have to remember deleting it..) I can only test on my Xterminal since vsphere connection is a black screen .. on Xterminal, xev : when hitting F1 in the small Event test window, I get answer: KeyPress event, serial 29, synthetic NO, window 0x481, root 0x28, subw 0x0, time 2562153193, (4,176), root:(759,203), state 0x0, keycode 15 (keysym 0xffbe, F1), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 31, synthetic NO, window 0x481, root 0x28, subw 0x0, time 2562153265, (4,176), root:(759,203), state 0x0, keycode 15 (keysym 0xffbe, F1), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False 2011/10/6 Matthias Apitz g...@unixarea.de El día Thursday, October 06, 2011 a las 01:15:04PM +0200, n dhert escribió: Are you sure it is a vSphere problem? I'm not sure: I have used it for 2 years without problem, only with the last reboot (for security update -p3 of FreeBSD 8.2) I got into problems. I update packages every week, maybe something changed in the X packages (I do read /ussr/ports/UPDATING always before updating, can't remember something would have to be done before upgrading) (Note: I will from now ignore all top posted questions.) You can watch with xev(1) if the F1 key stroke gets delivered to the X11 server. In my case it is only delivered when I do Ctrl-Alt-Space before. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ 200†-20††: 10 years war in Afghanistan. Stop it now! ___ 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 on Xterminals but not on console
Hi, In your labserver, do you have a graphical login window at your labserver or not ? I don't want a graphical login, since I can't get anymore to the login prompt via Ctrl Alt F1 In KDM, the config directory is /usr/local/share/config/kdm for kdm window manager, there is no Xservers file, and I can't see any file .. there are Xaccess, Xwilling, Xstartup, Xreset, Xsession files and a large kdmrc file. There are no man pages for kdm, kdm-bin, Xaccess, etc... I tried setting ServerCmd= instead of ServerCmd=/usr/local/bin/X -br in the kdmrc file ... Now I only have /usr/local/bin/kdm-bin running, not /usr/local/bin/X Am I right to believe the primary role of a local X server (local= on labserver) is to have a graphical environment on that labserver machine ? 2011/10/6 Manolis Kiagias son...@otenet.gr On 5/10/2011 1:33 μμ, n dhert wrote: FreeBSD-8.2 with Xorg: Is there a way one can specify that your never have X on the console (just the login: prompt) but still have X on any other X-windows termnal (an KDM login window) and graphical environment I've got a lab that uses XDMCP and X-terminals and I don't run X on the server. I am using XDM and have commented out the following line in /usr/local/lib/X11/xdm/**Xservers: # :0 local /usr/local/bin/X :0 It might be something similar for KDM that will allow it to listen for remote connections but not run locally. ___ 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 on Xterminals but not on console
On 6/10/2011 6:24 μμ, n dhert wrote: Hi, In your labserver, do you have a graphical login window at your labserver or not ? I don't want a graphical login, since I can't get anymore to the login prompt via Ctrl Alt F1 No graphical login. My lab server stops at the console login prompt. In KDM, the config directory is /usr/local/share/config/kdm for kdm window manager, there is no Xservers file, and I can't see any file .. there are Xaccess, Xwilling, Xstartup, Xreset, Xsession files and a large kdmrc file. There are no man pages for kdm, kdm-bin, Xaccess, etc... I tried setting ServerCmd= instead of ServerCmd=/usr/local/bin/X -br in the kdmrc file ... Now I only have /usr/local/bin/kdm-bin running, not /usr/local/bin/X Don't really know how KDM handles this. You could however - as a last resort - disable KDM and use xdm as your login manager. It is a bit rough (see login screens here http://www.flickr.com/photos/sonic2000gr/5033230929/in/set-72157625053818002) but it can start up any GUI using a simple .xsession file (xdm is not installed along with X but it is a very small port, x11/xdm). Am I right to believe the primary role of a local X server (local= on labserver) is to have a graphical environment on that labserver machine ? Yes, absolutely. There is no need to run a GUI on the lab server. It's a waste of CPU cycles and memory. ___ 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 on Xterminals but not on console
n dhert ndhert...@gmail.com writes: FreeBSD-8.2 with Xorg: Is there a way one can specify that your never have X on the console (just the login: prompt) but still have X on any other X-windows termnal (an KDM login window) and graphical environment Sure. It's all in how you configure KDM. In xdm it's set up in the access file; I wouldn't be surprised if kdm were the same. ___ 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 on Xterminals but not on console
El día Wednesday, October 05, 2011 a las 12:10:47PM -0400, Lowell Gilbert escribió: n dhert ndhert...@gmail.com writes: FreeBSD-8.2 with Xorg: Is there a way one can specify that your never have X on the console (just the login: prompt) but still have X on any other X-windows termnal (an KDM login window) and graphical environment Sure. It's all in how you configure KDM. In xdm it's set up in the access file; I wouldn't be surprised if kdm were the same. You have login: on console, login, create a file ~/.xinitrc with the lines: twm xterm and then you just say: startx and X11 will come up; ofc you could remove software or create some dirty xorg.conf file which X11 will not let come up; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ 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 on Xterminals but not on console
On Wed, Oct 5, 2011 at 10:59 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, October 05, 2011 a las 12:10:47PM -0400, Lowell Gilbert escribió: n dhert ndhert...@gmail.com writes: FreeBSD-8.2 with Xorg: Is there a way one can specify that your never have X on the console (just the login: prompt) but still have X on any other X-windows termnal (an KDM login window) and graphical environment Sure. It's all in how you configure KDM. In xdm it's set up in the access file; I wouldn't be surprised if kdm were the same. You have login: on console, login, create a file ~/.xinitrc with the lines: twm xterm and then you just say: startx and X11 will come up; ofc you could remove software or create some dirty xorg.conf file which X11 will not let come up; Couldn't you just remove execute permission for the X server binaries? People using X terminals will only be running X clients, since the server will be their terminal. In fact, i think you only need a server installed at all in this situation for dependency reasons. ___ 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 resolution
On 11/17/10 01:15, Warren Block wrote: It sounds like the EDID information isn't always working. Check your video cable to see if a pin is bent over, or try a different one. I guess it's working too much! :-D How does X know 2048x1536 is a valid resolution otherwise? Why would it override my settings? I've got this in my xorg.conf: Section Screen Identifier SyncMaster Device Card0 Monitor SyncMaster SubSection Display Viewport 0 0 Depth 32 Modes 1600x1200 EndSubSection EndSection 32 is not a valid depth, according to xorg.conf(5). Right: I changed that to 24 and this seemed to do the trick! Still wondering... it must have been there for eons, yet it started misbehaving only a week ago... Well, it works now! :-) What is the monitor? A Samsung SyncMaster 1200NF (http://www.neoseeker.com/Articles/Hardware/Reviews/samsung1200nf/). Thanks a lot for your help! bye av. ___ 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 resolution
On Tue, 16 Nov 2010, Andrea Venturoli wrote: Hello. I've configured my X to use a 1600x1200 resolution (or so I thought...). It used to work until the last X.Org upgrade; after that it *usually* worked: very rarely it would start at 2048x1536, but a couple of Ctrl-Alt-Backspace was normally enough. Since a couple of day, it always start at 2048x1536, and there is no way to get 1600x1200 unless I login and change resolution afterwards (which is however enought to mess all my KDE fonts up). It sounds like the EDID information isn't always working. Check your video cable to see if a pin is bent over, or try a different one. I've got this in my xorg.conf: Section Screen Identifier SyncMaster Device Card0 MonitorSyncMaster SubSection Display Viewport 0 0 Depth 32 Modes 1600x1200 EndSubSection EndSection 32 is not a valid depth, according to xorg.conf(5). Of course I can provide full xorg.conf and Xorg.0.log, but they are quite long... xorg.conf is usually not a problem. Log files can be posted on the web somewhere, like pastebin.com. Card is a Radeon HD 4200. What is the monitor? ___ 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 not responding
On Tuesday 22 June 2010 19:52:54 Andy Balholm wrote: I am having a problem with Xorg under FreeBSD 8.0 RELEASE and 8.1 RC1: When I type startx, the X server starts, and some xterm windows open, but it will not respond to keyboard or mouse input. The mouse pointer won't move, and the only keyboard input that does anything is CTRL-ALT-F1 etc. to switch virtual terminals. If I install FreeBSD 7.1, which installs Xorg straight from the installation CD, it works fine. Under version 8, I've tried installing from ports and packages, and I get this problem. When I first had this problem, I was running it under VirtualBox, so I thought maybe it was because VirtualBox's FreeBSD support is incomplete. But now I've tried it on real PC hardware, and I have the same problem. Obviously some people must be running X under FreeBSD 8, so I must be doing something wrong in my installation or configuration, but I can't guess what it is. Andy Balholm (509) 276-2065 a...@balholm.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Here it looks like you have made some mistakes in the configuring file for X. You did not mention that you have configured it. After X has been installed you must go into the X configuration file and configure your keyboard and mouse etc for use with it. When I installed X on my version 7 BSD I had to use some time tuning this file so X would work properly. The file gives you alternatives like which language keyboard you use and how your mouse works and other settings. Regards Richard Farnes ___ 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 not responding
On 6/22/10 1:52 PM, Andy Balholm wrote: I am having a problem with Xorg under FreeBSD 8.0 RELEASE and 8.1 RC1: When I type startx, the X server starts, and some xterm windows open, but it will not respond to keyboard or mouse input. The mouse pointer won't move, and the only keyboard input that does anything is CTRL-ALT-F1 etc. to switch virtual terminals. If I install FreeBSD 7.1, which installs Xorg straight from the installation CD, it works fine. Under version 8, I've tried installing from ports and packages, and I get this problem. When I first had this problem, I was running it under VirtualBox, so I thought maybe it was because VirtualBox's FreeBSD support is incomplete. But now I've tried it on real PC hardware, and I have the same problem. Obviously some people must be running X under FreeBSD 8, so I must be doing something wrong in my installation or configuration, but I can't guess what it is. Try adding the following to xorg.conf: Section ServerFlags option AllowEmptyInput off option AutoAddDevices off EndSection Regards, -- Glen Barber ___ 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 not responding
On Tue, 22 Jun 2010, Andy Balholm wrote: I am having a problem with Xorg under FreeBSD 8.0 RELEASE and 8.1 RC1: When I type startx, the X server starts, and some xterm windows open, but it will not respond to keyboard or mouse input. The mouse pointer won't move, and the only keyboard input that does anything is CTRL-ALT-F1 etc. to switch virtual terminals. Enable dbus and hal in rc.conf as shown here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html If you want to use X without hal for input device detection, add Option AutoAddDevices Off to the ServerLayout section. Do not set the AllowEmptyInput option, it is unnecessary and problematic. Or you can configure the xorg-server port without hal. ___ 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 not responding
Thanks. That fixed it. I guess I should have read the handbook more. Andy Balholm (509) 276-2065 a...@balholm.com On Jun 22, 2010, at 12:46 PM, Warren Block wrote: On Tue, 22 Jun 2010, Andy Balholm wrote: I am having a problem with Xorg under FreeBSD 8.0 RELEASE and 8.1 RC1: When I type startx, the X server starts, and some xterm windows open, but it will not respond to keyboard or mouse input. The mouse pointer won't move, and the only keyboard input that does anything is CTRL-ALT-F1 etc. to switch virtual terminals. Enable dbus and hal in rc.conf as shown here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html If you want to use X without hal for input device detection, add Option AutoAddDevices Off to the ServerLayout section. Do not set the AllowEmptyInput option, it is unnecessary and problematic. Or you can configure the xorg-server port without hal. ___ 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 is broken after upgrade
Jamie Griffin wrote: If you have moused enabled, you can select text with the left mouse button, and insert text with the middle mouse button. If you don't have a middle mouse button, press the wheel down. If you don't have a wheel, press the left and the right mouse button at the same time. Thanks for the tip, i didn't know I could do that. According to the error message, mentioning /usr/local/lib/xorg/ modules/drivers/intel_drv.so, I would think a modular component of xorg, maybe the drivers component, or a specific kernel module (for Intel video) needs a separate update. I did try recompiling the drivers after i read about a similar issue in a post i found in the archives but that did not fix it. Jamie. I just had a similar issue on a new install In my case it was because X could not find my configuration file. In your first post i notice that your x.org.log lists the default configuration. Double check that your xorg.conf file wasn't deleted or renamed accidentally. Mine was xorg.config instead of xorg.conf. Colin ___ 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 is broken after upgrade
/libexec/ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefinded symbol xf86LoaderReqSymLists Among other things, it means you transcribed the message by hand instead of copy-pasting it :) I did, you're right. With no X i'm working from the console so had no other option. :-) You seem to have a missing shared-library (runtime) dependency. Perhaps one of your X libs didn't get upgraded? What could I do to fix that, do you know? Jamie. -- --- Public Key: 1F50DE41 2010-03-24 Key Fingerprint = B009 05F3 7EEA 6192 6529 25F5 392D DD2C 1F50 DE41 --- pgp0E9XD802I3.pgp Description: PGP signature
Re: X is broken after upgrade
On Mon, May 3, 2010 at 07:57, Jamie Griffin j...@fantomatic.co.uk wrote: /libexec/ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefinded symbol xf86LoaderReqSymLists I have the same problem. I've submitted a PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=146256cat= Joey Mingrone ___ 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 is broken after upgrade
A little sidenote, maybe useful for further debugging: On Mon, 3 May 2010 11:57:08 +0100, Jamie Griffin j...@fantomatic.co.uk wrote: /libexec/ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefinded symbol xf86LoaderReqSymLists Among other things, it means you transcribed the message by hand instead of copy-pasting it :) I did, you're right. With no X i'm working from the console so had no other option. :-) If you have moused enabled, you can select text with the left mouse button, and insert text with the middle mouse button. If you don't have a middle mouse button, press the wheel down. If you don't have a wheel, press the left and the right mouse button at the same time. You can easily use two virtual terminals in text mode - one with the error message, the other one with an editor - to copy the error message without needing to use the usual means of output redirection. You seem to have a missing shared-library (runtime) dependency. Perhaps one of your X libs didn't get upgraded? What could I do to fix that, do you kno According to the error message, mentioning /usr/local/lib/xorg/ modules/drivers/intel_drv.so, I would think a modular component of xorg, maybe the drivers component, or a specific kernel module (for Intel video) needs a separate update. -- 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 is broken after upgrade
If you have moused enabled, you can select text with the left mouse button, and insert text with the middle mouse button. If you don't have a middle mouse button, press the wheel down. If you don't have a wheel, press the left and the right mouse button at the same time. Thanks for the tip, i didn't know I could do that. According to the error message, mentioning /usr/local/lib/xorg/ modules/drivers/intel_drv.so, I would think a modular component of xorg, maybe the drivers component, or a specific kernel module (for Intel video) needs a separate update. I did try recompiling the drivers after i read about a similar issue in a post i found in the archives but that did not fix it. Jamie. pgpYnXvVJva3r.pgp Description: PGP signature
Re: X is broken after upgrade
When it crashes, i've noticed another error that shows on the console: /libexec/ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefinded symbol xf86LoaderReqSymLists ... not sure what that means exactly, any ideas? -- --- Public Key: 1F50DE41 2010-03-24 Key Fingerprint = B009 05F3 7EEA 6192 6529 25F5 392D DD2C 1F50 DE41 --- pgp07dal2NEzk.pgp Description: PGP signature
Re: X is broken after upgrade
Jamie Griffin j...@fantomatic.co.uk wrote: When it crashes, i've noticed another error that shows on the console: /libexec/ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefinded symbol xf86LoaderReqSymLists ^^ ... not sure what that means exactly, any ideas? Among other things, it means you transcribed the message by hand instead of copy-pasting it :) You seem to have a missing shared-library (runtime) dependency. Perhaps one of your X libs didn't get upgraded? ___ 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 -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Sun, Dec 20, 2009 at 10:10:10PM +, Anton Shterenlikht wrote: On Sun, Dec 20, 2009 at 04:00:05PM +0100, Marius Strobl wrote: On Sat, Dec 19, 2009 at 09:48:03PM +, Anton Shterenlikht wrote: I've built X without hal, but get this error on X -configure: Actually when running `X -configure` or when trying to use the resulting /root/xorg.conf.new? This looks more like an error in the configuration file and the results returned by google for this failure message suggest that this can be due to the server not being able to load a configured module. Anyway, I'd try to use the resulting xorg.conf.new and if that fails manually checking its contents and removing unnecessary and unavailable stuff like DRI for example. yes, on 'X -configure'. Removing modules doesn't help. and then on 'X -config ./xorg.conf.new': Could you please make that xorg.conf.new available somewhere? Marius ___ 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 -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Sun, Dec 20, 2009 at 11:20:12PM +0100, Marius Strobl wrote: On Sun, Dec 20, 2009 at 10:10:10PM +, Anton Shterenlikht wrote: On Sun, Dec 20, 2009 at 04:00:05PM +0100, Marius Strobl wrote: On Sat, Dec 19, 2009 at 09:48:03PM +, Anton Shterenlikht wrote: I've built X without hal, but get this error on X -configure: Actually when running `X -configure` or when trying to use the resulting /root/xorg.conf.new? This looks more like an error in the configuration file and the results returned by google for this failure message suggest that this can be due to the server not being able to load a configured module. Anyway, I'd try to use the resulting xorg.conf.new and if that fails manually checking its contents and removing unnecessary and unavailable stuff like DRI for example. yes, on 'X -configure'. Removing modules doesn't help. and then on 'X -config ./xorg.conf.new': Could you please make that xorg.conf.new available somewhere? http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf.new thanks a lot -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'X' vs. 'Mouse'
On Fri, 11 Dec 2009 17:06:01 -0700 (MST), Warren Block wbl...@wonkity.com wrote: Normally, the user shouldn't have to create XML files. If they intended to use another than default english keyboard layout... well, creating the correspoinding XML file as shown in the handbook seemed to be the way to go. In the past, things were centralized in xorg.conf for all the options that would be interesting to the X server: Screen settings, fonts, mouse, keyboard. Now, those settings seem to be non-existent (autodetected) or scattered around into config files of different subsystems. Getting a three button mouse (with middle mouse for wheel functionality) would be an interesting task, too, awaiting my attention soon. :-) The new hal-0.5.13_12 solves some serious problems I had with the earlier version. Maybe problems other people had too, but there haven't been any posts about someone trying HAL again and seeing if it works better now. I'm confident that things like HAL and DBUS make the plug and play experience much better in the future, especially with the big desktop environments (KDE, Gnome, Xfce). Still, I'm a bit surprised that such functionalities have been present in times where HAL and DBUS didn't exist yet... but maybe due to the fact that more and more stuff is accessed via USB, and those USB devices often aren't interested in standards and specifications, the use of HAL and DBUS (and maybe others, such as CUPS) gets more and more unavoidable. -- 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' vs. 'Mouse'
On Sat, 12 Dec 2009, Polytropon wrote: On Fri, 11 Dec 2009 17:06:01 -0700 (MST), Warren Block wbl...@wonkity.com wrote: Normally, the user shouldn't have to create XML files. If they intended to use another than default english keyboard layout... well, creating the correspoinding XML file as shown in the handbook seemed to be the way to go. I had thought about putting a footnote about that, but it was already too long. Also, I don't know about non-English keyboards. Maybe there's a mechanism in hal to detect preferred keyboard layout from the LANG setting. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'X' vs. 'Mouse'
On Sat, 12 Dec 2009 11:50:33 -0700 (MST), Warren Block wbl...@wonkity.com wrote: I had thought about putting a footnote about that, but it was already too long. Also, I don't know about non-English keyboards. Maybe there's a mechanism in hal to detect preferred keyboard layout from the LANG setting. But if LANG isn't set, and LC_* settings differ? I think detecting the keyboard layout from the keyboard itself is not possible at all (how should it?). -- 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' vs. 'Mouse'
2009/12/12 Polytropon free...@edvax.de: On Sat, 12 Dec 2009 11:50:33 -0700 (MST), Warren Block wbl...@wonkity.com wrote: I had thought about putting a footnote about that, but it was already too long. Also, I don't know about non-English keyboards. Maybe there's a mechanism in hal to detect preferred keyboard layout from the LANG setting. But if LANG isn't set, and LC_* settings differ? I think detecting the keyboard layout from the keyboard itself is not possible at all (how should it?). Yeah -- for instance, my LANG and all LC_* variables are set to en_US.UTF-8, so guess what my keyboard layout is? Yes, it is us and cz_qwerty. When I was briefly using HAL, it took a lot of cursing to tell HAL that I want to have a second layout and that I want to be able to switch layouts using a keyboard shortuct. Using xorg.conf it is ridiculously easy. ~ Ondra ___ 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' vs. 'Mouse'
On Fri 2009-12-11 07:30:01 UTC-0500, Carmel (carmel...@hotmail.com) wrote: It is really hard to push the merits of an operating system when you have to give detailed instructions to the potential end user on how to get a mouse to work, when all they have to do in a Win32 based system Last time I had X working was in FreeBSD 6.3, with no dramas. Things may have changed a bit since then, but the general impression I get is that most of Xorg's design decisions are made by Linux developers, and so folks using Xorg in FreeBSD may have to put up with a few compromises to get it to work reliably. To be fair to FreeBSD, I don't think you can really call this as a fault of the OS since Xorg is not part of FreeBSD. is plug it in. I really cannot fathom a seven year old having to modify an XML document to facilitate their playing a How to Spell CD, assuming that they could even get the CD operational. I don't believe FreeBSD is intended to be used (let alone administered) by children. There are Linux distros better suited to children. Edubuntu springs to mind. Ubuntu is pretty much plug-and-play point-and-click on most PCs made in the last few years. Certainly no XML editing required to get Xorg working. Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'X' vs. 'Mouse'
On Fri, 11 Dec 2009, Carmel wrote: Honestly, did the 'X' developers go out of their way to break mouse, and to a lesser degree, keyboard support when upgrading? No, they were trying to upgrade a very old, static system (X11) to support their users. One thing that had been lacking was any support for hotplugging input devices. To implement that, they used HAL, because basically it's the only thing available. So now we have a combination of several unfortunate things: * Users are used to an X11 that has been unchanged for years. * At the same time, xorg users and developers want new features. * The only way to support some of the features is with new software, and HAL was the only thing out there that ran on multiple systems and supported hotplug detection. * HAL is totally unlike X and uses XML config files. * Most xorg development takes place on Linux, where HAL is more common than on FreeBSD. * There are only a couple of FreeBSD developers actively working on the huge and complicated job of porting and supporting xorg. * The first port of xorg-server with HAL support on FreeBSD had a bug. The bug workaround is still being applied by users, long after the bug was fixed, and sometimes--but not always!--it unfixes things. So add all this confusion together, and you end up where we are now. I suspect it seems worse than it really is, since the current xorg will run on a lot of systems without an xorg.conf at all. This forum has been riddled with questions on why their hardware (mouse) has stopped working and how to get it working again. If Microsoft had pulled a bone-headed stunt like this, they would be chastised; however, hardly a word has been uttered regarding the poor choices made by the 'X' development team. The other side of that argument is that Microsoft has supported hotplugging input devices for more than a decade. I question whether they actually tested this product prior to releasing it. I have been following a few forums besides this one and they all report the same problem. I realize that 'HAL' has something to do with this situation also. Perhaps if all the concerned parties would get their acts together this sort of fiasco would not continually happen. You could go to the xorg mailing lists at freedesktop.org and set them straight. They might cheerfully offer to refund your money. You could also offer to help development or testing, either to the FreeBSD developers or xorg. It is really hard to push the merits of an operating system when you have to give detailed instructions to the potential end user on how to get a mouse to work, when all they have to do in a Win32 based system is plug it in. xorg is not FreeBSD, but if you're looking for an integrated GUI operating system based on FreeBSD, PC-BSD seems to be well-regarded. I really cannot fathom a seven year old having to modify an XML document to facilitate their playing a How to Spell CD, assuming that they could even get the CD operational. Normally you'd start by finding out whether they prefer vi or emacs. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'X' vs. 'Mouse'
On Fri, 11 Dec 2009 08:48:36 -0700 (MST) Warren Block wbl...@wonkity.com replied: On Fri, 11 Dec 2009, Carmel wrote: Honestly, did the 'X' developers go out of their way to break mouse, and to a lesser degree, keyboard support when upgrading? No, they were trying to upgrade a very old, static system (X11) to support their users. One thing that had been lacking was any support for hotplugging input devices. To implement that, they used HAL, because basically it's the only thing available. Correct me if I am wrong; however, I believe I read that 'HAL' is dead. Further work on it is not going to happen. If that is correct, are we to expect another fiasco when its replacement comes online. So now we have a combination of several unfortunate things: * Users are used to an X11 that has been unchanged for years. * At the same time, xorg users and developers want new features. * The only way to support some of the features is with new software, and HAL was the only thing out there that ran on multiple systems and supported hotplug detection. * HAL is totally unlike X and uses XML config files. * Most xorg development takes place on Linux, where HAL is more common than on FreeBSD. * There are only a couple of FreeBSD developers actively working on the huge and complicated job of porting and supporting xorg. * The first port of xorg-server with HAL support on FreeBSD had a bug. The bug workaround is still being applied by users, long after the bug was fixed, and sometimes--but not always!--it unfixes things. So add all this confusion together, and you end up where we are now. I suspect it seems worse than it really is, since the current xorg will run on a lot of systems without an xorg.conf at all. This forum has been riddled with questions on why their hardware (mouse) has stopped working and how to get it working again. If Microsoft had pulled a bone-headed stunt like this, they would be chastised; however, hardly a word has been uttered regarding the poor choices made by the 'X' development team. The other side of that argument is that Microsoft has supported hotplugging input devices for more than a decade. I have often wondered what the delay in developing hot-plugging in non-win32 systems was. Worse, HAL requiring the creation of of XML files sort of defeats the entire concept of 'plug play'. I question whether they actually tested this product prior to releasing it. I have been following a few forums besides this one and they all report the same problem. I realize that 'HAL' has something to do with this situation also. Perhaps if all the concerned parties would get their acts together this sort of fiasco would not continually happen. You could go to the xorg mailing lists at freedesktop.org and set them straight. They might cheerfully offer to refund your money. I think you are being overly glib regarding this problem. I stand by my original statement that the parties involved should have tested the final product more thoroughly. As a side note, I officiate youth league sport's programs in my spare time. I don't get paid either. Still, I would never do a crap job just because I was not being financially compensated for my efforts. You could also offer to help development or testing, either to the FreeBSD developers or xorg. I have beta tested applications in the past. I was not aware that Xorg was releasing beta products aimed at FreeBSD. I was under the impression that offerings from Xorg were only ported to FreeBSD after they were released to Linux users. It is really hard to push the merits of an operating system when you have to give detailed instructions to the potential end user on how to get a mouse to work, when all they have to do in a Win32 based system is plug it in. xorg is not FreeBSD, but if you're looking for an integrated GUI operating system based on FreeBSD, PC-BSD seems to be well-regarded. I never meant to infer that FreeBSD == xorg. I really cannot fathom a seven year old having to modify an XML document to facilitate their playing a How to Spell CD, assuming that they could even get the CD operational. Normally you'd start by finding out whether they prefer vi or emacs. Absolutely; anything but OO. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | If one cannot enjoy reading a book over and over again, there is no use in reading it at all. Oscar Wilde ___ 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' vs. 'Mouse'
On Fri, 11 Dec 2009, Carmel wrote: On Fri, 11 Dec 2009 08:48:36 -0700 (MST) Warren Block wbl...@wonkity.com replied: On Fri, 11 Dec 2009, Carmel wrote: No, they were trying to upgrade a very old, static system (X11) to support their users. One thing that had been lacking was any support for hotplugging input devices. To implement that, they used HAL, because basically it's the only thing available. Correct me if I am wrong; however, I believe I read that 'HAL' is dead. Maintenance mode, so more like a zombie, but yes. Further work on it is not going to happen. If that is correct, are we to expect another fiasco when its replacement comes online. Possibly. It depends on the level of integration and testing done before release. The other side of that argument is that Microsoft has supported hotplugging input devices for more than a decade. I have often wondered what the delay in developing hot-plugging in non-win32 systems was. Worse, HAL requiring the creation of of XML files sort of defeats the entire concept of 'plug play'. Normally, the user shouldn't have to create XML files. The new hal-0.5.13_12 solves some serious problems I had with the earlier version. Maybe problems other people had too, but there haven't been any posts about someone trying HAL again and seeing if it works better now. I question whether they actually tested this product prior to releasing it. I have been following a few forums besides this one and they all report the same problem. I realize that 'HAL' has something to do with this situation also. Perhaps if all the concerned parties would get their acts together this sort of fiasco would not continually happen. You could go to the xorg mailing lists at freedesktop.org and set them straight. They might cheerfully offer to refund your money. I think you are being overly glib regarding this problem. I stand by my original statement that the parties involved should have tested the final product more thoroughly. I admit I was thinking of Monty Python on how to rid the world of all known diseases. Point being that more testing is easier to say than do. As a side note, I officiate youth league sport's programs in my spare time. I don't get paid either. Still, I would never do a crap job just because I was not being financially compensated for my efforts. Of course not: you do the best you can with what you've got. As the xorg and FreeBSD developers did and continue to do. You could also offer to help development or testing, either to the FreeBSD developers or xorg. I have beta tested applications in the past. I was not aware that Xorg was releasing beta products aimed at FreeBSD. I was under the impression that offerings from Xorg were only ported to FreeBSD after they were released to Linux users. There's always testing going on before the latest xorg is released on FreeBSD. Sometimes requests for testing are announced on freebsd-x11. It's also possible to contact the developers directly and offer to test. That can be particularly helpful if you have hardware the developers don't. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: x input method question
Steve Franks bahamasfra...@gmail.com writes: [...] I'm actually an english speaker, so the nabi www pages are a little hard to look at for help ;) http://nabi.kldp.net/english.html Sincerely, -- All the members of my family have lived well the last ten years, without danger, without harm. I can't endanger them or their livelihoods out of greed. -- Vito Corleone, Chapter 2, page 74 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED? Re: X - after some time can't lauch new windows, Error: Can't open display
On Thu, Sep 24, 2009 at 04:49:02PM +0100, Anton Shterenlikht wrote: After some time I cannot open any new windows in X, I get No protocol specified Error: Can't open display: :0.0 This is on i386 9.0-current with agp0: Intel 82845M (845M GMCH) SVGA controller on vgapci0 I've xorg-7.4_2, xorg-server-1.6.1,1, xf86-video-intel-2.7.1 and latest hal and dbus. My window manager is mwm (part of open-motif-2.2.3_6). After logging into X via xdm I can launch new windows fine. But after a while, probably several hours, an attempt to launch a new window, i.e. any program that opens a new window, like xterm or xpdf, results in the error message above. The only solution I've found is to logout of xdm and login again. But would be great to solve this properly. I realised that rsync from another box was overwriting $HOME/.Xauthority every time I sinchronised the two machines. After that connection to X server is refused because the data in .Xauthority doesn't match what the X server is expecting (is that so? not sure..). Logging out and on again creates a new .Xauthority file, and all is fine after that. Or perhaps the mechanism I described is not correct.. Anyway it seems to have helped. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X - after some time can't lauch new windows, Error: Can't open display
Anton Shterenlikht me...@bristol.ac.uk wrote: After some time I cannot open any new windows in X, I get No protocol specified Error: Can't open display: :0.0 This is on i386 9.0-current with ... xorg-7.4_2, xorg-server-1.6.1,1, xf86-video-intel-2.7.1 ... After logging into X via xdm I can launch new windows fine. But after a while, probably several hours, an attempt to launch a new window, i.e. any program that opens a new window, like xterm or xpdf, results in the error message above. I have not seen this with local clients, but I _have_ seen something similar from time to time with remote (ssh tunneled) clients. IIRC there was also some kind of squawk about display permissions, as if something related to xauth had gotten messed up. I'm running FreeBSD 6.1 with Xorg 6.9.0; remotes are various Linux and Solaris boxes (and I haven't made note of their versions, nor if the problem happens with some remote versions and not others). Point being that, if we're both seeing the same issue or closely related, it's not of recent origin. ___ 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 errors when I open gvim
On Saturday 25 July 2009 13:38:24 Andrew Falanga wrote: When I open gVim from the command line, I get the following errors: Xlib: extension Generic Event Extension missing on display :0.0. How do I fix this? What's there to fix? The warnings are harmless, search the archives for more info. -- Mel ___ 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 won't start after port upgrade
On Fri, 24 Jul 2009 16:34:35 +0200 Leslie Jensen les...@eskk.nu wrote: I've followed every advice in /usr/ports/UPDATING The portmaster -r jpeg* returns No match. portmaster -r jpeg-7 rebuilds only jpeg-7 no other ports! After this upgrade my X won't start :-( Any hints? Including the log output, it there is any, might be a good idea. Personally, I like 'portmanager' for fixing problems like this. Since you gave no indication of what the problem might be, you could try this for starters. Rebuild the xorg-7.4_2 meta port. Be sure to update you ports tree first, then run: portmanager x11/xorg -p -y -l If X still won't start, you may have to rebuild your window manager as well. -- Jerry ges...@yahoo.com If you could only get that wonderful feeling of accomplishment without having to accomplish anything. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED (Re: X Terminals problem)
The problem was a vimrc copied from a Windows machine to
/usr/local/share/vim/vimrc containing this long statusline:
set statusline=%F%m%r%h%w\ [FORMAT=%{ff}]\ [TYPE=%Y]\ [ASCII=\%03.3b]\
[HEX=\%02.2B]\ [POS=%04l,%04v][%p%%]\ [LEN=%L]
set laststatus=2
Leonardo M. Ramé
http://leonardorame.blogspot.com
- Original Message
From: Leonardo M. Ramé martinr...@yahoo.com
To: freebsd-questions@freebsd.org
Sent: Saturday, July 4, 2009 12:17:48 PM
Subject: X Terminals problem
In my newly installed 7.2-STABLE, any X Terminal (xterm, xfce's Terminal,
eterm,...) is working in the wrong way, specially while I use vim (v. 7.2.209)
in text mode (gvim works ok), it can't scroll, when I try to move the cursor
after the last line on the screen, the status bar shows that the position is
changing, but the screen doesn't scrolls.
Another issue is if I write a long line in the X terminal, instead of adding a
LF at the end and continuing in the next line, it starts at the beginning of
the same line.
My system's data:
uname -a:
FreeBSD inspiron.local 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13
UTC 2009r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Xorg -version:
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.2-PRERELEASE i386
env:
SSH_AGENT_PID=1128
GLADE_PIXMAP_PATH=:
TERM=xterm
SHELL=/bin/bash
WINDOWID=25165828
USER=martin
GLADE_MODULE_PATH=:
SSH_AUTH_SOCK=/tmp/ssh-DCZmP4l6vx/agent.1127
SESSION_MANAGER=local/inspiron.local:/tmp/.ICE-unix/1136,inet6/inspiron.local:54435,inet/inspiron.local:54631
PAGER=/usr/bin/less
FTP_PASSIVE_MODE=YES
MAIL=/var/mail/martin
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/martin/bin
BLOCKSIZE=K
PWD=/usr/home/martin/doc
EDITOR=/usr/local/bin/vim
SHLVL=1
HOME=/home/martin
GTK_PATH=:/usr/local/lib/gtk-2.0
LOGNAME=martin
XDG_DATA_DIRS=/usr/share:/usr/local/share
DBUS_SESSION_BUS_ADDRESS=unix:path=/var/tmp/dbus-g7d508SA96,guid=4488a97081aa02f88f1101ab4a4f700b
WINDOWPATH=9
DISPLAY=:0.0
GLADE_CATALOG_PATH=:
LIBGLADE_MODULE_PATH=:/usr/local/lib/libglade/2.0
COLORTERM=Terminal
_=/usr/bin/env
OLDPWD=/usr/home/martin
Does anyone faced the same problems?, any workaround?.
Leonardo M. Ramé
http://leonardorame.blogspot.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
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 Terminals problem
Hi, On 04 July 2009 pm 23:17:48 Leonardo M. Ramé wrote: In my newly installed 7.2-STABLE, any X Terminal (xterm, xfce's did you install from CD? I upgraded and I did not have this problem. If nothing helps, install 7.1 from CD and do an upgrade via sources. I faced others I have solved afterwards. See my mail regarding dbus and hal. Erich ___ 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 fails to start
On 7/2/09, Da Rock rock_on_the_...@hotmail.com wrote: I'm still having intermittent troubles with getting the freebsd servers seeing my mail servers for my normal maillist subscription, so if I could be cc'd... I'm struggling to get my head around a reasonably severe problem with Xorg - I'm wondering if anyone else is having the same. I've installed Xorg, got it working, started to refine some settings with the wm and other apps for it, and then Xorg refuses to work. My xorg log has only a couple of errors, for reference I'm using the i915 ko with drm: startx: X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.2-RELEASE-p1 i386 ... (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI. Setting master MIT-SHM extension disabled due to lack of kernel support Xorg.0.log: ... drmGetBusid returned '' (II) [drm] DRM interface version 1.0 (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 ... (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): Existing errors found in hardware state. ... MIT-SHM extension disabled due to lack of kernel support ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 Because of my communications issues I've been trying to resolve this myself- with no luck. I've been trying to get some more info on this, and it seems to be a huge bug on a lot of linux distros, but noone has a clear response- it all seems to be a secondary issue to whatever their problem is. SO, I then tried to find out how to debug, and ran into ANOTHER issue. I've rebuilt xorg-server with debug (ccflags='-O0 -g3' as per xorg wiki) with no real success, so then I moved to dri and hit this wall: ../../../src/mesa/main/dispatch.o(.text+0xbb90):../../../src/mesa/glapi/glapitemp.h:4951: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4130): In function `glPointParameteri': ../../../src/mesa/x86/glapi_x86.S:1270: multiple definition of `glPointParameteri' ../../../src/mesa/main/dispatch.o(.text+0xc8e0):../../../src/mesa/glapi/glapitemp.h:5256: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4140): In function `glPointParameteriv': ../../../src/mesa/x86/glapi_x86.S:1271: multiple definition of `glPointParameteriv' ../../../src/mesa/main/dispatch.o(.text+0xc940):../../../src/mesa/glapi/glapitemp.h:5266: first defined here mklib: Installing libGL.so.1 libGL.so in ../../../lib mv: rename libGL.so.1 to ../../../lib/libGL.so.1: No such file or directory gmake[2]: *** [../../../lib/libGL.so] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src/glx/x11' gmake[1]: *** [subdirs] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src' gmake: *** [default] Error 1 *** Error code 1 Stop in /usr/ports/graphics/dri. The various warnings are in the gallon, but my main problem lay with the mklib error. So I tried to simply copy or rename libGL.so(.1) to make it happy (I couldn't find references in the Makefile(s) after half an hour of examination, so I took a little shortcut). It did, but then the gallon of warnings came back to hit me again- but harder, and so I get another stop in the build. So now I can't get dri back, I can't get X working and I'm losing my patience fast! :) What I can't figure out is what started all this in the first place, because it was working. Unfortunately I was in the midst of several things happening at once, so I can't remember if I rebuilt the kernel, upgraded xorg or both before X failed. As far as I can tell that is only secondary at any rate, as I need to prevent this happening again during upgrades/updates whatever. My main questions here are: 1. How do debug Xorg? The debug flags haven't provided much at all so far (maybe I've done it wrong?) You can still use xf86-video-vesa even without dri. Debug flags are useful only if Xorg crashed and dropped core. 2. Why can I get the busid failure and Xorg keep going? How do I force it? Where is this problem lying (kmod, driver, server)? Is it critical? What kernel modules are loaded? What version of server, Mesa, drivers are installed and how are they installed? 3. Is the MIT-SHM error the cause of my problems? (Or a contributor) You are using custom kernel without sysv* modules. Not a good idea for X. 4. What do I need to do about the Mesa library? Is this related to the core issue? Is this a known bug in the port build? Your environment is highly polluted. I've considered manually debugging the drmGetBusID failure, but I don't exactly relish the idea of going through that much code. I could easily follow the procedures in the wiki, but I'd rather go through ports. I've also just completely removed xorg and started again
RE: X fails to start
Date: Thu, 2 Jul 2009 12:16:49 +0200 Subject: Re: X fails to start From: one...@gmail.com To: rock_on_the_...@hotmail.com CC: freebsd-questions@freebsd.org On 7/2/09, Da Rock rock_on_the_...@hotmail.com wrote: I'm still having intermittent troubles with getting the freebsd servers seeing my mail servers for my normal maillist subscription, so if I could be cc'd... I'm struggling to get my head around a reasonably severe problem with Xorg - I'm wondering if anyone else is having the same. I've installed Xorg, got it working, started to refine some settings with the wm and other apps for it, and then Xorg refuses to work. My xorg log has only a couple of errors, for reference I'm using the i915 ko with drm: startx: X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.2-RELEASE-p1 i386 ... (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI. Setting master MIT-SHM extension disabled due to lack of kernel support Xorg.0.log: ... drmGetBusid returned '' (II) [drm] DRM interface version 1.0 (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 ... (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): Existing errors found in hardware state. ... MIT-SHM extension disabled due to lack of kernel support ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 Because of my communications issues I've been trying to resolve this myself- with no luck. I've been trying to get some more info on this, and it seems to be a huge bug on a lot of linux distros, but noone has a clear response- it all seems to be a secondary issue to whatever their problem is. SO, I then tried to find out how to debug, and ran into ANOTHER issue. I've rebuilt xorg-server with debug (ccflags='-O0 -g3' as per xorg wiki) with no real success, so then I moved to dri and hit this wall: ../../../src/mesa/main/dispatch.o(.text+0xbb90):../../../src/mesa/glapi/glapitemp.h:4951: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4130): In function `glPointParameteri': ../../../src/mesa/x86/glapi_x86.S:1270: multiple definition of `glPointParameteri' ../../../src/mesa/main/dispatch.o(.text+0xc8e0):../../../src/mesa/glapi/glapitemp.h:5256: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4140): In function `glPointParameteriv': ../../../src/mesa/x86/glapi_x86.S:1271: multiple definition of `glPointParameteriv' ../../../src/mesa/main/dispatch.o(.text+0xc940):../../../src/mesa/glapi/glapitemp.h:5266: first defined here mklib: Installing libGL.so.1 libGL.so in ../../../lib mv: rename libGL.so.1 to ../../../lib/libGL.so.1: No such file or directory gmake[2]: *** [../../../lib/libGL.so] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src/glx/x11' gmake[1]: *** [subdirs] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src' gmake: *** [default] Error 1 *** Error code 1 Stop in /usr/ports/graphics/dri. The various warnings are in the gallon, but my main problem lay with the mklib error. So I tried to simply copy or rename libGL.so(.1) to make it happy (I couldn't find references in the Makefile(s) after half an hour of examination, so I took a little shortcut). It did, but then the gallon of warnings came back to hit me again- but harder, and so I get another stop in the build. So now I can't get dri back, I can't get X working and I'm losing my patience fast! :) What I can't figure out is what started all this in the first place, because it was working. Unfortunately I was in the midst of several things happening at once, so I can't remember if I rebuilt the kernel, upgraded xorg or both before X failed. As far as I can tell that is only secondary at any rate, as I need to prevent this happening again during upgrades/updates whatever. My main questions here are: 1. How do debug Xorg? The debug flags haven't provided much at all so far (maybe I've done it wrong?) You can still use xf86-video-vesa even without dri. Debug flags are useful only if Xorg crashed and dropped core. Nuts! :( 2. Why can I get the busid failure and Xorg keep going? How do I force it? Where is this problem lying (kmod, driver, server)? Is it critical? What kernel modules are loaded? What version of server, Mesa, drivers are installed and how are they installed? KMods: i915.ko drm.ko Xorg Server: 1.6.1 (in the Xorg log) Mesa (not entirely sure now, was current I believe though- I'll have to wait and see once I can build again...) Drivers: (installed or used?) used intel- xorg ports. Incidentally vesa is available, and is failover in the conf
Re: X fails to start
On 7/2/09, Da Rock rock_on_the_...@hotmail.com wrote: Date: Thu, 2 Jul 2009 12:16:49 +0200 Subject: Re: X fails to start From: one...@gmail.com To: rock_on_the_...@hotmail.com CC: freebsd-questions@freebsd.org On 7/2/09, Da Rock rock_on_the_...@hotmail.com wrote: I'm still having intermittent troubles with getting the freebsd servers seeing my mail servers for my normal maillist subscription, so if I could be cc'd... I'm struggling to get my head around a reasonably severe problem with Xorg - I'm wondering if anyone else is having the same. I've installed Xorg, got it working, started to refine some settings with the wm and other apps for it, and then Xorg refuses to work. My xorg log has only a couple of errors, for reference I'm using the i915 ko with drm: startx: X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.2-RELEASE-p1 i386 ... (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI. Setting master MIT-SHM extension disabled due to lack of kernel support Xorg.0.log: ... drmGetBusid returned '' (II) [drm] DRM interface version 1.0 (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 ... (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): Existing errors found in hardware state. ... MIT-SHM extension disabled due to lack of kernel support ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 Because of my communications issues I've been trying to resolve this myself- with no luck. I've been trying to get some more info on this, and it seems to be a huge bug on a lot of linux distros, but noone has a clear response- it all seems to be a secondary issue to whatever their problem is. SO, I then tried to find out how to debug, and ran into ANOTHER issue. I've rebuilt xorg-server with debug (ccflags='-O0 -g3' as per xorg wiki) with no real success, so then I moved to dri and hit this wall: ../../../src/mesa/main/dispatch.o(.text+0xbb90):../../../src/mesa/glapi/glapitemp.h:4951: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4130): In function `glPointParameteri': ../../../src/mesa/x86/glapi_x86.S:1270: multiple definition of `glPointParameteri' ../../../src/mesa/main/dispatch.o(.text+0xc8e0):../../../src/mesa/glapi/glapitemp.h:5256: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4140): In function `glPointParameteriv': ../../../src/mesa/x86/glapi_x86.S:1271: multiple definition of `glPointParameteriv' ../../../src/mesa/main/dispatch.o(.text+0xc940):../../../src/mesa/glapi/glapitemp.h:5266: first defined here mklib: Installing libGL.so.1 libGL.so in ../../../lib mv: rename libGL.so.1 to ../../../lib/libGL.so.1: No such file or directory gmake[2]: *** [../../../lib/libGL.so] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src/glx/x11' gmake[1]: *** [subdirs] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src' gmake: *** [default] Error 1 *** Error code 1 Stop in /usr/ports/graphics/dri. The various warnings are in the gallon, but my main problem lay with the mklib error. So I tried to simply copy or rename libGL.so(.1) to make it happy (I couldn't find references in the Makefile(s) after half an hour of examination, so I took a little shortcut). It did, but then the gallon of warnings came back to hit me again- but harder, and so I get another stop in the build. So now I can't get dri back, I can't get X working and I'm losing my patience fast! :) What I can't figure out is what started all this in the first place, because it was working. Unfortunately I was in the midst of several things happening at once, so I can't remember if I rebuilt the kernel, upgraded xorg or both before X failed. As far as I can tell that is only secondary at any rate, as I need to prevent this happening again during upgrades/updates whatever. My main questions here are: 1. How do debug Xorg? The debug flags haven't provided much at all so far (maybe I've done it wrong?) You can still use xf86-video-vesa even without dri. Debug flags are useful only if Xorg crashed and dropped core. Nuts! :( 2. Why can I get the busid failure and Xorg keep going? How do I force it? Where is this problem lying (kmod, driver, server)? Is it critical? What kernel modules are loaded? What version of server, Mesa, drivers are installed and how are they installed? KMods: i915.ko drm.ko Xorg Server: 1.6.1 (in the Xorg log) Mesa (not entirely sure now, was current I believe though- I'll have to wait and see once I can build again...) Drivers: (installed or used?) used
