Ximodel 1 Posted June 1, 2020 Share Posted June 1, 2020 (edited) edited Edited August 19, 2020 by Ximodel 0 Quote Link to post Share on other sites
Igor 2095 Posted June 1, 2020 Share Posted June 1, 2020 Send a merge request to this file https://github.com/armbian/build/blob/master/config/kernel/linux-sunxi64-current.config There will be a bug fix update - soon after we find a solution for this fatal problem. 0 Quote Link to post Share on other sites
Werner 318 Posted June 2, 2020 Share Posted June 2, 2020 Got missing here:https://github.com/armbian/build/commit/fea2ecb9f957101848bcf2af6b6b08ec44a5a526#diff-9d0bcdf961153323f063525ccdbca36d 0 Quote Link to post Share on other sites
dolphs 29 Posted June 4, 2020 Share Posted June 4, 2020 Hi, seems upgrading to 30 May release 20.05.01 I lost "bbr" as congestion control setting. Can this be put back in please? - TiA! - root@wgvpn01:/etc/sysctl.d# uname -a Linux wgvpn01 5.4.43-rockchip64 #20.05.1 SMP PREEMPT Sat May 30 13:30:37 CEST 2020 aarch64 GNU/Linux root@wgvpn01:/etc/sysctl.d# sysctl net.ipv4.tcp_available_congestion_control net.ipv4.tcp_available_congestion_control = reno cubic root@wgvpn01:/etc/sysctl.d# sysctl -p wg.conf net.core.default_qdisc = fq net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 65535 16777216 sysctl: setting key "net.ipv4.tcp_congestion_control": No such file or directory net.ipv4.tcp_congestion_control = bbr net.ipv4.tcp_fastopen = 3 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_slow_start_after_idle = 0 net.ipv4.tcp_mtu_probing = 1 0 Quote Link to post Share on other sites
dolphs 29 Posted June 4, 2020 Share Posted June 4, 2020 meanwhile read here things have been reported earlier this week, sorry for the additional request 0 Quote Link to post Share on other sites
Ximodel 1 Posted June 4, 2020 Author Share Posted June 4, 2020 the problem still exists after upgrading to armbian 20.05.1 but bbr does work in my another nanopineo2, which has 20.02.1 installed 0 Quote Link to post Share on other sites
dolphs 29 Posted June 4, 2020 Share Posted June 4, 2020 was hoping 20.05.2 solved things but alas, we have to wait a little more: # sysctl -p ovpn.conf sysctl: setting key "net.ipv4.tcp_congestion_control": No such file or directory net.ipv4.tcp_congestion_control = bbr # uname -a Linux wgvpn01 5.4.43-sunxi64 #20.05.2 SMP Tue Jun 2 17:20:17 CEST 2020 aarch64 GNU/Linux 0 Quote Link to post Share on other sites
Werner 318 Posted June 4, 2020 Share Posted June 4, 2020 Feel free to add it yourself and submit a PR 0 Quote Link to post Share on other sites
Igor 2095 Posted June 4, 2020 Share Posted June 4, 2020 1 hour ago, Ximodel said: the problem still exists after upgrading to armbian 20.05.1 Did you notice any information telling that this was included in the upgrade? Or that was it fixed in sources? Support terms:https://github.com/armbian/build#support Also when the problem will be fixed in sources, its not fully automatically yet to push it to the images. You are welcome to help out and improve the upgrading process. 0 Quote Link to post Share on other sites
dolphs 29 Posted June 4, 2020 Share Posted June 4, 2020 allritie then, proposed file change - hope did it proper way - 0 Quote Link to post Share on other sites
Werner 318 Posted June 4, 2020 Share Posted June 4, 2020 Looking good so far. Please test your adjustments before submitting them. 0 Quote Link to post Share on other sites
Igor 2095 Posted June 4, 2020 Share Posted June 4, 2020 I would propose that this is fixed in all configs under this pull requests. 0 Quote Link to post Share on other sites
Ximodel 1 Posted June 5, 2020 Author Share Posted June 5, 2020 On 6/4/2020 at 1:48 PM, Igor said: Did you notice any information telling that this was included in the upgrade? Or that was it fixed in sources? Support terms:https://github.com/armbian/build#support Also when the problem will be fixed in sources, its not fully automatically yet to push it to the images. You are welcome to help out and improve the upgrading process. As regards bbr, it is not fixed after the upgrade. I would like to provide any help if I can, but ironically, when i ran the following command right after upgrade sudo armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for. "the URL" is disappearing and I don't even know what is going wrong... And would you like to help me with the reply restriction? 1 reply a day is so harsh that I cannot give immediate information 1 Quote Link to post Share on other sites
Werner 318 Posted June 5, 2020 Share Posted June 5, 2020 3 minutes ago, Ximodel said: As regards bbr, it is not fixed after the upgrade. I would like to provide any help if I can, but ironically, when i ran the following command right after upgrade sudo armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for. "the URL" is disappearing and I don't even know what is going wrong... And would you like to help me with the reply restriction? 1 reply a day is so harsh that I cannot give immediate information You received a 'like', restriction should be gone now. Try armbianmonitor -U (take note the U is large), This will output the stuff directly to console/file. 1 Quote Link to post Share on other sites
Igor 2095 Posted June 5, 2020 Share Posted June 5, 2020 46 minutes ago, Ximodel said: As regards bbr, it is not fixed after the upgrade. Nobody claimed that. Such service is too expensive which is why we don't provide it yet. If you need this module faster than its our release update cycle, you are on your own. You can also ask someone to provide this update for you ... there are more ways. 46 minutes ago, Ximodel said: when i ran the following command right after upgrade Certain condition has to met: - network connection - 3rd party paste/bin service availability ... bugs are always possible and it takes time before they are addressed. 46 minutes ago, Ximodel said: And would you like to help me with the reply restriction? 1 reply a day is so harsh that I cannot give immediate information We will help you only under our terms and when possible. There are around 1000x too much - users are generating a lot of stress expecting even far better than paid support - of you asking (some dare to demand) for help (100% paid from our own pocket). Limit has its purpose and ofc some colateral damage ... since most of people seek for a free support its better that you wait, then us. Anyway, lots of cases are not resolved since its simply not possible. You are not restricted anymore after 7 days or if you get one like. Which you got. 0 Quote Link to post Share on other sites
Ximodel 1 Posted June 10, 2020 Author Share Posted June 10, 2020 just did apt update && apt upgrade, dignosis below fyi armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/2oQ0 Please post the URL in the forum where you've been asked for. regarding bbr, it is no. Not fixed yet. root@nanopineo2:~# find /lib -name "*tcp*" /lib/modules/5.4.43-sunxi64/kernel/drivers/scsi/libiscsi_tcp.ko /lib/modules/5.4.43-sunxi64/kernel/drivers/scsi/iscsi_tcp.ko /lib/modules/5.4.43-sunxi64/kernel/drivers/usb/typec/tcpm /lib/modules/5.4.43-sunxi64/kernel/drivers/usb/typec/tcpm/tcpci.ko /lib/modules/5.4.43-sunxi64/kernel/drivers/usb/typec/tcpm/tcpm.ko /lib/modules/5.4.43-sunxi64/kernel/drivers/usb/typec/tcpm/tcpci_rt1711h.ko /lib/modules/5.4.43-sunxi64/kernel/drivers/atm/atmtcp.ko /lib/modules/5.4.43-sunxi64/kernel/net/netfilter/xt_tcpudp.ko /lib/modules/5.4.43-sunxi64/kernel/net/netfilter/xt_tcpmss.ko /lib/modules/5.4.43-sunxi64/kernel/net/rds/rds_tcp.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_cdg.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_dctcp.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_yeah.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_highspeed.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_vegas.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_scalable.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_veno.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_htcp.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_illinois.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_lp.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_hybla.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_diag.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_nv.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_westwood.ko /lib/modules/5.4.43-sunxi64/kernel/net/ipv4/tcp_bic.ko In my another device /lib/modules/5.4.20-sunxi64/kernel/drivers/scsi/iscsi_tcp.ko /lib/modules/5.4.20-sunxi64/kernel/drivers/scsi/libiscsi_tcp.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_diag.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_bic.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_scalable.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_dctcp.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_nv.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_hybla.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_highspeed.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_westwood.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_cdg.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_illinois.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_htcp.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_bbr.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_veno.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_lp.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_yeah.ko /lib/modules/5.4.20-sunxi64/kernel/net/ipv4/tcp_vegas.ko /lib/modules/5.4.20-sunxi64/kernel/net/netfilter/xt_tcpmss.ko root@nanopineo2:~# ^C 0 Quote Link to post Share on other sites
Werner 318 Posted June 10, 2020 Share Posted June 10, 2020 4 minutes ago, Ximodel said: regarding bbr, it is no. Not fixed yet. 1 Quote Link to post Share on other sites
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.