August 21, 2025
- Looking if there is a way to flash the firmware of the Sitara AM355xZCZ. Found this post, yet the arago-project is gone. Luckely its archived. The main Arago page can be found here
- The git-page can now be found here
-
- Going to update the BIOS of nb-dual (Feb. 2025 version). Version is now 1.28.1
- Also Installed the Intel Killer Performance Suite version 40.25.614.156. Restart required.
-
- Updated nb-dual Linux partition from 20.04 to 22.04. After reboot software update seems to work again. First another reboot.
August 20, 2025
- Received a Printr One Element. Powering up with USB-micro. Green light lights up.
- The Element has 800MHz Ti ARM Soc, 4 GB storage, 512 Mb Memory, and 2.4 GHz Wifi. Most important, a Universal Printer Connector.
- The Element is still in Felix Shop.
- nb-dual sees a COM3 port.
- BlueTooth sees a number of unknown devices and Quest 3.
- See only two hidden wifi-networks.
- The Element was originally a KickStarter project.
- This update gives a lot of HW details.
August 17, 2025
- Booted my Shuttle and selected the boot-partition with F7. Selected P2 (1TB), which should startup my Windows11 partition. Get a Windows-icon, whereafter the screen stays black. Maybe it switches over to the Nvidia-card, although not connected. Try again, with the Nvidia-card on-board.
- With the Nvidia-card mounted, the P2 partition is no longer an option to select as boot-device.
- Put the secure boot (TPM) on again, but still the P2 partition is no longer visible.
- Tried to do a BIOS update with the secure boot on, but still get the ROM-check error. Also with the secure-boot off, the ROM-check fails.
- With the secure boot on, Windows 11 starts, but seems to switch to the Nvidia output, without drivers.
- How do I get in Safe mode.
- Followed this trick and forcefully shutdown (2x). Starting with an automatic recovery preparation.
- This ends with a stopcode DRIVER PNP WATCHDOG.
- Rebooting gives a Windows icon with endless progress sign.
- Going to make a CT-rescue stick from the 16GB Hema stick. (BIOS update didn't work anyway).
- Still had Rufus 3.18 on my nb-dual. Script seems to use Rufus 4.3. Don't see it in the download.
- Needed some time to find the option Uitsluitingen (Instellingen, Virus, Instellingen voor virus, Instellingenen Beheren, Uitsluitingen, Uitsluitingen toevoegen).
- The PEBackery failed the first time, because I unpacked it in C:\ctrescue2025\ctrescue instead of C:\ctrescue. In the right folder PEBackarey could claim the Defender exceptions itself and continue (currently on 31.8%)
- Yet, it failed again (on installing CrystalDiskInfo. Removed this application from the list on the left.
- Also HD-Tune, AgentRansac and BusyBox failed. From the drivers, the ExtraDrivers and Intel MEI drivers failed.
-
- In the mean-time I was looking at the other partition. Selected other restart options, and selected safe mode with networking. Yet, no network availab. Could try an ethernet cable or my wifi-stick. Wifi-stick worked.
- Exectuing the Nvidia App fialed, because DotNet could not be installed in Safe-mode. Looking for T400 drivers manually. Downloaded the RTX Driver 580. Install worked.
- Also downloaded Intel Driver Assistant, but failed to be installed.
- Used PowerShell to create UpdateLog. Last update seems to be today. Yet, Windows Update keeps on running for ever. Could reboot again, and try option 7 or 8 (allows drivers without signatures and disable early Malware detection).
August 12, 2025
- Made a clean BIOS-stick, still the ROM-check fails. A suggestion was to switch off Security Device Support. Still the ROM-check fails.
- Instead tried if the system now boots with the Security Device Support off.
- Normal boot doesn't work, recovery mode with Networking gives again the Windows 10 of the other SSD.
- Should next try connect the Ethernet and try to do an update.
July 25, 2025
- Started the upgrade of my Shuttle at home with downloading PC-Health Check app.
- Result of the check is that TPM 2.0 was not detected.
- Checked specs of Shuttle sh370r6. BIOS supports FirmWare TPM. Going into the BIOS.
- Removed the Nvidia T400. Connected the HDMI to my Dell screen, the left motherboard DP-port to my Samsung screen. Finally I had my BIOS screen (F2 or DEL), v1.15. Enabled Security Device Support. Windows took a while to make a new recovery point, but after that th pc-status was able to detect teh TPM 2.0 module.
- Used the time to clean-up the PC (94% full). Took me a while to find the location of the stored TotalWar games: C:\Users\*\AppData\Roaming\The Creative Assembly
- Note that I also could have updated the BIOS, the latest have TMP enabled by default.
- Seems that the flash is done on a USB-stick, if I interpret the FAQ correctly.
- The Windows11 compatibility page suggest to install drivers from DVD (or just update).
- After refreshing the WindowsUpdate, WindowsUpdate report that the PC is not ready for Windows11, while the suggested Health-check says OK.
- Followed the suggestion of ComputerTechniek and downloaded the WindowsInstallationAssistant. That seems to work OK, busy with step 3/3.
- That Worked. The Shuttle is now running Windows11 (24H2). Performing the additional updates.
- Put the GPU, which gives me a very long wait screen. Rebooting gives resetting devices, and being back at Windows10. Is this my other SSD (1GB instead of 1T). Resetting boot-order in BIOS gives black screen.
- Tried it again, but came again on my old drive. Tried to upgrade from there, but first had to update to Windows10 version 2004. At least the PC-Health Check said that my PC was OK.
July 11, 2025
- Trying to update XPS workstation to Windows11.
- Starting up. The HMDMI connected to GPU gives no signal, the one on the board. Does.
- The machine is doing a count-up at a terminal screen. Looks like Linux, although I would expect that the default boo-option would be Windows. Let it run.
- Last time I worked on the XPS was May 17, 2024 and March 20, 2023. In 2023 I had a working Ubuntu 22.04 system.
- On April 27, 2022 I mention a trick from September 12, 2021 to boot in recovery mode.
- I installed Ubuntu 20.04 on the XPS workstation on May 29, 2020.
- I made the workstation double boot at Febrary 7, 2019.
-
- Boot screen is the other HDMI (of the GPU). Was able to boot into Windows (nvme0n1p1 partition).
- Starting with updating Windows first. Also got the option to download Windows 11. First download the other updates.
- Had some trouble finding the PC Health Check, but had downloaded it before. Did the check, which are OK, except for the TPM 2.0.
- Seems that the XPS 8930 has no TPM-chip at all. According to this this Dell post, it seems that TPM is disabled in the BIOS.
- Couldn't turn TPM on in BIOS directly, because Secure Boot was off. Secure Boot could't be turned on, because Legacy Option ROMs was on. Turned Legacy Option ROMs off, which gave warning. Turned Secure Boot on, which gave same warning. TPM was now automatically turned on. Saved and rebooted. Grub boot-menu still showed up, was able to boot Windows 10.
- PC Health is now OK with the update, and after a Windows Update Refresh the option to Upgrade to 24H2 also showed up. Downloading the new version now.
- Upgrade succeeded.
-
- Trying to get Ubuntu 22.04 working again.
- Just sudo apt reinstall ubuntu-dekstop didn't work. Firefox was not running, so snap distable firefox was not needed.
- Did sudo systemctl list-units and saw a problem with sudo journalctl -b -u systemd-modules-load.service. Checked sudo dkms status and removed all edvi drivers with sudo dkms remove evdi/1.7.0 -all -a, followed by sudo displaylink-installer uninstall. At least no problems any according to systemctl. Did sudo apt install --reinstall linux-headers=$(uname -r). Still no reboot.
-
- Going ahead from 22.04 to 24.04 with sudo do-release-upgrade. Got a warning about ros, but continue.
February 22, 2025
- Repaired Barend's old laptop. The issue seemed to be a loose contact between the HDD board and the motherboard.
- First installed Ubuntu 20.04 on the original 250 Gb harddisk when it was external.
- Installed it internally, gparted saw the disk but without any partition. Selected msdos as partition type, and was able to install Ubuntu 20.04 again, but now internally.
- The laptop battery was on 70%, now charging again.
- When working on the HDD, I had to connect/deconnect the keyboard and touchpad. Forgot to test touchpad before screwing it close again. To be fixed the next time I open the computer again.
- For now I have a working spare Ubuntu 20.04 laptop again.
January 9, 2025
- Was able to use PulseSecure after cleaning some diskspace from ~/data/semfire, using the trick from stackexchange post: /opt/pulsesecure/bin/setup_cef.sh reinstall.
- Inspecting the disk from Barend's old laptop. Gparted sees that it has a rfs file system. Could not mount the file system. Gparted searches for a file system on this partition, to do data discovery, no avail.
- Tried some of the tricks of this post, but get from sudo zpool import the response no pools available to import.
- I have a vague memory that I tried a new-type of file-system when installing Ubuntu on Barend's laptop. Maybe that wasn't a good idea.
-
- Used Gparted to format the partition to ext4-format. Could mount the drive of 327Gb, but there was only a empty lost+found (although 1.94 Gb was used).
- Trying to put the SSD back in the computer and reinstall Ubuntu on it.
January 3, 2025
- The trick to use ssh -m hmac-sha2-512 worked. Haven't tried scp -o MACs=hmac-sha2-512.
- Better to set the default algorithm somewhere.
- The advice to
change a register key only works with nsoftware suite.
Better option would be to edit ~/.ssh/config.
Previous Labbooks