LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 02-23-2004, 03:44 PM   #1
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Rep: Reputation: 15
startx problems in Fedora Core 1


I recently used up2date to upgrade to kernel 2.4.22-1.2174.nptl with Fedora Core 1 (Yarrow). After I tried to boot into this new kernel I started having startx problems.
The system starts to boot up ok, but as soon as I get to the part where the interactive startup begins, I get: "/usr/bin/rhgb error while loading shared libraries libSm.so.6 can not open red object file".
Then the boot up continues until right before I get to the login screen and the second error message is : "init: Id "x" respawning too fast : disabled for 5 minutes".
I then hit enter and come to the command prompt login where I am able to log in to run level 3. When I enter the startx command the next error message I get is "xauth: error while loading shared libraries: libXmuu.so.1: cannot open shared object file: no such file or directory".
I 've checked the boot up logs, var/logs and the xfree86 logs and nothing seems to indicate the problem. All the files in question, are on the system, but seem to be binaries so I'm not sure exactly how to fix this problem. I'm not able to boot into the desktop(gnome) at all.
I'm running XFree86 version 4.3.0.
Any help would be appreciated.
Thanks
 
Old 02-23-2004, 05:26 PM   #2
trickykid
LQ Guru
 
Registered: Jan 2001
Posts: 24,149

Rep: Reputation: 261Reputation: 261Reputation: 261
Moved: Seems more suitable in our Fedora forum. Regards.
 
Old 02-23-2004, 09:06 PM   #3
RHELL
Member
 
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321

Rep: Reputation: 31
I'm wondering about that 'id x' stuff.
What's in /etc/inittab?

Also, what are privileges for the library file it dislikes?
 
Old 02-24-2004, 11:09 AM   #4
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Original Poster
Rep: Reputation: 15
reply to Rhell

The id "x" refers to the various run levels that the os will boot into: 3 is the command line and 5 is booting into the desktop. This is what I've read from various places on the net.
The various lib files mentioned are all owned by root. The respawning error seems to have to do with startx and it happens every 5 minutes. Even though I can't get into the desktop and am working at the command line.
I'm a little stumped by this because is happening for every kernel version I have access to; including kernel 2.6 which I compiled a while back. I would prefer to find a solution to this, if there is one, rather than having to do a complete install.
I have even tried to do an upgrade from the distro CD's but that doesn't even help.
Any suggestions or anything you can think of would be appreciated.
Thanks
 
Old 02-24-2004, 04:17 PM   #5
RHELL
Member
 
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321

Rep: Reputation: 31
Yes, id is init-default-runlevel. Sorry, thought you were quoting an exact message with a funky inittab value.

So, you've already confirmed that the lib's exist?

Anything more informative in dmesg?

From runlevel 3, try running redhat-config-xfree86, it's a whole lot easier to see problems there.

One other dumbass check is to use df to check /home and /tmp, if either partition is full(or over quota), x runs out of room, though I think the error message would point that way.
 
Old 02-24-2004, 06:33 PM   #6
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Original Poster
Rep: Reputation: 15
reply to Rhell

I looked in dmesg and there doesn't seem to be any indication of what could be the problem.
When I did redhat-config-xfree86, I got this error message:
"error while loading shared libraries : libSM.so.6 : can not open shared object file: no such file or directory.
I couldn't find this particular file using either whereis or find but when I did a locate I found it in /usr/X11R6/lib/libSM.so.6 and /usr/X11R6/lib/libSM.so.6.0.
When I opened them up they are essentially binaries.
I'm not sure if there is a problem with xfree86 or with the system being able to initialize it.
I was looking in the init man pages and it's given me a few other places I can try and look at.
If you can think of anything else I might try just let me know.
Thanks
 
Old 02-24-2004, 08:14 PM   #7
Jeff_G_1974
LQ Newbie
 
Registered: Feb 2003
Location: Belleville, Ontario, Canada
Distribution: Fedora
Posts: 14

Rep: Reputation: 0
This is really funny because I did the updates today for Fedora and I'm getting the exact same error. I'm beginning to wonder if maybe the kernel update is corrupted and as a result, it won't allow you to boot into KDE or GNOME. The other thing that I noticed about this update was that when I restarted my PC, there are two options I can choose to boot into Linux. I have the 2174 update and the original 2115. Hope that sheds some light on this issue as well.
 
Old 02-25-2004, 09:11 AM   #8
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Original Poster
Rep: Reputation: 15
Hi Jeff_G_1974,
As far as having the various options on the boot menu, I have always had that.
Unless you delete them from your startup configuration in Grub they will appear.
That really isn't that big a deal except that (I have several options including the 2.6 kernel I compiled) I can't boot into ANY of them.
You might be right about the latest kernel source being corrupted. I wonder if this is happening to anyone else. In fact; what I even noticed during the up2date process was after I installed the latest kernel, I tried to update a few other things and I got an error saying that rpm was not able to unpackage some of these other updates due to an unpackage error.
Right after this happened is when I tried to reboot and that's when the problems started to happen.
If you come up with any ideas about how to correct this, please let me know.
Thanks
 
Old 02-25-2004, 10:00 AM   #9
WhatsHisName
Senior Member
 
Registered: Oct 2003
Location: /earth/usa/nj (UTC-5)
Distribution: RHL9;F1-10; CentOS4-5; DebianSarge-Squeeze
Posts: 1,151

Rep: Reputation: 46
This one may be hardware related. My Dell Precision 360 (2.8Ghz Pentium 4, 875 chipset) updated to FC1 kernel 2.4.22-1.2174.nptl (“.2174”) without a problem, but my Athlon system is having problems (see system configuration at end).

After struggling with the Athlon for a while, I gave up, repartitioned the drive and did a clean reinstallation of FC1. Actually, I am now on the fifth clean reinstallation (or maybe it’s the sixth, since I lost count) and have flushed out a few details from each round of trials.

After each repartitioning and reinstalling FC1:

(1) Updating (up2date) everything caused the problem to reappear upon reboot to .2174. (2) Updating only the kernel to .2140 (athlon) followed by updating everything else, resulted in a slightly different, but fatal problem on reboot to .2140. (3) Updating only the kernel to .2174 gave a fully functional system. Since the XFree86-4.3-55 update appeared at the same time as the .2174 kernel did and might be related to the failure, I then updated everything but the XFree86. The reboot to .2174 failed (locks up during the check for new hardware and stops at “bringing up loopback interface”). At some point I will try a few more variations of #3, but must get back to my life for now.

In case it’s a hardware-specific problem (i.e., failure at the hardware detect stage), here’s my Athlon setup:

Asus A7V600 motherboard
Athlon XP 3200+ processor (Barton)
1GB (2x512) DDR 400 Micron MT16VDDT6464AG-40BC4 DIMMS
Asus V9520 (nVIDIA GeForce FX) video adapter
1x200GB WesternDigital ATA/100 drive
2x200GB WesternDigital SATA drives currently as hardware RAID 1
(SATA drives not detected by FC1, but detected by FC2 test 1 (very buggy))
Linksys LNE100TX 10/100 NIC (onboard gigabit LAN not configured)
Onboard sound not properly configured yet

It’s a new system, but it ran under FC1 kernel 2.4.22-1.2140 for a couple of weeks.

Last edited by WhatsHisName; 02-25-2004 at 11:11 AM.
 
Old 02-25-2004, 11:19 AM   #10
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Original Poster
Rep: Reputation: 15
Thanks for your input WhatsHisName,

My system is an Athlon too. Here's the odd thing. I had no trouble with FC1 running on versions 2.4.22-1.2115, 2.4.22-1.2140 or 2.4.22-1.2149 and kernel 2.6.
I'm also running (on the same drive) w2k and an eval copy of 2003 server and I am able to access each. I also have a second drive running Slackware 9 (2.4.22). I'm able to access this as well.
I'm running xfree86 version 4.3.0 Is there something about this version (2149) that is causing this. From what it's beginning to seem like, this has something to do with xfree86. I was able to run kernel version 2.6 without any problems.
If worse comes to worse, I will just reinstall the OS but I wouldn't mind finding out what is causing this, so that I could avoid it in the future.
If anyone else has seen this and has any ideas please let me know.
Thanks
 
Old 02-25-2004, 12:54 PM   #11
RHELL
Member
 
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321

Rep: Reputation: 31
If anyone cares: init keeps trying to respawn a broken xdm process, then after some number of tries in 2min, goes into a wait for 5 min. Then tries again.

/var/log/Xfree86.log might have something useful.

What does startX do?

I would also 1 check the changelog, and 2 see which package owns the evil library(assuming you rpm'd the install)

code:
rpm -q --changelog [package name]

rpm -q -f libSM.so.6.0
code
 
Old 02-25-2004, 02:11 PM   #12
RHELL
Member
 
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321

Rep: Reputation: 31
Saw some references to Nvidia drivers needing to be updated after kernel upgrades.
Could this be you?
 
Old 02-25-2004, 02:48 PM   #13
WhatsHisName
Senior Member
 
Registered: Oct 2003
Location: /earth/usa/nj (UTC-5)
Distribution: RHL9;F1-10; CentOS4-5; DebianSarge-Squeeze
Posts: 1,151

Rep: Reputation: 46
Re: my previous post, a clean reinstallation of FC1 followed by updating the kernel to .2174, followed by updating XFree86 to 4.3.0-55, yields a functional system after rebooting. The list of other available updates is very long (too long to list here, but can be viewed at http://download.fedora.redhat.com/pu...pdates/1/i386/). So, working through the list to find the update triggering the failure(s) will take a while (days!).

Since I am looking for a failure and am not trying to make the system functional at this time, any suggestions regarding which updates might be causing the previously described failure(s) would be appreciated. To limit the options, please note that the test system is currently configured as a desktop (as defined by the FC installer).

And to quote Howard Dean, “Aggggggggggggggggggg!”
 
Old 02-25-2004, 03:07 PM   #14
mjp
LQ Newbie
 
Registered: Nov 2003
Distribution: Red Hat 9
Posts: 22

Original Poster
Rep: Reputation: 15
Rhell & WhatsHisName

Rhell

No, I don't have nvidia drivers. As far as your prior message, the only place I was able to see anything about an xdm process was at the bottom of the /etc/inittab file. Is this where you saw it or was there someplace else?
What is listed in /etc/inittab is "x:5:respawn:/etc/X11/prefdm -nodaemon".
I went to this file and there doesn't seem to be any indication of any error of any kind.
This is what is happening with init for me; where it tries a certain number of times and then waits 5 minutes.
As far as startx is concerned, other than it being a file listed in /usr/X11R6/bin, I'm assuming it just starts runlevel 5 and the xwindow system.
As far as changelog and libSM.so.6.0 that was a zero as well.
There isn't anything in the xfree86 logs to indicate any problem.
I'll have to see if there is anything in the init man pages and maybe try and poke around the net to see if there is any other issues I might try.
Thanks for your input.

PS: To WhatsHisName
Did you try and boot into the new kernel before you upgraded the XFree86 version to 4.3.55. My version of XFree86 is still 4.3.0. Do you think this might be a problem with this new kernel; a conflict with an older XFree86 version.
 
Old 02-25-2004, 05:41 PM   #15
WhatsHisName
Senior Member
 
Registered: Oct 2003
Location: /earth/usa/nj (UTC-5)
Distribution: RHL9;F1-10; CentOS4-5; DebianSarge-Squeeze
Posts: 1,151

Rep: Reputation: 46
mjp

Yes, the system was rebooted after upgrading the kernel to .2174 with the XFree86 4.3.0-42 supplied with FC1 and everything was OK. Likewise, upgrading XFree86 to 4.3.0-55 with kernel .2174 running the system and then rebooting worked fine, too.

Regarding the NVIDIA drivers, FC1 already contains support for my GeForce FX card. The video adapter also seems to work well with several of the other GeForce drivers. I know NVIDIA drivers can be a problem, but even the ones you can download from the NVIDIA site sound fairly generic to begin with. It strikes me that the ability to upgrade the kernel to .2174 and XFree86 to 4.3.0-55 would seem to rule out a NVIDIA driver problem.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora Core Dual Boot, and Problem with startx Sova aka Ruso Linux - Newbie 1 06-12-2005 11:57 AM
Problems with Fedora Core 1 mahfouz Fedora 3 11-16-2004 03:47 PM
Severe problems with Fedora Core 1 and Fedora Core 2 installatiom TheOneKEA Fedora - Installation 2 07-14-2004 02:12 PM
Fedora Core 2 Problems gamehack Fedora 3 06-15-2004 01:48 AM
Fedora core 2 problems isso Fedora 5 02-15-2004 06:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 08:18 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration