1
submitted 1 week ago by [email protected] to c/[email protected]

Q: What do you look forward to on a Sunday morning?
A: Relaxing with calm music, a bowl of strawberries, and some quality time with NVDIMM Persistent Memory modules

03:19.. it's still early, plenty of time to debug IRQs! ๐Ÿ˜Š

also, for whoever needs to know this newfangled manner of kernel command line arguments in Fedora/Redhat distros ... if you're tired of typing out the active kernel string when looking up its params via "grubby", here's a var-subshell substituted whatever call to ease those pains:


root@upgrayyed:~# grubby --info=$(grubby --default-kernel)
index=1
kernel="/boot/vmlinuz-6.10.7-200.fc40.x86_64"
args="ro resume=UUID=redacted rd.md.uuid=redacted rd.md.uuid=redacted console_msg_format=syslog loglevel=7 hibernate=no iommu=pt mem_encrypt=off selinux=0 nouveau.blacklist=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau console=tty0 console=ttyS0 console=ttyS1"
root="UUID=redacted"
initrd="/boot/initramfs-6.10.7-200.fc40.x86_64.img $tuned_initrd"
title="Fedora Linux (6.10.7-200.fc40.x86_64) 40 (Server Edition)"
id="e1f345d2eb0a4de3ab64da772c942e05-6.10.7-200.fc40.x86_64"


#linux #freebsd #supermicro #dell #serial #nerdery #commandline #cli #terminaljunkies #berries #morning #sundaymorning #insomnia #diurnal #nosleep #optane #biostuningforever

a Serial over LAN terminal pane, showing the BIOS information from a Supermicro X12 motherboard, which displays Optane NVDIMM module specs and their summary values

[-] [email protected] 1 points 1 week ago

@[email protected] that's correct. it arrived rather recently, and firmware updates are required (easy, but requires Qualcomm's app which runs on windows, so that's a thing). As of today I'm working through some kernel debugging and setting up remote log capture for easier parsing during boot iterations. very fun!

1
submitted 1 week ago by [email protected] to c/[email protected]

desk, check. sorta noisy poe++ switch, uh hu... laptop about the size of my keyboard, yep. laptop that's constantly trying to distract me from priority tasks.. yes, again.

oooh okay saturday morning, you win this round. time for laptop debugging!

#arm64 #thinkpad #snapdragon #freebsd #nerdery #ihearthardware

[-] [email protected] 1 points 2 weeks ago

@[email protected] yep, that's a fun mod! ooh the X280 was a great laptop, and is still a great laptop! somewhere around here is a X260 waiting for a panel upgrade, will give your tutorial a shot before disassembly occurs. ๐Ÿ‘๐Ÿป

[-] [email protected] 1 points 2 weeks ago

@[email protected] fwupdmgr is one of the better examples of a distro-agnostic application. every time that I use it there's an urge for cloning and mirroring the firmware repos in an effort to port its functionality to freebsd.

[-] [email protected] 1 points 2 weeks ago

@[email protected] @[email protected] good question! still looking for a PCB schematic, though getting to a full boot command line would offer a step towards running hardware topo system calls necessary for enumeration.

for better or worse, the text screams by until the panic stops, so I'll be connecting its HDMI out to a PiKVM, which will facilitate streaming log capture; improving access to all that debugging data. typically my workflow for arm64 + freebsd involves either using a SoL terminal and/or RS232 / TTL output capture, but those are not available for a laptop... hmmm hmm.

[-] [email protected] 1 points 2 weeks ago

@[email protected] thanks, it's the higher spec OLED option

1
submitted 2 weeks ago by [email protected] to c/[email protected]

What have we here? First boot attempt with FreeBSD 14.1 aarch64 on a Thinkpad T14s gen6, running a Qualcomm Snapdragon X Elite processor.

A few next steps, update the BIOS and other firmware blobs, mess around with some dtb files, poke and prod, iterate as usual.

#FreeBSD #Thinkpad #Snapdragon #arm64 #kernel

Boot process screen with a kernel panic, showing sequence and debug details from FreeBSD 14.1 on an arm64 laptop, Thinkpad T14s Gen6

[-] [email protected] -3 points 1 month ago

@JackbyDev Why would that be a question at all? Buy a domain name and take care of your dns records.

that's an odd way to say that you don't own any domains. that's step one, but does it even need to be said?

[-] [email protected] 10 points 1 month ago

@solrize @thehatfox get a free wildcard cert for your domain and use it just like any other. nothing new, nothing different. I have those running on LAN-only hosts behind a firewall and NAT with no port punching or UpNP or any ingress possible.

if you don't want to run a private CA with automated cert distribution (also simple with ansible or a few tens of LOC in shell or python), the LetsEncrypt is trivial and costs nothing -- still requires one to load the cert and key onto a server though, which is 2/3 of the work vs private CA cert management.

winterschon

joined 3 months ago