RROrg / rr

Redpill Recovery (arpl-i18n)
GNU General Public License v3.0
4.7k stars 801 forks source link

after updated to 24.5.3 can't connect. #963

Closed eragon4k closed 4 months ago

eragon4k commented 6 months ago

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.)

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

DSM:

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 commented 6 months ago

check other model. Or enable this options. image

eragon4k commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

取一下 pid vid

eragon4k commented 6 months ago

for usb drive?

wjz304 commented 6 months ago

intel I219-LM

wjz304 commented 6 months ago

https://github.com/RROrg/rr/issues/173#issuecomment-1715763449

wjz304 commented 6 months ago

find [0200]

eragon4k commented 6 months ago

Can't find it.

The log is scrolling far too quickly.

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

wjz304 commented 6 months ago

lspci -nn | grep 0200

eragon4k commented 6 months ago

I219-LM [8086:15b7]

Thank you

snailium commented 6 months ago

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 commented 6 months ago

升级到 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 commented 6 months ago

I219-LM [8086:15b7]

Thank you

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

eragon4k commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

24.4.6升级到24.5.4一样找不到

wjz304 commented 6 months ago

try add e1000e.KumeranLockLoss=1 to cmdline image

eragon4k commented 6 months ago

try add e1000e.KumeranLockLoss=1 to cmdline image

Is this reply for me or @lyp49472060?

wjz304 commented 6 months ago

you

try add e1000e.KumeranLockLoss=1 to cmdline image

Is this reply for me or @lyp49472060?

eragon4k commented 6 months ago

you

try add e1000e.KumeranLockLoss=1 to cmdline image

Is this reply for me or @lyp49472060?

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

Thank you

eragon4k commented 6 months ago

you

try add e1000e.KumeranLockLoss=1 to cmdline image

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 commented 5 months ago

How many NIC are there in total?

eragon4k commented 5 months ago

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 commented 5 months ago

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

wjz304 commented 5 months ago

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

eragon4k commented 5 months ago

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

I'll give it a try with the netifsort addon

ZMDLBX commented 5 months ago

24.5.5更新后,我的DSM依旧失联。网卡是Intel I219LM, cpu:Intel 10500,ds918+

nillebor commented 5 months ago

Same here 24.5.x with intel i5 8600 DS1621xs+ with DSM7.2 Old version works fine. Clean install and online update does the same problem > no connection.

eragon4k commented 5 months ago

netifsort

I was busy and didn't have time to test it out e1000e. KumeranLockLoss=1 and netifsort addon.  Today I tested out with 24.5.6, and the result was negative.

tried with e1000e. KumeranLockLoss=1 / netifsort addon and e1000e.SmartPowerDownEnable=1 / netifsort addon. also just with netifsort addon by itself.

I wonder what has changed from 24.5.1 to 24.5.6.

wjz304 commented 5 months ago

try RR shell sed -i 's|/etc/init.d/S41dhcpcd|#/etc/init.d/S41dhcpcd|g' /opt/rr/boot.sh /opt/rr/init.sh

eragon4k commented 5 months ago

try RR shell sed -i 's|/etc/init.d/S41dhcpcd|#/etc/init.d/S41dhcpcd|g' /opt/rr/boot.sh /opt/rr/init.sh

I had an expi9301ctblk and just added 9301 NIC and it works for now with 5.6. Do you know if the intel 1226v or rtl8125b is supported?

What is your recommendation for a 2.5g nic?

wjz304 commented 5 months ago

try RR shell sed -i 's|/etc/init.d/S41dhcpcd|#/etc/init.d/S41dhcpcd|g' /opt/rr/boot.sh /opt/rr/init.sh

I had an expi9301ctblk and just added 9301 NIC and it works for now with 5.6. Do you know if the intel 1226v or rtl8125b is supported?

What is your recommendation for a 2.5g nic?

i226 OK, (No one is currently not available), R8125* OK, (someone feeds that certain suffixes are unavailable, but no details are provided).

wjz304 commented 5 months ago

@eragon4k e1000e try https://github.com/RROrg/rr/releases/tag/24.6.0

eragon4k commented 5 months ago

@eragon4k e1000e try https://github.com/RROrg/rr/releases/tag/24.6.0

It didn't work. But one wierd behavior.

When it boots, it's not responding from the e1000e, so I plug it into expi9301 and it works, and then while it's turned on, I plug it back into the e1000e and it works.

so it's just not responding when it boots.

Package center package icons are missing with 24.6.0

nillebor commented 5 months ago

i'm still with the old version. also the current release does not work

My device: HP Elitedesk G4 800 with Intel I219-LM LAN. The error occurs only with DSM boot, reconnecting also does not work anything. Everything works as it should in the loader. Of course, clean installation.

Please help and fix it

wjz304 commented 5 months ago

e1000e.zip image

wjz304 commented 5 months ago

To be honest, I don't know why. Since 24.5.1, I haven't modified the driver-related functions. Some issues related to DHCP have also been rolled back in 24.6.0. This problem is a bit difficult to solve. I don't have a physical e1000e device. I use PVE virtual e1000e. There are no problems in various tests. I modified the driver again and tested it.

e1000e.zip image

nillebor commented 5 months ago

Unfortunately, I have not had any success. I tried 2 DS (gemenilake & broadwellnk) in both versions. The connection works up to the loader. After that, a connection (ping) is no longer possible. Even a reboot does not help.

nillebor commented 5 months ago

Static IP in loader does not work.

wjz304 commented 5 months ago

dmesg | grep e1000e lsmod | grep e1000e

snailium commented 5 months ago

Just some idea. Is it related to the SN/MAC settings? How is the MAC used and how does DSM use the supplied MAC value?

Maybe try to set mac1 and mac2 to be the real MAC of the NIC (instead of 00:11:32 ones) and see if that works.

wjz304 commented 5 months ago

Unfortunately, I have not had any success. I tried 2 DS (gemenilake & broadwellnk) in both versions. The connection works up to the loader. After that, a connection (ping) is no longer possible. Even a reboot does not help.

get pid vid (Used to confirm whether it only occurs in a certain model)

nillebor commented 5 months ago

dmesg | grep e1000e:

[   13.660450] e1000e: Intel(R) PRO/1000 Network Driver
[   13.660451] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   13.661506] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   13.810673] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[   13.876500] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) xx:xx:xx:xx:xx:xx
[   13.876503] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[   13.876644] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
[   18.547463] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Duplicate of #The correct Mac address is displayed, I just anonymized it.

lsmod | grep e1000e: e1000e 282624 0

the same result with true and false option (p): grafik

nillebor commented 5 months ago

I select the DS, DSM and add-ons. Then I build the loader and start it. Under 24.4.8 it works without problems. But I need the current modules because of NVMe. An update of the modules is not possible. The network connection is disconnected. Also in the router, the device is no longer displayed as connected.

grafik

snailium commented 5 months ago

I select the DS, DSM and add-ons. Then I build the loader and start it. Under 24.4.8 it works without problems. But I need the current modules because of NVMe. An update of the modules is not possible. The network connection is disconnected. Also in the router, the device is no longer displayed as connected.

grafik

What is skip_vendor_mac_interface?