odie82544
-
Posts
53 -
Joined
-
Last visited
Posts posted by odie82544
-
-
is there a mirror for this file? I can't download the file.
error message (translated) : "Invalid link. The linked file is no longer shared."
The Asus Web Storage page still live, but very easy to run out of my bandwidth, usually 00:10 will reach everyday.
There are new build and fix some fatal bugs, for prevent unnecessary confusion, so I kill the google link.
Overall saying, this is not success build to me, and few feedback about this release, means not much people need it.
So I won't release any new build for x86 DSM here.
The latest build have able to modify volume layout and format as EXT4.
Before:
Example-3.jpg[/attachment]
-
Do I need to disable the on board nic when I add PCI nic?
How come that My router that set to DHCP show on the device list that there are host called DiskStation and it got valid IP number from the router (And I can ping it). I was thinking that it will not get IP if there are no driver for the card?
Just insert supported NIC on MB are enough, there are pci id tables inside kernel, if the table unable to mapping your device, maybe cause unable 100% drived.
-
Hello,
After installing the SA on my windows 8 pro pc I search for server and find none. When I look on my router I can see the IP address that allocated for this computer and I can ping it, but the SA can't find the server
04.Search the DSM booting box by Synology Assistant (SA) and provide "DS411-1067-x86-20130525.pat" to SA.
Your nic not supported by kernel.
The DSM 2.3 was very old kernel, maybe have bugs or few nic device id in kernel, so unable to support your nic.
-
Hi odie82544
方便的話,您可以私息給我您的IP.我可以讓您進來看我的環境..SSH/TELNET/DSM UI
Since this build can work on your box, I am considering that are enough, although I prefer to install x86 DSM 4.2 or (above) directly.
-
Hi odie82544
Can you help with Hyper-V Network Driver for X86 version!?
I am no interesting in Hyper-V. Sorry for that.
-
Hi, Guys
About odie82544 Provide the Image and DS411 upgrade to RS3413xs+
Maybe can refer my steps(I can't join NAS1/CN, So only Sharing in here)
Prepare one USB Key (32MB~8GB) and 2 HDD(must hvae 2 Hard DISK) connect to MB
(Any MainBoard ASUS P43TD/P43TDPRO/P8Z77-V/P9X79/P8H77-V)
All load from UEFI BIOS Default setting
HDD ID0 IDE/SATA/SAS 4.3G~120G(also use USB KEY and Force set type is HDD)
HDD ID1 IDE/SATA/SAS 40G~120G
Thanks, but the major issues about unable to change the volume, were because of lots of hdd/volume utility are for x64, this is the root cause.
I had manual change file system to ext4 success by recompiler some programs in DSM.
-
When trying to install after first reboot I boot to DSM 2.3 again (step 6). It then goes through the process of writing the configuration files and shows "== Philippines Coast Guard massacred Taiwan finishing boat on 2013-05-19 ==" a few times then invalid HDD 11 and invalid HDD 12, only one drive is connected during this. Then the system "kills" and just shuts down the machine. It never gives me a change to log in to webUI. Am I missing something?
Enable your com1 in bios and try again
-
hi Oddie,
Thanks for your amazing job, so what's the most reliable version in those DSM release? Looks like 4.2-3202 is not that reliable . Thanks.
I just like 3.2-1955 and 4.1-2668, if just for NAS purpose, I consider 3.2-1955 are best to me.
-
odie82544:
I have some questions:
- What toolchain / GPL sources (arch and version) did you use to build this kernel ?
- How to create the grub_cksum.syno file (Encrypted checksum) ?
- In your futur release can you include the .config file ?
You should read this: http://xpenology.com/wiki/en/building_xpenology
A1. I didn't recompiler the kernel for this build, because when I repack it, Synology still not release the GPL/ToolChain for DSM 4.2-3202.
A2. This is not necessary file, just remark it from the grbu index file and can pass it, this file just for booting purpose for make sure the rd.gz and zImage not modified.
A3. As A1, so no .config file to provide, I just add some NIC drivers and repack the .pat file, so just named it as "Repack" version.
-
May I ask if the I use the new .pat file to update the 3202 DSM?
Yes, but no more work after reboot your DSM.
-
支持下楼主。。楼主的全球首发已经拜读过了。。能否pm个联系方式有问题求教。。
You can contact with me at NAS1
-
This is release can let your old x86 only box have chance to use DSM 4.2-3211
Build Information:
================
Support NIC:
DSM 2.3 and 4.2: typhoon / b44 / e100 / 8139cp / 8139too / e1000 / e1000e / r8168 / r8169 / r8101 / skge / sky2 / sk98lin / tigon3 / bnx2 / atl1
DSM 4.2 only: atl1e / atl1c / igb / igbvf / jme / skge_genesis / vmxnet3
================
Support Controller:
DSM 2.3 and 4.2: sata_ahci / ata_piix / sata_mv / sata_promise / sata_sx4 / sata_sil / sata_sil24 / ata_generic / pata_hpt37x / pata_jmicron / pata_pdc2027x
DSM 4.2 only : pvscsi
================
Support Platform: Intel x86 CPU
================
How to Install:
01.Use RAW tool to write the "DS411-1067-x86-20130525.img" image file to your USB key (at least 16MB capacity).
02.Enable COM1 from BIOS then boot from USB key.
03.Select "Boot DSM 2.3-1167 x86" when the GRUB boot manager show up.
04.Search the DSM booting box by Synology Assistant (SA) and provide "DS411-1067-x86-20130525.pat" to SA.
05.DSM will auto reboot when .pat install done, the GRUB boot manager will show up again.
06.Select "Boot DSM 2.3-1167 x86" to complete the SA install process (Write configuration to DSM success).
07.Login into DSM from Web UI, create the HDD volume/space you want. (the SA will show the DSM version as 1.0.1000 now)
*.Very Important: You must create HDD volume/space at the step.
08.Reboot DSM when step.07 finish, select "Boot DSM 2.3-1167 x86" again when GRUB show up.
09.Search DSM by SA, SA will show "configuration lost" and ask to provide the .pat file, give "RS3413xs_3211-x86-20130525.pat" to SA.
10.The step.05 repeating now.
11.Select "Boot DSM 2.3-1167 x86" again when GRUB show up, the DSM 4.2 .pat file will install during this step.
On this step, we just want to the "RS3413xs_3211-x86-20130525.pat" wrote to HDD.
So press the computer "Reset" manaully when the screen continue show up "== Philippines Coast Guard massacred Taiwan finishing boat on 2013-05-19 ==".
*.It's really, no matter press "Reset" or the VGA console messages.
12.When the GRUB show up again, select "Boot DSM 4.2-3211 x86", the SA will finish the install process. (Write configuration to DSM success).
13.Login into DSM 4.2 Web UI and start to setup your DSM.
14.All done and enjoy it.
================
*.Very Important: You can't delete the HDD volume/space in DSM 4.2, otherwise need to go again the installation process.
Another words, the HDD volume layout must all finish in Step.07, and the file system will be EXT3.
Download URL: DEAD Link
EDIT Trantor : I reupload the file viewtopic.php?f=2&t=800&start=100#p6739
-
Ok Thanks you Andy i going try this.
Save your time to do it, the HA function can't work on my previous version.
-
Could you please share the exact build and kernel you used?
The DMS 3.2 build 2031 use Linux 2.6.32 kernel
-
What build used
DSM 3.2 build 2031
-
Your LOM and daughter board LAN chip need to install mii.ko, r8168.ko and r8169.ko.
The r8169 driver are older, but not fully support r8168, if load the r8169 first, than some r8168 chip can't work properly.
For fix your issue, the driver load sequence should be:
1.mii.ko
2.r8168.ko
3.r8169.ko
But from my view, the daughter board with LOM x3 won't improve the LAN performance too much if you are target for this.
Because most r8169 are for PCI base chip, the total Max. bandwidth for PCI-33 bus are only 133MB/sec.
-
What is your motherboard?
Abit TS-20 from SA-1000 NAS
-
I had success let my old Pentium III 886mhz with 384MB RAM old box work with DSM 3.2 build 2031 with x86 kernel now.
The WOL also work too, but the file system unable to upgrade to EXT4, anyone have idea to fix this issue on source code?
Anyway, at least, have chance to keep forward to DSM 4.2 for x86 only box.
-
This is because of the DSM will reset hardware clock during booting, for auto power on and schedule task using.
The ways to fix this issue maybe are any one as below:
1.patch DMS some files.
2.change BIOS vendor.
3.setup CMOS to read only.
-
I had success upgrade my Intel Pentium P3-866mhz with 384MB RAM old computer to DSM 3.2 x86 build.
-
hi.
my old system use below
IDE controller ALi M5229 PCI Bus Master IDE Controller
SCSI/RAID controller D347PRT SCSI Controller
SCSI/RAID controller ULi SATA/RAID Controller (M1573)
is it possible?
This box not only old but also very very old.
Not supported.
-
RTL8169 - not working
D-Link DGE-530T rev B1 (Marvell 88E8001-LKJ1) - no link, no leds
D-Link DGE-528T rev A1 (D-link DLG10028A) - linked, but no ping, leds always on
noname gigabit cards from ebay on the Realtek RTL8111E, DL - no link, no leds
M/b Intel D525MW, DSM 4.2 build 3202
Your MB have one PCI slot and LOM need r8169.ko, all your list card are not supported in my build.
The fastest way to you is: insert Intel PRO-1000 PCI series NIC (e1000)
-
The largest memory support based on the NorthBridge chipset or CPU (new CPU had include NB).
I can use 16GB memory capacity on Intel Z68 and Z77 platforms with Xeon E3 V2 CPU.
All the boot kernel for DSM had update to x64 after DSM 2.3 build 1167.
Maybe you need to update your MB BIOS to the latest version.
-
Marvel YUKON lan controllers seems to be supported by the 4.1-2668++ version ...
i have tested realtek pci 8168,the lan chips also not work probarly in 3202.
Most Realtek PCI 8168 NIC need to use r8169.ko
Synology RS3413xs+ DSM 4.2-3211 x86
in DSM 5.2 and earlier (Legacy)
Posted
I had try to install on Intel P4 socket 478 FSB800 CPU with 865 chipset yesterday, its really not easy to sucess install .
I am considering the reason as below:
01.Comparing to the DSM 2.3 and DSM 4.2, the code and kernel are really too old, suppose have lots of issues.
02.The e100 or most old PCI/PCI-X 10/100 NIC usually need "Firmware" file to initial in Linux OS, at my side, I also unable to let my 82599 LOM work properly. (only works on 10M)
03.Most of the old x86 cpmputers use Award BIOS, the Award BIOS seems not do very well between IDE and SATA HDD switching.
I use SATA HDD and turn it to IDE compatibility mode in BIOS, also got fail installation results.
All problems came from unable to success install by DSM 2.3, if you can install DSM 2.3 and turn to DSM 4.2, suppose the controller or NIC issues will solved.
I will suggest you to try Realtek gigabits NIC for PCI-33 (r8168 series), I am sure it can work in DSM 2.3, because one of my P3-733 just work with it.
About the Intel 82547, I have lots of it, mine are pci-66, I am sure the Intel 82547 (e1000) can work propely in DSM 2.3, no matter VMware or VirtualBOX (those virtual machine all default set as e1000).
If you also want to use iSCSI in x86, I can let you know that you should give up now, there are some DSM 4.2 programs relate to iSCSI portion are x64 only.