Canīt start xorg in ubuntu 8.10 due to fatal error caused by /lib/modules
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Canīt start xorg in ubuntu 8.10 due to fatal error caused by /lib/modules
Hello, I really need some urgent help please.
I installed ubuntu 8.10 in an acer aspire one using a wubi install. It was working correctly, but after I installed an update and tried to open a new shell( the update manager adviced that it was necesary to reboot the system), it did not open, so I went to a shell that I had opened before installing the update and tried to open several gnome applications, such like eog and gedit, to see if it could give information about the error. It showed and error saying that gettext symbol was not defined. I thought this was caused by the update and that it would be fixed as soon as I rebooted the system. But after rebooting, it wouldn`t load the graphic environment and showed the following error at startup:
Code:
X: warning; process set to priority -1 instead of requested priority 0
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux wicho 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 i686
Build Date: 09 March 2009 10:48:54AM
xorg-server 2:1.5.2-2ubuntu3.1 (buildd@rothera.buildd)
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: Wed May 20 21:40:27 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
FATAL: Could not load /lib/modules/2.6.27-14-generic/modules.dep: No such file or directory
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Couldn't allocate video memory
Fatal server error:
AddScreen/ScreenInit failed for driver 0
[/CODE]
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
I have tried to fix this problem using the recovery mode, but none of the options provided with 2.6.27-14-generic kernel has worked. I can still log in a root shell using recovery mode, and I am hoping I can solve the problem from there with the necessary advice.
...
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux wicho 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 i686
Build Date: 09 March 2009 10:48:54AM
xorg-server 2:1.5.2-2ubuntu3.1 (buildd@rothera.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
...
There is an inconsistency - the kernel doesn't fit the set of modules installed (they seem to be from 8.04 - how's that come about? wrong wubi version?). Where did you get the "wicho" kernel from? Didn't it come with modules? What kind of repository did you use? If you only installed the kernel from whichever source you got it, get the modules from the same source. But frankly, this has me puzzled... if you it all by the book, there's no reason why this should have happened. Normally, if you install a new kernel using the repositories (you said something about updates, so I guess you did), the modules and all tools are installed with it. The "reboot" advice points at the installation of a new kernel, too...
Can you still boot to the old kernel and use that? If that's the case, you can use apt-get or Synaptic to look for the modules set and install it.
There is an inconsistency - the kernel doesn't fit the set of modules installed (they seem to be from 8.04 - how's that come about? wrong wubi version?). Where did you get the "wicho" kernel from? Didn't it come with modules? What kind of repository did you use? If you only installed the kernel from whichever source you got it, get the modules from the same source. But frankly, this has me puzzled... if you it all by the book, there's no reason why this should have happened. Normally, if you install a new kernel using the repositories (you said something about updates, so I guess you did), the modules and all tools are installed with it. The "reboot" advice points at the installation of a new kernel, too...
Can you still boot to the old kernel and use that? If that's the case, you can use apt-get or Synaptic to look for the modules set and install it.
M.
I am pretty sure I installed ubuntu 8.10 and that the error was the one I posted before. "wicho" is only the hostname, not the name of the kernel. It seems that one the updates was corrupted and that caused the problem, but I have fixed it now, thanks for answering.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.