LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   X Fails To Start After Upgrade to Slackware64-current (http://www.linuxquestions.org/questions/slackware-14/x-fails-to-start-after-upgrade-to-slackware64-current-793700/)

hkothari 03-06-2010 08:11 PM

X Fails To Start After Upgrade to Slackware64-current
 
1 Attachment(s)
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:
Code:

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
format
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
format
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
        at http://wiki.x.org
 for help.
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.

mRgOBLIN 03-06-2010 08:45 PM

I'd guess you are running the huge kernel here.

You can try either rebuilding the kernel or switching to the generic kernel (may need an initrd).

This should fix the invalid module format error without the downgrades.

hkothari 03-06-2010 08:57 PM

Quote:

Originally Posted by mRgOBLIN (Post 3888757)
I'd guess you are running the huge kernel here.

You can try either rebuilding the kernel or switching to the generic kernel (may need an initrd).

This should fix the invalid module format error without the downgrades.

Sorry if this is really obnoxious, but how would I go about recompiling my kernel? Thanks.

rworkman 03-06-2010 09:02 PM

Just make an initrd and use the generic kernel - it's much easier, and there are step-by-step directions for that.

mRgOBLIN 03-06-2010 09:26 PM

I'd agree with rworkman there.

This might help point you in the right direction
http://www.linuxquestions.org/questi...9/#post3885211

damgar 03-06-2010 09:36 PM

Quote:

Sorry if this is really obnoxious, but how would I go about recompiling my kernel? Thanks.
Just FYI Googling
Code:

alien kernel
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.

hkothari 03-06-2010 09:40 PM

Yeah, I realized that it would be easier to switch to generic, thanks everybody, I'm happily posting from my slackware install again. Thanks :D

vbatts 03-06-2010 09:40 PM

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.

Take care,


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