Updating to the 2012-09-18-wheezy-raspbian image

[RaTTuS]

The CPU reports 700000 (700MHz) most the time, but it did report 1000000 (1GHz) one of the times, so I guess it is working. What is the logic on the speed, is it demand and the temperature? If so what is the temperature limit (I got just under 50degC on one of the 1GHz points)?

it will change on usage - so as your using it it will zip up to the higher values not just in the boot.
I found that I had to update raspi-config and the options showed up

[dom]

The CPU reports 700000 (700MHz) most the time, but it did report 1000000 (1GHz) one of the times, so I guess it is working. What is the logic on the speed, is it demand and the temperature? If so what is the temperature limit (I got just under 50degC on one of the 1GHz points)?

It goes up when busy. If CPU is hits 85% it goes up. When it idle for a while it drops down. Temperature limit is 85'C (which you'll not not see except in the hottest climates).

[Aydan]

What are the lowest possible minimum frequencies for under clocking?

[dom]

What are the lowest possible minimum frequencies for under clocking?

You can set arm_freq_min=100 for a low idle frequency. It is usable, but takes a little longer for turbo to kick in.

[Coxeroni]

But with xbian you can also update the firmware with the commands above, or am I wrong?

If XBian is derived from the Raspbian images on our download page then yes, that should be possible. You'd be best off asking the Xbian creator for support on this though.

It is, that I am certain. Will test it at home. Awesome work guys!

[simplesi]

I'm out of room to do the upgrade
What can I clean out of where to make some space please?

SImon

[penguintutor]

Quick heads up - in case someone else gets this same error

It appears that apt-get upgrade needs a reasonable amount of memory to work with. It depends what you Raspberry Pi is doing (mine is running as a squid proxy server), but you may need to free up some memory when running the upgrade. You only need to follow this if you get the "Failed to fork" error during the upgrade.

The error I got during the upgrade was:

315 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
FATAL -> Failed to fork.

whilst this may sound like it's done the upgrade before the failure it hasn't in fact started downloading / installing packages.

Failed to fork may sound like a problem with trying to pick up peas at dinner time - but in simple terms it means it couldn't start the new process to perform the update - most likely a memory problem.

Quick check shows that I had 10MB free memory, although significant amount of swap in use.

Code: Select all

free                                                                          
             total       used       free     shared    buffers     cached
Mem:        188104     177744      10360          0       5288      13632
-/+ buffers/cache:     158824      29280
Swap:       102396     102204        192

In my case a quick reboot helped clear the memory. If you don't want to completely reboot you could look at stopping some services or shutting down certain applications to see if that helps.

After reboot I had more available memory and swap usage was back to 0.

Code: Select all

free 
             total       used       free     shared    buffers     cached
Mem:        188104     162808      25296          0      13532      73380
-/+ buffers/cache:      75896     112208
Swap:       102396          0     102396

and repeating the sudo apt-get upgrade is now progressing nicely.

Good that the plan for the Model A has the same memory as the Model B, otherwise I could see problems like this happening a bit more in future.

[meltwater]

This is so impressive, even Scribus works well enough to use now <---- That alone makes it a massive thanks from the MagPi team!

[dom]

I'm out of room to do the upgrade
What can I clean out of where to make some space please?

Code: Select all

sudo apt-get clean

might free some space. Otherwise apt-get remove some packages.

[asb]

I'm out of room to do the upgrade
What can I clean out of where to make some space please?

SImon

apt-get clean will delete downloaded .deb packages, which may help. Also try "sudo apt-get update && sudo apt-get install raspberrypi* raspi-config" to update just the necessary packages for overclocking.

[hojnikb]

What are the lowest possible minimum frequencies for under clocking?

You can set arm_freq_min=100 for a low idle frequency. It is usable, but takes a little longer for turbo to kick in.

With such underclock it would make sense to undervolt aswell

[simplesi]

apt-get clean will delete downloaded .deb packages, which may help. Also try "sudo apt-get update && sudo apt-get install raspberrypi* raspi-config"

Still got no space errors I'm at 95% use on rootfs using df after an apt-clean

Are there any log files temp files somewhere I can get rid of?

Simon

[simplesi]

Otherwise apt-get remove some packages.

Got any good (large sized) candidates ?
Simon

[simplesi]

Found a few large downloads - got free space down to 91% and it seems to have worked - ta

Simon

[zigzag]

after

Code: Select all

sudo apt-get update && sudo apt-get upgrade
sudo apt-get update && sudo apt-get install raspberrypi* raspi-config

pi after reboot cannot mount root filesystem a repeatedly restarting

[Frank B]

Hi,

i'm having SD-Card problems again. The both previous raspbian-images worked perfect, with this image i get sd-card errors:

Code: Select all

[  198.620419] mmc0: final write to SD card still running
[  208.648726] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  208.649888] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
[  219.733927] mmc0: final write to SD card still running
[  229.748701] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  229.749870] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
[  235.849829] mmc0: final write to SD card still running
[  245.868729] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  245.869895] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
[  247.573302] mmc0: final write to SD card still running
[  257.588712] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  257.589920] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
[  266.429275] mmc0: final write to SD card still running
[  276.448702] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  276.449877] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
[  287.235896] mmc0: final write to SD card still running
[  297.248701] mmc0: Timeout waiting for hardware interrupt - cmd12.
[  297.249875] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900

Tested with Sandisk Ultra 2GB II & Sandisk Class 4 4GB, Samsung Class 6 8 GB

Frank

[dom]

i'm having SD-Card problems again. The both previous raspbian-images worked perfect, with this image i get sd-card errors:
Tested with Sandisk Ultra 2GB II & Sandisk Class 4 4GB, Samsung Class 6 8 GB

Can you confirm, that have downloaded the "2012-09-18-wheezy-raspbian" and imaged it to the sdcards? (rather than udpating your current one).
That is surprising, especially with Sandisk Ultra cards (which I use mysefl).

Do you have a different sdcard reader or a different machine you can write the image from?

[Frank B]

Hi Dom,

Can you confirm, that have downloaded the "2012-09-18-wheezy-raspbian" and imaged it to the sdcards? (rather than udpating your current one).
That is surprising, especially with Sandisk Ultra cards (which I use mysefl).

Do you have a different sdcard reader or a different machine you can write the image from?

Yes i've downloaded the 2012-09-18-wheezy-raspbian image.
i can try another sdcard reader, no problem. i also have a sandisk ultra 8GB which i can test (it's in my cam, at the moment).

I'll post my results in 30-40 minutes.
frank.

[pmj1979]

My Pi has been stuck on this line for about the last 20+ mins.

After "sudo apt-get update && sudo apt-get upgrade"

...
Unpacking replacement raspberrypi-bootloader ...
Processing triggers for man-db ...
Setting up manpages (3.42-1) ...
Setting up raspberrypi-bootloader (1.20120918-1) ...
Your current start.elf is the same as arm192_start.elf
Removing 'diversion of /boot/arm128_start.elf to /usr/share/rpikernelhack/arm128_start.elf by rpikernelhack'

Do I leave it? Is it ok? Has it crashed?
ACT light is solid (as are the others but occasional LNK light flashes.
I have HDMI plugged in but the display has gona blank, I entered the sudo apt-get through putty.

[Dweeber]

If your WiFi driver is supported by the default linux tree, or is based on the popular RTL8188CUS chipset, then WiFi should work out of the box. Boot the image with the WiFi dongle plugged in (a powered hub is recommended). Run startx and select “WiFi Config”. You can scan for wireless networks and enter your wireless password and connect from the GUI. No need to install additional packages or scripts.

Is there a non-GUI version of the WiFi Config?

I use my RPi's primarily via SSH (HDMI, WiFi, NO Ethernet, Keyboard if necessary, No mouse) I almost never use startx. My experimental RPi with a breadboard etc... doesn't have a keyboard or monitor at all.

If WiFi is not working, I have to sit in a hard to work area with a keyboard in one hand typing using the other. I could VNC in, but if the network isn't setup, that is not possible.

[asb]

Is there a non-GUI version of the WiFi Config?

I use my RPi's primarily via SSH (HDMI, WiFi, NO Ethernet, Keyboard if necessary, No mouse) I almost never use startx. My experimental RPi with a breadboard etc... doesn't have a keyboard or monitor at all.

If WiFi is not working, I have to sit in a hard to work area with a keyboard in one hand typing using the other. I could VNC in, but if the network isn't setup, that is not possible.

Once you've done the wifi setup once, it's saved and will come back on reboot. WiFi Config is just a shortcut to wpagui (not the most friendly UI for wireless configuration, but we had problems with resource consumption with network-manager and wicd). wpa_cli would be an obvious alternative for you.

[Frank B]

Hi Dom,

Can you confirm, that have downloaded the "2012-09-18-wheezy-raspbian" and imaged it to the sdcards? (rather than udpating your current one).
That is surprising, especially with Sandisk Ultra cards (which I use mysefl).

Do you have a different sdcard reader or a different machine you can write the image from?

Yes i've downloaded the 2012-09-18-wheezy-raspbian image.
i can try another sdcard reader, no problem. i also have a sandisk ultra 8GB which i can test (it's in my cam, at the moment).

I'll post my results in 30-40 minutes.
frank.

Hi Dom,
i identified my sdcard problem. tested with the 8gb card and had the same problem (as with all 3 other cards)
The Image is ok, the overclocking "high" was the problem.
I always had my raspi at 950 mhz,but core-freq at 325mhz. I did'nt remember that, so i set speed to "high" in raspi-config every time, which obviously was a fault.

Frank.

[Aydan]

Could you please enable CONFIG_CPU_FREQ_STAT_DETAILS for the next kernel version so it's possible to check how long the CPU spent in each frequency?
I did load the cpufreq-stats module but that didn't expose /sys/devices/system/cpu/cpu0/cpufreq/stats

Thanks
Aydan

[williamhbell]

Hi,

During the update, the Pi was turned off so that the update many not have completed correctly. How can the update be re-run? Is it enough to force the script in the deb file to re-run?

On the second Pi the update script is still running after 2hrs.

Thanks and best regards,

Will

[asb]

I've edited the post to make it clear that just to get newer firmware and overclocking, I recommend sudo apt-get update && sudo apt-get install raspberrypi* raspi-config