TinyCore RedPill Loader (TCRP)

[Peter Suh]

3 hours ago, gericb said:

Sure, based on the 10EC, I would agree that it's obvious.  Given the whole merger path and development partnerships that Rivet had, it then begs the question, who's maintaining the driver development, Intel or Realtek.  Is Intel really relying on Realtek to regularly release driver updates, for a product line they own...messy to be sure.

 

Latest release combo driver pack from Intel, which includes the E3100G is 10.10.2023  Realtek on the other hand is 11.28.23  Sadly, the package was no help either.

 

Thanks for your detective feedback!

 

First, prepare a separate USB and try mshell.
If you are worried about damage to your already installed DSM data, please prepare a practice disk.
If you run into any problems, please send me the dmesg results.

Edited December 13, 2023 by Peter Suh

[vbz14216]

5 hours ago, gericb said:

Sure, based on the 10EC, I would agree that it's obvious.  Given the whole merger path and development partnerships that Rivet had, it then begs the question, who's maintaining the driver development, Intel or Realtek.  Is Intel really relying on Realtek to regularly release driver updates, for a product line they own...messy to be sure.

 

Latest release combo driver pack from Intel, which includes the E3100G is 10.10.2023  Realtek on the other hand is 11.28.23  Sadly, the package was no help either.

 

Thanks for your detective feedback!

 

https://forums.freebsd.org/threads/patching-igc-driver-to-support-killer-e3100g.86080/#post-577571

 

It indeed is a realtek NIC in disguise.

[gericb]

1 hour ago, vbz14216 said:

 

https://forums.freebsd.org/threads/patching-igc-driver-to-support-killer-e3100g.86080/#post-577571

 

It indeed is a realtek NIC in disguise.

Funny, I ran across this article too.  There was another one somewhere else, can't find it at the moment, creating the same driver confusions due to it's "self-reported" info.  🤣

[Peter Suh]

26 minutes ago, gericb said:

Funny, I ran across this article too.  There was another one somewhere else, can't find it at the moment, creating the same driver confusions due to it's "self-reported" info.  🤣

 

The device management of the company acquired by Intel is really a mess.

Maybe you're experiencing the same thing on Linux.

 

I don't remember your last post, but did you say you tried and failed on rr?

If you test in mshell and the same error repeats,

As per the article above, I will add a line to if_igc.c and compile it.

 

It may be necessary to adjust and distribute the modules.alias.4.json file to point to igc in the DDSML mode I mentioned last time.

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/modules.alias.4.json

 

It is correct to assume that all VID 10EC in this file is Intel, right?

[killseeker]

On 12/2/2023 at 1:44 AM, Peter Suh said:

 

Please try my mshell.

We recommend the new model SA6400, which uses kernel 5.
Fast transcoding is also possible in Haswell.

https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v1.0.0.0

 

Hi Peter Suh, I'm running a 3617xs with mpt3sas drivers to support my raid card. Underneath its an 8700k CPU with 64GB RAM. Would the SA6400 be an appropriate upgrade pathway? Is there anything special required to enable fast transcoding for the CPU?

 

I'm keen to upgrade as I'm still on an older version of your loader "0.9.5.0".

[Peter Suh]

18 minutes ago, killseeker said:

 

Hi Peter Suh, I'm running a 3617xs with mpt3sas drivers to support my raid card. Underneath its an 8700k CPU with 64GB RAM. Would the SA6400 be an appropriate upgrade pathway? Is there anything special required to enable fast transcoding for the CPU?

 

I'm keen to upgrade as I'm still on an older version of your loader "0.9.5.0".

 

Activation has been verified only for Intel 4th generation, 11th to 13th generation IGPU, which is the transcoding of SA6400.
I think the 8th generation will be difficult.

There is a DS918+ (Apollo Lake) that supports both transcoding and mpt3sas.
All Apollo Lake supported models support the above in the same way.
DS1019+, DS620slim etc...

 

Edited December 14, 2023 by Peter Suh

[Peter Suh]

11 hours ago, gericb said:

Funny, I ran across this article too.  There was another one somewhere else, can't find it at the moment, creating the same driver confusions due to it's "self-reported" info.  🤣

 

Torvalds' script is mentioned in the article linked above by @vbz14216
In the end, it was made to work with r8125.

https://forums.freebsd.org/threads/patching-igc-driver-to-support-killer-e3100g.86080/#post-577569

https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/realtek/r8169_main.c#L165

This script is also applied to my mshell module repo.
However, there is no such part in kernel 4.
It is applied to kernel 5, which only uses SA6400.

https://github.com/PeterSuh-Q3/arpl-modules/blob/main/src/5.x/drivers/net/ethernet/realtek/r8169_main.c#L177

It seems that the already distributed SA6400 supports KillerLAN E3100G.
Want to be the first to try the SA6400 model?

Could you please forget about running on Intel i225 like Windows OS and look forward to Killer LAN running on r8125?

[killseeker]

20 hours ago, Peter Suh said:

 

Activation has been verified only for Intel 4th generation, 11th to 13th generation IGPU, which is the transcoding of SA6400.
I think the 8th generation will be difficult.

There is a DS918+ (Apollo Lake) that supports both transcoding and mpt3sas.
All Apollo Lake supported models support the above in the same way.
DS1019+, DS620slim etc...

 

Thanks Peter Suh, it is great that these do support transcoding. They still are having issues reading information from the disks. This means I can't see disk temperatures or smart information at all using this version. Mpt3sas  does work correctly with ds3617xs (without these below errors),  so is likely a driver issue with DS918+, DS1019+ etc?

 

These messages are flooded in the /var/log/messages file.

 

Do you know if support for 8th Gen or others is still being worked on for Kernel 5? Would be great to be able to move to the latest versions  

 

2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name

 

[thegremlin]

On 12/14/2023 at 4:03 PM, Peter Suh said:

 

Torvalds' script is mentioned in the article linked above by @vbz14216
In the end, it was made to work with r8125.

https://forums.freebsd.org/threads/patching-igc-driver-to-support-killer-e3100g.86080/#post-577569

https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/realtek/r8169_main.c#L165

This script is also applied to my mshell module repo.
However, there is no such part in kernel 4.
It is applied to kernel 5, which only uses SA6400.

https://github.com/PeterSuh-Q3/arpl-modules/blob/main/src/5.x/drivers/net/ethernet/realtek/r8169_main.c#L177

It seems that the already distributed SA6400 supports KillerLAN E3100G.
Want to be the first to try the SA6400 model?

Could you please forget about running on Intel i225 like Windows OS and look forward to Killer LAN running on r8125?

 

Hy,

it's possible to Update a Synology DS3617xs DSM 6.2.3-25426 BareMetal Installion (24 Slots / 19 Disks used) with your Loader the actual 7.x Version ?

Would it continue seamlessly? With Virtual Machine Manager / Plex and all Shares?

Does it make sense to take an intermediate step during the update? When I update I see DSM 7.0.1. Should you install this first before going to a higher version?

Best regards

Steven

 

Edited December 15, 2023 by thegremlin

[Peter Suh]

10 hours ago, thegremlin said:

 

Hy,

it's possible to Update a Synology DS3617xs DSM 6.2.3-25426 BareMetal Installion (24 Slots / 19 Disks used) with your Loader the actual 7.x Version ?

Would it continue seamlessly? With Virtual Machine Manager / Plex and all Shares?

Does it make sense to take an intermediate step during the update? When I update I see DSM 7.0.1. Should you install this first before going to a higher version?

Best regards

Steven

 

 

There is no need to go through intermediate versions.
Process upgrade and migration directly to DSM 7.2.1.

[Peter Suh]

On 12/15/2023 at 11:06 AM, killseeker said:

Thanks Peter Suh, it is great that these do support transcoding. They still are having issues reading information from the disks. This means I can't see disk temperatures or smart information at all using this version. Mpt3sas  does work correctly with ds3617xs (without these below errors),  so is likely a driver issue with DS918+, DS1019+ etc?

 

These messages are flooded in the /var/log/messages file.

 

Do you know if support for 8th Gen or others is still being worked on for Kernel 5? Would be great to be able to move to the latest versions  

 

2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name

 

 

I recently applied S.M.A.R.T activation of HBA (mpt3sas) on DS918+.
It looks like there are still some problems left.

 

I don't know if you can use a translator to translate this post from the Korean server forum where I work.

 

https://svrforum.com/nas/1068754

We conducted transcoding tests on Kernel 5 SA6400 for all generations from Intel's 1st generation.
This content also includes feedback from users.

I thought there was already feedback on the 8th generation, but I was mistaken.
No users have given any feedback yet.

 

And if transcoding acceleration doesn't work, the only thing you can adjust is
/sys/module/i915/parameters/enable_guc.

 

I use a setting of 2 or 3, but I'm not sure what each number means.

->

I found a setup guide for i915.enable_guc .

https://wiki.archlinux.org/title/intel_graphics#Enable_GuC_/_HuC_firmware_loading

Edited December 16, 2023 by Peter Suh

[killseeker]

53 minutes ago, Peter Suh said:

 

I recently applied S.M.A.R.T activation of HBA (mpt3sas) on DS918+.
It looks like there are still some problems left.

 

I don't know if you can use a translator to translate this post from the Korean server forum where I work.

 

https://svrforum.com/nas/1068754

We conducted transcoding tests on Kernel 5 SA6400 for all generations from Intel's 1st generation.
This content also includes feedback from users.

I thought there was already feedback on the 8th generation, but I was mistaken.
No users have given any feedback yet.

 

And if transcoding acceleration doesn't work, the only thing you can adjust is
/sys/module/i915/parameters/enable_guc.

 

I use a setting of 2 or 3, but I'm not sure what each number means.

->

I found a setup guide for i915.enable_guc .

https://wiki.archlinux.org/title/intel_graphics#Enable_GuC_/_HuC_firmware_loading

Thank you so much for sharing Peter Suh, this is awesome

 

I think I might be doing something wrong, I cant seem to change the /sys/module/i915/parameters/enable_guc with vi or by echoing an update? Is there another way to correctly update it with a new value?

 

using vi to update:

"/sys/module/i915/parameters/enable_guc"
"/sys/module/i915/parameters/enable_guc" E514: Write error (file system full?)
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!

 

trying to update with echo:

root@slave:/# sudo echo 2 > /sys/module/i915/parameters/enable_guc
-name: /sys/module/i915/parameters/enable_guc: Permission denied
 

I can see the device in transcoder:

 

As well as DRI in the system folders:

 

Just everything is software transcoding:

 

Edited December 16, 2023 by killseeker

[Peter Suh]

1 hour ago, killseeker said:

Thank you so much for sharing Peter Suh, this is awesome

 

I think I might be doing something wrong, I cant seem to change the /sys/module/i915/parameters/enable_guc with vi or by echoing an update? Is there another way to correctly update it with a new value?

 

using vi to update:

"/sys/module/i915/parameters/enable_guc"
"/sys/module/i915/parameters/enable_guc" E514: Write error (file system full?)
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!

 

trying to update with echo:

root@slave:/# sudo echo 2 > /sys/module/i915/parameters/enable_guc
-name: /sys/module/i915/parameters/enable_guc: Permission denied
 

I can see the device in transcoder:

 

As well as DRI in the system folders:

 

Just everything is software transcoding:

 

 

It seems that sudo is being used redundantly when the user is already a root account.
It looks like you have a plex pass since you can select the hw transcoding device.

 

Processing using i915.enable_guc to enable hw transcoding device acceleration has not yet had successful feedback for generations 5 through 10.
The situation seems to be the same for the 8th generation.

 

@MoetaYuko

, the i915 developer for sa6400, couldn't tell me any more about how to enable it.

 

 

 

[thegremlin]

7 hours ago, Peter Suh said:

 

There is no need to go through intermediate versions.
Process upgrade and migration directly to DSM 7.2.1.

 

Thank you very much. 

My system (Supermicro X9DRi-F / 2x Xeon E5-2670 @2.6/3.3 GHz % 192 GB RAM) has 4 LSI SAS controllers to which the SATA HDDs are connected. That's why I haven't dared to make an update yet. Do these controllers work now? I had often read that these were supposed to cause problems and couldn't be found.

[gericb]

On 12/14/2023 at 9:03 AM, Peter Suh said:

 

Torvalds' script is mentioned in the article linked above by @vbz14216
In the end, it was made to work with r8125.

https://forums.freebsd.org/threads/patching-igc-driver-to-support-killer-e3100g.86080/#post-577569

https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/realtek/r8169_main.c#L165

This script is also applied to my mshell module repo.
However, there is no such part in kernel 4.
It is applied to kernel 5, which only uses SA6400.

https://github.com/PeterSuh-Q3/arpl-modules/blob/main/src/5.x/drivers/net/ethernet/realtek/r8169_main.c#L177

It seems that the already distributed SA6400 supports KillerLAN E3100G.
Want to be the first to try the SA6400 model?

Could you please forget about running on Intel i225 like Windows OS and look forward to Killer LAN running on r8125?

"The device management of the company acquired by Intel is really a mess." Very much so, yes!

 

Thanks for your attention to detail and application of scripts as it relates to this part/driver.  Good to know that the SA6400 already has OEM support for the E3100G.

 

I'll definitely try a SA6400 build, and testing the HW transcoding as well.

[Hackaro1]

HELP!

 

@Peter Suh

 

I had a corruption of my USB stick that led to DSM not properly loading. 

So I remake the loader with a new USB stick using your TCRP v. 1.0.0.5 and built the loader with DSM_DS920+_64570.pat because I have on my DS920+  the DSM 7.2-64570 Update 1 .

 

Everything went smoothly during the rebuild process and now I can access my NAS again as expected BUT ... there is a BIG problem: the storage manager app doesn't start, I launch it and stay there forever... and doesn't open. I've checked every log and there is zero errors and zero warnings but simply the storage manager doesn't work!  

 

Resource monitor is ok, usage is at 3/5% of CPU and RAM. 

 

I suspect there is some kind of problem with my two NVMEs that work as cache drives (R/W), but I couldn't detach them when the problem occurred. And I cannot unmount them now because I don't know if I can do that from SSH (it's enabled, thanks God!) and how. I don't even know how I can flush their cache and rebuild it. 

 

What can I do now? Any help is welcome! 

 

update: to me it seems that there is soma sort of cache still in place because: 

$ mount -t btrfs
/dev/mapper/cachedev_0 on /volume1 type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)
/dev/mapper/cachedev_0 on /volume1/@docker type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)
/dev/mapper/cachedev_0 on /volume1/@docker/btrfs type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)

 

Edited December 18, 2023 by Hackaro1
adding info

[Peter Suh]

HELP!
 
@Peter Suh
 
I had a corruption of my USB stick that led to DSM not properly loading. 
So I remake the loader with a new USB stick using your TCRP v. 1.0.0.5 and built the loader with DSM_DS920+_64570.pat because I have on my DS920+  the DSM 7.2-64570 Update 1 .
 
Everything went smoothly during the rebuild process and now I can access my NAS again as expected BUT ... there is a BIG problem: the storage manager app doesn't start, I launch it and stay there forever... and doesn't open. I've checked every log and there is zero errors and zero warnings but simply the storage manager doesn't work!  
 
Resource monitor is ok, usage is at 3/5% of CPU and RAM. 
 
I suspect there is some kind of problem with my two NVMEs that work as cache drives (R/W), but I couldn't detach them when the problem occurred. And I cannot unmount them now because I don't know if I can do that from SSH (it's enabled, thanks God!) and how. I don't even know how I can flush their cache and rebuild it. 
 
What can I do now? Any help is welcome! 
 
update: to me it seems that there is soma sort of cache still in place because: 

$ mount -t btrfs/dev/mapper/cachedev_0 on /volume1 type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)/dev/mapper/cachedev_0 on /volume1/@docker type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)/dev/mapper/cachedev_0 on /volume1/@docker/btrfs type btrfs (rw,nodev,relatime,ssd,synoacl,nospace_cache,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno)

 

I don't know how to activate the storage manager with a command. But in the past I also experienced the same error as you and I solved it by reinstalling DSM. All settings will be initialized. Please back up your settings before initialization and use them for recovery. Reinstallation is possible in junior mode and enters with the J key within 7 seconds of friend booting.


Sent from my iPhone using Tapatalk

[Hackaro1]

1 hour ago, Peter Suh said:

I don't know how to activate the storage manager with a command. But in the past I also experienced the same error as you and I solved it by reinstalling DSM. All settings will be initialized. Please back up your settings before initialization and use them for recovery. Reinstallation is possible in junior mode and enters with the J key within 7 seconds of friend booting.


Sent from my iPhone using Tapatalk

 

Thanks for the reply! I made as for your instructions but no joy ! After re-installing DSM the storage manager still doesn't start ... I have the only option to update to the latest DSM ... do you suggest this? Or can I unmount SAFELY the cache drives?! I'm VERY afraid to damage my raid volume ... @Peter Suh

 

 Have to add that I got the warning to be low on free space because I'm under 20% of free storage space but, after restoring DSM's settings, that warning was put at 5% ... so there is some problem in the storage manager app !!! 

Edited December 18, 2023 by Hackaro1
additional info

[siri_uk]

Hi guys I'm pulling my hair out with the loader, I've been using arpl but wanted to swap to repill with m shell. I create the loader, boot, the loader comes up then the build menu, I build based on ds3622xs  (I use gen 8 microserver with xeon cpu). I set the model, serial, mac 1 & 2, leave the rest of the settings and click build loader, the server reboots but straight to the build loader again and serial etc are wiped, what am I doing wrong.

 

TIA

Edited December 18, 2023 by siri_uk

[Peter Suh]

4 hours ago, Hackaro1 said:

 

Thanks for the reply! I made as for your instructions but no joy ! After re-installing DSM the storage manager still doesn't start ... I have the only option to update to the latest DSM ... do you suggest this? Or can I unmount SAFELY the cache drives?! I'm VERY afraid to damage my raid volume ... @Peter Suh

 

 Have to add that I got the warning to be low on free space because I'm under 20% of free storage space but, after restoring DSM's settings, that warning was put at 5% ... so there is some problem in the storage manager app !!! 

 

It's a bit strange that the storage manager won't open due to insufficient storage space.
I saw a user I know using the disk to 100% free space and 0% free space.
In that state, the repository manager was captured and shown to us.

 

I have one other suggestion.
Install DS920+ with the same version as yours on a new, clean disk.
There is also a way to have both RAID disks and cache disks installed and recognized. It is highly likely that DSM will be initialized during this process.

[Peter Suh]

26 minutes ago, siri_uk said:

Hi guys I'm pulling my hair out with the loader, I've been using arpl but wanted to swap to repill with m shell. I create the loader, boot, the loader comes up then the build menu, I build based on ds3622xs  (I use gen 8 microserver with xeon cpu). I set the model, serial, mac 1 & 2, leave the rest of the settings and click build loader, the server reboots but straight to the build loader again and serial etc are wiped, what am I doing wrong.

 

TIA

 

Please upload a screen capture showing 4 windows before the loader build is completed.

 

[Hackaro1]

29 minutes ago, Peter Suh said:

 

It's a bit strange that the storage manager won't open due to insufficient storage space.
I saw a user I know using the disk to 100% free space and 0% free space.
In that state, the repository manager was captured and shown to us.

 

I have one other suggestion.
Install DS920+ with the same version as yours on a new, clean disk.
There is also a way to have both RAID disks and cache disks installed and recognized. It is highly likely that DSM will be initialized during this process.

Thanks 😊! I will give it a try… but if I use a fresh RAID disk is it better to physically detach both the actual NVME disks I’m using as cache?

[killseeker]

On 12/16/2023 at 2:45 PM, Peter Suh said:

 

I recently applied S.M.A.R.T activation of HBA (mpt3sas) on DS918+.
It looks like there are still some problems left.

@Peter Suh, if you need anyone to test any further improvements to the mpt3sas on DS918+ hit me up, I'm keen to help get them fixed

 

If you need any info from my system let me know what I can share.

[Peter Suh]

1 hour ago, killseeker said:

@Peter Suh, if you need anyone to test any further improvements to the mpt3sas on DS918+ hit me up, I'm keen to help get them fixed

 

If you need any info from my system let me know what I can share.

 

In fact, you need help from other developers to code for the stability of the module rather than from people to test it.
There are currently no people active in TTG.
Chinese developers have helped us a lot so far.

[Hackaro1]

On 12/18/2023 at 3:58 PM, Peter Suh said:

 

It's a bit strange that the storage manager won't open due to insufficient storage space.
I saw a user I know using the disk to 100% free space and 0% free space.
In that state, the repository manager was captured and shown to us.

 

I have one other suggestion.
Install DS920+ with the same version as yours on a new, clean disk.
There is also a way to have both RAID disks and cache disks installed and recognized. It is highly likely that DSM will be initialized during this process.

 

@Peter Suh

SOLVED !!!! I report here so that it can be helpful for others. 

 

The problem raised when my USB stick failed, at that point my NAS was on DSM 7.2 64570 Update 1. When I rebuilt the loader with your TCRP loader (v. 1.0.1.0) and built it with old v. 64570 I didn’t know you was referring to the Update 3 version of that DSM. That probably causes the problem of Storage Manger that was not opening. 

Infact I was able to replicate the problem with a new, fresh disk. I built a new USB stick from scratch and I went for DSM 64570 in your TCRP builder, and even with a new HDD and new install the Storage Manger didn’t open up. 

Now I have upgraded everything to DSM 7.2.1 Update 3 (69057-3) and on my RAID array everything is running smoothly as before! So thanks! 😊

 

Just 1 more question for you: my NAS have two 1 Gb ports, both of them with original Syno MAC addresses, and both QC and DDNS services are working like a charm; as I don’t want to mess up with those services but I’d like to add a 10Gb eth card to speed up things over my home network, I’m thinking to buy an original Synology card, like Synology E10G18-T1, in order to have an “official” MAC address to deal with. The problem may be that DS920+ doesn’t support any ethernet card expansion so do you think it can work? Will I need to rebuild the USB stick?