RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

On 12/11/2021 at 5:23 PM, Aigor said:

FYI it seems that you can use fibre channel adapter to act as SAN, i have one qlogic 8 gbit FC card, but it seems that is not recognized by DSM.
I decide to make an experiment.
Browse pocopico github , saw a qlnic compiled driver, download, uplod into gen8, insmod driver, nothing happens, run lun creation end with kernel dump and freeze of synobox 
One question, the extension feature is only for installation or add modules also after installation? 

Many thanks 

 

 

Synology compatibility list does not have 8Gb Qlogic HBAs, i dont know if anyone has succeed to use synology as FC target.

 

https://www.synology.com/en-global/compatibility?search_by=category&category=fc_host_bus_adapters&p=1&change_log_p=1

 

Edited by pocopico
Link to post
Share on other sites
44 minutes ago, Brunox said:

@pocopico
went faster than I thought....attached the desired logs and some pictures, I cannot establish a network connection with vmxnet3!

 

OK,  the module is loaded and that means the extension loads succesfully.

 

Can you try static IP for this interface on DSM ?  Mine is working at least with static ...

 

 

Edited by pocopico
Link to post
Share on other sites

Good morning to everybody. I have an Asrock J3455 motherboard with an Intel NIC and doing a clean install of DSM 7.0.1 42218 it starts correctly, but on reboot it asks me to install DSM again. Do you know why it may be due? 

 

On the other hand, could one go directly from 6.2.3 to 7.0.1?

 

I used Redpill toolchain 0.14, i try it UEFI and Legacy boot...

 

Thank you all!

Edited by rl91
Link to post
Share on other sites
16 hours ago, pocopico said:

 

Synology compatibility list does not have 8Gb Qlogic HBAs, i dont know if anyone has succeed to use synology as FC target.

 

https://www.synology.com/en-global/compatibility?search_by=category&category=fc_host_bus_adapters&p=1&change_log_p=1

 

Years a go i started to dig to understand if was possible and how, in my search landed on SCST website 
http://scst.sourceforge.net/
In which is explained howto implement FC SAN into linux, i was able to build kernel modules to try, but is mandatory to have kernel source.
My stop was userland part , i'm not a skilled programmer.
When synology will release kernel source i will try to se if it works 

 

Link to post
Share on other sites
3 hours ago, rl91 said:

Good morning to everybody. I have an Asrock J3455 motherboard with an Intel NIC and doing a clean install of DSM 7.0.1 42218 it starts correctly, but on reboot it asks me to install DSM again. Do you know why it may be due? 

 

On the other hand, could one go directly from 6.2.3 to 7.0.1?

 

I used Redpill toolchain 0.14, i try it UEFI and Legacy boot...

 

Thank you all!

This is caused by the loaded driver conflict

Link to post
Share on other sites
2 hours ago, Aigor said:

Years a go i started to dig to understand if was possible and how, in my search landed on SCST website 
http://scst.sourceforge.net/
In which is explained howto implement FC SAN into linux, i was able to build kernel modules to try, but is mandatory to have kernel source.
My stop was userland part , i'm not a skilled programmer.
When synology will release kernel source i will try to se if it works 

 

 

I have compile scsi_transport_fc.ko and i can create an extension, lets take this off this thread, PM me.

Link to post
Share on other sites

Hi!

 

Another guy trying to make DSM works well.

 

I'm with esxi 6.7.

 

A vm with a sata redpill. And a LSI card with passthrough and 10 disk attached.

 

I'm not able to view all 10 disks. Playing with sataportmap and others options I'm only able to see a max of 8 drives.

A resume...

Without options:                                                         33-40, 8 disks

SataPortMap=2A DiskIdxMap=0B00                        3-8, 12 7 disks
SataPortMap=1D DiskIdxMap=0C00                        2-8, 7 disks
SataPortMap=1D DiskIdxMap=000A                        2-8, 7 disks
SataPortMap=1DD DiskIdxMap=000A0A                    2-8, 7 disks

SataPortMap=008 DiskIdxMap=0007                        Kernel Panic
SataPortMap=10A DiskIdxMap=000007                    Ask for new install. I install and fail with corrupted file error.

 

Here are a few commands:

 

 

root@DiskStation:~# lspci -nn
0000:00:00.0 Class [0600]: Device [8086:7190] (rev 01)
0000:00:01.0 Class [0604]: Device [8086:7191] (rev 01)
0000:00:07.0 Class [0601]: Device [8086:7110] (rev 08)
0000:00:07.1 Class [0101]: Device [8086:7111] (rev 01)
0000:00:07.3 Class [0680]: Device [8086:7113] (rev 08)
0000:00:07.7 Class [0880]: Device [15ad:0740] (rev 10)
0000:00:0f.0 Class [0300]: Device [15ad:0405]
0000:00:11.0 Class [0604]: Device [15ad:0790] (rev 02)
0000:00:15.0 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.1 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.2 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.3 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.4 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.5 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.6 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:15.7 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.0 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.1 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.2 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.3 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.4 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.5 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.6 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:16.7 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.0 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.1 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.2 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.3 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.4 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.5 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.6 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:17.7 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.0 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.1 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.2 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.3 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.4 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.5 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.6 Class [0604]: Device [15ad:07a0] (rev 01)
0000:00:18.7 Class [0604]: Device [15ad:07a0] (rev 01)
0000:02:00.0 Class [0c03]: Device [15ad:0774]
0000:02:01.0 Class [0c03]: Device [15ad:0770]
0000:02:03.0 Class [0106]: Device [15ad:07e0]
0000:03:00.0 Class [0107]: Device [1000:0072] (rev 03)
0000:0b:00.0 Class [0200]: Device [15ad:07b0] (rev 01)
0000:13:00.0 Class [0107]: Device [15ad:07c0] (rev 02)
0001:07:00.0 Class [0106]: Device [1b4b:9235] (rev 11)
0001:08:00.0 Class [0106]: Device [1b4b:9235] (rev 11)
0001:09:00.0 Class [0106]: Device [1b4b:9235] (rev 11)
0001:0a:00.0 Class [0106]: Device [1b4b:9235] (rev 11)

 

Without options:

[    0.000000] Command line: BOOT_IMAGE=/zImage mac1=xxxxxxxxx netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x058f synoboot_satadom=1 syno_hdd_detect=0 pid=0x6387 console=ttyS0,115200n8 elevator=elevator sn=xxxxxxxxxxxx root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2

 

 

 

 

Thaaaanks a lot!

Link to post
Share on other sites
1 hour ago, pocopico said:

    "internalportcfg": "0xffff",
    "esataportcfg": "0xff000",
    "maxdisks": "12"

With this options y get the same at the moment.

 

Disks from 33 to 40, only 8 disks.

I'm playing with this plus other options.


EDITED:

More info, with these parameters plus this on grub:

DiskIdxMap=0C00 SataPortMap=4A SasIdxMap=1             5-12, 8 disks in total

DiskIdxMap=0C00 SataPortMap=4C SasIdxMap=1             5-12, 8 disks in total

 

.......

 

Eureka!

DiskIdxMap=0C00 SataPortMap=1A SasIdxMap=1 

This works at least!!!!!

 

Thanks @pocopico for the help!!! ^_^

Edited by jukito
  • Like 1
Link to post
Share on other sites
17 minutes ago, pehun said:

Hello, 

Everybody seems to be quite happy with V7 with redpill... Would it be possible to have a tutorial?

I have a hp n54L 

Not happy, no. It remains early beta and is not recommended for production. That people are a bit more experienced in installing it and made tools for easier installation does not change that.

 

There is still unsolved problem of databases in Docker hanging system in 3615 (which you'd want for n54l), among other things.

Link to post
Share on other sites

Hi,

 

While waiting for the TTG return. I'm trying to start working on the platform ds3617xs.

 

You will find on github a first test version for very basic modifications of redpill-klm with small draft of the development of this platform
https://github.com/jimmyGALLAND/redpill-lkm/tree/develop

 

And also the loader configurations on https://github.com/jimmyGALLAND/redpill-load/tree/develop

 

I specify here that I am far from having the level of team thor in kernel development (and english !).

So I wouldn't be able to go too far in increasing compatibility with 3617xs.
Regarding the compatibles extensions I only put online at https://github.com/jimmyGALLAND/redpill-ext, the virtio (without loading virtio_balloon which crach !),
The acpi management module, and intel e1000 net driver.

 

Note: The bromolow 3.10.105 modules from pocopico may work, but i haven't tested. However, given that archi is broadwell not bromolow, I think that it is preferable to compile extensions modules specifically for this platform.

 

I have not tested the USB boot! However the SATA boot works fine, and install  ds3617xs-25556xs.pat package work !

 

Note that if you want to update to ds3617xs-25556xs update2, DO NOT NOW ! then a new loader will be needed!

 

In the ds3617xs-25556-2xs root package, there is no rd.gz, and zimage: They are contained in a .deb archive in the archive tree. I would try to modify the loader for support criticals updates.

 

Regarding the development for DSM 7.0.1 with ds3617xs, I saw you coming;).


What is interesting about this "broadwell" platform  is that in DSM 7 version the kernel goes to version 4.4.180+, like the ds918+. (work with apache>2.46 by example. With kernel 3.1: "Function not implemented: AH00141: Could not initialize random number generator")

 

However we can always notice the lack of publication of the GPL sources for this 4.4.180+ kernel "sadness and cry"


The problem is, all modules i compiled with the vanilla kernel 4.4.180+ have gone into crach or not load.
I need more investigation on this. However the ds3617xs 7.0.1 boot, is ALIVE !!!, and I have the /dev/synoboot[1-3] in my sights! I would post this in few days.

 

Have a good day

 

Edited by buggy25200
  • Like 8
  • Thanks 2
Link to post
Share on other sites
28 minutes ago, buggy25200 said:

However we can always notice the lack of publication of the GPL sources for this 4.4.180+ kernel "sadness and cry"


The problem is, all modules i compiled with the vanilla kernel 4.4.180+ have gone into crach or not load.
I need more investigation on this. However the ds3617xs 7.0.1 boot, is ALIVE !!!, and I have the /dev/synoboot[1-3] in my sights! I would post this in few days.

 

Great start ! 

 

PM me, i think i have found a working routine for compiling the modules and extensions. Maybe we can work this out.

  • Like 3
Link to post
Share on other sites
On 12/12/2021 at 2:23 PM, root616 said:

Recently I build my loader with RedPill-helper v0.12 add VMxnet3 and acpid,  running at ESXI v7 platform physical SATA controller passthrough, booting with vdisk (IDE mode no V-SATA controller added) , install DSM pat file shows file corrupted, talent use fdisk command no boot related partitions found, define disk & port map NOT working just no disk drive warning. 

Then I try edit VM settings add a SATA controller(startup disk SATA mode, one v-SATA one on board SATA controller passthrough), all good. But at diskstation‘s storage manager physical slots all in unplug status disk number goes to over 30, although it works fine.

There is my question how can i work without virtual SATA controller, startup disk use IDE mode?

My build has one on board SATA controller 3 ports, 2 individual, 4 in 1 miniSAS port(SATA channel).

BTW RedPill-helper v0.12 after add exts use build-loader script there is no kernel module .ko file in default location needs to add manually then the script can copy as rp.ko

Screen Shot 2021-12-12 at 2.20.45 PM.png

Screen Shot 2021-12-12 at 2.21.29 PM.png

Do some digging myself, according to this post  modified to DiskIdxMap=0C00 SataPortMap=16 works for me perfect

 

 

Link to post
Share on other sites
10 hours ago, jukito said:

Eureka!

DiskIdxMap=0C00 SataPortMap=1A SasIdxMap=1 

This works at least!!!!!

I am surprised this works as SataPortMap is supposed to be a single decimal digit number from 1 to 9 (A can't be right for the 2nd controller), DiskIdxMap is a two digit hex value (which is used correct)..

 

i imagine the A was ignored all along and would work with SataPortMap=1 as well. The first controller is the one with the bootloader, which you set to a single slot and assigned the first drive on the controller to disk 13. Better to have a clean configuration that exactly reflects what it does than a "coincidental" configuration that just happens to work.

 

 

 

Edited by haydibe
Link to post
Share on other sites

Hi,

 

Il y a 7 heures, pocopico a dit :

Great start ! 

 

PM me, i think i have found a working routine for compiling the modules and extensions. Maybe we can work this out.

No problem, I will contact you.

I think you will have a lot of work to update your extension git ;)

Thank you

 

I have add support for ds3617xs DSM 6.2.4-25556 update 2.

https://github.com/jimmyGALLAND/redpill-load/commit/54f487c0de637f88206d4a7b2d07415a31e242e2

and of course base extension https://github.com/jimmyGALLAND/redpill-ext

 

To allow this, i add function in redpill-load to manage flashupdate deb package (required tool dpkg)

https://github.com/jimmyGALLAND/redpill-load/commit/66a6d3796bf75b0f9702e24a6fe3c672e71db042

 

The procedure is,

 

1) install the DSM 6.2.4-25556 update 2 package from DSM 6.2.4-25556 gui installation

https://global.download.synology.com/download/DSM/criticalupdate/update_pack/25556-2/synology_broadwell_3617xs.pat

 

2) Restart system on ds3617xs-6.2.4-25556u2 loader image build to terminate the migration/update.

 

Good evening ! Synoguy !

 

 

 

 

Capture DS3617xs.png

Edited by buggy25200
  • Like 4
Link to post
Share on other sites
31 minutes ago, haydibe said:

I am surprised this works as SataPortMap is supposed to be a single decimal digit number from 1 to 9 (A can't be right for the 2nd controller), DiskIdxMap is a two digit hex value (which is used correct)..

 

i imagine the A was ignored all along and would work with SataPortMap=1 as well. The first controller is the one with the bootloader, which you set to a single slot and assigned the first drive on the controller to disk 13. Better to have a clean configuration that exactly reflects what it does than a "coincidental" configuration that just happens to work.

 

 

 

But... If I cannot put more than 9 on sataportmap, how can I set to my 10 disks?

 

Now I'm trying to add a nvme disk (connected to pcie), but without success. It's not mandatory this last issue.

Link to post
Share on other sites
2 hours ago, jukito said:

But... If I cannot put more than 9 on sataportmap, how can I set to my 10 disks?

 

Now I'm trying to add a nvme disk (connected to pcie), but without success. It's not mandatory this last issue.

I solved my ESXI disk mapping problem according this post, you should check out

 

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.