fonix232

I double-checked before uploading, so that cannot be the reason, it is in the ramdisk for sure. Try using no password, only username (simply press enter when prompted for password) - in older DSM's it worked.

Try root - root. The username for sure is root, but I do not know the password - it is usually the admin accounts password, but as it is not set by default...

I hope it works, otherwise I'll have to go & learn what insmod it means. Insmod is a command in terminal - it installs a module (in this case, the sky2 one). The usage is quite simple: when you copied the sky2.ko to /lib/modules (cp /wherever/you/put/the/module/sky2.ko /lib/modules/), simply call insmod sky2 After that, the network card will be initialized, and you'll probably have to do a network interface setup (ifup eth0)

Sorry for the delay, I'm trying to find the proper release of the kernel to compile the module... So far tried 4 different sources, and no luck, but I'm not giving up! EDIT: Seems like my last trial was successful, insmodding worked! Download: http://sdrv.ms/13cf4ud Usage: Just like the original img you had to write to a USB flash: write it with DiskImager, and boot it. If it wouldn't work, I've included the sky2.ko, but you'll have to manually copy it to /lib/modules/, and insmod it. After that, you should have a network interface up and running!

Not just helped, I already compiled it The in-kernel built in version did not work unfortunately (kernel wouldn't boot, I need the original defconfig from 2668++'s kernel!), but the module should be working. interested: I will create the new image as soon as I tested that the module gets installed. That should be in about an hour!

First of all, the kernel automatically loads modules from a specific folders (I believe it is /lib/modules/[kernel-version]/path-to-module-type/), so that should not be a problem. But instead I would choose the solution to compile the sky2 module into the bzImage directly, then replace it on both partitions of the boot pendrive, and save the image from that. Not the best solution, but should definitely work. I will report back as soon as the kernel compile is done, and upload it for testing (first of course I will see if it boots at all).

thanks for your reply! I tried but with the same result.... Did you try following the instructions on the picture? If yes and it did not work, it might be your router blocking port 23. Try to install through the web interface (when Synology Assistant sees the device, right click and Open it instead of Install. Same procedure as in the Assistant, upload the file, then sit back and wait).

Apparently the ReadyNAS OS does not have the pcitools package installed. That is why I said you should try booting a live Ubuntu. "Marvell 8053 Gigabit LAN" is a pretty broad family of LAN NICs, I would need something more specific (though as far as I see, this should work with the generic Marvell Yukon drivers).

How does this relate to Synology DSM? By the way no, on Windows it is not possible in 99% of the cases (there are a few "blank slate" network cards that ask for a MAC address or generate a random one with each startup, usually from China).

On that, a sidenote. I simply can't understand people who want to jack their NAS up as much as possible. I mean, its whole point is to have a small, silent, cheap device to host your data when you can't fit all the hard drives into your PC. I personally would vote for the new Haswell 4x50U CPUs (though they are designed for ultrabooks, I can imagine a miniITX motherboard with an integrated 4650U, 4GB of RAM, a nice dual Gigabit NIC, and 6-8 SATA ports, exactly for building a NAS). Small, energy-efficient, great performance, though not an overkill. 15W for that, 30W for the mobo and some more for the hard drives, and you got yourself a really nice home server running everything you might want (even multiple Minecraft servers!), running on around 40W under load.

Can you check the BIOS messages, maybe it is restricted, and needs some extra keypresses? As I said I have no experience with this device, it might be that the BIOS locks out any kind of different NIC, but it still should show some kind of POST message (Illegal device detected, etc.) I will try to compile some further kernel modules later today, though if you could run "lspci" on a running Linux (Ubuntu Live is perfect) to see which Marvell-Yukon device it is exactly, I could see further.

That network card is PCI-E x1, while the socket is PCI-E x4, that's why it looks so different. Good thing is, that the PCI-E standard is backwards compatible - even a PCI-E x16 can accept an x1 card, though it will only use 1 lane, not all 16. Simply plug it in (the new network cards smaller ear should go into the longer bus on the connector, there will be only one way to insert it correctly so that one part fits perfectly), and give it a go. I will compile a kernel in a few days, hope it is not a huge problem (busy time of the year).

It is not just that the space is limited, the header of it has to be soldered first, what is not an easy task, especially if you've never done it.

It is the network card, apparently, especially if the router cannot find it. I am not too familiar with the ReadyNAS series, but is there any chance you can add an extra PCI network card, to test? In the meantime I will try to compile a kernel for you, including further support for the network card.

Seems odd. Could you please check the MAC address of the device? Also, try to connect the computer you are installing from to the router wired, and if you enabled it, disable isolation mode. If the MAC address matches the usual Synology ones (00:11:32:08:xx:xx), then there should be no reason your computer cannot see it, apart from a networking problem (isolation, for one, can quite much destroy it. Had the same problem during network setup with my own). If you can reach the webpage of the NAS after booting ([iP]/5000), then you can begin with the installation immediately, no need for the Synology Assistant (I actually prefer the web update method). Build 2668++ does support your hardware (including network card and SATA controller, my rig is quite similar, 775 socket, ICH7 controller, but I have an extra Intel card next to the Yukon, and 2668++ works perfectly), so I see no reason, apart from badly configured network, why it would not work.

Please, instead of begging for help, follow the instructions. What did it say on the screen? If it was stuck on "Booting kernel", it is no good. But if you saw a wall of text, then it should be up and running, except if your network card is not supported. Can you tell me the exact specs of your device? As in, NIC type (manufacturer and model), motherboard, SATA controller, etc., the really basics. With those I might be able to compile a kernel for your device, though I cannot guarantee it will work (I can't test it myself, as I have no such device).

Best thing to do is to try. Disconnect all hard drives on the inside, connect one you don't have any important data on, then follow the installation instructions. First try with the 4.2 3202 build, if it gets stuck at "Booting kernel", try the 4.1 2668++ version. If the latter does not boot either, you'll have to compile a customized kernel, what is quite easy if you had any experience with Linux kernels in the past.

3202 should boot with 3201 kernel, there should not be too many changes between the two.

Where did you get the 3211 sources? With minor modification, that can be used to build the x64 bzImage (and they apparently use the same tree for x86 and x86-64 builds, only difference is the configfile). The 3211 source is not on the SF page, latest is 3203, containing sources only for Armada 370.

Well then go on the Synology forum and ask for the GPL code

I am interested in this too, DSM always fucks up my BIOS and my motherboard does not have a CMOS write-only jumper unfortunately (I do not think that they put that on the new motherboards, last time I've seen it was with an old P3). I also don't want DSM fiddling with my BIOS settings, I can do finetuning myself!

There is a release of 3211 for x86, otherwise I don't think so: viewtopic.php?f=2&t=800

Let's not talk about speed, I have to use the onboard LAN (100Mbit) and an extra card (again 100Mbit) bonded to have enough speed to play 1080p files directly from CIFS

If run Video station, put more RAM better 2-3GB! Does anyone can help me to solve my ASUS E350 3GB RAM(installed 2x4GB) problem! 4 drives in JBOD (nothing important, so... I need the space ), apps I usually run inlude VPS Server, LDAP server, Mail Server, Transmission with Sickbeard, Couchpotato and Headphones, and sometimes a little Minecraft (with everything unnecessary disabled of course). Based on what you say, I could easily go with even 512MB then?

So let's say I get 4.2 running on my server, then 1GB RAM should be fine, right?