LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 08-24-2006, 02:09 PM   #1
imagined
LQ Newbie
 
Registered: Mar 2006
Posts: 15

Rep: Reputation: 0
Failed to start the X server


Hello,

I just installed Fedora 5 32 bit on a Dell GX 260 machine. When starting up I get the following error message on a blue screen:

Failed to start the X server (your graphical interface). It seems that the pointer device (your mouse) is not set up correctly. Would you like to view the X server output to diagnose the problem?

So I disconnected my mouse and I still got the same message. When I see the output I see there is more errors, some seem to be monitor errors. Here part of what I get:

(1280x1024,Monitor0) mode clock 108MHz exceeds DDC maximum 80MHz
(EE) Mouse0: cannot open input device
(EE) PreInit failed for input device "Mouse0"

What do I have to do to make Fedora work? Thanks in advance,

Leo
 
Old 08-24-2006, 02:48 PM   #2
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy jessie
Posts: 1,452

Rep: Reputation: 83
Can you post mouse part of config file?
Also, what kind of mouse do you have?
 
Old 08-24-2006, 03:22 PM   #3
imagined
LQ Newbie
 
Registered: Mar 2006
Posts: 15

Original Poster
Rep: Reputation: 0
I even DISCONNECTED the mouse and i get same error message. I have a Microsoft Optical USB and PS/2 Compatible mouse.

The error message says:

(==) Using cong file: "etc/X11/xorg.conf"
(1280x1024,Monitor0) mode clock 108MHz exceeds DDC maximum 80MHz
(EE) xf 860penSerial: Cannot open device /dev/psaux
No such file or directory
(EE) Mouse0: cannot open input device
(EE) PreInit failed for input device "Mouse0"
No core pointer

Fatal server error:
failed to initialize core devices

I dont know why it says this. I can even use the mouse on this screen.


on the xorg.cong file this comes out on the mouse section:

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" IMPS/2
Option "Device" /dev/psaux"
Option "ZAmixMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.

Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" /dev/input/mice"
Option "ZAmixMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
 
Old 08-25-2006, 08:01 AM   #4
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy jessie
Posts: 1,452

Rep: Reputation: 83
Your penguin does not have device file for mouse. (/dev/psaux is missing)

You need to figure out why it is missing. I have never used Fed5 Penguin, but I think /dev/psaux is supposed to exist. Check any error messages in dmesg, syslog and other files.
 
Old 08-25-2006, 11:35 AM   #5
imagined
LQ Newbie
 
Registered: Mar 2006
Posts: 15

Original Poster
Rep: Reputation: 0
I previously had Fedora 3, but i never used ot because there was something wrong with the monitor configuration and everything looked tiny. So i never used that partition. Now that I downloaded Fedora 5, I did an "upgrade" from 4 to 5. I guess something went wrong during the upgrade. So what I did is that I made a fresh new installation.

I removed all partitions, created them again and then installed Fedora 5. Everything went smooth and with no error messages. I'm now working on my Fedora 5 like a kid with a new toy.

Thanks guys for your help.

Leo
 
Old 08-25-2006, 09:35 PM   #6
RMLinux
Member
 
Registered: Jul 2006
Posts: 224

Rep: Reputation: 31
In debian thereis command 'mdetect -x' then move your mouse..automatically give you the type of mouse you have. I don't know in FEDORA.

put it in your XF86free-4 file or run dpkg-reconfigure xserver-xfree86...i repeat it is in debian.

Last edited by RMLinux; 08-25-2006 at 09:38 PM.
 
Old 09-04-2006, 05:32 AM   #7
kstan
Member
 
Registered: Sep 2004
Location: Malaysia, Johor
Distribution: Dual boot MacOS X/Ubuntu 9.10
Posts: 851

Rep: Reputation: 31
i think you'd recompile your kernel, i have same problem b4.
 
Old 09-04-2006, 06:58 AM   #8
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
you might want to check for typos too:

Quote:
Option "ZAmixMapping" "4 5"
I doubt that one has anything to do with your issues, but still.
 
Old 09-14-2006, 12:41 AM   #9
jackdanielswv
LQ Newbie
 
Registered: Sep 2006
Posts: 1

Rep: Reputation: 0
I am getting the same error: failed to start the x server (your graphical interface)
I am trying to install SuSE linux 10.1 enterprise edition and I am getting frustrated. On one machine I get a Grub Error 22 and on another machine I am getting the first error.
I am a serious newbie. Can anyone assist?
Thanks!
Jeremy
 
Old 09-15-2006, 10:15 AM   #10
lurko
Member
 
Registered: Jun 2006
Location: Ontario, Canada
Distribution: Debian
Posts: 448

Rep: Reputation: 35
usually it says exactly why the X server failed to start, in the same spot and time it tells you it failed.. Sometimes you have to look in /var/log/Xorg.0.log though, if you posted the lines out of that file that start with (EE) and (WW), and/or your xorg.conf, you might get a more specific answer.
 
Old 01-23-2007, 02:03 PM   #11
SgtAllen
LQ Newbie
 
Registered: Jan 2007
Posts: 2

Rep: Reputation: 0
Unhappy Failed to start the X server (your graphical interface)

Failed to start the X server (your graphical interface) this is pointing to my Graphics Card/Monitor. I am installing Fedora Core 6 on a DELL Inspiron 1150. It is saying that the monitor on is not being detected!! It works fine all the way thru the install what is up with this? I have FC3,4,5, and now 6 and I have never come across this!

Ok this is getting stupid.... I reinstalled and everything worked fine, then I decided that I wanted to Dual boot so I wiped my system and installed Vista, then I reinstalled FC6 and this stupid error came up again....... I looked at the info given and it says that the (EE) I810(0): No Video BOIS modes for chosen depth.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Last edited by SgtAllen; 01-24-2007 at 11:07 AM.
 
Old 03-24-2007, 12:40 PM   #12
swathi1
LQ Newbie
 
Registered: Mar 2007
Posts: 12

Rep: Reputation: 0
Quote:
Originally Posted by SgtAllen
Failed to start the X server (your graphical interface) this is pointing to my Graphics Card/Monitor. I am installing Fedora Core 6 on a DELL Inspiron 1150. It is saying that the monitor on is not being detected!! It works fine all the way thru the install what is up with this? I have FC3,4,5, and now 6 and I have never come across this!

Ok this is getting stupid.... I reinstalled and everything worked fine, then I decided that I wanted to Dual boot so I wiped my system and installed Vista, then I reinstalled FC6 and this stupid error came up again....... I looked at the info given and it says that the (EE) I810(0): No Video BOIS modes for chosen depth.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
Hiii
i have the same problem tooo
Did You get the solution....
please respond ..

thanks
swathi
 
Old 08-17-2007, 08:45 PM   #13
bkone
Member
 
Registered: Jun 2006
Distribution: Suse
Posts: 77

Rep: Reputation: 15
I also have this issue running OpenSuse 10.2 running on a Dell Dimension 2400. I have been able to install OpenOffice on both a Dell GX270 and GX280 with integrated graphics but cannot get a gui on the 2400. The message I am getting is:

Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem.

When I view the file I get a bunch of stuff I don't recognize and then towards the bottom I see:

ACPI: opening device
(EE) I810(0): No video BIOS modes for chosen depth
(EE) Screen(s) found, but none have a usable configuration

Fatal Screen Error: No screens found

Information about X.Org
ACPI: Closing device

I have my Xorg.log and Sax2.log file but the files are too large to post and it doesn't look like there is anyway to attach the zip file.
 
Old 08-18-2007, 12:38 AM   #14
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
You don't need to post your entire xorg.conf (though I suppose you could upload the files somewhere and provide links). Can you post the Screen section and the section for your graphics card?
 
Old 08-18-2007, 11:36 AM   #15
bkone
Member
 
Registered: Jun 2006
Distribution: Suse
Posts: 77

Rep: Reputation: 15
Is this the right section?
II) Module mouse: vendor="X.Org Foundation"
compiled for 7.1.99.902, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) v4l driver for Video4Linux
(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915),
915GM, 945G, 945GM, 965G, 965G, 965Q, 946GZ
(II) Primary Device is: PCI 00:02:0
(--) Chipset 845G found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfe9fe000 - 0xfe9fffff (0x2000) MX[B]
[5] -1 0 0xfeb7f900 - 0xfeb7f9ff (0x100) MX[B]
[6] -1 0 0xfeb7fa00 - 0xfeb7fbff (0x200) MX[B]
[7] -1 0 0xfeb7fc00 - 0xfeb7ffff (0x400) MX[B]
[8] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0xfeb80000 - 0xfebfffff (0x80000) MX[B](B)
[11] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[B](B)
[12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[14] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[15] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[16] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[17] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[18] -1 0 0x0000ed8c - 0x0000ed8c (0x1) IX[B]
[19] -1 0 0x0000ed98 - 0x0000ed98 (0x1) IX[B]
[20] -1 0 0x0000ed88 - 0x0000ed88 (0x1) IX[B]
[21] -1 0 0x0000ed90 - 0x0000ed90 (0x1) IX[B]
[22] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[23] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[24] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfe9fe000 - 0xfe9fffff (0x2000) MX[B]
[5] -1 0 0xfeb7f900 - 0xfeb7f9ff (0x100) MX[B]
[6] -1 0 0xfeb7fa00 - 0xfeb7fbff (0x200) MX[B]
[7] -1 0 0xfeb7fc00 - 0xfeb7ffff (0x400) MX[B]
[8] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0xfeb80000 - 0xfebfffff (0x80000) MX[B](B)
[11] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[B](B)
[12] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[13] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[14] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[18] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[19] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[20] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[21] -1 0 0x0000ed8c - 0x0000ed8c (0x1) IX[B]
[22] -1 0 0x0000ed98 - 0x0000ed98 (0x1) IX[B]
[23] -1 0 0x0000ed88 - 0x0000ed88 (0x1) IX[B]
[24] -1 0 0x0000ed90 - 0x0000ed90 (0x1) IX[B]
[25] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[26] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[27] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
[28] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[29] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.1.99.902, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.1.99.902, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.0
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 7.1.99.902, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.0
(**) I810(0): Depth 24, (--) framebuffer bpp 32
(==) I810(0): RGB weight 888
(==) I810(0): Default visual is TrueColor
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) I810(0): initializing int10
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 832 kB
(II) I810(0): VESA VBE OEM: Intel(r)845G/845GL/845GE/845GV Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)845G/845GL/845GE/845GV Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 845G
(--) I810(0): Chipset: "845G"
(--) I810(0): Linear framebuffer at 0xE8000000
(--) I810(0): IO registers at addr 0xFEB80000
(II) I810(0): 1 display pipe available.
(II) I810(0): detected 892 kB stolen memory.
(II) I810(0): Kernel reported 176384 total, 1 used
(II) I810(0): I830CheckAvailableMemory: 705532 kB available
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(WW) I810(0): Extended BIOS function 0x5f11 not supported.
(II) I810(0): Before: SWF1 is 0x00001801
(II) I810(0): After: SWF1 is 0x00001808
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) I810(0): initializing int10
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 832 kB
(II) I810(0): VESA VBE OEM: Intel(r)845G/845GL/845GE/845GV Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)845G/845GL/845GE/845GV Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): BIOS now sees 832 kB VideoRAM
(--) I810(0): Pre-allocated VideoRAM: 892 kByte
(==) I810(0): VideoRAM: 65536 kByte
(==) I810(0): video overlay key set to 0x101fe
(**) I810(0): page flipping disabled
(==) I810(0): Using gamma correction (1.0, 1.0, 1.0)
(II) I810(0): BIOS Build: 2980
(==) I810(0): Device Presence: disabled.
(==) I810(0): Display Info: enabled.
(II) I810(0): Broken BIOSes cause the system to hang here.
If you encounter this problem please add
Option "DisplayInfo" "FALSE"
to the Device section of your XF86Config file.
(II) I810(0): Display Info: CRT: attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: TV: attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: LFP (local flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: Second (second CRT): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: DFP2 (second digital flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Display Info: LFP2 (second local flat panel): attached: FALSE, present: FALSE, size: (0,0)
(II) I810(0): Currently active displays on Pipe A:
(II) I810(0): CRT
(==) I810(0): Display is using Pipe A
(--) I810(0): Maximum frambuffer space: 65368 kByte
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules//libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.1.99.902, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(**) I810(0): Option "NoDDC"
(II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs.
(--) I810(0): Maximum space available for video modes: 832 kByte
Mode: 20 (132x25)
 
  


Reply

Tags
failed, graphical, interface, server, start


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Failed to start the X server after installing Nvidia drivers... trancekid Linux - Newbie 10 09-27-2008 11:37 AM
Failed to start the display server several times in a short time 0x5A2B Linux - Newbie 1 05-22-2006 11:17 PM
Getting an error: Failed to start the X server Fasn8n Linux - General 5 02-09-2006 09:05 AM
Failed to start X server gwalk Linux - Newbie 3 11-21-2005 04:10 PM
Pam authentification failed, cannot start x Server Final Linux - Newbie 4 11-21-2003 08:26 PM


All times are GMT -5. The time now is 07:39 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration