“Honestly, a literal raspberry might do a better job at network integration than your printer right now. Just be careful it doesn’t jam… or jam, you know?”

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.)

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? 🙂

does this happen if you force it to shut down by holding the power button for +10sec, or if you remove and reinsert the battery after power off?

forcing a shutdown or removing and installing the battery, will ensure that the laptop is indeed shut down and not just halting during the shutdown process.

if you still have the same issue after this test I would guess your battery is dying, but if not you know that the issue is a software and not a hardware problem…

anyway, best of luck getting it sorted

do you have any usb devices, like external hard drives, chargers or similar connected to it? a lot of the laptops allows for usb charging/supply of power even when switched off, and this could be one of the sources for the drainage.

try disconnecting all USB cables if any are connected and see if the problem disappears?

never mind, did not see the line about no connected usb cables until after posting

Er jo en hel Lemmy instans for Danmark her, så det finnes nok flere av osw, og ja, jeg er fra Norge 🙂

Håper det ordner seg når du får installert ny font når du har tid og anledning til det 🙂

replying to myself here, but also, if this where supposed to work, which I doubt it will because it’s not feasible with tcpip, your second router would need to have the first router as gateway, but that is not possible when they are on the same subnet, and also your router will most likely not allow it because nat/routing will break, but if this was possible, devices behind your second router would not be able to connect to the devices before and vice versa, because since they have the same subnet, the traffic is considered local and not going through the router, and therefore the will not see each other as the NAT provides a separation between the networks…

you cannot use a router as a switch without using routing and different subnets … so … you might want to reconsider your design

Might be conflicts due to several routers using the same subnet… could cause some interesting ARP issues for the switches, and also DHCP conflicts if something is wrongly cabled / configured.

I would try disconnecting everything from after the first switch, connect a computer there to see if it works ok, then reconnect and test behind each step to see where it breaks instead of checking in the end where the problem could be agitated from a issue earlier in the network…

also, if the router has a firewall/nat you will not be able to reach anything behind it, even if there are different subnets being used… to be able to reach devices behind a router, the network would need to be routed and not nat’ed as nat combines all network traffic into the IP of the router before sending the traffic away, so clients on the other side has no way of knowing who or where the traffic came from after the nat’ed router.

I suggest you read up about this if you are not familiar with difference between NAT and routed traffic.

anyway, this is just my theory, hope you find your problem and get it sorted :)

(edit added part about nat)

you’re welcome :)

or since you probably are from Denmark since you mentioned Danish in your other comments:

🇩🇰 bare hyggelig, og håper du fikk løst problemet ditt 🇳🇴

thank you :)

not to be that guy . but have you tried to search for an answer?

https://github.com/flatpak/flatpak/issues/4435

first hit on “flatpak question marks”… it’s due to the font you use in the terminal does not support or not fully support Unicode characters or your locale settings are not correct.

hope this helps and answers your question :)

(edit, lost part of a sentence)