1 1
domoticity

problem with hotspot

Recommended Posts

Hy,

I have tried to use my tinkerboard like an hotspot. configuration done with armbian-config.

 

when i used the armbian jessie ( ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 4.19.20-rockchip) :

everything works IF i don't do an apt-upgrade.

 

If i do an apt-upgrade or using the last img of armbian strectch, i cannot connect any devices to my Tinkerboard :

here what i have when i used ssh to see what's wrong :

Spoiler

root@tinkerboard:~#
Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   42.906202] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.020451] Process RTW_CMD_THREAD (pid: 856, stack limit = 0x362bc6cc)

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.027837] Stack: (0xebdd3d40 to 0xebdd4000)

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.032713] 3d40: ec5aa59c c0747288 c1406588 ecbcfc00 f0f06f84 ebdd3d90 00000000 ebdd3e18

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.041862] 3d60: ebdd3dcc ebdd3d70 c0dbabb4 c02a48a4 00000005 00000013 00000000 eb8f3034

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.051011] 3d80: 00000011 c1406588 eb8f3014 eb8f3030 00000000 00000000 00dd3ddc c28bdd99

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.060160] 3da0: bf0a16a8 ec5b99c0 ec5b9000 00000000 00480020 ec5aa58a ebdd3e18 ecbcfc00

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.069308] 3dc0: ebdd3e14 ebdd3dd0 c0dbb28c c0dba280 00000000 ec5b9800 ec5b9000 ec5aa58a

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.078456] 3de0: ebdd3e18 ebdd3df0 bf097050 c1406588 f0f06f84 00000000 00000000 ffff04eb

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.087604] 3e00: bf0c1038 ec49a3c0 ebdd3eec ebdd3e18 bf0b475c c0dbb208 00000000 00000000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.096752] 3e20: 8020001f c02a43e0 ebdd3ebc ebdd3e38 c02a43e0 c015207c bf0972d4 bf096fcc

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.105900] 3e40: ebdd3e83 eb8ece80 c1406588 c28bdd99 00210d00 8020001e 00000001 00000001

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.115049] 3e60: eb8ece80 60010013 00000000 00000fff ebdd3e9c c02a32c8 ebdd3ec4 8020001e

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.124198] 3e80: ec5aa59c 0000004b 001fff00 ffffe000 00000201 00000067 ebdd3eb4 ebdd3ea8

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.133346] 3ea0: c06fc9cc c012c1f4 ebdd3ed4 ebdd3eb8 c012c1f4 c015207c bf06b828 f0f06f84

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.142484] 3ec0: ec5aa580 00000067 ebdd3eec c28bdd99 c0e9fab8 f0def000 ec5aa580 00000067

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.151620] 3ee0: ebdd3f0c ebdd3ef0 bf06b840 bf0b46e8 f0df0000 00000000 f0df04b8 c1404900

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.160755] 3f00: ebdd3f24 ebdd3f10 bf0767d0 bf06b6bc f0df0000 f0df2000 ebdd3f74 ebdd3f28

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.169882] 3f20: bf060d1c bf076750 ebdd3f4c ebdd3f38 f0df049c ed40f200 bf0d3000 f0def000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.179010] 3f40: ebdd2000 f0df0480 c0147fb8 edec8e00 ebdee740 00000000 ebdd2000 f0def000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.188137] 3f60: bf060b84 ec8ed790 ebdd3fac ebdd3f78 c01484dc bf060b90 edec8e28 edec8e28

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.197264] 3f80: 00000000 ebdee740 c0148370 00000000 00000000 00000000 00000000 00000000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.206391] 3fa0: 00000000 ebdd3fb0 c01010e8 c014837c 00000000 00000000 00000000 00000000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.215518] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.224644] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000

Message from syslogd@localhost at Feb 20 01:22:35 ...
 kernel:[   43.349151] Code: 1a000003 e5963004 e3130001 1a000000 (e7f001f2)

 

 

Can somebody help me please :) 

 

Edited by Tido
added spoiler - for better reading, please do that yourself next time. thx

Share this post


Link to post
Share on other sites
7 hours ago, domoticity said:

Can somebody help me please


I can confirm that it is crashing for me too. Finding out why will take a little longer. It would help to know which was last known good configuration ...

Share this post


Link to post
Share on other sites
42 minutes ago, Igor said:


I can confirm that it is crashing for me too. Finding out why will take a little longer. It would help to know which was last known good configuration ...

Hy.

When i use your image "ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 4.19.20-rockchip)" it Works. BUT don't do an apt-upgrade,if not it will crash.

 

I have a copy of this img if you need.

 

Share this post


Link to post
Share on other sites
5 hours ago, domoticity said:

When i use your image "ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 4.19.20-rockchip)" it Works. BUT don't do an apt-upgrade,if not it will crash.


Provide logs with 

armbianmonitor -u

 

Share this post


Link to post
Share on other sites
3 minutes ago, SecureXperts said:

Hello,

 

Hello domoticity. Can you please share the image with me. 

 

Many thanks

 

Roman

Hy

Of course.

I upload it in a share cloud and give toi the link.

But IMPORTANT, nous apt-get upgrade

Share this post


Link to post
Share on other sites

Hello i use ARMBIAN Nightly 5.75.190210 and ubuntu Bionic( 4.19.26). I have exact same bug ( and in last stable release : ARMBIAN 5.73)

 

I do not remember having this bug on ARMBIAN Stable Next bionic 5.72 (4.19.16).

Share this post


Link to post
Share on other sites
1 hour ago, dragonlost said:

Hello i use ARMBIAN Nightly 5.75.190210 and ubuntu Bionic( 4.19.26). I have exact same bug ( and in last stable release : ARMBIAN 5.73)

 

I do not remember having this bug on ARMBIAN Stable Next bionic 5.72 (4.19.16).

On Ubuntu bionic default 4.4 hotspot no have bug.

Share this post


Link to post
Share on other sites

I find the problem. This is the dnsmasq service that does not want to start with the system despite the presence of the "service dnsmasq start" command in the rc.local file. I do not know where is the problem ??

Share this post


Link to post
Share on other sites

Would someone have a solution for the hotspot?

For the "next" version, the hotspot lights up, the dnsmasq service works but it is impossible to connect to it (driver problem?).

For the "default" version, the hotspot is launched, but the dnsmasq service does not start at startup, if it is launched at the hands everything works.

Share this post


Link to post
Share on other sites
23 hours ago, dragonlost said:

Would someone have a solution for the hotspot?

For the "next" version, the hotspot lights up, the dnsmasq service works but it is impossible to connect to it (driver problem?).

For the "default" version, the hotspot is launched, but the dnsmasq service does not start at startup, if it is launched at the hands everything works.

Hy.

I haven't tried tout launcher manually. But with a Bash script starting automatically at the boot but it failed.

Share this post


Link to post
Share on other sites
23 hours ago, dragonlost said:

impossible to connect to it (driver problem?).


Yes, something is wrong with a driver upstream. It is crashing and until this is not solved, you can use legacy builds until then or some older kernel version -> armbian-config -> system -> alternative kernels.

Share this post


Link to post
Share on other sites
2 hours ago, domoticity said:

Hy.

I haven't tried tout launcher manually. But with a Bash script starting automatically at the boot but it failed.

 

1 hour ago, Igor said:


Yes, something is wrong with a driver upstream. It is crashing and until this is not solved, you can use legacy builds until then or some older kernel version -> armbian-config -> system -> alternative kernels.

 

It's good I found my bug with the hotspot version 4.4 (branch "default"). It was a synchronization command from the RTC that crashed the rc.local script.

Once the bug settles everything has become functional.

 

By cons version "default" has a dual wifi card (a physics + a virtual) which is very convenient to have the hotspot and wifi connection.

This feature is not present on the "next" version.

Share this post


Link to post
Share on other sites

After doing some tests.
On the latest version 4.4, the hotspot is running and there is the virtual wifi.
On the latest version 4.19, version 4.19.20 to a buggy hotspot and version 4.19.18 to a functional version (but without the virtual wifi networks).
Version 5.0 RC5 at a functional hotspot.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1