keesiewonder

Scoopy, I ran ldconfig -v, logged out and logged back in, and my PATH is the same.

This may be a clue for someone. I just looked at my environment variables with env. The next to the last one displayed has a similar error in it. _=/usr//bin/env I'm not sure what is setting this weird? environment variable, but bet it is the same program that messed up my PATH. And, bvc, here is /etc/ld.so.conf: /usr/X11R6/lib /usr/lib/qt3/lib

Somehow, sometime, I've messed up my PATH a bit and am trying to figure out where. What I've noticed is the PATH is always fine for root and is fine for susan at run level 3. At run level 5 (under either KDE or GNOME), it has an error in it that I'd like to fix. But I cannot figure out where it's getting its settings from. I theorize it has something to do with X initialization files ... but I have not been able to locate the culprit. Might there be possibilities other than X ... like other compiled programs? Do they alter the PATH sometimes? I do not have a .bash_login or a .profile file. /etc/passwd, /etc/profile, ~susan/.bash_profile and ~susan/.bashrc all seem fine to me. I'm running the shell from within KDE off the Terminal Sessions menu. run level 3 path: /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games run level 5 path: /usr//bin:/bin:/usr/bin::/usr/local/bin:/usr/X11R6/bin:/usr/games In run level 5, it sort of looks like some script tries to pre-pend to the run level 3 path, but loses the subdirectory name under /usr yielding /usr// . Perhaps a second script does the adding of the current directory evidenced by the :: Where do you think my PATH is getting messed up? What other .files do I need to check? Thanks for your thoughts.

How may I tell the order in which kernel modules are loaded? How may I find out which modules are loaded before the X Server starts?

I'm trying to make a boot floppy, but it doesn't fit on a 1.44 floppy. How do I work around this? Should I select one or more of the advanced preferences in drakfloppy? How can I make a boot CD rather than a boot floppy? Other, better, suggestions?

Kernel output in my syslog file suggests I report my system and BIOS to http://linux.dell.com/edd/results.html . I'd like to do this, but am not Linux fluent enough to understand the instructions there or on the other web sites I find if I do a Google search on CONFIG_EDD. Would someone here please elaborate a bit?

I have upgraded to kernel 2.6.3.1, booted to it, and issued a logout from KDE's menu, and the logout procedure did fully poweroff the machine. So the trick for me for my original problem seems to be solved by the most recent kernel. I now have some issues with booting through LILO. The default is currently my old linux kernel version, which will no longer boot. So, I'd like to change the default to be the new linux kernel version, currently the last item on the lilo boot menu. How do I specify the default boot option? How do I delete the malfunctioning boot option? I know there is a lilo.conf file ... May I just alter the order of the sections in there? I've messed this up before and ended up not being able to boot to either Linux or Windows and had to resort to luckily fixing things with Partition Magic ... I'd rather not go down this path again.

The ftp source referenced works fine and when I searched for kdeutils, I found packages to install. (KLaptop alone found nothing, so I assume you must get kdeutils as a set.) I installed kdeutils and think I have some new menu options ... but I supsect the kdeutils module does need to be compiled since I get an error message "There was an error loading the module. The diagnostics is: Library files for libkcm_laptop.la" not found in paths ........." If kdeutils does need to be compiled ... I too don't know how to do that ... I'm also concerned that this pursuit of kdeutils is not relevant ... i.e. the laptop module in kdeutils may deal only with laptop battery issues ... which is not my current problem. I always use AC since the battery has always been useless.

No problem about missing some info in my posts ... I'm wordy which can be a problem for lots of folks. And I'll probably still have this shutdown problem by the time you again have access to Linux. While I haven't acted on your most recent post, I checked my BIOS again and still see nothing directly referring to the kind of power management I'm using. I do have the most recent BIOS for my machine: Inspiron 8100 FlashBIOS Version A15. I cannot figure out how to tell more about my power management from Linux, but from Win XP I only find references to ACPI ... so I assume that is what I'm using. ACPI is more recent than APM, isn't it? So, you think the KLaptop module is a good idea, and that I should shut off Display Power Management in KDE? Should I also shut it off in the BIOS then? Or leave it as is for Win XP?

1. Doesn't the last line of my /etc/sysctl.conf file already enable kernel.sysreq? 2. I looked at my BIOS Power Management values for AC. Brightness: maximum Power Management: enabled Display Time Out: disabled Disk Time Out: disabled (I cannot alter this) Suspend Time Out: disabled SD2 Time Out: disabled Smart CPU: disabled Display Close: active Anything out of order in the above? 3. KDE Menu - Configuration - KDE - PowerControl - Display Power Control tells me that Enable Display Power Management is on and the number of minutes before standby, suspend and power off occur. I thought to look at Help ... and noticed a Tip that said to NOT use this module for laptops but to install kdeutils and refer to the Laptop Power Control Center. (I have not yet disabled this option.) I had a hard time determining whether kdeutils was already installed on my machine. I finally found a reference in the KDE Help Center - Chapter 18 - Utility Applications. There is a module called KLaptop. A ftp location is referenced: ftp.kde.org/pub/kde/stable/latest/distribution/stable When I try to access this, I receive a message that the file/directory does not exist. 4. How do I figure out whether I'm using ACPI or APM for power management. I didn't see anything in the BIOS ... I'll look there again.

Arthur, I'm confident your advice will work soon for me. I am thoroughly impressed with the speed and completeness with which Mandrake forum users respond to help one another. If I understand your suggestions, here are the results. Typing poweroff from a Konsole when I previously was running logout off of KDE's menu seems to yield the exact same result as I originally reported. Screen goes blank, status light stays on. Issuing <crtl>-<alt>-<backspace> at the moment when I was previously running logout off of KDE's menu appears to restart KDE. Issuing <crtl>-<alt>-<backspace> once the screen has gone blank and the status light remains on seems to do absolutely nothing. I read the Magic SysRq Key thread to which you referred me and printed it out. When my laptop was in its mode of screen blank, status light on after running poweroff or KDE's logout, I tried the SysRq sequence mentioned once and feel I was indeed using all 3 keys simultaneously each time. The sequence appeared to do nothing. I include the contents of my /etc/sysctl.conf below. (Sorry, I haven't figured out yet how to put this in 'code' format for forum messages.) This has kernel.sysrq enabled, doesn't it, per the last line of the file? Or, should I uncomment the line #kernel.sysrq = 0 and edit the 0 to a 1? *** beginning of /etc/sysctl.conf file *** # Kernel sysctl configuration file for Mandrake Linux # # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 0 # Disables IP dynaddr net.ipv4.ip_dynaddr = 0 # Disable ECN net.ipv4.tcp_ecn = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Controls the System Request debugging functionality of the kernel #kernel.sysrq = 0 # Controls whether core dumps will append the PID to the core filename. # Useful for debugging multi-threaded applications. kernel.core_uses_pid = 1 net.ipv4.icmp_ignore_bogus_error_responses=0 net.ipv4.conf.all.rp_filter=0 net.ipv4.icmp_echo_ignore_broadcasts=0 net.ipv4.icmp_echo_ignore_all=0 net.ipv4.conf.all.log_martians=0 kernel.sysrq=1 *** end of /etc/sysctl.conf file ***

I'm using Mandrake version 9.2. I thought this was in my signature file.

When I issue a logout from KDE's main menu and opt to turn off my Dell Inspiron 8100 laptop, the screen goes blank and the status light stays on. I know it is still on as I continue to hear the fans now and then. If I really want the machine to shut off, I need to hold the power button down for several seconds. 1. How do I change KDE so that logging out of KDE exits KDE and exits X but leaves me at the command line prompt so I may be in a better position to figure out what is going on? 2. What mode is the laptop in as described in the first paragraph above? How should I resume operation from this mode? Is it okay to power off from this point? 3. What do I need to do to get a real, clean, complete shutdown on my system? It seems like KDE is not doing it properly. I sense my problem is similar to http://www.MandrakeUsers.org/index.php?showtopic=9691 but I'm not quite experienced enough to determine exactly what to do, even with the text in this thread. I also gather that which kernel I'm using may be relevant. uname -a yields: Linux altered.net 2.4.22-10mdk #1 Thu Sep 18 12:30:58 CEST 2003 i686 unknown unknown GNU/Linux Thanks for your help.

Last night I ran Mandrake Update and Install for everything. Since things seemed to be working fine, I shut the system down for the day, turned it on today after work, and found that my network connection was gone and that I no longer had an option to open a Konsole window from the K Start Applications. How is this possible? I wouldn't expect a software update to alter network settings or menu options ... Would you? I finally figured out how adjust the network configuration so I can connect to the Internet again via my cable modem. I have not been able to figure out how to get a menu option back for a console window. I know there's a utility Menudrake ... but I shouldn't have to use that to get a console, should I?

To use http://urpmi.org/easyurpmi/index.php, I need to know my system's architecture. Choices included at urpmi.org include alpha, i586, ia64, ppc, x86_64. How do I figure this out? My processor is an Intel Pentium III Mobile CPU 1133 MHz.