[Lamobo-R1] [5.20] swconfig & problem with last 5.20 Armbian update

[Tido]

Except that

• This is not "core functionality" and can easily be fixed by replacing a single file
• We don't have all the boards that are listed on download page, some boards are just assumed to work since they are similar to others

 

I agree that this is not "core functionality" to the SoC of the board, but it is "core functionality" to the SBC Lamobo R1, whether some people like it or not.

I fully agree with second line above and without your work, help, support so many of us only had a paper weight.

 

Last but not least, can 2 or 3 of us R1 owners test the release candidate before you release it - or what else can be done to keep it 'stable' ?

[wildcat_paris]

@Tido

 

I guess soon something will emerge for Armbian (and/or Lamobo-R1) sake

 

Probably not Team Green Arrow nor Team Flash nor Team Hunter neither Team Kara

 

Maybe Team Armbian testing (Team Mikhail or Team Igor) but there is already Team Kaiser for testing (that is me modifying TK's posts, very efficient to make Thomas a little nervous to keep him working efficiently

http://forum.armbian.com/index.php/topic/2062-test-team-testers/?view=getnewpost

[zador.blood.stained]

Please test this swconfig package (don't forget to use absolute path or remove other binary):

https://dl.dropboxusercontent.com/u/5385968/swconfig_15.04-2%7Earmbian5.20%2B1_armhf.deb

[Rui Ribeiro]

Zador, the new binary seems to be working.

[badrianiulian]

Zador, the new binary seems to be working.

I can confirm... working for at least two weeks now... Thank you

[Remy]

Hi , I  think  I have a related problem:

 I'm using a Lamobo R1 and  I  done this:

Installed Armbian_5.00_Lamobo-r1_Debian_wheezy_4.4.1.zip

Configured R1 as switch coping cotent of /etc/network/interfaces.r1switch  in /etc/network/interfaces

(switch works fine)

Installed some packages, some reboots all fine

Done an apt-get update -apt-get upgrade

Reboot

here is the problem all ethernet ports don't works, non ping no ssh, if config is regulare..

Any ideas?

 

Remy

[erpomata]

see here

[alexschomb]

Please test this swconfig package (don't forget to use absolute path or remove other binary):

https://dl.dropboxusercontent.com/u/5385968/swconfig_15.04-2%7Earmbian5.20%2B1_armhf.deb

Any chance you could re-upload the file, please?

 

I just had to restart my router (Lamobo-R1) and found out that networking is not working anymore because ''swconfig'' ist missing, probably after the same update.

[zador.blood.stained]

Any chance you could re-upload the file, please?

Latest swconfig package is available in beta repository: http://beta.armbian.com/pool/utils/s/swconfig/swconfig_15.04-2~armbian5.24.161122%2b1_armhf.deb

[alexschomb]

Latest swconfig package is available in beta repository: http://beta.armbian.com/pool/utils/s/swconfig/swconfig_15.04-2~armbian5.24.161122%2b1_armhf.deb

Thanks, I installed it successfully. Unfortunately it doesn't work, because "swconfig failed to connect to switch." I also tried the packages from the stable repository - same result: http://apt.armbian.com/pool/utils/s/swconfig/

[zador.blood.stained]

Then you need to install the kernel from beta repository too (or install older one from main repo)

[alexschomb]

Then you need to install the kernel from beta repository too (or install older one from main repo)

Thank you very much. This did indeed help me a lot!

 

I had 4.8.4 installed that didn't work and am now successfully on 4.8.10 from here:

http://beta.armbian.com/pool/main/l/linux-4.8.10-sunxi/

 

(4.9.0 didn't work for me - it had the same swconfig problem)

 

Can you recommend to me how I should proceed concerning future apt-get updates? Should I switch to beta repository? How can I find out whether the fix is submitted to stable as well?

 

For further reference and other users:

You need to download all files from both given links (swconfig beta and kernel beta), mount them from a USB stick (use a hub to have a keyboard available) and install them with "dpkg -i <FILENAME>". Reboot afterwards and it should work fine again.

[zador.blood.stained]

Can you recommend to me how I should proceed concerning future apt-get updates? Should I switch to beta repository? How can I find out whether the fix is submitted to stable as well?

Don't know yet, but most likely in the future swconfig-compatible driver will be dropped for mainline kernel, instead new DSA driver will be used. Some background info can be found here: https://github.com/igorpecovnik/lib/issues/511