New stable firmware update

[asb]

Hi all. I updated the stable apt source with repackaged firmware which provides support for arbitrary memory splits on the new 512M boards. Sorry for the delay there. You should be able to upgrade with:

Code: Select all

sudo apt-get update && sudo apt-get install raspi-config libraspberrypi*

We no longer need a whole bunch of start.elf files, and instead the amount of GPU memory can be specified in /boot/config.txt. I have updated raspi-config to support this, which you may find more convenient. Unlike previous (and future) updates, this one will require you to re-set your preferred memory split if it was something other than the default.

Upon upgrade, it will default to 64MiB GPU and the rest to ARM. If you wish to change that, just run `sudo raspi-config` and make the appropriate change.

Any issues, let me know. There's also a 2012-10-28-wheezy-raspbian.zip up on the downloads page now.

[RaTTuS]

+1 updating one image now....
great work

[shuckle]

Seems to work.

Are these the correct new versions:
$ uname -a
Linux raspberrypi3 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux

$ sudo vcgencmd version
Oct 25 2012 16:37:21
Copyright (c) 2012 Broadcom
version 346337 (release)

[SirLagz]

Awesome. Great time for me to be getting back into the Pi then

[asb]

Seems to work.

Are these the correct new versions:
$ uname -a
Linux raspberrypi3 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux

$ sudo vcgencmd version
Oct 25 2012 16:37:21
Copyright (c) 2012 Broadcom
version 346337 (release)

Yes, the firmware is the version as of https://github.com/raspberrypi/firmware ... 8c75308773 as the changes introduced in https://github.com/raspberrypi/firmware ... a6098c46d5 have not been widely tested enough yet.

[Boezelman]

Nice work!

I keep my Pi up-to-date, so nothing new for me

Code: Select all

0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

[ski522]

Nice work!

I keep my Pi up-to-date, so nothing new for me

Code: Select all

0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

Yeah, but you have 3 not upgraded !

[RadioactiveMouse]

I ran the update fine although now I'm having problems booting.
I reconfigured the RAM split and now booting fails.

I have had a look at the config file on the SD card and the top half looks like total junk followed by human readable settings below it.

I'd rather not have to recompile Go, Riak and Redis so if anyone has any ideas that would be very helpful

[RadioactiveMouse]

I ran the update fine although now I'm having problems booting.
I reconfigured the RAM split and now booting fails.

I have had a look at the config file on the SD card and the top half looks like total junk followed by human readable settings below it.

I'd rather not have to recompile Go, Riak and Redis so if anyone has any ideas that would be very helpful

Tried removing the overclocking information from the config.txt, also with and without the gunk above it in the config text file I mentioned earlier.

I should also say that I've tried the kernel recovery image and also used a standard bootcode.bin from the wiki to no avail :/

I've tried my other SD card and it seems to work fine so it's not the polyfuse either.

Pretty much sure it's totally hosed now.... Anyone?

[laurent]

I ran the update fine although now I'm having problems booting.
I reconfigured the RAM split and now booting fails.

I have had a look at the config file on the SD card and the top half looks like total junk followed by human readable settings below it.

I'd rather not have to recompile Go, Riak and Redis so if anyone has any ideas that would be very helpful

Your file seems to be corrupted.
How did you reboot after you had modified the configuration file ?
A "sync" command before any reset/power off makes sure any modification on file system is done.

[RadioactiveMouse]

I ran the update fine although now I'm having problems booting.
I reconfigured the RAM split and now booting fails.

I have had a look at the config file on the SD card and the top half looks like total junk followed by human readable settings below it.

I'd rather not have to recompile Go, Riak and Redis so if anyone has any ideas that would be very helpful

Your file seems to be corrupted.
How did you reboot after you had modified the configuration file ?
A "sync" command before any reset/power off makes sure any modification on file system is done.

I called "sudo reboot" after exiting raspi-config

[asb]

You do seem to be running in to corruption on your FAT partition. A while back there were some issues with occasional FS corruption on the FAT partition. How long has this image been in use - is it one you've updated multiple times? It may well be there was some existing corruption which caused the file updates to cause havoc.

[RadioactiveMouse]

You do seem to be running in to corruption on your FAT partition. A while back there were some issues with occasional FS corruption on the FAT partition. How long has this image been in use - is it one you've updated multiple times? It may well be there was some existing corruption which caused the file updates to cause havoc.

I'd imagine it's been around a little over a month as I have had to recompile Go and Riak since then. I have run updates when I've remembered but this is the first that has caused any issues. I suppose there is no way to recover such a corruption?

[asb]

I'd recreate the FAT partition. Do you have a Linux machine? If so I'd first make sure the FAT partition is unmounted, then:

Code: Select all

sudo mkdosfs -S 512 -s 16 -v /dev/SD_CARD_PART1 # e.g. /dev/sdb1 for me

Then you can mount that partition and copy fresh files in to it (for convenience, you can untar the contents of http://asbradbury.org/tmp/raspi/2012_10_30_boot.tar.gz).

[magic_man185]

So is there any difference between running the commands given by asb, and running rpi-update? This method seems to be easier for someone who doesn't have rpi-update already installed. I think it is, from what I know I think rpi-update lets you update your firmware before it is stable, right? So since this was updated to stable there is no need to do rpi-update?

Thanks.

[asb]

So is there any difference between running the commands given by asb, and running rpi-update? This method seems to be easier for someone who doesn't have rpi-update already installed. I think it is, from what I know I think rpi-update lets you update your firmware before it is stable, right? So since this was updated to stable there is no need to do rpi-update?

Thanks.

Running rpi-update will give you a slightly newer and less tested version of the firmware. Use whichever method you're comfortable with, but be prepared you may sometimes experience breakage when running off the latest bleeding edge firmware.

[magic_man185]

Running rpi-update will give you a slightly newer and less tested version of the firmware. Use whichever method you're comfortable with, but be prepared you may sometimes experience breakage when running off the latest bleeding edge firmware.

Thank you. What would be the equivalent to installing the new image provided by the foundation? I don't need bleeding edge, I essentially want to be right where I would be with the new image, without having to reinstall everything.

Thanks again.

[asb]

Thank you. What would be the equivalent to installing the new image provided by the foundation? I don't need bleeding edge, I essentially want to be right where I would be with the new image, without having to reinstall everything.

Thanks again.

Following the instructions in the first post in the thread will leave you with something roughly equivalent to my regenerated 2012-10-28-wheezy-raspbian.zip

[sjfaustino]

Hi all. I updated the stable apt source with repackaged firmware which provides support for arbitrary memory splits on the new 512M boards. Sorry for the delay there. You should be able to upgrade with:

Code: Select all

sudo apt-get update && sudo apt-get install raspi-config libraspberrypi*

I just tried it and got:

Code: Select all

pi@raspberrypi ~ $ sudo apt-get update && sudo apt-get install raspi-config libraspberrypi*
Hit http://archive.raspberrypi.org wheezy InRelease
Hit http://mirrordirector.raspbian.org wheezy InRelease
Hit http://archive.raspberrypi.org wheezy/main armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-en_GB
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Get:1 http://mirrordirector.raspbian.org wheezy/main armhf Packages [9,463 kB]
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en
Fetched 1 B in 1min 15s (0 B/s)                                                                                                                              
W: Failed to fetch gzip:/var/lib/apt/lists/partial/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old ones used instead.

Any idea why?

[asb]

I'm going to blame it on a transient issue with one of the mirrors in the Raspbian mirror system.

[RadioactiveMouse]

I'd recreate the FAT partition. Do you have a Linux machine? If so I'd first make sure the FAT partition is unmounted, then:

Code: Select all

sudo mkdosfs -S 512 -s 16 -v /dev/SD_CARD_PART1 # e.g. /dev/sdb1 for me

Then you can mount that partition and copy fresh files in to it (for convenience, you can untar the contents of http://asbradbury.org/tmp/raspi/2012_10_30_boot.tar.gz).

Thanks.

I managed to get it sorted eventually by replacing all the data I could see when looking at the SD card(obviously backing up as well). I unzipped your data and realised I could just replace it like for like.

After I did that it was fine.

Thanks again

[k6rtm]

trying to update with
sudo apt-get update

gives me (after a while)

Reading package lists... Error!
E: Problem parsing dependency Depends
E: Error occurred while processing freediams (NewVersion2)
E: Problem with MergeList /var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages
E: The package lists or status file could not be parsed or opened.

I'm running

Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l

Any ideas, or just try again later?

cheers--
bob K6RTM

[birdman]

I too ended up with a system that would not reboot after doing:

aptitude update
aptitude safe-upgrade
aptitude clean

I switched back to the previous /boot files, which worked.
No idea I might have to update config.txt (as the update made no mention of it, and the file hadn't been changed).
I did report it as a bug on the Raspbian site.

[shuckle]

I got also problems while upgrading my second RPi (also 256 version):
1) the sudo apt-get upgrade hang with:
Setting up raspberrypi-bootloader (1.20121025-1) ...
Memory split is now set in /boot/config.txt.
You may want to use raspi-config to set it
Removing 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'
Removing 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'
Removing 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'
Removing 'diversion of /boot/kernel.img to /usr/share/rpikernelhack/kernel.img by rpikernelhack'
Removing 'diversion of /boot/kernel_cutdown.img to /usr/share/rpikernelhack/kernel_cutdown.img by rpikernelhack'
Removing 'diversion of /boot/kernel_emergency.img to /usr/share/rpikernelhack/kernel_emergency.img by rpikernelhack'
Removing 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack

After that I waited half an hour without progress and tried also to ssh into it, but no answer. Then I rebooted and it became up fine.

2) Now it says:
$ LANG=C sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
libmikmod2 lxsession openssh-client openssh-server
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

What does that mean? Kept back??

3) in the dmesg there are now strange /(but harmless) messages:
[ 25.046698] bcm2835 ALSA card created!
[ 25.059906] bcm2835 ALSA chip created!
[ 25.065977] bcm2835 ALSA chip created!
[ 25.084021] bcm2835 ALSA chip created!
[ 25.096201] bcm2835 ALSA chip created!
[ 25.108086] bcm2835 ALSA chip created!
[ 25.113755] bcm2835 ALSA chip created!
[ 25.132759] bcm2835 ALSA chip created!
[ 29.140870] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[ 29.151746] mmc0: DMA IRQ 6 ignored - results were reset
[ 29.159940] mmc0: missed completion of cmd 18 DMA (512/512 [1]/[1]) - ignoring it
[ 29.170922] mmc0: DMA IRQ 6 ignored - results were reset
[ 33.018981] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 33.157260] bcm2835-cpufreq: switching to governor ondemand


4) after sudo reboot, it does not wake boot anymore.

[shuckle]

I recovered the system by copying files:
kernel_cutdown.img
kernel_emergency.img
kernel.img
bootcode.bin

from a workgin system. All of those files were missing. Not sure if they all are needed, but now the system works again.