Re: KDE Crash on logout

Hi,

i'd the same problem on a PCG-FX801FR and after a KDE update by 
mandrake-update all is now ok !

Jack Coates a écrit :
> On Mon, 2003-07-28 at 02:31, John Andersen wrote:
> 
>>On Sunday 27 July 2003 10:36 pm, Deepak Chawla wrote:
>>
>>>Hi Folks,
>>>I just bought a Sony Vaio laptop and installed Mandrake 9.1 on it.  I am
>>>having a few problems with it.
>>>
>>>1. KDE crashes the system on logout. I read a few messages posted on the
>>>mailing list about this, but none of them had any information about any
>>>fixes. Currently, to logout, what I do is, at the command prompt, init 3
>>>and then init 5. Does anyone know of a fix for this ? I need this badly :(
>>>
> 
> 
> this is very likely to be the problem John describes -- see below.
> 
> 
>>>2. Mandrake 9.1 has been much better than RedHat in recognizing most of the
>>>devices, however, there are a few devices still unconfigured (Modem, IEEE
>>>1394 Controller and the memory stick reader). Does anyone know of suitable
>>>drivers for this ?
>>>
>>>thanks.
>>>-deepak
>>
>>Often this is caused by the system attempting to unload acpi modules
>>(specifically processor and thermal).  However, you didn't indicate 
>>wether you even have acpi running, and I don't know enough about
>>Mandrake 9.1 to know if it does acpi out of the box.
>>
> 
> 
> no, it doesn't. He'll need to edit /etc/lilo.conf and use the following
> append string:
> append="pci=biosirq resume=/dev/hda5 devfs=mount acpi=on"
> Change the resume entry to point at your swap partition, this is for
> swsusp suspend-to-disk.
> Also do a `chkconfig acpid on`, then reboot.
> 
> 
>>You also failed to specify model number, so we are left 
>>guessing about that as well.
>>
>>And you say it crashes, but Linux is NEVER that vague,
>>it always provides more information than that.  
>>
>>Do you have Blinking Cap-Lock lights?
>>Can you innitiate a log out and then quickly switch to console 10
>>(ctrl-alt-F10) and see what it was doing at the time of the crash?
>>
>>Do you have entries in /proc/acpi ?
>>Does lsmod display a module called processor and another
>>called thermal?
>>
>>Can you trigger the same crash by typing (as root) 
>>  rmmod processor   ?
>>
>>If the answer to the last few items are YES, then you need
>>to set your runlevels so that acpid is started ONLY at boot
>>time and not started or stopped at any other runlevel.
>>
>>How you do that with Mandrake is beyond me, as I haven't
>>run mandrake in years.
> 
> 
> Pretty much just like any other System V Unix -- look in
> /etc/rc.d/init.d. Edit acpi (not acpid) and look at the chkconfig line.
> This has the levels where the modules should load, the order they should
> load in, and the order they should load out. Mine currently reads:
> # chkconfig: 2345 04 70
> So run in all levels except single user, start early and exit late. This
> works fine. If you want to make it exit later, change the last number to
> 90 or so.