OPi 3 stuck login line and hdmi not work


Recommended Posts

Previously worked, but not now.

I am stuck in the login line and cannot login with the keyboard from the putty screen.

I cant login with keyboard on USB2.

Also HDMI not working. HDMI previously worked too.

 

I am newbie. Thanks in advance.

 

I cant remember which version loaded on the eMMC.

U-Boot SPL 2019.04-armbian (Jul 06 2019 - 20:55:41 +0200)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.1(debug):bb2d778-dirty
NOTICE:  BL31: Built : 20:55:33, Jul  6 2019
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc079e78, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2019.04-armbian (Jul 06 2019 - 20:55:41 +0200) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from EXT4... Card did not respond to voltage select!
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3042 bytes read in 1 ms (2.9 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
165 bytes read in 0 ms
Card did not respond to voltage select!
29583 bytes read in 5 ms (5.6 MiB/s)
4161 bytes read in 3 ms (1.3 MiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 44000000
9135838 bytes read in 923 ms (9.4 MiB/s)
15147016 bytes read in 1530 ms (9.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    9135774 Bytes = 8.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49749000, end 49fff69e ... OK
   Loading Device Tree to 00000000496d9000, end 0000000049748fff ... OK

Starting kernel ...


Ubuntu 18.04.3 LTS orangepi3 ttyS0

orangepi3 login:

 

And

This one is Armbian_19.11.4_Orangepi3_bionic_current_5.4.6_desktop with SDCard boot. (2019-12-23)

U-Boot SPL 2019.10-armbian (Dec 23 2019 - 09:47:42 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(debug):aeb3d83-dirty
NOTICE:  BL31: Built : 09:47:34, Dec 23 2019
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc07f048, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
INFO:    PMIC: Probing AXP805 on I2C
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: bldo2 voltage: 1.800V
INFO:    PMIC: bldo3 voltage: 1.800V
INFO:    PMIC: cldo1 voltage: 3.300V
INFO:    PMIC: dcdcd voltage: 0.960V
INFO:    PMIC: dcdce voltage: 1.200V
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2019.10-armbian (Dec 23 2019 - 09:47:42 +0100) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3033 bytes read in 12 ms (246.1 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
165 bytes read in 7 ms (22.5 KiB/s)
31388 bytes read in 39 ms (785.2 KiB/s)
4161 bytes read in 40 ms (101.6 KiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 44000000
9549521 bytes read in 1010 ms (9 MiB/s)
15685640 bytes read in 1650 ms (9.1 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    9549457 Bytes = 9.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 496e4000, end 49fff691 ... OK
   Loading Device Tree to 0000000049673000, end 00000000496e3fff ... OK

Starting kernel ...

[   17.213687] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1
[   17.222692] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   17.386257] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1
[   17.395289] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   17.428555] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1
[   17.437574] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   17.466272] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1
[   17.475285] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   17.504444] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1
[   17.513515] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

Armbian 19.11.4 Bionic ttyS0

orangepi3 login:

 

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

8 minutes ago, bbayin said:

Thanks for reply.

I tried with old led tv this morning and HDMI is worked. Previously i tried with samsung smart tvs 3 HDMI connections and it doesnt worked.

But now i cant got audio on HDMI connection.

I dont try analog audio output.


Not sure if we have HDMI audio driver enabled yet. First support stage is focused to server cases, general stability ... things like multimedia comes later.

Link to post
Share on other sites
10 hours ago, Igor said:


Not sure if we have HDMI audio driver enabled yet. First support stage is focused to server cases, general stability ... things like multimedia comes later.

Of course it is.

I wanted to point out the problem I was experiencing because you are doing a good job.
I'm trying to understand something myself from the forum.

 

10 hours ago, jernej said:

@bbayin Can you try this kernel patch to see if it helps with your "no HDMI output" issue? https://github.com/jernejsk/linux-1/commit/8c3e6bc8a98212a18536d54e23421036891e832b If so, I'll send fix upstream.

 

 

I haven't got file like "sun8i_hdmi_phy.c". Do I need to create and put this file on my own?

There is a file named sun6i_mipi_dsi.ko instead.

Link to post
Share on other sites
On 12/26/2019 at 1:15 AM, Igor said:


Yes, I can confirm that I also notice those problems, but didn't have time to look yet. However I do have HDMI. Perhaps this blacks out by random ... also possible. In any case, there is still some work.

 

The reason for gphy not working is this:

 

    INFO: PMIC: aldo2 voltage: 3.300V

 

ATF is enabling aldo2 which is half of the phy supply, whithout enabling the other half.

 

When Linux enables the other half later on, it's too late and phy is in a broken state. The phy regulators have to be enabled at the same time. This bug was discussed on IRC, but it looks like nobody fixed this, and the broken code got pushed to ATF master, where the Armbian is pulling it from. The fix is to downgrade ATF. The issue is basically that ATF is enabling all AXP regulators that are referenced by anything in the DTS, which is non-sensical. Device drivers should be enabling regulators for the devices they manage in a proper order.

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