I have an x86 pc installed openwrt and realtek rtl8111h 4 ports ethernet nic on pcie. The device was detected. but have some strange behavior. The link is always down. and the nic was detected as r8169 when I checked on dmesg.
The day before wjz304 decided to stop his work, someone reported a new issue on his GitHub and asked why modules were not open source on his repo. There was reference to something that was named "secret". You could see it called out in the code.
I didn't see what wjz304 responded to him, but that seemed to upset him to the point of leaving the scene. I don't want to believe wjz304 did something malicious, but he immediately closed everything and said he was accused of not disclosing driver source code. It was an extreme reaction.
I also suggest this to @Flautista1988, another user who asked the same question.
If there is a problem with r8168 or r8169 in the integrated module of TCRP-mshell, we will switch to the final version of the module of rr.
Ok, in RR, DSM installation is fine and successful, but in ARC, the loader config menu boot fine, and i can config the loader fine. But when loader boot to DSM, the network card did not respond, no appear in wnetwatcher, no ping, nothing. My network card is onboard realtek R8168.
In ARC if config a DS923+ the loader boot successful, and works fine ?
Yes, I was a little extreme at the time, because I roughly guessed who that person was.
(A brand new account, so to speak, the account created specifically for the purpose of creating that issue) This is what makes me angry.
So when he mentioned the open source agreement, I didn't think much about it. Since I can't publish it because the second release under the protocol requires public modification, I delete the repository and don't publish it.
I installed the loader M-shell last night, it didn't want to on the first try, but I succeeded on the second try. My network card is recognized and works without problems. Thanks a lot for the advice!
I'm very sad because of this, he is the only dev that kept dsm 6.2.4 alive and it is also very frustrating thinking that maybe some other dev is involved in this situation. (He did said that someone wanted the source of the drivers he had). It really saddens me. But he deserves a break and hope he will be back someday. Thank you for your amazing work.
I have xpenology 7.2.1 under proxmox, TRPC loader. I have 5 hdd (100 gb virtual for system, 3 in raid, 1 single). It worked properly. I did a restart, it restarted, but i cant login, xpeno says: The system getting ready, please log in later.
For me there's no loader working anymore (Intel H61). I have a R8111C NIC (R8168) and the only loader that have this module is the ARC but it won't suport bromolow.
Anyone can help me how do i add this module to a ARPL loader?
Hello, thank you for your answer!
I think the driver exists and is installed, I can see it on the sysinfo and network card led (yellow on the left and green on the right were flashing) everything is fine until I start the DSM kernel, from then on my card network is no longer recognized and only the yellow LED flashes to see the photos.
Which addon do you think I should add?
Thanks for your information, it doesn't work for me, I tried everything as explained on the ARC Wiki site, but it doesn't work.
I tested on 2 platforms Intel and AMD, the same network card r8168 cannot work with DS3622xs+ but it can work with DS923+ like yours, it does not work from the moment the DSM kernel is started, the same problem and I don't understand anything.
Avec RR and ARPL M-shell I have no problems.
I'm in the market for a mini PC unit to run XG Home on my network and I've come across a few worthy contenders (in terms of price, having quad-core CPUs, etc.) but they seem to all be running some form of Realtek NIC. One unit in particular I'm interested in (the QOTOM Q160S) appears to be running Realtek 8111E NICs.
A lot of the posts I've seen are at least a year old, if not older, so I want to know definitively; will using XG Home with Realtek NICs result in a bad time? If the choice is between dual-core Core i3 with Intel NICs vs a quad-core Celeron N1360 with Realtek NICs, which one would be the "better" choice?
the issue with the realtek NICs is they offload processing to the CPU which then becomes a bottleneck for throughput. If your internet connection is say 100/40 or smaller and your number of connected devices is quite small then the realteks will be okay otherwise you need to consider intel or broadcom. CPU should be the fastest you can get, though not the highest performance.
Ok gotcha. I'm moving soon and I'm probably going to get 150/15 min and 150/150 max, with about 15 devices (5 of which will need to stream or video call), but I do quite a lot of streaming video and video calling. Based on that, would I run into issues?
Since it's mostly me anyway I'd mostly be using XG to separate my trusted devices, IoT devices, and guest devices across VLANs, with web filtering and ATP on all networks, and IPS on the IoT and guest network.
Got it. In terms of processor, would a processor like the i3-4010Y or a Celeron 3855U be enough (both dual-core, the i3 is 4 threads though) be enough or would I need to step up to a quad-core processor?
A quad core is nice, but not essential, the dual core with hyper threading will work with capacity to spare and is not the preferred processor but if that is what you can get on your budget then that is it. The only issue really is the GUI update performance that is why I have an e3 up from a fast atom because I like to fiddle and try various issues posed in these forums.
If it's still not recognised, reboot your OMV6 system using a previous kernel. If you have a keyboard and monitor attached to your OMV6 system simply choose the 5.19 or 5.16 kernel from the grub boot menu.
Both kernel 6.0 and kernel 5.19 appear to load the correct module listed as r8169 in your screen caps. Don't reinstall just yet. Why not reboot to kernel 5.16, assuming you did not remove it? Check your network cable connections too.
There be some clues in the logs re: your problem with RTL8111H. You can pick out a "day" from the systemd journal when the kernel 5.16 was in use and the NIC was working and compare this to the last system boot. For example, check logs from 2 days ago for info about realtek nic:
Your logs show the onboard nic - RTL8111 was working with module r8169, which exist in the later kernels. But is the linux firmware package still on your system? Check with "apt list firmware* --installed".
c80f0f1006