[SOLVED] Best kernel for 4gb ram + Boot swap problem

[Aleph]

Hi friends,

I have got a new toy, an old Lenovo T61 Thinkpad (4Gb Ram - 2,2 Ghz - Nvidia Card)


Wich kernel sould I install, the 2.6.38.0-pclos.3.pae? How install it, from the repos?

Thanks

[rubentje1991]

I'd say, the .pae, or maybe even better, the pae.bfs one 

Installing it by searching for "kernel" in Synaptic; select and install the one you like to have, and reboot 

[parnote]

+1 for pae.bfs! (8 GB RAM here)

parnote

[menotu]

I'd say, the .pae, or maybe even better, the pae.bfs one 

Installing it by searching for "kernel" in Synaptic; select and install the one you like to have, and reboot 

Additionally, on the first reboot it may take a few minutes or so for the kernel to "build" itself into your system so please be patient on that boot.

It will become your default boot option but your other kernels will still be in the list in case you want to use it/them again.

It's also good practice to not remove your other kernel(s) until you are happy with the new one. And as they don't take up much space they can also simply be left in place.

[kjpetrie]

Kernels, with their associated modules, take up about 200MB or so. Whether that's a lot of space depends on whether you're remastering or not. However, it's best to keep them if you can.

[YouCanToo]

Hi friends,

I have got a new toy, an old Lenovo T61 Thinkpad (4Gb Ram - 2,2 Ghz - Nvidia Card)


Which kernel should I install, the 2.6.38.0-pclos.3.pae? How install it, from the repos?

Thanks

Since the .pae kernel(s) (IE: .pae - .pae.bfs) are the only ones that will let the end user access 4gig or more of memory in a 32 bit environment, do you really have some other choice???  Also as has been said on the forum many many times over, It is suggested that the user ONLY installs software from the REPOS! (this also goes for the kernel(s))  A search of the forum for both of your questions would have resulted in the answers you seek.

[Aleph]

Hi friends,

I did, now I have the new kernel pae.bfs in my laptop, I have 4Gb of ram and everything is working!

The new PCLOS 2012 is fantastic, very very fast, even Net applet, that was very slow in my others laptops... (I don't know why)

I like PCLOS!!!

Thanks!

[Aleph]

 

Something wrong is happening... now the boot is very very slow, in booth kernels. About 2 min... Why?

Edit:
I did a verbose boot. Stop thinking for a while with

"cannot open file delete"

and after "cannot find .....something...."

[AS]

Something wrong is happening... now the boot is very very slow, in booth kernels. About 2 min... Why?

Edit:
I did a verbose boot. Stop thinking for a while with

"cannot open file delete"

and after "cannot find .....something...."

Do not worry about the "cannot open file delete" message, it is a glitch in plymouth theme but doesn't cause any issue nor any delay.

The "cannot find ... something" suggest it could be because you changed some partitions ... may be ... not enough  info ...
If this is the case, you need to rebuild the initrd image ...

[Aleph]

The message is:

"cannot find divice UUID..."

I did a install of Spotify, doesn't work, crashes...

And... a installed Crunchbang(my main distro is PCLOS but I like more than one OS), the partition where I installed CB where made before.

Could be this the problem?

How to solve?

[JohnW_57]

The message is:

"cannot find divice UUID..."

I did a install of Spotify, doesn't work, crashes...

And... a installed Crunchbang(my main distro is PCLOS but I like more than one OS), the partition where I installed CB where made before.

Could be this the problem?

How to solve?

Crunchbang using Grub2 as default boot-loader, maybe this could causing the issue??

JohnW

[Aleph]

Crunchbang using Grub2 as default boot-loader, maybe this could causing the issue??

Maybe, but I am using the Grub Legacy of PCLOS, no Grub2.

[kjpetrie]

Installing the other distros probably reformatted your swap partition, changing its UUID. This means your system cannot find it and it hangs for a minute waiting for it.

The cure is:

1. use blkid to find the UUID for the swap partition. Copy it to your clipboard.
2. As root, edit your /boot/grub/menu.lst, and paste in the correct value for the UUID for the resume partition. Save menu.lst and then do the same for your /etc/fstab file. Exit the editor.
3. Open a terminal, su to root, and issue mkinitrd /boot/initrd-`uname -r`.img `uname -r` (those are backticks, not quotes - best to use copy and paste to make sure you get it right).

This should change the stored UUID to the current one.

[AS]

Installing the other distros probably reformatted your swap partition, changing its UUID. This means your system cannot find it and it hangs for a minute waiting for it.

The cure is:

1. use blkid to find the UUID for the swap partition. Copy it to your clipboard.
2. As root, edit your /boot/grub/menu.lst, and paste in the correct value for the UUID for the resume partition. Save menu.lst and then do the same for your /etc/fstab file. Exit the editor.
3. Open a terminal, su to root, and issue mkinitrd /boot/initrd-`uname -r`.img `uname -r` (those are backticks, not quotes - best to use copy and paste to make sure you get it right).

This should change the stored UUID to the current one.

+1,
you need option -f too when initrd image already exists

mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`

[Aleph]

Thanks kjpetrie, thanks As!!!

Now PCLOS booted in 39 sec only!

Could be affected this problem to others things? I hope not...