Intermittent slow performance in lxde

[windy54]

Hi,
I have been using a model A to control a robot for the last 12 months with no problems. When developing software I plug a powered USB hub into the PI and then keyboard, mouse and wifi dongle into the hub. I have never noticed slow performance in the past.

This week I removed the Pj from the robot and added a PI camera. When I booted the PI performance was ridiculously slow, I.e. Click on a lxde terminal and two minutes later it opens, press a key and 30 seconds late it appears in window. Usage monitor is running at 100%.

All my peripherals, hub, keyboard, mouse dongle and psu are from Maplins and supposed to be compatible, the fact I have had no problem in the past makes me believe they are not the problem.

When I installed the camera I ran sudo apt-get update , upgrade etc to update software and firmware, I have also done t his on my model B and have not got the same problem. I have removed the camera and still have the problem.

Any ideas what to try.
I have fitted the model a sd card in the model b and do not have the problem.
Are there any log files I can look at after the event?
I was thinking of trying a new sd card in the model A.

Cheers

[windy54]

Sorted after using dmesg to look at errors, and searching on google a task was hanging for four minutes.
The task implied a memory allocation problem.
Using raspi-config the memory allocation was 128 to the gpu, reducing this to 64 solved the problem.

When the camera is enabled raspi-config allocates 128 to the gpu, which makes sense, apart from the fact that my model A only has 256.

So, I will revert my model A back to a simple robot controlled via Bluetooth and my Nintendo wii controller and go get myself a new model B for the next generation of my robot.

[jamesh]

Sorted after using dmesg to look at errors, and searching on google a task was hanging for four minutes.
The task implied a memory allocation problem.
Using raspi-config the memory allocation was 128 to the gpu, reducing this to 64 solved the problem.

When the camera is enabled raspi-config allocates 128 to the gpu, which makes sense, apart from the fact that my model A only has 256.

So, I will revert my model A back to a simple robot controlled via Bluetooth and my Nintendo wii controller and go get myself a new model B for the next generation of my robot.

Depending on what you do with the camera you could get away with a 64MB memory split - try it and see! I did a lot of camera dev work on a 256MB Model B.