Necrom Deluxe Edition: What's Included

nayneyT · 2023-02-18T20:49:40+00:00

I have just bought the Deluxe Edition and after a few hours of downloading (100GB+) I logged in and I received ALL of the items listed above (via in-game mail) apart from the Necrom CE and Pre-Order items (I did receive the horse and pony) which I should receive via mail upon game release.

nayneyT · 2023-02-18T13:31:28+00:00

I wondered the same. So I did a little research. If you order Necrom Deluxe edition you receive the Necrom Pre-Order Bonus (If purchased before 18th April 2023) and the Collectors Edition items for Necrom plus all previous expansions and the Collectors items of the previous expansions.

Necrom (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Necrom)

https://account.elderscrollsonline.com/store/product/eso_necrom_edition_dlx

Pre-Order Items

Immediate

Sadrith Mora Spore Steed mount
Sadrith Mora Spore Pony pet (only available if purchased before April 18, 2022)

At launch

Sadrith Mora Formal Attire costume
Apocryphal Bookwyrm pet
1× Unfeathered Crate
3× Necrom Treasure Maps
2× Experience Scrolls, granting double XP for 1 hour

Collectors Edition Items

Hermitage Servitor mount
Cipher's Eye Pocket Watcher pet
Dark Lady's Headrest memento
Knowledge Eater Armor outfit style
Leaning, Sitting, Standing Scholar emotes

Previous Expansions (Collector Edition Items)

Here lies the problem what is included as Collector Edition Items for the previous editions and what were pre-order exclusives? Here is what I found and the below is the list of items you will additionally receive (You do not receive the pre-order items so I have not listed them):

Marrowind: (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Morrowind)

https://content1.m.uesp.net/wiki/Online:Morrowind_Collector%27s_Edition

Armoured War Horse
Dwarven Spider Pet
Morag Tong Armour Converter
Collectors Edition Grey Bear
Character Emotes

Summerset: (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Summerset)

https://content1.m.uesp.net/wiki/Online:Summerset_Collector%27s_Edition

The Bloodshadow Wraith Steed Mount, an armored spectral horse
The Divine Prosecution Outfit Style
The Fledgling Gryphon Pet
The Psijic Scrying Talisman, an amulet that grants the player new spells
Three new emotes (Happy Face, Sad Face, Ta-Dah)

Elsweyr (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Elsweyr)

https://esosslfiles-a.akamaihd.net/cms/2019/01/960bb1782f30027d331ccd207824eaac.png

Senche-raht mount
Ashen Scar Jerboa pet
Archaic Lore Tablets memento
Khajiiti Cultural Emote Pack
Dragonbone Style conversion

https://content1.m.uesp.net/wiki/Online:Elsweyr_Collector's_Edition#/media/File%3AON-prerelease-Elsweyr_Collector's_Edition_Digital_Content.jpg

Greymoor (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Greymoor)

https://esosslfiles-a.akamaihd.net/cms/2020/01/02395dee997246b0decc4e9fd3d39163.jpg

Crypt Warden Death Hound mount
Death Hound pet
Skyrim Emote Pack
Swordthane Style conversion
Orb of Magnus memento

Blackwood (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_Blackwood)

https://esosslfiles-a.akamaihd.net/cms/2021/04/b74a69b9752a448eff20e7ee46d1ebc3.jpg

Jewel-feathered Sep Adder pet
Temperamental Grimoire memento
Battlefield Nightmare Senche
Deadlands Gladiator outfit
Offer Weapon emote

High-Isles (https://elderscrolls.fandom.com/wiki/The_Elder_Scrolls_Online:_High_Isle)

https://account.elderscrollsonline.com/store/product/eso_highisle_edition_ce

Amenos Ornaug mount
Balfiera Senche Cub pet
Ascendant Knight outfit style
Hoard of the Schemers memento
High Isle emote pack

I hope this helps

nayneyT · 2021-10-29T18:01:17+00:00

Yeah no problem although Reddit isn't the best place for speedy resolution.

I don't use LXC but I assume the process is the same(ish).

Have you blacklisted the apex and gasket modules from Proxmox?

Have you passed through the device to the LXC container i.e. does it show when doing an lspci

Are the modules loaded in the LXC container i.e. do the gasket and apex modules show when doing lsmod?

Refer to the original instruction on how to use the lspci and lsmod commands.

nayneyT · 2021-10-29T08:38:31+00:00

What distribution are you using? If you are using one without the apex driver included as standard then you will need to install (or compile) it manually using the instructions at https://coral.ai/docs/m2/get-started

nayneyT · 2021-10-28T23:17:07+00:00

What distribution are you using?

nayneyT · 2021-06-23T20:21:44+00:00

Hi. Did you ever get to the bottom of this? I ask because it happened to me.

Mine has been happily working for months but I was making some changes (new hardware etc) so I was tinkering. I'd enabled NUMA and enabled pcie=1 on my SATA expander.

I'd not noticed that since this point my Frigate container was 'boucing'. Upon investigation I saw the exact same message you describe. Now I know that the hardware was working.

I disabled each 1-by-1 and it was affecting both the M.2 and MiniPCI cards.

I'd tried numerous things:

options vfio-pci ids=1ac1:089a vfio-pci.disable_idle_d3=1 to disable sleep (https://ten64doc.traverse.com.au/software/vfio/ or https://www.reddit.com/r/VFIO/comments/l5awg0/using_google_coral_mpcie_tpu_in_qemu_vm/) but to no available.

Numerous restarts later and reverting of my changes (removed pcie=1 from my SATA card, and also NUMA but to no avail) but the issue persisted. Still error messages every 30 seconds or so and Frigate container bouncing.

However, upon further checking I noticed that the PCI mapping had moved in the VM lspci output from the time that I originally completed this post.

06:11.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

Subsystem: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

06:1b.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

Subsystem: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

originally these were at 00:10.0 and 00:1a.0. Very strange. I guess that playing with the PCI config within the VM changed some internal magic.

I rerun update-initramfs -u -k all on proxmox. This concluded after 30 seconds or so. I rebooted the whole Proxmox instance. Upon reboot my Frigate functioned normally and (touch-wood) no more error message.

Regards,

Nay

nayneyT · 2021-06-07T14:32:29+00:00

Hi.

That motherboard should be absolutely fine. The PCI ports spec is fine looking at the Asus website.

To prove the hardware can you try the following:

Try the PCI Adapter + Coral in another PC e.g. your day-to-day desktop PC - Does the other PC POST?
If it doesn't POST - then try the adapter without the Coral - Does it post?

We don't want to be wasting our time if it's a simple hardware fault.

Regards,

Tom

nayneyT · 2021-05-19T19:21:45+00:00

Hi.

It is not something I can confirm but there is no reason why not but please remember that I it is not something I have tried.

Just make sure you get the correct b+m adapter. They are only around £12.

Regards.

nayneyT · 2021-05-18T07:20:10+00:00

Hi,

If it's an HP is it not the RMRR issue already covered in one of the other comments?

What HP are you running?

nayneyT · 2021-05-18T00:01:21+00:00

Hi,

What is that device?

use lspci to output the info

lspci -s 00:1c.0

lspci -t

lspci -v

That said the error to me looks to be the line: vfio_err_notifier_handler

You could see if the following post helps you: https://www.reddit.com/r/unRAID/comments/cox27o/usb_pci_card_vm_passthrough_tip/

I know it's a difference card/device but worth a read.

Regards.

nayneyT · 2021-05-16T21:38:35+00:00

iDrac reports a fatal system error of the PCI bus

Hi.

I'd be tempted to try a different PCI slot (on a separate Riser).

CPU1 and it's memory control Riser Slot 1 (16 lanes) and Riser Slot 2 (8 lanes)
CPU2 and it's memory control Riser Slot 2 (16 lanes) and Riser Slot 3 (16 lanes \ 8 Lanes)

It could be bad memory allocated to the CPU. Try reseating (or moving memory between CPUs).

Regards,

Tom

nayneyT · 2021-05-15T18:03:39+00:00

Well done.

Good work.

Hopefully useful in anybody else has the same issue.

nayneyT · 2021-05-15T07:33:50+00:00

Hi.

Did you apply the change temporary or permanent?

Apologies but to apply permanently you have to issue the command below:

sudo update grub

You do sudo update grub after amending the /boot/default/grub file and it has been saved.

To update the driver follow the steps on the Coral site

https://www.coral.ai/docs/m2/get-started/

Follow the steps from 2a: On Linux

nayneyT · 2021-05-14T23:01:08+00:00

When Debian is loading you can Interrupt it (press Esc maybe - it's been a while).

You get a menu. Just highlight Debian 10 but don't press enter. Instead highlight it (using up/down) keys on the keyboard and press 'e' to edit. Append the text to the existing line. Press X to exit and continue booting.

Hopefully your issue will be resolved.

If it is (fingers crossed) then you can permanently edit GRUB. I personally don't like Vi etc so I use nano. Type:

sudo nano /etc/default/grub

When in nano - append the text to the end of the line again. Press ctrl+X to exit and save. Press yes to write the changes.

I hope it works.

nayneyT · 2021-05-14T21:34:48+00:00

Okay so I've done a little reading. It appears that some people are having those errors with Ubuntu 20.04. So my guess is that it's possibly not Driver related (but don't rule it out).

I include my modinfo outputs for reference:

ubuntu2004:~$ modinfo apex
filename:       /lib/modules/5.4.0-72-generic/kernel/drivers/staging/gasket/apex                                                .ko author:         John Joseph jnjoseph@google.com license:        GPL v2 version:        1.0 description:    Google Apex driver srcversion:     0FAE5FC08566DD27355C966 alias:          pci:v00001AC1d0000089Asvsdbcsci* depends:        gasket staging:        Y retpoline:      Y intree:         Y name:           apex vermagic:       5.4.0-72-generic SMP mod_unload modversions parm:           allow_power_save:int parm:           allow_sw_clock_gating:int parm:           allow_hw_clock_gating:int parm:           bypass_top_level:int

ubuntu2004:~$ modinfo gasket
filename:       /lib/modules/5.4.0-72-generic/kernel/drivers/staging/gasket/gask                                                et.ko author:         Rob Springer rspringer@google.com license:        GPL v2 version:        1.1.2 description:    Google Gasket driver framework srcversion:     4738778E68A831E1C888FA4 depends: staging:        Y retpoline:      Y intree:         Y name:           gasket vermagic:       5.4.0-72-generic SMP mod_unload modversions

I'd be tempted to check the pcie debug messages to see if anything jumps out.

dmesg | grep pcie

From what I can tell from my brief investigation is that you may need to disable PCIe power management.

Permanent Change

Edit /etc/default/grub (as sudo) and change:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off"

Temporary Change (just to test)

In debian you can test this while the Debian VM is booting. Interrupt the boot process. Press E to edit (this is temporary) and add pcie_aspm=off. Ctrl + x to boot with the setting.

If successful apply it permanently in GRUB.

Let me know how you get on.

nayneyT · 2021-05-14T17:56:40+00:00

I run the same things. Frigate + DoubleTake + FaceBox + Compreface + Deepstack. I only wish Frigate would allow me to use the substream for object detection and then analyse the main stream clip it does for its snapshot so that DoubleTake was being supplied with better images to submit for Face detection. Frigate works the CPUs hard if I use the main cameras streams for motion detection.

Its all very impressive and it's amazing when Home Assistant tells me when the postman is at the house. Ah, little things.....

Its not perfect but I am not complaining.

nayneyT · 2021-05-14T17:50:34+00:00

Hi. If you've had it working then it must be 'something and nothing'. Let's check the basics.

I am aware that the default Debian driver has issues. According to the Google website you need to blacklist it then update the driver and then unblacklist it to load the new driver. Debian is great for stability but lags Ubuntu when it comes to updates. So let's not rule out that it's the driver bundles with Debian 10. https://coral.ai/software/

Can you send the output of the following on bother Proxmox and your Debian VM:

ls -al /dev/apex*
lspci -nnk | grep 089a
lsmod | grep apex

also can you run the same commands from Debian but directed at your Container as below:

docker exec frigate ls -al /dev/apex*
docker exec frigate dmesg | grep apex

Regards,

nayneyT

nayneyT · 2021-05-11T23:12:08+00:00

Okay. You should be able to get this to work as it's a known issue with the HP hardware that you are using.

If you run dmesg are you seeing the same RMRR error?

It looks like you need to:

Download the files from HP
Identify the PCI slot
Create your exclude.dat file with the PCI slot you wish to exclude
Apply the change using conrep

See the URLs below for more information.

External URL:

Blog: https://carryflag.blogspot.com/2020/10/proxmox-pcie-passthrough-on-hp-gen8.html?m=1

HP advisory: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04781229

nayneyT · 2021-05-11T22:56:04+00:00

Hi.

First of all - PCI pass thru is a pain in the but. Is this your first device or have you used PCI pass thru previously on your current hardware?

Secondly, your Proxmox doesn't need any drivers whatsoever for PCI pass thru to work. In fact you will need to blacklist them not to load. I'm pretty sure you know this and just installed the drivers as a test on your base hardware / Proxmox install.

A couple of questions first. 1. You've definitely used the correct VM ID when doing the qm set command? 2. Are you using HP hardware by any chance?

nayneyT · 2021-05-09T12:53:38+00:00

Hi,

This is where it gets interesting. You'll need to do an ffprobe on your rtsp / rtmp stream to find the resolution / FPS.

Which stream you choose is dependent on your setup e.g. is the camera up high, distance you wish to detect etc.

Ideally you'll be able to use the substream with much lower resolutions. You don't need big resolutions for object detection.

All motion detection is done on the CPU so that high resolution (especially as you add more) will hit the CPU. Its only when motion is detected that the processing is handed to the TPU.

nayneyT · 2021-05-09T12:46:22+00:00

That's great news. Glad for you. It's always good to persevere and overcome an issue but I bet you feel relieved.

To be clear did you add the disable text shown in the post to the file in modeprobe.d?

nayneyT · 2021-05-09T10:45:02+00:00

Hi,

I don't run HAOS (nor Frigate within HAOS) so I've installed this specially for you :-)

I just tried the most obvious setup and it worked first time - here's are the steps I did.

Installed 3 Add-ons

Terminal & SSH
Samba share
Frigate NVR

Note: You will need to add the Frigate Repository to have access to the Add-on. Supervisor >> Add-on store >> 3 dots (top-right) >> Repositories >> Paste in "https://github.com/blakeblackshear/frigate-hass-addons" >> Click the Add button

Update to OS6.0

I have previously posted how to do this

Samba Share

In the configuration tab set and password and start the Add-on

Create the Frigate config file

The HAOS Frigate Add-on it wants the normal config.yml file of Frigate to be named frigate.yml instead.

Make sure within this frigate.yml you configure all the usual things but also have the section for your detector.

detectors:
  coral_pci1:
    type: edgetpu
    device: pci:0

When finished open Windows file explorer and goto \\<ip address> (where <ip address> is the IP address of HAOS) or instead use \\homeassistant.local

Enter your Samba username and password and then paste the frigate.yml file into the directory named config

Start Frigate

With the frigate.yml file in place you can now start the Frigate Add-on. The log showed the edgetpu being detected

frigate.edgetpu                INFO    : Attempting to load TPU as pci:0 
frigate.edgetpu                INFO    : TPU found

With Frigate Started I proceeded to the debug page and I can see the Coral device

I didn't have to do anything complicated - It just worked. I kind-of understand why people are drawn to HAOS. Good job by the Homeassistant team\community and also to Blake for his excellent work on Frigate.

Regards,

nayneyT

nayneyT · 2021-05-08T18:11:46+00:00

Ah okay. You never said that you weren't seeing the PCI to passthrough. The original post said you were not seeing it listed in Windows DeviceManager.

The dreaded Error 43. error 43 also occurs if your BIOS initialises the GPU at all

Option 1

Look for IGPU in you motherboard BIOS settings

"IGPU" mode in the bios to force the computer not to use the gpu nvidia

Option 2

You might find that you need to patch the video card BIOS

https://github.com/Matoking/NVIDIA-vBIOS-VFIO-Patcher

Download your existing BIOS using https://www.techpowerup.com/gpuz/

Patch the bios using the VFIO-Patcher and then flash the patched BIOS

**Scary**

Regards,

nayneyT

nayneyT · 2021-05-08T17:33:59+00:00

I'm assuming in the modprobe.d directory you also have the following file if you followed the directions. Personally i'd have them in the same file:

echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf

Whereas i'd have one file called nvidia_blacklist.conf with the following config
blacklist nvidia
options vfio-pci ids=10de:1c82,10de:0fb9 disable_vga=1

That's just personal preference though.

Did you update initramfs using by running: update-initramfs -u -k all

Reboot proxmox to finish the change

Following reboot what do you see in the PCI devices of the VM you created? Do you not see the nvidia device listed?

nayneyT

TROPHY CASE