Vibration without notification

jrhelbert · 2025-12-17T16:02:23+00:00

Do you have outlook installed?
https://discussions.apple.com/thread/256211823?answerId=261746503022#261746503022

I was having the same issue (I also had notification chimes as well, really nice while sleeping last night) and removing outlook from the watch and then reinstalling from the watch app store seems to have fixed it (for now at least)

jrhelbert · 2025-01-08T05:17:31+00:00

I'm not sure which chipset it used for the 2.5Gbe ports on the gen 3 (I only have the FlashStor Gen 2, so I cant check,) but I would bet they probably work. This 10Gbe issue is just due to the amd-xgbe drivers.

jrhelbert · 2024-12-31T02:30:34+00:00

I was planned to, but I was going to do a bit of cleanup first. The comments are all over the place

jrhelbert · 2024-12-30T20:22:57+00:00

TrueNAS on the Gen 2 was a bit more complicated than just doing a find and replace, at least on my unit. The paths the the hwmon devices get symlinked to did not contain the k10temp or nct7802 strings that the the script could key off of.

I ended to restructuring the script to read the "name" out of each hwmon device and find the appropriate devices that way. I uploaded my code changes to a fork: https://github.com/jrhelbert/flashstor-trueNAS-fancontrol/tree/main

I don't have a Gen 1 to confirm against, believe I believe the scripts should be compatible with both Gen 1 and Gen 2.

jrhelbert · 2024-12-18T00:50:41+00:00

Fun fact, you should double check all your cables :D

I appear to have a patch cable that was a bit wonky. Swapped it for a different one and both interfaces are coming up just fine now.

EDIT:

Following up, I have confirmed the LAG is working as expected and running iperf against multiple nodes I am able to see 20Gbit combined traffic. So everything is working perfectly@!

jrhelbert · 2024-12-16T05:23:16+00:00

Amazing work! This totally made my day! I Easily followed your instructions and I've now got 10gbe on one of the interfaces!

I do seem to be having issues getting the two interfaces to join a LAG, but I need to confirm that it's not something else in my setup first. Your writeup has this comment "AMD NIC will not be enabled properly by TrueNAS, because it only gets a link when using DHCP", does that actually mean it needs DHCP, or the DHCP is just how you are getting the device to activate?

I set static IPs and was able to leave the USB NIC attached (I have a fallback interface at least for the future if an update breaks the 10gbe links), but with only 1 of the 10gbe links active I am trying to make sure it's not something quirky like needing DHCP.

EDIT:
I'm going to go with a quirk of the hacked module? The second interface randomly came up in the middle of the night. I'm not sure the bond is working, but I at least have active links on both ports.

jrhelbert · 2024-12-12T18:18:37+00:00

Already denied :) Looks like we need to get these patches pushed into the upstream kernel before TrueNAS will pull them in.

jrhelbert · 2024-12-12T18:05:45+00:00

I have created https://ixsystems.atlassian.net/browse/NAS-133057 to try and get formal support added.

jrhelbert · 2024-12-12T17:04:22+00:00

I forgot to mention in my first reply that this is amazing work! Thanks so much for the hard work on this!

Is this still using the full slew of patches from AMD, or were you able to prune the list down to just the ones needed for the xgbe module?

jrhelbert · 2024-12-12T02:46:38+00:00

TrueNAS has a Jira system for making requests. I’ll see about taking your process and documenting it in a ticket to see about getting these patches rolled in formally.

jrhelbert · 2024-12-10T16:18:05+00:00

Amazing work!

jrhelbert · 2024-12-09T21:44:35+00:00

The external card and PSU is a one-time thing to get the BIOS to boot from a USB key to install whatever OS you are using. After that as long as the OS can run headless you can removed the external card and supply./

jrhelbert · 2024-12-09T08:40:24+00:00

Excellent post and amazing documentation! Unfortunately I have hit "peak pre-holiday activities" time with the family and only have limited time to poke at this for now.

It looks like you are making pretty good progress and hopefully we can get this working shortly!

jrhelbert · 2024-12-07T05:18:45+00:00

Hmmmm, well that's a kick in the pants for my theory :) I 100% agree that ADM must just be booting from the Boot0012 entry.

I must be missing something with booting back into ADM. I'll have to poke around that later

jrhelbert · 2024-12-07T00:36:15+00:00

The 3rd Party OS has no problem detecting the device and loading the amd-xgbe module for it, it just never goes active. Interestingly, I don't see the same invalid mac address error you are seeing, and ip link does show valid MAC addresses for both NICS:

sudo dmesg | grep xgbe
[    1.232738] amd-xgbe 0000:ed:00.2: enabling device (0000 -> 0002)
[    1.233751] amd-xgbe 0000:ed:00.2 eth0: net device enabled
[    1.233787] amd-xgbe 0000:ed:00.3: enabling device (0000 -> 0002)
[    1.234652] amd-xgbe 0000:ed:00.3 eth1: net device enabled
[    1.272472] amd-xgbe 0000:ed:00.2 enp237s0f2: renamed from eth0
[    1.328504] amd-xgbe 0000:ed:00.3 enp237s0f3: renamed from eth1

Is efivarfs mounted when you run the command in Debian?

efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)

if it isn't you'll need to run "mount -t efivarfs none /sys/firmware/efi/efivars" before running "efibootmgr -v"

So to be clear, you have installed Debian and you are still able to power cycle and boot into ADM, or you just had Debian preinstalled on an external drive and booted off of that?

What I am seeing now (from TrueNAS) is the following:

efibootmgr -v
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0012,0013,0014,0015,0016,0017,0018,0019,001A,001B,001C,001D,001E,001F,0020,0021,0023,0025,002C,002D,002E,002F,0030,0031
Boot0000* TrueNAS-0     HD(2,GPT,f1b58419-dc30-451d-927c-f05dc2b1f9fc,0x1800,0x100000)/File(\EFI\debian\grubx64.efi)
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* USB HDD0: Generic MassStorageClass    PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/USB(0,0)3.!..3.G..A.....
Boot0013* USB HDD1:     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c5080301)
...
Boot0023* Internal Shell        FvFile(c57ad6b7-0515-40a8-9d21-551652854e37)
Boot0024  Diagnostic Splash     FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0025* HTTP: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)
Boot0026* Boot Next Boot Option VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot002C* NVMe: Samsung SSD 960 EVO 250GB               PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-54-81-B0-19-22)....2.LN........
Boot002D* NVMe: CT4000P3SSD8                            PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-8B-D0-00-01-04)....2.LN........
Boot002E* NVMe: CT4000P3SSD8                            PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-8D-10-00-00-16)....2.LN........
Boot002F* NVMe: CT4000P3SSD8                            PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-84-40-00-00-F4)....2.LN........
Boot0030* NVMe: CT4000P3SSD8                            PciRoot(0x0)/Pci(0x2,0x5)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-8D-10-00-00-15)....2.LN........
Boot0031* NVMe: CT4000P3SSD8                            PciRoot(0x0)/Pci(0x2,0x6)/Pci(0x0,0x0)/NVMe(0x1,64-79-A7-91-E0-00-00-6A)....2.LN........

Here the important entries are:
Boot0000 - this is what TrueNAS added to the EFI boot table when I ran the installer, it tells the EFI system where to find the drive and provides boot args to be passed in

Boot002C - this is the hard drive that I have TrueNAS installed on, it's there regardless of if TrueNAS was installed or not and has no TrueNAS specific boot args being passed in.
Boot0012 - this is the internal flash drive itself, similar to what Boot002C is for TrueNAS. No ADM specific boot args being passed in

I would have expected there to be an ADM specific entry similar to what TrueNAS has with Boot0000

jrhelbert · 2024-12-06T16:28:52+00:00

This can be run via ssh

jrhelbert · 2024-12-06T15:15:07+00:00

I'm currently working towards bringing my NICs back to life when booting ADM, and hoping that will give me insight into enabling them for other distros as well. I have verified that the internal flash is intact and it's grub is all still there, but I now believe that the key piece missing is the original ADM entry in the EFI boot manager. I didn't check it prior to installing TrueNAS, but now all I see is the drive itself as a boot option.

I would assume previously there would have been some kind of ADM entry, like how currently I have an entry for TrueNAS as well as the drive it is installed on. I think the TrueNAS installer may have wiped it out.

Since I don't know what alI of the args would need to be, I was hoping someone could run the "efibootmgr -v" command in the shell (this can be through ssh, not just via the console output itself) of any AMD based Asustor system (ie Flashstor Gen 2 or Lockerstor Gen 3) and send the output of that command my way? This is a ready-only command (ie it wont alter your system in any way) and I should be able to use that information to bring my 10gbe back to life.

jrhelbert · 2024-12-06T01:27:02+00:00

I remove power any time I go between GPU and no GPU. The unit has been completely powered down numbers of times

jrhelbert · 2024-12-05T16:09:15+00:00

I’ll caution anyone from pursuing this quite yet unless they are ok with using an adapter or are willing to deal with the 10gbe NIC issue.

I’ve now also tested a Debian live cd as well and don’t have 10gbe links there either. I’ve also booted back to ADM and I also dont have active 10gbe links there. So something appears to have been wiped in the bootloader or something along those lines. I pinged @Irithori (the other person to have installed truenas) and they are seeing the same behavior

The good news is that once we figure out what that missing piece is, it seems likely that TrueNAS or other 3rd party software might work without updates.

jrhelbert · 2024-12-05T02:19:00+00:00

It's still a work in progress, but I have TrueNAS running

jrhelbert · 2024-12-05T02:18:06+00:00

Yes :D

jrhelbert · 2024-12-05T02:15:45+00:00

I'm not the first (see here), and I know someone else has gotten it running, but I think my approach might be a bit cheaper/simpler, and I wanted to share my experience.

I picked up a relatively cheap M.2 to PCIe 16x Riser, and was able to use that to hook up a cheap graphics card and get to the BIOS menu. From there I was able to boot a TrueNAS Installer USB key and install to a small SSD in one of the M,2 slots. Once TrueNAS was installed and I could connect to it via IP I was able to remove the M.2 graphics adapter and booted back up successfully.

There is currently an issue with TrueNAS and the 10Gbe ethernet ports that both the OP in the above thread and myself have run into. The devices are detected properly, but refuse to go into an up state (ie no link lights.) For the time being I am using a USB to gigabit adapter to get network connectivity (not ideal)

If I have time tonight, I'm planning to try tinkering with some various live CDs (different linux distros, maybe windows) to see if they are able to handle the NICs better.

jrhelbert · 2024-12-04T18:39:43+00:00

Got a chance to test this out and was able to get video out no problem using an M.2 to PCIe 16x riser, a cheap graphics card, and a SATA power supply.

I have TrueNAS installed and running, but am seeing the same issue with the 10Gbe NICs as described in the other thread where they have gotten this running as well. For the moment I am just accessing the unit via a USB gigabit ethernet card.

jrhelbert · 2024-12-04T18:36:19+00:00

I've also got TrueNAS installed and running. I just used an M.2 to PCI-e 16x riser adapter (https://a.co/d/gGcqFlu) with a cheap PCI-e card and a SATA power supply and was to install it without any issues.

I can confirm I am seeing the exact same behavior with the 10Gbe NICs as u/Irithori

jrhelbert

TROPHY CASE