X won't start after port upgrade

2009-07-24 Thread Leslie Jensen

I've followed every advice in /usr/ports/UPDATING

The portmaster -r jpeg* returns No match.

portmaster -r jpeg-7 rebuilds only jpeg-7 no other ports!

After this upgrade my X won't start :-(

Any hints?

Thanks

Leslie

-- snip ---

(II) LoadModule: synaptics
(WW) Warning, couldn't open module synaptics
(II) UnloadModule: synaptics
(EE) Failed to load module synaptics (module does not exist, 0)
(EE) No input driver matching `synaptics'
(**) default pointer: Device: /dev/sysmouse
(==) default pointer: Protocol: Auto
(**) Option AlwaysCore
(**) default pointer: always reports core events
(==) default pointer: Emulate3Buttons, Emulate3Timeout: 50
(**) default pointer: ZAxisMapping: buttons 4 and 5
(**) default pointer: Buttons: 9
(**) default pointer: Sensitivity: 1
(**) default pointer: (accel) keeping acceleration scheme 1
(**) default pointer: (accel) filter chain progression: 2.00
(**) default pointer: (accel) filter stage 0: 20.00 ms
(**) default pointer: (accel) set acceleration profile 0
(II) default pointer: SetupAuto: hw.iftype is 4, hw.model is 0
(II) default pointer: SetupAuto: protocol is SysMouse



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: X won't start after port upgrade

2009-07-24 Thread Jerry
On Fri, 24 Jul 2009 16:34:35 +0200
Leslie Jensen les...@eskk.nu wrote:

 
 I've followed every advice in /usr/ports/UPDATING
 
 The portmaster -r jpeg* returns No match.
 
 portmaster -r jpeg-7 rebuilds only jpeg-7 no other ports!
 
 After this upgrade my X won't start :-(
 
 Any hints?

Including the log output, it there is any, might be a good idea.

Personally, I like 'portmanager' for fixing problems like this. Since
you gave no indication of what the problem might be, you could try this
for starters. Rebuild the xorg-7.4_2 meta port. Be sure to update you
ports tree first, then run:

portmanager x11/xorg -p -y -l

If X still won't start, you may have to rebuild your window manager as
well.


-- 
Jerry
ges...@yahoo.com

If you could only get that wonderful feeling of
accomplishment without having to accomplish anything.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Fresh install 7.2-RELEASE i386, X won't start

2009-05-30 Thread Wojciech Puchar

/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

2009-05-29 Thread Wojciech Puchar

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

2009-05-29 Thread Leslie Jensen



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

2009-05-29 Thread Wojciech Puchar

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

2009-05-29 Thread Leslie Jensen



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

2009-05-29 Thread Glen Barber
Leslie,

On Fri, May 29, 2009 at 3:06 PM, Leslie Jensen les...@eskk.nu 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

2009-05-29 Thread Leslie Jensen



Glen Barber skrev:

Leslie,

On Fri, May 29, 2009 at 3:06 PM, Leslie Jensen les...@eskk.nu 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


Fresh install 7.2-RELEASE i386, X won't start

2009-05-28 Thread Leslie Jensen


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 RALT 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




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 default 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 default 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 default 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, reconfigure HAL or disable 
AllowEmptyInput.
(II) System resource ranges:
[0] -1  0   0x000f - 0x000f (0x1) MX[B]
[1] -1  0   0x000c - 0x000e (0x3) MX[B]
[2] -1  0   0x - 0x0009 (0xa) MX[B]
   

Re: Fresh install 7.2-RELEASE i386, X won't start

2009-05-28 Thread Peter Ulrich Kruppa

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 RALT 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 default 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 default 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 default 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, reconfigure HAL or disable 
AllowEmptyInput.

Re: Fresh install 7.2-RELEASE i386, X won't start

2009-05-28 Thread Leslie Jensen



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 RALT 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: X won't start up; No matching Device section

2008-08-02 Thread Helge Rohde
On Saturday 02 August 2008 02:30:22 David Gurvich wrote:
 Have you loaded all the kernel modules you need and installed
 xf86-video-chips?

I am not aware of any kernel modules that i would have to load explicitely. 
And, yes, as indicated by the Xorg.log snippet, the chips driver is present.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


X won't start up; No matching Device section

2008-08-01 Thread Helge Rohde
Hello List,
I got an old TFT that uses a special connector to a CHIPS ct65554 graphics 
card. However, although the ct65554 is listed as supported, it is not 
recognized by the chips driver. System is FreeBSD 7-Release AMD64. I am 
pretty sure that the same xorg.conf worked under i386. 


pciconf -lvc claims device='65554 Flat Panel/LCD CRT GUI Accelerator' for the 
card, however although i do have an xorg.conf Device section containing 

Driver chips
Chipset ct65554

X wont start up. Xorg.0.log complains:

(II) CHIPS: Driver for Chips and Technologies chipsets: ct65520, ct65525,
ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550,
ct65554, ct6, ct68554, ct69000, ct69030, ct64200, ct64300
(II) Primary Device is: 
(WW) CHIPS: No matching Device section for instance (BusID PCI:3:7:0) found
(EE) No devices detected.


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: X won't start up; No matching Device section

2008-08-01 Thread David Gurvich
Have you loaded all the kernel modules you need and installed
xf86-video-chips?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: keyboard problem X won't start

2005-05-02 Thread Toni Schmidbauer
On Sun, May 01, 2005 at 10:19:17AM -0400, [EMAIL PROTECTED] wrote:
 (EE) Failed to load module speedo (module does not exit,0)
 (EE) Failed to load module Keyboard (module does not exit,0)
 (EE) No input driver matching 'Keyboard'
 No core keyboard
 
 Fatal server error:
 failed to inititalize core devices
 
 It seems the keyboard driver is missing.  Any suggestions to get it
 working are really appreciated.

seems like a wrong Driver in Section InputDevice
(/etc/x11/xorg.conf.) 

you do not say which version of x11/xorg you are running, but
here is my Section InputDevice for xorg 6.8.1

Section InputDevice
Identifier  Keyboard0
Driver  kbd
Option  XkbModel pc105
Option  XkbLayout de
Option  XkbVariant nodeadkeys
Option  XkbOptions ctrl:nocaps
EndSection

Xorg.0.log tells me:

(II) LoadModule: kbd
(II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o
(II) Module kbd: vendor=X.Org Foundation

hth,
toni
-- 
Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at
mehr irrt, der hat auch zu arbeiten aufgehoert| Toni Schmidbauer
-- Max Planck |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: keyboard problem X won't start

2005-05-02 Thread Subhro
On 5/1/2005 19:49, [EMAIL PROTECTED] wrote:
I just upgraded from 5.3 to 5.4 RC3 via sysinstall from a cd.The
upgrade was successful however, when I try startx I get the
following error:
(EE) Failed to load module speedo (module does not exit,0)
(EE) Failed to load module Keyboard (module does not exit,0)
(EE) No input driver matching 'Keyboard'
No core keyboard
 

Are you running a generic kernel? If not then did you include the 
keyboard driver in your kernel configuration file?

Regards
S.
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: keyboard problem X won't start

2005-05-02 Thread Franz Klammer
[EMAIL PROTECTED] wrote:
I just upgraded from 5.3 to 5.4 RC3 via sysinstall from a cd.The
upgrade was successful however, when I try startx I get the
following error:
(EE) Failed to load module speedo (module does not exit,0)
(EE) Failed to load module Keyboard (module does not exit,0)
(EE) No input driver matching 'Keyboard'
No core keyboard
xorg 6.8.2?
remove »load speedo« - it's gone.
change »Driver keyboard«  to:  »Driver kbd«
if i'm not completely wrong you can remove »Load type1« too
because type1-fonts are also handelt with freetype.
franz.
Fatal server error:
failed to inititalize core devices
It seems the keyboard driver is missing.  Any suggestions to get it
working are really appreciated.
TIA,
Andy
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


keyboard problem X won't start

2005-05-01 Thread andy
I just upgraded from 5.3 to 5.4 RC3 via sysinstall from a cd.The
upgrade was successful however, when I try startx I get the
following error:

(EE) Failed to load module speedo (module does not exit,0)
(EE) Failed to load module Keyboard (module does not exit,0)
(EE) No input driver matching 'Keyboard'
No core keyboard

Fatal server error:
failed to inititalize core devices

It seems the keyboard driver is missing.  Any suggestions to get it
working are really appreciated.

TIA,

Andy

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


X won't start

2003-08-05 Thread mess-mate
Hi,
X no more start after a crash with root.
Error Knotify, kdeinit, etc.. pid... 
As user all goes well.
What can I do ??
Thanks for your help.
mess-mate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: X won't start

2003-08-05 Thread Greg 'groggy' Lehey
On Tuesday,  5 August 2003 at 14:21:38 +0200, mess-mate wrote:
 Hi,
 X no more start after a crash with root.
 Error Knotify, kdeinit, etc.. pid...

If you get that far, X is running.  Those error messages are there for
a purpose.  Read them.

 As user all goes well.

So you're saying that root can't start X?  That's probably a good
idea.  You shouldn't be running as root.

 What can I do ??

Start by describing how far you get.  Also take a look at
/var/log/XFree86.0.log.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers


pgp0.pgp
Description: PGP signature