after updated to 24.5.3 can't connect.

[eragon4k]

It shows and detected e1000e (intel I219-LM) but cant connect.

请填写以下信息.
Please fill in the following information.

Install ENV: (You can find it in the boot interface.)

• DMI: Thinkstation p520
• CPU: Xeon W-2135
• NIC: intel I219-LM

RR version: (You can find it in the update menu.)

• RR: 24.5.3
• addons:
• modules:
• lkms:

DSM:

• model: DS3622xs+
• version: 7.2.1-69057 update 5

Issue: can't connect after updating from 24.5.1 to 24.5.3 and 24.5.4 with (Priority use of official drivers: false or Priority use of official drivers: ture)

logs:

(请先看一下#173、#175、#226的内容)
(Plz review the content of #173, #175, #226 first)
...

... 如果你提供不了详细信息，那就等有缘人吧!
... If you can't provide detailed information, then wait for someone who is destined!

[wjz304]

check other model.
Or enable this options.

[eragon4k]

used RR Manager 2.0.19 from 24.5.1 to 24.5.3.

24.5.1 was working and stable. (checked and it was working with "Priority use of official drivers: false")

I'll give it a try "Priority use of official drivers: true" method.

[eragon4k]

Looks like it's not the driver issue.
I believe there is conflict when you setup static ip with in the DSM.

When the loader give and detects lan and it give initial IP address to connect but when you have static ip already set up inside DSM. It not responding from static ip and the loaders initial ip address.

And when it boots, I ping the loader's initial IP address, and it responds, and then it stops.

Now I'm going back to 24.5.1, removing the static IP from the DSM, and trying to update.

[wjz304]

The e1000e simulated by pve will continue to go up/down using the driver I compiled. Just use the official driver.
Of course, there are many models of e1000e, and it may not be suitable for all.
Just that the e1000e driver has not been updated recently.

[eragon4k]

i did tried "Priority use of official drivers: true" with 24.5.4 but the result was the same thing.

I'll try to rebuild the loader from scratch.

[eragon4k]

So I did a few tests.

1. I freshly built the loader and the "Priority use of official drivers: true" method with 24.5.4.
   Out comes with no success.

2. With version 24.5.1 removed DSM Static ip and updated to 24.5.4 with "Priority use of official drivers: true" and out come was no success.

For now going back to 24.5.1.

[wjz304]

取一下 pid vid

[eragon4k]

for usb drive?

[wjz304]

intel I219-LM

[wjz304]

#173 (comment)

[wjz304]

find [0200]

[eragon4k]

Can't find it.

The log is scrolling far too quickly.

There may be more logs on the top part of the screen.

[wjz304]

lspci -nn | grep 0200

[eragon4k]

I219-LM [8086:15b7]

Thank you

[snailium]

My loader lost model/architecture information after upgrade to 24.5.4. I had to rebuild the loader from scratch.

After that, DSM seems corrupted. It gave me the first setup wizard. I had to setup everything as new, and recover the configuration from Synology account.

There are too much hassle upgrade cross 24.5.2 version, which seems heavily restructuring in the loader.

[wjz304]

升级到 24.5.4 后，我的加载器丢失了模型/架构信息。我不得不从头开始重建装载机。

在那之后，DSM似乎已损坏。它给了我第一个设置向导。我必须将所有内容都设置为新的，并从 Synology 帐户中恢复配置。

跨 24.5.2 版本升级有太多麻烦，这似乎在加载器中进行了大量重组。

My loader lost model/architecture information after upgrade to 24.5.4. I had to rebuild the loader from scratch.

After that, DSM seems corrupted. It gave me the first setup wizard. I had to setup everything as new, and recover the configuration from Synology account.

There are too much hassle upgrade cross 24.5.2 version, which seems heavily restructuring in the loader.

Yes, the logic adjustment in 5.2 is significant, but it does not involve driver adjustment,
At that time, I was hesitant about whether to revise it to restrict updates from being allowed,

[wjz304]

I219-LM [8086:15b7]

Thank you

还好，官方的驱动也支持这个 pid&vid

[eragon4k]

I219-LM [8086:15b7]
Thank you

Fortunately, the official driver also supports this pid&vid

So, my understanding is the driver was removed after 24.5.1. Right?

[wjz304]

I219-LM [8086:15b7]
Thank you

Fortunately, the official driver also supports this pid&vid

So, my understanding is the driver was removed after 24.5.1. Right?

no, I don’t know why at the moment. I’ll try updating the driver version.

[eragon4k]

I219-LM [8086:15b7]
Thank you

Fortunately, the official driver also supports this pid&vid

So, my understanding is the driver was removed after 24.5.1. Right?

no, I don’t know why at the moment. I’ll try updating the driver version.

I did try with Priority use of official drivers: true as you mentioned before

[lyp49472060]

24.4.6升级到24.5.4一样找不到

[wjz304]

try add e1000e.KumeranLockLoss=1 to cmdline

[eragon4k]

try add e1000e.KumeranLockLoss=1 to cmdline

Is this reply for me or @lyp49472060?

[wjz304]

you

try add e1000e.KumeranLockLoss=1 to cmdline

Is this reply for me or @lyp49472060?

[eragon4k]

you

try add e1000e.KumeranLockLoss=1 to cmdline

Is this reply for me or @lyp49472060?

Understood. I'll try this later today and update you.

Thank you

[eragon4k]

you

try add e1000e.KumeranLockLoss=1 to cmdline

Is this reply for me or @lyp49472060?

so i tried with "e1000e.KumeranLockLoss=1". the result was the same and I just removed the ethernet cable and re-plugged it and it was getting a ping again.

therefore i removed "e1000e.KumeranLockLoss=1" and test it out to see if I could get a ping just by removing the ethernet cable and re-plugging it. Surprisingly I was getting a ping.

But after the recovery process it’s not responding even after unplugging and relugging the ethernet cable.

[wjz304]

How many NIC are there in total?

[eragon4k]

How many NIC are there in total?

Just one.
I am using a white label SN but it got banned after upgrade to 5.4.

[wjz304]

e1000e has another parameter e1000e.SmartPowerDownEnable=1 , You can also try it

[wjz304]

I use PVE to simulate e1000e, with a total of 5 simulated network cards. After adding e1000e.KumeranLockLoss=1 and netifsort addon, DHCP to IP works normally

[nillebor]

After the new update 24.6.1, the connection does not work. :(
How can I help to fix the error?

[wjz304]

Change this option to true and try

[lyp49472060]

24.6.1更新后，我的DSM依旧失联。24.4.6版本正常
网卡是intel 82599 10g，固定ip地址，ds920+,

[wjz304]

如果方便就远程（anydesk，todesk，向日葵）吧，QQ: 304403268，TG: https://t.me/wjz304

[lyp49472060]

24.6.1更新后，我的DSM依旧失联。24.4.6版本正常 网卡是intel 82599 10g，固定ip地址，ds920+,

ESXi-8.0U2c 确认和下图一致，

删除vmw_pvscsi，正常启动

[nillebor]

@wjz304,

Thanks, the booting and connecting works. :)
Can you just briefly say what the problem is and why it doesn't work with the default values?

[wjz304]

@wjz304,

Thanks, the booting and connecting works. :) Can you just briefly say what the problem is and why it doesn't work with the default values?

I just guess that it is related to the power management or memory of the network card.
Direct boot will skip the RR system, and the network card will be started under DSM
Indirect boot means that the network card is started under RR, and then kexec to the DSM system to start again. This process may cause power/memory abnormalities of the network card

[wjz304]

We still need to investigate the details, but it is not easy to investigate the existing logs for problems like this. I don't have the relevant hardware, so this is difficult.

[nillebor]

@wjz304,
This process may cause power/memory abnormalities of the network card

wouldn't it be better to make direct boot as standard?

[wjz304]

@wjz304,
This process may cause power/memory abnormalities of the network card

wouldn't it be better to make direct boot as standard?

There is no good or bad difference, the non-direct startup UI just displays more information

[eragon4k]

Change this option to true and try

I confirm that this method works.
Wish it could display more information, but this is better than not working.

[adiom123]

同样的问题，改为直接启动后正常连接

[wjz304]

https://github.com/RROrg/rr/releases/tag/24.6.7

[nillebor]

The problem is finally fixed with version 24.5.7. As already written in the thread here and here. I thought it was the same error!

Nevertheless, thank you for the many tests and the time spent. It was always very late or early. You're doing a great job!

This issue can be closed.
.
Many thanks for your fast fix @wjz304!

[wjz304]

The root cause is a modification in buildroot 24.02.2 -24.02.3.
Different environments may also be caused by different modifications, so some people appear in RR24.6.3, some people appear in RR24.6.4,... Currently, they are all included in the modification of 24.02.2 -24.02.3.
The huge modification record is difficult to confirm, so it is temporarily stopped at 24.02.2

[wjz304]

Close this one first, and create new issues if you have any questions later.

[nillebor]

Same Problem @ 24.7.2
Boot after enable direct boot works fine.

[wjz304]

Same Problem @ 24.7.2 Boot after enable direct boot works fine.

how 24.7.1, 24.7.0 ?

[nillebor]

from 24.7.1 > 24.7.2

[eragon4k]

Same Problem @ 24.7.2 Boot after enable direct boot works fine.

how 24.7.1, 24.7.0 ?

I had a issue with 24.7.0
But it was solved with "Power off display after boot: false"

[wjz304]

😔, The hardware environment is too complicated.

[nillebor]

I had a issue with 24.7.0 But it was solved with "Power off display after boot: false"

I would like to test the function. Unfortunately, I can't find them in the loader (advance settings?). I did the updates online. I still used a 720.

[eragon4k]

I had a issue with 24.7.0 But it was solved with "Power off display after boot: false"

I would like to test the function. Unfortunately, I can't find them in the loader (advance settings?). I did the updates online. I still used a 720.

It's under the advanced settings

[nillebor]

Not here:

i will be re-installing (ckean) the loader tomorrow.
Maybe the online update is not ok

[eragon4k]

Not here: i will be re-installing (ckean) the loader tomorrow. Maybe the online update is not ok

I believe it was removed on 24.7.2 also if the problem is related to nic, you have to use "direct boot"

[wjz304]

Some settings do not apply to Direct Boot, so they will be hidden when Direct Boot is on true.

[nillebor]

@wjz304,
Between the versions 24.6.7 and 24.7.1 the connection worked without problems (online & offline Update).
From version 24.5.3 -24.6.4 and now from 24.7.2 there are these problems again.