Re: [newbie] Shutdown problem

[Tom Brinkman]

On Saturday 11 December 2004 03:50 pm, RickSisler wrote:
 Also drawing from your experience,
 wouldn't *dmidecode* be of use in this case to see what a bios
 supports ?

 The reason I ask, IIRC ..was of a post about what the bios
 reporting information, on this list or the expert list ..
 arrgh ..can't find the link now 8( sorry for asking another
 question.

 Thanks Tom,
 you helped me find out my MB supported local apic for 9.2, thru
 lurkin, since I was having stability problems then.

 As I understand it 'dmidecode' just reads what is programmed 
into the bios chip by the vendor.  Since much hardware is 
designed and marketed for Windoze, it may not be entirely 
accurate.  EG, dmidecode returns that the motherboard supports 
ACPI and APIC.  All this probly means is M$ non-standard and 
non-compliant ACPI and APIC is supported.  I haven't run Win$ux 
in years and not since W98, but I do know for a fact ACPI wasn't 
standards compliant then, and was handled in software thru a 
registry hack to work with Winblows.

About all you can do with Linux is to try trial'n error to see 
if your hardware will get along with the various bios 
capabilities that dmidecode reports.  Complicated with the 
variables of different bios manufactures and bios settings. The 
combo of bios, hardware, and OS configuration variables can be 
very problematic, almost completely overwhelming.

   As always, hardware is a moving target, best researched prior 
to purchase an use, the latest and greatest avoided, and (rave) 
hardware reviews on prominent Web hardware sites taken with a 
grain of salt.  Specially when the testbed OS is Windoze.  LKML, 
cooker, and other distro development ML's are helpful as is 
Google/linux and as such should be given the greatest weight.

 FWIW, currently I'd look for an Award bios board, with a VIA 
chipset. Next would be SiS, last would be nForce*, as a starting 
point.  Intel chipsets, I only have my own research to go by as I 
haven't used Intel in quite a while (P3 - BX was the last one). 
Seems the latest ones (about 6 months old) are best supported 
tho.

 There's only one, more certain solution.  Don't use desktop 
or laptop hardware. Buy expensive production server kit designed 
to run Un*x ;)
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[RickSisler]

Tom Brinkman ([EMAIL PROTECTED]) wrote:
 On Saturday 11 December 2004 03:50 pm, RickSisler wrote:
  Also drawing from your experience,
  wouldn't *dmidecode* be of use in this case to see what a bios
  supports ?
 About all you can do with Linux is to try trial'n error to see 
 if your hardware will get along with the various bios 
 capabilities that dmidecode reports.  Complicated with the 
 variables of different bios manufactures and bios settings. The 
 combo of bios, hardware, and OS configuration variables can be 
 very problematic, almost completely overwhelming.
 
As always, hardware is a moving target, best researched prior 
 to purchase an use, the latest and greatest avoided, and (rave) 
 hardware reviews on prominent Web hardware sites taken with a 
 grain of salt.  Specially when the testbed OS is Windoze.  LKML, 
 cooker, and other distro development ML's are helpful as is 
 Google/linux and as such should be given the greatest weight.
 
  FWIW, currently I'd look for an Award bios board, with a VIA 
 chipset. Next would be SiS, last would be nForce*, as a starting 
 point.  Intel chipsets, I only have my own research to go by as I 
 haven't used Intel in quite a while (P3 - BX was the last one). 
 Seems the latest ones (about 6 months old) are best supported 
 tho.
Thanks Tom for sharing your knowledge, I started to really get into
these kernels doc's and howto's. Quite a load of material to cover.
Funny you should say nForce I have an nForce2 now working well with
an AMD Athlon although it seems the most stable with local APIC added
to lilo append line.
  There's only one, more certain solution.  Don't use desktop 
 or laptop hardware. Buy expensive production server kit designed 
 to run Un*x ;)
g Well, if I hit the lotto someday, 
I'd buy one for everybody ;)

Thanks again Tom
-- 
RickS  Registered Linux user #338463
Mdk 10.1 OE - Linux 2.6.8.1-12mdk@ http://counter.li.org

gpg --recv-keys --keyserver www.keyserver.net 0x24AABE61


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem (update)

[Keith Powell]

Things have changed regarding my shutdown problem, but have got even more 
confusing.

But first, I have just connected for the first time today, to get my e-mails 
and postings. I have found that there is nothing from the list between about 
eight o'clock last night (GMT, or UTC) and mid-day today. I have no idea 
where any postings between those times have gone to, so if anyone has been 
kind enough to send me a reply, I am afraid that it has gone :(  I'll look 
in the archives to see if I can find the missing postings.

I have been busy trying to sort things.

I have installed several distributions in turn, on my spare hard drive to see 
what shutdown problems there are with other distros. There were none with two 
of them, so I installed Mandrake10.0 Official. 

That gave me the choice of several boots:

Linux (no shutdown problems)
Linux-smp (wouldn't shut down)
linux-nonfb (no shutdown problems)
263-7 (no shutdown problems)
Failsafe and floppy, which I didn't test.

Before, with 10.0, I have only had the choice of Linux, 263-7, failsafe and 
floppy.

So, I did a clean installation of 10.1.

That gave me the choice of:

Linux (wouldn't shut down)
Linux-nonfb (wouldn't shut down)
Failsafe and floppy 

So, I am back to 10.0 on my spare hard drive to send this, and will use that 
unless someone could please give me some advice about the work-around 
needed with 10.1. Does it still look like hardware problems?

By the way, sorry if I went a bit over the top last night, but I was tired 
and the information I was given was a real blow. I had only got my new 
computer the previous day.

Any help will be very gratefully received.

Thanks

Keith


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem (solved)

[Keith Powell]

On Saturday 11 Dec 2004 16:14, Keith Powell wrote:
 Things have changed regarding my shutdown problem, but have got even more
 confusing.

 I have installed several distributions in turn, on my spare hard drive to
 see what shutdown problems there are with other distros. There were none
 with two of them, so I installed Mandrake10.0 Official.

 That gave me the choice of several boots:

 Linux (no shutdown problems)
 Linux-smp (wouldn't shut down)
 linux-nonfb (no shutdown problems)
 263-7 (no shutdown problems)
 Failsafe and floppy, which I didn't test.

 Before, with 10.0, I have only had the choice of Linux, 263-7, failsafe and
 floppy.

 So, I did a clean installation of 10.1.

 That gave me the choice of:

 Linux (wouldn't shut down)
 Linux-nonfb (wouldn't shut down)
 Failsafe and floppy


This is bordering  on being ridiculous!

I have run the Mandrake10.1 (the one in which I had to edit 
the  /etc/lilo.conf  file append line to get it to shut down), which is 
installed on my main hard drive.

As an experiment, I re-edited its lilo.conf file, replacing apic=off with the 
default apic=ht. Then I ran lilo. It now shuts down correctly! But it 
definitely didn't when there was  apic=ht  in the append line when it was 
installed. 

I wonder if re-running lilo sorted out an installation problem? I'm probably 
wrong.

Cheers

Keith


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[RickSisler]

Tom Brinkman ([EMAIL PROTECTED]) wrote:

snip

 I appreciate the addition Rick.  Let me take this opportunity 
 to add a caution to your post, but more so to previous replies I 
 sent in this thread. 
 
   ** Unless you know what you're doing, don't edit kernel config 
 files by hand and then compile a kernel **
 
 I do, but then I'm a reckless idiot ;   Many of y'all have 
 run 'make menuconfig' or 'make xconfig' and noticed that when you 
 changed somethin, some, sometimes many other options either were 
 greyed out (disabled), or became enabled.
Great advice, as always, I haven't had the guts to try to compile 
a kernel yet. Although I did just get an older box to break/test/
learn with. g

 This automatically protects you against setting conflicting 
 compile options, and/or automatically presents others 
 appropriately.  This protection is not afforded if you edit 
 kernel configs manually.
 
Still as Rick has very well illustrated, you should take a look 
 and get familiar with the kernel options, features, and 
 capabilities which are Linux. The very heart of your system, and 
 a good place to begin diagnosing peculiar problems. A little 
 knowlege in this basic area will lead you to other involved 
 processes, like various init functions that have a lot to do with 
 booting up, or shutting down, and everything in between.
 -- 
   Tom Brinkman Corpus Christi, Texas
Proud to be an American
Also drawing from your experience,
wouldn't *dmidecode* be of use in this case to see what a bios
supports ? 

The reason I ask, IIRC ..was of a post about what the bios reporting
information, on this list or the expert list .. 
arrgh ..can't find the link now 8( sorry for asking another question.

Thanks Tom,
you helped me find out my MB supported local apic for 9.2, thru
lurkin, since I was having stability problems then.

-- 
RickS  Registered Linux user #338463
Mdk 10.1 OE - Linux 2.6.8.1-12mdk@ http://counter.li.org

gpg --recv-keys --keyserver www.keyserver.net 0x24AABE61


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Kaj Haulrich]

On Saturday 11 December 2004 07:03, Tom Brinkman wrote:
 On Friday 10 December 2004 09:37 pm, care free wrote:
  I wonder if it is acpi=on or set you acpi on in your bios
 
  J.T.

According to past and present kernel-parameters.txt,  acpi=on
 is _not_ a valid option.
   ...
 acpi=  [HW,ACPI] Advanced Configuration and Power Interface
Format: { force | off | ht | strict }
 force -- enable ACPI if default was off
 off -- disable ACPI if default was on
 noirq -- do not use ACPI for IRQ routing
 ht -- run only enough ACPI to enable Hyper Threading
 strict --  Be less tolerant of platforms that are not
  strictly ACPI specification compliant.

 See also Documentation/pm.txt, pci=noacpi

 acpi_sleep= [HW,ACPI] Sleep options
 Format: { s3_bios, s3_mode }
 See Documentation/power/video.txt

 acpi_sci=   [HW,ACPI] ACPI System Control Interrupt
  trigger mode
 Format: { level | edge |  high | low }

 acpi_irq_balance[HW,ACPI] ACPI will balance
 active IRQs default in APIC mode

 acpi_irq_nobalance  [HW,ACPI] ACPI will not move
  active IRQs (default)
 default in PIC mode

 acpi_irq_pci=   [HW,ACPI] If irq_balance, Clear listed
  IRQs for use by PCI
 Format: irq,irq...

 acpi_irq_isa=   [HW,ACPI] If irq_balance, Mark listed
 IRQs used by ISA
 Format: irq,irq...

 acpi_osi=   [HW,ACPI] empty param disables _OSI

 acpi_serialize  [HW,ACPI] force serialization of AML
 methods

 acpi_skip_timer_override [HW,ACPI]
 Recognize and ignore IRQ0/pin2 Interrupt
 Override.
 For broken nForce2 BIOS resulting in
 XT-PIC timer.
   ...

  This is the mesg about ML/twiki type opinions and advice I'm
 tryin to make known.  acpi=on   doesn't exist or is purposely
 neglected and undocumented.  In either case it's almost certain
 to be ignored by the kernel and have no effect, or possibly an
 unintended one.

  Be concerned about ACPI tho. It's becoming most important on
 current systems where more than the original 15 IRQ's and IRQ
 sharing is needed.  IMO, if you need to add 'acpi=any of the
 options listed in kernel-parameters.txt' to your kernel, what
 you really need to add is better and standards compliant hardware
 to your system.  The facts are available before you purchase,
 only opinions afterwards.

  APIC isn't all that big a fsck'n deal. Nice to have, might
 add a slight touch of performance to ACPI IRQ handling.

  This thread is the last of me being an ogre about advice and
 opinions as gleaned from ML's and twiki's when it's contrary to
 past and current developer's and maintainer's documentation.

  Probly why after years, I hardly post anymore.

Tom, two things :

1. I sincerely apologize for having ignited your ire by posting an 
inaccurate and amateurish anwer to Keith's shutdown question.

2. I certainly will become very depressed if you reduce your 
activity here on the newbie list.  In fact, you are a leviathan to 
most of us newbies.  Admittedly, the newbie list and the twiki are 
not authoritative manuals or documentation, but merely opinions and 
experiences.  Nevertheless they provide tremendous help for most 
newbies, especially when somebody like you are willing to inject 
some corrections and wisdom.  Your above quoted words are a proof 
of just that.

Kaj Haulrich. 
-- 
*sent from a 100% Microsoft-free workstation*
 * http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2.6.8*


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem (update)

[Kaj Haulrich]

On Sunday 12 December 2004 06:01, Keith Powell wrote:

snip
 Also, there are no Newbie archives for December.
 So I can't check there.
/snip

Keith, there are more than one archive. Try here :

http://www.mail-archive.com/newbie@linux-mandrake.com/maillist.html

Kaj Haulrich.
-- 
*sent from a 100% Microsoft-free workstation*
 * http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2.6.8*


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem (update)

[care free]

I know the frustration.  I don't know why mdk10.1 does not turn off you 
computer.  I have an Athlon 800Mhz box with a very buggy FD11 mobo, and 
mdk10 turns it off after shut down, but not rh9 or any of Fedora Cores.  Rh9 
says that my bios has a way too old acpi, so it turns off that function 
automatically.  I wonder if it has anything to do with the bios.

J.T.
From: Keith Powell [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [newbie] Shutdown problem (update)
Date: Sat, 11 Dec 2004 16:14:26 +
Things have changed regarding my shutdown problem, but have got even more
confusing.
But first, I have just connected for the first time today, to get my 
e-mails
and postings. I have found that there is nothing from the list between 
about
eight o'clock last night (GMT, or UTC) and mid-day today. I have no idea
where any postings between those times have gone to, so if anyone has been
kind enough to send me a reply, I am afraid that it has gone :(  I'll 
look
in the archives to see if I can find the missing postings.

I have been busy trying to sort things.
I have installed several distributions in turn, on my spare hard drive to 
see
what shutdown problems there are with other distros. There were none with 
two
of them, so I installed Mandrake10.0 Official.

That gave me the choice of several boots:
Linux (no shutdown problems)
Linux-smp (wouldn't shut down)
linux-nonfb (no shutdown problems)
263-7 (no shutdown problems)
Failsafe and floppy, which I didn't test.
Before, with 10.0, I have only had the choice of Linux, 263-7, failsafe and
floppy.
So, I did a clean installation of 10.1.
That gave me the choice of:
Linux (wouldn't shut down)
Linux-nonfb (wouldn't shut down)
Failsafe and floppy
So, I am back to 10.0 on my spare hard drive to send this, and will use 
that
unless someone could please give me some advice about the work-around
needed with 10.1. Does it still look like hardware problems?

By the way, sorry if I went a bit over the top last night, but I was 
tired
and the information I was given was a real blow. I had only got my new
computer the previous day.

Any help will be very gratefully received.
Thanks
Keith

Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Kaj Haulrich]

On Friday 10 December 2004 11:37, Keith Powell wrote:
 I KNOW that this has been asked before, but I can't find the
 answer in the archives or in twiki. Sorry for asking it again.

 I have a new machine, and now, when I close down, everything
 closes down correctly, but then Mandrake does not actually switch
 the computer off.

 If I remember correctly, there is something to change in the
 lilo.conf file, but I can't remember what it is - not having
 needed it before.

 Please, what is it?

 Many thanks

 Keith

In /etc/lilo.conf try editing the append-line, especially the apic 
thing. Remove it completely or set it to apic=ht or noapic.

HTH
Kaj Haulrich.
-- 
*sent from a 100% Microsoft-free workstation*
 * http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2.6.8*


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Margot]

Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I KNOW that this has been asked before, but I can't find the
answer in the archives or in twiki. Sorry for asking it again.
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to change in the
lilo.conf file, but I can't remember what it is - not having
needed it before.
Please, what is it?
Many thanks
Keith

In /etc/lilo.conf try editing the append-line, especially the apic 
thing. Remove it completely or set it to apic=ht or noapic.

HTH
Kaj Haulrich.
Kaj, I think you're mixing up apic and acpi!
The options for apic include noapic and/or nolapic. The options for 
acpi include acpi=on, acpi=off and acpi=ht.

There doesn't seem to be any magic formula for which combinations 
of these options will work - it seems to be just a case of trial and 
error until you hit the particular combination that will give you a 
clean shutdown.

Keith, if you still have problems after checking all possible 
combinations of apic  acpi, you might need to try a different kernel.
--
Regards
Margot
*-*-*-*
Sent using Mozilla on a 100% Microsoft-Free Computer
Registered Linux User 307617 http://counter.li.org
Mandrakelinux release 10.1 (Community) for i586 kernel 2.6.8.1-10mdk
~~~
One cannot make an omelette without breaking eggs -- but it is amazing
how many eggs one can break without making a decent omelette.
		-- Professor Charles P. Issawi
~~~


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Keith Powell]

Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I KNOW that this has been asked before, but I can't find the
answer in the archives or in twiki. Sorry for asking it again.
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to change in the
lilo.conf file, but I can't remember what it is - not having
needed it before.
Please, what is it?
Many thanks
Keith

In /etc/lilo.conf try editing the append-line, especially the apic 
thing. Remove it completely or set it to apic=ht or noapic.

HTH
Kaj Haulrich.

Thanks, Kaj.
apic=off  has solved it.
The append line was already  apic=ht,  so I first changed it to  noapic 
 and then  apic=noapic. Neither had any effect.

Cheers
Keith


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Tom Brinkman]

On Friday 10 December 2004 08:53 am, Keith Powell wrote:
  In /etc/lilo.conf try editing the append-line, especially the
  apic thing. Remove it completely or set it to apic=ht or
  noapic.
 
  HTH
  Kaj Haulrich.

 Thanks, Kaj.

 apic=off  has solved it.

 The append line was already  apic=ht,  so I first changed it to
  noapic and then  apic=noapic. Neither had any effect.

For proper and valid kernel parameters give   
  kernel-parameters.txt   a thorough read.  You'll need to have 
kernel-source installed, as it contains the file.  eg,
/usr/src/linux-2.6.8.1-20mdk/Documentation/kernel-parameters.txt
Or you might Google for the file for your kernel.

Many of the parameters I see in various ML posts are not valid 
(possibly undocumented) and are ignored by the kernel, ie, 'no 
effect'.

   APIC, advance programable interrupt control. If your system 
works better with 'noapic', then what this really means is you 
have non-compliant and/or deficient hardware bordering on the 
'designed for windoze' variety.

   Disabling ACPI and/or APIC is best avoided when not absolutely 
necessary, to deal with sloppy, sub-standard hardware.  Tho in 
fairness, other popular distros do disable them by default.  If 
your system can't use these advanced features, don't kid youself 
with believing that optimization for i586, i686, or K7, compiling 
with PREEMPT and such, will provide any benefit. 
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Keith Powell]

Tom Brinkman wrote:
On Friday 10 December 2004 08:53 am, Keith Powell wrote:

apic=off  has solved it.
The append line was already  apic=ht,  so I first changed it to
noapic and then  apic=noapic. Neither had any effect.

APIC, advance programable interrupt control. If your system 
works better with 'noapic', then what this really means is you 
have non-compliant and/or deficient hardware bordering on the 
'designed for windoze' variety.

Disabling ACPI and/or APIC is best avoided when not absolutely 
necessary, to deal with sloppy, sub-standard hardware.  Tho in 
fairness, other popular distros do disable them by default.  If 
your system can't use these advanced features, don't kid youself 
with believing that optimization for i586, i686, or K7, compiling 
with PREEMPT and such, will provide any benefit. 

This is *very* depressing reading, Tom. It is a new computer which I had 
built to my own specification, using components which have been 
recommended by people on this list as working well with Mandrake.

For example, Asus motherboard, Pentium4 processor, NVidia graphics card, 
 and so on.

Are you saying that the recommendations on this list are false?
There is no way that I can afford to change this substandard hardware now.
Keith

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Alan Shoemaker]

On Friday 10 December 2004 02:20 pm, Keith Powell wrote:

 Sometime, I must find out the difference between apic and apci - I
 thought they were almost the same!

APIC - Advanced Programmable Interrupt Controller
ACPI - Advanced Configuration and Power Interface

-- 
Alan


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Margot]

Keith Powell wrote:
Margot wrote:
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to change in the
lilo.conf file, but I can't remember what it is - not having
needed it before.
Please, what is it?
Many thanks
Keith


In /etc/lilo.conf try editing the append-line, especially the apic 
thing. Remove it completely or set it to apic=ht or noapic.

HTH
Kaj Haulrich.

Kaj, I think you're mixing up apic and acpi!
The options for apic include noapic and/or nolapic. The options for 
acpi include acpi=on, acpi=off and acpi=ht.

There doesn't seem to be any magic formula for which combinations of 
these options will work - it seems to be just a case of trial and 
error until you hit the particular combination that will give you a 
clean shutdown.

Keith, if you still have problems after checking all possible 
combinations of apic  acpi, you might need to try a different kernel.

Thanks Margot.
Sometime, I must find out the difference between apic and apci - I 
thought they were almost the same!

But, at the moment, Tom's reply has made me very depressed to find out 
that my new computer is no good!

I don't think that it can be the kernel, as everything closed down OK on 
my old machine.

Cheers
Keith
Keith,
Don't get too depressed! Tom's a bit of a perfectionist when it 
comes to hardware - and he's saved me a lot of heartache on many 
occasions - but if everything else is working for you except the 
shutdown, then your new computer is probably fine. Just experiment a 
bit with the apic  acpi options in the kernel append line, and 
you'll probably find some combination that works - it just might 
take a few shutdown/reboots to hit the ideal mix!
--
Regards
Margot
*-*-*-*
Sent using Mozilla on a 100% Microsoft-Free Computer
Registered Linux User 307617 http://counter.li.org
Mandrakelinux release 10.1 (Community) for i586 kernel 2.6.8.1-10mdk
~~~
The more things change, the more they stay insane.
~~~


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Kaj Haulrich]

On Friday 10 December 2004 21:47, Tom Brinkman wrote:
 On Friday 10 December 2004 08:53 am, Keith Powell wrote:
   In /etc/lilo.conf try editing the append-line, especially the
   apic thing. Remove it completely or set it to apic=ht or
   noapic.
  
   HTH
   Kaj Haulrich.
 
  Thanks, Kaj.
 
  apic=off  has solved it.
 
  The append line was already  apic=ht,  so I first changed it to
   noapic and then  apic=noapic. Neither had any effect.

 For proper and valid kernel parameters give
   kernel-parameters.txt   a thorough read.  You'll need to have
 kernel-source installed, as it contains the file.  eg,
 /usr/src/linux-2.6.8.1-20mdk/Documentation/kernel-parameters.txt
 Or you might Google for the file for your kernel.

 Many of the parameters I see in various ML posts are not
 valid (possibly undocumented) and are ignored by the kernel, ie,
 'no effect'.

APIC, advance programable interrupt control. If your system
 works better with 'noapic', then what this really means is you
 have non-compliant and/or deficient hardware bordering on the
 'designed for windoze' variety.

Disabling ACPI and/or APIC is best avoided when not absolutely
 necessary, to deal with sloppy, sub-standard hardware.  Tho in
 fairness, other popular distros do disable them by default.  If
 your system can't use these advanced features, don't kid youself
 with believing that optimization for i586, i686, or K7, compiling
 with PREEMPT and such, will provide any benefit.

Tom, does that mean, that an empty append line defaults to booting 
with both enabled ?

Kaj Haulrich.
-- 
*sent from a 100% Microsoft-free workstation*
 * http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2.6.8*


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[RickSisler]

Kaj Haulrich ([EMAIL PROTECTED]) wrote:
 On Friday 10 December 2004 21:47, Tom Brinkman wrote:
  On Friday 10 December 2004 08:53 am, Keith Powell wrote:
In /etc/lilo.conf try editing the append-line, especially the
apic thing. Remove it completely or set it to apic=ht or
noapic.
   
HTH
Kaj Haulrich.
  
   Thanks, Kaj.
  
   apic=off  has solved it.
  
   The append line was already  apic=ht,  so I first changed it to
    noapic and then  apic=noapic. Neither had any effect.
 
  For proper and valid kernel parameters give
kernel-parameters.txt   a thorough read.  You'll need to have
  kernel-source installed, as it contains the file.  eg,
  /usr/src/linux-2.6.8.1-20mdk/Documentation/kernel-parameters.txt
  Or you might Google for the file for your kernel.
 
  Many of the parameters I see in various ML posts are not
  valid (possibly undocumented) and are ignored by the kernel, ie,
  'no effect'.
 
 APIC, advance programable interrupt control. If your system
  works better with 'noapic', then what this really means is you
  have non-compliant and/or deficient hardware bordering on the
  'designed for windoze' variety.
 
 Disabling ACPI and/or APIC is best avoided when not absolutely
  necessary, to deal with sloppy, sub-standard hardware.  Tho in
  fairness, other popular distros do disable them by default.  If
  your system can't use these advanced features, don't kid youself
  with believing that optimization for i586, i686, or K7, compiling
  with PREEMPT and such, will provide any benefit.
 
 Tom, does that mean, that an empty append line defaults to booting 
 with both enabled ?
 
 Kaj Haulrich.
Kaj,
as Tom said,you'll need the kernel sources installed
and the place to look for default kernel info is in:

$ cd /usr/src/linux/arch/i386/

*linux* should be a symlink but YMMV..
which contains the default configs for many different kernels.
So for example, mine is:

# uname -sr
Linux 2.6.8.1-12mdk

since we're in the proper dir.. 
we grep the file for apic :
 # cat defconfig |grep -i acpi
 # Power management options (ACPI, APM)
 # ACPI (Advanced Configuration and Power Interface) Support
 CONFIG_ACPI=y
 CONFIG_ACPI_BOOT=y
 CONFIG_ACPI_INTERPRETER=y
 CONFIG_ACPI_SLEEP=y
 CONFIG_ACPI_SLEEP_PROC_FS=y
 CONFIG_ACPI_AC=m
 CONFIG_ACPI_BATTERY=m
 CONFIG_ACPI_BUTTON=m
 CONFIG_ACPI_FAN=m
 CONFIG_ACPI_PROCESSOR=m
 CONFIG_ACPI_THERMAL=m
 CONFIG_ACPI_ASUS=m
 CONFIG_ACPI_TOSHIBA=m
 # CONFIG_ACPI_DEBUG is not set
 CONFIG_ACPI_BUS=y
 CONFIG_ACPI_EC=y
 CONFIG_ACPI_POWER=y
 CONFIG_ACPI_PCI=y
 CONFIG_ACPI_SYSTEM=y
 CONFIG_ACPI_INITRD=y
 CONFIG_ACPI_TC1100=m
 CONFIG_X86_ACPI_CPUFREQ=m
 # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
 CONFIG_X86_POWERNOW_K7_ACPI=y
 CONFIG_X86_POWERNOW_K8_ACPI=y
 CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
 CONFIG_HOTPLUG_PCI_ACPI=m
 CONFIG_SERIAL_8250_ACPI=y
 CONFIG_SERIAL_WACOM_ACPI=m
 
Then also grep for apic:
# cat defconfig |grep -i apic
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y

I got this info from Thomas Backlund from lurking the expert list
earlier this year.

So it would seem *yes* Kaj, it is on by default.

HTH
-- 
RickS  Registered Linux user #338463
Mdk 10.1 OE - Linux 2.6.8.1-12mdk@ http://counter.li.org

gpg --recv-keys --keyserver www.keyserver.net 0x24AABE61


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Tom Brinkman]

On Friday 10 December 2004 07:30 pm, RickSisler wrote:
 Kaj Haulrich ([EMAIL PROTECTED]) wrote:
  On Friday 10 December 2004 21:47, Tom Brinkman wrote:
   On Friday 10 December 2004 08:53 am, Keith Powell wrote:
 In /etc/lilo.conf try editing the append-line,
 especially the apic thing. Remove it completely or set
 it to apic=ht or noapic.

 HTH
 Kaj Haulrich.
   
Thanks, Kaj.
   
apic=off  has solved it.
   
The append line was already  apic=ht,  so I first changed
it to noapic and then  apic=noapic. Neither had any
effect.
  
   For proper and valid kernel parameters give
 kernel-parameters.txt   a thorough read.  You'll need to
   have kernel-source installed, as it contains the file.  eg,
   /usr/src/linux-2.6.8.1-20mdk/Documentation/kernel-parameter
  s.txt Or you might Google for the file for your kernel.
  
   Many of the parameters I see in various ML posts are
   not valid (possibly undocumented) and are ignored by the
   kernel, ie, 'no effect'.
  
  APIC, advance programable interrupt control. If your
   system works better with 'noapic', then what this really
   means is you have non-compliant and/or deficient hardware
   bordering on the 'designed for windoze' variety.
  
  Disabling ACPI and/or APIC is best avoided when not
   absolutely necessary, to deal with sloppy, sub-standard
   hardware.  Tho in fairness, other popular distros do
   disable them by default.  If your system can't use these
   advanced features, don't kid youself with believing that
   optimization for i586, i686, or K7, compiling with PREEMPT
   and such, will provide any benefit.
 
  Tom, does that mean, that an empty append line defaults to
  booting with both enabled ?
 
  Kaj Haulrich.

 Kaj,
 as Tom said,you'll need the kernel sources installed
 and the place to look for default kernel info is in:

 $ cd /usr/src/linux/arch/i386/

 *linux* should be a symlink but YMMV..
 which contains the default configs for many different kernels.
 So for example, mine is:

 # uname -sr
 Linux 2.6.8.1-12mdk

 since we're in the proper dir..
 we grep the file for apic :
  # cat defconfig |grep -i acpi
  # Power management options (ACPI, APM)
  # ACPI (Advanced Configuration and Power Interface) Support
  CONFIG_ACPI=y
  CONFIG_ACPI_BOOT=y
  CONFIG_ACPI_INTERPRETER=y
  CONFIG_ACPI_SLEEP=y
  CONFIG_ACPI_SLEEP_PROC_FS=y
  CONFIG_ACPI_AC=m
  CONFIG_ACPI_BATTERY=m
  CONFIG_ACPI_BUTTON=m
  CONFIG_ACPI_FAN=m
  CONFIG_ACPI_PROCESSOR=m
  CONFIG_ACPI_THERMAL=m
  CONFIG_ACPI_ASUS=m
  CONFIG_ACPI_TOSHIBA=m
  # CONFIG_ACPI_DEBUG is not set
  CONFIG_ACPI_BUS=y
  CONFIG_ACPI_EC=y
  CONFIG_ACPI_POWER=y
  CONFIG_ACPI_PCI=y
  CONFIG_ACPI_SYSTEM=y
  CONFIG_ACPI_INITRD=y
  CONFIG_ACPI_TC1100=m
  CONFIG_X86_ACPI_CPUFREQ=m
  # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
  CONFIG_X86_POWERNOW_K7_ACPI=y
  CONFIG_X86_POWERNOW_K8_ACPI=y
  CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
  CONFIG_HOTPLUG_PCI_ACPI=m
  CONFIG_SERIAL_8250_ACPI=y
  CONFIG_SERIAL_WACOM_ACPI=m

 Then also grep for apic:
 # cat defconfig |grep -i apic
 CONFIG_X86_GOOD_APIC=y
 CONFIG_X86_UP_APIC=y
 CONFIG_X86_UP_IOAPIC=y
 CONFIG_X86_LOCAL_APIC=y
 CONFIG_X86_IO_APIC=y

 I got this info from Thomas Backlund from lurking the expert
 list earlier this year.

 So it would seem *yes* Kaj, it is on by default.

 HTH

I appreciate the addition Rick.  Let me take this opportunity 
to add a caution to your post, but more so to previous replies I 
sent in this thread. 

  ** Unless you know what you're doing, don't edit kernel config 
files by hand and then compile a kernel **

I do, but then I'm a reckless idiot ;   Many of y'all have 
run 'make menuconfig' or 'make xconfig' and noticed that when you 
changed somethin, some, sometimes many other options either were 
greyed out (disabled), or became enabled.

This automatically protects you against setting conflicting 
compile options, and/or automatically presents others 
appropriately.  This protection is not afforded if you edit 
kernel configs manually.

   Still as Rick has very well illustrated, you should take a look 
and get familiar with the kernel options, features, and 
capabilities which are Linux. The very heart of your system, and 
a good place to begin diagnosing peculiar problems. A little 
knowlege in this basic area will lead you to other involved 
processes, like various init functions that have a lot to do with 
booting up, or shutting down, and everything in between.
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Tom Brinkman]

On Friday 10 December 2004 09:37 pm, care free wrote:
 I wonder if it is acpi=on or set you acpi on in your bios

 J.T.

   According to past and present kernel-parameters.txt,  acpi=on  
is _not_ a valid option.  
  ...
acpi=  [HW,ACPI] Advanced Configuration and Power Interface
   Format: { force | off | ht | strict }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
ht -- run only enough ACPI to enable Hyper Threading
strict --  Be less tolerant of platforms that are not
 strictly ACPI specification compliant.

See also Documentation/pm.txt, pci=noacpi

acpi_sleep= [HW,ACPI] Sleep options
Format: { s3_bios, s3_mode }
See Documentation/power/video.txt

acpi_sci=   [HW,ACPI] ACPI System Control Interrupt 
 trigger mode
Format: { level | edge |  high | low }

acpi_irq_balance[HW,ACPI] ACPI will balance active 
 IRQs default in APIC mode

acpi_irq_nobalance  [HW,ACPI] ACPI will not move 
 active IRQs (default)
default in PIC mode

acpi_irq_pci=   [HW,ACPI] If irq_balance, Clear listed 
 IRQs for use by PCI
Format: irq,irq...

acpi_irq_isa=   [HW,ACPI] If irq_balance, Mark listed IRQs 
 used by ISA
Format: irq,irq...

acpi_osi=   [HW,ACPI] empty param disables _OSI

acpi_serialize  [HW,ACPI] force serialization of AML 
methods

acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt 
Override.
For broken nForce2 BIOS resulting in 
XT-PIC timer.
  ...

 This is the mesg about ML/twiki type opinions and advice I'm 
tryin to make known.  acpi=on   doesn't exist or is purposely 
neglected and undocumented.  In either case it's almost certain 
to be ignored by the kernel and have no effect, or possibly an 
unintended one.

 Be concerned about ACPI tho. It's becoming most important on 
current systems where more than the original 15 IRQ's and IRQ 
sharing is needed.  IMO, if you need to add 'acpi=any of the 
options listed in kernel-parameters.txt' to your kernel, what 
you really need to add is better and standards compliant hardware 
to your system.  The facts are available before you purchase, 
only opinions afterwards.

 APIC isn't all that big a fsck'n deal. Nice to have, might 
add a slight touch of performance to ACPI IRQ handling.

 This thread is the last of me being an ogre about advice and 
opinions as gleaned from ML's and twiki's when it's contrary to 
past and current developer's and maintainer's documentation.

 Probly why after years, I hardly post anymore.  
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Kaj Haulrich]

On Friday 10 December 2004 15:48, Margot wrote:

snip
 Kaj, I think you're mixing up apic and acpi!
/snip

Yes.  Sorry.  Never came to grips with this alphabet-thingy.

Kaj Haulrich.
-- 
*sent from a 100% Microsoft-free workstation*
 * http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2.6.8*


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Keith Powell]

Margot wrote:
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to change in the
lilo.conf file, but I can't remember what it is - not having
needed it before.
Please, what is it?
Many thanks
Keith

In /etc/lilo.conf try editing the append-line, especially the apic 
thing. Remove it completely or set it to apic=ht or noapic.

HTH
Kaj Haulrich.

Kaj, I think you're mixing up apic and acpi!
The options for apic include noapic and/or nolapic. The options for acpi 
include acpi=on, acpi=off and acpi=ht.

There doesn't seem to be any magic formula for which combinations of 
these options will work - it seems to be just a case of trial and error 
until you hit the particular combination that will give you a clean 
shutdown.

Keith, if you still have problems after checking all possible 
combinations of apic  acpi, you might need to try a different kernel.

Thanks Margot.
Sometime, I must find out the difference between apic and apci - I 
thought they were almost the same!

But, at the moment, Tom's reply has made me very depressed to find out 
that my new computer is no good!

I don't think that it can be the kernel, as everything closed down OK on 
my old machine.

Cheers
Keith


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

RE: [newbie] Shutdown problem

[care free]

I wonder if it is acpi=on or set you acpi on in your bios
J.T.
From: Keith Powell [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [newbie] Shutdown problem
Date: Fri, 10 Dec 2004 10:37:13 +
I KNOW that this has been asked before, but I can't find the answer in the 
archives or in twiki. Sorry for asking it again.

I have a new machine, and now, when I close down, everything closes down
correctly, but then Mandrake does not actually switch the computer off.
If I remember correctly, there is something to change in the lilo.conf 
file, but I can't remember what it is - not having needed it before.

Please, what is it?
Many thanks
Keith

Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com

Re: [newbie] Shutdown problem

[Mark Weaver]

 
 1. When I issue the Shutdown command from the console of KDE desktop, it 
 will close X-Windows and restarts (without rebootng) Linux in character 
 based single user mode. Here it automatically logins as root without asking 
 any password, even if I was logged as a normal user when issuing shutdown 
 command. It may create a security problem. Why is it so?

The correct shutdown command should be typed in the command line and
look like this:

shutdown now -hENTER

When the command line reads

powerdown

you're free to turn off the machine with doing any damage to the file
system.

 
 2. When I browse the net using Navigator, some times after visiting several 
 sites my hard will begin to read continously. After that Navigator hangs and 
 I can't even kill it. Sometimes the whole system will not respond at all. My 
 system has Windows 98 running on another partition, which shows no problem 
 while browsing.
 

First, what version of Netscape are you running? Secondly, there is a
program listed in the menu under Applications -Monitoring -Process
management. This program will show you all the processes running when
Netscaoe freezes and you will be able to kill the runaway process.

If your desktop locks up and you can't get anything to work there are
several things you can do without resorting to a hard boot.

1) CTRL-ALT-F1  will take you to a console login prompt. FRom here you can
login as root and find out the offending process and kill it.

you can find it by issuing the command 'top' on the command line, read the
CPU usage percentage, type 'k' and then supply the PID which is listed
down the left side of the display.

2) when that's accomplished you can get back the X graphical login, if in
fact this is the method you're using to log into your machine. This is
done by performing the following steps:

CTRL-ALT-F7

This will restart X and you will be delivered to the X-windows login
screen.

I seriously doubt that windows has anything what-so-ever to do with your
troubles. It sounds alot like the problems a lot of folks are experiencing
to one degree or another with Netscape though.

As far as Netscape goes, if all else fails uninstall the version of
Netscape you're running and install Communicator 4.61. That version at
least is stable enough that it won't give you the troubles you're having
at the moment. There is also the alternative of running Mozilla which is
very fast surpassing recent releases of Netscape Communicator and Netscape
6. The difference in the two are these:

Netscape Communicator  Netscape 6 are being coded and released by AOL. In
plain words since AOL bought Netscape took over the reigns Netscape
Communicator has gone to hell in a hand-basket. It sucks and it isn't
getting any better.

Mozilla in the other hand is still being coded by a lot of Netscapes'
original programmers as well as the open source community and programmers
all over the world that adhere to the original programming standards that
USED to be Netscape. The Mozilla project is progressing beautifuly. The
latest release, M17, while being somewhat resource hungry, is quite nice
in appearence and functionality. The nightly releases of M18 are getting
even better. It's not quite there yet, but from what I've seen so far it's
going to be GREAT browser/email client/editor suite when it's finished.

Mark

Re: [newbie] Shutdown problem

[A V Flinsch]

On Fri, 01 Sep 2000, you wrote:
 Hi,
 
 I'm a new user of Linux from India. I've with me LM 7.1 Complete. I've two 
 problems
 
 1. When I issue the Shutdown command from the console of KDE desktop, it 
 will close X-Windows and restarts (without rebootng) Linux in character 
 based single user mode. Here it automatically logins as root without asking 
 any password, even if I was logged as a normal user when issuing shutdown 
 command. It may create a security problem. Why is it so?
 

This sounds a bit odd.  Exactly what shutdown command are you issuing. It looks
like you are doing "shutdown -r now" and have inittab set to a default runlevel
of 1.  If that is the case, change your runlevel in inittab to something
sensible like 3, or 5.



 2. When I browse the net using Navigator, some times after visiting several 
 sites my hard will begin to read continously. After that Navigator hangs and 
 I can't even kill it. Sometimes the whole system will not respond at all. My 
 system has Windows 98 running on another partition, which shows no problem 
 while browsing.

A few suggestions here -

Upgrade to whatever is the newest version of netscape-navigator. Don't even
try to use communicator. Communicator seems to be unstable on some systems, and
there are better options for everything it gives you over the plain navigator
package.

Try increasing your cache size in netscape.

Run junkbuster  squid as procies


-- 
Alex
(Go easy on me, I'm a COBOL programmer in real life)

Re: [newbie] Shutdown problem

[Jeff Malka]

 Run junkbuster  squid as procies

What are these?  Are they included in Mandrake 7.1?

Jeff Malka [EMAIL PROTECTED]
Registered Linux user  183185

Re: [newbie] Shutdown problem

[Jeff Malka]

Thank you.

Jeff Malka [EMAIL PROTECTED]
Registered Linux user  183185

- Original Message -
From: A V Flinsch [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, September 02, 2000 5:11 PM
Subject: Re: [newbie] Shutdown problem


 On Sat, 02 Sep 2000, you wrote:
   Run junkbuster  squid as procies

 oops, that should have been proxies (what the hell is a procies anyway?)

 
  What are these?  Are they included in Mandrake 7.1?
 

 squid is a proxy caching server, keeps track of recently viewed objects 
dns
 entries in ram, makes surfing a bit quicker.

 junkbuster is a banner ad  cookie blocker, prevents you from seeing all
of the
 junk that clutters up webpages.

 squid is on the 7.1 main install cd, junkbuster may be on second cd, otr
the
 contribs disk, but I prefer the version of junkbuster from
 http://www.waldherr.org/ as it had a more up to date list of banner sites.

 --
 Alex
 (Go easy on me, I'm a COBOL programmer in real life)

Re: [newbie] Shutdown problem with v7.0...

[Philip Hinds]

I,ve been following this thread with interest as I've the same. I installed
Open Linux and there was no problem. I have AMD K11-6 400  Soyo 5ehm,
64ram. It has a via chip. I'll re-install Mandrake again and see if I can
fix it. The reason for  posting this is in case it is an AMD or Soyo/VIA
problem which may help to slove problem. Not everyone has it, so what is the
common denominator? Generally is it better to stick with Intel?
P Hinds
- Original Message -
From: Dennis Myers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 11, 2000 6:56 PM
Subject: Re: [newbie] Shutdown problem with v7.0...


 flupke wrote:

  Sorry, I didn't follow this tread from the begining, so I hope I won't
say
  anything stoopid or something that has already been said.
  If I understand, the problem here is all the dump of the stack and
  registers caused by a page default or something at the end of a
shutdown.
 
  I have the same problem. I think it only happens on Motherboards with
VIA
  chips. I don't mind about it since it doesn't cause any damage, but it
is
  nice to get rid of that bad stuff.
  I solved the problem by modifying the /etc/rc.d/init.d/halt file and
  change the line
  eval $command -i -d -p
  to
  eval $command -i -d
 
  PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)
 
  HTH
  Flupke
 
  On Sun, 11 Jun 2000, Fran Parker wrote:
 
   I second what Ronald wrote...I went to DRAKCONF and
   found it there no problem and disabled it.  Shutdown and
   there were all the things on the screen again...full screen
   all over the screen...
  
   I also already had the power management in KDE disabled
   as well.
  
   Oh, well it was worth a shot.
  
   Anyway, reboot works just fine :)
  
   Bambi
  
  
   "Ronald J. Hall" wrote:
  
Paul wrote:
   
 Log in as root, or run "su"
 Then run "setup" in a console
 Go to system services, and uncheck the APM daemon. it is right
below the
 anacron daemon.
 After a reboot you're all set!

 Paul
   
Hi. Well, I opened up a shell on my desktop,
ran su, password, typed in "setup" and it told
me, "bash: command not found".
   
So I went into the DRAKCONF and ran startup,
found it (under anacron, like you said) and
disabled it. Unfortunately, after powering
down, and rebooting, the problem still exists.
I also have dmps disabled from the kde desktop
(don't know if that needed to be or not). Any
other possible ideas as to what it might be?
   
(Thanks to Dennis Myers for the DRAKCONF tip)
   
Thanks much!
   
PS Did you see the reply I posted with the details
on the screen that I'm left with? Maybe you can
find a clue there...
   
See ya...
  
  
  
 
  --
   There's no place like ~ ! 

 Well, I tried my own advise and it didn't work for me either.  I see the
 suggestion to edit or modify the rc.d files but don't know how to do that.
The
 last time I tried to change a file I crashed the whole config and had to
 reinstall.  By the way, I am getting very good at reinstall or new install
since
 there seems to be something  that causes me to lose my mouse and Keyboard
every
 now and then.  I keep trying to find the problem but no luck so far.  I am
 running an AMD K6 II - 333  with a soyo 5EMA + motherboard 64 meg ram  and
 western Digital  13.6 gig ide hard drive, generic floppy and cdrom.   If
there is
 a man page or faq that talks about editing files I would like to know.  I
am not
 trained in computers just determined to learn.   Thanks in advance for any
help
 here.

Re: [newbie] Shutdown problem with v7.0...

[Dennis Myers]

Philip Hinds wrote:

 I,ve been following this thread with interest as I've the same. I installed
 Open Linux and there was no problem. I have AMD K11-6 400  Soyo 5ehm,
 64ram. It has a via chip. I'll re-install Mandrake again and see if I can
 fix it. The reason for  posting this is in case it is an AMD or Soyo/VIA
 problem which may help to slove problem. Not everyone has it, so what is the
 common denominator? Generally is it better to stick with Intel?
 P Hinds
 - Original Message -
 From: Dennis Myers [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, June 11, 2000 6:56 PM
 Subject: Re: [newbie] Shutdown problem with v7.0...

  flupke wrote:
 
   Sorry, I didn't follow this tread from the begining, so I hope I won't
 say
   anything stoopid or something that has already been said.
   If I understand, the problem here is all the dump of the stack and
   registers caused by a page default or something at the end of a
 shutdown.
  
   I have the same problem. I think it only happens on Motherboards with
 VIA
   chips. I don't mind about it since it doesn't cause any damage, but it
 is
   nice to get rid of that bad stuff.
   I solved the problem by modifying the /etc/rc.d/init.d/halt file and
   change the line
   eval $command -i -d -p
   to
   eval $command -i -d
  
   PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)
  
   HTH
   Flupke
  
   On Sun, 11 Jun 2000, Fran Parker wrote:
  
I second what Ronald wrote...I went to DRAKCONF and
found it there no problem and disabled it.  Shutdown and
there were all the things on the screen again...full screen
all over the screen...
   
I also already had the power management in KDE disabled
as well.
   
Oh, well it was worth a shot.
   
Anyway, reboot works just fine :)
   
Bambi
   
   
"Ronald J. Hall" wrote:
   
 Paul wrote:

  Log in as root, or run "su"
  Then run "setup" in a console
  Go to system services, and uncheck the APM daemon. it is right
 below the
  anacron daemon.
  After a reboot you're all set!
 
  Paul

 Hi. Well, I opened up a shell on my desktop,
 ran su, password, typed in "setup" and it told
 me, "bash: command not found".

 So I went into the DRAKCONF and ran startup,
 found it (under anacron, like you said) and
 disabled it. Unfortunately, after powering
 down, and rebooting, the problem still exists.
 I also have dmps disabled from the kde desktop
 (don't know if that needed to be or not). Any
 other possible ideas as to what it might be?

 (Thanks to Dennis Myers for the DRAKCONF tip)

 Thanks much!

 PS Did you see the reply I posted with the details
 on the screen that I'm left with? Maybe you can
 find a clue there...

 See ya...
   
   
   
  
   --
There's no place like ~ ! 
 
  Well, I tried my own advise and it didn't work for me either.  I see the
  suggestion to edit or modify the rc.d files but don't know how to do that.
 The
  last time I tried to change a file I crashed the whole config and had to
  reinstall.  By the way, I am getting very good at reinstall or new install
 since
  there seems to be something  that causes me to lose my mouse and Keyboard
 every
  now and then.  I keep trying to find the problem but no luck so far.  I am
  running an AMD K6 II - 333  with a soyo 5EMA + motherboard 64 meg ram  and
  western Digital  13.6 gig ide hard drive, generic floppy and cdrom.   If
 there is
  a man page or faq that talks about editing files I would like to know.  I
 am not
  trained in computers just determined to learn.   Thanks in advance for any
 help
  here.
 
 

Your setup is exactly the same as mine.  AMD K6 II  400 , 64 MB ram via chip on
the soyo 5EHM+  motherboard ,   ergo you should be able to fix the problem with
the specified edit if the problem is indeed the CPU or chipset.  Seems as
though the chipset is the common factor.

Re: [newbie] Shutdown problem with v7.0...

[Ronald J. Hall]

Dennis Myers wrote:

 Followup to this thread, I figured out how to edit (hooray!!!) and went
 in to the above listed   /etc/ files and deleted the -p and voila!  the
 error message is gone when I "halt" the sys.  I think that I am
 beginning to get the hang of some of this and am falling in love with
 "linux".  You can actually fix things if you want to take the time to
 learn.

Exactly! It worked for me as well. I think the
biggest thing is:

1) Take your time
2) *really* read the manuals
3) Listen (hard) to advice from "vets"
4) Repeat steps 1 - 3 as necessary!

smile

Re: [newbie] Shutdown problem with v7.0...

[Dennis Myers]

Dacia and AzureRose wrote:

 hmmm...both of the computers I've seen this problem on
 had Via chipsets on their motherboards.

 Dacia
 --- flupke [EMAIL PROTECTED] wrote:
  Sorry, I didn't follow this tread from the begining,
  so I hope I won't say
  anything stoopid or something that has already been
  said.
  If I understand, the problem here is all the dump of
  the stack and
  registers caused by a page default or something at
  the end of a shutdown.
 
  I have the same problem. I think it only happens on
  Motherboards with VIA
  chips. I don't mind about it since it doesn't cause
  any damage, but it is
  nice to get rid of that bad stuff.
  I solved the problem by modifying the
  /etc/rc.d/init.d/halt file and
  change the line
eval $command -i -d -p
  to
eval $command -i -d
 
  PS :
  http://www.mandrakeuser.org/troubles/tquick1.html
  :-)
 
  HTH
  Flupke
 
  On Sun, 11 Jun 2000, Fran Parker wrote:
 
   I second what Ronald wrote...I went to DRAKCONF
  and
   found it there no problem and disabled it.
  Shutdown and
   there were all the things on the screen
  again...full screen
   all over the screen...
  
   I also already had the power management in KDE
  disabled
   as well.
  
   Oh, well it was worth a shot.
  
   Anyway, reboot works just fine :)
  
   Bambi
  
  
   "Ronald J. Hall" wrote:
  
Paul wrote:
   
 Log in as root, or run "su"
 Then run "setup" in a console
 Go to system services, and uncheck the APM
  daemon. it is right below the
 anacron daemon.
 After a reboot you're all set!

 Paul
   
Hi. Well, I opened up a shell on my desktop,
ran su, password, typed in "setup" and it told
me, "bash: command not found".
   
So I went into the DRAKCONF and ran startup,
found it (under anacron, like you said) and
disabled it. Unfortunately, after powering
down, and rebooting, the problem still exists.
I also have dmps disabled from the kde desktop
(don't know if that needed to be or not). Any
other possible ideas as to what it might be?
   
(Thanks to Dennis Myers for the DRAKCONF tip)
   
Thanks much!
   
PS Did you see the reply I posted with the
  details
on the screen that I'm left with? Maybe you can
find a clue there...
   
See ya...
  
  
  
 
  --
   There's no place like ~ ! 
 

 __
 Do You Yahoo!?
 Yahoo! Photos -- now, 100 FREE prints!
 http://photos.yahoo.com

Followup to this thread, I figured out how to edit (hooray!!!) and went
in to the above listed   /etc/ files and deleted the -p and voila!  the
error message is gone when I "halt" the sys.  I think that I am
beginning to get the hang of some of this and am falling in love with
"linux".  You can actually fix things if you want to take the time to
learn.

Re: [newbie] Shutdown problem with v7.0...

[flupke]

On Sun, 11 Jun 2000, Dennis Myers wrote:

 flupke wrote:
 
  Sorry, I didn't follow this tread from the begining, so I hope I won't say
  anything stoopid or something that has already been said.
  If I understand, the problem here is all the dump of the stack and
  registers caused by a page default or something at the end of a shutdown.
 
  I have the same problem. I think it only happens on Motherboards with VIA
  chips. I don't mind about it since it doesn't cause any damage, but it is
  nice to get rid of that bad stuff.
  I solved the problem by modifying the /etc/rc.d/init.d/halt file and
  change the line
  eval $command -i -d -p
  to
  eval $command -i -d
 
  PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)
 
  HTH
  Flupke
 
[...]
 
 
 Well, I tried my own advise and it didn't work for me either.  I see the
 suggestion to edit or modify the rc.d files but don't know how to do that. The
 last time I tried to change a file I crashed the whole config and had to
 reinstall.  By the way, I am getting very good at reinstall or new install since
 there seems to be something  that causes me to lose my mouse and Keyboard every
 now and then.  I keep trying to find the problem but no luck so far.  I am
 running an AMD K6 II - 333  with a soyo 5EMA + motherboard 64 meg ram  and
 western Digital  13.6 gig ide hard drive, generic floppy and cdrom.   If there is
 a man page or faq that talks about editing files I would like to know.  I am not
 trained in computers just determined to learn.   Thanks in advance for any help
 here.
 
 
 
OK, Dennis. Don't be afraid. To avoid problem when modifying a file that
is important for the system, you just have to save before editing :
  cd /etc/rc.d/init.d/
  cp halt halt.orig
  vi halt

(NB : DON'T DO THAT if you never used vi... in that case, use kedit, pico 
or another one that you know. But if you want to give vi a blind try,
once it is opened, just type "G$xxx" to go to the last line of the file,
go to the end of the line and erase the last 3 chars, then type ":wq" and
press enter to save the file and quit edition)

That way, if there is a problem, you simply have to boot in single-user
mode and put the files as they were before. But note that there is no
danger here, since the file that has to be edited is only invoked at
shutdown or reboot time.

There is also something that can be usefull : make an archive of /etc and
put it in a safe place, so that you can restore a file that you broke.

For doc about safe edition, maybe you could browse the HOWTOs. There is a
security-HOWTO that talks about safety in a network, maybe there is
another one about safety in your system...
For doc about edition itself, well, I must say that I'm a vi fan. So, I
would suggest you two things :
- In the man vi, I think you will find a reference to a basic
  tutorial. Read that tutorial.

- Then, you take a cup of cofee, you start vi, and you type ':help'


HTH
Flupke

 -- 
 There's no place like ~ ! 

Re: [newbie] Shutdown problem with v7.0...

[Fran Parker]

Thanks Ronald...I will try this.
Seems funny though that if it doesn't find it there (and
it does look there) it also looks in my /home/fran directory
and still doesn't find it.

Not sure what the problem is there, but will put it in the
share directory and see if it helps.

Thanks,
Bambi


"Ronald J. Hall" wrote:

 Fran Parker wrote:

  Now do you you know how to get lxdoom to work..it says it can't
  find an IWAD...I have downloaded the shareware 1.8 wad file,
  I have gone to get the iwad file they had and unzipped it...doom1.wad
  Anyway it can't find it and I tried to run it in terminal window to see
  it's complaints ... they only thing it says besides the memory size is
  it can't find an IWAD file!
 
  I am at a lose as to how to proceed.  Any help?
 
  Thanks in advance,
  Bambi

 Hi. On my setup of lxdoom, the doom1.wad file
 goes in /usr/share/games/doom. Hope this helps!

Re: [newbie] Shutdown problem with v7.0...

[Paul]

On Sat, 10 Jun 2000, Fran Parker wrote:

Same hereI don't shutdown the computer...I only reboot and shut
off the computer from there, I hate getting error messages! :)

Bambi

Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
said that was disabled!!
Sorry!

Paul

-- 
Read the funnies.
Throw the rest of the paper away

)0([[EMAIL PROTECTED]])0(
http://nlpagan.net -  ICQ 147208
Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[Paul]

On Sat, 10 Jun 2000, Fran Parker wrote:

Same hereI don't shutdown the computer...I only reboot and shut
off the computer from there, I hate getting error messages! :)

 BTW, I can shutdown and restart, and I do NOT
 get this problem. Odd, eh?

Did you all get the message Dacia sent in? In it he says of knowing of the
same problem, and that disabling advanced power management in the BIOS
fixed the problem

Paul

-- 
Read the funnies.
Throw the rest of the paper away

)0([[EMAIL PROTECTED]])0(
http://nlpagan.net -  ICQ 147208
Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[Paul]

On Sun, 11 Jun 2000, Ronald J. Hall wrote:

Hi Dacia. Hmm. I'll go into my Bios and try that
then. Power management -is- working here though.
My system goes through the stages, the screen-
saver kicks in (love that Matrix one!), then a
few minutes later, the monitor goes black,  etc,
etc,... I do have the shutdown options for the
other system components (fan, HD, etc) turned off
though. 

APM is a service in Linux. You can disable it by running 'setup' as root,
it is in 'system services'.

Paul

-- 
Read the funnies.
Throw the rest of the paper away

)0([[EMAIL PROTECTED]])0(
http://nlpagan.net -  ICQ 147208
Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[Fran Parker]

Hi Ronald,

I have a dual boot system with Win98 and Linux Mandrake 7.0 (Air).

Actually I have a Celeron 366mhz ...I do not use power-management.
I have one hard drive that doesn't recover from power-management
on the hard drives (old 540 meg - my 3rd drive -  is actually mainly a place
holder more than anything else..to keep my CDRom as F: in Windows 98
for a program that I don't want to re-install that I can't find the little
file that designates the CDRom drive letter in it, and my screensaver
in Linux works fine for me, and of course the screen blanks on its own
if left in log-in screen.  Power management on my PC hasn't been an
issue for me.  If I were on a laptop...that would be different.

I will have to verify whether it is actually enabled in the bios though
to see if that is the situation with shutting down errors here.

I don't see it as a problem though...I reboot and shut off the computer
works like a champ and no errors.

Bambi




"Ronald J. Hall" wrote:

 Fran Parker wrote:
 
  Same hereI don't shutdown the computer...I only reboot and shut
  off the computer from there, I hate getting error messages! :)
 
  Bambi

 Hi. Yeah, me too...if I wanted a lot of error
 messages, I could have got a Windog machine,
 grin which I've never owned in my life, even
 though I've been "into" computing since '83
 when I first bought an Atari 800XL... ;-)

 You probably caught the other replies, but the
 suggestions run along the lines of:

 1) Turn power management off
 2) problem with AMD processors, get a patch

 I'm still online, so I'll try 1) when I get off,
 and I'll see if Mandrake's site has anything about
 a shutdown problem with AMD processors. BTW, are
 U using an AMD CPU?

 Let me know if any of these work for you, and I'll
 do the same! ;-)

 PS If its the patch, I'm assuming (dangerous!)
 that v7.1 should have it fixed...

Re: [newbie] Shutdown problem with v7.0...

[Ronald J. Hall]

Paul wrote:

 Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
 said that was disabled!!
 Sorry!
 
 Paul

Argh, I missed that too...anyways, I turned off
power management in Bios and of course, it made
nary a difference.

So...how do I disable the APMD daemon? ;-)

Thanks!

Re: [newbie] Shutdown problem with v7.0...

[Fran Parker]

Thanks Paul will look into that end of things.  I didn't
think I had that enabled in the bios.

Bambi

Paul wrote:

 On Sun, 11 Jun 2000, Ronald J. Hall wrote:

 Hi Dacia. Hmm. I'll go into my Bios and try that
 then. Power management -is- working here though.
 My system goes through the stages, the screen-
 saver kicks in (love that Matrix one!), then a
 few minutes later, the monitor goes black,  etc,
 etc,... I do have the shutdown options for the
 other system components (fan, HD, etc) turned off
 though.

 APM is a service in Linux. You can disable it by running 'setup' as root,
 it is in 'system services'.

 Paul

 --
 Read the funnies.
 Throw the rest of the paper away

 )0([[EMAIL PROTECTED]])0(
 http://nlpagan.net -  ICQ 147208
 Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[Ronald J. Hall]

Paul wrote:

 APM is a service in Linux. You can disable it by running 'setup' as root,
 it is in 'system services'.
 
 Paul

Ah, got it. I just printed out your reply, will
try that next. Ignore my earlier question! ;-)

Re: [newbie] Shutdown problem with v7.0...

[Paul]

On Sun, 11 Jun 2000, Ronald J. Hall wrote:

 Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
 said that was disabled!!
 Sorry!

Argh, I missed that too...anyways, I turned off
power management in Bios and of course, it made
nary a difference.

So...how do I disable the APMD daemon? ;-)

Log in as root, or run "su"
Then run "setup" in a console
Go to system services, and uncheck the APM daemon. it is right below the
anacron daemon.
After a reboot you're all set!

Paul

-- 
Read the funnies.
Throw the rest of the paper away

)0([[EMAIL PROTECTED]])0(
http://nlpagan.net -  ICQ 147208
Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[flupke]

Sorry, I didn't follow this tread from the begining, so I hope I won't say
anything stoopid or something that has already been said.
If I understand, the problem here is all the dump of the stack and
registers caused by a page default or something at the end of a shutdown.

I have the same problem. I think it only happens on Motherboards with VIA
chips. I don't mind about it since it doesn't cause any damage, but it is
nice to get rid of that bad stuff.
I solved the problem by modifying the /etc/rc.d/init.d/halt file and
change the line
eval $command -i -d -p
to
eval $command -i -d

PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)

HTH
Flupke

On Sun, 11 Jun 2000, Fran Parker wrote:

 I second what Ronald wrote...I went to DRAKCONF and
 found it there no problem and disabled it.  Shutdown and
 there were all the things on the screen again...full screen
 all over the screen...
 
 I also already had the power management in KDE disabled
 as well.
 
 Oh, well it was worth a shot.
 
 Anyway, reboot works just fine :)
 
 Bambi
 
 
 "Ronald J. Hall" wrote:
 
  Paul wrote:
 
   Log in as root, or run "su"
   Then run "setup" in a console
   Go to system services, and uncheck the APM daemon. it is right below the
   anacron daemon.
   After a reboot you're all set!
  
   Paul
 
  Hi. Well, I opened up a shell on my desktop,
  ran su, password, typed in "setup" and it told
  me, "bash: command not found".
 
  So I went into the DRAKCONF and ran startup,
  found it (under anacron, like you said) and
  disabled it. Unfortunately, after powering
  down, and rebooting, the problem still exists.
  I also have dmps disabled from the kde desktop
  (don't know if that needed to be or not). Any
  other possible ideas as to what it might be?
 
  (Thanks to Dennis Myers for the DRAKCONF tip)
 
  Thanks much!
 
  PS Did you see the reply I posted with the details
  on the screen that I'm left with? Maybe you can
  find a clue there...
 
  See ya...
 
 
 

-- 
 There's no place like ~ ! 

Re: [newbie] Shutdown problem with v7.0...

[Dacia and AzureRose]

That worked on my brother computer.  He has a SOYO
socket 7 motherboard.  I forget the exact model.  He
disabled apmd and it got better.  When I had that same
motherboard in my old computer I had to disable
Advanced power management in my bios and apmd to get
it to stop.


Dacia
--- Paul [EMAIL PROTECTED] wrote:
 On Sat, 10 Jun 2000, Fran Parker wrote:
 
 Same hereI don't shutdown the computer...I only
 reboot and shut
 off the computer from there, I hate getting error
 messages! :)
 
  BTW, I can shutdown and restart, and I do NOT
  get this problem. Odd, eh?
 
 Did you all get the message Dacia sent in? In it he
 says of knowing of the
 same problem, and that disabling advanced power
 management in the BIOS
 fixed the problem
 
 Paul
 
 -- 
 Read the funnies.
 Throw the rest of the paper away
 
 )0([[EMAIL PROTECTED]])0(
 http://nlpagan.net -  ICQ 147208
 Registered  Linux  User   174403
 
 


__
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

Re: [newbie] Shutdown problem with v7.0...

[Dacia and AzureRose]

That probably will not work.  My brother disabled the
apm daemon in linux not advanced power management in
his BIOS.  I had to do BOTH to make mine work.

The easiest way I know to disable the apmd is to open
DrakConf, click startup services and uncheck the box
by apmd.  It won't take affect until the next time you
boot however.


Dacia



--- "Ronald J. Hall" [EMAIL PROTECTED] wrote:
 Dacia and AzureRose wrote:
  
  My brother had this same problem and we found that
 in
  his case it was because of a conflict between his
  motherboard advanced power management features and
 the
  way linux was trying to access those functions.
  
  He disabled apmd and it stopped happening.
  
  Dacia
 
 Hi Dacia. Hmm. I'll go into my Bios and try that
 then. Power management -is- working here though.
 My system goes through the stages, the screen-
 saver kicks in (love that Matrix one!), then a
 few minutes later, the monitor goes black,  etc,
 etc,... I do have the shutdown options for the
 other system components (fan, HD, etc) turned off
 though. 
 
 Thanks for the suggestion!
 


__
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

Re: [newbie] Shutdown problem with v7.0...

[Dacia and AzureRose]

hmmm...both of the computers I've seen this problem on
had Via chipsets on their motherboards.


Dacia
--- flupke [EMAIL PROTECTED] wrote:
 Sorry, I didn't follow this tread from the begining,
 so I hope I won't say
 anything stoopid or something that has already been
 said.
 If I understand, the problem here is all the dump of
 the stack and
 registers caused by a page default or something at
 the end of a shutdown.
 
 I have the same problem. I think it only happens on
 Motherboards with VIA
 chips. I don't mind about it since it doesn't cause
 any damage, but it is
 nice to get rid of that bad stuff.
 I solved the problem by modifying the
 /etc/rc.d/init.d/halt file and
 change the line
   eval $command -i -d -p
 to
   eval $command -i -d
 
 PS :
 http://www.mandrakeuser.org/troubles/tquick1.html
 :-)
 
 HTH
 Flupke
 
 On Sun, 11 Jun 2000, Fran Parker wrote:
 
  I second what Ronald wrote...I went to DRAKCONF
 and
  found it there no problem and disabled it. 
 Shutdown and
  there were all the things on the screen
 again...full screen
  all over the screen...
  
  I also already had the power management in KDE
 disabled
  as well.
  
  Oh, well it was worth a shot.
  
  Anyway, reboot works just fine :)
  
  Bambi
  
  
  "Ronald J. Hall" wrote:
  
   Paul wrote:
  
Log in as root, or run "su"
Then run "setup" in a console
Go to system services, and uncheck the APM
 daemon. it is right below the
anacron daemon.
After a reboot you're all set!
   
Paul
  
   Hi. Well, I opened up a shell on my desktop,
   ran su, password, typed in "setup" and it told
   me, "bash: command not found".
  
   So I went into the DRAKCONF and ran startup,
   found it (under anacron, like you said) and
   disabled it. Unfortunately, after powering
   down, and rebooting, the problem still exists.
   I also have dmps disabled from the kde desktop
   (don't know if that needed to be or not). Any
   other possible ideas as to what it might be?
  
   (Thanks to Dennis Myers for the DRAKCONF tip)
  
   Thanks much!
  
   PS Did you see the reply I posted with the
 details
   on the screen that I'm left with? Maybe you can
   find a clue there...
  
   See ya...
  
  
  
 
 -- 
  There's no place like ~ ! 
 


__
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

Re: [newbie] Shutdown problem with v7.0...

[Dennis Myers]

flupke wrote:

 Sorry, I didn't follow this tread from the begining, so I hope I won't say
 anything stoopid or something that has already been said.
 If I understand, the problem here is all the dump of the stack and
 registers caused by a page default or something at the end of a shutdown.

 I have the same problem. I think it only happens on Motherboards with VIA
 chips. I don't mind about it since it doesn't cause any damage, but it is
 nice to get rid of that bad stuff.
 I solved the problem by modifying the /etc/rc.d/init.d/halt file and
 change the line
 eval $command -i -d -p
 to
 eval $command -i -d

 PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)

 HTH
 Flupke

 On Sun, 11 Jun 2000, Fran Parker wrote:

  I second what Ronald wrote...I went to DRAKCONF and
  found it there no problem and disabled it.  Shutdown and
  there were all the things on the screen again...full screen
  all over the screen...
 
  I also already had the power management in KDE disabled
  as well.
 
  Oh, well it was worth a shot.
 
  Anyway, reboot works just fine :)
 
  Bambi
 
 
  "Ronald J. Hall" wrote:
 
   Paul wrote:
  
Log in as root, or run "su"
Then run "setup" in a console
Go to system services, and uncheck the APM daemon. it is right below the
anacron daemon.
After a reboot you're all set!
   
Paul
  
   Hi. Well, I opened up a shell on my desktop,
   ran su, password, typed in "setup" and it told
   me, "bash: command not found".
  
   So I went into the DRAKCONF and ran startup,
   found it (under anacron, like you said) and
   disabled it. Unfortunately, after powering
   down, and rebooting, the problem still exists.
   I also have dmps disabled from the kde desktop
   (don't know if that needed to be or not). Any
   other possible ideas as to what it might be?
  
   (Thanks to Dennis Myers for the DRAKCONF tip)
  
   Thanks much!
  
   PS Did you see the reply I posted with the details
   on the screen that I'm left with? Maybe you can
   find a clue there...
  
   See ya...
 
 
 

 --
  There's no place like ~ ! 

Well, I tried my own advise and it didn't work for me either.  I see the
suggestion to edit or modify the rc.d files but don't know how to do that. The
last time I tried to change a file I crashed the whole config and had to
reinstall.  By the way, I am getting very good at reinstall or new install since
there seems to be something  that causes me to lose my mouse and Keyboard every
now and then.  I keep trying to find the problem but no luck so far.  I am
running an AMD K6 II - 333  with a soyo 5EMA + motherboard 64 meg ram  and
western Digital  13.6 gig ide hard drive, generic floppy and cdrom.   If there is
a man page or faq that talks about editing files I would like to know.  I am not
trained in computers just determined to learn.   Thanks in advance for any help
here.

Re: [newbie] Shutdown problem with v7.0...

[Fran Parker]

That could be true flupke, mine is a VIA chipset.

It doesn't seem to hurt anything, if I accidentally choose
shutdown, I just choose alt-cntrl-del and it finishes it.

But if it can be fixed...cool.  I will look into it with my system.

Thanks,
Bambi

Now do you you know how to get lxdoom to work..it says it can't
find an IWAD...I have downloaded the shareware 1.8 wad file,
I have gone to get the iwad file they had and unzipped it...doom1.wad
Anyway it can't find it and I tried to run it in terminal window to see
it's complaints ... they only thing it says besides the memory size is
it can't find an IWAD file!

I am at a lose as to how to proceed.  Any help?

Thanks in advance,
Bambi

flupke wrote:

 Sorry, I didn't follow this tread from the begining, so I hope I won't say
 anything stoopid or something that has already been said.
 If I understand, the problem here is all the dump of the stack and
 registers caused by a page default or something at the end of a shutdown.

 I have the same problem. I think it only happens on Motherboards with VIA
 chips. I don't mind about it since it doesn't cause any damage, but it is
 nice to get rid of that bad stuff.
 I solved the problem by modifying the /etc/rc.d/init.d/halt file and
 change the line
 eval $command -i -d -p
 to
 eval $command -i -d

 PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)

 HTH
 Flupke

 On Sun, 11 Jun 2000, Fran Parker wrote:

  I second what Ronald wrote...I went to DRAKCONF and
  found it there no problem and disabled it.  Shutdown and
  there were all the things on the screen again...full screen
  all over the screen...
 
  I also already had the power management in KDE disabled
  as well.
 
  Oh, well it was worth a shot.
 
  Anyway, reboot works just fine :)
 
  Bambi
 
 
  "Ronald J. Hall" wrote:
 
   Paul wrote:
  
Log in as root, or run "su"
Then run "setup" in a console
Go to system services, and uncheck the APM daemon. it is right below the
anacron daemon.
After a reboot you're all set!
   
Paul
  
   Hi. Well, I opened up a shell on my desktop,
   ran su, password, typed in "setup" and it told
   me, "bash: command not found".
  
   So I went into the DRAKCONF and ran startup,
   found it (under anacron, like you said) and
   disabled it. Unfortunately, after powering
   down, and rebooting, the problem still exists.
   I also have dmps disabled from the kde desktop
   (don't know if that needed to be or not). Any
   other possible ideas as to what it might be?
  
   (Thanks to Dennis Myers for the DRAKCONF tip)
  
   Thanks much!
  
   PS Did you see the reply I posted with the details
   on the screen that I'm left with? Maybe you can
   find a clue there...
  
   See ya...
 
 
 

 --
  There's no place like ~ ! 

Re: [newbie] Shutdown problem with v7.0...

[Dennis Myers]

Fran Parker wrote:

 That could be true flupke, mine is a VIA chipset.

 It doesn't seem to hurt anything, if I accidentally choose
 shutdown, I just choose alt-cntrl-del and it finishes it.

 But if it can be fixed...cool.  I will look into it with my system.

 Thanks,
 Bambi

 Now do you you know how to get lxdoom to work..it says it can't
 find an IWAD...I have downloaded the shareware 1.8 wad file,
 I have gone to get the iwad file they had and unzipped it...doom1.wad
 Anyway it can't find it and I tried to run it in terminal window to see
 it's complaints ... they only thing it says besides the memory size is
 it can't find an IWAD file!

 I am at a lose as to how to proceed.  Any help?

 Thanks in advance,
 Bambi

 flupke wrote:

  Sorry, I didn't follow this tread from the begining, so I hope I won't say
  anything stoopid or something that has already been said.
  If I understand, the problem here is all the dump of the stack and
  registers caused by a page default or something at the end of a shutdown.
 
  I have the same problem. I think it only happens on Motherboards with VIA
  chips. I don't mind about it since it doesn't cause any damage, but it is
  nice to get rid of that bad stuff.
  I solved the problem by modifying the /etc/rc.d/init.d/halt file and
  change the line
  eval $command -i -d -p
  to
  eval $command -i -d
 
  PS : http://www.mandrakeuser.org/troubles/tquick1.html :-)
 
  HTH
  Flupke
 
  On Sun, 11 Jun 2000, Fran Parker wrote:
 
   I second what Ronald wrote...I went to DRAKCONF and
   found it there no problem and disabled it.  Shutdown and
   there were all the things on the screen again...full screen
   all over the screen...
  
   I also already had the power management in KDE disabled
   as well.
  
   Oh, well it was worth a shot.
  
   Anyway, reboot works just fine :)
  
   Bambi
  
  
   "Ronald J. Hall" wrote:
  
Paul wrote:
   
 Log in as root, or run "su"
 Then run "setup" in a console
 Go to system services, and uncheck the APM daemon. it is right below the
 anacron daemon.
 After a reboot you're all set!

 Paul
   
Hi. Well, I opened up a shell on my desktop,
ran su, password, typed in "setup" and it told
me, "bash: command not found".
   
So I went into the DRAKCONF and ran startup,
found it (under anacron, like you said) and
disabled it. Unfortunately, after powering
down, and rebooting, the problem still exists.
I also have dmps disabled from the kde desktop
(don't know if that needed to be or not). Any
other possible ideas as to what it might be?
   
(Thanks to Dennis Myers for the DRAKCONF tip)
   
Thanks much!
   
PS Did you see the reply I posted with the details
on the screen that I'm left with? Maybe you can
find a clue there...
   
See ya...
  
  
  
 
  --
   There's no place like ~ ! 

Just took a look at the specs on my motherboard (Soyo 5EMA+)  and it has an ETEQ
chipset, guess what ETEQ  is just another name for VIA,  don't suppose Mandrake
Soft has a patch out to fix this glitch?  Anyway the pattern seems to be
consistant.

Re: [newbie] Shutdown problem with v7.0...

[Ronald J. Hall]

Dacia and AzureRose wrote:
 
 hmmm...both of the computers I've seen this problem on
 had Via chipsets on their motherboards.
 
 Dacia

Not sure if I have a Via chipset or not? I do
have a socket 7 MB, (Gigabyte GA-5AX), and it
uses the ALI Aladdin V AGPset... Oh well.

Re: [newbie] Shutdown problem with v7.0...

[Ronald J. Hall]

Fran Parker wrote:

 Now do you you know how to get lxdoom to work..it says it can't
 find an IWAD...I have downloaded the shareware 1.8 wad file,
 I have gone to get the iwad file they had and unzipped it...doom1.wad
 Anyway it can't find it and I tried to run it in terminal window to see
 it's complaints ... they only thing it says besides the memory size is
 it can't find an IWAD file!
 
 I am at a lose as to how to proceed.  Any help?
 
 Thanks in advance,
 Bambi

Hi. On my setup of lxdoom, the doom1.wad file
goes in /usr/share/games/doom. Hope this helps!

Re: [newbie] Shutdown problem with v7.0...

[Paul]

On Sat, 10 Jun 2000, Ronald J. Hall wrote:

Until shutdown. No matter how I shutdown, from
the graphical logon screen, to "shutdown now"
from a shell, I always get a final BW text
screen that displays a segmentation error, with
an error in line x, something to do with rec.d.

You listed your hardware well, but could you also be more specific about
the error message?
It is difficult to understand what happens when "something to do with
rec.d" is all the info we have.

Thanks for segmenting again,
Paul

-- 
I'm not a complete idiot.
Some parts are missing.

)0([[EMAIL PROTECTED]])0(
http://nlpagan.net -  ICQ 147208
Registered  Linux  User   174403

Re: [newbie] Shutdown problem with v7.0...

[Dacia and AzureRose]

My brother had this same problem and we found that in
his case it was because of a conflict between his
motherboard advanced power management features and the
way linux was trying to access those functions.

He disabled apmd and it stopped happening.


Dacia


--- "Ronald J. Hall" [EMAIL PROTECTED] wrote:
 Paul wrote:
 
  You listed your hardware well, but could you also
 be more specific about
  the error message?
  It is difficult to understand what happens when
 "something to do with
  rec.d" is all the info we have.
  
  Thanks for segmenting again,
  Paul
  
  --
  I'm not a complete idiot.
  Some parts are missing.
  
  )0([[EMAIL PROTECTED]])0(
  http://nlpagan.net -  ICQ 147208
  Registered  Linux  User   174403
 
 Hi Paul. Thanks for the reply. Okay. I'll do
 that next message. Just as soon as I shutdown
 and copy that message down. grin Its a full
 screen, so be prepared. ;-)
 
 BTW, I can shutdown and restart, and I do NOT
 get this problem. Odd, eh?
 


__
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com

Re: [newbie] Shutdown problem with v7.0...

[Fran Parker]

Same hereI don't shutdown the computer...I only reboot and shut
off the computer from there, I hate getting error messages! :)

Bambi


"Ronald J. Hall" wrote:

 Paul wrote:

  You listed your hardware well, but could you also be more specific about
  the error message?
  It is difficult to understand what happens when "something to do with
  rec.d" is all the info we have.
 
  Thanks for segmenting again,
  Paul
 
  --
  I'm not a complete idiot.
  Some parts are missing.
 
  )0([[EMAIL PROTECTED]])0(
  http://nlpagan.net -  ICQ 147208
  Registered  Linux  User   174403

 Hi Paul. Thanks for the reply. Okay. I'll do
 that next message. Just as soon as I shutdown
 and copy that message down. grin Its a full
 screen, so be prepared. ;-)

 BTW, I can shutdown and restart, and I do NOT
 get this problem. Odd, eh?

Re: [Re: [newbie] Shutdown problem with v7.0...]

[Jaguar]

I don't have your original message here...but I think you said you were using
an AMD CPU...I think there was a shutdown problem and a subsequent patch for
itmaybe that is the problem.  (if I am remembering your hardware
correctly)
HTH
Jaguar

"Ronald J. Hall" [EMAIL PROTECTED] wrote:
 Paul wrote:
 
  You listed your hardware well, but could you also be more specific about
  the error message?
  It is difficult to understand what happens when "something to do with
  rec.d" is all the info we have.
  
  Thanks for segmenting again,
  Paul
  
  --
  I'm not a complete idiot.
  Some parts are missing.
  
  )0([[EMAIL PROTECTED]])0(
  http://nlpagan.net -  ICQ 147208
  Registered  Linux  User   174403
 
 Hi Paul. Thanks for the reply. Okay. I'll do
 that next message. Just as soon as I shutdown
 and copy that message down. grin Its a full
 screen, so be prepared. ;-)
 
 BTW, I can shutdown and restart, and I do NOT
 get this problem. Odd, eh?


The Dogma chased the Stigma, and was hit by the Karma.


Get your own FREE, personal Netscape WebMail account today at 
http://webmail.netscape.com.

RE: [newbie] shutdown problem

[Alvarez, Angel]

halt

  Angel Claudio Alvarez


-Mensaje original-
De: evan light [mailto:[EMAIL PROTECTED]]
Enviado el: Jueves 13 de Abril de 2000 17:41
Para: newbie
Asunto: [newbie] shutdown problem


Hi there...having a bit of a problem with shutting down 7.0.  When I
issue the "shutdown now" command, everything seems fine and dandy until
it switches into "single-user" mode.  If I try ctl-ald-del at the
single-user prompt, I get the message "no authorized users logged in."
If I try shutdown again, it spins for a bit and goes right back to
single-user mode.  At that point, I couldn't do anything but cringe and
power it off..  Anybody have any ideas?

-evan-

Re: [newbie] shutdown problem

[mark willenbring]

shutdown -h now

--- evan light [EMAIL PROTECTED] wrote:
 Hi there...having a bit of a problem with shutting
 down 7.0.  When I
 issue the "shutdown now" command, everything seems
 fine and dandy until
 it switches into "single-user" mode.  If I try
 ctl-ald-del at the
 single-user prompt, I get the message "no authorized
 users logged in."
 If I try shutdown again, it spins for a bit and goes
 right back to
 single-user mode.  At that point, I couldn't do
 anything but cringe and
 power it off..  Anybody have any ideas?
 
 -evan-
 
 

__
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com

Re: [newbie] shutdown problem

[mark willenbring]

shutdown -h now

--- evan light [EMAIL PROTECTED] wrote:
 Hi there...having a bit of a problem with shutting
 down 7.0.  When I
 issue the "shutdown now" command, everything seems
 fine and dandy until
 it switches into "single-user" mode.  If I try
 ctl-ald-del at the
 single-user prompt, I get the message "no authorized
 users logged in."
 If I try shutdown again, it spins for a bit and goes
 right back to
 single-user mode.  At that point, I couldn't do
 anything but cringe and
 power it off..  Anybody have any ideas?
 
 -evan-
 
 

__
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com

Re: [newbie] shutdown problem

[Stephen F. Bosch]

evan light wrote:
 
 Hi there...having a bit of a problem with shutting down 7.0.  When I
 issue the "shutdown now" command, everything seems fine and dandy until
 it switches into "single-user" mode.

That doesn't at all fine and dandy to me. It shouldn't be going into
single user mode, it should be halting.

Are you getting error messages during the shutdown procedure?

-Stephen-

Re: [[newbie] shutdown problem]

[Michael Scottaline]

evan light [EMAIL PROTECTED] wrote:
 Hi there...having a bit of a problem with shutting down 7.0.  When I
 issue the "shutdown now" command, everything seems fine and dandy until
 it switches into "single-user" mode.  If I try ctl-ald-del at the
 single-user prompt, I get the message "no authorized users logged in."
 If I try shutdown again, it spins for a bit and goes right back to
 single-user mode.  At that point, I couldn't do anything but cringe and
 power it off..  Anybody have any ideas?
 
 -evan-
=
Try "shutdown -h now" w/o quotes.
If that doesn't work, try the same command after su-ing to root.
Mike 

"What contemptible scoundrel has stolen the cork to my lunch?"
--W. C. Fields


Get your own FREE, personal Netscape WebMail account today at 
http://webmail.netscape.com.

Re: [newbie] shutdown problem

[Mike Corbeil]

For problems of this sort, try reading the man page for the program or
utility you're trying to use and don't seem to be able to get to work as
you want.

E.g.,

% man shutdown


-h now is correct, but it's also important for newbies to be aware of
the man pages and knowing this can sometimes provide quicker answers
than asking in a mailing list.  Reading the man page on shutdown would
have given you the answer as quickly as it took for the initial question
to be written, let alone waiting for the reply.

mike



mark willenbring wrote:

 shutdown -h now

 --- evan light [EMAIL PROTECTED] wrote:
  Hi there...having a bit of a problem with shutting
  down 7.0.  When I
  issue the "shutdown now" command, everything seems
  fine and dandy until
  it switches into "single-user" mode.  If I try
  ctl-ald-del at the
  single-user prompt, I get the message "no authorized
  users logged in."
  If I try shutdown again, it spins for a bit and goes
  right back to
  single-user mode.  At that point, I couldn't do
  anything but cringe and
  power it off..  Anybody have any ideas?
 
  -evan-
 
 

 __
 Do You Yahoo!?
 Send online invitations with Yahoo! Invites.
 http://invites.yahoo.com

Re: [newbie] shutdown problem fixed

[John Aldrich]

On Tue, 13 Jul 1999, you wrote:

 
 there isn't a single difference between su - and loging in as root (ok one
 the utmp entry, but that has nothing todo with anything major)
  
Well, MY experience has been that there are some
applications that can ONLY be run as "root." Editing system
files appears to be one of those functions. I may not know
much about theory and all that, but I *do* know that in the
past when I've tried to run system commands as an SU-ed
user, it wouldn't let me. *shrug*

 -- 
John Aldrich
COL Tech Support
===
Chattanooga Online Internet
423-267-8867

Re: [newbie] shutdown problem fixed

[Axalon]

On Tue, 13 Jul 1999, John Aldrich wrote:

 On Tue, 13 Jul 1999, you wrote:
 
  
  there isn't a single difference between su - and loging in as root (ok one
  the utmp entry, but that has nothing todo with anything major)
   
 Well, MY experience has been that there are some
 applications that can ONLY be run as "root." Editing system
 files appears to be one of those functions. I may not know
 much about theory and all that, but I *do* know that in the
 past when I've tried to run system commands as an SU-ed
 user, it wouldn't let me. *shrug*
 
  -- 
   John Aldrich
   COL Tech Support
 ===
 Chattanooga Online Internet
   423-267-8867
 

For a program to run as root and not when su - root, it would have to
step thru parent pid's looking specificly for su (it could test the parent
pids uid, they all eventualy lead to root), which is posible but ugly.
As for editing system files, I am quite certain the filesystem drivers do
not check for su as a parent pid, so when editing files if your root or su
- root it will write the file. So if you do find a program that does this
let me know i'd like a look at it.

Re: [newbie] shutdown problem fixed

[Nick Kay]

At 12:20 13/07/99 -0400, you wrote:
On Tue, 13 Jul 1999, you wrote:

 For a program to run as root and not when su - root, it would have to
 step thru parent pid's looking specificly for su (it could test the parent
 pids uid, they all eventualy lead to root), which is posible but ugly.
 As for editing system files, I am quite certain the filesystem drivers do
 not check for su as a parent pid, so when editing files if your root or su
 - root it will write the file. So if you do find a program that does this
 let me know i'd like a look at it.

Okone I can give you right off the top is "timed" It
will NOT run as SuperUser, but it WILL run as "root." It
comes back with "timed command not found." This is from a
text-mode prompt, not a window prompt, just a standard
shell prompt. However, I run that logged in as "root" and
it works just fine.

When you do "su" you don't always get the PATH environment of root
(depending on the system)
The above error was because "timed" is not in your path - not
because you cannot run it. Try "/usr/sbin/timed" instead.

ttfn
nick@nexnix



 -- 
   John Aldrich
   COL Tech Support
===
Chattanooga Online Internet
   423-267-8867

Re: [newbie] shutdown problem fixed

[Dan Brown]

John Aldrich wrote:

 Okone I can give you right off the top is "timed" It
 will NOT run as SuperUser, but it WILL run as "root." It
 comes back with "timed command not found." This is from a

It will still run just fine as su, but you need to specify the path to
it.  When you su, it doesn't run the normal login files for root, which
means that anything that's in root's path, but not in your path, won't
be visible.  There is an option to su to change this behavior, but I
don't remember what it is.  man su would tell you, though.

--
Dan Brown, KE6MKS, [EMAIL PROTECTED]
Meddle not in the affairs of dragons, for you are crunchy and taste good
with ketchup.

Re: [newbie] shutdown problem fixed

[Bernhard Rosenkränzer]

On Tue, 13 Jul 1999, John Aldrich wrote:

 Okone I can give you right off the top is "timed" It
 will NOT run as SuperUser, but it WILL run as "root." It
 comes back with "timed command not found." This is from a
 text-mode prompt, not a window prompt, just a standard
 shell prompt. However, I run that logged in as "root" and
 it works just fine.

You did just "su", not "su -". The difference is that "su -" reruns the
login scripts, etc., so you get the right PATH for root.

timed is in /usr/sbin, which is in the PATH of root, but not the PATH of
normal users.

Either do "su -", or stay with "su" and run /usr/sbin/timed rather than
just timed.

LLaP
bero

Re: [newbie] shutdown problem fixed

[John Aldrich]

On Tue, 13 Jul 1999, you wrote:
 
 When you do "su" you don't always get the PATH environment of root
 (depending on the system)
 The above error was because "timed" is not in your path - not
 because you cannot run it. Try "/usr/sbin/timed" instead.
 
Ahh...Ok. That makes a bit of sense there... :-) I'm sure
there are other apps that won't run for that reason.

 -- 
John Aldrich
COL Tech Support
===
Chattanooga Online Internet
423-267-8867

Re: [newbie] shutdown problem fixed

[John Aldrich]

On Tue, 13 Jul 1999, you wrote:
 
 You did just "su", not "su -". The difference is that "su -" reruns the
 login scripts, etc., so you get the right PATH for root.

Ah. I just learned something new. :-) I didn't know about
"su -"  Thanks. :-)
-- 
John Aldrich
COL Tech Support
===
Chattanooga Online Internet
423-267-8867

Re: [newbie] shutdown problem fixed

[John Aldrich]

Yep. If you've logged in as "root" and not SU-ed to root (two different
things... there are some things that you just can't do as "SU" that you can
do as "root") It very well may be time to reinstall. I thought I was at that
point last week, but with a little help from the author of KMail, I managed
to salvage my install w/o having to log back in. 'Course now I have a couple
of half-installed X-based email clients... Oh, well... :-)
John

- Original Message -
From: Rhichard Barth  Family [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 11, 1999 5:22 PM
Subject: Re: [newbie] shutdown problem fixed




 John Aldrich wrote:

  Log in as "root" instead of a normal user. Try that instead of SU.
  John

 I did log on as "root"
 It insists that my mtab and fstab files/Dir's are gone...
 I'm going to start over again.
 Axalon Thank you for your help.But it's time to clean-up my mistakes
and
 start
 new, I will be doing the partitions the way we talked about, however, my
 back-ups are on my Network to a Back-up drive Onstream 30gig...I just
didn't get
 that far during my 6.0 install
 Oh I'm sorry Thank you too, John.
 This has got to be one of the greatest sites there is.
 I owe you guys.
 I'll be back!

 Rhich
 "The Phoneless Guy"
 Icq 8150164


 
  - Original Message -
  From: Rhichard Barth  Family [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, July 11, 1999 7:54 AM
  Subject: Re: [newbie] shutdown problem fixed
 
  
  
   John Aldrich wrote:
  
Are you editing the file as "root"? If not, that's a "system file"
and
  only
"root" can edit it.
- Original Message -
From: Rhichard Barth  Family [EMAIL PROTECTED]
    To: [EMAIL PROTECTED]
Sent: Saturday, July 10, 1999 6:48 PM
Subject: Re: [newbie] shutdown problem fixed
At the # I type SU? I believe (or it likes me to think I am) SU.
  
   It must be SU because if I don't type that I can't even use MC, but
once
  in MC
   all I can do is look, can't touchtried that when Axalon suggested
  removing
   the -p in SShalt, but it won't let me save the changes.
  
   


 Axalon wrote:

  On Wed, 30 Jun 1999, Flight16 wrote:
 
   For anybody else having the problem I was of a huge error
crashing
their system
   whenever the shutdown script tried to halt, it is because of
the
  power
off command,
   like Axalon said, but the specific problem comes from the -p
  parameter
that tries to
   power down your pc.  This command is near the end in SShalt
  script..
Just look in
   your /etc/rc.d/rc0.d directory, and edit one of the last lines
  which
contain "halt -i
   -d -p" so that it doesn't contain the p, and is just
"halt -i -d"
  and
any other
   parameters you used with it.  Hope this helps somebody else
out
  there.
See ya.
  
   Flight16
  
 

 Found it !!
 but it won't let me save the changes..
 can I rename it?


  

Re: [newbie] shutdown problem fixed

[Axalon]

On Mon, 12 Jul 1999, John Aldrich wrote:

 Yep. If you've logged in as "root" and not SU-ed to root (two different
 things... there are some things that you just can't do as "SU" that you can
 do as "root") It very well may be time to reinstall. I thought I was at that
 point last week, but with a little help from the author of KMail, I managed
 to salvage my install w/o having to log back in. 'Course now I have a couple
 of half-installed X-based email clients... Oh, well... :-)
 John

there isn't a single difference between su - and loging in as root (ok one
the utmp entry, but that has nothing todo with anything major)
 
 - Original Message -
 From: Rhichard Barth  Family [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, July 11, 1999 5:22 PM
 Subject: Re: [newbie] shutdown problem fixed
 
 
 
 
  John Aldrich wrote:
 
   Log in as "root" instead of a normal user. Try that instead of SU.
   John
 
  I did log on as "root"
  It insists that my mtab and fstab files/Dir's are gone...
  I'm going to start over again.
  Axalon Thank you for your help.But it's time to clean-up my mistakes
 and
  start
  new, I will be doing the partitions the way we talked about, however, my
  back-ups are on my Network to a Back-up drive Onstream 30gig...I just
 didn't get
  that far during my 6.0 install
  Oh I'm sorry Thank you too, John.
  This has got to be one of the greatest sites there is.
  I owe you guys.
  I'll be back!
 
  Rhich
  "The Phoneless Guy"
  Icq 8150164
 
 
  
   - Original Message -
   From: Rhichard Barth  Family [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Sunday, July 11, 1999 7:54 AM
   Subject: Re: [newbie] shutdown problem fixed
  
   
   
John Aldrich wrote:
   
 Are you editing the file as "root"? If not, that's a "system file"
 and
   only
 "root" can edit it.
 - Original Message -
 From: Rhichard Barth  Family [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, July 10, 1999 6:48 PM
 Subject: Re: [newbie] shutdown problem fixed
 At the # I type SU? I believe (or it likes me to think I am) SU.
   
It must be SU because if I don't type that I can't even use MC, but
 once
   in MC
all I can do is look, can't touchtried that when Axalon suggested
   removing
the -p in SShalt, but it won't let me save the changes.
   

 
 
  Axalon wrote:
 
   On Wed, 30 Jun 1999, Flight16 wrote:
  
For anybody else having the problem I was of a huge error
 crashing
 their system
whenever the shutdown script tried to halt, it is because of
 the
   power
 off command,
like Axalon said, but the specific problem comes from the -p
   parameter
 that tries to
power down your pc.  This command is near the end in SShalt
   script..
 Just look in
your /etc/rc.d/rc0.d directory, and edit one of the last lines
   which
 contain "halt -i
-d -p" so that it doesn't contain the p, and is just
 "halt -i -d"
   and
 any other
parameters you used with it.  Hope this helps somebody else
 out
   there.
 See ya.
   
Flight16
   
  
 
  Found it !!
  but it won't let me save the changes..
  can I rename it?
 
 
   
 
 

Re: [newbie] shutdown problem fixed

[John Aldrich]

Are you editing the file as "root"? If not, that's a "system file" and only
"root" can edit it.
- Original Message -
From: Rhichard Barth  Family [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 10, 1999 6:48 PM
Subject: Re: [newbie] shutdown problem fixed




 Axalon wrote:

  On Wed, 30 Jun 1999, Flight16 wrote:
 
   For anybody else having the problem I was of a huge error crashing
their system
   whenever the shutdown script tried to halt, it is because of the power
off command,
   like Axalon said, but the specific problem comes from the -p parameter
that tries to
   power down your pc.  This command is near the end in SShalt script..
Just look in
   your /etc/rc.d/rc0.d directory, and edit one of the last lines which
contain "halt -i
   -d -p" so that it doesn't contain the p, and is just "halt -i -d" and
any other
   parameters you used with it.  Hope this helps somebody else out there.
See ya.
  
   Flight16
  
 

 Found it !!
 but it won't let me save the changes..
 can I rename it?

Re: [newbie] shutdown problem fixed

[John Aldrich]

Log in as "root" instead of a normal user. Try that instead of SU.
John
- Original Message -
From: Rhichard Barth  Family [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 11, 1999 7:54 AM
Subject: Re: [newbie] shutdown problem fixed




 John Aldrich wrote:

  Are you editing the file as "root"? If not, that's a "system file" and
only
  "root" can edit it.
  - Original Message -
  From: Rhichard Barth  Family [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Saturday, July 10, 1999 6:48 PM
  Subject: Re: [newbie] shutdown problem fixed
  At the # I type SU? I believe (or it likes me to think I am) SU.

 It must be SU because if I don't type that I can't even use MC, but once
in MC
 all I can do is look, can't touchtried that when Axalon suggested
removing
 the -p in SShalt, but it won't let me save the changes.

 
  
  
   Axalon wrote:
  
On Wed, 30 Jun 1999, Flight16 wrote:
   
 For anybody else having the problem I was of a huge error crashing
  their system
 whenever the shutdown script tried to halt, it is because of the
power
  off command,
 like Axalon said, but the specific problem comes from the -p
parameter
  that tries to
 power down your pc.  This command is near the end in SShalt
script..
  Just look in
 your /etc/rc.d/rc0.d directory, and edit one of the last lines
which
  contain "halt -i
 -d -p" so that it doesn't contain the p, and is just "halt -i -d"
and
  any other
 parameters you used with it.  Hope this helps somebody else out
there.
  See ya.

 Flight16

   
  
   Found it !!
   but it won't let me save the changes..
   can I rename it?
  
  

Re: [newbie] shutdown problem fixed

[Rhichard Barth Family]

John Aldrich wrote:

 Log in as "root" instead of a normal user. Try that instead of SU.
 John

I did log on as "root"
It insists that my mtab and fstab files/Dir's are gone...
I'm going to start over again.
Axalon Thank you for your help.But it's time to clean-up my mistakes and
start
new, I will be doing the partitions the way we talked about, however, my
back-ups are on my Network to a Back-up drive Onstream 30gig...I just didn't get
that far during my 6.0 install
Oh I'm sorry Thank you too, John.
This has got to be one of the greatest sites there is.
I owe you guys.
I'll be back!

Rhich
"The Phoneless Guy"
Icq 8150164



 - Original Message -
 From: Rhichard Barth  Family [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, July 11, 1999 7:54 AM
 Subject: Re: [newbie] shutdown problem fixed

 
 
  John Aldrich wrote:
 
   Are you editing the file as "root"? If not, that's a "system file" and
 only
   "root" can edit it.
   - Original Message -
   From: Rhichard Barth  Family [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Saturday, July 10, 1999 6:48 PM
   Subject: Re: [newbie] shutdown problem fixed
   At the # I type SU? I believe (or it likes me to think I am) SU.
 
  It must be SU because if I don't type that I can't even use MC, but once
 in MC
  all I can do is look, can't touchtried that when Axalon suggested
 removing
  the -p in SShalt, but it won't let me save the changes.
 
  
   
   
Axalon wrote:
   
 On Wed, 30 Jun 1999, Flight16 wrote:

  For anybody else having the problem I was of a huge error crashing
   their system
  whenever the shutdown script tried to halt, it is because of the
 power
   off command,
  like Axalon said, but the specific problem comes from the -p
 parameter
   that tries to
  power down your pc.  This command is near the end in SShalt
 script..
   Just look in
  your /etc/rc.d/rc0.d directory, and edit one of the last lines
 which
   contain "halt -i
  -d -p" so that it doesn't contain the p, and is just "halt -i -d"
 and
   any other
  parameters you used with it.  Hope this helps somebody else out
 there.
   See ya.
 
  Flight16
 

   
Found it !!
but it won't let me save the changes..
can I rename it?
   
   
 

Re: [newbie] shutdown problem fixed

[Axalon]

On Wed, 30 Jun 1999, Flight16 wrote:

 For anybody else having the problem I was of a huge error crashing their system
 whenever the shutdown script tried to halt, it is because of the power off command,
 like Axalon said, but the specific problem comes from the -p parameter that tries to
 power down your pc.  This command is near the end in SShalt script..  Just look in
 your /etc/rc.d/rc0.d directory, and edit one of the last lines which contain "halt -i
 -d -p" so that it doesn't contain the p, and is just "halt -i -d" and any other
 parameters you used with it.  Hope this helps somebody else out there.   See ya.
 
 Flight16
 

Ah yes, an even better idea then you don't have to worry about a phone
ringing and missing the chance to power off manualy.

thanks guy..

Re: [newbie] shutdown problem fixed

[John Aldrich]

BTW, on my machine (RedHat 6.0) it was not called SShalt, I believe it was
calles S0halt. :-) I took a guess that it was the right script and opened it
with joe. It was. :-)
- Original Message -
From: Axalon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 28, 2000 1:55 PM
Subject: Re: [newbie] shutdown problem fixed




 On Wed, 30 Jun 1999, Flight16 wrote:

  For anybody else having the problem I was of a huge error crashing their
system
  whenever the shutdown script tried to halt, it is because of the power
off command,
  like Axalon said, but the specific problem comes from the -p parameter
that tries to
  power down your pc.  This command is near the end in SShalt script..
Just look in
  your /etc/rc.d/rc0.d directory, and edit one of the last lines which
contain "halt -i
  -d -p" so that it doesn't contain the p, and is just "halt -i -d" and
any other
  parameters you used with it.  Hope this helps somebody else out there.
See ya.
 
  Flight16
 

 Ah yes, an even better idea then you don't have to worry about a phone
 ringing and missing the chance to power off manualy.

 thanks guy..

Re: [newbie] shutdown problem fixed

[John Aldrich]

Hmm...really? I didn't know you could edit a symlinkOTOH, I suppose you
can, now that I think about it... :-)
- Original Message -
From: Axalon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 30, 1999 8:35 PM
Subject: Re: [newbie] shutdown problem fixed




 On Wed, 30 Jun 1999, John Aldrich wrote:

  BTW, on my machine (RedHat 6.0) it was not called SShalt, I believe it
was
  calles S0halt. :-) I took a guess that it was the right script and
opened it
  with joe. It was. :-)

 those are all symlinks anyway the true filename is /etc/rc.d/init.d/halt
 y