Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

1 hour ago, Aigor said:

To avoid use of a too new GCC, can be possible use cross-tools from synology? 

Just tested using their tool chain (apollolake-gcc493_glibc220_linaro_x86_64-GPL.txz)  rather than Debian 8 with GNU GCC 4.9 and it does indeed work, built on Ubuntu 20.10 So this is probably the path of least resistance for this project is to use the proper tool chain as well.

 

START /linuxrc.syno
[    2.343812] redpill: module verification failed: signature and/or required key missing - tainting kernel
[    2.345495] <redpill/redpill_main.c:23> ================================================================================================
[    2.347283] <redpill/redpill_main.c:24> RedPill loading...

 

  • Like 1
Link to comment
Share on other sites

That's a lot of posts! You're quick and eager to test guys ;) We're trying to sort out through the posts and it actually gets hard even at this stage to decipher bugs from questions while keeping each bug/missing feature flow separately.

 

So in the future if you have obvious bugs with something exploding or not working on a specific platform but working on another etc please, can you add a ticket on GH? That way we can attach all files and screenshots for a given problem with all people reporting to a given issue.

 

To make it simpler to separate and not create 101 topics at this stage (where things are expected to be broken rather than configured) we added bugs to the repos.

Short rundown:

 

=====================

10 hours ago, GhostlyCrowd said:

@ThorGroup I only seem to have ttys0 output and ttys1 which i paste binned previously for you. Here is ttys0's output. 

Oh, sorry, we missed that. Your issue seems to be with the VID+PID combo as your previous ttyS log shows "<redpill/boot_device_shim.c:70> Found new device <vid=1d6b, pid=0002> - didn't match expected <vid=46f4, pid=0001>". If this looks like correct values for your USB stick you can simply change these values in the grub config on the 1st partition (or change them in user_config.json and regenerate the image).

 

 

9 hours ago, loomes said:

@ThorGroup When i set CPU to Host: (same with ALL flags set to off)

See below, flagged as bug.

 

8 hours ago, yanjun said:

A person showed a screenshot of his successful installation of 7.0 in the telegram.

 

(...)

 

redpill-load and cannot install version 7.0.

Damn open source (/s), that's faster than we were able to try :lol: In all seriousness we didn't include v7 to not add even more unknowns to the equation now.

Adding v7 to the loader generator is simple. It requires a new platform config and a kernel patch. We will definitely add it but we're first trying to stabilize v6 so that we are sure that bugs are due to some missing stuff rather than v7 differences.

 

 

8 hours ago, ilovepancakes said:

I re-compiled using Debian 8 and GCC-4.9 like recommended to make sure I have a perfect loader and I still get the file corrupted error 13 message when it gets to 56% on "Installing DSM...".

 

Convert the .img file to VMDK file using Starwind V2V Converter. It is free download on their site. Choose the options in there for ESXi compatible VMDKs then upload those and boot of that.

This is most likely caused by the RTC. Can you post the full install log from /var/log/messages?

 

 

8 hours ago, scoobdriver said:

Thanks. Looks like I may need to find a windows machine. Unless qemu-utils is an option. 

Toolset from QEMU is kind of a default go-to way of converting images between formats. We didn't even think about including that as we're used of Proxmox swallowing any image thrown at it... but hey, VMWare being VMWare.

 

8 hours ago, GhostlyCrowd said:

Just tested using their tool chain (apollolake-gcc493_glibc220_linaro_x86_64-GPL.txz)  rather than Debian 8 with GNU GCC 4.9 and it does indeed work, built on Ubuntu 20.10 So this is probably the path of least resistance for this project is to use the proper tool chain as well.

That is actually a great idea. The official toolchain will probably cause least friction. We approached the compilation like any other Linux v3 or v4 module without looking into syno-specific stuff.

Edited by ThorGroup
  • Like 5
  • Thanks 2
Link to comment
Share on other sites

22 minutes ago, ThorGroup said:

That is actually a great idea. The official toolchain will probably cause least friction. We approached the compilation like any other Linux v3 or v4 module without looking into syno-specific stuff.

I don't want to come across as ungrateful for your work. Banging it out on GNU GCC probably would have been fine, you hit it like intelligent people who know more then me. However mix in modern environments... and you're seeing the issues we have :)  Although seriously a docker might be the end game for click button for end users. Hell I like Dockers I'm lazy, I just wanted to point out less work for you. 

Link to comment
Share on other sites

19 hours ago, ilovepancakes said:

Convert the .img file to VMDK file using Starwind V2V Converter. It is free download on their site. Choose the options in there for ESXi compatible VMDKs then upload those and boot of that.

Thanks I spun up a windows VM and that did the trick . 

 

It starts to boot , but never discoverable (Using ESXi 6.7 , DS3615xs ) Possibly similar issue to @loomes ? I see the serial output (2) with lots or messages like below , nothing on serial (1)

 

[    3.517024] BUG: unable to handle kernel paging request at 0000000001f4b498
[    3.517026] IP: [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517028] PGD 3a879067 PUD 3aed6067 PMD 39e17067 PTE 8000000001bf7067
[    3.517029] Oops: 0001 [#31] SMP 
[    3.517031] Modules linked in: redpill(OF)
[    3.517032] CPU: 2 PID: 4913 Comm: ash Tainted: GF     D    O 3.10.105 #25556
[    3.517033] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018
[    3.517034] task: ffff88003dd79040 ti: ffff88003ad94000 task.ti: ffff88003ad94000
[    3.517036] RIP: 0010:[<ffffffff8127b794>]  [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517037] RSP: 0018:ffff88003ad97f28  EFLAGS: 00010206
[    3.517037] RAX: ffffffffa0000c10 RBX: ffffffffa0009500 RCX: 000000000000058b
[    3.517038] RDX: 0000000001f554e8 RSI: ffff880038246b60 RDI: 0000000001f4b499
[    3.517039] RBP: 0000000001f4b498 R08: 0000000000000000 R09: 0000000000000066
[    3.517039] R10: 000000000000058b R11: 0000000000000202 R12: 0000000001f4b510
[    3.517040] R13: 0000000001f554e8 R14: 0000000000000000 R15: 0000000000000000
[    3.517041] FS:  00007fce85811700(0000) GS:ffff88003fc80000(0000) knlGS:0000000000000000
[    3.517042] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    3.517042] CR2: 0000000001f4b498 CR3: 0000000039e6e000 CR4: 00000000003607e0
[    3.517043] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    3.517044] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    3.517045] Stack:
[    3.517046]  ffffffffa0000c36 0000000000000000 0000000000000000 0000000000000000
[    3.517048]  0000000000000000 ffffffff814cfdc4 0000000000000000 0000000001f554e8
[    3.517049]  0000000000000000 0000000001f4b510 0000000001f554e8 0000000001f4b498
[    3.517050] Call Trace:
[    3.517052]  [<ffffffffa0000c36>] ? shim_sys_execve+0x26/0x90 [redpill]
[    3.517054]  [<ffffffff814cfdc4>] ? system_call_fastpath+0x22/0x27
[    3.517062] Code: 0f 1f 80 00 00 00 00 48 83 c6 01 0f b6 4e ff 48 83 c2 01 84 c9 88 4a ff 75 ed f3 c3 66 66 2e 0f 1f 84 00 00 00 00 00 48 83 c7 01 <0f> b6 47 ff 48 83 c6 01 3a 46 ff 75 0f 84 c0 75 eb 31 c0 c3 0f 
[    3.517064] RIP  [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517065]  RSP <ffff88003ad97f28>
[    3.517065] CR2: 0000000001f4b498
[    3.517066] ---[ end trace 1310bcd7b39d15af ]---

 

Link to comment
Share on other sites

9 minutes ago, ilovepancakes said:

 

Where do I access this?

You can login using the serial interface, for example on proxmox 

qm terminal <vmid> -iface serial1  // or serial2

then login as root w/o pw and navigate to /var/log/messages

Link to comment
Share on other sites

6 minutes ago, smoojay said:

You can login using the serial interface

 

Hmm, I'm on ESXi and that is what I thought because in past with Jun's loader I add a serial port to VM then telnet to it and can access console. When I do that now though (added 3 serial ports total to see all outputs), I can see the console outputs and boot process but can't get a login prompt to show up. And I supposed to see the prompt somewhere else?

Link to comment
Share on other sites

4 minutes ago, ilovepancakes said:

 

Hmm, I'm on ESXi and that is what I thought because in past with Jun's loader I add a serial port to VM then telnet to it and can access console. When I do that now though (added 3 serial ports total to see all outputs), I can see the console outputs and boot process but can't get a login prompt to show up. And I supposed to see the prompt somewhere else?

after successful boot, you should see something like

..
:: Loading module hid ... [  OK  ]
:: Loading mo[   46.880017] usbcore: registered new interface driver usbhid
dule usbhid[   46.905318] usbhid: USB HID core driver
 ... [  OK  ]
:: Loading module syno_hddmon ... [FAILED]
============ Date ============
Wed Jul 28 15:38
Wed Jul 28 15:38:09 2021

DiskStation login:

then you are sure you are at the right port. sorry i don't know other ways to access the log.

Link to comment
Share on other sites

17 minutes ago, smoojay said:

after successful boot, you should see something like



..
:: Loading module hid ... [  OK  ]
:: Loading mo[   46.880017] usbcore: registered new interface driver usbhid
dule usbhid[   46.905318] usbhid: USB HID core driver
 ... [  OK  ]
:: Loading module syno_hddmon ... [FAILED]
============ Date ============
Wed Jul 28 15:38
Wed Jul 28 15:38:09 2021

DiskStation login:

then you are sure you are at the right port. sorry i don't know other ways to access the log.

 

This is exactly what I remember getting from Jun's loader, but I'm not seeing that login prompt here. To confirm, I am supposed to get that prompt even before DSM is actually installed? @ThorGroup requested my logs because I am getting the "File Corrupted" Error (13) message when trying to install DSM via redpill-load. If I am supposed to get that login before DSM is actually installed, then yeah I tried 3 serial ports at same time so far. 1st one shows initial boot then stops, 2nd shows 3 lines of gibberish, 3rd shows remaining boot process but then ends at "[   29.157663] usbhid: USB HID core driver" and hitting enter doesn't bring up a login prompt.

Edited by ilovepancakes
Link to comment
Share on other sites

8 minutes ago, smoojay said:

yes, the core os is already part of the image which you will get with the the redpill-loader

 

OK, I confirmed then the console is hanging after that last line and not showing a login prompt, despite the syno web interface still working and the VM being up. @ThorGroup because of that, can I get the /var/log/messages you requested another way or any idea why console is hanging after that line? This is the output of that 3rd serial port where console should show up: https://pastebin.com/nvVTtVC2

 

That shows from boot of VM to after I receive the Error 13, but as you can see, no login prompt ever shows up on console and hitting enter doesn't do anything.

Link to comment
Share on other sites

18 hours ago, GhostlyCrowd said:

I don't want to come across as ungrateful for your work. Banging it out on GNU GCC probably would have been fine, you hit it like intelligent people who know more then me. However mix in modern environments... and you're seeing the issues we have :)  Although seriously a docker might be the end game for click button for end users. Hell I like Dockers I'm lazy, I just wanted to point out less work for you. 

Oh no, quite the opposite! Your suggestion is really helpful and we're happy someone brought this up. We were actually laughing on a channel that nobody actually checked if syno has a toolkit for building extensions (we kind of assumed that they don't).

 

17 hours ago, Aigor said:

@ThorGroup

As far i Remember there Is a bash script to build toolchain, to avoid the use of synology dependant stuff, we can build our toolchain in the same way as Synology does 

Is there hardcoded command line used to build  into GCC ? 

 

We didn't dig into their toolchain yet but you're right - being independent from it is probably a wise idea. Since it's a kernel module we don't need any of their userland stuff so it's much easier to build it. Conceptually we just need to see how they use ancient GCC on new systems reliably + automatically download kernel sources for a given platform.

 

12 hours ago, mcdull said:

it would be great if someone can share the cow2 of the compiled image. The rest of us may help to test the procedure and compatibility.

At the current stage giving a premade solution is unwise as non-developers shouldn't use it as we're not certain as to stability (as we know some things are missing even if it passes the 24 and 48h test). Additionally, we're not sharing the image on GH as this gets into DMCA territory - the loader contains no copyrighted code of any sort while the final image has non-GPL copyrighted modules from the PAT. This is the reason why we're sharing a tool to build it rather than dropping an image.

 

7 hours ago, ilovepancakes said:

 

OK, I confirmed then the console is hanging after that last line and not showing a login prompt, despite the syno web interface still working and the VM being up. @ThorGroup because of that, can I get the /var/log/messages you requested another way or any idea why console is hanging after that line? This is the output of that 3rd serial port where console should show up: https://pastebin.com/nvVTtVC2

 

That shows from boot of VM to after I receive the Error 13, but as you can see, no login prompt ever shows up on console and hitting enter doesn't do anything.

That is.... strange. Can you share your exact config of hardware + exact version of the hypervisor you're running it on? It clearly went through the whole process and is working while not giving you the shell.

Can you also try tapping Ctrl+D (even if you're on a Mac still use Ctrl). It should trigger restart of the login process.

 

1 hour ago, wiruzdk said:

can someone post a guide on how to install this for us deadly people that are not linux experts 

Not at this stage. The current version is meant for development and intended for users with Linux experience. This isn't a beta release yet.

 

Link to comment
Share on other sites

41 minutes ago, ThorGroup said:

Can you also try tapping Ctrl+D (even if you're on a Mac still use Ctrl). It should trigger restart of the login process.

 

No dice. Console still seems to hang at that last line and won't present a login prompt despite the VM being okay otherwise. Here is my hardware config. I am running ESXi 7.0.1, build 17551050. I also tried with USB 2.0 controller instead of 3.1. The NIC is e1000e. The 128MB loader HDD is SCSI and the 50GB HDD is SATA. I couldn't seem to get DSM install wizard to find an HDD unless it was SATA.

Screen Shot 2021-07-30 at 7.46.45 PM.png

Link to comment
Share on other sites

15 hours ago, scoobdriver said:

Thanks I spun up a windows VM and that did the trick . 

 

It starts to boot , but never discoverable (Using ESXi 6.7 , DS3615xs ) Possibly similar issue to @loomes ? I see the serial output (2) with lots or messages like below , nothing on serial (1)

 



[    3.517024] BUG: unable to handle kernel paging request at 0000000001f4b498
[    3.517026] IP: [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517028] PGD 3a879067 PUD 3aed6067 PMD 39e17067 PTE 8000000001bf7067
[    3.517029] Oops: 0001 [#31] SMP 
[    3.517031] Modules linked in: redpill(OF)
[    3.517032] CPU: 2 PID: 4913 Comm: ash Tainted: GF     D    O 3.10.105 #25556
[    3.517033] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018
[    3.517034] task: ffff88003dd79040 ti: ffff88003ad94000 task.ti: ffff88003ad94000
[    3.517036] RIP: 0010:[<ffffffff8127b794>]  [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517037] RSP: 0018:ffff88003ad97f28  EFLAGS: 00010206
[    3.517037] RAX: ffffffffa0000c10 RBX: ffffffffa0009500 RCX: 000000000000058b
[    3.517038] RDX: 0000000001f554e8 RSI: ffff880038246b60 RDI: 0000000001f4b499
[    3.517039] RBP: 0000000001f4b498 R08: 0000000000000000 R09: 0000000000000066
[    3.517039] R10: 000000000000058b R11: 0000000000000202 R12: 0000000001f4b510
[    3.517040] R13: 0000000001f554e8 R14: 0000000000000000 R15: 0000000000000000
[    3.517041] FS:  00007fce85811700(0000) GS:ffff88003fc80000(0000) knlGS:0000000000000000
[    3.517042] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    3.517042] CR2: 0000000001f4b498 CR3: 0000000039e6e000 CR4: 00000000003607e0
[    3.517043] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    3.517044] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    3.517045] Stack:
[    3.517046]  ffffffffa0000c36 0000000000000000 0000000000000000 0000000000000000
[    3.517048]  0000000000000000 ffffffff814cfdc4 0000000000000000 0000000001f554e8
[    3.517049]  0000000000000000 0000000001f4b510 0000000001f554e8 0000000001f4b498
[    3.517050] Call Trace:
[    3.517052]  [<ffffffffa0000c36>] ? shim_sys_execve+0x26/0x90 [redpill]
[    3.517054]  [<ffffffff814cfdc4>] ? system_call_fastpath+0x22/0x27
[    3.517062] Code: 0f 1f 80 00 00 00 00 48 83 c6 01 0f b6 4e ff 48 83 c2 01 84 c9 88 4a ff 75 ed f3 c3 66 66 2e 0f 1f 84 00 00 00 00 00 48 83 c7 01 <0f> b6 47 ff 48 83 c6 01 3a 46 ff 75 0f 84 c0 75 eb 31 c0 c3 0f 
[    3.517064] RIP  [<ffffffff8127b794>] strcmp+0x4/0x30
[    3.517065]  RSP <ffff88003ad97f28>
[    3.517065] CR2: 0000000001f4b498
[    3.517066] ---[ end trace 1310bcd7b39d15af ]---


 

not having any joy with Esxi I tried to boot the .img in Synology VMM,  the machine now boots , and is discoverable  when I then try to upload the .pat it stops at approx 56% with an error 13 . Not sure I can add serial ports to VMM , is there anyway to check the logs ? 
1CD46897-3B8D-41D7-BE6D-4430CD766FB9.thumb.jpeg.4d6fec1c92509bb96ac6df05efc45e5e.jpeg

Edited by scoobdriver
Formatting
Link to comment
Share on other sites

15 minutes ago, Aigor said:

@scoobdriver

You can add serial Port to VM and you can connect to via putty, serial ports are virtual and you have to add TCP Port to connect to.

Ti view, Simply open Telnet session on esxi host where VM rum, into Port you have defined 

Thanks @Aigor I'm able to do this on Esxi . It was Synology VMM I don't see the options .. (The boot process appears to get further on VMM , allowing me to discover the the DSM and upload a pat file , but then fails ) 

Link to comment
Share on other sites

OK

i have succesfully created a 7.0-41890 loader.

redpill lkm created with pkgscripts-ng.

Mak config for the redpill loader and change some lines in the init patches.

Extracting the vmlinux and patched with: patch-ramdisk-check.php

Remake zImage with killers script.

Build it together and fire it up in Proxmox with a "e1000e" Lan Card.....

 

Comes up load redpill and bring me the install pat Webinterface.

So thats it.

When i install the pat it hangs at: vfat: "synoboot1 mounted, process=updater" forever.

 

When i kill the Updater Process the Machine shuts down, reboot and says a install is find.

Same procedure again.

 

Any Hints?

 

Tested it with the virtio module from the DSM_VirtualDSM_41890.pat but the also dont work.

 

[    4.316362] virtio: Unknown symbol pv_irq_ops (err 0)
[    4.316860] virtio: Unknown symbol pv_lock_ops (err 0)
[    4.322421] virtio: Unknown symbol pv_irq_ops (err 0)
[    4.322951] virtio: Unknown symbol pv_lock_ops (err 0)
insmod: can't insert '/lib/modules/virtio.ko': unknown symbol in module, or unknown parameter
[    4.330711] virtio_pci: Unknown symbol virtio_device_restore (err 0)
[    4.331513] virtio_pci: Unknown symbol virtio_config_changed (err 0)
[    4.332185] virtio_pci: Unknown symbol unregister_virtio_device (err 0)
[    4.332879] virtio_pci: Unknown symbol virtio_device_freeze (err 0)
[    4.333377] virtio_pci: Unknown symbol register_virtio_device (err 0)
[    4.337474] virtio_pci: Unknown symbol virtio_device_restore (err 0)
[    4.337970] virtio_pci: Unknown symbol virtio_config_changed (err 0)
[    4.338466] virtio_pci: Unknown symbol unregister_virtio_device (err 0)
[    4.338965] virtio_pci: Unknown symbol virtio_device_freeze (err 0)
[    4.339458] virtio_pci: Unknown symbol register_virtio_device (err 0)
insmod: can't insert '/lib/modules/virtio_pci.ko': unknown symbol in module, or unknown parameter
[    4.347155] virtio_blk: Unknown symbol register_virtio_driver (err 0)
[    4.347866] virtio_blk: Unknown symbol unregister_virtio_driver (err 0)
[    4.348588] virtio_blk: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.354371] virtio_blk: Unknown symbol register_virtio_driver (err 0)
[    4.355031] virtio_blk: Unknown symbol unregister_virtio_driver (err 0)
[    4.355691] virtio_blk: Unknown symbol virtio_check_driver_offered_feature (err 0)
insmod: can't insert '/lib/modules/virtio_blk.ko': unknown symbol in module, or unknown parameter
[    4.363892] virtio_net: Unknown symbol register_virtio_driver (err 0)
[    4.364616] virtio_net: Unknown symbol unregister_virtio_driver (err 0)
[    4.365303] virtio_net: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.372512] virtio_net: Unknown symbol register_virtio_driver (err 0)
[    4.373154] virtio_net: Unknown symbol unregister_virtio_driver (err 0)
[    4.373668] virtio_net: Unknown symbol virtio_check_driver_offered_feature (err 0)
insmod: can't insert '/lib/modules/virtio_net.ko': unknown symbol in module, or unknown parameter
[    4.382859] virtio_scsi: Unknown symbol register_virtio_driver (err 0)
[    4.383860] virtio_scsi: Unknown symbol unregister_virtio_driver (err 0)
[    4.384855] virtio_scsi: Unknown symbol pv_irq_ops (err 0)
[    4.385671] virtio_scsi: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.386819] virtio_scsi: Unknown symbol pv_lock_ops (err 0)
[    4.392298] virtio_scsi: Unknown symbol register_virtio_driver (err 0)
[    4.393243] virtio_scsi: Unknown symbol unregister_virtio_driver (err 0)
[    4.394227] virtio_scsi: Unknown symbol pv_irq_ops (err 0)
[    4.395044] virtio_scsi: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.396199] virtio_scsi: Unknown symbol pv_lock_ops (err 0)
insmod: can't insert '/lib/modules/virtio_scsi.ko': unknown symbol in module, or unknown parameter
[    4.403692] virtio_console: Unknown symbol register_virtio_driver (err 0)
[    4.404676] virtio_console: Unknown symbol hvc_remove (err 0)
[    4.405557] virtio_console: Unknown symbol unregister_virtio_driver (err 0)
[    4.406574] virtio_console: Unknown symbol pv_irq_ops (err 0)
[    4.407462] virtio_console: Unknown symbol hvc_kick (err 0)
[    4.408317] virtio_console: Unknown symbol hvc_alloc (err 0)
[    4.409122] virtio_console: Unknown symbol hvc_poll (err 0)
[    4.409919] virtio_console: Unknown symbol hvc_instantiate (err 0)
[    4.410843] virtio_console: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.411985] virtio_console: Unknown symbol __hvc_resize (err 0)
[    4.412509] virtio_console: Unknown symbol pv_lock_ops (err 0)
[    4.417429] virtio_console: Unknown symbol register_virtio_driver (err 0)
[    4.418463] virtio_console: Unknown symbol hvc_remove (err 0)
[    4.419309] virtio_console: Unknown symbol unregister_virtio_driver (err 0)
[    4.419738] virtio_console: Unknown symbol pv_irq_ops (err 0)
[    4.420268] virtio_console: Unknown symbol hvc_kick (err 0)
[    4.421096] virtio_console: Unknown symbol hvc_alloc (err 0)
[    4.421926] virtio_console: Unknown symbol hvc_poll (err 0)
[    4.422782] virtio_console: Unknown symbol hvc_instantiate (err 0)
[    4.423685] virtio_console: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.424838] virtio_console: Unknown symbol __hvc_resize (err 0)
[    4.425699] virtio_console: Unknown symbol pv_lock_ops (err 0)

 

Edited by loomes
Link to comment
Share on other sites

2 hours ago, loomes said:

OK

i have succesfully created a 7.0-41890 loader.

redpill lkm created with pkgscripts-ng.

Mak config for the redpill loader and change some lines in the init patches.

Extracting the vmlinux and patched with: patch-ramdisk-check.php

Remake zImage with killers script.

Build it together and fire it up in Proxmox with a "e1000e" Lan Card.....

 

Comes up load redpill and bring me the install pat Webinterface.

So thats it.

When i install the pat it hangs at: vfat: "synoboot1 mounted, process=updater" forever.

 

When i kill the Updater Process the Machine shuts down, reboot and says a install is find.

Same procedure again.

 

Any Hints?

 

Tested it with the virtio module from the DSM_VirtualDSM_41890.pat but the also dont work.

 


[    4.316362] virtio: Unknown symbol pv_irq_ops (err 0)
[    4.316860] virtio: Unknown symbol pv_lock_ops (err 0)
[    4.322421] virtio: Unknown symbol pv_irq_ops (err 0)
[    4.322951] virtio: Unknown symbol pv_lock_ops (err 0)
insmod: can't insert '/lib/modules/virtio.ko': unknown symbol in module, or unknown parameter
[    4.330711] virtio_pci: Unknown symbol virtio_device_restore (err 0)
[    4.331513] virtio_pci: Unknown symbol virtio_config_changed (err 0)
[    4.332185] virtio_pci: Unknown symbol unregister_virtio_device (err 0)
[    4.332879] virtio_pci: Unknown symbol virtio_device_freeze (err 0)
[    4.333377] virtio_pci: Unknown symbol register_virtio_device (err 0)
[    4.337474] virtio_pci: Unknown symbol virtio_device_restore (err 0)
[    4.337970] virtio_pci: Unknown symbol virtio_config_changed (err 0)
[    4.338466] virtio_pci: Unknown symbol unregister_virtio_device (err 0)
[    4.338965] virtio_pci: Unknown symbol virtio_device_freeze (err 0)
[    4.339458] virtio_pci: Unknown symbol register_virtio_device (err 0)
insmod: can't insert '/lib/modules/virtio_pci.ko': unknown symbol in module, or unknown parameter
[    4.347155] virtio_blk: Unknown symbol register_virtio_driver (err 0)
[    4.347866] virtio_blk: Unknown symbol unregister_virtio_driver (err 0)
[    4.348588] virtio_blk: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.354371] virtio_blk: Unknown symbol register_virtio_driver (err 0)
[    4.355031] virtio_blk: Unknown symbol unregister_virtio_driver (err 0)
[    4.355691] virtio_blk: Unknown symbol virtio_check_driver_offered_feature (err 0)
insmod: can't insert '/lib/modules/virtio_blk.ko': unknown symbol in module, or unknown parameter
[    4.363892] virtio_net: Unknown symbol register_virtio_driver (err 0)
[    4.364616] virtio_net: Unknown symbol unregister_virtio_driver (err 0)
[    4.365303] virtio_net: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.372512] virtio_net: Unknown symbol register_virtio_driver (err 0)
[    4.373154] virtio_net: Unknown symbol unregister_virtio_driver (err 0)
[    4.373668] virtio_net: Unknown symbol virtio_check_driver_offered_feature (err 0)
insmod: can't insert '/lib/modules/virtio_net.ko': unknown symbol in module, or unknown parameter
[    4.382859] virtio_scsi: Unknown symbol register_virtio_driver (err 0)
[    4.383860] virtio_scsi: Unknown symbol unregister_virtio_driver (err 0)
[    4.384855] virtio_scsi: Unknown symbol pv_irq_ops (err 0)
[    4.385671] virtio_scsi: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.386819] virtio_scsi: Unknown symbol pv_lock_ops (err 0)
[    4.392298] virtio_scsi: Unknown symbol register_virtio_driver (err 0)
[    4.393243] virtio_scsi: Unknown symbol unregister_virtio_driver (err 0)
[    4.394227] virtio_scsi: Unknown symbol pv_irq_ops (err 0)
[    4.395044] virtio_scsi: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.396199] virtio_scsi: Unknown symbol pv_lock_ops (err 0)
insmod: can't insert '/lib/modules/virtio_scsi.ko': unknown symbol in module, or unknown parameter
[    4.403692] virtio_console: Unknown symbol register_virtio_driver (err 0)
[    4.404676] virtio_console: Unknown symbol hvc_remove (err 0)
[    4.405557] virtio_console: Unknown symbol unregister_virtio_driver (err 0)
[    4.406574] virtio_console: Unknown symbol pv_irq_ops (err 0)
[    4.407462] virtio_console: Unknown symbol hvc_kick (err 0)
[    4.408317] virtio_console: Unknown symbol hvc_alloc (err 0)
[    4.409122] virtio_console: Unknown symbol hvc_poll (err 0)
[    4.409919] virtio_console: Unknown symbol hvc_instantiate (err 0)
[    4.410843] virtio_console: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.411985] virtio_console: Unknown symbol __hvc_resize (err 0)
[    4.412509] virtio_console: Unknown symbol pv_lock_ops (err 0)
[    4.417429] virtio_console: Unknown symbol register_virtio_driver (err 0)
[    4.418463] virtio_console: Unknown symbol hvc_remove (err 0)
[    4.419309] virtio_console: Unknown symbol unregister_virtio_driver (err 0)
[    4.419738] virtio_console: Unknown symbol pv_irq_ops (err 0)
[    4.420268] virtio_console: Unknown symbol hvc_kick (err 0)
[    4.421096] virtio_console: Unknown symbol hvc_alloc (err 0)
[    4.421926] virtio_console: Unknown symbol hvc_poll (err 0)
[    4.422782] virtio_console: Unknown symbol hvc_instantiate (err 0)
[    4.423685] virtio_console: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.424838] virtio_console: Unknown symbol __hvc_resize (err 0)
[    4.425699] virtio_console: Unknown symbol pv_lock_ops (err 0)

 

31 16:00:06 updater: updater.c:913 open /tmp/bootmnt/EFI/boot//SynoBootLoader.c
 31 16:00:06 updater: updater.c:968 This model does not contain KPTI config and
 31 16:00:06 updater: updater.c:1177 Failed to update KPTI config
 31 16:00:06 updater: updater.c:6557 failed to update factory partition, retry 0


actually I think we are stuck at this.

Link to comment
Share on other sites

got a little bit further :)

Create on the first Partition in the Bootloader following directory structure: EFI/boot

Then touch EFI/boot/SynoBootLoader.conf

 

Reboot and the Install procedure goes to 100% with automatic reboot.... but after that the Installer pops up again 😞

Link to comment
Share on other sites

Compiled lkm on Ubuntu 1404 desktop vm, loader on Debian 10. Upgraded (keep settings option) 25426 to 25556 ok. Installed Drive packages and Surveillance etc

Auto shutdown/start ok

Drive syncing with DSM7 on two real synos, testing ok so far

HP N36L n360t network card

3615xs

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...