Jump to content

Orangepi 3 h6 allwiner chip


constantius

Recommended Posts

so reboot with the latest nightly works for me, great! wifi does not work out of the box but I think 5.1 will bring this in?

 

asa this works it would be really nice if one could write the wifi password onto the sd card somehow without having to build the image by myself, if thats possible a hint would be very welcome :)

 

[ docker via snap does still not work but as I said if you use the docker install script it will work fine (cause I think someone had the same issue) ]

Link to comment
Share on other sites

48 minutes ago, martinayotte said:

simply define it in /etc/network/interface ...

I guess the main issue is that I'm using a mac and cant see the filesystem, on rasperry pi/ rasbian I could see some part of the fs e.g. /boot and you could do something like touch ssh to enable ssh (which is on in armbian by default which is fine) but something along the lines for wifi would make it easier. I guess rasbian has some part of its system on fat32 and armbian is ext4 all the way or something like that?

Link to comment
Share on other sites

17 hours ago, Murdag said:

I guess the main issue is that I'm using a mac and cant see the filesystem, on rasperry pi/ rasbian I could see some part of the fs e.g. /boot and you could do something like touch ssh to enable ssh (which is on in armbian by default which is fine) but something along the lines for wifi would make it easier. I guess rasbian has some part of its system on fat32 and armbian is ext4 all the way or something like that?

 

connect it up via ethernet, ssh in and make your edits

Link to comment
Share on other sites

On 4/12/2019 at 11:43 PM, megi said:

Everything necessary is built in. It's just a dd for u-boot and cp for kernel and dtb, and that's it. :) You don't even need /lib/firmware or /lib/modules.

 

PPP missing, can't make DSL connection

Edited by prasanta
Link to comment
Share on other sites

Hi guys! I'm still with my sore) Perhaps this log will enlighten the problem.

 

ozz@orangepi3:~$ systemctl status systemd-modules-load.service
* systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; ven
  Drop-In: /lib/systemd/system/systemd-modules-load.service.d
           `-10-timeout.conf
   Active: failed (Result: exit-code) since Thu 2019-04-18 20:26:57 MSK; 3min 49
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 465 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=
 Main PID: 465 (code=exited, status=1/FAILURE)

Apr 18 20:26:57 orangepi3 systemd[1]: Starting Load Kernel Modules...
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'lp'
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'ppde
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'parp
Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Main process
Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Failed with
Apr 18 20:26:57 orangepi3 systemd[1]: Failed to start Load Kernel Modules.
lines 1-17/17 (END)...skipping...
* systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-modules-load.service.d
           `-10-timeout.conf
   Active: failed (Result: exit-code) since Thu 2019-04-18 20:26:57 MSK; 3min 49s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 465 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 465 (code=exited, status=1/FAILURE)

Apr 18 20:26:57 orangepi3 systemd[1]: Starting Load Kernel Modules...
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'lp'
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'ppdev'
Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'parport_pc'
Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1
Apr 18 20:26:57 orangepi3 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Apr 18 20:26:57 orangepi3 systemd[1]: Failed to start Load Kernel Modules.

 

Link to comment
Share on other sites

22 minutes ago, ilchenko Evgeny said:

Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'lp'

Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'ppdev'

Apr 18 20:26:57 orangepi3 systemd-modules-load[465]: Failed to find module 'parport_pc'

Your image seems to try to find those modules and not finding them ...

This doesn't seem to be a "untouched" image, since those modules are not part of the build.

Did you install a specific applications or did you modified /etc/modules-load.d/modules.conf ?

 

Link to comment
Share on other sites

34 minutes ago, ilchenko Evgeny said:

Hi guys! I'm still with my sore) Perhaps this log will enlighten the problem.

 

Kernel configuration that is used for development is not fine tuned. Add those:

CONFIG_PARPORT=m
CONFIG_PRINTER=m
CONFIG_PPDEV=m

and this error will go away.

Link to comment
Share on other sites

On 4/17/2019 at 3:24 PM, martinayotte said:

I guess you can install VirtualBox on your Mac and lunch a VM with Linux Live CD and could then mount the SDCard and edit /etc/network/interface .

 

Yeah I scraped VB cause it was so slow, now have qemu setup and running but did not figure out how to forward a drive (that is not even mounted on the host).  Putting it onto a LAN and then configuring the wifi things works sure, it's just a bit more to do. thanks anyway :) 

Link to comment
Share on other sites

3 hours ago, dolphs said:

Currently for OpiOnePlus still 5.07 is being used

Right, because Armbian is using Megous branch, and Megous branch didn't merge 5.0.9 yet.

Armbian will switch to 5.1.y as soon as there is no more RCs, maybe in few days/weeks from now.

(I'm using Megous 5.1.y branch locally).

Link to comment
Share on other sites

13 hours ago, martinayotte said:

Right, because Armbian is using Megous branch, and Megous branch didn't merge 5.0.9 yet.

Armbian will switch to 5.1.y as soon as there is no more RCs, maybe in few days/weeks from now.

(I'm using Megous 5.1.y branch locally).

@martinayottewould it be possible to shared git diff for anyone else who would like to start experimenting with 5.1.y branch?

Link to comment
Share on other sites

10 hours ago, kexec said:

would it be possible to shared git diff for anyone else who would like to start experimenting with 5.1.y branch?

It is not that easy, you will need to disable few patches, tweaks some others, and create new ones ...

But here is at least where you should begin with :

diff --git a/config/sources/sun50iw6.conf b/config/sources/sun50iw6.conf
index e42581a..0245e64 100644
--- a/config/sources/sun50iw6.conf
+++ b/config/sources/sun50iw6.conf
@@ -46,11 +46,11 @@ case $BRANCH in
                KERNELPATCHDIR='sunxi-dev-h6'
                BOOTSOURCE=$MAINLINE_UBOOT_SOURCE
                BOOTDIR=$MAINLINE_UBOOT_DIR
-               BOOTBRANCH='tag:v2019.01'
+               BOOTBRANCH='tag:v2019.04'
 
                #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE
                KERNELSOURCE="https://github.com/megous/linux"
-               KERNELBRANCH="branch:orange-pi-5.0"
+               KERNELBRANCH="branch:orange-pi-5.1"
                KERNELPATCHDIR='sunxi-dev'
                KERNELDIR=$MAINLINE_KERNEL_DIR
 
diff --git a/config/sources/sunxi64_common.inc b/config/sources/sunxi64_common.inc
index fea1322..aa84a2e 100644
--- a/config/sources/sunxi64_common.inc
+++ b/config/sources/sunxi64_common.inc
@@ -54,7 +54,7 @@ case $BRANCH in
                #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE
                KERNELSOURCE="https://github.com/megous/linux"
                #KERNELBRANCH='branch:linux-4.19.y'
-               KERNELBRANCH="branch:orange-pi-5.0"
+               KERNELBRANCH="branch:orange-pi-5.1"
                KERNELDIR=$MAINLINE_KERNEL_DIR
                KERNELPATCHDIR='sunxi-dev'
                KERNEL_USE_GCC='> 7.0'
diff --git a/config/sources/sunxi_common.inc b/config/sources/sunxi_common.inc
index 26f8602..c767d33 100644
--- a/config/sources/sunxi_common.inc
+++ b/config/sources/sunxi_common.inc
@@ -40,7 +40,7 @@ case $BRANCH in
 
                #KERNELSOURCE=$MAINLINE_KERNEL_SOURCE
                KERNELSOURCE="https://github.com/megous/linux"
-               KERNELBRANCH="branch:orange-pi-5.0"
+               KERNELBRANCH="branch:orange-pi-5.1"
                KERNELDIR=$MAINLINE_KERNEL_DIR
                KERNELPATCHDIR='sunxi-dev'
                KERNEL_USE_GCC='> 7.0'

 

Link to comment
Share on other sites

Hello.
Is that possible to check if PCIe-to-SATA native controller (like the one based on ASM1061 chip) works?
Does it work out-of-the-box or it requires driver rework? Is the rework even possible? Who could do it?
I'm aware of a broken PCIe implementation.
I think that such device in companion with SSD could be a perfect solution for Quad-Core A53 providing both performance and storage capacity.HTB1KpihX5LrK1Rjy1zdq6ynnpXab.jpg

Edited by VDenisov
Added picture
Link to comment
Share on other sites

40 minutes ago, ilchenko Evgeny said:

Hi guys. I did a clean install of the latest nightly. I haven't installed anything else. Just install ntfs-3g package and added a external USB ntfs drive to fstab. After rebooting I got the following errors. What could be the matter? Maybe wrong fstab record?

 

 

 

Screenshot_93.png

Screenshot_92.png

Screenshot_91.png

Oh... as I understand it has nothing to do with fstab. (

 

Link to comment
Share on other sites

5 hours ago, ilchenko Evgeny said:

Hi guys. I did a clean install of the latest nightly. I haven't installed anything else. Just install ntfs-3g package and added a external USB ntfs drive to fstab. After rebooting I got the following errors. What could be the matter? Maybe wrong fstab record?

 

 

 

Screenshot_93.png

Screenshot_92.png

Screenshot_91.png

Don't worry, these are just early driver probe failures, that succeed later on as they are retried.

Link to comment
Share on other sites

I just went to build a new image for my OPi3 and found that the 'Buster' option has appeared - I just had to go for it! :thumbup:

 

Everything seemed to have built OK and once I'd applied the WiFi 'fix' from here I was up and running.

 

The issue I've found is that I was unable to ping anything :

george@orangepi3:~$ ping 127.0.0.1
ping: socket: Operation not permitted

This seems to be because the ping binary apparently should have the SUID bit set, so :

george@orangepi3:~$ which ping
/bin/ping
george@orangepi3:~$ ls -l /bin/ping
-rwxr-xr-x 1 root root 73280 Aug  3  2018 /bin/ping
george@orangepi3:~$ sudo chmod +s /bin/ping
george@orangepi3:~$ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.118 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.127 ms
^C

I don't know if this is an issue with the Armbian build process or perhaps it is being echoed from the Debian Buster sources, and so I'm not sure how/where is the correct place to report it :unsure:

 

 

Link to comment
Share on other sites

13 minutes ago, GeorgeP said:

I don't know if this is an issue with the Armbian build process or perhaps it is being echoed from the Debian Buster sources

It is probably Buster related since my own Armbian image doesn't have the issue :

root@orangepi3:~# uname -a
Linux orangepi3 5.1.0-rc4-sunxi64 #5.78 SMP Fri Apr 12 15:02:40 EDT 2019 aarch64 GNU/Linux
root@orangepi3:~# ll /bin/ping
-rwsr-xr-x 1 root root 65088 Nov 10  2016 /bin/ping*

 

Link to comment
Share on other sites

48 minutes ago, martinayotte said:

It is probably Buster related since my own Armbian image doesn't have the issue :

 

There's clearly more to this than it seems :

 

I found this article from back in 2016, which then led me to here.

 

And so now:

george@orangepi3:~$ sudo dpkg-reconfigure iputils-ping
george@orangepi3:~$ ls -l /bin/ping
-rwxr-xr-x 1 root root 73280 Aug  3  2018 /bin/ping
george@orangepi3:~$ ping google.com
PING google.com (216.58.208.174) 56(84) bytes of data.
64 bytes from lhr25s09-in-f174.1e100.net (216.58.208.174): icmp_seq=1 ttl=57 time=28.7 ms
64 bytes from lhr25s09-in-f174.1e100.net (216.58.208.174): icmp_seq=2 ttl=57 time=76.7 ms

What the ????

 

The discussion thread goes on (and on..) but this is getting a bit beyond me :wacko:

 

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines