Slackware This Forum is for the discussion of Slackware Linux.
|
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
01-21-2006, 07:20 AM
|
#1
|
Member
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89
Rep:
|
Downgrade to 2.4.33 -> KDE can't start
Slackware 10.2, happily using kernel 2.6.13 After downgrade to kernel 2.4.33, the inittialization went through normally until KDE starts (I use ini4 for graphical login) KDE complains that "Could not read network connection list Please check that the dcopserver program is running" After clicking OK another dialog appeared saying Home directory is not accessible and finally dump me in text mode with no prompt and I have to reboot.
Thanks
|
|
|
01-21-2006, 11:52 PM
|
#2
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Try booting in single-user mode and check whether all
device-nodes are present (for starters). Which file-
systems did you compile into your kernel?
Cheers,
Tink
|
|
|
01-21-2006, 11:57 PM
|
#3
|
Member
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89
Original Poster
Rep:
|
Quote:
Originally Posted by Tinkster
Try booting in single-user mode and check whether all
device-nodes are present (for starters). Which file-
systems did you compile into your kernel?
Cheers,
Tink
|
can't remember which exactly, could it be that I compile the wrong type of file system support which is the cause of the problem? currently I'm using ext3 for all of my partitions.
|
|
|
01-22-2006, 02:37 PM
|
#4
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Well, it *IS* a possibility... if /home was on a separate partition,
and you didn't compile support for its file-system you may get
messages like that - after all the .DCOP stuff is being created in
~ ...
Cheers,
Tink
|
|
|
All times are GMT -5. The time now is 11:36 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|