| View previous topic :: View next topic |
| Author |
Message |
iulius
n00b
Joined: 16 Mar 2008
Posts: 9
|
 Posted: Tue Mar 18, 2008 7:02 pm Post subject: Installing X fails! |
 |
|
hi!
I just solved one problem and now i have another one  I can't get X running at all. when i punch in "X" in console i get the following output:
| Code: |
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/localhost:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux localhost 2.6.24-gentoo-r3 #9 PREEMPT Sun Mar 16 17:50:10 Local time zone must be set--see i686
Build Date: 18 March 2008
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: Tue Mar 18 20:58:18 2008
(==) Using config file: "/etc/X11/xorg.conf"
(EE) No devices detected.
Fatal server error:
no screens found
|
my xorg.conf is:
| Code: |
Section "ServerLayout"
Identifier "X.org"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/75dpi"
EndSection
Section "Module"
Load "xtrap"
Load "GLcore"
Load "dbe"
# Load "wfb"
Load "glx"
Load "record"
Load "extmod"
Load "dri"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor"
ModelName "Monitor"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
|
Thanks for your help!
cya
iulius |
|
| Back to top |
|
 |
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Tue Mar 18, 2008 7:04 pm Post subject: |
|
|
Moved from Installing Gentoo to Desktop Environments.
Desktop stuff, so moved here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
notHerbert
Advocate
Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W
|
| Posted: Tue Mar 18, 2008 8:22 pm Post subject: |
|
|
try starting X11 with
|
|
| Back to top |
|
|
iulius
n00b
Joined: 16 Mar 2008
Posts: 9
|
| Posted: Tue Mar 18, 2008 9:34 pm Post subject: |
|
|
basically i experience the same problems but in addition there's this after no screens found:
| Code: |
XIO: fatal IO error 104 (Connection reset by peer on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
|
|
|
| Back to top |
|
|
jn91048
n00b
Joined: 18 Mar 2008
Posts: 2
|
| Posted: Tue Mar 18, 2008 9:46 pm Post subject: Same |
|
|
| I have the same problems, although I think it's probably due to the fact that I'm a laptop that's hardware isn't supported. If it helps I have ATI Radeon Xpress Integrated Graphics, and the machine is a Acer 3050. If I try to restart X i get the same error message. I'm having an irritating time for my first install of gentoo. |
|
| Back to top |
|
|
kevinsgs
n00b
Joined: 16 Oct 2007
Posts: 34
|
| Posted: Wed Mar 19, 2008 2:33 am Post subject: |
|
|
| If your using an ati chipset try using the /opt/bin/aticonfig that comes with the proprietary ati-drivers package. I have an ati xpress 200m chipset on my laptop and this configures it correctly. |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed Mar 19, 2008 2:36 am Post subject: |
|
|
| Can you post your emerge --info and also what version of ati-drivers are you using ? |
|
| Back to top |
|
|
jn91048
n00b
Joined: 18 Mar 2008
Posts: 2
|
| Posted: Wed Mar 19, 2008 10:55 pm Post subject: |
|
|
| Can someone rephrase what kevinsgs said except for people who have used windows exclusively for the past 10 years? |
|
| Back to top |
|
|
Achi
n00b
Joined: 01 Nov 2006
Posts: 20
|
| Posted: Wed Mar 19, 2008 11:36 pm Post subject: |
|
|
kevinsgs is referring to a program by ati that comes with their driver. It configures a new xorg.conf file that X uses to start desgined for the fglrx driver.
(the following should be done as root)
If you want to try it first backup your current config (if you want to)
cp /etc/X11/xorg.conf /etc/X11/xorg.bck
Then try running the following
/opt/bin/aticonfig --initial --input=/etc/X11/xorg.conf
If I recall correctly it will ask you a few questions that if you don't know the answer to just hit enter for the default. |
|
| Back to top |
|
|
kevinsgs
n00b
Joined: 16 Oct 2007
Posts: 34
|
| Posted: Fri Mar 21, 2008 11:21 am Post subject: |
|
|
I think it needs a working xorg.conf to start with so you can delete or move your old one and run (xorgconfig) to generate one.
All I had to do was set my gfx card to radeon generic in the xorgconfig gui exit out run the aticonfig command shown in the post above and bam I had 3d acceleration and a working x server. |
|
| Back to top |
|
|
GTrax
n00b
Joined: 02 Jan 2007
Posts: 40
Location: Hampshire UK
|
| Posted: Fri Mar 21, 2008 3:25 pm Post subject: |
|
|
In the last 2 hours - I was at the same place as you, with the identical messages ending with :
| Code: | Fatal server error:
no screens found |
There is no question that navigating Xorg, xorgconf, xorgcfg, and "nano /etc/X11/xorg.conf" is one of the most awkward stages of getting a working desktop, and easily messes up more often than not. We don't need to get me started on that just because I think the whole business of delivering a choce of GUIs via Xorg and a variety of startup scripts is a confusing mess.
For you - the answer is to edit /etc/X11/xorg.conf, and make it give you some screens. Its not enough to give it a named monitor (which had better be capable or displaying the screens you are going to order up). Any "automatically generated" xorg.conf is usually capable of getting the name of the driver right, and maybe even the monitor. Don't expect much more, and if Nvidia did the job, you can end up with a fantastic full resolution screen, but no working mouse.
xorg.conf is capaple of calling up modes which can be specified in incredible detail to position the display, and resolution, with significant potential to mess up if you get the dotclock pixel calculations wrong, but fortunately, we don't have to go there. Simple expressions like "1280x10244" are recognised and will set to the standard all the world's monitors use.
Look at the piece of xorg.conf.
| Code: | Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection |
We will assume that "fgrlx" is the correct driver.
You can have as many "screens" as you like defined, but the one called up is "screen 0"
Its subsection "Display" needs to be expanded to get real.
Now look at one that works..
| Code: | Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 8
Modes "1600x1200" "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1600x1200" "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1600x1200" "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600x1200" "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display" SubSection "Display"
Depth 32
Modes "1400x1050"
Depth 32
Modes "1400x1050"
EndSubSection
|
Don't be put of by the boring generic names "Card0" and "Monitor0" They are defined elsewhere in xorg.conf, and called up in that critical bit. So long as your xorg.conf at least offers some displays to be found, there will be an attempt to drive the monitor. It may be a catastrophic choice if you specify screens your monitor cannot deliver.
Notice that BEFORE the screen section gets up to the "subsections" setting out the various possible screens, it gets to the very important | Code: | | DefaultColorDepth 24 |
setting. This means that startup default is going to be the highest resolution on that "24" colour depth line. Your eventual desktop (KDE, Gnome, Xfce, whatever) may well allow you to set other screens at will from these choices, but you start with that one first. Your default colour depth might have to something else. The graphics card memory has to be able to handle the combination of colour depth bits and highest resolution mentioned on that line.
Even when you get it right, such that "startx" does something other than crash, you are not yet there. It might deliver a very simple "TWM" display (The Window" Manager) with a few terminals and a clock on it. It is not much, but its way better than invoking "nano" from a 640x480 command line screen. Unless you are enthralled by the fast minimalism, you still yet have to get your choice desktop working.
There will be a window manager. It can be xdm or gdm or kdm or maybe others. You only need one, and generally they all can work each other's applications. Obviously you can associate "kdm" with KDE, but GDM can run KDE desktops as can vice-versa. The place you find it is etc/conf.d/xdm where you find a DISPLAYMANAGER setting.
Getiing past that, what happens is decided in yet another file called /etc/rc.conf.
Here you notice that DISPLAYMANAGER can also be set, and if it is, will take precedence.
You also discover that if a hidden .xinitrc file exists in the user home directory, it rules above all.
In the end, set the XSESSION to "kde" or "fluxbox" or whatever.
It is OK to have already "emerged" various desktops. Typing "start [TAB] [TAB] will reveal stuff like "startfluxbox" or "startxfce4". You will know if "startkde" is there because nobody can miss what happens if you dare to "emerge kde". If you do "startx", then one of them will start. If you attempt (say) "startkde" directly, I am not sure it will work without problems.
I have not yet found the perfect how-to that takes one all the way to a well set up startup via a login manager all the way through to a full resolution 3D capable desktop of choice. The individual parts can be great, but someone like me manages to mess up often.
TIP: Keep the old xorg.conf attempts. My root folder has got xorg.conf.duh, xorg.conf.crap1 (2) and (3), and xorg.conf.example.bad1. You only have to experience getting a great display without a working mouse to appreciate the value of grabbing the good bits from otherwise useless settings.
TIP2: Read the xorg.conf files from other distros. Don't copy them verbatim, but just reading them gives you the idea how xorg.conf works.
TIP3: The xorgconfig tool can be awkward. You cannot go back on a wrong choice, and can easily stumble. Even you get it right, it manages to yield a 640x480 no colour depth display. I did better with xorgcfg. IT at least got me a desktop. Then I went to xorg.conf, and 'made it better'.
I am with you in this. I feel what you feel. I slug on anyway. Lots of luck with it. I do hope this helps, but it is in the nature of the thing that every good find yields more potential traps. (You can tell I was gnashing a bit!) 
_________________
Living with: Ubuntu, Sidux and Gentoo |
|
| Back to top |
|
|
GTrax
n00b
Joined: 02 Jan 2007
Posts: 40
Location: Hampshire UK
|
| Posted: Fri Mar 21, 2008 4:05 pm Post subject: |
|
|
An afterthought..
None will work unless the $DISPLAY environment variable is correctly set.
I am still reading up on how to get it set to be something good, and not lose it.
This is almost real-time. I may post again when I have got it working.
_________________
Living with: Ubuntu, Sidux and Gentoo |
|
| Back to top |
|
|
iulius
n00b
Joined: 16 Mar 2008
Posts: 9
|
| Posted: Sat Apr 19, 2008 10:17 pm Post subject: |
|
|
sorry guys that I haven't replied in a while, but I've been pretty busy and had no time to worry about Gentoo for a while.
Anyway I'm back working on my problem.
I reinstalled the drivers, however i get the following error message when trying
| Code: |
modprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.24-gentoo-r3/video/fglrx.ko): Invalid module format
|
dmesg output
| Code: |
fglrx: disagrees about version of symbol struct_module
|
any suggestions what's wrong? thanks for your help!
iulius |
|
| Back to top |
|
|
|
Desktop Environments
