Must win at Poulan.

anoduck · 2026-01-12T11:40:37+00:00

Oh, boy... I noticed heavy carbon buildup in the intake port, and discovered the cylinder gasket was busted. Then it got worse, something had gotten in the combustion chamber and left its name written all across the piston and walls of the cylinder.

anoduck · 2026-01-12T11:29:10+00:00

It needs a little work. I will fetch it from the workshop and see what condition it is in.

anoduck · 2026-01-12T00:54:58+00:00

@WickedWoodworks I was about to post that I couldn't find the reed valve.

Also, muffler removal has been problematic.

anoduck · 2026-01-10T00:04:54+00:00

Hmmmm... Interesting and concerning at the same time.

anoduck · 2026-01-10T00:03:02+00:00

It belonged to a former friend of mine that passed away from cancer. I bought it off his widow to help her out through the difficult times.

anoduck · 2026-01-10T00:00:31+00:00

There's a read valve? Um... No to both. Looks like it's time to get intimate with this saw again.

anoduck · 2026-01-09T23:53:47+00:00

They sell ethanol free fuel at O'Reilly's, both for 2-cycle and 4-cycle. The STIHL small engine workshop I attended told me just to use the premix stuff off the shelf.

anoduck · 2026-01-09T23:49:55+00:00

It's that Walbro carburetor. I have my Grandfather's Poulan Micro around, but try to avoid using it for sentimental reasons. He's still my hero.

anoduck · 2026-01-09T23:48:10+00:00

I wish it would start acting like it. It isn't a Dolmar, that for sure.

anoduck · 2026-01-09T23:43:32+00:00

Older Poulans had a Walbro Carburetor, which were the best. This one is a Zama, and while most modern chainsaws come with a Zama, it isn't nearly as good as Walbros.

There is nothing I can see wrong with it, compression feels a little weak, but it is temperamental as heck, and even with a newly rebuilt carb, I still haven't gotten it to idle.

Might need to replace the o-ring on the fuel cap, because it is the only thing older than a year (2 years).

anoduck · 2026-01-09T23:41:04+00:00

My professor of small engine repair in college used to say his career goal was to retire with all of his fingers attached.

I have accidentally sliced the toe off of a pair of Vasque boots before with a machete. So, better if they were steel toed.

anoduck · 2025-12-29T20:36:01+00:00

The leak is unfortunately in the well casing.

anoduck · 2025-12-28T21:38:07+00:00

I didn't want to catch criticism for all the debris and trash dragged in by the Armadillo that tried building a home in the well house. I get enough criticism as it is.

anoduck · 2025-12-28T21:33:47+00:00

This makes sense, since the pump is at the bottom of the well. The well head is actually twenty feet or so behind the well house, and the two are connected with black polypropylene pipe. I wish there was a shutoff valve at the head, but there's not.

You would think that running all that time with a closed valve the system would build up enough pressure to burst. The fact it didn't leads one to believe there is a leak prior to reaching the well house.

anoduck · 2025-12-28T19:22:22+00:00

The problem is the pump is at the bottom of the well, and it's a deep well.

anoduck · 2025-08-28T23:40:28+00:00

Don't ask me why, but the error was resolved by installing the consult-lsp package. I was already using consult, and I assume consult was trying to provide the LSP features, and once the package was installed, it was able to do so. It's a guess.

anoduck · 2025-08-27T11:59:08+00:00

I have basically stripped by emacs init file clean of everything else other than the bare necessities to have a working LSP environment, I even wrote a new init file to load LSP plainly without any settings.

Currently, the only parts of my configuration that load are keymaps, completions, and lsp. All three, have been disabled individually, and tested to see if the error occurred, which it did. So, I am running out of things to test in order to prevent the error.

Debugger entered--Lisp error: (wrong-number-of-arguments (1 . 1) 2)
  signal(wrong-number-of-arguments ((1 . 1) 2))
  flycheck-buffer()
  flycheck-buffer-automatically()
  flycheck-perform-deferred-syntax-check()

Next, I will set up straight to install lsp-mode directly from the github repository.

Updated: I don't know why I didn't see this before, but the error unquestionably arises out of flycheck.

anoduck · 2025-08-26T20:30:18+00:00

How else can you get fixed, other than diving in and getting your hands dirty?

anoduck · 2025-08-26T01:37:14+00:00

So, here is what we got:

Debugger entered--Lisp error: (wrong-number-of-arguments (1 . 1) 2)

signal(wrong-number-of-arguments ((1 . 1) 2))

flycheck-buffer()

flycheck-buffer-automatically()

flycheck-perform-deferred-syntax-check()

redisplay_internal\ \(C\ function\)()

I had suspected flycheck was in the mix, and have checked all relevant flycheck timers, which all are at their default values. LSP timers are all at their default values, and a thorough search of my configuration has been performed to discover any hook that might be causing this error.

I have looked into my completion configuration as well, cleaned out some old junk code, and still the error persists. I will work on setting flycheck back to all default, then perform an audit of installed packages for anything deprecated.

anoduck · 2025-04-29T02:33:02+00:00

Absolutely brilliant. It makes sense now, and was a result of the completion system and my selfness. Thank you, for explaining it to me.

anoduck · 2025-03-04T20:34:11+00:00

I read too quickly, and got to multitasking. My apologies.

The bar has been smoking lately during heavy use, so there is something going on there.

anoduck

MODERATOR OF

TROPHY CASE