CWWK/Topton/... Nxxx quad NIC router
- Thread starter Becks0815
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Apparently I've been trying to install lm_sensors all the time instead of lm-sensors. Not sure where I got this from but at least it's working now 
:
I did also do some performance benchmarks for my N100 and they came out a bit low. I think I'll need to play a bit with the power-levels as people have been doing in this thread.
Another question I had was how much SSD's can this device fit at once. I'm asuming one in the standard NVME port and 4 with the 4x => 4x 1x NVME board for a total of 5 right?
:
Code:
root@proxmox1:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +44.0°C (high = +105.0°C, crit = +105.0°C)
Core 0: +44.0°C (high = +105.0°C, crit = +105.0°C)
Core 1: +44.0°C (high = +105.0°C, crit = +105.0°C)
Core 2: +44.0°C (high = +105.0°C, crit = +105.0°C)
Core 3: +44.0°C (high = +105.0°C, crit = +105.0°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +27.8°C (crit = +110.0°C)
nvme-pci-0500
Adapter: PCI adapter
Composite: +55.9°C (low = -40.1°C, high = +83.8°C)
(crit = +87.8°C)
Sensor 1: +77.8°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +53.9°C (low = -273.1°C, high = +65261.8°C)Another question I had was how much SSD's can this device fit at once. I'm asuming one in the standard NVME port and 4 with the 4x => 4x 1x NVME board for a total of 5 right?
Those are my findings. 2 m.2 slots. One running at 4x and the other at 1x. I believe there's a non-standard SATA port/pins but I'm assuming it's 1x as well.
Then what you're left with are the USB2.0 ports.
And unless I'm mistaken, if you do get one of those add-on boards that allow additional m.2 SSDs, you're still limited to the same lanes. So they'll run at 1x.
At the moment, I have a 3 node Proxmox cluster with Ceph. The OS are on the 1x m.2 slot, and Ceph is using the storage on the 4x m.2 since that's where the speed is needed.
Last edited:
complete long shot, have you tried to upgrade the bios?
There was a post 20-30 pages ago, someone else updated the bios and got fuller speeds might be worth a shot or notify cwwk or topton or your manufacturer of the issue.
I would imagine Windows drivers would be rock solid, but they have had i225/6 driver issues in the past regarding performance and stability.
Might also be worth flashing openwrt onto a usb stick (testing purposes) and try running openwrt also just in case.
I have a simple question, for which I cannot find documentation.
Is the serial port pin header on the mainboard, atleast on the topton (variant A) boards, usable for linux tty output (serial console) purposes?
I'm asking because these units (atleast my variant A topton one) doesn't have the dedicated RJ45 serial console connector on it.
Is the serial port pin header on the mainboard, atleast on the topton (variant A) boards, usable for linux tty output (serial console) purposes?
I'm asking because these units (atleast my variant A topton one) doesn't have the dedicated RJ45 serial console connector on it.
Hi Alexw1982,
Thanks for adding the image, that was hard from my mobile phone.
Yes, indeed, that is the pinheader I was talking about. Is that one setup for tty console output, or is that (optional) controlable via the BIOS?
Or can it only output the tty console after setting it up under linux, so that would mean there isn't any output from BIOS posting?
Thanks for adding the image, that was hard from my mobile phone.
Yes, indeed, that is the pinheader I was talking about. Is that one setup for tty console output, or is that (optional) controlable via the BIOS?
Or can it only output the tty console after setting it up under linux, so that would mean there isn't any output from BIOS posting?
Sorry, I misread your question. Usually it should be available if you boot a compatible OS or ISO image. I doubt there is BIOS console support on those boxes (but I could be wrong). Ideally you try and let us know … I still don’t have a n100 box to play with.
A couple of new user to this device questions....
(1) Am I correct in thinking that the two jumpers that are labeled "Power off USB power off switch" disable the USB ports so they do not provide power when the system is shutdown or am I misreading this?
(2) Does anyone know which bios setting(s) prevent automatic booting when power is first applied?
This is on a HUNSN RJ35
Thanks, Keith
(1) Am I correct in thinking that the two jumpers that are labeled "Power off USB power off switch" disable the USB ports so they do not provide power when the system is shutdown or am I misreading this?
(2) Does anyone know which bios setting(s) prevent automatic booting when power is first applied?
This is on a HUNSN RJ35
Thanks, Keith
I'm trying to get GPU passthrough to work on the N100 device. I've followed this guide but for some reason my IOMMU won't enable:
I couldn't find the VT-d option in the bios, but I saw multiple people in this thread post the same while still having success enabling GPU passthrough.
My files:
cat /etc/default/grub
dmesg | grep -i -e DMAR -e IOMMU
This command also shows no results:
ls /sys/kernel/iommu_groups/
I couldn't find the VT-d option in the bios, but I saw multiple people in this thread post the same while still having success enabling GPU passthrough.
My files:
cat /etc/default/grub
Code:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Code:
[ 0.011866] ACPI: DMAR 0x000000007550E000 000088 (v02 INTEL EDK2 00000002 01000013)
[ 0.011900] ACPI: Reserving DMAR table memory at [mem 0x7550e000-0x7550e087]
[ 0.144570] DMAR: Host address width 39
[ 0.144571] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.144578] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 29a00f0505e
[ 0.144582] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.144587] DMAR: dmar1: reg_base_addr fed91000 ver 5:0 cap d2008c40660462 ecap f050da
[ 0.144590] DMAR: RMRR base: 0x0000007c000000 end: 0x000000803fffff
[ 0.144593] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.144596] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.144597] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.146254] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 10.483000] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphics
[ 12.326958] iommu: Default domain type: Translated
[ 12.326961] iommu: DMA domain TLB invalidation policy: lazy models /sys/kernel/iommu_groups/
Last edited:
Did you "commit" the grub change? Did you also configure the Modules file with the following?
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
for everyones NXXXX device are you just using 2 of the NIC's fpor your opnsense or are you using much more?
I figured it out, apparently I'm using the systemd variant for booting rather then GRUB. I thought GRUB would be the default for Proxmox but apparently not.
So after updating /etc/kernel/cmdline I now see:
Code:
[ 0.061921] DMAR: IOMMU enabled
[ 0.144552] DMAR: Host address width 39
[ 0.144553] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.144561] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 29a00f0505e
[ 0.144564] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.144569] DMAR: dmar1: reg_base_addr fed91000 ver 5:0 cap d2008c40660462 ecap f050da
[ 0.144573] DMAR: RMRR base: 0x0000007c000000 end: 0x000000803fffff
[ 0.144576] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.144578] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.144580] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.146248] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 7.655000] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphics
[ 8.982965] iommu: Default domain type: Passthrough (set via kernel command line)
[ 10.115740] DMAR: No ATSR found
[ 10.115742] DMAR: No SATC found
[ 10.115744] DMAR: IOMMU feature fl1gp_support inconsistent
[ 10.115744] DMAR: IOMMU feature pgsel_inv inconsistent
[ 10.115746] DMAR: IOMMU feature nwfs inconsistent
[ 10.115748] DMAR: IOMMU feature dit inconsistent
[ 10.115749] DMAR: IOMMU feature sc_support inconsistent
[ 10.115751] DMAR: IOMMU feature dev_iotlb_support inconsistent
[ 10.115753] DMAR: dmar0: Using Queued invalidation
[ 10.115757] DMAR: dmar1: Using Queued invalidation
[ 10.115981] pci 0000:00:02.0: Adding to iommu group 0
[ 10.116023] pci 0000:00:00.0: Adding to iommu group 1
[ 10.116041] pci 0000:00:14.0: Adding to iommu group 2
[ 10.116050] pci 0000:00:14.2: Adding to iommu group 2
[ 10.116060] pci 0000:00:16.0: Adding to iommu group 3
[ 10.116072] pci 0000:00:19.0: Adding to iommu group 4
[ 10.116081] pci 0000:00:19.1: Adding to iommu group 4
[ 10.116089] pci 0000:00:1a.0: Adding to iommu group 5
[ 10.116103] pci 0000:00:1c.0: Adding to iommu group 6
[ 10.116114] pci 0000:00:1d.0: Adding to iommu group 7
[ 10.116127] pci 0000:00:1d.1: Adding to iommu group 8
[ 10.116141] pci 0000:00:1d.2: Adding to iommu group 9
[ 10.116153] pci 0000:00:1d.3: Adding to iommu group 10
[ 10.116171] pci 0000:00:1f.0: Adding to iommu group 11
[ 10.116180] pci 0000:00:1f.3: Adding to iommu group 11
[ 10.116189] pci 0000:00:1f.4: Adding to iommu group 11
[ 10.116198] pci 0000:00:1f.5: Adding to iommu group 11
[ 10.116211] pci 0000:01:00.0: Adding to iommu group 12
[ 10.116226] pci 0000:02:00.0: Adding to iommu group 13
[ 10.116237] pci 0000:03:00.0: Adding to iommu group 14
[ 10.116253] pci 0000:04:00.0: Adding to iommu group 15
[ 10.116264] pci 0000:05:00.0: Adding to iommu group 16
[ 10.116358] DMAR: Intel(R) Virtualization Technology for Directed I/O
So as I previously mentioned I now managed to get IOMMU working and attached my GPU as primary GPU to a VM. However when I boot the VM the screen of the HDMI port turns black + I can't use noVNC anymore. I would expect the output of the VM to be output to the HDMI port on the CWWK Device:
