Re: Fresh install 7.2-RELEASE i386, X won't start
/Leslie of course turn off hald, and run moused. Unfortunately that did not fix the problem :-( What do I test next? /Leslie do X -configure and look at xorg.conf then try fixing something there. ___ freebsd-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: Fresh install 7.2-RELEASE i386, X won't start
Glen Barber skrev: Leslie, On Fri, May 29, 2009 at 3:06 PM, Leslie Jensen wrote: of course turn off hald, and run moused. Unfortunately that did not fix the problem :-( What do I test next? Could you paste the output of: cd /usr/ports/x11/xorg; make missing There's no output! This is really a mystery for me! The machine was upgraded several times with freebsd-update. Unfortunately the last update to 7.2 gave me some problems so I decided to make a fresh install. I'm using the same settings as before I reinstalled where I had no problem with X and I used hal before. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Fresh install 7.2-RELEASE i386, X won't start
Leslie, On Fri, May 29, 2009 at 3:06 PM, Leslie Jensen wrote: >> of course turn off hald, and run moused. >> > Unfortunately that did not fix the problem :-( > What do I test next? Could you paste the output of: cd /usr/ports/x11/xorg; make missing -- 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: Fresh install 7.2-RELEASE i386, X won't start
Wojciech Puchar skrev: Produces the same result :-( wouldn't it be better to pkg_delete xserver, make config, turn off hal dependency and then install. Probably it will work fine then. Sounds lika a good idea. I'll try it and repport back. /Leslie of course turn off hald, and run moused. Unfortunately that did not fix the problem :-( What do I test next? /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Fresh install 7.2-RELEASE i386, X won't start
Produces the same result :-( wouldn't it be better to pkg_delete xserver, make config, turn off hal dependency and then install. Probably it will work fine then. Sounds lika a good idea. I'll try it and repport back. /Leslie of course turn off hald, and run moused. ___ freebsd-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: Fresh install 7.2-RELEASE i386, X won't start
Wojciech Puchar skrev: Errors from xkbcomp are not fatal to the X server (EE) config/hal: NewInputDeviceRequest failed (EE) config/hal: NewInputDeviceRequest failed Protocol not supported by server Do you have dbus_enable="YES" hald_enable="YES" in your /etc/rc.conf ? Yes I have If not: add them, reboot and try to create a new xorg.conf with # Xorg -configure Produces the same result :-( wouldn't it be better to pkg_delete xserver, make config, turn off hal dependency and then install. Probably it will work fine then. Sounds lika a good idea. I'll try it and repport back. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Fresh install 7.2-RELEASE i386, X won't start
Errors from xkbcomp are not fatal to the X server (EE) config/hal: NewInputDeviceRequest failed (EE) config/hal: NewInputDeviceRequest failed Protocol not supported by server Do you have dbus_enable="YES" hald_enable="YES" in your /etc/rc.conf ? Yes I have If not: add them, reboot and try to create a new xorg.conf with # Xorg -configure Produces the same result :-( wouldn't it be better to pkg_delete xserver, make config, turn off hal dependency and then install. Probably it will work fine then. ___ freebsd-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: Fresh install 7.2-RELEASE i386, X won't start
Peter Ulrich Kruppa skrev: On Fri, 29 May 2009, Leslie Jensen wrote: When I try to startx my screen goes black for a while and then it returns to the prompt. At the screen I see this The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server (EE) config/hal: NewInputDeviceRequest failed (EE) config/hal: NewInputDeviceRequest failed Protocol not supported by server Do you have dbus_enable="YES" hald_enable="YES" in your /etc/rc.conf ? Yes I have If not: add them, reboot and try to create a new xorg.conf with # Xorg -configure Produces the same result :-( Greetings Uli. Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Fresh install 7.2-RELEASE i386, X won't start
On Fri, 29 May 2009, Leslie Jensen wrote: When I try to startx my screen goes black for a while and then it returns to the prompt. At the screen I see this The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server (EE) config/hal: NewInputDeviceRequest failed (EE) config/hal: NewInputDeviceRequest failed Protocol not supported by server Do you have dbus_enable="YES" hald_enable="YES" in your /etc/rc.conf ? If not: add them, reboot and try to create a new xorg.conf with # Xorg -configure Greetings Uli. My xorg.conf is the same as it was before I made the fresh install. I've tried to remove xorg.conf and let everything be autodetected. I see no apparent errors apart from that the Xorg.0.log stops at the same point independent of which driver (none, nv, nvidia or vesa) is loaded. Any hints what to try? Thanks /Leslie - snip Xorg.0.log 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 i386 Current Operating System: FreeBSD blj01.no-ip.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 27 May 2009 08:19:08PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 29 05:51:49 2009 (II) Loader magic: 0x7a0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@5:0:0) nVidia Corporation G70 [GeForce 7600 GS] rev 161, Mem @ 0xcf00/16777216, 0xd000/268435456, 0xce00/16777216, I/O @ 0xe800/128, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default nv Device 0" Driver "nv" EndSection Section "Screen" Identifier "Builtin Default nv Screen 0" Device "Builtin Default nv Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default nv Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default nv Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default nv Device 0" (==) No monitor specified for screen "Builtin Default nv Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, rec
