Tell us about it man!!!
You'll have to expand on the wine shattering lol. As somebody with limited time to cook (we're all strapped, I agree), is it worth making a pot roast? Cooking intimidates me, but I'd like to learn where possible.
Any news on pricing? Else it looks like a beast of a radio (QRP aside).
In the market for an HF setup, so thank you for posting this.
Corrod
While I generally agree: in this case - you hit most of the points I cared to have mentioned. But considering that lack of participation that comes with small(er) communities, I'd rather have provided some input (visual or otherwise) to encourage further participation, or to at least have furthered the perception.
Otherwise, I don't have much to add. We just need more bodies doing more things here at the Fediverse in more niche communities that we care about. The issue with the larger audience is it tends to transform into the "Hive Mind" that we all know and love. Because lurkers (such as myself) don't typically add to conversations when we feel our thoughts have been well enough captured (eg - "this").
A double-edged sword, for sure.
This.
Moves like this are rather inspirational. Quality submission OP.
Day-hiking to the LeConte Lodge was more than refreshing and in beautiful November weather.
Any recipes you would recommend I start with? I've heard of but never tried this dish and I'd like to experiment :D
So this occurs after an update. Is it not possible to boot into the prior kernel?
If possible to boot into the prior kernel, can you inspect logs or the journal to see where your error is cropping up?
This issue sounds like a regression of sorts with a driver, but log/debug would help confirm. This would be one worth reporting to upstream if you can rescue some logs (I gather you can if you can boot the disk from another enclosure).
If you can boot into the machine, investigate note from the journal:
journalctl --list-bootsjournalctl -b -1,-- If you are booting into a live environment or are otherwise mounting the disk:
journalctl -D /var/log/journal/ID_GOES_HERE/var/log/journal/2dff8304d5114c44bfb1311357a3cd87-- Keep us posted.
If truly a driver regression, but you can boot from the prior kernel (if you don't have it, install it via livecd or so), definitely report this one and remain on the prior kernel until resolved. Bleeding edge things.
I read that with Guga cadence.
++ for no bar.
RIP and thanks for all the hard work I've benefited from over the last decade.
I'll think of this man while explaining vim to my new hire next week.
Where can we get them? :D