Have you ever tried puppy linux ? It uses a lot less ram and hard drive space than lubuntu . It might be something to try . It is not as easy to use but it is super fast and works great .
So how does
as mentioned above work?Code:sudo apt-get clean sudo apt-get autoremove
After that please post (in CODE tags) the output from
So I guess that`s actually a root shell prompt. I tried those commands at that prompt and they do nothing.
I can select Clean that way, and it seems to run okay. But as soon as I hit resume normal boot, it acts the same way...Lubuntu screen, flicker, gone.
I`m thinking maybe it`s a lost cause...
Klunker; Hi !
Let's not give up so easily !
Try this to get to a terminal:
Boot the Lubuntu install, as soon as the bios screen clears depress and hold the right shift key -> grub's boot menu;
With a "non-recovery" kernel highlighted depress the 'e' key for edit mode; -> boot parameters screen;
arrow down and across to the terms "quiet splash" and replace them with the term "text" - with out the quotes;
key combo ctl+x to continue the boot process -> to a text login (TTY1).
Enter your user name and then your password - there is no response to the screen when the password is entered (security reasons).
Now perform mörgæs' directive.
my little bit to help
Klunker; Hey, Making progress !
OK, The problem is identified as no disk space in the '/' directory.
So, let's see what is using it all up.
and post back the output of the "du" command.Code:cd / sudo du -sx * | sort -n cd ##returns your Present Working Directory to your /home directory##
If you need to drill down further, use cd to move to a directory of interest then repeat the du command.
The results are in megabytes,
df -m says "you are out of space", and du -sx tells you where your space hogs are .
Then we can look at a means to remove files to get that space back.
all in the process
Rerun the commands as given, and give the 'du' command lots of time to complete. It takes a lot of time to look at every file on the system and sort them out.
As to proc, ignore that output, proc is a virtual file system, constantly changing so can not get a handle on it. That is normal for that command.
ain't no big deal