Salamandar Posted December 8, 2020 Share Posted December 8, 2020 I ran the 5.8/5.9 kernel for weeks without any issues (no RAM unstability, no crash, no ethernet issue). Now I reinstalled the thing and came back to a 4.4 kernel to have USB-C support. The thing is… Once every hours, the 1GBps Ethernet disconnects. Once connected through serial port, I can check the port status and it's shown as `Unknown`. I can `ip link set down eth0; ip link set up eth0` to set it back up. Am I the only one with this issue ? Is it well known on 4.4 and solved on 5.9 ? 0 Quote Link to comment Share on other sites More sharing options...
aprayoga Posted December 8, 2020 Share Posted December 8, 2020 I don't recall if i ever have issue with 1G ethernet. Was it idle? regarding USB-C support, what do you want to do? Currently the only issue with USB C support in LK 5.9 is switching role "on the fly". 0 Quote Link to comment Share on other sites More sharing options...
Salamandar Posted December 9, 2020 Author Share Posted December 9, 2020 It sometimes disconnects while idle (my Home Assistant web gui does not update, and I discover hours later it had been disconnected), sometimes while transferring data. Quote regarding USB-C support, what do you want to do? Currently the only issue with USB C support in LK 5.9 is switching role "on the fly". OK, then I guess I will switch to `current`. Is there any easy switching procedure or should I just install `linux-current-image` ? 0 Quote Link to comment Share on other sites More sharing options...
aprayoga Posted December 10, 2020 Share Posted December 10, 2020 there are several other packages than 'linux-current-image' to switch. You could use armbian-config > System > Other to switch to current. That being said, we are still recommend to do fresh install using CURRENT image rather than switch from LEGACY. 0 Quote Link to comment Share on other sites More sharing options...
Salamandar Posted December 12, 2020 Author Share Posted December 12, 2020 Yeah, I tried a manual upgrade but /boot was too small, and it wouldn't reboot after a resize2fs. So I reinstalled my server, and eth1 is running without any issue ! Looks like it really was a legacy kernel issue. 0 Quote Link to comment Share on other sites More sharing options...
gprovost Posted December 14, 2020 Share Posted December 14, 2020 On 12/13/2020 at 3:20 AM, Salamandar said: Yeah, I tried a manual upgrade but /boot was too small, and it wouldn't reboot after a resize2fs Effectively there was an issue with /boot partition behind too small, it has been fixed in future build https://github.com/armbian/build/pull/2425 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.