Actually, I managed to restore the system after running fsck. I also had Opera installed which I removed. At the moment Ubuntu 9.04 64 bit runs stable and I can use the wireless. Also I can hibernate and suspend but sometimes after suspend the caps lock light starts blinking. So I do not have a real clue what caused the problems. It could be:
1. I forcefully shutdown the machine after a period of no response which corrupted the filesystem.
2. The error was caused by a faulty Opera install (which I have now removed)
3. Either suspend or hibernate caused the problems at the first place followed by problem 1 and 2
4. I use the machine on different networks and I am in the habit of suspending the machine on the one network and starting the machine up on the other network.
On a Dell home computer I now experience the same problem. The filesystem is corrupted as well. So I will have to run fsck there as well. Which by the way defaults to the ext2 filesystem, so you have to specify ext3 explicitly!!
Still I think these are quite a serious problems and if Ubuntu wants to get rid of their first and main bug, then these kind of problems should be addressed. As much as I sympathize with the philosophy behind Ubuntu, I have to admit that Windows XP has never failed me in this way. But I will continue to use Ubuntu as operating system of choice for now.
Actually, I managed to restore the system after running fsck. I also had Opera installed which I removed. At the moment Ubuntu 9.04 64 bit runs stable and I can use the wireless. Also I can hibernate and suspend but sometimes after suspend the caps lock light starts blinking. So I do not have a real clue what caused the problems. It could be:
1. I forcefully shutdown the machine after a period of no response which corrupted the filesystem.
2. The error was caused by a faulty Opera install (which I have now removed)
3. Either suspend or hibernate caused the problems at the first place followed by problem 1 and 2
4. I use the machine on different networks and I am in the habit of suspending the machine on the one network and starting the machine up on the other network.
On a Dell home computer I now experience the same problem. The filesystem is corrupted as well. So I will have to run fsck there as well. Which by the way defaults to the ext2 filesystem, so you have to specify ext3 explicitly!!
Still I think these are quite a serious problems and if Ubuntu wants to get rid of their first and main bug, then these kind of problems should be addressed. As much as I sympathize with the philosophy behind Ubuntu, I have to admit that Windows XP has never failed me in this way. But I will continue to use Ubuntu as operating system of choice for now.