[SOLVED] X Fails To Start After Upgrade to Slackware64-current
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
X Fails To Start After Upgrade to Slackware64-current
So I made the upgrade to slackware64-current and all of a sudden after my next reboot, startx failed, and x refused to start the output was the following:
Release Date: 2010-02-16
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.1 Slackware Linux Project
Current Operating System: Linux hd830 2.6.33 #3 SMP Sat Feb 27 19:42:32 CST 2010 x86_64
Kernel command line: BOOT_IMAGE=Linux ro root=803 vt.default_utf8=0
Build Date: 23 February 2010 12:09:32PM
Current version of pixman: 0.16.6
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: Sat Mar 6 19:21:18 2010
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
WARNING: Error inserting button (/lib/modules/2.6.33/kernel/drivers/acpi/button.ko): Invalid module format
WARNING: Error inserting i2c_algo_bit (/lib/modules/2.6.33/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module
WARNING: Error inserting agpgart (/lib/modules/2.6.33/kernel/drivers/char/agp/agpgart.ko): Invalid module format
WARNING: Error inserting drm (/lib/modules/2.6.33/kernel/drivers/gpu/drm/drm.ko): Invalid module format
WARNING: Error inserting drm_kms_helper (/lib/modules/2.6.33/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module
FATAL: Error inserting i915 (/lib/modules/2.6.33/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format
(EE) intel(0): No kernel modesetting driver detected.
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
So then after some googling I got the suggestion to downgrade udev-151 to udev-141, but that yeilded no results. So I did some more googling and a bunch of people who had the same problem said that downgrading module-init-tools worked, so I downgraded from module-init-tools 3.11 something to 3.6 and now, not only does my X no longer work, but no modules are being loaded I believe, for example I saw in my startup that fuse was not being loaded, ndiswrapper which I had installed was not loaded. Does anyone know how I can take care of my predicament? It's rather urgent. Thanks all.
Sorry if this is really obnoxious, but how would I go about recompiling my kernel? Thanks.
Just FYI Googling
will bring you to a good tutorial for rolling your own kernel. I am not suggesting an alternate solution to the problem that you are currently experiencing, although it might be a good read because it gives some good explanations of what it is that is being suggested above.
I second the recommendation, of rworkman, to just use the generic kernel that is already available and then create an initrd using the mkinitrd command.
But be advised, with the error you've reported, the compositing of KDE may not play well this the drivers right now, but that's always subject to change with the next upgrades to the kernel and/or Xorg.