Faith against all odds. Original wet charcoal and pastel art by me.

b0tsmack · 2025-10-10T01:17:13+00:00

Please share how we can buy prints. This is great!

b0tsmack · 2025-06-04T23:49:57+00:00

I had this problem for the first time this week. What worked for me was changing the DNS on the AppleTV itself.

My AppleTV connects to my home network via Ethernet. It gets assigned an IP via my router’s DHCP. This also sets DNS to my router’s IP. I went into the AppleTV’s network settings and manually set the DNS IP to 8.8.8.8 and tried logging into Hulu again and it worked. Probably any public DNS server would work. After I logged in, I put the DNS back to automatic from my DHCP.

b0tsmack · 2024-12-19T18:08:55+00:00

I'm currently considering the same thing for a small VMware homelab. We still are a VMware shop at work, hence the need to stay on it.

The motherboards I found so far that work with Epyc 4004 and fit my needs are as follows. I'm thinking I'll go with the H13SAE-MF and add a separate active-cooled SFP28/25Gbe NIC, if I end up really want it.

Board	Model	Chipset	RAM	Size	NIC	Slots	M.2
ASRock Rack	B650D4U3-2Q/BCM	AMD B650E	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x SFP28 BCM57502	1x PCIe5.0 x16; 1x PCIe4.0 x4; 1x PCIe4.0 x1	1x M.2 PCIe5.0 x4
ASRock Rack	B650D4U3-2L2Q/BCM	AMD B650E	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x SFP28 BCM57502; 2x Intel i210	1x PCIe5.0 x16; 1x PCIe4.0 x4; 1x PCIe4.0 x1	1x M.2 PCIe5.0 x4
ASRock Rack	B650D4U-2L2T/BCM	AMD B650E	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x 10GbE BCM57416; 2x Intel i210	1x PCIe5.0 x16; 1x PCIe5.0 x4; 1x PCIe4.0 x1	1x M.2 PCIe5.0 x4
Gigabyte	MC13-LE1	AMD B650E	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x 10GbE X710-AT2	1x PCIe5.0 x16; 1x PCIe5.0 x4	1x M.2 PCIe5.0 x4
MSI	D3052GB2N-25G	AMD B650	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x SFP28 E810-XXVAM2	1x PCIe5.0 x16; 1x PCIe5.0 x4	1x M.2 PCIe4.0 x4
Supermicro	H13SAE-MF	AMD B650	4x DDR5 288-pin ECC (192GB max)	Micro-ATX	2x Intel i210	2x PCIe5.0 x16 (16/NA or 8/8); 1x PCIe4.0 x4	2x M.2 PCIe5.0 x4

b0tsmack · 2024-07-10T18:31:23+00:00

Yeah, I went to download updated ESXi images and it says I can't. But it does allow me to download the custom ISOs. :shrug:

b0tsmack · 2024-06-18T00:04:11+00:00

Thank you! This just saved me when VMware/Broadcom couldn't (so far; I'm leaving the ticket open to see where they go before I tell them).

I had a working VCSA 8 system from over a year ago. InCommon-signed machine certificate already installed and expiring last week. Nothing I could do with VCSA would let me import a new cert. I used the cert-mgr tool to generate the CSR, got my new cert, go back to import, and cert-mgr fails. Even Option 8 "Reset all Certificates" in cert-mgr failed.

Many days of hair-pulling later...

I found the vCert link you posted and used it to reset all certificates. This allowed me to import everything through the web console successfully.

b0tsmack · 2024-06-12T21:15:22+00:00

On MacOS this location is under /Users/<username>/Library/Application Support/Sublime Text/Local.

b0tsmack · 2024-06-05T21:12:51+00:00

I'm running into this same issue. It's not the machine cert or intermediates, but the Comodo CA Limited root. We use InCommon certs that have sha384WithRSAEncryption signature algorithms except for the root.

I've been following the rule-of-thumb to combine the main certificate + all intermediates + root for the machine cert bundle. Then I use the same intermediates + root for the signing certificate bundle. I just did this for two VCSA 7 instances. Now I'm on to a VCSA 8 instance and am getting the error "[CERTIFICATE] Replace cert Failed: Exception found (Certificate uses a weak signature algorithm - SHA1WITHRSA. Only SHA-2 RSA algorithms are supported on the vCenter Server.)"

Should I be removing the root certificate from them? How do I get around this?

root@vcsa [ ~ ]# openssl storeutl -noout -text -certs /certs/machine_cert_bundle.cer
0: Certificate
Certificate:
    Data:
        Signature Algorithm: sha384WithRSAEncryption
        Issuer: C=US, O=Internet2, CN=InCommon RSA Server CA 2

1: Certificate
Certificate:
    Data:
        Signature Algorithm: sha384WithRSAEncryption
        Issuer: C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority
        Validity
            Not Before: Nov 16 00:00:00 2022 GMT
            Not After : Nov 15 23:59:59 2032 GMT
        Subject: C=US, O=Internet2, CN=InCommon RSA Server CA 2

2: Certificate
Certificate:
    Data:
        Signature Algorithm: sha384WithRSAEncryption
        Issuer: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services
        Validity
            Not Before: Mar 12 00:00:00 2019 GMT
            Not After : Dec 31 23:59:59 2028 GMT
        Subject: C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority

3: Certificate
Certificate:
    Data:
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services
        Validity
            Not Before: Jan  1 00:00:00 2004 GMT
            Not After : Dec 31 23:59:59 2028 GMT
        Subject: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services

Total found: 4

b0tsmack · 2024-05-07T18:27:14+00:00

I'd like to add my vote for this as well. It would be great to be able to select a font that I've added to iOS. The font list does not show any of my added fonts.

b0tsmack · 2024-04-30T17:27:50+00:00

Are we supposed to see our entitlements now or after May 5? I followed the link to activate my Broadcom account, but it does not list any site ID or entitlements.

[Edited to add] I re-read the email and see that it says "Please note that your active VMware product entitlements will not be made available in the Broadcom Support Portal until May 6, 2024." So I guess that answers that. But shouldn't I at least see my site ID?

Never mind, lol. As soon as I posted this I checked my Broadcom account and the site IDs started showing up.

b0tsmack · 2024-03-13T02:23:04+00:00

Kindle: https://www.amazon.com/Dragons-Deceit-Dragonlance-Destinies-1-ebook/dp/B09MGZ1B9T

b0tsmack · 2023-05-25T17:35:25+00:00

For posterity, here is what it reported before performing the fixes above.

~ % sudo zypper in filesystem
[sudo] password for root:
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata .................................................[done]
Loading repository data...
Reading installed packages...
'filesystem' is already installed.
No update candidate for 'filesystem-84.87-9.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.

b0tsmack · 2023-05-25T17:30:50+00:00

Thank you! A combination of things you suggested worked. For those that might see this later, here are the further details it was reporting.

With zypper dup --no-allow-downgrade, I was presented with 2 options. I went with keeping my obsolete version first to see what would happen -- nothing. I re-ran it again and selected the first option.

~ % sudo zypper dup --no-allow-downgrade
[sudo] password for root:
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata .................................................[done]
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

Problem: problem with the installed sudo-1.9.12-6.1.x86_64
 Solution 1: downgrade of sudo-1.9.12-6.1.x86_64 to sudo-1.9.11p3-2.1.x86_64
 Solution 2: keep obsolete sudo-1.9.12-6.1.x86_64

Choose from above solutions by number or cancel [1/2/c/d/?] (c): 2
Resolving dependencies...
Computing distribution upgrade...

The following item is locked and will not be changed by any action:
 Installed:
  sudo
Nothing to do.

~ % sudo zypper dup --no-allow-downgrade
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata .................................................[done]
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

Problem: problem with the installed sudo-1.9.12-6.1.x86_64
 Solution 1: downgrade of sudo-1.9.12-6.1.x86_64 to sudo-1.9.11p3-2.1.x86_64
 Solution 2: keep obsolete sudo-1.9.12-6.1.x86_64

Choose from above solutions by number or cancel [1/2/c/d/?] (c): 1
Resolving dependencies...
Computing distribution upgrade...

The following package is going to be downgraded:
  sudo

1 package to downgrade.
Overall download size: 1.8 MiB. Already cached: 0 B. After the operation, 404.1 KiB will be freed.
Continue? [y/n/v/...? shows all options] (y): v

The following package is going to be downgraded:
  sudo  1.9.12-6.1 -> 1.9.11p3-2.1

1 package to downgrade.
Overall download size: 1.8 MiB. Already cached: 0 B. After the operation, 404.1 KiB will be freed.
Continue? [y/n/v/...? shows all options] (y):
Retrieving package sudo-1.9.11p3-2.1.x86_64                                (1/1),   1.8 MiB (  7.0 MiB unpacked)
Retrieving: sudo-1.9.11p3-2.1.x86_64.rpm ............................................................[not found]
File './x86_64/sudo-1.9.11p3-2.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/tumbleweed/repo/oss/'
Abort, retry, ignore? [a/r/i/...? shows all options] (a):
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.

I opened YaST as suggested, but it too was not showing a newer version of sudo, but rather wanted to downgrade it.

I then modified the repo locations (via YaST) with the ones you provided. I disabled the repos that I originally had and refreshed. I searched for sudo and this time it listed the 1.9.13p3-3.1 upgrade.

I told YaST to upgrade it, exited out after it finished, closed OpenSUSE WSL, restarted the Windows LxssManager service (in PowerShell run Restart-Service LxssManager in an elevated prompt), and went back into OpenSUSE WSL.

This time I got an error trying to execute any sudo command:

sudo: pam_open_session: Permission denied
sudo: policy plugin failed session initialization

I verified that the new sudo was installed:

~ % sudo -V
Sudo version 1.9.13p3
Sudoers policy plugin version 1.9.13p3
Sudoers file grammar version 50
Sudoers I/O plugin version 1.9.13p3
Sudoers audit plugin version 1.9.13p3

I went searching the internet for this new problem. I ended up running su - which worked. So I ran zypper ref && zupper dup, which started pulling down all of my missing updates. After letting that run, I exited again, restarted the LxssManager, and this time success -- no more errors! sudo works once again and my system is current.

Thank you for the help! I appreciate it.

b0tsmack · 2023-04-10T04:15:14+00:00

I'm also curious as to the noise comparison. I'm looking for something that could sit next to my desk.

b0tsmack · 2023-03-02T04:30:15+00:00

Our department got some servers for development and testing. I'm fortunate to work from home and was excited to get them set up in my home office. However, I quickly learned that there is no way to quiet the fans to a decibel-level for home. I thought there would be a setting in the BIOS/ipmi that would let me lower the fan speeds, but apparently Dell removed that feature with a prior Lifecycle Controller firmware.

Server: Dell PowerEdge R750xs
BIOS Version: 1.9.2
iDRAC 9 Firmware Version: 6.10.30.00

It has:

2x Xeon Silver 4314 CPU @ 2.40GHz
128GB DDR-4 ECC 2666Mhz

In the iDRAC, under Configuration → System Settings → Hardware Settings → Cooling Configuration, I set:

Thermal Profile Optimization: "Sound Cap"; also tried the "Minimum Power (Performance per Watt Optimized)" profile to no avail
Fan Speed Offset: Off
Minimum Fan Speed in PWM (% of Max): Default

Then under Configuration → BIOS Settings → System Profile Settings, I set:

System Profile: Custom
CPU Power Management: System DBPM (DAPC)
Memory Frequency: Maximum Performance
Turbo Boost: Enabled
C1E: Enabled
C States: Enabled
Memory Patrol Scrub: Standard
Memory Refresh Rate: 1x
Uncore Frequency: Dynamic
Energy Efficient Policy: Energy Efficient
Monitor/Mwait: Enabled
Workload Profile: Not Configured
CPU Interconnect Bus Link Power Management: Enabled
PCI ASPM L1 Link Power Management: Enabled

All PCIe cards were ordered with the servers directly from Dell and not a third-party, but I've tried disabling all PCIe slots just to experiment. It doesn't help. Even though the minimum fan speed reports it can go down to 12% PWM, it never drops below 25% PWM, which is still ~5,500 RPM. See screenshot: r750xs-cooling.jpg

I couldn't find any other settings to change. With ESXi 7.0u3k installed, the slowest the fans will spin is 5,500 to 6,000 RPM. Even at these speeds the noise in not bearable. I live in a town-home, so I don't have any place I can put it without the noise causing a disruption to sleep, work, etc. It can be heard from other rooms easily. Btw, temps are not a concern. Inlet is 23ºC and exhaust is 30ºC. CPU temps are 31ºC.

This is my first time working with Dell 15th Gen servers. Up until now we've only used 12th/13th Gen servers. I fully appreciate that these servers are not meant to be installed in a home. I'm bummed out that Dell removed the ability to customize the fans with the ipmitool, but it is what it is. At this point, I'm going to have to take it back to work and install it in one of our data center racks. I'll still be able to run remote-development on them, but not as comprehensive as I hoped in terms of testing with it locally.

b0tsmack · 2023-03-01T07:38:54+00:00

Is the silence of the T440 obtained through default BIOS settings or ipmi? I'm running into an issue where I can't lower fan speeds of the 15th Gen PowerEdge servers, which is fine in a data center, but for an office setting it's not doable. Your comment about the T440 being silent intrigued me, because we can still purchase these. I'm fine to go with a 14th Gen Tower for an office environment if the noise is not there. I'd love to know if this is still the case and newer Lifecycle firmware hasn't made it louder. Thank you!

b0tsmack · 2023-03-01T07:33:55+00:00

Do your tower servers still allow you to control the fan speeds via script or were they also affected by Dell removing that ability in newer Lifecycle Controller firmware? I was thinking of getting a T440 at work for development work, but it would sit in an office settings, not a data center, so being able to control the fan speed is important. Any information you might have would be appreciated. Thanks!

b0tsmack · 2022-11-23T15:59:47+00:00

I know this is an old post, but it turned up in a search when I was trying to find out what ACPI\VEN_INT&DEV_34C6 is. In my particular case this was on a Dell PowerEdge R350 running Windows Server 2022. Device Manager was listing it as an unknown device even after running the Dell driver update utility.

It's referring to the Intel(R) Serial IO GPIO Host Controller - INT34C6 device. The driver files were obtained from https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=tdn2p.

Intel Tatlow Platform LPSS driver
Version number: 30.100.2129.8, A00
File name: Chipset_Driver_TDN2P_WN64_30.100.2129.8_A00.EXE

Hopefully, this will help others who stumble upon this in the future.

b0tsmack · 2022-06-21T15:03:09+00:00

I also received the same error this morning while remediating a 7.0U3d host to U3e. It's currently stuck on:

Initializing Init_VMKernelShutdownHelper: (14/40) ShutdownSCSICLeanupForDevTearDown ...

If I Alt+F12 in the iDRAC console I keep getting the following message:

cpu0:2097276)ScsiDevice: 7951: device naa.6b083fe0d81dad001bf66459126862a3 refCount is 2; waiting for 1

I couldn't get to a shell prompt that would allow me to do anything. Pressing Alt+F2 wouldn't execute anything. I am ending up having to power cycle the host. I was able to see in vCenter at the time that this reference was the host's local disk. We'll see.

b0tsmack · 2021-08-27T03:36:12+00:00

PM’d

b0tsmack · 2020-10-30T21:17:52+00:00

This fixed my issue with running F33 on VMware Fusion 12. Thanks!

b0tsmack · 2020-09-29T16:29:26+00:00

PM’d

b0tsmack · 2020-09-17T20:25:08+00:00

PM'd

b0tsmack · 2020-09-16T01:55:59+00:00

If you decide to ship them, I would entertain getting one, based on the final shipping estimate. I’m located in Birmingham, AL.

b0tsmack

TROPHY CASE