Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
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.
Hi there guy's. A month or so ago I posted this thread .
As you can read I had (and still have) problems shutting down my machine. I don't know what to do about this. I have installed the proper nVidia drivers, but this didn't help. Here is my XF86config file:
# /.../
# SaX generated XFree86 config file
# Created on: 2002-10-03.
#
# Version: 4.3
# Contact: Marcus Schaefer <sax@suse.de>, 2001
#
# Automatically generated by [SaX2] (4.3)
# PLEASE DO NOT EDIT THIS FILE!
#
Does any one see anything wrong here ? Also, in the nVidia readme file, I read that stability problems could be AGP related. Here is the related section :
If you are experiencing AGP stability problems, you should be aware of
the following:
o Support for the processor's Page Size Extension on Athlon Processors
Some linux kernels have a conflicting cache attribute bug that is
exposed by advanced speculative caching in newer AMD Athlon family
processors (AMD Athlon XP, AMD Athlong 4, AMD Athlon MP, and Models 6
and above AMD Duron). This kernel bug usually shows up under heavy use
of accelerated 3D graphics with an AGP graphics card.
Linux distributions based on kernel 2.4.19 and later *should*
incorporate the bug fix. But, older kernels require help from the user
in ensuring that a small portion of advanced speculative caching is
disabled (normally done through a kernel patch) and a boot option is
specified in order to apply the whole fix.
Nvidia's driver automatically disables the small portion of advanced
speculative caching for the affected AMD processors without the need
to patch the kernel; it can be used even on kernels which do already
incorporate the kernel bug fix. Additionally, for older kernels the
user performs the boot option portion of the fix by explicitly disabling
4MB pages. This can be done from the boot command line by specifying:
mem=nopentium
Or by adding the following line to etc/lilo.conf:
append = "mem=nopentium"
o AGP drive strength BIOS setting (Via based mainboards)
Many Via based mainboards allow adjusting the AGP drive strength in
the system BIOS. The setting of this option largely affects system
stability, the range between 0xEA and 0xEE seems to work best for
NVIDIA hardware. Setting either nibble to 0xF generally restults in
severe stability problems.
If you decide to experiment with this, you need to be aware of
the fact that you are doing so at your own risk and that you may
render your system unbootable with improper settings until you
reset the setting to a working value (w/ a PCI graphics card or
by resetting the BIOS to its default values).
o System BIOS version
Make sure to have the latest system BIOS provided by the board
manufacturer.
o AGP Rate
You may want to decrease the AGP rate setting if you are seeing
lockups with the value you are currently using. You can do so
with the NVreg_ReqAGPRate NVdriver module parameter.
If you are inserting the module manually:
insmod NVdriver NVreg_ReqAGPRate=2 # force AGP Rate to 2x
insmod NVdriver NVreg_ReqAGPRate=1 # force AGP Rate to 1x
If you are using modprobe (/etc/modules.conf):
alias char-major-195 NVdriver
options NVdriver NVreg_ReqAGPRate=2 # force AGP Rate to 2x
options NVdriver NVreg_ReqAGPRate=1 # force AGP Rate to 1x
On Athlon motherboards with the VIA KX133 or 694X chip set, such as the
ASUS K7V motherboard, NVIDIA drivers default to AGP 2x mode to work around
insufficient drive strength on one of the signals. You can force AGP 4x
by setting NVreg_EnableVia4x to 1. Note that this may cause the system
to become unstable.
On ALi1541 and ALi1647 chipsets, NVIDIA drivers disable AGP to work
around timing issues and signal integrity issues. You can force AGP
to be enabled on these chipsets by setting NVreg_EnableALiAGP to 1.
Note that this may cause the system to become unstable.
But this is all rather criptic to me, and I don't want to do anything wrong here. I could get in to big trouble. Could any one help me ?
My system specs are listed in the thread I pointed to at the beginning of this message
And a nother thing, I tried giving the "mem=nopentuim" option to lilo. It didn't work
i assume you did rerun lilo afterwards ? and you actually
typed mem=nopentium and nopentuim is a typo here and not in your lilo.conf ?
To check do dmesg|less and see what is after;
Kernel command line:
I have to use it to keep my X stable, and i do have an
AMD inside. My errors without it were; total freeze up in
X whilst doing certain opengl things games, blender etc.
From your previous thread i understand that you are quite
sure it is an X related shutdown error.
Maybe go into runlevel 3 before shutting down;
go to console
be root
type; telinit 3
then; shutdown -h now
I had an issue concerning the loginmanager kdm, i use
gdm now instead ; the problem related to falling back to
runlevel 3 in every 10-20 boot up.
good luck
Yes, the "mem=nopentuim" thing is a typeo (I know I did it again).
I have tried giving the command to lilo directly at boot-up and after that I edited the lilo.conf file. I didn't forget to run lilo.
Do be frank, I am not absolutely sure that it is X thats causing the problem. Are you familiar with suse ? If you are you might have seen that the first console in suse (you know, the one excesible with cnrl-alt-f1) is semi-graphical. It's not X, but you do see nice pictures of tux for instance. I think I have trouble getting I or out if that console. Cos in very rear cases the problem has occurd when I was just switching to that console.
I hope you have a good picture in your mind on how the fist suse console looks like. Some one told me it woks via a frame-buffer device, but I have no clue on what that is.
Appreciate the reply. Could you help me some more ?
Well if it happens whenever you switch to the first console then it could very well be problems with the frame buffer device. Since you work in graphical mode you probably won't have any benefit from it, except watching the nice little penguin when it boots up. So why don't you try compiling a kernel without frame buffer support. You can turn it off in the Console drivers section of the kernel configuration.
He, thanks man. Is there any way of just turning off the frame buffer device ?
I am planing to re-compile my kernel any way, even if it isn't possible, no problem
I have SuSE 8 running on five machines, four of them different hardware. I have observed what might be the same problem. When trying to either log off or shut down they will sometimes hang after sending the terminate signal. The screen changes slightly, the panels either disappear or at least change. And it is generally not responsive to the mouse or the keyboard.
With one exception: I can always C-M-F3 and log on a text screen, then do a ps -A and start killing what I'll call "high level" processes which will invariably be still running. For example, there seems to be a bug in acroread which will leave a process running in the background which will hang up the shutdown process until it is killed. Some applications like nautilus, opera, konqueror, etc, if left running when attempting to log off or shutdown, will also hang it up. All I have to do though, is kill them and it goes on and completes its process.
Since then I just make sure I have nothing but terminal windows open when I log off or shut down. It would be nice to not have to do this, however. (It would also be really nice if terminal windows would open back up to the paths they were at when they were shut down!).
He he he, thanks a million jkcunningham. Now I won't have to hard reboot my machine any more. By the way, How dit you know that you must press C-M-F3 ?
I thinks it's realy bad that prog. keep on running on the background and cause system's to hang. They sould realy disign there apps better.
Again man thanks. mrGee and Mik, also many thanks to you.
In case anyone's interested: I recently installed SuSE 8.1 and so far have not seen a recurrance of this logout problem, no matter what I've had up and running at the time. Its a definite improvement. Now, if they would just put Octave back into the distro I would be completely happy....
-Jeff
Hi there,
What do you mean Ciccio? I can't even get to a console when this happens. Any way, I doesn't matter any more. I switch to another distro. I'm using debian now. I don't know if it will solve the problem though. I'f only been using it for a couple of day's. If it does'nt, well then you'l see a grown man cry. ()
O and a completly different thing, how do you people edit the info you see in the box to the left here. It say's "Distribution: SuSE" How do you change that?
And another thing. pushing C-M-F3 did'nt work for me. Maby it's because i was using suse 7.3 and you were talking about 8.0
Ok I meant before shutting down your system switching to a console (ctrl + alt + F1) and AS ROOT typing init 1 (for Single User) and then a command like poweorff (don't know if it works in suse)
Debian, as far as I know, is one of the best distros... but if you are looking fore something a little bit more user-friendly then you should try Mandrake 9.0 with kde3.0
IMHO MDK9.0 with KDE3.0 has an excellent balance between the features of UNIX and the user-friendlyness of a full graphical OS (like MacOS or Windows). And you can always use the console mode for certain operations that can only be done from there (or that it is faster to do so)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
