![]() Link partner advertised FEC modes: Not reported Link partner advertised auto-negotiation: Yes ![]() Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised link modes: 10baseT/Half 10baseT/Full Supported link modes: 10baseT/Half 10baseT/FullĪdvertised link modes: 10baseT/Half 10baseT/FullĪdvertised pause frame use: Symmetric Receive-only nfo: Processes: 142 Uptime: 6 min Memory: 168.8/7637.8MB Init: Other NAS2 parts aresystemd runlevel: 5 Gcc sys: N/AĬlient: Shell (sudo) inxi: 2.3.56NAS2 IP Address has also been reserved according to its MAC Address in my router. Sensors: System Temperatures: cpu: 31.0C mobo: N/Aįor your information. RAID: No RAID devices: /proc/mdstat, md_mod kernel module present ID-1: /dev/sda model: MTFDDAK256MAM size: 256.1GB temp: 0C IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: ĭrives: HDD Total Size: 256.1GB (1.8% used) Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controllerĭriver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 01:00.0 Graphics: Card: Intel Device 5a85 bus-ID: 00:02.0ĭisplay Server: X.Org 1.19.6 driver: i915 Resolution: renderer: llvmpipe (LLVM 9.0, 128 bits) version: 3.3 Mesa 19.2.8 Direct Render: Yes Machine: Device: desktop Mobo: ASRock model: J3455-ITX serial: UEFI: American Megatrends v: P1.60 date: ĬPU: Quad core Intel Celeron J3455 (-MCP-) arch: N/A cache: 1024 KBįlags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11980Ĭlock speeds: max: 2300 MHz 1: 1697 MHz 2: 1135 MHz 3: 1206 MHz 4: 1637 MHz One difference though is that NAS1 has got an 1.40 UEFI version while NAS2 is on a 1.60 UEFI version.īoth have the following UEFI setup that, to my understanding, should enable WoL:Ĭode: System: Host: NAS2 Kernel: 4.15.0-96-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: MATE NAS1 and NAS2 components are very similar, and both are based on the very same motherboard, an Asrock J3455-ITX. ![]() I showed this to a friend and it ended up with him wanting the same solution, so I made him one similar Ubuntu Server 18.04 build, let's call it NAS2.Īs you may guess, NAS2 is not responding to WoL, no way to power it on remotely. When NAS1 has been shut down (with sudo shutdown - h now), I can turn it on from PC1 by sending wake-on-lan (WoL) magic packets to it either with the powerwake or wakeonlan command. I am successfully powering on my home made Ubuntu Server 18.04 NAS1 from my PC1 Linux Mint 19.2 Build (Ubuntu 18.04 based).īoth have their IP addresses reserved in my router according to their MAC Addresses and are on the same subnet. First post, long time reader of the forum to help solving my problems, needing your support this time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |