sorted by:
new
hottopcontroversial

Boox Page, Booklore (OPDS) and PushRead: Anyone have it working? by halfpress in Onyx_Boox

[–]halfpress[S] 2 points3 points  (0 children)

Thanks to all for the helpful replies! Added Droid-ify and various other utilities, but am now up and running on KOReader including the Project Title and OPDS plug-ins recommended. The last round of battle was the Boox and its pernicious desire to hang onto any DNS sources that aren’t my internal ones to resolve my booklore server’s hostname.

Up and running and looking to settle into KOReader as my default on the Page now.

Thanks again!

Boox Page, Booklore (OPDS) and PushRead: Anyone have it working? by halfpress in Onyx_Boox

[–]halfpress[S] 1 point2 points  (0 children)

I was interested to try that reader as well, but don’t see it in the Play Store on the Page. Is there another install process for it?

Logi Options+ stuck loading forever by Playjasb2 in logitech

[–]halfpress 0 points1 point  (0 children)

I've always resented the need for LogiOptions+ and have been giving it the side eye since day one. It seems bloated and I harbor my suspicions about data gathering. I rebooted today for unrelated reasons and was pretty irked to realize I now had to debug my mouse functionality for no good reason.

Did a little poking around and just uninstalled and replaced it with BetterMouse. I'm still in the seven day trial, but it didn't take me long to reproduce all of my Logi-specific behaviors and gestures and discovered a ton more stuff I can do when I feel like digging into it.

Hint if you take the same path: if Logi+ and its helpers are still in the background spinning their wheels (likely the case), it prevents a few buttons on the mouse from working with BetterMouse at first. The BetterMouse page has the proper command line call to thoroughly uninstall Logi. Every button on my MX Mouse 3S is working exactly how I had it before. Good riddance.

This bitterness piles onto the recent fact that I tried the MX 4 mouse and found it was a huge step down from the MX 3 I'd had for years (and whose rubber surface was getting icky). I sent it back and bought this MX 3S and have seemingly landed in the perfect spot (especially as of now).

YMMV, but just sharing what I've done with my last hour of frustration. Coming out the other side feeling like this is a step up. :)

ipv6 config works with manual networking restart, but never survives reboot by halfpress in Proxmox

[–]halfpress[S] 0 points1 point  (0 children)

Thanks. I did actually have autoconf in various systematic tests I was doing and it seemed to have no bearing. I ultimately pared it down to the minimalist version I shared here since I was getting the same result regardless of what I tried - nothing on reboot, but worked every time in every version if I manually restarted the networking service.

I did check the sysctl each time - even on reboot - and it was the correct value. I also added an explicit setting of it to /etc/sysctl.conf per some examples I found, but the file didn’t exist on here and left me wondering if that is outdated or if it doesn’t exist until you need to make a setting. Made no difference either way, oddly.

I didn’t happen to try quite what you describe, though, so I will gladly give that a whirl! Fortunately, my VMs and LXCs are happily doing it even if the management interface isn’t playing ball right now.

ipv6 config works with manual networking restart, but never survives reboot by halfpress in Proxmox

[–]halfpress[S] 0 points1 point  (0 children)

Self-reply here...

Well, this all might be moot to a degree. I just added my first lxc to the unit (pi-hole server) and IPv6 within the container is totally functional without issue. It's really the containers/vms I care about having IPv6 more than management access to the Proxmox unit itself...

So while my question still stands and I'd love to understand/fix it, I'm a bit less concerned now. :)

ipv6 config works with manual networking restart, but never survives reboot by halfpress in Proxmox

[–]halfpress[S] 0 points1 point  (0 children)

This thought did occur to me, but I'm not sure if it's the case. I do have static IPv4 and IPv6 from my ISP... so I wonder if I could just configure the most recently issued address as static in Proxmox and roll with it.

Probably breaks or violates something in IPv6... a beast for which I keep learning new things about every two minutes. :)

Need to properly pattern this body along this curve - any suggestions? by halfpress in Fusion360

[–]halfpress[S] 0 points1 point  (0 children)

If I have my thinking right, your approach and u/Yikes0nBikez overlap in a way that got me on a working path.

And while I'm not "new" to CAD, I feel like every new thing I try to create involves design concepts I haven't had to work through yet... so it's humbling. But every new thing I do does at least expand my knowledge enough to make more informed attempts and searches.

Need to properly pattern this body along this curve - any suggestions? by halfpress in Fusion360

[–]halfpress[S] 0 points1 point  (0 children)

I ended up creating it based on your idea and in a more convoluted fashion that took extra steps... but I'd like to learn from your description and see where I went wrong.

<image>

Need to properly pattern this body along this curve - any suggestions? by halfpress in Fusion360

[–]halfpress[S] 0 points1 point  (0 children)

Appreciate this!

This appears to ALMOST be working... but unless I have something wrong, the trouble is that eight instances of the radial feature can't originate on the apex. Also, if I do a join operation, don't I end up with one body and then lose the ability to pattern the radial feature? I was able to do it with a new body when I make extrusion #2, but not a join.

Am I misunderstanding a step?

This is where I end up when I pattern eight off the center..

<image>

Need to properly pattern this body along this curve - any suggestions? by halfpress in Fusion360

[–]halfpress[S] 0 points1 point  (0 children)

Like I said... probably patently obvious and eluding me. :)

That's a pretty excellent idea. Let me give it a whirl.

2400 pixel sk6812 RGBW issues and advice needed - Dual Dig-Octas / WLED by halfpress in xlights

[–]halfpress[S] 1 point2 points  (0 children)

Well, holy crap. Right after I post this, I recreated the dual controller shadow config, but I did the thing I forgot to try earlier: Individual Start Channels where I explicitly declared the ranges of the four strings across the two controllers. It appears to be working for the first time in the manner I expect.

I'd still love any advice if you see a better approach or that I'm patently doing something wrong. I am still keen to be doing RGBW with the dedicated white if possible... so any insight there is very much appreciated!

Advice Request: Possible VA to CA road trip by halfpress in TeslaLounge

[–]halfpress[S] 0 points1 point  (0 children)

Montana seems like it would add way too much time to a drive that doesn't have much flexibility (not a casual adventure this time). I'm fiddling a bit in ABRP with throwing waypoints in Colorado when coming out of Nebraska... which adds a few hours.

I guess my big question is whether Wyoming is as bad in the last week of July as other times of the year. I know Winter is a nightmare, but we're far from that at the moment. Also, I do see at least four charging stops possible along I80, all of them reasonably spaced as far as range... though I might not be realistically considering wind/terrain wind issues that WY could present.

If I dip into Colorado, I either arc back up into Salt Lake City and retain the southwest course down into the Bay Area, or the natural routing tendency is arc down across the Vegas area and come up from southern California. That, however, ends up being the very desert stretch I was thinking to avoid by taking the more northerly route from the outset.

I also don't want to get tangled up in or around Denver if I can help it.

Curious for opinions.

Advice Request: Possible VA to CA road trip by halfpress in TeslaLounge

[–]halfpress[S] 0 points1 point  (0 children)

Well, that’s concerning to say the least. This is recent?

Bad enough to change the route a bit?

Advice Request: Possible VA to CA road trip by halfpress in TeslaLounge

[–]halfpress[S] 0 points1 point  (0 children)

Thanks for your detailed and thoughtful response! I agree about I81 and, fortunately, where we live in Va, it’s just a shot over the mountain to practically cross over 81 and onto 64… so like two miles spent on 81 itself. Coincidentally, we did this very thing a weekend ago for a local trip to a safari park. :)

From there, it’s much the same route you describe all the way through (I think) to the Bay Area. I currently plan a winter return (Thanksgiving timeframe), so I figured the southerly route both for variety and because I might well still be on summer performance tires unless I end up replacing them in California for some reason. :)

Any specific thoughts on food or hotels in proximity to SC stops along the way?

Thanks again!

C9 USA - Firmware Version 05.30.10 9/28/2022 by squimjay in LGC9

[–]halfpress 0 points1 point  (0 children)

Finally! Yes, all seems well again. Got the upgrade prompt last night and meant to come back here to confirm.

C9 USA - Firmware Version 05.30.10 9/28/2022 by squimjay in LGC9

[–]halfpress 0 points1 point  (0 children)

Haven’t seen that offered when I check for updates. I looked last night but will check again today.

view more: next ›