DSM 6.1.x Loader


Recommended Posts

Thanks Trantor for V1.02alpha.

 

I can confirm it is working bare metal on ASUS C60M1-I with AMD Fusion APU C-60. Network card is Realtek 8111F.

 

System is running with DSM 6.1-15047-1 Raid1 Btrfs. I was able to perform the automatic update 1 and rebooted without issue afterwards.

 

Prior to this I was running Version: 6.0.2-8451-8 on this same system without issue.

6.1 worked on AMD, see my signature.

Jun, would you mind commenting on this? I have seen several people saying that v1.02a is working with AMD based CPU hardware. How is this possible? Thanks.

Link to post
Share on other sites
I attempted to inject firmware into image via OFSMount with no success.

 

sorry i'm just guessing, its what i would try so ....

looking further into the extra.lzma, there is /etc/rc.modules

...

EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin"

...

so looks like the firmware file has to be mentioned in that file to work?

 

I am not sure if jun compiled or just tossed a kernel ID. Guessing its not compiled for 3.10

 

Tossed a kernel ID? Not sure what that is supposed to mean but if modules were not compiled against the proper source code they would simply not work. Do not confuse modules and firmware.

All modules within the v1.02a (or v1.02a2) loaders are compiled against DSM 6.1 source code and made to work with linux kernel 3.10.102. There is no other way around. In your case, the firmware seems to be missing. I checked the extra ramdisk and it is not there. The rc.modules also needs to be updated with the added firmware or whatever module you add in the ramdisk else it wont be loaded during kernel boot. I have made the necessary changes in the ramdisk. Let me know if it works (or not). I can't test it myself since I do not have that NIC.

 

https://mega.nz/#!OQplzISJ!L6HzXJq2ZwX- ... k99jYVwKBc

 

note to myself: This ramdisk only contains the additional firmware bnx2-mips-09-6.2.1b.fw on top of the default ones added by Jun. Nothing else.

 

The original DSM 6.0 loader/modules was compiled with beta source code. Are you saying the DSm 6.1 loader (1.02a and such) was compiled with the released source code? if I remember correctly, the loader was available before the source code was.

 

thanks

Link to post
Share on other sites

 

The original DSM 6.0 loader/modules was compiled with beta source code. Are you saying the DSm 6.1 loader (1.02a and such) was compiled with the released source code? if I remember correctly, the loader was available before the source code was.

 

thanks

 

Jun released v1.02a 3 weeks prior the release of the source code of DSM 6.1. He said that he did not need the source code to make the loader work since his patching method was still functional with DSM 6.1. That's one thing.

 

Now for the modules, I am guessing that he either reverse engineered the modules and fiddled with them or recompiled the modules with the kernel source code of linux 3.10.102 which has been available for close to a year already. I am just guessing here, so do not quote me on this one. That's a question that Jun would need to answer himself. But in general one needs at least the source code of the kernel to be able to compile a module that will work with that kernel version.

Link to post
Share on other sites

Tossed a kernel ID? Not sure what that is supposed to mean but if modules were not compiled against the proper source code they would simply not work. Do not confuse modules and firmware.

All modules within the v1.02a (or v1.02a2) loaders are compiled against DSM 6.1 source code and made to work with linux kernel 3.10.102. There is no other way around. In your case, the firmware seems to be missing. I checked the extra ramdisk and it is not there. The rc.modules also needs to be updated with the added firmware or whatever module you add in the ramdisk else it wont be loaded during kernel boot. I have made the necessary changes in the ramdisk. Let me know if it works (or not). I can't test it myself since I do not have that NIC.

 

https://mega.nz/#!OQplzISJ!L6HzXJq2ZwX- ... k99jYVwKBc

 

note to myself: This ramdisk only contains the additional firmware bnx2-mips-09-6.2.1b.fw on top of the default ones added by Jun. Nothing else.

 

The original DSM 6.0 loader/modules was compiled with beta source code. Are you saying the DSm 6.1 loader (1.02a and such) was compiled with the released source code? if I remember correctly, the loader was available before the source code was.

 

thanks

 

Thanks for helping but unfortunately still not working for me. comparing this version with previous one there is also a file in the modules folder called bnx2list.ko that is missing.

Link to post
Share on other sites
Was that for 3617 1.02a2 or 3615 .2a?

1.02a2 3617 the nic's are up and running. find syno worked initially. Loading DSM not so much. Looking at logs to see whats up when I have time.

 

Yes that was for v1.02a2. The model (3615 or 3617) is irrelevant.

Link to post
Share on other sites
Thanks Trantor for V1.02alpha.

 

I can confirm it is working bare metal on ASUS C60M1-I with AMD Fusion APU C-60. Network card is Realtek 8111F.

 

System is running with DSM 6.1-15047-1 Raid1 Btrfs. I was able to perform the automatic update 1 and rebooted without issue afterwards.

 

Prior to this I was running Version: 6.0.2-8451-8 on this same system without issue.

6.1 worked on AMD, see my signature.

Jun, would you mind commenting on this? I have seen several people saying that v1.02a is working with AMD based CPU hardware. How is this possible? Thanks.

 

I have tested the following AMD Mini ITX motherboards with 1.02A and working:

 

Asus C60m1-I

Asus E35M1-I

Asus E35M1-I Deluxe

 

Asrock C70M1

Asrock E350M1

Link to post
Share on other sites
Thanks Trantor for V1.02alpha.

 

I can confirm it is working bare metal on ASUS C60M1-I with AMD Fusion APU C-60. Network card is Realtek 8111F.

 

System is running with DSM 6.1-15047-1 Raid1 Btrfs. I was able to perform the automatic update 1 and rebooted without issue afterwards.

 

Prior to this I was running Version: 6.0.2-8451-8 on this same system without issue.

6.1 worked on AMD, see my signature.

Jun, would you mind commenting on this? I have seen several people saying that v1.02a is working with AMD based CPU hardware. How is this possible? Thanks.

 

I testing in hp n54L is amd onboard cpu

In 1.01 us needed boot on amd title mode

 

In 1.02a amd title mode in conf is # hidden on boot screen

Link to post
Share on other sites

 

I testing in hp n54L is amd onboard cpu

In 1.01 us needed boot on amd title mode

 

In 1.02a amd title mode in conf is # hidden on boot screen

 

@shal

Nice news

How can I unlock the hidden function?

cu-ya

 

There is a good reason why the AMD line and boot sequence is commented out in v1.02a. It's not hidden, it simply isn't fully functional or maybe Jun didn't go through the code to make sure it is working as expected with AMD based hardware. This loader is already an alpha so I do not recommend you host important data on the box if you are planning on using the loader on an AMD based machine.

Link to post
Share on other sites
Here is a video install i made of DS3615xs 6.1 Jun's Mod V1.02-alpha on ESXI 6.5 Ill be making another one on how to install ds3617xs V1.02a2-alpha soon...

 

 

That's would be awesome! Can you do a your next video for a barebone install of 10.2a2 please? :grin:

Thanks a lot!

 

Bare metal install would be awesome for me too. Thanks a lot!

Link to post
Share on other sites

I have tested last loader with ESXI 6.0, no problem.

 

I just cannot add second network card ? Someone did that ?

I add another network interface on VM on ESXI.

I restart Syno, but anything

I use grub menu and mac2 command, anything....

 

Another step missed ?

 

 

EDIT: It's a success, i changed Network interface with E1000 instead VMnet2.

Link to post
Share on other sites

No boot loader screen? Nothing?

 

I have also a bloody bastard HP Elite Desktop that cannot boot from USB. If I burn a CDROM, everything is fine. Now I screw a small CDROM into the box behind a cover and that works good. So it boots up from internal CDROM. But I made this for 5.2 and not for 6.1. But I think its the same.

Link to post
Share on other sites

@dasis, you have to boot from USB. Check the Advance or other tab for "Boot Order", or "Boot option". You can even try to manually select boot device by pressing F11, F12, or other F-keys, depending on your system. Also, your computer is fairly old, and likely don't support UEFI, which is needed for this bootloader.

Link to post
Share on other sites
@dasis, you have to boot from USB. Check the Advance or other tab for "Boot Order", or "Boot option". You can even try to manually select boot device by pressing F11, F12, or other F-keys, depending on your system. Also, your computer is fairly old, and likely don't support UEFI, which is needed for this bootloader.

 

Is it UEFI only? I thought either would work

Link to post
Share on other sites
@dasis, you have to boot from USB. Check the Advance or other tab for "Boot Order", or "Boot option". You can even try to manually select boot device by pressing F11, F12, or other F-keys, depending on your system. Also, your computer is fairly old, and likely don't support UEFI, which is needed for this bootloader.

 

Is it UEFI only? I thought either would work

 

It's a hybrid loader. It will boot in legacy (BIOS) or UEFI enabled motherboards.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.