June 29Jun 29 On 5/27/2026 at 4:45 AM, DelDadam said:Hi,We have two UGREEN DXP4800 PLUS's here, but as far as I know your DXP4800 uses the same ITE IT8613E Super IO chip as ours do. And unfortunately, ich77's ITE IT87 Driver plugin does not support this variant of the chip. At least this was reported by the terminal commands installed by the plugin when I last time attempted to use the plugin.AFAIK the only way to control the fan of your NAS is possible only via its BIOS settings. Look for the ADVANCED panel in the BIOS, and the Hardware Monitoring sub-menu. There you'll find various settings like Fan PWM Slope, Fan Start PWM and Fan Start Temperature Limit. You need to play with/change these 3 settings only. In our NAS these have the following default values:Fan PWM Slope: 35 (how fast the PWM value of the fan increased if temp changes by 1C)Fan Start PWM: 51 (base PWM value of the fan, in our case this corresponded to approx. 600 RPM)Fan Start Temperature Limit: 25 (that is obvious: below this temp the fan does not run)We've changed the above defaults to these values:Fan PWM Slope: 50Fan Start PWM: 62Fan Start Temperature Limit: 20Since the change of these settings the temperature of the processor and the motherboard decreased by ~8-10 C, while the HDD's temp went down by ~5-6 C when not idle (at room temp of 26C).Hope it helps.thanks for the detailed explanation, I run DXP4800 PRO (which uses the same Super IO ITE8613E) and saw this comment which upset me initially. But I then decided to try the ITE IT87 DRIVER and FanCtrl Plus, turns out, both work great in my setup. Not only I can see the new dashboard panel with the fan speed and reason for it, FanCtrl actually does control the fan. I first tried the "fan discovery" which was able to max-spin both the CPU fan and Rear fan (Noctua in my case) and then I tried changing the Fan speed percentage to see if those would make a change and they did.
July 1Jul 1 Hi ich777 — I think I've hit a packaging/registration issue with the AMD Vendor Reset plugin on my kernel version. I've narrowed it down fairly far before posting; details and exact command output below.SystemUnraid 7.3.1Kernel: 6.18.33-UnraidBoard/CPU: ASRock Rack ROMED8-2T / EPYC 7543PGPU (passthrough target): AMD reference RX 6900 XT, Navi 21, all four functions stubbed to vfio-pci from boot via vfio-pci.cfgHost boots on onboard ASPEED VGA; video=efifb:off on the append line so the host never touches the 6900 XT.Symptom The plugin installs and the module loads (hook reports installed), but the reset method never becomes device_specific — it stays bus, and writing device_specific fails with write error: Invalid argument. This happens even with the card idle, no VM running, in a clean vfio-bound state.Exact outputKernel and module (vermagic matches the running kernel):# uname -r 6.18.33-Unraid # modinfo vendor_reset filename: /lib/modules/6.18.33-Unraid/updates/vendor-reset.ko.xz version: 0.1.1 author: Adam Madsen <[email protected]> author: Geoffrey McRae <[email protected]> license: GPL v2 srcversion: 9DB935EFAD3315A519FE253 depends: name: vendor_reset retpoline: Y vermagic: 6.18.33-Unraid SMP preempt mod_unload parm: install_hook:bool Package folder matches the kernel:# ls /boot/config/plugins/amd-vendor-reset/packages/ 6.18.33/ Hook reports installed:# dmesg | grep -i vendor [ 67.711636] vendor_reset_hook: installed Reset method stays bus and rejects device_specific:# cat /sys/bus/pci/devices/0000:07:00.0/reset_method bus # echo device_specific > /sys/bus/pci/devices/0000:07:00.0/reset_method bash: echo: write error: Invalid argument GPU (all four functions, vfio-pci bound):# lspci -nnk -s 07:00. 07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT [1002:0e3a] Kernel driver in use: vfio-pci Kernel modules: amdgpu 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28] Kernel driver in use: vfio-pci 07:00.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:73a6] Kernel driver in use: vfio-pci 07:00.3 Serial bus controller [0c80]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 USB [1002:73a4] Kernel driver in use: vfio-pci Boot command line:# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot video=efifb:off What I've ruled outWrong/mismatched module: vermagic is 6.18.33-Unraid, matching the running kernel exactly; package folder is 6.18.33/.vfio-lock / timing: I unbound 07:00.0 from vfio-pci and the write still failed with Invalid argument; rebound it to vfio-pci (clean state) and it still fails. Same result in both states, card idle, no VM.Unsupported card: Navi 21 1002:73bf is reported working with vendor-reset elsewhere (same device IDs).Conflicting local config: removed earlier manual go-file reset_method write and a modprobe.d softdep; go is back to stock, only zfs.conf remains in modprobe.d.My read (could be wrong) The hook installs, but the module's device_specific handler does not appear to register into the kernel PCI reset infrastructure on this kernel — the kernel rejects device_specific as invalid for the device even when idle and regardless of bind state. This looks like it could be a build/registration issue with the pre-built package for 6.18.33-Unraid, rather than a config problem on my end.Question Is the pre-built vendor-reset package for 6.18.33-Unraid known-good, or might it need a rebuild against this kernel? Anything else I can check to confirm whether the handler is registering? Happy to provide full diagnostics or test a rebuilt package. unraid-diagnostics-20260630-2029.zip
July 1Jul 1 Hello All, I am in need of some assistance with the UGreen LED driver. I just purchased the DXP8800 Plus and installed Uraid on it. I downloaded the ugreen LED driver from ich777 and followed the instructions (At least I think) but I can only get the Network, HD1 and HD3 lights working. I have tried leaving it as default, (ata), serial and adding in my serial numbers in order (ST26000NM001C-XXXXXX_XXXXXXXX) with a space in between as well as the hctl option with (0:0:0:0 1:0:0:0 etc) but nothing seems to change after rebooting. I have been able to successfully change the LED colors but nothing else. When the unit firsts boots, it does light up all of the hard drive LED's in white for a brief moment but then turns off and only shows the network, 1st and 3rd again. What am I missing here? The model is listed as compatible but for the life of me, can't find the correct configuration. Below is a screenshot of the hard drives and current layout. Disk1 is parity (currently building), Disk2 is a future parity so it is empty, Disk3, 4 and 5 are 26TB drives in the pool. Any help would be greatly appreciated.
July 5Jul 5 On 7/1/2026 at 4:20 PM, Bigsease30 said:Hello All,I am in need of some assistance with the UGreen LED driver. I just purchased the DXP8800 Plus and installed Uraid on it. I downloaded the ugreen LED driver from ich777 and followed the instructions (At least I think) but I can only get the Network, HD1 and HD3 lights working. I have tried leaving it as default, (ata), serial and adding in my serial numbers in order (ST26000NM001C-XXXXXX_XXXXXXXX) with a space in between as well as the hctl option with (0:0:0:0 1:0:0:0 etc) but nothing seems to change after rebooting. I have been able to successfully change the LED colors but nothing else. When the unit firsts boots, it does light up all of the hard drive LED's in white for a brief moment but then turns off and only shows the network, 1st and 3rd again. What am I missing here? The model is listed as compatible but for the life of me, can't find the correct configuration. Below is a screenshot of the hard drives and current layout. Disk1 is parity (currently building), Disk2 is a future parity so it is empty, Disk3, 4 and 5 are 26TB drives in the pool. Any help would be greatly appreciated. Does anyone know anything about this driver and how to make it work? Any help would be appreciated.
July 7Jul 7 Subject/context: IT8689E rev 2 — PWM writes accepted but have no effect (fix available in upstream PR #114)Hi ich777, first of all thanks for all your driver plugins!System: Unraid 7.3.1 · Gigabyte B760I AORUS PRO DDR4 · IT8689E revision 2 (detected via your IT87 plugin: it87: Found IT8689E chip at 0xa40 [MMIO at 0x00000000fc000000], revision 2)Problem: Sensors and fan RPM readings work perfectly, but manual PWM control has no effect:echo 1 > pwmN_enable succeeds and persistsecho <duty> > pwmN succeeds and persists (value reads back correctly)Fan RPM never changes — on any of the 5 channelsTested with mmio=on (default) and mmio=off ignore_resource_conflict=1 — same resultBIOS Smart Fan curves set to flat 40% per the CoolerControl docs workaround — the EC respects the flat curve (fans dropped from 100% to 40%), but sysfs writes still have no effect on top of itThis is exactly the symptom tracked in frankcrawford/it87 issue #96 (IT8689E: PWM writes accepted, zero effect, works fine on Windows via LibreHardwareMonitor).The good news: there is now a minimal tested fix upstream — PR #114 (https://github.com/frankcrawford/it87/pull/114). Root cause: on these FEAT_BRIDGE_MMIO chips the internal "vector" fan controller only releases the channel in manual mode when all temp-map-select bits are set; LibreHardwareMonitor writes 0x7f to the base PWM control register on Windows, which is why it works there. The PR is a one-line change in set_pwm_enable() and a reviewer confirmed this method is specifically needed on the IT8689 (the IT8696 is unaffected).Request: would it be possible to get a test build of the IT87 plugin with the PR #114 patch applied (kernel 6.18.33-Unraid / Unraid 7.3.1)? Happy to test and report back — I have a reproducible setup and can validate manual control + enable=2 auto-restore on all channels.Thanks a lot!
July 9Jul 9 On 6/29/2026 at 11:03 PM, meandnano said:thanks for the detailed explanation, I run DXP4800 PRO (which uses the same Super IO ITE8613E) and saw this comment which upset me initially. But I then decided to try the ITE IT87 DRIVER and FanCtrl Plus, turns out, both work great in my setup. Not only I can see the new dashboard panel with the fan speed and reason for it, FanCtrl actually does control the fan. I first tried the "fan discovery" which was able to max-spin both the CPU fan and Rear fan (Noctua in my case) and then I tried changing the Fan speed percentage to see if those would make a change and they did.That is a fun fan-control (sorry :-)) method, but at least it is also a great news. I've also tried it, and really, it works. However, I have no idea why the terminal commands installed by the driver reported me initially that this Super IO chip is unsupported, which led me to the conclusion that it is not even worth to try it out. Anyway, thanks for the feedback.
July 13Jul 13 On 7/1/2026 at 4:20 PM, Bigsease30 said:Hello All,I am in need of some assistance with the UGreen LED driver. I just purchased the DXP8800 Plus and installed Uraid on it. I downloaded the ugreen LED driver from ich777 and followed the instructions (At least I think) but I can only get the Network, HD1 and HD3 lights working. I have tried leaving it as default, (ata), serial and adding in my serial numbers in order (ST26000NM001C-XXXXXX_XXXXXXXX) with a space in between as well as the hctl option with (0:0:0:0 1:0:0:0 etc) but nothing seems to change after rebooting. I have been able to successfully change the LED colors but nothing else. When the unit firsts boots, it does light up all of the hard drive LED's in white for a brief moment but then turns off and only shows the network, 1st and 3rd again. What am I missing here? The model is listed as compatible but for the life of me, can't find the correct configuration. Below is a screenshot of the hard drives and current layout. Disk1 is parity (currently building), Disk2 is a future parity so it is empty, Disk3, 4 and 5 are 26TB drives in the pool. Any help would be greatly appreciated. Is the ugreen LED driver supported on this forum?
July 13Jul 13 I just click update to 7.3.2 and this notifications shown up, what should i do? But when i check for update in plugins menu, IT87 Driver is up-to date, and the only one that not update is just Community Applications (2026.05.15gh) which upgradeable to 2026.07.12 b
July 13Jul 13 33 minutes ago, anokata said:I just click update to 7.3.2 and this notifications shown up, what should i do? But when i check for update in plugins menu, IT87 Driver is up-to date, and the only one that not update is just Community Applications (2026.05.15gh) which upgradeable to 2026.07.12 bI just ran into the same problem when I was trying to update to 7.3.2. After the error, I have canceled the update process (for now). Hope to get some advice here.
July 14Jul 14 It seems that several (maybe all?) of the plugins of user ich777 are affected. At least I found three different threads, where users are all facing the same issue.Unfortunately, it seems that user ich777 wasn't online here for a couple of weeks.Maybe @JorgeB can give some advice? Update to 7.3.2 is strongly recommended, but we can't update because of several plugins aren't ready.
July 14Jul 14 3 hours ago, JayDee73 said:Update to 7.3.2 is strongly recommended, but we can't update because of several plugins aren't ready.I just did a quick test and it appears to be working, maybe a temp/load issue? Try again.
July 14Jul 14 5 hours ago, JorgeB said:I just did a quick test and it appears to be working, maybe a temp/load issue? Try again.You may be right with the temp issue. Now it's also working for me. Nevertheless....now I'm a little hesitant with rebooting...😬 Because I canceled the update process before rebooting during the first try (because of the plugin error) and now, when I start the 7.3.2-update process again, there simply isn't any kind of plugin update helper tool saying anything. No "everything done, please reboot to install 7.3.2" or stuff like that.
July 14Jul 14 2 hours ago, JayDee73 said:Nevertheless....now I'm a little hesitant with rebooting...😬That should always be OK, worst case, you should get the plugin error again if it still fails; these latest errors were likely due to temporary GitHub issues; if they happen again, just wait an hour or so and retry
July 14Jul 14 30 minutes ago, JorgeB said:That should always be OK, worst case, you should get the plugin error again if it still fails; these latest errors were likely due to temporary GitHub issues; if they happen again, just wait an hour or so and retryYou were right (as usual... 😄). I just rebooted and updated to 7.3.2 without any problems. Thanks for your support.
Monday at 06:00 AM4 days Guten Morgen,Ich versuche den "QNAP-EC" (für meinen TVS-863a) zu aktivieren. Ich denke er wäre kompertibel mit den "TS-464".Habe auch schon etliches gemacht, wie Dateien erstellt (laut Githup von Ich777 - https://github.com/ich777/unraid-qnapec/blob/master/TS464.md) Nur wo befindet sich der QNAP-EC-Kernel, den ich anpassen soll?Die Befehler habe ich ins Terminal von Unride eingegeben (könnte das als "SSH" bezeichnet sein?)Leider finde ich keinen PWMx in den Ordner "hwmon0-2" nur "Temp1-max" in hwmon0.Wo bekomme ich den QNAP-Kernel her? aus dem DOM-Modul?Good morning,I am trying to activate "QNAP-EC" (for my TVS-863a). I believe it should be compatible with the "TS-464".I have already taken several steps, such as creating files (following the GitHub guide by Ich777 – https://github.com/ich777/unraid-qnapec/blob/master/TS464.md). However, where is the QNAP-EC kernel located that I am supposed to modify?I entered the commands into the Unraid terminal (is this what is referred to as "SSH"?).Unfortunately, I cannot find any "PWMx" entries in the "hwmon0-2" folders; there is only "Temp1-max" in "hwmon0".Where do I get the QNAP kernel from? Is it from the DOM module?Klaus Edited Monday at 07:15 AM4 days by KSMBln
Tuesday at 04:37 AM3 days 22 hours ago, KSMBln said:I am trying to activate "QNAP-EC" (for my TVS-863a). I believe it should be compatible with the "TS-464".as far as i see, different platforms, how you come to the conclusion its compatible ?
Tuesday at 04:49 AM3 days Ob ein oder zwei Lüfter sollte nur durch die Nummer der Lüfter angezeigt werden. Auch stehen viele QNAP als Komatibel drin, Ich weiß nur nicht welcher Chipsatz die Lüfter steuert. Sollte aber bestimmt von der Steuerung gleich sein. Aus meiner Sicht wird eventuell der Chipsatz aktuellisiert aber die Befehle nicht. Wäre zu großer Aufwand in der Programmierung der QNAP-Software.....The distinction between one or two fans should simply be indicated by the fan count. Many QNAP models are listed as compatible, though I don't know exactly which chipset controls the fans; however, the control mechanism is likely the same across them. In my view, the chipset might get updated, but the commands don't—updating the QNAP software programming to reflect that would simply be too much effort... Edited Tuesday at 04:50 AM3 days by KSMBln
12 hours ago12 hr When I updated to 7.3.2, I can't install the plugin "it 87 driver", it said like this:Downloading plugin plugin: installing: it87-driver.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks -----------------------Downloading IT87 Drivers!------------------------- ---------This could take some time, please don't close this window!---------- -----------------------Can't download IT87 Drivers----------------------- plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed
10 hours ago10 hr When I updated to 7.3.2, I can't install the plugin "it 87 driver", it said like this:Downloading plugin plugin: installing: it87-driver.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks -----------------------Downloading IT87 Drivers!------------------------- ---------This could take some time, please don't close this window!---------- -----------------------Can't download IT87 Drivers----------------------- plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed
10 hours ago10 hr I just fixed this issue using the steps Codex gave me.---title: Manual Pre-stage Install for the Unraid it87 Driver Plugin (Method A)description: Offline workaround for the ITE IT87 Driver plugin on Unraid 7.3.x / kernel 6.18.x when the GitHub API lookup inside the plugin fails.tags: [unraid, it87, plugin, driver, fan-control, sensors]---# Manual Pre-stage Install for the Unraid it87 Driver Plugin (Method A)> When to use this: after upgrading Unraid, installing the **ITE IT87 Driver**> plugin from the WebGUI fails with> `-----------------------Can't download IT87 Drivers-----------------------`> and never completes.---## 1. Background- **Unraid 7.3.2** (released 2026-07-08) ships with the **Linux 6.18.38-Unraid** kernel.- ich777's `ITE IT87 Driver` plugin (repo: `ich777/unraid-it87-driver`) is packaged per kernel version. For `6.18.38-Unraid` the matching `.txz` is `it87-20260416-6.18.38-Unraid-1.txz` (published 2026-07-07).- The plugin's installer resolves the asset name through the GitHub API: ```bash LAT_PACKAGE="$(wget -qO- https://api.github.com/repos/ich777/unraid-it87-driver/releases/tags/${KERNEL_V} | jq ...)" ``` When that request is rate-limited (60 req/h for an unauthenticated IP) or returns empty, `LAT_PACKAGE` ends up empty, the subsequent `wget` against a malformed URL fails, and the installer exits with `Can't download IT87 Drivers`.- Pre-placing the matching `.txz` (and `.md5`) into the plugin's `packages/` cache causes the script to skip the API call entirely and succeed locally.---## 2. Prerequisites### 2.1 Confirm the running kernelSSH into the Unraid server as `root`:```bashuname -r```Expected output:```6.18.38-Unraid```Note the numeric part (the suffix after the last `-`), e.g. `6.18.38`.### 2.2 Download the matching driver packageIn a local browser, open:<https://github.com/ich777/unraid-it87-driver/releases>Find the release tag matching `uname -r` (e.g. `6.18.38-Unraid`) and downloadboth files:| File | Purpose ||---|---|| `it87-20260416-6.18.38-Unraid-1.txz` | Kernel module package || `it87-20260416-6.18.38-Unraid-1.txz.md5` | Checksum |> ⚠️ The `20260416` segment is the upstream driver source date and will change> whenever ich777 repackages. Always use the exact filename shown on the> GitHub release page.Place both files in a temporary directory (e.g. `D:\it87\` on Windows).---## 3. Step-by-step### 3.1 Upload the files to the Unraid hostEither:**Option A: scp** (from a local PowerShell / terminal):```powershellscp D:\it87\it87-20260416-6.18.38-Unraid-1.txz* root@<UNRAID_IP>:/tmp/```**Option B: USB drive / SMB share**Copy the files into a writable directory on the server (for example`/config/plugins/.tmp/`), then `cd` there in SSH.### 3.2 Stage them into the plugin cache```bashKVER=$(uname -r | cut -d- -f1) # e.g. 6.18.38echo "$KVER"mkdir -p /boot/config/plugins/it87-driver/packages/$KVERcp /tmp/it87-*-${KVER}-Unraid-1.txz* /boot/config/plugins/it87-driver/packages/$KVER/ls -l /boot/config/plugins/it87-driver/packages/$KVER/```You should see both the `.txz` and `.txz.md5` files.### 3.3 Finish the install from the WebGUI1. Open **Plugins** → **Available Plugins**.2. Find **ITE IT87 Driver** (author: ich777) and click **Install**.3. In the install log you should see: ``` -----------------------IT87 Drivers found locally------------------------ ----------------Installation of IT87 Drivers successful------------------ ```4. Reboot the server (Settings → Reboot, or `reboot` from the console) so the `it87` module loads at boot.---## 4. VerificationAfter the reboot, SSH back in and run:```bash# 4.1 Module loaded?lsmod | grep it87# Expected: it87 <size> 0# 4.2 mmio parameter present? (confirms it's the ich777 patched module, not the kernel built-in)modinfo it87 | grep -E "mmio|filename"# 4.3 Chips visible to libsensors?sensors | grep -iE "it|k10|cpu"# Expected: it87xxx-isa-xxxx / k10temp-pci-00xx entries# 4.4 Dynamix System Temperature sees the devices?# WebGUI → Settings → Dynamix System Temperature → should list it87 / CPU```All four checks passing means the install is good.---## 5. Advanced: fully manual install (when the plugin refuses to install at all)If the WebGUI plugin install keeps failing even after staging, you can installthe module without the plugin wrapper:```bashcd /tmpwget https://github.com/ich777/unraid-it87-driver/releases/download/<KERNEL_V>/it87-<...>-<KERNEL_V>-1.txzinstallpkg it87-<...>-<KERNEL_V>-1.txzdepmod -amodprobe it87 ignore_resource_conflict=1sensors # verify```> This path doesn't write to `/usr/local/emhttp/plugins/it87-driver/`, so the> Dynamix System Temperature and FanCtrl Plus UIs may not show plugin metadata,> but `sensors` and `sysfs` (`/sys/devices/platform/it87.*/hwmon/*/pwm*`) work> normally and can be driven from external scripts or FanCtrl Plus.---## 6. One-click scriptA ready-to-run helper is provided in `install-it87.sh`. It performs the entirepre-stage (kernel detection → API lookup → fallback scraping → md5 verify →copy into the cache directory) and accepts three flags:| Flag | Effect ||---|---|| *(none)* | Pre-stage only. Safe to re-run. || `--install` | Also `installpkg` + `depmod` + `modprobe it87` immediately. || `--force` | Overwrite files already in the cache directory. || `--uninstall` | Remove the pre-staged cache for the current kernel. |Example:```bashchmod +x install-it87.sh./install-it87.sh```After it finishes, complete the install through the WebGUI as in §3.3.---## 7. Troubleshooting| Symptom | Likely cause | Fix ||---|---|---|| Still `Can't download IT87 Drivers` after staging | File name / directory doesn't match kernel | Verify `uname -r` and `$KVER` line up; double-check the package filename || `sensors` shows nothing for ITE | BIOS has SIO Hardware Monitor disabled | Enable *SIO Hardware Monitor* / *EC Support* in BIOS || Temperatures read correctly but PWM writes have no effect (e.g. IT8689E) | Board EC ignores sysfs writes | See [ich777 support thread #92865](https://forums.unraid.net/topic/92865-support-ich777-amd-vendor-reset-coraltpu-hpsahba/) — frankcrawford/it87 PR #114 || Plugin breaks again after a kernel upgrade | No cache for the new `KVER` | Re-run this Method A, or wait for ich777 to publish a release for the new kernel |---## 8. References- Plugin repo: <https://github.com/ich777/unraid-it87-driver>- Upstream driver: <https://github.com/frankcrawford/it87>- ich777 support thread: <https://forums.unraid.net/topic/92865-support-ich777-amd-vendor-reset-coraltpu-hpsahba/>- Unraid 7.3.2 release notes: <https://docs.unraid.net/unraid-os/release-notes/7.3.2/>- Related plugins: Dynamix System Temperature, FanCtrl Plus
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.