I feel like I have to get something off my chest regarding not only, but in particular the attitude
at the beginning of this thread. I’m aware it has nothing to contribute to the solution and if it’ s considered to cross certain boundaries, feel free to delete it or ban me entirely.
Let me explain.
There is the [quote=“ActionA, post:2, topic:11817, full:true”]
Nothing can be confirmed without logs…
[/quote] statement to begin with. A bold statement on it’s own, but regarding the problem I described, this is just plain wrong. In my following post, not only did I provide the debug logs, I also tried to explain why the symptoms of this specific problem can be reproduced quite easily, and certainly without the need of the logs.
Even if I’m the only one reporting this, doesn’t necessarily mean, that is a non-issue. I understand
that it comes with some unlikeliness and I’m sure the devs have seen their fair share of that, but again
I didn’t post this without verifying this on two PI2s with two different SD cards hooked to two different
power sources using a greenfield installation AND a updated installation. Occurred every single time, which made me think it’s worth sharing.
Let me explain my train of thought on the above!
The original December update featured a new and improved sdcard driver which, after further review was reverted back to the original driver for issues that are not relevant in this discussion. Furthermore the December update featured a broken PiConfig package which was corrected shortly thereafter. All of this led me to think, that MAYBE the PiConfig module may have some more issues, which in turn led me to ask if anybody else has this…
Well not necessarily because:
- You don’t hit Pi config that often coming from an upgrade to another because, well, your system is tweaked
- New users tend not to use this because they are unsure or don’t want to risk to screw their installation
- User relying on automated configuration like Ansible (in my case) won’t notice this possible bug because ssh-ing in your system and changing the config.txt works as expected
Those were just a few from the top of my head…
Would it have killed me to provide the debug logs straightaway? Certainly not. Will I provide them in the future. Absolutely! Is this lecture-ish tone really necessary? I want to think it is not.
But guys. I understand you’re doing this in your free time and are sick and tired of chasing debug logs. I get that. I really do. Furthermore I’m immensely grateful for the work you are doing. I mean that. But we’re all part of this community which I really like and therefore sometimes a slightly more friendly tone would sure help.
Just my 2c… I don’t mean to attack anybody with this, it’s just something that I noticed.
I can’t stress it enough, your work is highly appreciated and respected.
Have a nice evening.