ARMBIAN for Amlogic S905 and S905X
18 18

941 posts in this topic

@balbes150

if i do "sudo modprobe dhd" the prompt does not return back.

stays there like is trying to do something unknown to me.

Because of this behavior, i think dhd is not for my system ( Mini m8S )

Share this post


Link to post
Share on other sites

Just now i found that i cannot break it either with CTRL+C

not only "sudo modprobe dhd" but any command i run after this....

For example: i run the dhd thing, i couldn't break it so i close the terminal with xkill
After that i opened a new terminal and run "sudo nano /etc/modules"

i never got nano to take over the terminal screen, and i couldn't break this terminal either.

So something very weird is going on after the dhd thing to my system.

Share this post


Link to post
Share on other sites
10 minutes ago, xXx said:

Just now i found that i cannot break it either with CTRL+C

not only "sudo modprobe dhd" but any command i run after this....

For example: i run the dhd thing, i couldn't break it so i close the terminal with xkill
After that i opened a new terminal and run "sudo nano /etc/modules"

i never got nano to take over the terminal screen, and i couldn't break this terminal either.

So something very weird is going on after the dhd thing to my system.

What version of image (date) you have worked with WiFi ?

Share this post


Link to post
Share on other sites

EDIT:
After booting this same image a third time here are some interesting facts.

The wifi is now connecting . This was the case with the not long ago tested images but i was trying things and i was not sure. This time i didn't changed anything and wifi started working.

Reboot and shutdown is also worked now ( in the 2 previous boots was coming dekstop back in a loop ).

Right now i did changed the audio /etc/pulse/default.pa the line load-module module-udev-detect (remove the tsched=0).

Another thing is that one core is always 100%

Share this post


Link to post
Share on other sites
7 minutes ago, balbes150 said:

What version of image (date) you have worked with WiFi ?

Is always the same image "Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_KODI_20170623.img"

Share this post


Link to post
Share on other sites

4th boot via unpluging the power adapter, because the restart/shutdown loop back to dektop is here.

Share this post


Link to post
Share on other sites

The problem seems to be with sudo.
When i run commands without sudo, all is good and snappy

If i run the same command with sudo, the terminal stays there for ever.

Something must be wrong with users and groups i imagine.

Also:

Eth0 seems to be succesfully connected although i have no ethernet cable plugged to the system!!! , and wifi is not going nowhere ( only connecting with right ip's and all ).

Share this post


Link to post
Share on other sites
5 minutes ago, xXx said:

The problem seems to be with sudo.
When i run commands without sudo, all is good and snappy

If i run the same command with sudo, the terminal stays there for ever.

Something must be wrong with users and groups i imagine.

Also:

Eth0 seems to be succesfully connected although i have no ethernet cable plugged to the system!!! , and wifi is not going nowhere ( only connecting with right ip's and all ).

IMHO it is better not to use "sudo" . All teams who need a level of "root" to execute after the transition mode the "root" (using the command "su -").

Share this post


Link to post
Share on other sites

found a solution with the wifi issues:

i made /etc/network/interfaces like this:

user@amlogic:~$ cat /etc/network/interfaces
source /etc/network/interfaces.d/*

# Local loopback
auto lo
iface lo inet loopback
user@amlogic:~$ 

Now is connecting without problems...
In fact i'm writing this message straight from the box.

I'm in the 6th forced reboot by unplugging the power adapter.

Stress and balbes150 like this

Share this post


Link to post
Share on other sites

This image was EXTREMELY unstable for my box.

 

I changed only 6 thigs so far:

1) Added the "wifi_dummy" in /etc/modules

2) Removed tsched=0 from /etc/pulse/default.pa

3) Stopped NetworkManager service ( sudo service NetworkManager stop)

4) Removed network-manager from startup to save me ~6 minutes delay ( update-rc.d network-manager remove )

5) Added my wifi details in /etc/network/interfaces:

source /etc/network/interfaces.d/*
# Local loopback
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-ssid MyAccesPointName
wpa-psk mycopmplexpassword

6) removed nodm and added lightdm

Right now the system seems stable and the one core was 100% is gone ( all cores are in sane percentages )

Now lets test some HD videos with kodi :-)

Stress likes this

Share this post


Link to post
Share on other sites

I can confirm that kodi works as expected.

All kodi functions worked for me ( scanning my samba shares, adding my videos to collection, etc )

Playing 1080p and 720p videos was a pleasant experience.

The only thing ( unrelated to kodi ) is that my wifi died after 10-15 minutes again, and kodi started buffering for ever.

Since then the system become extremely laggy and unresponsive and took me about 10 minutes to get out of kodi without unplugging the power cord.

Eventually it did manage to get out of kodi, and the system is almost usable again, but with one core to be 100% and no internet/network access again.

So the biggest problem in my system seems to be wifi stability.
The image as i said before is the same Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_KODI_20170623.img  and the box is MiniM8S.

Anyone else had better luck with this image?

balbes150 likes this

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
18 18

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.