Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)

pocopico

By pocopico
in Loaders

 Share

Recommended Posts

loveburn Regular Member

loveburn

Posted
Posted (edited)
50 минут назад, nemesis122 сказал:

Maybe 3617xs DSM 7 and 3622xs cant running o a gen8 ?

with 3617 with 7.142661 



[    2.714707] Call Trace:
[    2.715531]  [<ffffffff812dca8b>] dump_stack+0x4d/0x72
[    2.717237]  [<ffffffff811216d7>] panic+0xc6/0x21e
[    2.718845]  [<ffffffff81099279>] ? vprintk_default+0x9/0x10
[    2.720799]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.722500]  [<ffffffffa000ef7f>] rp_crash+0x10/0x10 [redpill]
[    2.724441]  [<ffffffffa0025146>] init_+0x146/0x176 [redpill]
[    2.726350]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.728217]  [<ffffffff811620c9>] ? __vunmap+0x99/0xf0
[    2.730009]  [<ffffffff810bf16b>] do_init_module+0x5b/0x1d0
[    2.732223]  [<ffffffff810c0f44>] load_module+0x1be4/0x2080
[    2.734112]  [<ffffffff810bde40>] ? __symbol_put+0x40/0x40
[    2.735961]  [<ffffffff8118a3ac>] ? kernel_read+0x3c/0x50
[    2.737770]  [<ffffffff810c159d>] SYSC_finit_module+0x7d/0xa0
[    2.739767]  [<ffffffff810c15d9>] SyS_finit_module+0x9/0x10
[    2.741612]  [<ffffffff8156380a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
[    2.743783] ---[ end Kernel panic - not syncing: Fatal exception
[    2.745776] ------------[ cut here ]------------
[    2.747298] WARNING: CPU: 0 PID: 427 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x55/0x60()
[    2.750482] Modules linked in: redpill(OE+)
    2.780524] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 #42661
[    2.857137]  0000000000000000 ffff880309603db0 ffffffff812dca8b 0000000000000009
[    2.859833]  0000000000000000 ffff880309603de8 ffffffff81050f82 0000000000000001
[    2.862458]  ffff880309656340 0000000000000000 ffff8802fafb3fc0 ffff880309612380
[    2.865088] Call Trace:
[    2.865940]  <IRQ>  [<ffffffff812dca8b>] dump_stack+0x4d/0x72
[    2.867918]  [<ffffffff81050f82>] warn_slowpath_common+0x82/0xa0
[    2.869995]  [<ffffffff81051055>] warn_slowpath_null+0x15/0x20
[    2.871948]  [<ffffffff8102ff35>] native_smp_send_reschedule+0x55/0x60
[    2.874158]  [<ffffffff81085d19>] trigger_load_balance+0x209/0x210
[    2.876207]  [<ffffffff81078f38>] scheduler_tick+0xa8/0xd0
[    2.878034]  [<ffffffff810a9345>] update_process_times+0x45/0x70
[    2.880099]  [<ffffffff810b7090>] tick_sched_handle.isra.21+0x20/0x50
[    2.882236]  [<ffffffff810b72d8>] tick_sched_timer+0x38/0x70
[    2.884118]  [<ffffffff810b72a0>] ? tick_sched_do_timer+0x30/0x30
[    2.886131]  [<ffffffff810a9b23>] __hrtimer_run_queues+0xe3/0x250
[    2.888151]  [<ffffffff810aa1fb>] hrtimer_interrupt+0xab/0x180
[    2.890157]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.891872]  [<ffffffff81031d6d>] local_apic_timer_interrupt+0x3d/0x40
[    2.894036]  [<ffffffff8103263e>] smp_apic_timer_interrupt+0x3e/0x60
[    2.896144]  [<ffffffff8156459b>] apic_timer_interrupt+0x9b/0xa0
[    2.898148]  <EOI>  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.900197]  [<ffffffff811217eb>] ? panic+0x1da/0x21e
[    2.901888]  [<ffffffff81099279>] ? vprintk_default+0x9/0x10
[    2.903777]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.905474]  [<ffffffffa000ef7f>] rp_crash+0x10/0x10 [redpill]
[    2.907454]  [<ffffffffa0025146>] init_+0x146/0x176 [redpill]
[    2.909475]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.911386]  [<ffffffff811620c9>] ? __vunmap+0x99/0xf0
[    2.913061]  [<ffffffff810bf16b>] do_init_module+0x5b/0x1d0
[    2.914862[<ffffffff810c0f44>] load_module+0x1be4/0x2080
[    3.016737]  [<ffffffff810bde40>] ? __symbol_put+0x40/0x40
[    3.018509]  [<ffffffff8118a3ac>] ? kernel_read+0x3c/0x50
[    3.020335]  [<ffffffff810c159d>] SYSC_finit_module+0x7d/0xa0
[    3.022199]  [<ffffffff810c15d9>] SyS_finit_module+0x9/0x10
[    3.024010]  [<ffffffff8156380a>] entry_SYSCALL_64_fastpath+0x1e/0x8e

 

Try to change firmware, and not use ILO during installation... And only use USB2 ports

 

entry_SYSCALL_64_fastpath+0x1e/0x8e (error when system stops booting during CPU register error... (Can't operate with 64bit instructions, ) sometimes this error can be fixed by microcode update (bios firmware update)

 

 

 

Edited by loveburn
Link to comment
Share on other sites
Badger Regular Member

Badger

Posted
Posted
16 minutes ago, Badger said:

Ok so I finally gave up on migrating and started from scratch.  I created a linux mint disk and am trying to delete the partitions on the hard drives (3 2TB Drives).  Gparted would not let me delete one of the partitions (locked).  I left that partition on each disk.... built a new 7.0.1 loader and upon boot and connection to the new DSM... it still forces me to "recover".  I know that won't work.  Can anyone council me on how to delete a locked partition?

 

 

 

This command seemed to do the trick   "dd if=/dev/zero of=/dev/sdX bs=512 count=1"

Link to comment
Share on other sites
IG-88 Guru Master

IG-88

Posted
Posted
20 hours ago, loveburn said:

When I tried install dsm 6.2.3 u3 via juns 1.04 loader, integrated i219v not be working...., It's work after using your extra lzma build...

But in my ASRock z370m itx-ac with built-in 2 nic (i219v and 211t) two nic worked from the box.... I don't know why))) but in Asus I must be use your extra lzma pack)

my extra.lzma has a newer driver then jun's original (that one was made years back), there can be newer revisions or phy chips that will need a driver made/compiled from newer driver source

at least intel does provide one driver fitting all cases (same for realtek), i also have seen drivers where every oem had its own revision with custom firmware files making it a puzzle game to get them all together to create a driver that fits all hardware available

  • Like 2
Link to comment
Share on other sites
loveburn Regular Member

loveburn

Posted
Posted
2 минуты назад, IG-88 сказал:

my extra.lzma has a newer driver then jun's original (that one was made years back), there can be newer revisions or phy chips that will need a driver made/compiled from newer driver source

I think firstly I try boot up redpill without any add-ons, and if PHY not be worked i try to use different drivers modules...

Link to comment
Share on other sites
IG-88 Guru Master

IG-88

Posted
Posted
9 hours ago, phone guy said:

Found a solution to getting ReakTek USB lan adapters to work. My onboard 2nd NIC port.

It seems we were fighting against dsm removing that function of supporting usb lan adapters, not having the correct r8152 driver at build. It required a modified r8152 driver that will load and run in dsm7 with its restrictions in place. This guy figured it out, and my second nic port worked immediately. though it still shows it default mac and not mac2= in user_config.json, I do not how to change its mac, if anyone can help with that.

 

https://github.com/bb-qq/r8152/releases

 

he has instruction, basically get his file in the right folder and presto, my second nic port eth1 internal but obviously on the usb bus not the pci bus. Instantly worked...

@pocopico needs to add this in the package building, that way it will just work on build. @IG-88 tried to help me with this too, so I hope he gets the chance to see it working and hopefully get it included in the next release or at least an easy add ext command.

 

the thing i can see that it might be a newer driver then @pocopico's, his might be the old one from kernel 4.4.180 and the one bb-qq uses as base is realtek's r8152.53.56-2.15.0 (one year old by now) , afair i used realtek's driver for my 6.2.3 extra.lzma

bb-qq added support for EDC-QUA3C-B and ASUS USB-C2500

(https://github.com/bb-qq/r8152/commits?author=bb-qq)

but as long as you dont have that specific one the reason was simply a outdated driver  and that was the reason i aske to check the log, it usually would show when the driver is loaded

Link to comment
Share on other sites
scoobdriver Advanced Member

scoobdriver

Posted
Posted
2 hours ago, RedCat said:

920+ 7.1 also successfully complied, booting, but dont find any hard drive :((

What can I try?

 

Same issue here on Proxmox . 

DS3622xs working fine on same hardware, same procedure . Can’t get Ds918+ 7.1 working from fresh or using postupdate , 7.0.1 working ok 

Can’t find Hard Drive with DS920+ (Added virtio ext )

  • Like 1
Link to comment
Share on other sites
coint_cho Junior Member

coint_cho

Posted
Posted (edited)

For anyone with the issue of machine shutting down after accessing setup pages http://[local IP]:5000 after finish installing pat and reboot, 1st check whether you have added the redpill.misc extension, if you have it added and it's still not working, it might be an issue with your CPU just plain not supported. I had the same problem in proxmox with a kvm64 CPU flag pass through to the VM. I passed through my host CPU E5-1275 v6 to it and it booted up straight without any issues. However I can't confirm nor deny completely that this is the issue but that's the only way I've circumvented the error. If I had to guess why, it might be something to do with the flags of your CPU.


E5-1276 v6 Host Passthrough

image.png.61df7a423f99e58fc7dd0e363dfc857b.png

 

KVM64 Passthrough

image.png.cd937d45ffb11dd353cf2f55cc6c629c.png

 

As you can see KVM64 has a lot of flags that host has but it just doesn't, which might be essential for DS3622xs+ to function properly since the original DS3622xs+ is based on Xeon D-1531. And older CPUs or some specific qemu CPU flags just doesn't have the proper CPU features flags passthrough to the VM. There's more sample sizes that'll be needed to make sure if this is the correct theory, as so far I've only done testing on one machine. Baremetal + VMs results input would be appreciated.

https://pve-devel.pve.proxmox.narkive.com/d1wiRhm0/kvm64-or-qemu64

Here are some of the flags of each CPU, there are for sure more google to be done on this matter.

Edited by coint_cho
  • Like 1
Link to comment
Share on other sites
IG-88 Guru Master

IG-88

Posted
Posted
29 minutes ago, loveburn said:
34 minutes ago, IG-88 said:

my extra.lzma has a newer driver then jun's original (that one was made years back), there can be newer revisions or phy chips that will need a driver made/compiled from newer driver source

I think firstly I try boot up redpill without any add-ons, and if PHY not be worked i try to use different drivers modules...

 

chip was referring the the network chip itself and phy chip to the chip responsible for the network physical layer https://en.wikipedia.org/wiki/PHY#PHY

both features of the hardware you use, if a older driver recognizes the the network chip but not the phy chip it will also result in a non working system, newer driver might have support for that newer phy chip and would work

it was often seen on 6.2.3 with intel onboard nic's and with realtek's r8125 (2.5G nic) and the usual fix was to use the latest driver

  • Like 1
Link to comment
Share on other sites
phone guy Super Member

phone guy

Posted
Posted
1 hour ago, Badger said:

Ok so I finally gave up on migrating and started from scratch.  I created a linux mint disk and am trying to delete the partitions on the hard drives (3 2TB Drives).  Gparted would not let me delete one of the partitions (locked).  I left that partition on each disk.... built a new 7.0.1 loader and upon boot and connection to the new DSM... it still forces me to "recover".  I know that won't work.  Can anyone council me on how to delete a locked partition?

 

 

I have used Disk Management tools in Windows 10, lets me delete (remove) any partition and makes drive look unformatted for fresh install.

 

 

24 minutes ago, IG-88 said:

 

the thing i can see that it might be a newer driver then @pocopico's, his might be the old one from kernel 4.4.180 and the one bb-qq uses as base is realtek's r8152.53.56-2.15.0 (one year old by now) , afair i used realtek's driver for my 6.2.3 extra.lzma

bb-qq added support for EDC-QUA3C-B and ASUS USB-C2500

(https://github.com/bb-qq/r8152/commits?author=bb-qq)

but as long as you dont have that specific one the reason was simply a outdated driver  and that was the reason i aske to check the log, it usually would show when the driver is loaded

On the next build, would I be able to add this bb-qq driver in rp before the build command (add ext url), or still must add it after the fact like I did now...? I would also like the mac2# to be spoofed, as mac2 is set and netif is set to 2 in user_config, but when the 2nd nic popped up working it was its original factory mac

I guess  @pocopico maybe he will look at it and either add it or refresh his r8152 to whatever latest version is, if you say its just an outdated driver.... I think lots of people are needing working support for realtek driver r8152... This unit I have cant be the only "internal" nic connected via usb bus. :)

Link to comment
Share on other sites
gadreel Super Member

gadreel

Posted
Posted
39 minutes ago, scoobdriver said:

 

Same issue here on Proxmox . 

DS3622xs working fine on same hardware, same procedure . Can’t get Ds918+ 7.1 working from fresh or using postupdate , 7.0.1 working ok 

Can’t find Hard Drive with DS920+ (Added virtio ext )

So do I...

Link to comment
Share on other sites
ditheo Junior Member

ditheo

Posted
Posted
40 minutes ago, coint_cho said:

For anyone with the issue of machine shutting down after accessing setup pages http://[local IP]:5000 after finish installing pat and reboot, 1st check whether you have added the redpill.misc extension, if you have it added and it's still not working, it might be an issue with your CPU just plain not supported. I had the same problem in proxmox with a kvm64 CPU flag pass through to the VM. I passed through my host CPU E5-1275 v6 to it and it booted up straight without any issues. However I can't confirm nor deny completely that this is the issue but that's the only way I've circumvented the error. If I had to guess why, it might be something to do with the flags of your CPU.


E5-1276 v6 Host Passthrough

image.png.61df7a423f99e58fc7dd0e363dfc857b.png

 

KVM64 Passthrough

image.png.cd937d45ffb11dd353cf2f55cc6c629c.png

 

As you can see KVM64 has a lot of flags that host has but it just doesn't, which might be essential for DS3622xs+ to function properly since the original DS3622xs+ is based on Xeon D-1531. And older CPUs or some specific qemu CPU flags just doesn't have the proper CPU features flags passthrough to the VM. There's more sample sizes that'll be needed to make sure if this is the correct theory, as so far I've only done testing on one machine. Baremetal + VMs results input would be appreciated.

https://pve-devel.pve.proxmox.narkive.com/d1wiRhm0/kvm64-or-qemu64

Here are some of the flags of each CPU, there are for sure more google to be done on this matter.

I think that you can set the cpu flags on proxmox. I will do a test tomorrow.  For now with the command I gave before , the system runs fine on 42661. 

Link to comment
Share on other sites
sam juan Regular Member

sam juan

Posted
Posted
On 4/9/2022 at 3:47 PM, Peter Suh said:

 

For users who are confused by multiple installation guides, I will define the purpose of each guide.

A. It is a TinyCore Redfill (shortened as TCRP) introductory document that installs only DSM 7.0.1.

 

 

 


B. It is a guide that utilizes postupdate action when DSM 7 is already installed and updates are needed.

 

 


C. This is a guide that requires the build process of TWOS STEP UPDATE (referred to as TSU for single installation of DSM 7.1).

 

 

 

 

 

thanks @Peter Suh @pocopico

B. works for me, updating from 7.0.1-42218 to 7.1.0-42661

C. did not worked for me, corrupted from 40% 41%

Link to comment
Share on other sites
sam juan Regular Member

sam juan

Posted
Posted
7 minutes ago, phone guy said:

Everybody saying the install corrupts at %... When you manually install dsm, are you pointing to the rp created pat file you moved from the cache folder of the usb?

Or installing (pointing) to a genuine synology downloaded pat file, taken directly from synology web site?

for me, when i tried the TSU, i copied the pat file from the cache folder of the usb;
then navigated to http://ip:5000 and load the pat file from cache; then it failed at 41%;

so i did the fresh install of 7.0.1-42218 first; then manual update to 7.1.0-42661; right before boot, i went to TCRP prompt and do the postupdate steps;
now i am running 7.1.0-42661;

Link to comment
Share on other sites
phone guy Super Member

phone guy

Posted
Posted

Everybody seem to do the process a little different.

 

I used genuine pat from synology, manually updated to 7.1

on reboot, got to tc ran commands and reboot into dsm 7.1

 

I have also been able to build straight to 7.1, using same tsu build process (build 701 clean build 7.1) and go straight to 7.1

I did not use the cached pat from the usb, I used genuine pat from synology....

 

Was I suppose to use pat from cache?

  • Like 1
Link to comment
Share on other sites
sam juan Regular Member

sam juan

Posted
Posted
13 minutes ago, NotHere said:

Hi hi. Did you ever get this working? I get the corrupted file over and over.....

no, i get 41% corrupted for: 
C. This is a guide that requires the build process of TWOS STEP UPDATE (referred to as TSU for single installation of DSM 7.1).

so what i did is:
B. It is a guide that utilizes postupdate action when DSM 7 is already installed and updates are needed.

see previous posts thanks.

Link to comment
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.

×
 Share
Go to topic listing
×
×
  • Create New...