xinit: Server error. Ubuntu 8.10
xinit: Server error. Ubuntu 8.10
Hi!
I've been running 8.10 on a desktop for a month now. Its been working fine. I've been using it for some project work.
I had to reboot the computer (I used to have it on all the time) and when it rebooted it takes me to the CLI and there is no GUI.
When I "startx" at the terminal I get an error that says "xinit: Server error"
Here are the things I've already tried:
1. sudo dpkg-reconfigure xserver-xorg
This skips the steps for the graphics card, does the keyboard configuration and then ends without the mouse and monitor configuration.
2. sudo apt-get install --reinstall gdm
Gets stuck at 'setting up ssl-cert (1.0.23)
3. sudo aptitude install ubuntu-desktop (I guess same command as above)
Gets stuck at 'setting up ssl-cert (1.0.23) again.
It was working fine so I don't know if its really a problem with my video driver.
Also the reason I think they're getting stuck at 'setting up ssl-cert' is because I've been playing around with the openssl on the computer.
So I don't think I will be able to download anything from the reps.
Anybody has any other ideas? Any help would be appreciated as I'm stuck with this and this computer has a lot of information and configuration that I've been working on lately and don't wish to reinstall.
Warm wishes,
Shabs.
I've been running 8.10 on a desktop for a month now. Its been working fine. I've been using it for some project work.
I had to reboot the computer (I used to have it on all the time) and when it rebooted it takes me to the CLI and there is no GUI.
When I "startx" at the terminal I get an error that says "xinit: Server error"
Here are the things I've already tried:
1. sudo dpkg-reconfigure xserver-xorg
This skips the steps for the graphics card, does the keyboard configuration and then ends without the mouse and monitor configuration.
2. sudo apt-get install --reinstall gdm
Gets stuck at 'setting up ssl-cert (1.0.23)
3. sudo aptitude install ubuntu-desktop (I guess same command as above)
Gets stuck at 'setting up ssl-cert (1.0.23) again.
It was working fine so I don't know if its really a problem with my video driver.
Also the reason I think they're getting stuck at 'setting up ssl-cert' is because I've been playing around with the openssl on the computer.
So I don't think I will be able to download anything from the reps.
Anybody has any other ideas? Any help would be appreciated as I'm stuck with this and this computer has a lot of information and configuration that I've been working on lately and don't wish to reinstall.
Warm wishes,
Shabs.
We talked about this before and I know you didn't want to reinstall.
But since we talked about Debian woody as a possible solution for the right openssl version that you needed for your work, I think I found a good download spot for you : - )
Still can't come up with anything else for you unfortunately, just gotta hope someone else has a solution for you ^^
Hope you solve it! Good luck!
But since we talked about Debian woody as a possible solution for the right openssl version that you needed for your work, I think I found a good download spot for you : - )
Code: Select all
http://iso.linuxquestions.org/debian/debian-3.0r2-woody/
Hope you solve it! Good luck!
"The best place to hide a tree, is in a forest"
- bad_brain
- Site Owner
- Posts: 11636
- Joined: 06 Apr 2005, 16:00
- 19
- Location: In your eye floaters.
- Contact:
phew...ok...where to start...
first of all, you should figure out that ssl-cert problem, because when a package "hangs" with an unresolvable dependency for example it can keep you away from installing anything, so it should be solved first. ssl-cert has nothing to do at all with the desktop, xserver, etc., it's a package in context with a web server (most likely Apache) or other services that need to create SSL certificates.
do:
do you get any errors when doing that? if yes: post them.
what computer is it? if it's a laptop post the brand/model, if it's a desktop what g-card is it?
first of all, you should figure out that ssl-cert problem, because when a package "hangs" with an unresolvable dependency for example it can keep you away from installing anything, so it should be solved first. ssl-cert has nothing to do at all with the desktop, xserver, etc., it's a package in context with a web server (most likely Apache) or other services that need to create SSL certificates.
do:
Code: Select all
apt-get update
apt-get upgrade
what computer is it? if it's a laptop post the brand/model, if it's a desktop what g-card is it?
Hi J. I think the version I'm looking for is without the revs, so just 3.0 (if I'm not wrong of course).
haha.. bad, that sounds like a good start
Thanks for your help though
apt-get update went by fine.
apt-get upgrade got stuck at ssl-cert as usual.
I do have courier IMAP running on the computer and I have removed the default version of openssl and installed an older version (0.9.6c). I'm afraid reinstalling ssl-cert (which I assume will fix the problem) may update the openssl version too.
Its a desktop and the card is a : Intel 82865G Integrated Graphics Controller (rev 02)
Shabs.
haha.. bad, that sounds like a good start
Thanks for your help though
apt-get update went by fine.
apt-get upgrade got stuck at ssl-cert as usual.
I do have courier IMAP running on the computer and I have removed the default version of openssl and installed an older version (0.9.6c). I'm afraid reinstalling ssl-cert (which I assume will fix the problem) may update the openssl version too.
Its a desktop and the card is a : Intel 82865G Integrated Graphics Controller (rev 02)
Shabs.
- Lundis
- Distorter of Reality
- Posts: 543
- Joined: 22 Aug 2008, 16:00
- 15
- Location: Deadlock of Awesome
- Contact:
After restarting, there was a new boot option, right? If/when you fix the package issues you should try booting using the old one. Then your old kernel will be loaded and if the problem is indeed a kernel change it'll work.
If you're still having problems after trying that as well, run startx and check your Xorg log file: /var/log/Xorg.0.log
The relevant info should be at the end, post it here if you need help. Include the contents of your /etc/X11/xorg.conf as well, if you have one.
If you're still having problems after trying that as well, run startx and check your Xorg log file: /var/log/Xorg.0.log
The relevant info should be at the end, post it here if you need help. Include the contents of your /etc/X11/xorg.conf as well, if you have one.
Hi Lundis
I didn't see any new boot options (why would I?), but I've tried the ones I've seen and there was no improvement.
Here are the contents of /etc/X11/xorg.conf
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Device"
Identifier "Configured Video Device"
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
And some parts of the /var/log/Xorg.0.log
sudo cat /var/log/Xorg.0.log | grep \(WW\)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) intel(0): Failed to allocate texture space.
sudo cat /var/log/Xorg.0.log | grep \(EE\)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
I didn't see any new boot options (why would I?), but I've tried the ones I've seen and there was no improvement.
Here are the contents of /etc/X11/xorg.conf
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Device"
Identifier "Configured Video Device"
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
And some parts of the /var/log/Xorg.0.log
sudo cat /var/log/Xorg.0.log | grep \(WW\)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) intel(0): Failed to allocate texture space.
sudo cat /var/log/Xorg.0.log | grep \(EE\)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
- Lundis
- Distorter of Reality
- Posts: 543
- Joined: 22 Aug 2008, 16:00
- 15
- Location: Deadlock of Awesome
- Contact:
Every time the kernel is upgraded I get a new boot option, examples:
ubuntu ... 2.6.31-14
ubuntu ... 2.6.31-16
ubuntu ... 2.6.31-17
ubuntu ... 2.6.31-19
In my case 2.6.31-17 broke the network driver, so I had to stick to 2.6.31-16 for a while
Anyway, there's apparently something wrong with the intel driver, I suggest you try vesa, which is supposed to be a slow fail-safe universal driver. It's not really that bad for general usage, but you won't have any hardware acceleration at all. (note: read my entire post before changing anything ^^ )
Your xorg.conf is set to automatically detect the gfx driver, I added Driver "vesa" to the device section, this will force it to use vesa instead. I suggest you make a backup of xorg.conf before changing it. This is just a temporary solution though.
Let's find out if you still have the old kernel lying around (assuming that it was updated ofc, but we'll find out in any case now). Run:
It'll show the relevant files, in my case it looks like this:
in the file /boot/grub/menu.lst you can edit the boot entries. Scroll down until you see something like
Now, if you want to add an entry for an older kernel present in /boot You would replace vmlinuz-2.6.31-19-generic and initrd.img-2.6.31-19-generic with the relevant filenames. Like this:
I hope this is enough to keep you busy until tomorrow
ubuntu ... 2.6.31-14
ubuntu ... 2.6.31-16
ubuntu ... 2.6.31-17
ubuntu ... 2.6.31-19
In my case 2.6.31-17 broke the network driver, so I had to stick to 2.6.31-16 for a while
Anyway, there's apparently something wrong with the intel driver, I suggest you try vesa, which is supposed to be a slow fail-safe universal driver. It's not really that bad for general usage, but you won't have any hardware acceleration at all. (note: read my entire post before changing anything ^^ )
Code: Select all
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
Let's find out if you still have the old kernel lying around (assuming that it was updated ofc, but we'll find out in any case now). Run:
Code: Select all
ls /boot | grep generic
Code: Select all
abi-2.6.28-16-generic
abi-2.6.31-14-generic
abi-2.6.31-16-generic
abi-2.6.31-17-generic
abi-2.6.31-19-generic
config-2.6.28-16-generic
config-2.6.31-14-generic
config-2.6.31-16-generic
config-2.6.31-17-generic
config-2.6.31-19-generic
initrd.img-2.6.28-16-generic
initrd.img-2.6.31-14-generic
initrd.img-2.6.31-16-generic
initrd.img-2.6.31-17-generic
initrd.img-2.6.31-19-generic
System.map-2.6.28-16-generic
System.map-2.6.31-14-generic
System.map-2.6.31-16-generic
System.map-2.6.31-17-generic
System.map-2.6.31-19-generic
vmcoreinfo-2.6.28-16-generic
vmcoreinfo-2.6.31-14-generic
vmcoreinfo-2.6.31-16-generic
vmcoreinfo-2.6.31-17-generic
vmcoreinfo-2.6.31-19-generic
vmlinuz-2.6.28-16-generic
vmlinuz-2.6.31-14-generic
vmlinuz-2.6.31-16-generic
vmlinuz-2.6.31-17-generic
vmlinuz-2.6.31-19-generic
Code: Select all
title Ubuntu 9.10, kernel 2.6.31-19-generic
uuid fe39f017-15b3-462e-b397-d3e700231687
kernel /vmlinuz-2.6.31-19-generic root=UUID=1a1e4c8a-fa84-4111-9997-02e846dbe2e1 ro quiet splash
initrd /initrd.img-2.6.31-19-generic
quiet
Code: Select all
title Ubuntu 9.10, kernel 2.6.31-19-generic
uuid fe39f017-15b3-462e-b397-d3e700231687
kernel /vmlinuz-2.6.31-19-generic root=UUID=1a1e4c8a-fa84-4111-9997-02e846dbe2e1 ro quiet splash
initrd /initrd.img-2.6.31-19-generic
quiet
title Ubuntu 9.10, testing 2.6.31-14
uuid fe39f017-15b3-462e-b397-d3e700231687
kernel /vmlinuz-2.6.31-14-generic root=UUID=1a1e4c8a-fa84-4111-9997-02e846dbe2e1 ro quiet splash
initrd /initrd.img-2.6.31-14-generic
quiet
Hi Lundis!
Thanks for the detailed post. I'm sorry I couldn't reply earlier as I didn't have access to that machine.
The problem I have is not because I have upgraded recently.
I have not upgraded the kernel since I installed 8.10.
Just that I restarted the system (after a long time I might add) and it just broke, I couldn't get the display manager to work, and had only the command line to work with.
Which I don't mind really, but I need the GUI or wireshark.
I changed the driver to vesa but that has made no difference. I still get the errors when I try 'startx'
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error
and when I try 'startx' again, I get the following:
xinit: Server error.
Shabs.
Thanks for the detailed post. I'm sorry I couldn't reply earlier as I didn't have access to that machine.
The problem I have is not because I have upgraded recently.
I have not upgraded the kernel since I installed 8.10.
Just that I restarted the system (after a long time I might add) and it just broke, I couldn't get the display manager to work, and had only the command line to work with.
Which I don't mind really, but I need the GUI or wireshark.
I changed the driver to vesa but that has made no difference. I still get the errors when I try 'startx'
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error
and when I try 'startx' again, I get the following:
xinit: Server error.
Shabs.
- bad_brain
- Site Owner
- Posts: 11636
- Joined: 06 Apr 2005, 16:00
- 19
- Location: In your eye floaters.
- Contact:
eeewww....:
is it a nvidia g-card? if yes, which model? have you installed the nvidia driver, and if yes is it the binary driver originally from nvidia?
Code: Select all
CRITICAL: gdm_config_value_get_bool: assertion `value->type == GDM_CONFIG_VALUE_BOOL' failed