Re: Xorg strange behavior
On Thursday 05 February 2009 09:36 pm, Glen Barber wrote: > For what it's worth, adding 'option "AutoAddDevices" "off"' to > xorg.conf enables the mouse, but the keyboard is still not > functional. Please report your problems with /var/log/Xorg.0.log, /etc/xorg.conf (if there is one), and /usr/local/bin/hal-device output from *broken* setup. The log file from Xserver 1.4.2 isn't very helpful because its behavior and options are quite different from 1.5.3. Also, please do not mix and match HAL, Xserver, mouse driver, and their configrations. It is really confusing. :-( Thanks, Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Thursday 05 February 2009 09:13 pm, Glen Barber wrote: > Jung-uk Kim said: > > Can you show us /usr/local/bin/hal-device output? > > Sure thing, but this hal-device output is from my (working) Xorg > config, not the broken one. Well, I need output from the broken configuration. :-( Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
For what it's worth, adding 'option "AutoAddDevices" "off"' to xorg.conf enables the mouse, but the keyboard is still not functional. -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Thursday 05 February 2009 08:42 pm, Glen Barber wrote: > Jung-uk Kim said: > > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > > xorg-server-1.5.3_4,1, which I just committed. If the problem > > does not go away, please send us /var/log/Xorg.0.log. > > I wish I could report success on this, but unfortunately, I cannot. > > Attached is my Xorg.0.log. Any other information I can provide, > let me know, but I think I am going to stick with xorg-server from > pkg_add for quite some time after this point. Can you show us /usr/local/bin/hal-device output? Thanks, Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
Jung-uk Kim said: > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. > I wish I could report success on this, but unfortunately, I cannot. Attached is my Xorg.0.log. Any other information I can provide, let me know, but I think I am going to stick with xorg-server from pkg_add for quite some time after this point. Regards, -- Glen Barber X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-PRERELEASE i386 Current Operating System: FreeBSD phoenix.local 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Sun Feb 1 11:31:52 EST 2009 r...@phoenix.local:/usr/obj/usr/src/sys/PHOENIX i386 Build Date: 08 September 2008 12:37:00PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 5 20:15:36 2009 (EE) Unable to locate/open config file (II) Loader magic: 0x81ced80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f908, mode1Res1 = 0x8000 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2590 card 1028,01c9 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2592 card 1028,01c9 rev 03 class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2792 card 1028,01c9 rev 03 class 03,80,00 hdr 80 (II) PCI: 00:1b:0: chip 8086,2668 card 1028,01c9 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,2660 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:3: chip 8086,2666 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2658 card 1028,01c9 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 1028,01c9 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 1028,01c9 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev d3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2641 card 1028,01c9 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,266f card 1028,01c9 rev 03 class 01,01,8a hdr 00 (II) PCI: 02:00:0: chip 14e4,170c card 1028,01c9 rev 02 class 02,00,00 hdr 00 (II) PCI: 02:03:0: chip 14e4,4318 card 1028,0005 rev 02 class 02,80,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,12), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 11: bridge is at (0:28:0), (0,11,11), BCTRL: 0x0002 (VGA_EN is cleared) (II) PCI-to-PCI bridge: (II) Bus 12: bridge is at (0:28:3), (0,12,13), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 12 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 12 non-prefetchable memory range: [0] -1 0 0xdfc0 - 0xdfdf (0x20) MX[B] (II) Bus 12 prefetchable memory range: [0] -1 0 0xd000 - 0xd01f (0x20) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xdfb0 - 0xdfbf (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff0/19, 0xc000/28, 0xdfec/18, I/O @ 0xeff8/3 (--) PCI: (0:2:1) Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller rev 3, Mem @ 0xdff8/19 New driver is "i810" (==) Using default built-in configuration (55 lines) (==) --- Start of built-in con
Re: Xorg strange behavior
On Thu, Feb 5, 2009 at 5:24 PM, Jung-uk Kim wrote: > On Thursday 05 February 2009 05:48 pm, Scot Hetzel wrote: >> On Thu, Feb 5, 2009 at 2:19 PM, Jung-uk Kim > wrote: >> >> > How do you start xdm normally? Is hald running? Can you show >> >> > me '/usr/local/bin/hal-device' output when xdm is running? >> >> >> >> Normally, I login as root and then start either xdm or kdm. >> >> >> >> Hald and dbus are both running. >> > >> > 31: udi = '/org/freedesktop/Hal/devices/psm_0' >> > info.udi = '/org/freedesktop/Hal/devices/ignored-device' >> > (string) input.device = '/dev/psm0' (string) >> > info.subsystem = 'platform' (string) >> > info.product = 'Ignored Device' (string) >> > info.ignore = true (bool) >> > freebsd.driver = 'psm' (string) >> > freebsd.unit = 0 (0x0) (int) >> > info.parent = '/org/freedesktop/Hal/devices/atkbdc_0' (string) >> > platform.id = 'psm.0' (string) >> > freebsd.device_file = '/dev/psm0' (string) >> > >> > It is being ignored. By any chance, do you have any custom >> > policy file? >> >> Not that I am aware of. I grep'd for both psm and ignore in the >> files located under /usr/local/etc/hal and /usr/local/etc/dbus-1, >> which didn't turn up any files with these settings. > > Did you try /usr/local/share/hal? ;-) > I found a file in there that was disabling hal's ability to manage the psm0 device, after removing the file, rebooting the system, and starting xdm the mouse is now working. Thanks for the assistance. Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Thursday 05 February 2009 02:00 pm, Scot Hetzel wrote: > I have these verions installed. But when I start > xdm there is no mouse movement. The keyboard is > working. When I compare an old Xorg.0.log to the > recently generated log, it shows that hal detected > the keyboard, but no mouse. > > I had been using Xorg 7.3 with no xorg.conf file. > > /etc/rc.conf has moused_enable set. First, xdm problem is NOT addressed with these patches. How do you start xdm normally? Is hald running? Can you show me '/usr/local/bin/hal-device' output when xdm is running? Thanks, Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On 2/5/09, Scot Hetzel wrote: > On 2/4/09, Jung-uk Kim wrote: >> On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: >>> On Wed, Feb 4, 2009 at 8:13 AM, L Campbell >> wrote: >>> > I experienced the same symptoms after the recent upgrade. I found >>> > that rebuilding x11-servers/xorg-server without HAL fixed the >>> > problem. I think there are a couple of other ways to fix it, but >>> > AFAIK the root of the problem is HAL not playing nicely with >>> > other components (ie, moused). >>> >>> Interestingly, this solution did *not* work for me yesterday. The >>> only solution was to install the binary xorg-server and >>> xorg-drivers. >> >> Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and >> xorg-server-1.5.3_4,1, which I just committed. If the problem does >> not go away, please send us /var/log/Xorg.0.log. >> > I have these verions installed. But when I start > xdm there is no mouse movement. The keyboard is > working. When I compare an old Xorg.0.log to the > recently generated log, it shows that hal detected > the keyboard, but no mouse. > > I had been using Xorg 7.3 with no xorg.conf file. > > /etc/rc.conf has moused_enable set. > Opps, hit the wrong key in lynx. Attached is a copy of the Xorg 7.4 Xorg.0.log Scot X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT amd64 Current Operating System: FreeBSD hp010.hetzel.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Jan 18 09:18:31 CST 2009 r...@hp010.hetzel.org:/usr/obj/usr/src/8x-zfs/sys/DV8135NR amd64 Build Date: 05 February 2009 11:01:34AM 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: Thu Feb 5 12:22:58 2009 (EE) Unable to locate/open config file (II) Loader magic: 0x671d80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:5:0) ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/65536 (==) Matched ati for the autoconfigured driver New driver is "ati" (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati 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 "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 "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (==) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF,
Re: Xorg strange behavior
On 2/4/09, Jung-uk Kim wrote: > On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: >> On Wed, Feb 4, 2009 at 8:13 AM, L Campbell > wrote: >> > I experienced the same symptoms after the recent upgrade. I found >> > that rebuilding x11-servers/xorg-server without HAL fixed the >> > problem. I think there are a couple of other ways to fix it, but >> > AFAIK the root of the problem is HAL not playing nicely with >> > other components (ie, moused). >> >> Interestingly, this solution did *not* work for me yesterday. The >> only solution was to install the binary xorg-server and >> xorg-drivers. > > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. > I have these verions installed. But when I start xdm there is no mouse movement. The keyboard is working. When I compare an old Xorg.0.log to the recently generated log, it shows that hal detected the keyboard, but no mouse. I had been using Xorg 7.3 with no xorg.conf file. /etc/rc.conf has moused_enable set. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wed, Feb 4, 2009 at 2:07 PM, Jung-uk Kim wrote: > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. > I, unfortunately, got tied up in a few things this evening. I'll build these tomorrow and provide feedback one way or another. Regards, -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[RESOLVED] Re: Xorg strange behavior
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jung-uk Kim wrote: > On Wednesday 04 February 2009 06:38 pm, Xin LI wrote: >> Jung-uk Kim wrote: >>> On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: On Wed, Feb 4, 2009 at 8:13 AM, L Campbell >>> wrote: > I experienced the same symptoms after the recent upgrade. I > found that rebuilding x11-servers/xorg-server without HAL fixed > the problem. I think there are a couple of other ways to fix > it, but AFAIK the root of the problem is HAL not playing nicely > with other components (ie, moused). Interestingly, this solution did *not* work for me yesterday. The only solution was to install the binary xorg-server and xorg-drivers. >>> Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and >>> xorg-server-1.5.3_4,1, which I just committed. If the problem >>> does not go away, please send us /var/log/Xorg.0.log. >> I think it greatly improved the situation but not resolved >> completely. By chance, it seems that the system would stop >> responding to keyboard until I move mouse or the pointer stick. >> >> This is a ThinkPad T61 with Logitech mouse plugged into USB. > > This is a symptom of openning /dev/sysmouse multiple times. You have > > Option "AllowEmptyInput" "off" > > and there is a mouse section pointing to /dev/sysmouse in xorg.conf, > i.e., /dev/sysmouse is configured via your static configuration AND > via hald. > > - If you don't have to keep "AllowEmptyInput", then just remove the > option. The mouse section will be ignored and hald will do the right > thing now. > > - If you really have to keep "AllowEmptyInput" for some reason, then > you should remove mouse section from xorg.conf OR you may add > "AutoAddDevices" "off" in the server layout section. > > I hope it helps. By removing Option "AllowEmptyInput" "off" the problem goes away (this time, completely). Thanks a lot! Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmKL3kACgkQi+vbBBjt66C+xwCfby4oj/VHKkc9hb4rcaNs6LaP JxMAoJLNM9OPMbbpc7Z3zsHl9kdifvsa =eUp3 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wednesday 04 February 2009 06:38 pm, Xin LI wrote: > Jung-uk Kim wrote: > > On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: > >> On Wed, Feb 4, 2009 at 8:13 AM, L Campbell > > > > wrote: > >>> I experienced the same symptoms after the recent upgrade. I > >>> found that rebuilding x11-servers/xorg-server without HAL fixed > >>> the problem. I think there are a couple of other ways to fix > >>> it, but AFAIK the root of the problem is HAL not playing nicely > >>> with other components (ie, moused). > >> > >> Interestingly, this solution did *not* work for me yesterday. > >> The only solution was to install the binary xorg-server and > >> xorg-drivers. > > > > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > > xorg-server-1.5.3_4,1, which I just committed. If the problem > > does not go away, please send us /var/log/Xorg.0.log. > > I think it greatly improved the situation but not resolved > completely. By chance, it seems that the system would stop > responding to keyboard until I move mouse or the pointer stick. > > This is a ThinkPad T61 with Logitech mouse plugged into USB. This is a symptom of openning /dev/sysmouse multiple times. You have Option "AllowEmptyInput" "off" and there is a mouse section pointing to /dev/sysmouse in xorg.conf, i.e., /dev/sysmouse is configured via your static configuration AND via hald. - If you don't have to keep "AllowEmptyInput", then just remove the option. The mouse section will be ignored and hald will do the right thing now. - If you really have to keep "AllowEmptyInput" for some reason, then you should remove mouse section from xorg.conf OR you may add "AutoAddDevices" "off" in the server layout section. I hope it helps. Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jung-uk Kim wrote: > On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: >> On Wed, Feb 4, 2009 at 8:13 AM, L Campbell > wrote: >>> I experienced the same symptoms after the recent upgrade. I found >>> that rebuilding x11-servers/xorg-server without HAL fixed the >>> problem. I think there are a couple of other ways to fix it, but >>> AFAIK the root of the problem is HAL not playing nicely with >>> other components (ie, moused). >> Interestingly, this solution did *not* work for me yesterday. The >> only solution was to install the binary xorg-server and >> xorg-drivers. > > Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and > xorg-server-1.5.3_4,1, which I just committed. If the problem does > not go away, please send us /var/log/Xorg.0.log. I think it greatly improved the situation but not resolved completely. By chance, it seems that the system would stop responding to keyboard until I move mouse or the pointer stick. This is a ThinkPad T61 with Logitech mouse plugged into USB. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmKJvQACgkQi+vbBBjt66A6EQCfSFjj4pHhuTyxSeVm4a6fMCty 1+UAnA/UGe026Tz5b7RZ5Xy75gMEDy6I =QsRL -END PGP SIGNATURE- X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT amd64 Current Operating System: FreeBSD charlie.delphij.net 8.0-CURRENT FreeBSD 8.0-CURRENT #6 r188063MS: Tue Feb 3 00:24:29 PST 2009 delp...@charlie.delphij.net:/download/obj/data/src/sys/CHARLIE amd64 Build Date: 04 February 2009 03:18:32PM 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: Wed Feb 4 15:29:22 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "AllowEmptyInput" "off" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/dejavu/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/dejavu/"). (==) Including the default font path /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/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/TrueType/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /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/ (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x671d80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:0:0) nVidia Corporation Quadro NVS 140M rev 161, Mem @ 0xd600/16777216, 0xe000/268435456, 0xd400/33554432, I/O @ 0x2000/128, BIOS @ 0x/65536 (II) System resource ranges: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x00ff (0x100) IX[B] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "freetype" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "rec
Re: Xorg strange behavior
,--- You/Robert (Wed, 04 Feb 2009 13:37:18 -0500) * | | On Wed, 2009-02-04 at 07:53 -0500, Alex Goncharov wrote: | > ,--- Xin LI (Wed, 04 Feb 2009 00:59:18 -0800) * | > | Is there anybody noticing that Xorg, when there is no mouse event, | > | would not respond to keyboard events? Sometimes application would | > | stall and moving mouse would make it resume... | > | > Yes -- I've been noticing this since about last August. | > | > It's dramatically more pronounced in the new X, from which I reverted | > to the old one -- this problem being the key reason. | | This is reported to be resolved with jkim@ latest commits to | sysutils/hal. When I saw this behavior, I saw it both with and without HAL; in fact, I had been running HAL-less for about five days, before going to the old X. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote: > On Wed, Feb 4, 2009 at 8:13 AM, L Campbell wrote: > > I experienced the same symptoms after the recent upgrade. I found > > that rebuilding x11-servers/xorg-server without HAL fixed the > > problem. I think there are a couple of other ways to fix it, but > > AFAIK the root of the problem is HAL not playing nicely with > > other components (ie, moused). > > Interestingly, this solution did *not* work for me yesterday. The > only solution was to install the binary xorg-server and > xorg-drivers. Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and xorg-server-1.5.3_4,1, which I just committed. If the problem does not go away, please send us /var/log/Xorg.0.log. Thanks, Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wed, Feb 4, 2009 at 8:13 AM, L Campbell wrote: > I experienced the same symptoms after the recent upgrade. I found that > rebuilding x11-servers/xorg-server without HAL fixed the problem. I > think there are a couple of other ways to fix it, but AFAIK the root > of the problem is HAL not playing nicely with other components (ie, > moused). Interestingly, this solution did *not* work for me yesterday. The only solution was to install the binary xorg-server and xorg-drivers. -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wed, 2009-02-04 at 07:53 -0500, Alex Goncharov wrote: > ,--- Xin LI (Wed, 04 Feb 2009 00:59:18 -0800) * > | Is there anybody noticing that Xorg, when there is no mouse event, > | would not respond to keyboard events? Sometimes application would > | stall and moving mouse would make it resume... > > Yes -- I've been noticing this since about last August. > > It's dramatically more pronounced in the new X, from which I reverted > to the old one -- this problem being the key reason. This is reported to be resolved with jkim@ latest commits to sysutils/hal. robert. > > -- Alex -- alex-goncha...@comcast.net -- > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Xorg strange behavior
L Campbell writes: > I experienced the same symptoms after the recent upgrade. I found > that rebuilding x11-servers/xorg-server without HAL fixed the > problem. I think there are a couple of other ways to fix it, but > AFAIK the root of the problem is HAL not playing nicely with > other components (ie, moused). I currently have X running with HAL and without those symptoms. I _believe_ the cure, as discused, was a) rebuilding libxcb per UPDATING b) rebuilding xorg-server c) adding Option "AllowEmptyInput""off" Option "AutoAddDevices" "off" to the ServerFlags section on the config file. While we're talking about symptoms ... anyone else having problems with NumLock/CapsLock? At the moment, once activated the effect is permanent (have to restart X); further presses change the keyboard light, but not the state (i.e. all characters ARE NOW CAPS). Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
On Wed, Feb 4, 2009 at 3:59 AM, Xin LI wrote: > Is there anybody noticing that Xorg, when there is no mouse event, would > not respond to keyboard events? Sometimes application would stall and > moving mouse would make it resume... I experienced the same symptoms after the recent upgrade. I found that rebuilding x11-servers/xorg-server without HAL fixed the problem. I think there are a couple of other ways to fix it, but AFAIK the root of the problem is HAL not playing nicely with other components (ie, moused). ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Xorg strange behavior
,--- Xin LI (Wed, 04 Feb 2009 00:59:18 -0800) * | Is there anybody noticing that Xorg, when there is no mouse event, | would not respond to keyboard events? Sometimes application would | stall and moving mouse would make it resume... Yes -- I've been noticing this since about last August. It's dramatically more pronounced in the new X, from which I reverted to the old one -- this problem being the key reason. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Xorg strange behavior
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Is there anybody noticing that Xorg, when there is no mouse event, would not respond to keyboard events? Sometimes application would stall and moving mouse would make it resume... Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmJWOYACgkQi+vbBBjt66C57gCdFZC1B2GcT/wyOoILtt1KHX3+ G1EAmgM8FXots2v4EfjuQAfAF5o981cc =bSgJ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
