y0din

Alright, let’s get into the nitty-gritty of Duckpower.

First, let’s settle the “waddling vs. flying vs. swimming” debate. Horses aren’t big on flying, so we’re talking waddling power here. Until someone locates a Pegasus, we’re limited to the traditional land-bound horsepower. If you want swimming power, I guess you’d need to measure a seahorse?

Now, here’s where it gets serious: according to the brilliant minds at Art of Engineering, we can calculate Duckpower using a clever formula. They took the mass of a duck, compared it to a horse, and ran it through Kleiber’s Law. The answer? One horsepower = 131.2 Duckpower. So, back to our math:

3 horsepower = 3 x 131.2 Duckpower = 393.6 ducks waddling their hearts out.

But wait! We probably don’t need all 393.6 ducks if we give them some solid shift schedules. Horses only get 3 HP so two can rest; following this logic, we’d only need around 100 well-rested ducks, provided they get naps and stay hydrated.

So, let’s optimize our duck workforce with a shift schedule. Assuming we only need 100 ducks, here’s the plan:

Duckpower Shift Schedule:

Total Ducks: 100

Working Ducks per Shift: 25

Shift Duration: 2 hours on, 6 hours off (plenty of time for snacks and naps)

In a day, we’d run 4 shifts like this:

1. Shift 1: 25 ducks start strong at 8:00 AM, waddling with purpose.

2. Shift 2: Fresh 25 ducks take over at 10:00 AM while Shift 1 ducks hit the ducky lounge for snacks and a nap.

3. Shift 3: At 12:00 PM, another 25 ducks clock in to keep those wheels turning.

4. Shift 4: Finally, at 2:00 PM, the last 25 ducks take over while the others catch up on R&R.

With this cycle, each duck works only 2 hours out of every 8, staying energized, waddling at peak efficiency, and ready for action.

TL;DR: 3 horsepower = 393.6 ducks waddling but if we set up a 4-shift system, we can pull this off with only 100 ducks working 2 hours each, plus snack breaks.

3 horses = 3 horsepower, which translates to a whopping 393.6 Duckpower.

Honestly, why are we still using horses as the standard here? Ducks are clearly the superior metric. So if you’re like me and prefer a more feathered approach, just remember:

3 horses = 3 horsepower = 393.6 ducks You’re welcome.

(PS: Just imagine 393.6 ducks handling 10Gb… now that’s efficiency.)

😂

well, then there is no need for the masks that drop down either then? I was making a joke, no need to be so serious? 🙂

I would hate not to be able to use the dispenser if the plane lost cabin pressure… how would I ever survive dying if I had dirty hands when it happened?..

probably related to this kernel bug though:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738

downgrading the kernel should fix it as a workaround it would seem.

the halt command is like a handbrake for the kernel, so it basically shuts everything down hard and stops, but it does not power off the system without you telling it to, so that is why your LEDs stayed on after you used the other parameter.

you could just try to downgrade/ upgrade the kernel, do s shutdown for a few hours during daytime when the computer is not beeing used, then turn it back on and check the percentage.

you will see the drain if it’s not a full night, but it might not be so drastic.

if it’s completely shut down there should be no loss in percentage, even for a short period of time as there probably is now…

I’ll try to think up another solution, but a bit busy today as I mentioned on the last post

Hi, a bit busy today so I can investigate some more later, but the problem you are describing is in many cases related to the kernel version and has been resolved by up or downgrading the kernel version.

it might be worth looking into, at least it’s a simple task, while I get some more time to investigate or offer more for you to look into.

great that it worked so far, at least now you know where the problem is :)

let’s hope it’s a software issue, in general it’s much cheaper to fix software than hardware 🙂

you can also try using the “sudo halt --poweroff” command.

if it ks software related. that command will force an instant shutdown ignoring all normal shutdown run levels (use with caution if you have open files that need to be saved in advance).

if that command succeeds as well after the battery test, you can be sure the problem lies within the shutdown run level scripts, which should help you narrow it down even more.

That’s true, but long press on the power button still works, so you can try that instead then? 🙂