gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 9:27 pm

I downgraded back to the 10 Nov build (8fd111f77895450323abc5b34efde19548ffc480) and the FSTRIM command functions ok. Upon re-upgrading to the latest rpi-update FSTRIM again fails with the ioctl error.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 9:35 pm

gstreeter wrote:I downgraded back to the 10 Nov build (8fd111f77895450323abc5b34efde19548ffc480) and the FSTRIM command functions ok. Upon re-upgrading to the latest rpi-update FSTRIM again fails with the ioctl error.
Can you confirm if it is the gpu firmware or kernel?
i.e. does a latest rpi-update, with start*.elf and fixup*.dat reverted to 10 Nov version work?

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 9:47 pm

Looks like it's the firmware. I ran rpi-update with SKIP_KERNEL=1 on the 10 Nov build. The #587 kernel was retained and the firmware updated. I now get the FSTRIM ioctl failure again with the updated firmware.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:01 pm

gstreeter wrote:Looks like it's the firmware. I ran rpi-update with SKIP_KERNEL=1 on the 10 Nov build. The #587 kernel was retained and the firmware updated. I now get the FSTRIM ioctl failure again with the updated firmware.
It's hard to image what is causing it, but we can narrow it down some more. Go back to latest firmware, and added config.txt option:
emmc_pll_core=0

That should behave pretty much like the previous firmware.

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:03 pm

A full rpi-update followed by restoring the 10 Nov firmware gives a functioning FSTRIM with the newer #590 kernel.

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:16 pm

Latest rpi-update with emmc_pll_core=0 allows FSTRIM to work.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:20 pm

gstreeter wrote:Latest rpi-update with emmc_pll_core=0 allows FSTRIM to work.
How about:
emmc_pll_core=1
init_emmc_clock=100000000

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:26 pm

emmc_pll_core=1
init_emmc_clock=100000000

Results in a working FSTRIM

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:41 pm

gstreeter wrote:emmc_pll_core=1
init_emmc_clock=100000000

Results in a working FSTRIM
Okay, seems to be the higher emmc clock. I imagine if you do:
emmc_pll_core=0
init_emmc_clock=250000000

on either new or old firmware you will get the same effect (fstrim stops working).

I'm guessing it's reading some of teh sdcard config registers wrong. E.g.

Code: Select all

 cat /sys/devices/platform/mmc_host/mmc0/mmc0*/*
may be different in the two cases.

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:47 pm

I've just noticed a reply from ghollingworth on GitHub to the issue I raised about this:

"FSTRIM is not supported by SD cards therefore it failing is a good thing...
Previous updates were clearly incorrect and someone has fixed it more like"

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 10:54 pm

gstreeter wrote:I've just noticed a reply from ghollingworth on GitHub to the issue I raised about this:

"FSTRIM is not supported by SD cards therefore it failing is a good thing...
Previous updates were clearly incorrect and someone has fixed it more like"
Yes. Whether fstrim does anything useful on an sdcard is a different question.
There are a few thread on this forum about it, and results are inclusive.
Also it appears the ability to run fstrim comes and goes. See:
http://www.raspberrypi.org/phpBB3/viewt ... 63&t=19554

But that's not what I'm interested in. The fstrim behaviour changed for a surprising reason.
Being surprised normally means something funny is going on, and I'd like to understand what is happening.

gstreeter
Posts: 106
Joined: Sun Sep 02, 2012 11:11 am
Location: UK

Re: Next firmware tree is now 3.10

Tue Nov 12, 2013 11:05 pm

I check the cat on the mmc device for the cases when FSTRIM works and fails. The results are identical.

User avatar
g7ruh
Posts: 67
Joined: Mon Apr 23, 2012 9:49 am
Location: Blackfield UK

Re: Next firmware tree is now 3.10

Fri Nov 15, 2013 4:41 pm

Dom,

SPI is working in 3.10 now, thanks to you and popcornmix for your help and to chrisy for the issue on github

Roger

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Fri Nov 15, 2013 5:44 pm

g7ruh wrote: SPI is working in 3.10 now, thanks to you and popcornmix for your help and to chrisy for the issue on github
Glad it's working (and popcornmix is glad too :-))

User avatar
DougieLawson
Posts: 36312
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Next firmware tree is now 3.10

Fri Nov 15, 2013 9:21 pm

dom wrote:
g7ruh wrote: SPI is working in 3.10 now, thanks to you and popcornmix for your help and to chrisy for the issue on github
Glad it's working (and popcornmix is glad too :-))
Thank you.

I've had lots of fun this week trying each of your new firmware/kernel/module builds.
/dev/spidev0.0 and /dev/spidev0.1 have magically re-appeared with 3.10.18+ #596.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

Nige C
Posts: 46
Joined: Thu Jul 19, 2012 12:22 am
Location: Hadleigh, Suffolk

Re: Next firmware tree is now 3.10

Sun Nov 17, 2013 2:49 am

Thank you, my PiFace is working again. Thanks Dom and Popcornmix and others. SPI working now under 3.10. Great work thanks again.
Retired power engineer with a lot of real life experience. Life is an adventure again :)

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Next firmware tree is now 3.10

Mon Nov 18, 2013 7:40 am

B.Jay wrote:Okay... seems there's still a problem with SD card corruption and Overclocking going on (latest update installed) ...

config.txt snippet:

Code: Select all

force_turbo=1
init_emmc_clock=500000000
emmc_pll_core=1
core_freq=500
arm_freq_min=700
arm_freq=1000
sdram_freq_min=400
sdram_freq=500
over_voltage=6
With these settings now my rasp passed a full stress test of 2 hours 100% cpu.
So from my point of view the sd corruption gone away :D :D :D

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Mon Nov 18, 2013 12:01 pm

mcgyver83 wrote: With these settings now my rasp passed a full stress test of 2 hours 100% cpu.
So from my point of view the sd corruption gone away :D :D :D
Good to hear it has worked.

With latest firmware, you don't have to specify emmc_pll_core=1 or init_emmc_clock (they will be set as a default).
force_turbo is optional - should be no problems with or without it.

fabriced
Posts: 10
Joined: Thu Jun 06, 2013 7:56 pm

Re: Next firmware tree is now 3.10

Mon Nov 18, 2013 12:59 pm

Hi,
Master branch is on 3.10.19 and the next branch is on 3.10.18.
Now they are both on 3.10.y, it is unclear for me what is on each branch and we do not have the sources.
When I read the commits, I do not really understand what is or isn't in each.
Could it be possible to give a summary of the differences?
Or at least a summary for USB and SD fixes since these are the most tricky part of the Pi ?
Best regards,
Fabrice

B.Jay
Posts: 28
Joined: Thu Jul 18, 2013 10:57 pm

Re: Next firmware tree is now 3.10

Mon Nov 18, 2013 1:01 pm

mcgyver83 wrote:
B.Jay wrote:Okay... seems there's still a problem with SD card corruption and Overclocking going on (latest update installed) ...

config.txt snippet:

Code: Select all

force_turbo=1
init_emmc_clock=500000000
emmc_pll_core=1
core_freq=500
arm_freq_min=700
arm_freq=1000
sdram_freq_min=400
sdram_freq=500
over_voltage=6
With these settings now my rasp passed a full stress test of 2 hours 100% cpu.
So from my point of view the sd corruption gone away :D :D :D
Well, just for the LULZ I took a 256MB MMC (yes, a MMC card - good enough to "Kickstart" the Pi from it and make it continue booting from USB) I found in some old phone while clearing out my severely overflowing electronics junk carton box and put the firmware/kernel onto the card. To my surprise the Pi boots off of it without any problem and when mounting/un-mounting/mounting the vfat partition in the fully booted system I don't see the "was not cleanly unmounted" message popping up in the syslogs anymore (though it still happens with the Sony 2GB mSD-in-SD Adapter card where even Windows keeps on insisting that 'No errors found' upon a full chkdsk run - and yes, I peeked at the card with a HexEditor and the dirty-bit is fine).

Anyway, the MMC works perfect with the overclocked Pi, though I'm still resorting to my "rpi-update wrapper" that only mounts the card to copy files in case the firmware has been updated.
dom wrote:With latest firmware, you don't have to specify emmc_pll_core=1 or init_emmc_clock (they will be set as a default).
force_turbo is optional - should be no problems with or without it.
Thanks for the heads-up.
*goes editing his config.txt*

plugwash
Forum Moderator
Forum Moderator
Posts: 3462
Joined: Wed Dec 28, 2011 11:45 pm

Re: Next firmware tree is now 3.10

Tue Dec 10, 2013 12:18 am

Are there still outstanding issues with 3.10 and/or the latest firmware that are preventing it being pushed to the foundation's apt repo?

gkreidl
Posts: 6114
Joined: Thu Jan 26, 2012 1:07 pm
Location: Germany

Re: Next firmware tree is now 3.10

Tue Dec 10, 2013 11:48 am

plugwash wrote:Are there still outstanding issues with 3.10 and/or the latest firmware that are preventing it being pushed to the foundation's apt repo?
yes, look here:

http://www.raspberrypi.org/phpBB3/viewt ... 58#p466644
Minimal Kiosk Browser (kweb)
Slim, fast webkit browser with support for audio+video+playlists+youtube+pdf+download
Optional fullscreen kiosk mode and command interface for embedded applications
Includes omxplayerGUI, an X front end for omxplayer

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Dec 10, 2013 12:27 pm

plugwash wrote:Are there still outstanding issues with 3.10 and/or the latest firmware that are preventing it being pushed to the foundation's apt repo?
I'm not aware of any blocker issues. We're going through a beta test cycle of a new 3.10 based raspbian image that will end up with a new sdcard image and updated apt-repo.

User avatar
DougieLawson
Posts: 36312
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Next firmware tree is now 3.10

Tue Dec 10, 2013 12:33 pm

I think the point is that we can't download the kernel headers or Linux source package for 3.10.##+ using apt-get.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Dec 10, 2013 2:11 pm

DougieLawson wrote:I think the point is that we can't download the kernel headers or Linux source package for 3.10.##+ using apt-get.
I don't believe this is the issue being discussed. This is no different from 3.6. See:
http://www.raspberrypi.org/phpBB3/viewt ... 66&t=57401

Return to “Advanced users”