Tony wrote:
Roland Berbalk wrote:
Hi,
the mobo is an asus tr-dls last bios the plugged NIC an 64bit Intel 1000 TX the onboard Intel 100. I`ve tried to change slots, give fixed IRQ`s, NO plug and pray...
All that works is 2.03!
I’ve no experience with that board so I took some time to download and read through the manual. Definitely an oddball board Roland. Very strange design for sure. There are BIOS options to disable some devices and jumpers to disable others. There are none to shut off the damn NIC though.
The dilemma is this: As a design rule we do not save hardware-specific data into the NASLite configuration. That is the reason you do not see any hardware-specific options in the administration menu. By design NASLite evaluates the hardware at boot and configures itself automatically. The auto-configuration rules are pretty robust and have evolved in complexity to what you see in 2.04. There are cases, such as the one you are experiencing, that will not conform to what we’ve considered to be the norm.
With that said, is there anyone else experiencing the same problem? If this is not an isolated case, then we may have to come up with a way to select the fastest NIC. I don’t know if it will be effective, but it is the only thing that comes to mind of at this time.
Hi,
I noticed this at installing (testing that board) with knoppix, ubuntu and suse linux: onboard>eth0 plugged>eth1. I can understand for benefits of others changing this in 2.04 but where is the problem to add a menuepoint in network - change - eth0 to eth1 - reboot???
This box does it`s job since 2.01 in a furious kind of data transmission.
:how to add a screenshot.jpg???
We had 5 computers attached with 1g Intels all, writing and copying from it. nas system load of 128% delivering all of them with no delay! This means: 20MB/s single at smb - we didn`t try ftp yet.
P.S.: Thanks for changing updates payments
And: never change a running system