You are not logged in.
I've installed KDE 3.2 several times with as many different configurations as I can imagine, but I dont' seem to be able to get it to start very quickly under Arch 0.6 (Widget). The desktop WILL finally display and (more or less work), but only after 10 minutes or so. The machine I'm running is a Pentium 4 2.53 Ghz with 512 Mb RAM, so ithis is not a power issue. In any case, I have gotten 3.2 to run perfectly well under Slackware and Librfanet on this machiine without a hitch.
I've done a simple install (with only kdelibs and kdebase) and a full install, both with the same results.
Does anyone have any suggestions or recommendations fo rthings to try?
Thanks.
Win
Is your hostname listed properly, pointing back to localhast, in /etc/hosts?
Stated another way: do you have the proper entry in /etc/hosts? It has to have localhost and your hostname there.
Also, is your loopback (lo) device set up properly?
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
Hi xentac.
Thanks for the prompt and successful recommendation.
I was totally amazed to find that the loopback device was not up.
Where in Arch Linux should the loopback device be brought up? For the time being, I'm doing this in rc.local, but that is surely inappropriate.
II didn't notice anything specific in rc.sysinit or rc.multi.
Thanks again for the prompt help!
Win
In your rc.conf file. You configure all of your network devices there, including lo.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
if you run "fam" from /etc/rc.conf DAEMONS, the File alternation monitor, it will speed up kde a little
note: kde3.2 is full of "features" and that's why it has momentum starting
The impossible missions are the only ones which succeed.
Offline
Thanks xentac and dp.
Thanks again for your prompt and helpful suggestions.
I originally through the problem was with "fam," too. But it was plain boneheadedness: I had not set up the boot sequence properly and "lo" was not being brought up. I had the proper "lo" setting in rc.conf, but didn't start both "lo" and "eth0" using "network". I was starting "eth0" using "dhcpcd" alone. After straightening out "rc.conf" and "rc.local," things are running swimmingly (well, there ARE still a few more details to iron out ...).
Win
I also have this problem. Slow KDE startup and I see the "resolving xyz.com/net/org" for far too long in Firefox.
I'm running DHCP (IP assigned to me is always 192.168.1.100), btw, and my /etc/hosts file looks like this:
127.0.0.1 localhost
192.168.1.100 jester.rogers.com jester
Is that right?
Would it matter that in my /etc/rc.conf that ROUTES is empty?
Right now part of my /etc/rc.conf file looks like this:
HOSTNAME="jester"
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
DAEMONS=(syslogd klogd !pcmcia network netfs crond)
Offline
Your /etc/hosts file will work if your IP is always .100. Usually you'll just set your hostname to be 127.0.0.1... that always is you
Apart from that, I don't know... check your logs?
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
True.
I checked my /etc/hosts on my Slack laptop and set it the same as that (except I changed the hostname), but there was still no difference.
I guess I need to learn how to look at logs.
Which one should I be looking at? I'm a total n00b when it comes to that.
/var/log/syslog?
Well... I guess I'll go through everything. 8)
Offline
bump.
ARgh. This is @*%!@$*# frustrating! :x
I really don't know what to do at this point.
The KDE startup isn't a problem. It just doesn't resolve anything for at least 10 seconds.
Offline
For me I had to recompile the kernel and disable anything to do with IPv6.
My Linksys router was having a whale of a time resolving anything (10-20 sec delays). But when I did this, everything started running as smooth as silk.
Hope this helps
Daniel
Offline
So the stock Arch 2.6.5 kernel has IPv6 compiled in?
Ah, that makes sense! 8) (I have a Linksys router, too)
I've seen a ton of people complaining about that on the Gentoo forums.
I'll give that a shot the moment I have a chance.
It's strange that I was getting this problem on my Gentoo laptop with IPv6 NOT compiled in.
What ended up fixing it was setting
#domainname rogers.com
(Rogers is my ISP)
Anyway, thanks.
Offline
Update for anyone who cares :
I re-compiled the kernel without IPv6 and it runs perfectly now. Thanks.
Offline
Try changing:
ROUTES=(!gateway)
to:
ROUTES=(gateway).
That is what I have, and it works just fine with a stock kernel.
Offline
after adding lo to INTERFACES i could use k3b without having to wait forever and a day, but i don't understand
sorry for the near insulting ignorance but, what is the function of the loopback thing and why would KDE need to it start timely
Offline
loopback is needed for accessing the localhost running services
eg. samba cups etc.
Offline
oh :oops: makes sense
thanks
Offline
Update for anyone who cares :
I re-compiled the kernel without IPv6 and it runs perfectly now. Thanks.
Sorry to sound like a newb, but where in the world is this option? I've looked through menuconfig, xconfig, and gconfig, and I thought I saw it once, but I can't find it anymore. Thanks.
Offline