50 50
constantius

Orangepi 3 h6 allwiner chip

Recommended Posts

 

Just now, Flole said:

I assume there is no way to just disable the GPU completely? I don't need it at all, so if there is a way to disable it I would give that a try. 

Try to blacklist panfrost module.

Share this post


Link to post
Share on other sites
On 6/24/2020 at 9:02 AM, Francisco said:

 

Thank you all for your answers and tips!

The wi-fi works as expected, there is no external network restriction, I plug several devices to the same ethernet port (one at a time, of course).

I'll try the serial console messages next.

Regarding the "armbianmonitor -U", here's the result: https://pastebin.com/3kBFfhUZ

I'll try the serial console next.

Thanks again,

Francisco

I've connected to a 10/100M switch, and now it works. Connected to a 1G switch, it doesn't.

Could that be something related to the regulators, also?

Thanks,

Francisco

 

Share this post


Link to post
Share on other sites
6 minutes ago, Werner said:

 

Try to blacklist panfrost module.

That indeed disabled those messages. I have a few more, are those normal and necessary aswell or can I disable something to get rid of them:

Quote

[   34.811404] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PD regulator
[   34.811412] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 96
[   34.811419] sun50i-h6-pinctrl 300b000.pinctrl: pin-96 (5020000.ethernet) status -517
[   34.811427] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 96 (PD0) from group PD0  on device 300b000.pinctrl
[   34.811433] dwmac-sun8i 5020000.ethernet: Error applying setting, reverse things back
[   34.812121] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator
[   34.812130] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 65
[   34.812137] sun50i-h6-pinctrl 300b000.pinctrl: pin-65 (4022000.mmc) status -517
[   34.812145] sun50i-h6-pinctrl 300b000.pinctrl: could not request pin 65 (PC1) from group PC1  on device 300b000.pinctrl
[   34.812150] sunxi-mmc 4022000.mmc: Error applying setting, reverse things back
[   34.812417] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PC regulator
[   34.812423] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 79
[   34.812429] sun50i-h6-pinctrl 300b000.pinctrl: pin-79 (300b000.pinctrl:79) status -517
[   34.814736] sun50i-h6-pinctrl 300b000.pinctrl: Couldn't get bank PD regulator
[   34.814745] sun50i-h6-pinctrl 300b000.pinctrl: request() failed for pin 102
[   34.814753] sun50i-h6-pinctrl 300b000.pinctrl: pin-102 (300b000.pinctrl:102) status -517
[   34.815255] sun50i-h6-pinctrl 300b000.pinctrl: 300b000.pinctrl supply vcc-pf not found, using dummy regulator 

 

Share this post


Link to post
Share on other sites

I think I found the reason for my crashes: I used the ondemand power governor and apparently that caused the issues. Maybe the voltage regulator was set to an invalid level or something. Anyways, since I disabled it and used performance I now have had no crashes, that's an uptime of 8 days now. My absolute record was 14 days so I guess the next weeks will show if that was really the issue or not.

Share this post


Link to post
Share on other sites
6 hours ago, Flole said:

I think I found the reason for my crashes: I used the ondemand power governor and apparently that caused the issues. Maybe the voltage regulator was set to an invalid level or something. Anyways, since I disabled it and used performance I now have had no crashes, that's an uptime of 8 days now. My absolute record was 14 days so I guess the next weeks will show if that was really the issue or not.

Hm @dolphs@martinayotte did you experience these issues too? Should th Orangepi 3 be tweaked to a fixed clock by default?

Share this post


Link to post
Share on other sites

same here ( idle most time ) but must admit I always use "conservative" even on the H5 boards.

BTW still did not have time to spin up a new build ( rc5 ) , come to that later ( weekend perhaps )

Share this post


Link to post
Share on other sites

This is what happened right before a crash, looks like it was adjusting the frequency quite often at that time. I would assume that many frequency adjustments are the cause of it and also that is the only thing I changed and since then it's running super stable. Not even my selfmade power supply that provides 5.25V 3A through the dc jack made a change, I still had the same crashes while the voltage that comes out of the USB ports is super stable (checked with an oscilloscope). Only after switching to the performance governor it started to run stable (at least until now, but's thats already longer than usual).

Scaling.PNG

Share this post


Link to post
Share on other sites

Anyone updated their OrangePi 3 to the latest kernel released? Now my unit won't boot up unless I plug in an SD card with an earlier kernel

 

The details of previous working image:-

 

armbian@orangepi3:~$ lsb_release -a ; uname -a


Distributor ID:    Ubuntu
Description:    Ubuntu 20.04 LTS
Release:    20.04
Codename:    focal
Linux orangepi3 5.7.8-sunxi64 #trunk.40 SMP Fri Jul 17 19:09:21 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

 

I think I need help on how to start troubleshooting this

Share this post


Link to post
Share on other sites
45 minutes ago, lanefu said:

FYI you're running a nightly which is un supported.  Try a different kernel via armbian-config

Sorry for asking a newbie question.

How do I run armbian-config if I cannot boot up? should I try chroot?

Share this post


Link to post
Share on other sites
20 minutes ago, 062621AM said:

Sorry for asking a newbie question.

How do I run armbian-config if I cannot boot up? should I try chroot?

 

yep try chroot.

Share this post


Link to post
Share on other sites
On 7/6/2020 at 9:43 AM, Francisco said:

I've connected to a 10/100M switch, and now it works. Connected to a 1G switch, it doesn't.

Could that be something related to the regulators, also?

Thanks,

Francisco

 

The problem is on autonegotiation,  until solveded in some distro you can use something like :

ethtool -s eth0 speed 100 duplex full autoneg off.

Share this post


Link to post
Share on other sites
(edited)

Current update to current stable focal server image is broken. Pic after reboot.

 

IMG_20200723_140647.jpg

Edited by bojarin

Share this post


Link to post
Share on other sites
On 7/20/2020 at 8:50 AM, lanefu said:

 

yep try chroot.

managed to recover after chroot.

could you comment if this error is normal?

Spoiler

armbian@orangepi3:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done

The following packages will be upgraded:
  linux-dtb-current-sunxi64 linux-image-current-sunxi64
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/31.3 MB of archives.
After this operation, 14.9 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 70290 files and directories currently installed.)
Preparing to unpack .../linux-dtb-current-sunxi64_20.08.0-trunk.43_arm64.deb ...
Unpacking linux-dtb-current-sunxi64 (20.08.0-trunk.43) over (20.08.0-trunk.40) ...
dpkg: error processing archive /var/cache/apt/archives/linux-dtb-current-sunxi64_20.08.0-trunk.43_arm64.deb (--unpack):
 trying to overwrite '/boot/dtb-5.7.8-sunxi64/allwinner/overlay/README.sun50i-a64-overlays', which is also in package linux-dtb-dev-sunxi64 20.08.0-trunk.43
Preparing to unpack .../linux-image-current-sunxi64_20.08.0-trunk.43_arm64.deb ...
Unpacking linux-image-current-sunxi64 (20.08.0-trunk.43) over (20.08.0-trunk.40) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-current-sunxi64_20.08.0-trunk.43_arm64.deb (--unpack):
 trying to overwrite '/boot/System.map-5.7.8-sunxi64', which is also in package linux-image-dev-sunxi64 20.08.0-trunk.43
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-dtb-current-sunxi64_20.08.0-trunk.43_arm64.deb
 /var/cache/apt/archives/linux-image-current-sunxi64_20.08.0-trunk.43_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Share this post


Link to post
Share on other sites
1 minute ago, Werner said:

Well nightlies can be broken at any time...tried to switch back to stable?

Ok. But I think i will stay at trunk.40. No issue with dev trunk.40 so far.

Share this post


Link to post
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...
50 50