Dell Latitude E6520 Xorg Problems
Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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: Dell Latitude E6520 Xorg Problems
Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.net/ __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org -- Gary Dunn Open Slate Project http://openslate.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: Dell Latitude E6520 Xorg Problems
Nope, but perhaps I found some information, that has me in going in the right direction, this has an integrated intel video card with the core i7, in process of rebuilding world and kernel with Kim's and xorg_new set in make.conf. Sent from my iPad On Jul 18, 2013, at 8:12 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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 -- Gary Dunn Open Slate Project http://openslate.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: Dell Latitude E6520 Xorg Problems
Oops stupid iPAD spell correct Kim's = KMS. Sent from my iPad On Jul 18, 2013, at 8:38 AM, Dean E. Weimer dwei...@dweimer.net wrote: Nope, but perhaps I found some information, that has me in going in the right direction, this has an integrated intel video card with the core i7, in process of rebuilding world and kernel with Kim's and xorg_new set in make.conf. Sent from my iPad On Jul 18, 2013, at 8:12 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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 -- Gary Dunn Open Slate Project http://openslate.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 ___ 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: Dell Latitude E6520 Xorg Problems
I have only gone as far as scanning wifi and it did find all the ssids I expected. System is now recompiling the xorg ports with new kernel and world in place. Sent from my iPad On Jul 18, 2013, at 8:50 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: I am interested in your solution as I plan to more from my old desktop to a notebook, most likely the same Dell you have. Have you gotten as far as WiFi? Dell has a bad reputation for network drivers, especially WiFi. On Jul 18, 2013 3:41 AM, Dean E. Weimer dwei...@dweimer.net wrote: Oops stupid iPAD spell correct Kim's = KMS. Sent from my iPad On Jul 18, 2013, at 8:38 AM, Dean E. Weimer dwei...@dweimer.net wrote: Nope, but perhaps I found some information, that has me in going in the right direction, this has an integrated intel video card with the core i7, in process of rebuilding world and kernel with Kim's and xorg_new set in make.conf. Sent from my iPad On Jul 18, 2013, at 8:12 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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 -- Gary Dunn Open Slate Project http://openslate.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 ___ 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: Dell Latitude E6520 Xorg Problems
I am interested in your solution as I plan to more from my old desktop to a notebook, most likely the same Dell you have. Have you gotten as far as WiFi? Dell has a bad reputation for network drivers, especially WiFi. On Jul 18, 2013 3:41 AM, Dean E. Weimer dwei...@dweimer.net wrote: Oops stupid iPAD spell correct Kim's = KMS. Sent from my iPad On Jul 18, 2013, at 8:38 AM, Dean E. Weimer dwei...@dweimer.net wrote: Nope, but perhaps I found some information, that has me in going in the right direction, this has an integrated intel video card with the core i7, in process of rebuilding world and kernel with Kim's and xorg_new set in make.conf. Sent from my iPad On Jul 18, 2013, at 8:12 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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 -- Gary Dunn Open Slate Project http://openslate.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 ___ 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: Dell Latitude E6520 Xorg Problems
Success X is running after some more playing to verify what works and doesn't I will post back with full config, FYI I did have to re-enable Optimus after rebuilding with KMS. Sent from my iPad On Jul 18, 2013, at 9:04 AM, Dean E. Weimer dwei...@dweimer.net wrote: I have only gone as far as scanning wifi and it did find all the ssids I expected. System is now recompiling the xorg ports with new kernel and world in place. Sent from my iPad On Jul 18, 2013, at 8:50 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: I am interested in your solution as I plan to more from my old desktop to a notebook, most likely the same Dell you have. Have you gotten as far as WiFi? Dell has a bad reputation for network drivers, especially WiFi. On Jul 18, 2013 3:41 AM, Dean E. Weimer dwei...@dweimer.net wrote: Oops stupid iPAD spell correct Kim's = KMS. Sent from my iPad On Jul 18, 2013, at 8:38 AM, Dean E. Weimer dwei...@dweimer.net wrote: Nope, but perhaps I found some information, that has me in going in the right direction, this has an integrated intel video card with the core i7, in process of rebuilding world and kernel with Kim's and xorg_new set in make.conf. Sent from my iPad On Jul 18, 2013, at 8:12 AM, OpenSlate ChalkDust openslatep...@gmail.com wrote: Does it work with the lid open and no additional monitor attached? On Thu, Jul 18, 2013 at 1:43 AM, dweimer dwei...@dweimer.net wrote: Is anyone out there running FreeBSD on a Dell Latitude E6520? I am struggling to Xorg to start, doing the Xorg -configure I get number of created screens does not match number of detected devices I have tried with an external monitor attached and laptop closed, with external monitor attached and laptop open, and with no external monitor. All same results, I did remember to disable the Optimus feature in the bios, even tried enabling it, no change. -- Thanks, Dean E. Weimer http://www.dweimer.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 -- Gary Dunn Open Slate Project http://openslate.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 ___ 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: Dell Latitude E6520 Xorg Problems
On 07/18/2013 9:18 am, Dean E. Weimer wrote:
Success X is running after some more playing to verify what works and
doesn't I will post back with full config, FYI I did have to re-enable
Optimus after rebuilding with KMS.
So far I still haven't been able to get the external monitor working, I
have rebuilt the system using options KMS and NEW_XORG, in the
make.conf, here is the full make.conf file.
# Port Options
WITH_OPENSSL_PORT=YES
WRKDIRPREFIX=/var/ports
PACKAGES=/var/ports/packages
WITH_PKGNG=YES
WITH_KMS=YES
WITH_NEW_XORG=YES
# Build Options
NO_WERROR=
WERROR=
#${.CURDIR:M*/www/squid*} | \
# Use Clang instead of GCC
.if target(index) | \
${.CURDIR:M*/lang/gcc*}
USE_GCC?=4.2
.endif
.if !defined(USE_GCC)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang-cpp
.endif
.endif
# added by use.perl 2013-07-18 17:54:32
PERL_VERSION=5.16.3
Here is the content of /etc/X11/xorg.conf:
Section ServerLayout
Identifier X.org Configured
Screen 0 Screen0 0 0
Screen 1 Screen1 LeftOf Screen0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection
Section Files
ModulePath /usr/local/lib/xorg/modules
FontPath /usr/local/lib/X11/fonts/misc/
FontPath /usr/local/lib/X11/fonts/TTF/
FontPath /usr/local/lib/X11/fonts/OTF/
FontPath /usr/local/lib/X11/fonts/Type1/
FontPath /usr/local/lib/X11/fonts/100dpi/
FontPath /usr/local/lib/X11/fonts/75dpi/
EndSection
Section Module
Load extmod
Load dri2
Load dbe
Load dri
Load record
Load glx
EndSection
Section InputDevice
Identifier Keyboard0
Driver kbd
EndSection
Section InputDevice
Identifier Mouse0
Driver mouse
Option Protocol auto
Option Device /dev/sysmouse
Option ZAxisMapping 4 5 6 7
EndSection
Section Monitor
Identifier Monitor0
VendorName Monitor Vendor
ModelNameMonitor Model
EndSection
Section Monitor
Identifier Monitor1
VendorName Monitor Vendor
ModelNameMonitor Model
EndSection
Section Device
### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz,
### percent: f%
### [arg]: arg optional
#Option SWcursor # [bool]
#Option HWcursor # [bool]
#Option NoAccel # [bool]
#Option ShadowFB # [bool]
#Option UseFBDev # [bool]
#Option Rotate# [str]
#Option VideoKey # i
#Option FlatPanel # [bool]
#Option FPDither # [bool]
#Option CrtcNumber# i
#Option FPScale # [bool]
#Option FPTweak # i
#Option DualHead # [bool]
Identifier Card0
Driver nv
BusID PCI:1:0:0
EndSection
Section Device
### Available Driver options are:-
### Values: i: integer, f: float, bool: True/False,
### string: String, freq: f Hz/kHz/MHz,
### percent: f%
### [arg]: arg optional
#Option NoAccel # [bool]
#Option AccelMethod # str
#Option Backlight # str
#Option DRI # str
#Option ColorKey # i
#Option VideoKey # i
#Option Tiling# [bool]
#Option LinearFramebuffer # [bool]
#Option SwapbuffersWait # [bool]
#Option TripleBuffer # [bool]
#Option XvPreferOverlay # [bool]
#Option HotPlug # [bool]
#Option RelaxedFencing# [bool]
#Option XvMC # [bool]
#Option ZaphodHeads # str
#Option TearFree # [bool]
#Option PerCrtcPixmaps# [bool]
#Option FallbackDebug # [bool]
#Option DebugFlushBatches # [bool]
#Option DebugFlushCaches # [bool]
#Option DebugWait # [bool]
#Option BufferCache # [bool]
Identifier Card1
Driver intel
BusID PCI:0:2:0
EndSection
Section Screen
Identifier Screen0
Device Card1
MonitorMonitor0
SubSection Display
Viewport 0 0
Re: Xorg Problems
On Thu, Aug 26, 2010 at 04:11:27PM -0400, Eitan Adler wrote: I used make install as I had no way of knowing that additional drivers could be selected. Perhaps that should be an option to the sysinstall program when FBSD is initially being installed. Yes, people can't guess what are the names of the drivers, it's in my opinion a problem for this port. I Cced the maintainer. I have a lot on my plate right now so I can't guarantee that I'll solve this soon. Would depending on x11-driver/xorg-drivers instead of requiring VIDEO_DRIVER being set help at all? I intended this port to be used when you require X11 to up and running fast without any overhead. That is why things like xset aren't installed. It is possible to run X11 with the vesa driver even if you can get better performance with a different driver. Having a config menu to select the drivers to be installed (via OPTIONS) is what is missing. -- Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Dear Sir/Madam, Your email was unable reach the intended person that you were sending it to. For more information on our business please click on the following link: [1]Click here for our website We look forward to your continued business in the future. Regards, Webmaster References 1. http://www.xpbargains.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: Xorg Problems
On Sun, Aug 22, 2010 at 07:17:48AM -0700, Fred Boatwright wrote: For x11/xorg-minimal installation you issued the command: make install or make install VIDEO_DRIVER=your_video_driver ? Without the mention of the driver it installs the vesa driver only. This is sub-optimal, an options screen with all existing drivers should be proposed. -- Marc I used make install as I had no way of knowing that additional drivers could be selected. Perhaps that should be an option to the sysinstall program when FBSD is initially being installed. Yes, people can't guess what are the names of the drivers, it's in my opinion a problem for this port. I Cced the maintainer. -- Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
I used make install as I had no way of knowing that additional drivers could be selected. Perhaps that should be an option to the sysinstall program when FBSD is initially being installed. Yes, people can't guess what are the names of the drivers, it's in my opinion a problem for this port. I Cced the maintainer. I have a lot on my plate right now so I can't guarantee that I'll solve this soon. Would depending on x11-driver/xorg-drivers instead of requiring VIDEO_DRIVER being set help at all? I intended this port to be used when you require X11 to up and running fast without any overhead. That is why things like xset aren't installed. It is possible to run X11 with the vesa driver even if you can get better performance with a different driver. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Fred Boatwright f...@blakemfg.com wrote: Until FBSD X is working on the pc I have to use Netscape 4.79 on a Sun running Solaris 2.6 (which I would prefer to keep using if only a modern browser was available) ... If the problems with X on FBSD are limited to the X server (display subsystem), perhaps you can run X clients (such as a recent version of FireFox) on the FBSD box with DISPLAY set to the Solaris box. The simplest way of doing this is to ssh into the FBSD box from an xterm (or rxvt, or whatever) on the Solaris box. Depending on how ssh is set up you may (or may not) need to specify -X to get the X protocol forwarded. Forwarding will result in DISPLAY being set to something like localhost:10.0 in the FBSD shell session, and it should just 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: Xorg Problems
per...@pluto.rain.com wrote: Fred Boatwright f...@blakemfg.com wrote: Until FBSD X is working on the pc I have to use Netscape 4.79 on a Sun running Solaris 2.6 (which I would prefer to keep using if only a modern browser was available) ... If the problems with X on FBSD are limited to the X server (display subsystem), perhaps you can run X clients (such as a recent version of FireFox) on the FBSD box with DISPLAY set to the Solaris box. The simplest way of doing this is to ssh into the FBSD box from an xterm (or rxvt, or whatever) on the Solaris box. Depending on how ssh is set up you may (or may not) need to specify -X to get the X protocol forwarded. Forwarding will result in DISPLAY being set to something like localhost:10.0 in the FBSD shell session, and it should just work. ___ The problem I was having is fixed now. xrdb was hanging for some reason to be fixed later. However, I am very much interested in your suggestion and planned to post some questions about how to do it when I had time to work on it. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
in message 4c70a618.d6d35...@blakemfg.com, wrote Fred Boatwright thusly... The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm ... I don't understand why xterm and xconsole are to be started before the window manager. Window manager is started at the end so that when it exits, it takes all the open programs with it. If you start the window manager in background too ... xrdb ... exec fvwm ... then all you would see is a flash of window opening (and subsequently closing) as no program would be there to block exiting out of X11. You could start any other program in foreground after starting window manager ... xrdb ... fvwm # Exit this xterm, exit out of X11. exec xterm -T 'Die, Die!' You would need to then exit that program so that open files close, other programs die, X11 shuts down, and so on, so forth. - parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sat, Aug 21, 2010 at 07:41:49PM -0700, Fred Boatwright wrote: Warren Block wrote: On Sat, 21 Aug 2010, Warren Block wrote: Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log First notes: You're running the old version of X, 1.6.1. Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. I think the Handbook has a section on adding fonts. While looking for the xorg-minimal that I installed I found a bunch of nVidea drivers in the same directory. Do you think I should install them now or wait. For x11/xorg-minimal installation you issued the command: make install or make install VIDEO_DRIVER=your_video_driver ? Without the mention of the driver it installs the vesa driver only. This is sub-optimal, an options screen with all existing drivers should be proposed. -- Marc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sunday 22 August 2010 06:22:48 Fred Boatwright wrote: Eitan Adler wrote: The actual problem I am having is that startx produces only a completely black screen.  Xorg -config xorg.conf.new -retro  produces the expected grid and mouse pointer.  A .xinitrc file is supposed to start a window manager. Modern X.org installs don't show a default window manager (so a black screen is expected). What is the contents of your .xinitrc file? The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm I have also tried twm. This file was generated from an example in the Handbook. Check if you actually have those programs installed. If not, you need to install these ports: x11/xrdb, x11/xsetroot, x11/xterm, x11/xconsole, x11-wm/fvwm. signature.asc Description: This is a digitally signed message part.
Re: Xorg Problems
On Sat, 21 Aug 2010 21:22:40 -0600 (MDT) Warren Block wbl...@wonkity.com articulated: Those would be the nVidia binary drivers. There's also x11-drivers/xf86-video-nv. I avoid nVidia cards, so someone else will have to comment on those. I came to this party late, so please excuse me if this has been discussed. 1) Ha the user installed the latest nVidia driver from ports: Port: nvidia-driver-195.36.15 Path: /usr/ports/x11/nvidia-driver Info: NVidia graphics card binary drivers for hardware OpenGL rendering And it accompanying utilities: Port: nvidia-settings-195.36.31 Path: /usr/ports/x11/nvidia-settings Info: Display Control Panel for X NVidia driver Port: nvidia-xconfig-195.36.31 Path: /usr/ports/x11/nvidia-xconfig Info: Tool to manipulate X configuration files for the NVidia driver And installed a line in the /boot/loader.conf file for this driver: nvidia_load=YES # nVidia video driver 2) After doing the above, if not done previously, reboot the system. 3) Move to the /etc/X11 directory and run as root: nvidia-xconfig The man nvidia-xconfig file will supply all the details. You really should not run it with any command line arguments the first time. 4) Now start 'xorg and run as root: nvidia-settings. That should complete the process. You may have to reload 'xorg' for all settings to take affect. Please see man nvidia-settings for full details. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ 40 isn't old, if you are a 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: Xorg Problems
Marc Fonvieille wrote: On Sat, Aug 21, 2010 at 07:41:49PM -0700, Fred Boatwright wrote: Warren Block wrote: On Sat, 21 Aug 2010, Warren Block wrote: Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log First notes: You're running the old version of X, 1.6.1. Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. I think the Handbook has a section on adding fonts. While looking for the xorg-minimal that I installed I found a bunch of nVidea drivers in the same directory. Do you think I should install them now or wait. For x11/xorg-minimal installation you issued the command: make install or make install VIDEO_DRIVER=your_video_driver ? Without the mention of the driver it installs the vesa driver only. This is sub-optimal, an options screen with all existing drivers should be proposed. -- Marc I used make install as I had no way of knowing that additional drivers could be selected. Perhaps that should be an option to the sysinstall program when FBSD is initially being installed. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Tijl Coosemans wrote: On Sunday 22 August 2010 06:22:48 Fred Boatwright wrote: Eitan Adler wrote: The actual problem I am having is that startx produces only a completely black screen.  Xorg -config xorg.conf.new -retro  produces the expected grid and mouse pointer.  A .xinitrc file is supposed to start a window manager. Modern X.org installs don't show a default window manager (so a black screen is expected). What is the contents of your .xinitrc file? The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm I have also tried twm. This file was generated from an example in the Handbook. Check if you actually have those programs installed. If not, you need to install these ports: x11/xrdb, x11/xsetroot, x11/xterm, x11/xconsole, x11-wm/fvwm. Those programs are actually installed. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Jerry wrote: On Sat, 21 Aug 2010 21:22:40 -0600 (MDT) Warren Block wbl...@wonkity.com articulated: Those would be the nVidia binary drivers. There's also x11-drivers/xf86-video-nv. I avoid nVidia cards, so someone else will have to comment on those. I came to this party late, so please excuse me if this has been discussed. 1) Ha the user installed the latest nVidia driver from ports: Port: nvidia-driver-195.36.15 Path: /usr/ports/x11/nvidia-driver Info: NVidia graphics card binary drivers for hardware OpenGL rendering And it accompanying utilities: Port: nvidia-settings-195.36.31 Path: /usr/ports/x11/nvidia-settings Info: Display Control Panel for X NVidia driver Port: nvidia-xconfig-195.36.31 Path: /usr/ports/x11/nvidia-xconfig Info: Tool to manipulate X configuration files for the NVidia driver And installed a line in the /boot/loader.conf file for this driver: nvidia_load=YES # nVidia video driver 2) After doing the above, if not done previously, reboot the system. 3) Move to the /etc/X11 directory and run as root: nvidia-xconfig The man nvidia-xconfig file will supply all the details. You really should not run it with any command line arguments the first time. 4) Now start 'xorg and run as root: nvidia-settings. That should complete the process. You may have to reload 'xorg' for all settings to take affect. Please see man nvidia-settings for full details. -- Jerry â?? freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ 40 isn't old, if you are a tree. ___ Hi Jerry, I do not have the driver you suggest on the CD. I have: nividia-driver nividia-driver-173 nividia-driver-71 nividia-driver-96 Which should be used? I was not able to find the version you mentioned with the freebsd website ports search function. Since Xorg -config xorg.conf.new -retro works then I think the default vesa driver should work until the other problems are sorted out. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sun, 22 Aug 2010 07:42:35 -0700 Fred Boatwright f...@blakemfg.com articulated: Hi Jerry, I do not have the driver you suggest on the CD. I have: nividia-driver nividia-driver-173 nividia-driver-71 nividia-driver-96 Which should be used? I was not able to find the version you mentioned with the freebsd website ports search function First, update your ports tree. This is what you are looking for: Port: nvidia-driver-195.36.15 Path: /usr/ports/x11/nvidia-driver Info: NVidia graphics card binary drivers for hardware OpenGL rendering Al;l of the relevant paths, etc. were in the first post I sent regarding this matter. The 173 and other drivers are deprecated and should probably be avoided. If you have one of them installed, do a make_deinstall -dfv nvidia* first before attempting to install the new drive and utilities. If you are still experiencing problems, post back. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ History is the version of past events that people have decided to agree on. Napoleon Bonaparte, Maxims ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sunday 22 August 2010 06:22:48 Fred Boatwright wrote: The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm Is this file executable? signature.asc Description: This is a digitally signed message part.
Re: Xorg Problems
On Sun, Aug 22, 2010 at 07:19:36PM +0200, Tijl Coosemans wrote: On Sunday 22 August 2010 06:22:48 Fred Boatwright wrote: The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm Is this file executable? It doesn't have to be executable but xrdb needs arguments or it just waits for input. My suggestion to Fred: drop the xrdb line in his ~/.xinitrc Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Frank Shute wrote: On Sun, Aug 22, 2010 at 07:19:36PM +0200, Tijl Coosemans wrote: On Sunday 22 August 2010 06:22:48 Fred Boatwright wrote: The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm Is this file executable? It doesn't have to be executable but xrdb needs arguments or it just waits for input. My suggestion to Fred: drop the xrdb line in his ~/.xinitrc Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html Well, some progress has been made! The .xinitrc file is not executable. I found the file on my Sun running Solaris 2.6. That file also does not have execute permissions but it has #!/bin/sh at the beginning. However, that doesn't appear to be needed under FBSD. I tried an empty .Xresources file but that didn't make any difference. Commenting out the xrdb does allow the window manager to start. The .xinitrc file was generated from an example in the man page for xinit, not the Handbook as I earlier stated. So, I can move forward again. Thank you very much for the help. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Warren Block wrote: On Fri, 20 Aug 2010, Fred Boatwright wrote: I am having trouble setting up X similar to a previous posting. I have a new 8.0 installation. Using the Handbook chapter suggested below I waas able to generate and edit an xorg.conf file. It tests ok. I generated a .xinitrc file based on an example in the Handbook. When a user runs startx the screen completely blanks out. It is possible to return to the command line prompt with ctrl-alt-F1 and then ^c. No errors are listed. Where would I look for the problem? [please don't top-post, it makes responding more difficult] Could you show your .xinitrc? Also, the xorg.conf and Xorg.0.log are often useful. Links to those files may be easier to post than the files themselves. When you say the screen is completely blank--is there a mouse pointer? Hello, The screen is completely black. No mouse pointer. When the xorg.conf file is tested using Xorg -conf xorg.conf.new -retro I get the gray grid and the X mouse pointer. Without the -retro I get a totally black screen, no mouse pointer. .xinitrc xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm xorg.conf Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName HP ModelName2009 ModeLine 1600x900 108.0 1600 1624 1704 1800 900 901 904 1000 Option DPMS EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh# [bool] #Option ModeSetClearScreen# [bool] Identifier Card0 Driver vesa VendorName nVidia Corporation BoardName NV44 [GeForce 6200 A-LE] BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 # SubSection Display # Viewport 0 0 # Depth 1 # EndSubSection # SubSection Display # Viewport 0 0 # Depth 4 # EndSubSection # SubSection Display # Viewport 0 0 # Depth 8 # EndSubSection # SubSection Display # Viewport 0 0 # Depth 15 # EndSubSection # SubSection Display # Viewport 0 0 # Depth 16 # EndSubSection SubSection Display Viewport 0 0 Depth 24 Modes 1600x900 EndSubSection EndSection Is there is somewhere I can park the log file that you would have access to? I don't know of any way to provide a link to it here. The log file has warnings that mouse and keyboard are disabled and other places where mouse and keyboard are enabled. However, in the test the mouse works and the keyboard must work as I can return to the command line prompt. I just don't have video. The log file says: (--) using VT number 9. This does not exist in /etc/ttys and I didn't find anywhere in the Handbook chapter that says it needs to be added. The log file generated by Xorg -configure appears to have everything there is to know about the monitor being used. These values were manually put in the xorg.conf file. However, the log file says: (II) VESA(0): Not using mode 1600x900 (no mode of this name) However, the xorg.conf test did work. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On 21/08/2010 18:13:09, Fred Boatwright wrote: The screen is completely black. No mouse pointer. When the xorg.conf file is tested using Xorg -conf xorg.conf.new -retro I get the gray grid and the X mouse pointer. Without the -retro I get a totally black screen, no mouse pointer. Um yes. That's what the '-retro' flag does: reintroduce the grid pattern etc. that lets you confirm X is responsive, rather than the new and really not at all improved behaviour of just throwing up a black screen which is remarkably similar to some common failure modes. Try starting up a window manager or similar. It might be that nothing at all is actually wrong... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Xorg Problems
On Sat, 21 Aug 2010, Fred Boatwright wrote: .xinitrc xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm Before trying a different window manager, try good old twm. xorg.conf Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection If you're running hal, those InputDevice sections aren't needed. Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection These InputDevice definitions are also unnecessary with hal. Section Monitor Identifier Monitor0 VendorName HP ModelName2009 ModeLine 1600x900 108.0 1600 1624 1704 1800 900 901 904 1000 Option DPMS EndSection Modelines are... well, avoid them unless they are required. Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh # [bool] #Option ModeSetClearScreen # [bool] Identifier Card0 Driver vesa VendorName nVidia Corporation BoardName NV44 [GeForce 6200 A-LE] BusID PCI:1:0:0 EndSection The nVidia driver should produce better results than vesa. Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes 1600x900 EndSubSection EndSection Finally, starting with a more common resolution like 1024x768 may help. Get it working first, then polish one thing at a time so you can tell what works. Is there is somewhere I can park the log file that you would have access to? I don't know of any way to provide a link to it here. http://pastebin.com/ is popular. The log file says: (--) using VT number 9. This does not exist in /etc/ttys and I didn't find anywhere in the Handbook chapter that says it needs to be added. xorg creates it automatically. It's the alt-F9 to switch from console to X. The log file generated by Xorg -configure appears to have everything there is to know about the monitor being used. These values were manually put in the xorg.conf file. However, the log file says: (II) VESA(0): Not using mode 1600x900 (no mode of this name) However, the xorg.conf test did work. vesa may not be able to handle that resolution. 1024x768 is a safe starting value. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Hi Matthew, The .xinitrc file starts fvwm. I have not found any error message that would indicate fvwm is not running. One of the common failure modes you mention is probably what I have! Best regards, Fred Matthew Seaman wrote: On 21/08/2010 18:13:09, Fred Boatwright wrote: The screen is completely black. No mouse pointer. When the xorg.conf file is tested using Xorg -conf xorg.conf.new -retro I get the gray grid and the X mouse pointer. Without the -retro I get a totally black screen, no mouse pointer. Um yes. That's what the '-retro' flag does: reintroduce the grid pattern etc. that lets you confirm X is responsive, rather than the new and really not at all improved behaviour of just throwing up a black screen which is remarkably similar to some common failure modes. Try starting up a window manager or similar. It might be that nothing at all is actually wrong... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW Name: signature.asc signature.asc Type: application/pgp-signature Description: OpenPGP digital signature ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Warren Block wrote: On Sat, 21 Aug 2010, Fred Boatwright wrote: .xinitrc xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm Before trying a different window manager, try good old twm. xorg.conf Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection If you're running hal, those InputDevice sections aren't needed. Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection These InputDevice definitions are also unnecessary with hal. Section Monitor Identifier Monitor0 VendorName HP ModelName2009 ModeLine 1600x900 108.0 1600 1624 1704 1800 900 901 904 1000 Option DPMS EndSection Modelines are... well, avoid them unless they are required. Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh # [bool] #Option ModeSetClearScreen # [bool] Identifier Card0 Driver vesa VendorName nVidia Corporation BoardName NV44 [GeForce 6200 A-LE] BusID PCI:1:0:0 EndSection The nVidia driver should produce better results than vesa. Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes 1600x900 EndSubSection EndSection Finally, starting with a more common resolution like 1024x768 may help. Get it working first, then polish one thing at a time so you can tell what works. Is there is somewhere I can park the log file that you would have access to? I don't know of any way to provide a link to it here. http://pastebin.com/ is popular. The log file says: (--) using VT number 9. This does not exist in /etc/ttys and I didn't find anywhere in the Handbook chapter that says it needs to be added. xorg creates it automatically. It's the alt-F9 to switch from console to X. The log file generated by Xorg -configure appears to have everything there is to know about the monitor being used. These values were manually put in the xorg.conf file. However, the log file says: (II) VESA(0): Not using mode 1600x900 (no mode of this name) However, the xorg.conf test did work. vesa may not be able to handle that resolution. 1024x768 is a safe starting value. Hello Warren, I installed twm and changed .xinitrc to run it. I commented out the sections of xorg.conf that you suggested and changed the resolution. I changed the driver from vesa to nVidia but the nVidia driver could not be found and X exited. After restoring vesa I ran the test on xorg.conf -retro and it worked ok. However, startx still produced only a black screen. I was not able to make heads or tails out of the pastebin.com site. Until FBSD X is working on the pc I have to use Netscape 4.79 on a Sun running Solaris 2.6 (which I would prefer to keep using if only a modern browser was available). Netscape doesn't work on most web sites anymore. Is there someplace I could ftp or email the log file? Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sat, 21 Aug 2010, Fred Boatwright wrote: I installed twm and changed .xinitrc to run it. twm should have been part of the xorg install already. I commented out the sections of xorg.conf that you suggested and changed the resolution. I changed the driver from vesa to nVidia but the nVidia driver could not be found and X exited. After restoring vesa I ran the test on xorg.conf -retro and it worked ok. However, startx still produced only a black screen. nVidia is a long story. There are binary drivers provided by nVidia, and there's a limited open-source driver provided by xorg. Someone else is going to have to provide detail. For now, vesa at 1024x768 should be fine. I was not able to make heads or tails out of the pastebin.com site. Until FBSD X is working on the pc I have to use Netscape 4.79 on a Sun running Solaris 2.6 (which I would prefer to keep using if only a modern browser was available). Netscape doesn't work on most web sites anymore. Is there someplace I could ftp or email the log file? If you want to mail it to me, I can put it up temporarily. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On 8/21/10 7:12 PM, Warren Block wrote: I changed the driver from vesa to nVidia but the nVidia driver could not be found and X exited. After restoring vesa I ran the test on xorg.conf -retro and it worked ok. However, startx still produced only a black screen. nVidia is a long story. There are binary drivers provided by nVidia, and there's a limited open-source driver provided by xorg. Someone else is going to have to provide detail. For now, vesa at 1024x768 should be fine. Just curious - why are you using vesa instead of nv (not nVidia)? 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: Xorg Problems
Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Glen Barber wrote: On 8/21/10 7:12 PM, Warren Block wrote: I changed the driver from vesa to nVidia but the nVidia driver could not be found and X exited. After restoring vesa I ran the test on xorg.conf -retro and it worked ok. However, startx still produced only a black screen. nVidia is a long story. There are binary drivers provided by nVidia, and there's a limited open-source driver provided by xorg. Someone else is going to have to provide detail. For now, vesa at 1024x768 should be fine. Just curious - why are you using vesa instead of nv (not nVidia)? 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 Glen, Vesa is what Xorg -configure comes up with. Should the nVidia driver name be nv? Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sat, 21 Aug 2010, Warren Block wrote: Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log First notes: You're running the old version of X, 1.6.1. Something odd is going on with some of the fonts. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Warren Block wrote: On Sat, 21 Aug 2010, Warren Block wrote: Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log First notes: You're running the old version of X, 1.6.1. Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. I think the Handbook has a section on adding fonts. While looking for the xorg-minimal that I installed I found a bunch of nVidea drivers in the same directory. Do you think I should install them now or wait. Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sat, 21 Aug 2010, Fred Boatwright wrote: Warren Block wrote: On Sat, 21 Aug 2010, Warren Block wrote: Log file is at http://wonkity.com/~wblock/tmp/Xorg.0.log First notes: You're running the old version of X, 1.6.1. Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. I don't want all the stuff for gnome and kde as I will never use them. The nice thing about the full xorg is that you get a known set of stuff, like twm. At worst, you could deinstall xorg-minimal and install xorg. It appeared to me that the fonts could be straightened out when everything else is working. I think the Handbook has a section on adding fonts. Yes, it doesn't look like a serious problem. While looking for the xorg-minimal that I installed I found a bunch of nVidea drivers in the same directory. Do you think I should install them now or wait. Those would be the nVidia binary drivers. There's also x11-drivers/xf86-video-nv. I avoid nVidia cards, so someone else will have to comment on those. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Eitan Adler wrote: Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. Â I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. Â I think the Handbook has a section on adding fonts. Hi, I'm the maintainer of x11/xorg-minimal. I have not been following this thread. Did you have problems with fonts when installing x11/xorg-minimal ? -- Eitan Adler Hi Eitan, The Xorg.0.log file shows it can't find some expected fonts. The file is at http://wonkity.com/~wblock/tmp/Xorg.0.log The actual problem I am having is that startx produces only a completely black screen. Xorg -config xorg.conf.new -retro produces the expected grid and mouse pointer. A .xinitrc file is supposed to start a window manager. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Sat, Aug 21, 2010 at 11:42 PM, Fred Boatwright f...@blakemfg.com wrote: Eitan Adler wrote: Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. Ā I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. Ā I think the Handbook has a section on adding fonts. Hi, I'm the maintainer of x11/xorg-minimal. I have not been following this thread. Did you have problems with fonts when installing x11/xorg-minimal ? -- Eitan Adler Hi Eitan, The Xorg.0.log file shows it can't find some expected fonts. The file is at http://wonkity.com/~wblock/tmp/Xorg.0.log These are harmless. X.org will work without them which is why I didn't depend on them on x11/xorg-minimal The actual problem I am having is that startx produces only a completely black screen. Xorg -config xorg.conf.new -retro produces the expected grid and mouse pointer. A .xinitrc file is supposed to start a window manager. Modern X.org installs don't show a default window manager (so a black screen is expected). What is the contents of your .xinitrc file? Best regards, Fred -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Eitan Adler wrote: On Sat, Aug 21, 2010 at 11:42 PM, Fred Boatwright f...@blakemfg.com wrote: Eitan Adler wrote: Something odd is going on with some of the fonts. I installed ports/x11/xorg-minimal as the full Monty appeared to be a huge amount of software that will never get used. Ä? I don't want all the stuff for gnome and kde as I will never use them. It appeared to me that the fonts could be straightened out when everything else is working. Ä? I think the Handbook has a section on adding fonts. Hi, I'm the maintainer of x11/xorg-minimal. I have not been following this thread. Did you have problems with fonts when installing x11/xorg-minimal ? -- Eitan Adler Hi Eitan, The Xorg.0.log file shows it can't find some expected fonts.  The file is at http://wonkity.com/~wblock/tmp/Xorg.0.log These are harmless. X.org will work without them which is why I didn't depend on them on x11/xorg-minimal The actual problem I am having is that startx produces only a completely black screen.  Xorg -config xorg.conf.new -retro  produces the expected grid and mouse pointer.  A .xinitrc file is supposed to start a window manager. Modern X.org installs don't show a default window manager (so a black screen is expected). What is the contents of your .xinitrc file? Best regards, Fred -- Eitan Adler The .xinitrc file: xrdb xsetroot -solid gray xterm -geometry +0-100 xconsole -geometry -0+0 -fn 5x7 #exec olvwm #complained about a missing font exec fvwm I have also tried twm. This file was generated from an example in the Handbook. I don't understand why xterm and xconsole are to be started before the window manager. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Finally got motivated to put together a little writeup on this: http://www.wonkity.com/~wblock/docs/html/aei.html This writeup will give me options to experiment with and see which works when I'm back in FreeBSD, am in Linux (Slackware 13.0) now. I think I tried other things besides AllowEmptyInput without success but will look again. There was nothing regarding hald in /etc/X11/xorg.conf (Linux), and there is no /etc/rc.conf (maybe in other Linux distributions?) I found hald called in /etc/rc.d/rc.hald which is called by /etc/rc.d/rc.M I found D-Bus called in /etc/rc.d/rc.messagebus which is also called by /etc/rc.d/rc.M I think the M in rc.M means multiuser. Using HAL (hald) seems much more logical than not using HAL. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Fri, 20 Aug 2010 09:22:44 +, Thomas Mueller mueller6...@bellsouth.net wrote: This writeup will give me options to experiment with and see which works when I'm back in FreeBSD, am in Linux (Slackware 13.0) now. Personally, I went the way with compiling X without HAL and DBUS, as I have no need for it. This keeps X in a kind of old-fashioned working state. There was nothing regarding hald in /etc/X11/xorg.conf (Linux), That's correct. The integration of HAL and DBUS is done at compile time, as defined by make config for the X port. and there is no /etc/rc.conf (maybe in other Linux distributions?) Not even /etc/rc.config? Oh no wait, that was S.u.S.E. Linux. :-) I found hald called in /etc/rc.d/rc.hald which is called by /etc/rc.d/rc.M In FreeBSD, this equals a similar mechanism in /usr/local/etc/rc.d, with an invoking setting in /etc/rc.conf or /etc/rc.conf.local. I think the M in rc.M means multiuser. As far as I remember - I'm not a Linux user anymore - the M refers to one of the various runlevels. M can indeed be refering to multi- user runlevel... Using HAL (hald) seems much more logical than not using HAL. If you have need for it, sure. There are several programs that rely on it (as well as on DBUS), and it can detect mouse and keyboard. I've tried X with HAL and DBUS on another system, and it seems to work. A downside is this: If you live in a country that is not US or GB, you usually want to have a localized keyboard, like the german layout in my case. This isn't selected in xorg.conf anymore, so you have to change settings for HAL and PolicyKit, this means you will have to manually edit XML files. No big deal, really, but a bit sad, as central control mechanisms are moved out of xorg.conf and scattered through many files arbitrarily placed in /usr/local. But really, it's not THAT hard; I tried this on the testing system mentioned before, and as soon as you got keyboard, permissions and so on configured, it works. But finally, let me say that I don't trust all this autodetect stuff, as it usually does not work on *my* hardware, which simply is too old. I like to have control in ONE place, for ALL the relevant settings, and I hate to have to use xrandr just to convince X.org to run in a mode that XFree86 did out of the box. It's still nice that you are not FORCED to use HAL and DBUS, and if I remember correctly, one of them (or both?) are already being obsoleted by something different that spreads in Linux right now. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Hello, I am having trouble setting up X similar to a previous posting. I have a new 8.0 installation. Using the Handbook chapter suggested below I waas able to generate and edit an xorg.conf file. It tests ok. I generated a .xinitrc file based on an example in the Handbook. When a user runs startx the screen completely blanks out. It is possible to return to the command line prompt with ctrl-alt-F1 and then ^c. No errors are listed. Where would I look for the problem? Best regards, Fred Warren Block wrote: On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 19-Aug-10 13:20, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. The Handbook chapter describes what to do: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html New Xorg requires HAL and Dbus to recognize input devices by default. Do you have these enabled? Alternatively, you revert to the old, no-HAL method by adding Option AutoAddDevices False Yes. Option AllowEmptyInput False No. Please don't use that, it's not necessary and sometimes causes problems. AutoAddDevices Off by itself disables hal input device detection. into your ServerFlags in xorg.conf. Or just put them in ServerLayout. You might also want to add Option DontZap false into the same section as well to have Ctrl-Alt-Backspace working again. I think that DontZap is back to the default, but it's now the key combination that is unset, so setxkbmap -option terminate:ctrl_alt_bksp is the way to fix it. But it's been a while since I've needed to kill X manually, so haven't tried it lately. ___ 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: Xorg Problems
On Fri, 20 Aug 2010, Fred Boatwright wrote: I am having trouble setting up X similar to a previous posting. I have a new 8.0 installation. Using the Handbook chapter suggested below I waas able to generate and edit an xorg.conf file. It tests ok. I generated a .xinitrc file based on an example in the Handbook. When a user runs startx the screen completely blanks out. It is possible to return to the command line prompt with ctrl-alt-F1 and then ^c. No errors are listed. Where would I look for the problem? [please don't top-post, it makes responding more difficult] Could you show your .xinitrc? Also, the xorg.conf and Xorg.0.log are often useful. Links to those files may be easier to post than the files themselves. When you say the screen is completely blank--is there a mouse pointer? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
My guess: the windows are not locked, they just don't receive any input, because X does not see your mouse and keyboard. Make sure that hal and dbus are started before you start X! toma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On 8/19/2010 6:20 AM, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. Rem Look in /var/log/Xorg.0.log and go from there. If something's not working, it's probably in there, or verbosity can be added to make it show up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. Rem I had that problem too, looked extensively for possible answers, and one that worked was Option AllowEmptyInput false Now I can't remember if it was AllowEmptyInput (no spaces) or Allow Empty Input but would think the former; am in Linux as I type this and didn't need that line in that xorg.conf . Synonyms for false are 0 off no Antonyms are true 1 on yes I got Xfce 4.6.1, built from the FreeBSD meta port, to work. I think initially startx is set to start twm, a spartan window manager that is included with xorg. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 19-Aug-10 13:20, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. The Handbook chapter describes what to do: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html New Xorg requires HAL and Dbus to recognize input devices by default. Do you have these enabled? Alternatively, you revert to the old, no-HAL method by adding Option AutoAddDevices False Yes. Option AllowEmptyInput False No. Please don't use that, it's not necessary and sometimes causes problems. AutoAddDevices Off by itself disables hal input device detection. into your ServerFlags in xorg.conf. Or just put them in ServerLayout. You might also want to add Option DontZap false into the same section as well to have Ctrl-Alt-Backspace working again. I think that DontZap is back to the default, but it's now the key combination that is unset, so setxkbmap -option terminate:ctrl_alt_bksp is the way to fix it. But it's been a while since I've needed to kill X manually, so haven't tried it lately. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Thu, 19 Aug 2010, Thomas Mueller wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. Rem I had that problem too, looked extensively for possible answers, and one that worked was Option AllowEmptyInput false Now I can't remember if it was AllowEmptyInput (no spaces) or Allow Empty Input but would think the former; am in Linux as I type this and didn't need that line in that xorg.conf . Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. If you want to disable hal input device detection in X, use Option AutoAddDevices Off AllowEmptyInput will borrow your stuff and never return it. AllowEmptyInput will cause trouble and say it was your idea. AllowEmptyInput cheats at cards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On 08/19/2010 15:02, Warren Block wrote: Now I can't remember if it was AllowEmptyInput (no spaces) or Allow Empty Input but would think the former; am in Linux as I type this and didn't need that line in that xorg.conf . Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. And all these years I've been using AllowEmptyInput with no problems whatsoever. Still good to know it may cause trouble. AllowEmptyInput will borrow your stuff and never return it. AllowEmptyInput will cause trouble and say it was your idea. AllowEmptyInput cheats at cards. On a second thought, it might explain a few things that have been going on in my life lately... ~ 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: Xorg Problems
On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 08/19/2010 15:02, Warren Block wrote: Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. Finally got motivated to put together a little writeup on this: http://www.wonkity.com/~wblock/docs/html/aei.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[OT] AllowEmptyInput is bad (was: Re: Xorg Problems)
On 8/19/10 1:59 PM, Warren Block wrote: On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 08/19/2010 15:02, Warren Block wrote: Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. Finally got motivated to put together a little writeup on this: http://www.wonkity.com/~wblock/docs/html/aei.html Can we have an RSS feed for that last section? :) -- 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: Xorg Problems
Warren Block wrote: On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 08/19/2010 15:02, Warren Block wrote: Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. Finally got motivated to put together a little writeup on this: http://www.wonkity.com/~wblock/docs/html/aei.html Isn't your summary (and your last section, despite it being tongue-in-cheek) misleading, because it says that AllowEmptyInput is bad, when you actually mean that it is _good_, and that _disabling_ it in Xorg.conf is bad? Or am I missing something? b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On Thu, 19 Aug 2010, b. f. wrote: Warren Block wrote: On Thu, 19 Aug 2010, Ondrej Majerech wrote: On 08/19/2010 15:02, Warren Block wrote: Don't need it in FreeBSD, either. In fact, using it in FreeBSD often causes hesitant input characters that only show up when you move the mouse. Or a draggy mouse. Or both. Finally got motivated to put together a little writeup on this: http://www.wonkity.com/~wblock/docs/html/aei.html Isn't your summary (and your last section, despite it being tongue-in-cheek) misleading, because it says that AllowEmptyInput is bad, when you actually mean that it is _good_, and that _disabling_ it in Xorg.conf is bad? Or am I missing something? Think of it as having an invisible To disable hald, using prefix. But point taken, I'll look at elaborating. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xorg Problems
I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
Ondrej Majerech wrote: On 19-Aug-10 13:20, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. New Xorg requires HAL and Dbus to recognize input devices by default. Do you have these enabled? Alternatively, you revert to the old, no-HAL method by adding Option AutoAddDevices False Option AllowEmptyInput False into your ServerFlags in xorg.conf. You might also want to add Option DontZap false into the same section as well to have Ctrl-Alt-Backspace working again. ~ Ondra Thank you Ondra...that did the trick. ---Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg Problems
On 19-Aug-10 13:20, Rem Roberti wrote: I'm having trouble with xorg on a new 8.1 installation. I haven't installed a wm yet, but when I try to call up the generic x windows by typing startx they do indeed appear, but all three of the x windows are locked up. By that I mean that there is no mouse, and no possibility of entering data in the windows via the keyboard. Totally frozen. And you can't get out of x in the usual manner i.e. ctrl-alt-backspace. The only thing that works is ctrl-alt-del which, of course, reboots the computer. Any ideas are appreciated. New Xorg requires HAL and Dbus to recognize input devices by default. Do you have these enabled? Alternatively, you revert to the old, no-HAL method by adding Option AutoAddDevices False Option AllowEmptyInput False into your ServerFlags in xorg.conf. You might also want to add Option DontZap false into the same section as well to have Ctrl-Alt-Backspace working again. ~ 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
ibm t22 xorg problems
I'm having problems with xorg on an IBM t22 using 6.2 freebsd. The video card shows to be an S3 savage, but the savage driver is broken (blank screen on startx) so I am using the vesa driver. It works fine untill I drop out of X, the screen goes blank, keyboard and mouse become unresponsive. I've done quite a bit of searching but have not found anything to help with the problem. I've enabled the dri option in xorg.conf as some suggest, but it does not help. Any ideas?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange Xorg problems - SOLVED
Richard Danter wrote: Hi All, I have a strange problem with starting Xorg after a boot on my Compaq Presario 1800T laptop. First time I try to startx the screen is corrupted, the mouse moves very slowly (if at all) and sometimes the only way out is to kill the window manager by SSH'ing in from a remote host. What is odd is that the second time I run startx it works perfectly! Same for all subsequent starts, so only the very first startx after a boot has this problem. Lookling through the logs I can see that there is a failure to open the device /dev/dri/card0 first time, but it seems to work second time. I managed to find some references to problems with dri by googling but could not find any resolutions. I have attached a dump from dmesg after starting X so you can see the boot and drm messages. Also attached are logs from Xorg after both a bad and a good start. I hope attachments are ok. One think I noticed from the dmesg dump is that the graphics card is detected as an ATI Rage 128 Mobility LF, but Linux said it was an M3. Not sure if that is relevant. I used to have RedHat Linux 7.2 and then 9 running on this machine and never had any problems with X, was even able to play DVD's perfectly using Ogle, so I am sure Xorg should work. Does anyone know what is going on here? Have I made a mistake somewhere?? I fixed it! It was simply a matter of adding r128_load=YES to /boot/loader.conf. Another newbie mistake I think. :) Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Xorg problems..
Hello.. I've been having some problems with Xorg under fbsd 5.3 (Production release). While using my computer under X (xorg 6.7) it suddenly hangs.. These crashes seems to be somewhat random. They have occurd while i'm using firefox or valknut and performing some sort of action, pressing the refresh button or something like that.. The only thing that the computer responds to is the mouse movements.. It does not respond to any buttons pressed on the keybord.. When I, via ssh, logged on to the computer it showed that Xorg was using about 98% of processor capacity.. I could reboot the computer via ssh... Anyone got any ideas of what could cause these problems?? Any help appreciated.. //Stefan dmesg Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
