Kubuntu/Ubuntu does not remove everything from memory at shutdown

Mark Greenwood fatgerman at ntlworld.com
Sat Mar 13 12:16:30 UTC 2010

On Saturday 13 Mar 2010 11:41:19 Reinhold Rumberger wrote:
> On Saturday 13 March 2010, Steve Morris wrote:
> <snipping /etc/init.d/killprocs>
> > I looked at the /etc/rc6.d/S20sendsigs which are the scripts that
> > get processed at shutdown.
> You're right, killprocs is for runlevel 1. Should've paid closer 
> attention to that.
> > This script is very similar to what
> > you have listed above, but as far as I can see it is issuing
> > invalid killall5 commands that are invalid.
> Hmm, looking through sendsigs, I can't confirm that the commands are 
> invalid. Why would you think so?
> > I use a Soundblaster Audigy LE sound card for which there is no
> > driver in Win 7, and the Win 7 driver from the vendor that
> > supposedly supports all versions of the Audigy card up to the
> > current Soundblaster Audigy 4 does not work with the card either
> > (it says there is no supported hardware when you try to install
> > it), so I am using the Win XP drivers supplied with the card
> > which work fine.
> You know, if you had actually said that from the beginning, there 
> might have been a lot more decent responses.
> That said, you're using an unsupported driver for a not natively 
> supported sound card and are blaming *Ubuntu* that it isn't working? 
> And you don't see anything wrong with that?
> The fact that it's working properly after Mandriva is likely pure 
> coincidence, as is the fact that the sound card is working with the 
> XP drivers.
> You do know that MS apparently completely overhauled the driver 
> framework and that few or no XP drivers work properly with Vista or 
> Win7?
> > As I understand it the driver will ask the
> > hardware what it is and what features it supports. So if apps are
> > being shutdown properly then it seems to me that the Ubuntu
> > driver is configuring the hardware as a device that the windows
> > driver doesn't support.
> Right, because Ubuntu reassembles the hardware specifically to make 
> it incompatible with Win7...
> Funnily, we're right back where we started: your win driver isn't 
> properly initialising the hardware.

You're completely ignoring the information before you. You're not the only one, this is exactly the reason I gave up with my original bug report.

Let me see if I can explain it any more clearly. Perhaps something is being lost in translation.

With a choice of three OSs, the only combination that does not work is when I boot *from* Kubuntu into another. The only common factor in every failing case is that I *start* in Kubuntu. How many more ways can I explain it? There is only one logical conclusion from this, and it is that Kubuntu is doing something different.

This is supported by the observable facts. When I reboot from Windows or Mandriva, my laptop does a proper restart - I see the BIOS POST screen and I get a little beep, like I do when I switch it on. When I reboot from Kubuntu, I never see the BIOS POST screen and I do not get the beep; Kubuntu goes directly from its shutdown screen to the Grub menu, and this clearly leaves the hardware in an unstable state because most of it doesn't work properly afterwards, in any OS.

Do you now accept that Kubuntu is not resetting my hardware properly when I choose 'Restart Computer'.

This only applies on my Sony laptop. My Acer laptop and my desktop reset properly. I know it could be a BIOS issue, but if it is then why does Mandriva work?


>   --Reinhold

More information about the kubuntu-users mailing list