eba3
![]() |
|
|
|
|
|||||||
| X.Org X.Org on FreeBSD installation & configuration. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
After massive recompile and upgraded everything to use Xorg 7.4, every time after reboot, kdm is started but not accepting and kb/mouse input.
Checked the pids of Xorg and hald and so it seems Xorg is started before hald. Explicitly killing Xorg and get kdm restarted then everything becomes back to normal. I understand that Xorg and kdm is started through init and according to /etc/ttys whereas hald is started through /usr/local/etc/rc.d/hald. So my question is what should be the best way to start the things in proper order. Or am I missing something in the whole upgrade process? And I am wondering the problem happens because of my PC is old and slow. (PIII 1GHz 386MB) |
|
#2
|
||||
|
||||
|
I am struggling with new Xorg 7.4 already a month. I got it finally working with kbd and mouse but there are many other things are going wrong so I reinstall Xorg 7.3.2 or my main machine and continue on my 7 y.o. (P4-anyway)one that's for kids and experiments. I installed there only basic without any packages and then Xorg 7.4, then firefox3, then fluxbox and icewm and some more packages. Everything is woking just fine in twm, fluxbox and icewm. Next step I'll try Xfce (already lots of complains). I got an idea that problem is not in new Xorg but in desktop environment such as kde and gnome. Something is not ready there for new Xorg. Sorry that I cannot help, just an idea...
|
|
#3
|
||||
|
||||
|
There are two possible solutions to this problem:
1) Do not start kdm via /etc/ttys. Use a startup script like /usr/local/etc/rc.d/kdm which will postpone the start of kdm until after hald and the gettys are up and running. This is the way GNOME uses to start up gdm. Not sure though, if the kdm port does install such a script already, since I do not use KDE. 2) Statically configure your mouse/keyboard in your xorg.conf file and turn off auto-detection via hal, i.e. add the following to the 'ServerFlags' section: options "AutoAddDevices" "False" Either way should fix your problem. 1 by waiting for HAL and 2 by not having to wait for HAL. |
|
#4
|
||||
|
||||
|
There is no "ServerFlags" section in xorg.conf (ServerLayout is instead).
Should new Section "ServerFlags" be created or it's the same as ServerLayout? Is the syntax below correct: Code:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "AutoAddDevices" "False"
EndSection
|
|
#5
|
||||
|
||||
|
Simply create a new section named "ServerFlags", i.e.
Section "ServerFlags" Option "AutoAddDevices" "False" EndSection This section specifies global xorg server options, see xorg.conf(5). Be warned though, that when setting AutoAddDevices to false, hot-plugging of i.e. USB mice/keyboard will presumably not work. |
|
#6
|
|||
|
|||
|
I recently had the same problem, instead of messing with the launch order I added
Code:
Option "AllowEmptyInput" "off" |
| The Following 2 Users Say Thank You to marcelesflores For This Useful Post: | ||
ericturgeon (April 21st, 2009), kiyolee (February 17th, 2009) | ||
|
#7
|
|||
|
|||
|
Adding Option "AllowEmptyInput" "off" does really help. Great!
|
![]() |
| Tags |
| xorg hald |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Optimising mouse control in Xorg | aragon | Howtos & FAQs | 16 | June 17th, 2012 01:14 |
| FreeBSD Mouse Roll Call/USB Mouse Help | aesop | Peripheral Hardware | 10 | September 27th, 2009 19:37 |
| hald + ACPI - processor load 100% | Plague | General | 0 | February 11th, 2009 21:09 |
| Postfix issue - Must issue a STARTTLS command first | rubijn | Web & Network Services | 2 | January 22nd, 2009 05:34 |
| hald issue .... | Silverback | Installation and Maintenance of FreeBSD Ports or Packages | 4 | December 28th, 2008 11:18 |