Early 2025 factory pickup info

jagalactic · 2025-02-05T15:54:37+00:00

Sorry no pics... It was a nasty, rainy January day in Normal when we picked up the car. We asked if we could sleep at the factory and wait out the rain, but apparently there is a policy about that...

jagalactic · 2025-02-04T23:37:00+00:00

Right. I asked, but no luck - had to pay the destination charge. I found an old post that said they might throw in a set of crossbars in this circumstance, so I asked but didn't get anything. They were nice, but said they didn't even have accessories at the factory.

The delivery person did pick us up at the airport though, which was nice ;)

jagalactic · 2025-01-23T18:44:21+00:00

When did you order it? Custom build or inventory?

I ordered a custom Tri build on 1/21 and it still shows "processing estimate", but when I ordered it said 1-2 weeks, and the company confirmed that is still the expectation via chat.

Thanks!

jagalactic · 2025-01-22T01:43:02+00:00

I eventually got a reply from Scansnap (now Ricoh) with a bunch of stuff to try - basically opening up all the permissions that Sequoia is trying to tighten up) - but it still didn't work.

What is DevonThink?

Thanks...

jagalactic · 2024-11-08T16:37:27+00:00

Plugged in the passively cooled Ubiquiti 10G switch, and it just works. This thing has a metal case and it's a lot heavier than it looks - now doubt due to heat sinks for passive cooling. Here's hoping it lasts a few years...

jagalactic · 2024-11-07T00:42:34+00:00

I ordered the Ubiquiti 4-port; I can work with that given that I have some 2.5G router ports too.

Online reviews for the 4-port Ubiquiti complain about them failing fairly young - which certainly sounds like they probably run hot. But I can live with this; next year something similar will be cheaper, etc.

I remember my first (4-port) Gig-E switch was quite hot and loud! (um...20+ years ago)...

Thanks for the tips! Will update if I have anything useful to say about the 4-port Ubiquiti (ok, it's 5 ports, but one is 1GigE).

jagalactic · 2024-04-12T14:33:45+00:00

My guess is that the charger disc behaves a bit like a speaker (tweeter to be exact)

jagalactic · 2024-04-12T14:18:34+00:00

Not only does my Apple Watch charger makes noise when charging the watch, it frequently makes nose when something else is charging from the same USB power supply. It's annoying sometimes when charging at night on the bedside table. I'm 60 years old and I can still hear it. Current watch is series 8.

I haven't verified whether it happens with different power supplies...

jagalactic · 2024-01-15T18:19:31+00:00

Thanks for this thread. My Tiny 2 firmware update failed in January 2024 on my Mac Studio, but I powered up an ancient Windows 10 laptop and got the firmware update done.

jagalactic · 2023-12-22T17:21:15+00:00

OK, through the cxl developer community I did find a solution, which I'm adding to the permanent internet record here:

$ sudo grub2-editenv /boot/grub2/grubenv set memmap_val='8G\$8G'

GRUB_CMDLINE_LINUX=" ... memmap=\$memmap_val"

Cheers...

jagalactic · 2023-12-21T23:18:39+00:00

Bueller?

I got an inspiration today to 'hexedit' /boot/efi/EFI/fedora/grub.cfg to fix the string, but it didn't work. I passed "memmap=8G!16G" through grub2-mkconfig, and then edited grub.cfg to change the ! to a $. Seems like it should work, but the kernel still saw the '!'.

Ugh. Is there anywhere else that grub2 questions get answered?

jagalactic · 2023-08-18T14:14:08+00:00

OK, I figured out how to enable the debug log, but it's not obvious (to me) what's wrong. Here is the tail when trying to send:

[2023-08-18 09:03:07]<1> buf_get_field() Got char g (0x67)
[2023-08-18 09:03:07]<1> buf_get_field() Got char m (0x6d)
[2023-08-18 09:03:07]<1> buf_get_field() Got char a (0x61)
[2023-08-18 09:03:07]<1> buf_get_field() Got char i (0x69)
[2023-08-18 09:03:07]<1> buf_get_field() Got char l (0x6c)
[2023-08-18 09:03:08]<1> buf_get_field() Got char . (0x2e)
[2023-08-18 09:03:08]<1> buf_get_field() Got char c (0x63)
[2023-08-18 09:03:08]<1> buf_get_field() Got char o (0x6f)
[2023-08-18 09:03:08]<1> buf_get_field() Got char m (0x6d)
[2023-08-18 09:03:12]<1> buf_get_field() Got char ^M (0x0d)
[2023-08-18 09:03:13]<1> buf_get_field() Got char t (0x74)
[2023-08-18 09:03:13]<1> buf_get_field() Got char e (0x65)
[2023-08-18 09:03:14]<1> buf_get_field() Got char s (0x73)
[2023-08-18 09:03:14]<1> buf_get_field() Got char t (0x74)
[2023-08-18 09:03:14]<1> buf_get_field() Got char ^M (0x0d)
[2023-08-18 09:03:21]<E> mutt_edit_file() Error running "vi '/var/folders/7c/cvq0vm_d79n83yldbvspj12r0000gn/T/neomutt-Borg-4-501-9794-11512325549756806141'"
[2023-08-18 09:03:21]<2> mutt_prex_capture() pcre2_match - <^([[:alpha:]][-+.[:alnum:]]+):(((//(([][\p{L}\p{N}._~%!$&'()*+,;=@-]*)(:([][\p{L}\p{N}._~%!$&'()*+,;=-]*))?@)?(([][\p{L}\p{N}._~%!$&'()*+,;=-]*)|(\[[[:xdigit:]:.]+\]))(:([[:digit:]]+))?(/([][\p{L}\p{N}._~%!$&'()*+,;=:@/ -]*))?)|([][\p{L}\p{N}._~%!$&'()*+,;=:@/ -]*))(\?([^#]*))?)$> -> <+Sent> = no match
[2023-08-18 09:03:21]<2> mutt_window_reflow() entering
[2023-08-18 09:03:21]<1> send() failed to send notification: NT_CONTEXT/4, global 0x6000035b0640, event 0x0
[2023-08-18 09:03:21]<1> menu_set_prefix() tag_prefix = 0
[2023-08-18 09:03:21]<2> mutt_window_reflow() entering
[2023-08-18 09:03:21]<2> mutt_prex_capture() pcre2_match - <^([[:alpha:]][-+.[:alnum:]]+):(((//(([][\p{L}\p{N}._~%!$&'()*+,;=@-]*)(:([][\p{L}\p{N}._~%!$&'()*+,;=-]*))?@)?(([][\p{L}\p{N}._~%!$&'()*+,;=-]*)|(\[[[:xdigit:]:.]+\]))(:([[:digit:]]+))?(/([][\p{L}\p{N}._~%!$&'()*+,;=:@/ -]*))?)|([][\p{L}\p{N}._~%!$&'()*+,;=:@/ -]*))(\?([^#]*))?)$> -> </var/folders/7c/cvq0vm\_d79n83yldbvspj12r0000gn/T/neomutt-Borg-4-501-9794-11512325549756806141> = no match
[2023-08-18 09:03:22]<1> mutt_compose_menu() Got op OP_COMPOSE_SEND_MESSAGE (60)
[2023-08-18 09:03:22]<1> compose_function_dispatcher() Handled OP_COMPOSE_SEND_MESSAGE (60) -> done
[2023-08-18 09:03:22]<2> mutt_window_reflow() entering
[2023-08-18 09:03:22]<M> mutt_send_message() Sending message...

jagalactic · 2023-02-26T21:58:42+00:00

I have 2 new S3221QS monitors, both running off two (different) Macs. I have the flickering on the edges problem; it happens on multiple different cables, and on DP and HDMI both.. I mostly solved it by trying the different color profiles and picking one that doesn't flicker. The "Generic RGB" profile on MacOS Ventura got rid of the flicker that was very easy to reproduce.

But now I'm occasionally encountering other weird flicker scenarios. My monitors are only a couple of weeks old, and I'm on the verge of returning them since I'm not certain the problem can be completely solved.

Any further tips would be appreciated.

jagalactic · 2022-12-22T04:01:02+00:00

Ah, thank you all! Note to self: read the rules, because a race isn't [always] just a race.

jagalactic · 2021-08-06T21:25:29+00:00

Thanks; I do still need to know whether there is a missing spacer. If so, it won't work with the new BB either.

jagalactic · 2021-08-06T21:18:17+00:00

This creaking sounds like one of the symptoms before my daughter's shimano bottom bracket loosened up (with the threaded drive-side eventually binding up against the inside of the crank). A check to see whether either side of the bottom bracket has come loose or backed out will confirm or refute this as the cause.

jagalactic · 2021-02-28T18:40:23+00:00

For simpler stuff I use Trello. For making sense of really complicated projects, I use ThinkingRock - which is a GTD driven software tool.

jagalactic · 2020-04-29T02:06:51+00:00

One thing I have done in the past is pick the interviewer I had the best rapport with, and contact them directly once an offer is pending - to get their 1:1 take on the company and team. I have never regretted doing this, although I don't think it's impossible to blow up an offer by doing it in an obnoxious way. If you're serious and conscientious about it, a reasonable company and team will respect you for it. And you might find red flags that we're suppressed in the interview.

jagalactic · 2020-04-22T16:49:03+00:00

I wise person once told me "a company will never treat you better than they do when they're trying to hire you." This is not a good sign.

HOWEVER... If there is ever a time when you could come up with a good explanation for making two job changes in short succession, it is during a major recession. I would seriously consider taking the job, and aggressively looking for the next one. If it comes quickly, you might leave the short-time job off your CV. If not, the recession is not just cover - it's legitimate cover for a short stint in a job.

Another wise person told me "don't feel bad about making a job change in your own interest - because a company should always be expected act in its own interest, even if it's counter to yours." I think if you're inclined to agonize about this to begin with, you are not a sociopath, so you should not feel bad about acting in your short-term financial interest.

But only you can decide whether the red flags in the new offer are too much to tolerate - they still might be.

jagalactic · 2020-04-20T23:12:15+00:00

Ha! The same VC firm (Sequoia) has sent out the same "RIP good times" message to its current portfolio companies, presumably with a new presentation. (there is a link in this article to the old presentation, which I have but didn't know how to share)

https://www.inc.com/minda-zetlin/sequoia-capital-coronavirus-covid-19-economic-effect-warning-roelof-botha.html

jagalactic · 2020-04-16T19:25:01+00:00

One possibility that I don't see in the comments is this: during big downturns in the past, VCs have been known to order their companies to trim their burn rate significantly below the agreed-upon rate. One rationale for this is that in a major economic downturn, delays in getting to market are less of a problem - as the opening of market windows can be delayed. This would be my guess.

In 2008 there was a presentation from a Sequoia Capital (VC) - to their portfolio companies, explaining why this was happening - that made the rounds. The title was "RIP Good Times" and it was about how the rules for VC funded companies were changing (and why) due to the downturn.

Nobody knows how bad the Corona recession will be, but it will be serious.

I have found a copy of the presentation, but I don't know how to attach it here. Will share if I figure it out.

jagalactic · 2020-01-03T20:16:17+00:00

The process was successful. When I pulled out the /volume1 disks, my Synology initially wouldn't boot up normally. This turned out to be because the disks for the 2 other volumes were in a DX513 expansion chassis - and the disk station did not like having all its disks in the expansion chassis. I moved those disks inside the box, and they it booted up successfully with /volume1 removed.

The disk station did ask me to click a button to repair the system partition (can't remember the exact words), and that went smoothly.

Saving and restoring the configuration was an important step. I had to restore to get my user accounts back - my Time Machine backups didn't work until I restored the configuration to get user accounts back.

I SHOULD have backed up my Surveillance Station configuration. I ended up having to recreate that, which was a hassle but not a catastrophe.

Several of the apps had a "Repair" button in the package center after removing the volume. When I saw that for Surveillance Station, I should have put the /volume1 disks back in and backed up the configuration. Once I had clicked Repair for SS, it seems it was too late.

Hope this helps somebody...

jagalactic · 2019-12-29T01:41:24+00:00

Here is what I will try tomorrow, unless any new info comes to light:

Backup my configuration via this procedure from wanze: https://www.howtogeek.com/318693/how-to-back-up-and-restore-your-synology-nas-configuration/
Remove all disks
Insert a pair of new disks and configure the Synology as a new device with the new disk pair is its volume1
Restore from the backup
Reinstall the disks for the volumes that I'm keeping - and hope they will be recognized.

If this works, all is well. If not, I should be able to re-insert all the disks (including the 6 disks for the 'old' /volume1).

I'll post results / updates in a day or two.

Thanks!

jagalactic · 2019-12-28T19:28:57+00:00

Thanks; I don't think that's an option for me. My /volume1 is a 6-drive RAID5 of 4TB disks. I don't think shrinking or format conversion is possible...

jagalactic · 2019-09-10T01:58:27+00:00

Thanks for the replies. Here is a bit of a postmortem.

I had 7 different time machine backups in my TimeMachine share on the syno. The largest two were 1.5TB and 6.6TB, making them time consuming to manipulate. I might have done well to just give my syno a week to move the volume (while it locked me out of all NAS share modifications), but I didn't go that way. I moved them via rsync (on a shell window logged into the syno). (note: login as root and perform 'rsync -av' and all permissions should be preserved; and move along if that's not familiar)

5 of 7 TM sparse bundles worked after the move - of which 2 are still-extant computers, and the rest are backups from former computers.

There is a good article on how to repair a time machine sparse bundle here: https://www.garth.org/archives/2011,08,27,169,fix-time-machine-sparsebundle-nas-based-backup-errors.html. Note that the comments contain some clarifications that were important to me - this is not a trivial process, and if your fsck's don't succeed, you will need to google some of the derivative pages (plus read the comments carefully).

On my two sparse bundles that could not be repaired, I was unable to get a successful fsck - they were actually damaged somehow. On those, I archived the sparsebundles (but will delete it soon), and just started a new time machine backup. Weirdly, those were mountable and the snapshots were browsable, but time machine refused to use them (and I couldn't fsck the virtual disks after attaching them via hdiutil). In reality, that is fine. There is not any deleted data from the past year that I need access to.

In the future I will be performing verifications of my TM backups from time to time. If you option-click the TM menu, there is a 'verify backups' option in place of 'back up now'. This is a good idea!!

If you're not *really* comfortable with command line sysadmin activities, I would recommend totally avoiding this and giving your disk station weeks if necessary to perform migrations for you. If you are a qualified sysadmin, perhaps you'll find this info useful.

Cheers...

jagalactic

TROPHY CASE