likeme
-
Posts
6 -
Joined
-
Last visited
Posts posted by likeme
-
-
On 9/19/2022 at 10:38 AM, likeme said:
I encountered this problem on my Gigabyte motherboard, but only on the DS920+ model. And the result is the same whether it is ARPL, TCRP or TCRP-JUN.
This problem has existed since DSM7, and was finally solved in v0.4-alpha11. Many thanks for the efforts made for this.
-
On 9/17/2022 at 3:20 AM, fbelavenuto said:
There is an issue detected by a user that affects all loaders. I didn't know but it's old.
The synobios module corrupts the CMOS of some machines and when resetting the BIOS it drops to the "CMOS Checksum bad" screen.
More information:
https://github.com/fbelavenuto/arpl/issues/174
I encountered this problem on my Gigabyte motherboard, but only on the DS920+ model. And the result is the same whether it is ARPL, TCRP or TCRP-JUN.
-
35 minutes ago, pocopico said:
最安全的方法总是启动到 DSM 并检查 /sys/block/sata1/device/syno_block_infolrwxrwxrwx 1 root root 0 Apr 22 2022 sata1 -> ../devices/pci0000:00/0000:00:11.0/0000:02:03.0/ata1/host0/target0:0:0/0:0:0:0/block/sata1
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata2 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata31/host30/target30:0:0/30:0:0:0/block/sata2
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata3 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata32/host31/target31:0:0/31:0:0:0/block/sata3
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata4 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata33/host32/target32:0:0/32:0:0:0/block/sata4
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata5 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata34/host33/target33:0:0/33:0:0:0/block/sata5
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata6 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata35/host34/target34:0:0/34:0:0:0/block/sata6
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata7 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata36/host35/target35:0:0/35:0:0:0/block/sata7
SynologyNAS> cat /sys/block/sata1/device/syno_block_info
pciepath=00:11.0,03.0
ata_port_no=0
driver=ahci
SynologyNAS> cat /sys/block/sata2/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=0
driver=ahci
SynologyNAS> cat /sys/block/sata3/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=1
driver=ahci
SynologyNAS> cat /sys/block/sata4/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=2
driver=ahci
SynologyNAS> cat /sys/block/sata5/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=3
driver=ahci
SynologyNAS> cat /sys/block/sata6/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=4
driver=ahci
SynologyNAS> cat /sys/block/sata7/device/syno_block_info
pciepath=00:11.0,04.0
ata_port_no=5
driver=ahci
SynologyNAS>ds920p.dts
pcie_root = "00:11.0,04.0";
ata_port = <0x0>;......
pcie_root = "00:11.0,04.0";
ata_port = <0x1>;......
pcie_root = "00:11.0,04.0";
ata_port = <0x2>;
Still can't find the hard drive.
-
How to modify my ds920p.dts ?
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata1 -> ../devices/pci0000:00/0000:00:11.0/0000:02:03.0/ata1/host0/target0:0:0/0:0:0:0/block/sata1
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata2 -> ../devices/pci0000:00/0000:00:11.0/0000:02:03.0/ata2/host1/target1:0:0/1:0:0:0/block/sata2
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata3 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata32/host31/target31:0:0/31:0:0:0/block/sata3
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata4 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata33/host32/target32:0:0/32:0:0:0/block/sata4
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata5 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata34/host33/target33:0:0/33:0:0:0/block/sata5
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata6 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata35/host34/target34:0:0/34:0:0:0/block/sata6
lrwxrwxrwx 1 root root 0 Apr 22 2022 sata7 -> ../devices/pci0000:00/0000:00:11.0/0000:02:04.0/ata36/host35/target35:0:0/35:0:0:0/block/sata7tc@box:~$ lspci -tvnnq
-[0000:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190]
+-01.0-[01]--
+-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110]
+-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111]
+-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113]
+-07.7 VMware Virtual Machine Communication Interface [15ad:0740]
+-0f.0 VMware SVGA II Adapter [15ad:0405]
+-11.0-[02]--+-00.0 VMware USB1.1 UHCI Controller [15ad:0774]
| +-01.0 VMware USB2 EHCI Controller [15ad:0770]
| +-03.0 VMware SATA AHCI controller [15ad:07e0]
| \-04.0 VMware SATA AHCI controller [15ad:07e0]
+-15.0-[03]----00.0 Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
+-15.1-[04]--pcie_root = "00:11.0,04.0";
ata_port = <0x31>;and
pcie_root = "00:11.0,02:04.0";
ata_port = <0x31>;all not worked
-
38 minutes ago, Dvalin21 said:
@pocopico ./rploader.sh: line 1183: syntax error near unexpected token '}'
./rploader.sh line 1183: '}'Im getting the same error
I also came to feed back this question😁
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
Compiling "geminilake-7.1.1-42962" with V0.9.2.3, "CMOS Checksum bad" which has existed since history https://github.com/fbelavenuto/arpl/issues/174 problem still exists. The latest ARPL has been solved, I hope pocopico also work hard to solve this historical problem. Thank you.