fwroller
Posts: 11
Joined: Sun Mar 06, 2016 11:58 am

Re: New Jessie Image (2017-01-11) Difference ??

Sat Jan 14, 2017 2:41 pm

Still no addition to the release notes?

User avatar
HawaiianPi
Posts: 4531
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: New Jessie Image (2017-01-11) Difference ??

Sun Jan 15, 2017 10:52 am

Wait, seriously? A new image was released just for a FAT32 boot partition?

That can't be true because it's completely pointless and utterly ridiculous.

So what's the real story here?
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

User avatar
rpdom
Posts: 14985
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: New Jessie Image (2017-01-11) Difference ??

Sun Jan 15, 2017 11:53 am

HawaiianPi wrote:Wait, seriously? A new image was released just for a FAT32 boot partition?

That can't be true because it's completely pointless and utterly ridiculous.

So what's the real story here?
:roll:
Why don't you compare the contents of the images and tell us?

mikerr
Posts: 2774
Joined: Thu Jan 12, 2012 12:46 pm
Location: UK
Contact: Website

Re: New Jessie Image (2017-01-11) Difference ??

Tue Jan 17, 2017 2:52 pm

FYI here's a little more info on why the change, related to the CM3 it seems:
Gordon Hollingworth says:
The only note a relevance is that we changed the FAT partition to be FAT32, this is because there is a problem when booting from an eMMC device with a FAT16 partition.
https://www.raspberrypi.org/blog/comput ... nt-1268493
Android app - Raspi Card Imager - download and image SD cards - No PC required !

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 12120
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: New Jessie Image (2017-01-11) Difference ??

Tue Jan 17, 2017 3:18 pm

So it seems the only change that was made was not to any code, so that explains that there was no release document generated, the change is just that now for the FAT partition of \boot a FAT32 directory structure was chosen instead of a FAT16 structure, because the CM3 doesn't boot properly from a FAT16 formatted directory. Again, no software has changed!
also, all systems installed using NOOBS normally format the boot partition to FAT32, not FAT16.

beta-tester
Posts: 1236
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: New Jessie Image (2017-01-11) Difference ??

Tue Jan 17, 2017 9:39 pm

mahjongg wrote:So it seems the only change that was made was not to any code, so that explains that there was no release document generated, the change is just that now for the FAT partition of \boot a FAT32 directory structure was chosen instead of a FAT16 structure... Again, no software has changed!
but even this is a change that should be list in the release notes... otherwise it will always come to wild speculations over again, each time a new release date is shown with no proper updated release note.
{ I only give negative feedback }
RPi Model B (rev1, 256MB) & B (rev2, 512MB) & B+, RPi2B, RPi3B, RPi3B+, RPiZeroW, ...

User avatar
HawaiianPi
Posts: 4531
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: New Jessie Image (2017-01-11) Difference ??

Tue Jan 17, 2017 11:03 pm

If a new image was needed for the FAT32 partition, they should have included the fixes for the SSH script. That fix was tested.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 12120
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: New Jessie Image (2017-01-11) Difference ??

Thu Jan 19, 2017 12:06 am

beta-tester wrote:
mahjongg wrote:So it seems the only change that was made was not to any code, so that explains that there was no release document generated, the change is just that now for the FAT partition of \boot a FAT32 directory structure was chosen instead of a FAT16 structure... Again, no software has changed!
but even this is a change that should be list in the release notes... otherwise it will always come to wild speculations over again, each time a new release date is shown with no proper updated release note.
True, I suspect this is an automated process that runs each time code has changed.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5862
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: New Jessie Image (2017-01-11) Difference ??

Thu Jan 19, 2017 6:40 pm

mahjongg wrote:True, I suspect this is an automated process that runs each time code has changed.
The release notes come as a part of the Raspbian for NOOBS files rather than the .img. The system is a little fragile, so I am not going to mess with it until the next real image.

ktb
Posts: 1380
Joined: Fri Dec 26, 2014 7:53 pm

Re: New Jessie Image (2017-01-11) Difference ??

Fri Jan 20, 2017 4:00 am

This change prevents me from being able to "Check" the boot partition in GParted on a x86_64 Ubuntu 17.04 box. I believe it's due to some FAT32 libparted bug. Not a big deal.

jahboater
Posts: 4598
Joined: Wed Feb 04, 2015 6:38 pm

Re: New Jessie Image (2017-01-11) Difference ??

Fri Jan 20, 2017 9:39 am

ktb wrote:This change prevents me from being able to "Check" the boot partition in GParted on a x86_64 Ubuntu 17.04 box. I believe it's due to some FAT32 libparted bug. Not a big deal.
gparted didn't work for me with the old FAT16 boot partition either (unexpected cluster size, then fails).

fsck works fine for both old FAT16 and new FAT32, and its quicker to use, so that's OK.
Not that I ever need to check a freshly written image.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5862
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: New Jessie Image (2017-01-11) Difference ??

Fri Jan 20, 2017 11:17 am

I've seen that too and will look into it. Since the partition is created on a file rather than a real sf card, I suspect that leads to problems like that.

Return to “Raspbian”