They say suse works. The problem is to get suse I need to wait a 30 days download of 4gb.

My system became too corrupted now. I suspect also that the graphics driver has an issue. Sometimes it freezes at boot and there's a white line in the screen freezed

I just strangely lost an extremely important document i typed in open office (20 pages i need to present this week for a lecture).
The system freezed twice meanwhile typing, I had to force restart, i re-open the document, at the end i had it duplicated, but one with just the first page. When i saved the document (the 20 pages), afterwords, quite strangely, it was the only page who was saved over the final version. In microsoft office i could always solve this kind of problem searching for the file extensions of autobackup files and recovering parts of text. I tryed to search *.bak and nothing. THe backup folder has only dic files. And the versions command is also empty.
Only headaches

If you lose any documents, may want to have a look at photorec, which is a recovery application. It's not in the repositories but it's not easy to find if you use google. It does take a while to run (but it's faster than simply redoing a 20 page text) but you can narrow the search down by specifying the document format. You'll also need sufficient space for the application to write its results to. It makes a copy of all that it finds so it will return at least as much as the size of the parition that it is searching.

By the way, has your laptop got any entries related to APM? That is the predecessor to ACPI so, who knows, it may provide a workaround.

Hi, thanks a lot for the program advice. I found it, but there is not a .deb version, only tar and rpm which means a very difficult instalation, no?

About rpm, I see it in "services", but I had it unmarked, because I tought it could make interference with ACPI.

No need to install. Just extract the tar.gz version wherever you like. Then cd into the folder and run the executable. That should be something like ./photorec if I remember well.

Thanks!

I run it in shell as root (didn't allow me to access the program as user, which starts to irritate me this impossibility to access the root login graphically, like if I was a kido who needs protection from myself)
But doesn't seem to have a file option for open office files (odt), so I just recovered txt and doc. And there's more than 56000 which is like trying to find a nail in sand mointain!

About the shutdown problem my laptop assistance didn't understood my questions about the ACPI and DSDT. They just answer LG doesn't provide linux drivers!!
I see I will have to find myself back to windows. At least there I know how to handle with problems.

you shouldn't log in as root graphically anyways, its a security hazard, and there is no need for you to

Well, yes, photorec can't recover names so you end up with tons of unnamed files. If you more or less know the size of the text you are looking for, you can simply filter them by size. If you text was 20 pages, you'll find that there really aren't all that many text files in that category.

My old desktop HewPack HP230MT I used WUBI cause i failed to do the resizing and therefore the partition. So I tried wubi instead and that one had no shutdown problem while my AOpen XC Cube Small barebone that use fairly modern intel chip set 915 failed I don't remember if I tried to resize and partition that one. Most likely not cause I decided to use the HP as a linux machine but keep windows on it so I could do windows stuff.

So the HP had compatible bios and hardware. Sadly I only have 256 MByte memory on the HP but Firefox do work. I could surf and log into the forum using linux. So I could practice linux on that one. Have some 10Giga for new applications? Wubi had only fiesty fawn I guess. But the 7.1 Gudsty may already have arrived on wubi. I did this yesterday.

Sorry for jumping on the bandwagon but I also have the shutdown issue on a machine with an Asus P5GDC deluxe mobo. If I remember well there has been a bug report opened specifically for this mobo.

BTW the bug has always existed for me since 5.10 on this machine. I have tried everything imaginable and retrievable on the net, I've even flashed the BIOS (a bit dangerous when everything is actually working), absolutely no joy. Ubuntu won't shut down. Mandriva 200X and Suse 10.X no problem, it's just Ubuntu. Weird.

Those of us users who can't get rid of the bug might just have to get used to it. It's difficult for me though as I sometimes have to rush out. I my hectic I just do the 'soft' shut down and when I come back hours later I find the machine still running, stuck on the Ubuntu progression bar.
not good....

I am surprised that so few care about it among those who have the knowledge.

I found this that maybe could help us.

http://www.kroah.com/log/linux/devic...rt_needed.html

It is not 100% exactly what we want cause this was about devices. And for us it seems to be the motherboard.

But read it. 300+ eager programmers wanting to help with problems with Linux.

At least one of them might care about us.

I'm totally noob so could you write to them.

I have confirmed failure to explain things in English so if I write to them about our problem they just go What?!! and don't get a thing and we loose their interest.

And if we fail to get help from them what about this:
http://ftp.kernel.org/pub/linux/kern...es/README.ACPI

Hopefully this one is related
http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems

Sorry to insist but I've got an idea - I'm sure I'm not the first to think of this but I'll give it a try.

As I mentioned before, shutdown works properly on Mandriva. Therefore there must be some element that makes it work, as opposed to Ubuntu. As I'm a tech boob when it comes to details I can't tell if Ubuntu is lacking something or has something 'too much' in comparison to other distros where the shutdown works.

(I'm actually thinking of the OSX world where you have kext files (kernel extensions) which allow you to influence a lot of hardware-related things. Worst case you could kill your install but well...)

If some guru can tell us what it is that makes a system shut down properly - ie the files that control it - couldn't you just copy those files from another distro to Ubuntu and off you go?

You can have a laugh now if that's way too far-fetched but where's the problem in trying? I would just need to know which those elements are.

Any takers?

... have you tried Linux Mint? I've recently had odd things happen with Ubuntu which did not happen in Mint. Since they are mostly the same, people who want ubuntu without a bug may be well advised to try this.

I've heard of it but never tried it. Perhaps worth a shot for myself.

The thing is, this install is actually for my wife who loves Ubuntu and is very used to it. I can understand if somebody isn't really keen on switching to another distro if shutdown is the only issue.

The point I was trying to make is that there must be some relatively simple way to patch this without much command line and coding knowledge (I suppose) as it does work in other distros on basically the same kernel.

Shutdown does work even in Ubuntu Studio on the same machine. I just can't leave it on there for other much more complicated issues (I can't get into Gnome at all, it stays on a command line prompt).

Anyway I'll insist on the shutdown issue

Here is an extreme long shot so if it fails do bear with me.

http://www.linuxfromscratch.org/

So if I get it. They describe the whole process so somewhere in there they deal with Shut Down and ACPI and DTST and what could go wrong. Or me too much of a N00b to get optimistic over nothing.

I second that one should look into distros that do work. And find somebody we could ask

What is different from Ubuntu in that distro.

Most likely it could be the Kernel cause I used Google and searched for the words:
Linux kernel shutdown

and many many told about people having this shutdown problem and all of them had tested numerous shortcuts and Command Line directives? but to no help.
I did found a guy mentioning he had found a distro that didn't have it. Gento? or Mandriva. But Iwas sleepy and thtought I would remember but next day my poor memory had lost it.

So it should be something that the Kernel fail to do right. So if we could find those that do it that would be a good start.

Yes it would definitely be nice to find somebody who's willing to make the effort. I suppose it's got to be somebody though, apart from being a true tech head, who has the problematic hardware at hand to test. Unfortunately, this is where the scatteredness of the Linux world shows its not-so-nice rear side.

The thing I can't get my head around is that every Ubuntu release I tried so far had the exact same shutdown problem. The kernels were all different. The other thing is that at some point I had an Ubuntu release which had the same kernel as Mandriva. I don't remember which one it was. The problem existed in Ubuntu but not in Mandriva, so I assume it must be a distro specific problem.