e2fsck - no progress shown

[jury]

Until now, when e2fsck was working it was showing progress through '#' character ( if I remember this correctly, but nevertheless, it was some character ) and percentage number. Lately it has just stopped to display anything, but seems to work in the background, because when the MiNT is closed properly it doesnt fire e2fsck during next boot.
First time I though that my MiNT installation got broke, as it just looks as it stopped loading MiNT. But the second time booting I decided to wait longer and see what happens. And after couple of minutes ( it takes some time to scan my 20GB ext2 partition ) process of loading MiNT started to continue and the system started fine. So now each time e2fsck is fired at boot it behaves the same.
What could happen and how to get the progress to be shown again?

Attached the screen at witch each boot, when e2fsck works, it stops for few minutes.

[mikro]

This has been fixed in recent kernels: https://github.com/freemint/freemint/issues/40

EDIT: Ah, actually now I see it's a different issue. If your partition is cleanly unmounted, you don't have to wait, correct? In that case it's another bug and I kindly ask you to provide a bugreport here: https://github.com/freemint/freemint/issues

[leech]

I need to work out why my e2fsck isn't working.

But on that note, is there a point in time when a 1.20 version of FreeMiNT is released? Just curious, I would love to contribute if I could code worth a damn.

[mikro]

But on that note, is there a point in time when a 1.20 version of FreeMiNT is released?

Rather confusingly, it's the 1.19 release you are curious about -- current 1.19 is a development alpha. The maintainer, Alan (alanh here) will decide that, I think it would be nice to make a release after all this mysterious errors are solved, most notably:

- this issue ;) (https://github.com/freemint/freemint/issues/73)
- the netusbee regression (https://github.com/freemint/freemint/issues/70) [FIXED]
- the Milan PCI USB issue (https://github.com/freemint/freemint/issues/62)
- the PCI BIOS issue (https://github.com/freemint/freemint/issues/71) [FIXED]
- more flexible mint.cnf / xaaes.cnf parsing (https://github.com/freemint/freemint/issues/32)
- maybe the XaAES + SuperVidel bugs (https://github.com/freemint/freemint/issues/41)

I've been trying to help out a little (before you thank me -- for purely selfish reasons as I want to have USB working in FreeMiNT when I finally get back home and will be able to play with the EtherNAT again) so if most/all of those issue will be solved, I'll try to push the release forward.

Apart from that, current FreeMiNT 1.19 contains heaps of improvements over 1.18 so it's certainly worth a new release.

[leech]

Thanks for the explanation, I wasn't 100% sure if it was an Odd/Even Dev/Stable type release like the Linux Kernel used to be. So 1.18 is stable, 1.19 dev branch, 1.20 stable, etc.

Whoa, see I thought I'd read and seen mass storage working on the NetUSBee, but have yet to get it working myself,

Hell, I use a ton of open source software, and I know damn well most of it is "It works for me because I wanted it to, here it is, if it works for you too, cool." Your selfishness helps everyone else

[wongck]

- this issue
- the netusbee regression (https://github.com/freemint/freemint/issues/70)
- the Milan PCI USB issue (https://github.com/freemint/freemint/issues/62)
- the PCI BIOS issue (https://github.com/freemint/freemint/issues/71)
- more flexible mint.cnf / xaaes.cnf parsing (https://github.com/freemint/freemint/issues/32)
- maybe the XaAES + SuperVidel bugs (https://github.com/freemint/freemint/issues/41)

Thanks Mikro.