[ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

mad_ady wrote:
Fri Oct 16, 2020 12:47 am
Great! Is this flashable on top of alpha0.2 through Odroid utility -> Update?
Yes. Online update also should be work.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

MajkyM wrote:
Sat Sep 26, 2020 7:42 am
VID:PID from lsusb : Bus 002 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
I prepare test version with Realtek 8188eu driver.
https://drive.google.com/file/d/1yO2Wk1 ... sp=sharing

Can you download and check is your Wi-Fi working ?
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

macmino
Posts: 13
Joined: Sun Dec 08, 2013 8:53 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by macmino »

hi, I'm a new odroid c4 user and after tried to install CoreELEC and this new LineageOS, I cannot use the board anymore. I changed few SD card even if the CoreELEC worked the first time but now I'm in front of the Android Recovery. The crazy thing is that I'm not able to select any options because keyboard, minicom (via UART) and the TV remote doesn't works. I tried several installation (ambrian, Debian and so on but still the same issue!)

I don't know where to start so I upload some TXT files I grab from the console....plz help me :)

Thank you!

EDIT:

AAARGH!!! I just read this message "Avoid using Android on MicroSD cards!" and I'm using MicroSD !!!
Attachments
odroid-c4.txt
(14.46 KiB) Downloaded 15 times
minicom.log
(140 Bytes) Downloaded 16 times
minicom-console.txt
(11.02 KiB) Downloaded 14 times
minicom-log.txt
(525.74 KiB) Downloaded 12 times

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

But it doesn't mean that it don't work at all.
Try to format your sdcard to FAT before you flash the LineageOS image once more.

macmino
Posts: 13
Joined: Sun Dec 08, 2013 8:53 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by macmino »

joerg wrote:
Fri Oct 16, 2020 1:18 pm
But it doesn't mean that it don't work at all.
Try to format your sdcard to FAT before you flash the LineageOS image once more.
I did it already...nothing happens...I'm stuck in the loading kernel part, whatever the OS I choose

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I have no other idea as you try another sdcard, or you try to flash a linux image or the Pie image. (To check if your C4 is o.k.)

macmino
Posts: 13
Joined: Sun Dec 08, 2013 8:53 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by macmino »

joerg wrote:
Fri Oct 16, 2020 10:25 pm
I have no other idea as you try another sdcard, or you try to flash a linux image or the Pie image. (To check if your C4 is o.k.)
the problem is that I don't now how to...

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Hi @macmino, I thought of this: You flash your sdcard with a linux image that is well known that it works:
https://wiki.odroid.com/odroid-c4/os_im ... e/20200422
If this is working, your C4 is fine.
If this is not working, your sdcard or your C4 are not o.k. ,or the method you are flashing is wrong.
I prefer the dd method to flash (only on Linux host machine). On Windows (and on Linux) you have etcher.
https://wiki.odroid.com/odroid-c4/getti ... _odroid-c4
If this is also not working, think of buying another sdcard or even an emmc.

mad_ady
Posts: 9090
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 597 times
Been thanked: 584 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

voodik wrote:
mad_ady wrote:
Fri Oct 16, 2020 12:47 am
Great! Is this flashable on top of alpha0.2 through Odroid utility -> Update?
Yes. Online update also should be work.
I tried the online update. It downloaded fine, I did the update and it rebooted (to recovery I presume). However the screen remained dark and I couldn't see the recovery. I was connected to a Samsung TV that can do 1080p. I powercycled and it booted to a black screen again. I'm currently stuck (I will try with a serial cable on monday)

mad_ady
Posts: 9090
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 597 times
Been thanked: 584 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Ok, managed to hook up a serial adapter (and a VU7A). It seems to start in recovery, but doesn't display anything. First boot is with vu7a connected via HDMI, but unpowered. Next reboot is with the vu7a powered. Most likely recovery can't display properly...
https://paste.ubuntu.com/p/KH5StvvDZR/

I'm going to try to see how to boot to system while stuck in recovery with no screen.

mad_ady
Posts: 9090
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 597 times
Been thanked: 584 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Ok, not sure what I did exactly, but I got it to boot. I mounted the emmc on a different system and changed boot.ini and env.ini and manually set the VU7 resolution (was 720p before). I booted and still the screen was black (though it didn't keep saying no signal as it did before). So, I ran recovery in the serial shell, while in recovery, and it displayed the recovery screen. Couldn't get touch input to work, nor a mouse, so I rebooted (from serial) again. This time it booted to system (still dark screen). I did a new reboot, and now I got the Android screen. I checked, and it's running the Oct 15 update (so the update finished correctly).
So, scary update (for me). I'll make sure to leave the screen in autodetection mode.

One problem that I haven't fixed, sadly, is wifi performance. I'm currently using a Wifi module 5 (the old one, https://www.hardkernel.com/shop/wifi-module-5/) and I get terrible performance at a 5m distance from the AP (2.5GHz, no walls). There is very little radio interference (house), and other terminals have no problem achieving rates of 80Mbps - but the odroid with module 5 (and also module 0) gets a measly 2Mbps. It's so bad that youtube or online content has to buffer constantly. Any suggestion what I can do about it?

Thanks!

MajkyM
Posts: 7
Joined: Sat May 16, 2020 4:03 pm
languages_spoken: english
ODROIDs: Odroid C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by MajkyM »

voodik wrote:
Fri Oct 16, 2020 3:11 am
MajkyM wrote:
Sat Sep 26, 2020 7:42 am
VID:PID from lsusb : Bus 002 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
I prepare test version with Realtek 8188eu driver.
https://drive.google.com/file/d/1yO2Wk1 ... sp=sharing

Can you download and check is your Wi-Fi working ?
Downloaded. How can I update OS? Via odroid settings-> update or other way?
I tried via settings, but Odroid rebooted to recovery and nothing else happened

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

MajkyM wrote:
Thu Oct 22, 2020 3:51 am
voodik wrote:
Fri Oct 16, 2020 3:11 am
MajkyM wrote:
Sat Sep 26, 2020 7:42 am
VID:PID from lsusb : Bus 002 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
I prepare test version with Realtek 8188eu driver.
https://drive.google.com/file/d/1yO2Wk1 ... sp=sharing

Can you download and check is your Wi-Fi working ?
Downloaded. How can I update OS? Via odroid settings-> update or other way?
I tried via settings, but Odroid rebooted to recovery and nothing else happened
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

MajkyM
Posts: 7
Joined: Sat May 16, 2020 4:03 pm
languages_spoken: english
ODROIDs: Odroid C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by MajkyM »

I did it in that way, but I get error.
Update reached 20% and Odroid rebooted to recovery.
In a log there's an error and it says that update was aborted.

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

MajkyM wrote:
Thu Oct 22, 2020 4:29 pm
I did it in that way, but I get error.
Update reached 20% and Odroid rebooted to recovery.
In a log there's an error and it says that update was aborted.
Sd card or emmc ?
Can you pull recovery log and send it ?

Code: Select all

adb pull /cache/recovery/last_log
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

MajkyM
Posts: 7
Joined: Sat May 16, 2020 4:03 pm
languages_spoken: english
ODROIDs: Odroid C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by MajkyM »

eMMC 32gb

Do I need UART to get the adb service?

When it loads to recovery, I got these error
Attachments
USER_SCOPED_TEMP_DATA_MSGR_PHOTO_FOR_UPLOAD_1603479065008_6725478656282280692.jpeg
USER_SCOPED_TEMP_DATA_MSGR_PHOTO_FOR_UPLOAD_1603479065008_6725478656282280692.jpeg (390.65 KiB) Viewed 1171 times

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

MajkyM wrote:
Sat Oct 24, 2020 3:53 am
eMMC 32gb

Do I need UART to get the adb service?

When it loads to recovery, I got these error
For adb you just need micro USB cable and install adb to your pc.
https://www.xda-developers.com/install- ... cos-linux/
Drivers
https://developer.android.com/studio/run/win-usb

Do you directly download file to Odroid ? Can you first download it to pc then copy it to internal storage of your eMMC ?
you can do this via adb command from windows cmd after you setup it.

Code: Select all

adb push lineage_odroidc4-ota-eng.root.zip /sdcard/
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

MajkyM
Posts: 7
Joined: Sat May 16, 2020 4:03 pm
languages_spoken: english
ODROIDs: Odroid C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by MajkyM »

Via adb push, and then try to update, odroid has updated its files.

Wifi works now :D
You have a beer from me :D
These users thanked the author MajkyM for the post:
voodik (Sun Oct 25, 2020 10:23 am)

specter
Posts: 3
Joined: Thu Nov 05, 2020 8:57 am
languages_spoken: english
ODROIDs: odroid-c4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by specter »

Hey voodik,

First of all, thank you for making this awesome ROM for the C4!

I have noticed that if I hook the C4 w/ LineageOS up to a TV via HDMI, and then power cycle the TV, the odroid-c4 never resumes the HDMI feed when the TV is alive again.

Is this a limitation of Android, LineageOS, or the odroid-c4?

If it's something that is specific to the LineageOS build, where in the source code could I attempt to do some tinkering to get HDMI to resume if the display is power cycled?

Thanks! And keep up the awesome work! :D

specter
Posts: 3
Joined: Thu Nov 05, 2020 8:57 am
languages_spoken: english
ODROIDs: odroid-c4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by specter »

joerg wrote:
Mon May 18, 2020 9:08 pm
After booting several times this is looking normal now. The gray background rect went away... :o
Also, just to add an answer to the "grey box effect" to this thread:
The grey box that sometimes lurks behind widgets and app icons is a "feature" of Android when a keyboard is detected. You can actually move this grey box around with your keyboard arrow keys and then hit enter or OK to activate the actively highlighted item. Sometimes it is actually helpful if you don't want to move the mouse. :roll:

Jaguaruk
Posts: 39
Joined: Mon Jun 12, 2017 6:24 am
languages_spoken: english
ODROIDs: Odroid c2
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by Jaguaruk »

will android 10 work with the c2 unit?

User avatar
odroid
Site Admin
Posts: 36468
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 1451 times
Been thanked: 990 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by odroid »

Jaguaruk wrote:
Tue Nov 10, 2020 8:27 am
will android 10 work with the c2 unit?
Any C4 OS images are not compatible with the C2.

User avatar
istanbulls
Posts: 449
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID; N2, C4, XU4, N2+, CH4
Location: Istanbul-Turkey
Has thanked: 279 times
Been thanked: 65 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by istanbulls »

It works with uSD on HC4. Thanks

User avatar
odroid
Site Admin
Posts: 36468
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 1451 times
Been thanked: 990 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by odroid »

istanbulls wrote:
Tue Nov 10, 2020 9:13 pm
It works with uSD on HC4. Thanks
Could you access the SATA storage device from Android OS?

User avatar
istanbulls
Posts: 449
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID; N2, C4, XU4, N2+, CH4
Location: Istanbul-Turkey
Has thanked: 279 times
Been thanked: 65 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by istanbulls »

odroid wrote:
Wed Nov 11, 2020 9:45 am
istanbulls wrote:
Tue Nov 10, 2020 9:13 pm
It works with uSD on HC4. Thanks
Could you access the SATA storage device from Android OS?
viewtopic.php?f=204&t=38821 : No access via SATA; Access via USB2 Port.
viewtopic.php?f=204&t=38579 : No access via SATA; Access via USB2 Port.
viewtopic.php?f=204&t=38771 : No access via SATA; Access via USB2 Port.
http://de.eu.odroid.in/mirror/dn.odroid ... 105.img.xz : Yes access via SATA; Access via USB2 Port.

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

odroid wrote:
Wed Nov 11, 2020 9:45 am
istanbulls wrote:
Tue Nov 10, 2020 9:13 pm
It works with uSD on HC4. Thanks
Could you access the SATA storage device from Android OS?
istanbulls wrote:
Wed Nov 11, 2020 6:29 pm
odroid wrote:
Wed Nov 11, 2020 9:45 am
istanbulls wrote:
Tue Nov 10, 2020 9:13 pm
It works with uSD on HC4. Thanks
Could you access the SATA storage device from Android OS?
viewtopic.php?f=204&t=38821 : No access via SATA; Access via USB2 Port.
viewtopic.php?f=204&t=38579 : No access via SATA; Access via USB2 Port.
viewtopic.php?f=204&t=38771 : No access via SATA; Access via USB2 Port.
http://de.eu.odroid.in/mirror/dn.odroid ... 105.img.xz : Yes access via SATA; Access via USB2 Port.
Work in progress, HC4 supported image will be released in 1-2 days.
These users thanked the author voodik for the post:
istanbulls (Wed Nov 11, 2020 9:18 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

Update :!:

Code: Select all

20201113 Alpha-v0.4
* Fixed Odroid Things
* Fixed rtl8812au minor issues
* Fixed minor Wifi and BT issues 
* Added Realtek WIFI 8188eus driver
* Added persist.wifi_arg property to set WIFI module loading arguments.
* Added Bluetooth command line tools (bccmd, hciconfig, hcitool, hcidump)
* tvheadend updated to latest version
* Merge with last BSP changes (HC4 Android does not support Petitboot)
* Lineage merge with upstream
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
istanbulls
Posts: 449
Joined: Tue May 14, 2019 10:18 pm
languages_spoken: Turkish
ODROIDs: ODROID; N2, C4, XU4, N2+, CH4
Location: Istanbul-Turkey
Has thanked: 279 times
Been thanked: 65 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by istanbulls »

Thanks voodik <3

Sata, now I have access.
These users thanked the author istanbulls for the post:
odroid (Fri Nov 13, 2020 10:18 am)

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Updated my C4 to Alpha-v0.4.
Something wrong with the pwm driver / overlays. I use pin33 with my TemperatureService app for the pwm fan, there is no signal. On pin35 there is signal, but this pin I use for shutdown with my GpioShutdownService app. As this is hard coded on the interface board I designed, I cannot change it easily. This signal on pin35 makes the shutdown oscillating. Luckily there is a resistor from pin35 to the ATTiny so that should not destroy. I need to learn, how to make my own overlay for the pwm driver, so that only pin33 is activated and working. I saw already the wiki pages explaining how to make a overlay.
For the first I will remove the pwm overlay as I need the C4 in my car tomorrow.
@voodik: Can you tell me, where are the overlay files are located on the file system?

mad_ady
Posts: 9090
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 597 times
Been thanked: 584 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

They're inside the dtbs partition. You need to mount it (or its image) as a cramfs filesystem.
These users thanked the author mad_ady for the post (total 2):
voodik (Wed Nov 18, 2020 3:38 am) • joerg (Wed Nov 18, 2020 3:39 am)

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

Is I2S working?

I have selected the option in Odroid Setting, but am getting nothing.

The configuration I have is working with CoreElec and Ubuntu 20.04

There is a thread in Korean (viewtopic.php?f=183&t=40526&p=308348&hilit=i2s#p308348) for the N2 that seems to mention "media.audio hal.device=8" in default.prop for I2S, but the one I'm using has "media.audio hal.device=0".

I'll try changing next opportunity and see if there is any progress.

Any thoughts?

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I have modified the overlay pwm_ab so that pwm0 does not point to pin35.
The good: The oscillating effect for shutdown went away.
The bad: pwm1 is still without signal.
I can see an error in pwm_AO, I wonder if this lets the pwm driver crash totally?

Code: Select all

[    0.827709] meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
I see in mesonsm1_odroid_common.dtsi in the node pwm_A0_cd pinctrl entries are missing. Is it safe to disable the node?
BTW. pwm_AO_cd is on aobus and pwm_ab is on cbus, so my change should not affect this.

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

If I try to boot to Recovery, I get a blank screen; my screen resolution is 1024*600.

Is there a way to set the display resolution for Recovery as I am guessing there might be a mismatch?

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Yeah, I found what was wrong. When they made the changes for devicetree overlays, they swapped pwm0 and pwm1. No wonder that after I have updated, the pwm for fan went to pin35 where shutdown function is. :o
I have found a minor bug in GpioShutdownService, that the notification for shutdown does not terminate, after restarting the service, also if another pin was selected. I have corrected this. And I have implemented a check that the ALT of the shutdown pin must be 0 == IN.
I have corrected also TemperatureService, so that number of pwm (0|1) can be edited in settings.

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

@maxycatz: I see with the Odroid VU7+, it's also 1024*600, the recovery menu very distorted, with my old 1280*1024 monitor only black screen.
@voodik: Do you see any chance to make it work with the resolution settings of env.ini?

cesare86
Posts: 1
Joined: Sun Nov 22, 2020 8:48 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by cesare86 »

Hi All,

Thanks voodik for the amazing effort you put in place for supporting this project! I am experiencing the same issue described by specter here below, once the TV is on all good, I can also use the remote via CEC, but after the TV swtiched off (manually or after timeout) and then switched on again from the Odroid HDMI I see only the black screen with No Signal (although the odroid is running with both blue and red leds). Any suggestion to solve it?

Ciao,
Cesare.
specter wrote:
Thu Nov 05, 2020 9:03 am
Hey voodik,

First of all, thank you for making this awesome ROM for the C4!

I have noticed that if I hook the C4 w/ LineageOS up to a TV via HDMI, and then power cycle the TV, the odroid-c4 never resumes the HDMI feed when the TV is alive again.

Is this a limitation of Android, LineageOS, or the odroid-c4?

If it's something that is specific to the LineageOS build, where in the source code could I attempt to do some tinkering to get HDMI to resume if the display is power cycled?

Thanks! And keep up the awesome work! :D

specter
Posts: 3
Joined: Thu Nov 05, 2020 8:57 am
languages_spoken: english
ODROIDs: odroid-c4
Has thanked: 0
Been thanked: 0
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by specter »

Hey Cesare86,

I think I just figured this one out.

To fix:
1. Connect your odroid-c4 to your laptop with a USB 2.0 cable.
2. Open a terminal to your device with

Code: Select all

adb shell
3. Use a text editor to make changes to the following two files:
(i) /odm/boot.ini
(ii) /odm/env.ini
4. In /odm/boot.ini, change

Code: Select all

setenv disablehpd "false"
to

Code: Select all

setenv disablehpd "true"

5. In /odm/env.ini, change

Code: Select all

disablehpd="false"
to

Code: Select all

disablehpd="true"
6. Reboot your device. It should be fixed now.

I use nano for editing these files, so an editor command would be

Code: Select all

nano /odm/boot.ini
once you are in adb shell.

Let me know if this fixes your odroid as well!

-Specter
cesare86 wrote:
Sun Nov 22, 2020 8:55 pm
Hi All,

Thanks voodik for the amazing effort you put in place for supporting this project! I am experiencing the same issue described by specter here below, once the TV is on all good, I can also use the remote via CEC, but after the TV swtiched off (manually or after timeout) and then switched on again from the Odroid HDMI I see only the black screen with No Signal (although the odroid is running with both blue and red leds). Any suggestion to solve it?

Ciao,
Cesare.
specter wrote:
Thu Nov 05, 2020 9:03 am
Hey voodik,

First of all, thank you for making this awesome ROM for the C4!

I have noticed that if I hook the C4 w/ LineageOS up to a TV via HDMI, and then power cycle the TV, the odroid-c4 never resumes the HDMI feed when the TV is alive again.

Is this a limitation of Android, LineageOS, or the odroid-c4?

If it's something that is specific to the LineageOS build, where in the source code could I attempt to do some tinkering to get HDMI to resume if the display is power cycled?

Thanks! And keep up the awesome work! :D

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

joerg wrote:
Sun Nov 22, 2020 8:14 pm
@maxycatz: I see with the Odroid VU7+, it's also 1024*600, the recovery menu very distorted, with my old 1280*1024 monitor only black screen.
@voodik: Do you see any chance to make it work with the resolution settings of env.ini?
maxycatz wrote:
Fri Nov 20, 2020 10:04 pm
If I try to boot to Recovery, I get a blank screen; my screen resolution is 1024*600.

Is there a way to set the display resolution for Recovery as I am guessing there might be a mismatch?
Temporary solution.
from adb set

Code: Select all

fw_setenv boot_recovery 'if test ${hdmimode} = custombuilt; then setenv cmode modeline=${modeline} customwidth=${customwidth} customheight=${customheight}; fi; if test ${hdmimode} == 2160p*; then setenv hdmimode 1080p60hz; fi; setenv bootargs ${initargs} logo=${display_layer},loaded,${fb_addr} vout=1024x600p60hz,enable hdmimode=1024x600p60hz ${cmode} voutmode=dvi cvbsmode=${cvbsmode} osd_reverse=${osd_reverse} video_reverse=${video_reverse} androidboot.selinux=permissive jtag=disable androidboot.hardware=odroidn2 recovery_part=recovery recovery_offset=0; movi read dtbs 0 ${cramfsaddr}; cramfsload ${dtb_mem_addr} meson64_odroidn2_android.dtb;if test ${variant} != c4; then cramfsload ${loadaddr} odroid${variant}-opp.dtbo;fdt addr ${dtb_mem_addr};fdt resize 8192;fdt apply ${loadaddr};fi;movi read recovery 0 ${loadaddr}; booti ${loadaddr} - ${dtb_mem_addr}; bootm ${loadaddr};'
When have a free time i will try to check why boot.ini and env.ini not reading while booting recovery.
P.S.
This env variable will overwritten at update. so you need to set it again after update.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

@joerg
@maxycatz


Download
odroid_postboot.zip
(920 Bytes) Downloaded 9 times
Extract, push to /vendor/bin/
reboot, wait until boot finished, reboot recovery

Depends
display_autodetect="false", proper hdmimode and voutmode sould be set in /odm/env.ini
These users thanked the author voodik for the post:
joerg (Mon Nov 23, 2020 8:42 pm)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

Thanks speckter & voodik; will try this asap.

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

Any thoughts available about my earlier enquiry regards I2S?

I have noticed that te music player opens an audio file ,but stays at 00:00 on the track progress bar if audio set to I2S.

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

maxycatz wrote:
Mon Nov 23, 2020 9:08 pm
Any thoughts available about my earlier enquiry regards I2S?

I have noticed that te music player opens an audio file ,but stays at 00:00 on the track progress bar if audio set to I2S.
Do you know any version where it works ?
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

Have not had any audio out via I2S at all yet

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

maxycatz wrote:
Mon Nov 23, 2020 9:42 pm
Have not had any audio out via I2S at all yet
So there is no anything about alsaPORT-i2s1 in odroid-c4 dtbs.
alsaPORT-i2s1 is selected when you chose I2S output on Odroid Settings.
I not an spec of i2s, not have a much knowledge.
I just see alsaPORT-i2s1 is available on N2 overlay but missing or not supported on C4.
So open separate topic and ask HK hardware spec for this.
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I have tried now in odroid settings the adjustment of screen position. As I need to lift up the bottom around 60 pixels, the touches are to high, the more at the bottom the more the error. I went back to lift the bottom with wm overscan 0,0,0,60, then the touches are right. The other edges I set with odroid settings 0, 2, 6, 0, because they are drawn rare, if I adjust them with wm.

maxycatz
Posts: 20
Joined: Mon Jun 22, 2020 11:04 pm
languages_spoken: english
ODROIDs: C4
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by maxycatz »

I am overjoyed; I really must say how thankful I am that after nine months with the C4 (coming from the RPi), I have a setup with this ROM where I am looking forward to installing apps and having some fun. Rooted with Magisk and rolling! Multiboot next stop. :)

I2S sorted with last patch: I have sound on Android. In Odroid Settings>Audio only HDMI/LineOut shows although Odroid Settings>Overlays shows "hifishield".

Recovery boot shows Menu, so resolution must fixed too.

Many thanks to you, your work on this is amazing.
These users thanked the author maxycatz for the post:
voodik (Sun Nov 29, 2020 4:26 am)

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

Again I am struggling with flashing custom kernel.
I use your kernel source, @voodik:

Code: Select all

Ihr Branch ist auf demselben Stand wie 'origin/lineage-16.0_odroidg12_64'
git pull
Bereits aktuell.
I change this for enabling DS1307 driver:

Code: Select all

diff --git a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts b/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
index 44211817af1d..974c806a5457 100644
--- a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
+++ b/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
@@ -962,6 +962,11 @@
                compatible = "nxp,pcf8563";
                reg = <0x51>;
        };
+       ds3231: rtc@68 {
+               status = "okay";
+               compatible = "maxim,ds3231";
+               reg = <0x68>;
+       };
 };
 
 &i2c3 {
diff --git a/arch/arm64/configs/odroidc4_android_defconfig b/arch/arm64/configs/odroidc4_android_defconfig
index 706f89f1205d..435333200c42 100644
--- a/arch/arm64/configs/odroidc4_android_defconfig
+++ b/arch/arm64/configs/odroidc4_android_defconfig
@@ -3902,7 +3902,7 @@ CONFIG_RTC_INTF_DEV=y
 #
 # CONFIG_RTC_DRV_ABB5ZES3 is not set
 # CONFIG_RTC_DRV_ABX80X is not set
-# CONFIG_RTC_DRV_DS1307 is not set
+CONFIG_RTC_DRV_DS1307=y
 # CONFIG_RTC_DRV_DS1374 is not set
 # CONFIG_RTC_DRV_DS1672 is not set
 # CONFIG_RTC_DRV_HYM8563 is not set
I get the boot.img with dd and unpack it:

Code: Select all

abootimg -x boot.img
I replace the zImage with Image.gz and repack it (before rename it to zImage of course):

Code: Select all

abootimg --create newboot.img -f bootimg.cfg -k zImage -r initrd.img
I flash it with fastboot:

Code: Select all

sudo fastboot flash boot newboot.img
target reported max download size of 134217728 bytes
sending 'boot' (16384 KB)...
OKAY [  0.693s]
writing 'boot'...
^[[A^[[AOKAY [  1.872s]
finished. total time: 2.565s
I get last log message:

Code: Select all

[   12.243950@0] vout: aml_tvout_mode_work: monitor_timeout
I check if abootimg packing command is right. Packing boot.img with formerly saved original zImage and flash it with fastboot -> YES, it boots up.
Self compiled kernel has 9.8MB, original kernel has 10.0MB.
My kernel version:

Code: Select all

make kernelrelease
4.9.113-g7e2e405e027d
While I am writing this, comes the idea to change the version. Create an empty .scmversion file in the root directory of kernel, version is now:

Code: Select all

4.9.113
Same as the original kernel.
But it does not come up.
Full log:

Code: Select all

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 141191

BL2 Built : 22:54:32, Apr 28 2020. g12a ga659aac-dirty - changqing.gao@droid11

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
DDR driver_vesion: LPDDR4_PHY_V_0_1_15 build time: Apr 28 2020 22:54:28
board id: 1
Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from eMMC, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
00000000
emmc switch 1 ok
00000000
emmc switch 2 ok
fastboot data verify
verify result: 255
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
ddr clk to 1320MHz
Load ddrfw from eMMC, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0
00000000
emmc switch 0 ok

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from eMMC, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

R0_RxClkDly_Margin==94 ps 8
R0_TxDqDly_Margi==118 ps 10


R1_RxClkDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0

 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 

soc_vref_reg_value 0x 0000004e 0000004e 00000050 00000050 0000004f 0000004e 0000004f 0000004b 0000004d 0000004f 0000004c 0000004e 0000004d 0000004e 0000004c 00000052 0000004f 0000004e 00000050 00000050 00000050 00000050 0000004e 0000004f 00000050 0000004f 00000050 0000004f 0000004e 0000004e 0000004e 0000004f dram_vref_reg_value 0x 0000001f
2D training succeed
aml_ddr_fw_vesion: LPDDR4_PHY_V_0_1_15 build time: Jun 18 2019 20:29:43
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00700024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass

non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 440
result report
boot times 1Enable ddr reg access
00000000
emmc switch 3 ok
Authentication key not yet programmed
get rpmb counter error 0x00000007
00000000
emmc switch 0 ok
Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from eMMC, src: 0x0003c200, des: 0x0172c000, size: 0x0009c000, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0


MVN_1=0x00000000


MVN_2=0x00000000


[Image: g12a_v1.1.3386-3b31431 2019-05-21 10:41:54 luan.yuan@droid15-sz]


OPS=0x10


ring efuse init


2b 0c 10 00 01 13 18 00 00 04 34 39 32 47 38 50 


[0.939967 Inits done]


secure task start!
high task start!
low task start!
run into bl31
NOTICE:  BL31: v1.3(release):4fc40b1
NOTICE:  BL31: Built : 15:57:33, May 22 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01-00003-g2d114aa643-dirty (Nov 13 2020 - 03:27:23)

DRAM:  3.5 GiB
Relocation Offset is: d6eef000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f83668
MMC:   aml_priv->desc_buf = 0x00000000d3edf7c0
aml_priv->desc_buf = 0x00000000d3ee1b00
SDIO Port C: 0, SDIO Port B: 1
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x172000
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 12
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x2b
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
reading boot-logo.bmp.gz
27178 bytes read in 4 ms (6.5 MiB/s)
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=3840, height=1440
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
[OSD]osd_hw.free_dst_data: 0,1919,0,1079
USB3.0 XHCI init start
Net:   dwmac.ff3f0000
Hit Enter or space or Ctrl+C key to stop autoboot -- :  1  0 
## Attempting fetch boot.ini in mmc:0...
reading boot.ini
3287 bytes read in 3 ms (1 MiB/s)
## Executing script at 04000000
reading env.ini
5089 bytes read in 2 ms (2.4 MiB/s)
ini: Imported hdmimode as 1024x600p60hz
ini: Imported modeline as 2560,1440,241500,88800,60,2560,2608,2640,2720,1440,1442,1447,1481,1,1,1
ini: Imported customwidth as 2560
ini: Imported customheight as 1440
ini: Imported voutmode as dvi
ini: Imported display_autodetect as false
ini: Imported autoFramerate as true
ini: Imported backlight_pwm as no
ini: Imported adjustScreenWay as alignment
ini: Imported zoom_rate as 99
ini: Imported screenAlignment as 0 2 6 0
ini: Imported colorattribute as 444,8bit
ini: Imported osd_reverse as 0
ini: Imported video_reverse as 0
ini: Imported suspend_hdmiphy as 1
ini: Imported disablehpd as false
ini: Imported disable_vu7 as true
ini: Imported touch_invert_x as false
ini: Imported touch_invert_y as false
ini: Imported test_mt_vid as 0000
ini: Imported test_mt_pid as 0000
ini: Imported prevent_sleep as 1
ini: Imported max_freq_little as 2016
ini: Imported governor_little as performance
ini: Imported enable_wol as 0
ini: Imported heartbeat as 1
ini: Imported sg_tablesize as 2
ini: Imported overlays as i2c0 i2c1 uart0 pwm_ab
ini: Imported overlays_resize as 16384
ini: Imported gpuScaleMode as 2
movi: the partiton 'dtbs' is reading...
### CRAMFS load complete: 69364 bytes loaded to 0x10000000
### CRAMFS load complete: 223 bytes loaded to 0x1080000
### CRAMFS load complete: 223 bytes loaded to 0x1080000
### CRAMFS load complete: 380 bytes loaded to 0x1080000
### CRAMFS load complete: 412 bytes loaded to 0x1080000
movi: the partiton 'boot' is reading...
libfdt fdt_path_offset() returned FDT_ERR_BADPATH
Bad Linux ARM64 Image magic!
ee_gate_off ...
## Booting Android Image at 0x01080000 ...
reloc_addr =d3f0be50
copy done
Kernel command line: otg_device=1 buildvariant=userdebug
No androidboot.dtbo_idx configuredactive_slot is <NULL>
Unknown command 'store' - try 'help'
No dtbo patitions found
load dtb from 0x10000000 ......
No valid dtbo image found
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x02930a00
   reserving fdt memory region: addr=10000000 size=28000
   Loading Ramdisk to 3d6f8000, end 3d7ffb85 ... OK
   Loading Device Tree to 000000001ffd5000, end 000000001fffffff ... OK

Starting kernel ...

uboot time: 5905945 us
pwr_key=ffffffff
[    0.000000@0] 	07400000 - 07500000,     1024 KB, ramoops@0x07400000
[    0.000000@0] 	05000000 - 05400000,     4096 KB, linux,secmon
[    0.000000@0] 	ed800000 - ed800000,        0 KB, linux,ppmgr
[    0.000000@0] 	7f800000 - 80000000,     8192 KB, linux,meson-fb
[    0.000000@0] 	e5800000 - ed800000,   131072 KB, linux,ion-dev
[    0.000000@0] 	e3000000 - e5800000,    40960 KB, linux,di_cma
[    0.000000@0] 	cfc00000 - e3000000,   315392 KB, linux,codec_mm_cma
[    0.000000@0] 	cfc00000 - cfc00000,        0 KB, linux,codec_mm_reserved
[    0.000000@0] 	cdc00000 - cfc00000,    32768 KB, linux,vm0_cma
[    0.000000@0] sm1 clk probe ok
[    0.266907@0] codec_mm_module_init
[    0.297915@0] cvbs_out: error: failed to get vdac_config
[    0.298092@0] cvbs_out: chrdev devno 264241152 for disp
[    0.555374@0] dmi: Firmware registration failed.
[    0.826229@3] meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
[    0.854452@2] mtdoops: mtd device (mtddev=name/number) must be supplied
[    0.879761@1] meson_cpufreq_init:don't find the node <dynamic_gp1_clk>
[    0.885317@1] ff803000.serial: clock gate not found
[    0.993540@2] gpio-keypad ff800000.gpio_keypad: failed to get gpio index from dts
[    1.006300@3] fb: failed to init reserved memory
[    1.016015@3] di_get_vpu_clkb: get clk vpu error.
[    1.021811@3] Reserved memory: failed to init DMA memory pool at 0x00000000ed800000, size 0 MiB
[    1.032976@2] meson-mmc: >>>>>>>>hostbase ffffff8008825000, dmode 
[    1.083315@1] meson-mmc: >>>>>>>>hostbase ffffff800882e000, dmode 
[    1.124887@1] cectx ff80023c.aocec: cec driver date:2019/12/09:sm1 bus check reg define err
[    1.124887@1] 
[    1.129745@2] cectx ff80023c.aocec: compatible:amlogic, aocec-sm1
[    1.135567@2] cectx ff80023c.aocec: cecb_ver:0x2
[    1.140059@2] cectx ff80023c.aocec: line_reg:0x1
[    1.144604@2] cectx ff80023c.aocec: line_bit:0x3
[    1.149167@2] cectx ff80023c.aocec: ee_to_ao:0x1
[    1.154638@1] cectx ff80023c.aocec: not find 'port_num'
[    1.159026@1] cectx ff80023c.aocec: using cec:1
[    1.163691@1] cectx ff80023c.aocec: no hdmirx regs
[    1.168294@1] cectx ff80023c.aocec: no hhi regs
[    1.175256@1] cectx ff80023c.aocec: wakeup_reason:0x0
[    1.177902@1] cectx ff80023c.aocec: cev val1: 0x0;val2: 0x0
[    1.183307@1] cectx ff80023c.aocec: aml_cec_probe success end
[    1.202177@3] page_trace_module_init, create sysfs failed
[    1.208402@3] defendkey ff630218.defendkey: Reserved memory is not enough!
[    1.218660@3] Error: Driver 'spdif-dit' is already registered, aborting...
[    1.577347@3] thermal: read gpupp failed
[    1.577593@3] thermal: read gpupp failed
[    1.579712@3] thermal: read gpupp failed
[[    1.716657@0] init: Could not get mount point for '/' in /proc/mounts, /system will not be available for overlayfs
[    2.383752@1] init: /system/etc/init/lineage-system.rc: 14: ignored duplicate definition of service 'bugreport'
[    2.413546@0] libprocessgroup: Failed to mount blkio cgroup: No such file or directory
[    2.417378@0] libprocessgroup: Failed to mount memory cgroup: No such file or directory
[    2.507820@2] ueventd: /ueventd.odroidc4.rc: 102: /sys/ lines must have 5 entries
[    2.556689@2] Unable to handle kernel paging request at virtual address 0002001a
[    2.558488@2] pgd = ffffffc0092bf000
[    2.562112@2] [0002001a] *pgd=0000000000000000, *pud=0000000000000000
[    2.568413@2] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[    2.574123@2] Modules linked in: mali_kbase(O+)
[    2.578628@2] CPU: 2 PID: 2250 Comm: init Tainted: G           O    4.9.113 #2
[    2.585819@2] Hardware name: Hardkernel ODROID-C4 (DT)
[    2.590933@2] task: ffffffc0c7cd8000 task.stack: ffffff80201ac000
[    2.597005@2] PC is at of_clk_get+0x40/0x98
[    2.601223@2] LR is at kbase_platform_device_probe+0x180/0xd90 [mali_kbase]
[    2.608095@2] R4  : ffffff80201afa10, PFN:a2804
[    2.612599@2] R5  : ffffff80201af6f0, PFN:a2804
[    2.617106@2] pc : [<ffffff80094e40e8>] lr : [<ffffff8001d7ecb0>] pstate: 80400149
[    2.624645@2] sp : ffffff80201af9e0
[    2.628113@2] x29: ffffff80201af9e0 x28: 0000000000000124 
[    2.633572@2] x27: ffffffbefe9d5224 x26: ffffff8001db1c08 
[    2.639032@2] x25: ffffff8001db1c00 x24: ffffff8001db1bf8 
[    2.644491@2] x23: ffffffc0c8bfb810 x22: ffffffc0c8bfb800 
[    2.649951@2] x21: 00000000ffffffed x20: 0000000000020002 
[    2.655411@2] x19: 0000000000000000 x18: 0000000000000001 
[    2.660872@2] x17: 0000000000000000 x16: 0000000000002000 
[    2.666331@2] x15: ffffffffffffffff x14: 6c6f72746e6f6320 
[    2.671791@2] x13: 0000000000000000 x12: 0000000000000004 
[    2.677251@2] x11: 0000000000000463 x10: 0000000000000006 
[    2.682712@2] x9 : 0000000000000463 x8 : 0000000000000001 
[    2.688172@2] x7 : 0000000000000000 x6 : 0000000000000000 [    2.692342@3] usb 1-1.1: new low-speed USB device number 3 using xhci-hcd
[    2.700219@3] x5 : ffffff80201af6f0 x4 : ffffff80201afa10 
[    2.705678@3] x3 : 0000000000000000 x2 : ffffff800a0dd178 
[    2.711138@3] x1 : ffffff800a0dd188 x0 : 0000000000020002 
[    2.716604@2] 
[    2.716604@2] X22: 0xffffffc0c8bfb780:
[    2.721972@2] b780  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.730291@2] b7a0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.738611@2] b7c0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.746931@2] b7e0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.755251@2] b800  c8bc2940 ffffffc0 ffffffff 00000000 0a7f8790 ffffff80 c8bbcf00 ffffffc0
[    2.763571@2] b820  c8bc2940 ffffffc0 c8a87f80 ffffffc0 c7fc8c28 ffffffc0 0a7f87a0 ffffff80
[    2.771891@2] b840  c8a87f80 ffffffc0 0a7f84c0 ffffff80 c807bd98 ffffffc0 00000003 00000007
[    2.780211@2] b860  00000000 00000000 00000000 00000000 00000000 00000000 c8bfb878 ffffffc0
[    2.788533@2] 
[    2.788533@2] X23: 0xffffffc0c8bfb790:
[    2.793905@2] b790  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.802224@2] b7b0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.810545@2] b7d0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.818864@2] b7f0  00000000 00000000 00000000 00000000 c8bc2940 ffffffc0 ffffffff 00000000
[    2.827184@2] b810  0a7f8790 ffffff80 c8bbcf00 ffffffc0 c8bc2940 ffffffc0 c8a87f80 ffffffc0
[    2.835505@2] b830  c7fc8c28 ffffffc0 0a7f87a0 ffffff80 c8a87f80 ffffffc0 0a7f84c0 ffffff80
[    2.843825@2] b850  c807bd98 ffffffc0 00000003 00000007 00000000 00000000 00000000 00000000
[    2.852145@2] b870  00000000 00000000 c8bfb878 ffffffc0 c8bfb878 ffffffc0 c7cd8000 ffffffc0
[    2.860466@2] 
[    2.862114@2] Process init (pid: 2250, stack limit = 0xffffff80201ac000)
[    2.868786@2] Stack: (0xffffff80201af9e0 to 0xffffff80201b0000)
[    2.873149@3] input: Logitech USB-PS/2 Optical Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C00E.0001/input/input4
[    2.873633@3] hid-generic 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-xhci-hcd.0.auto-1.1/input0
[    2.902414@2] f9e0: ffffff80201afa60 ffffff8001d7ecb0 ffffffc0c7608000 ffffffc0c7608000
[    2.910388@2] fa00: 00000000ffffffed ffffff80201afa10 ffffff80201afa60 ffffff80201afa60
[    2.918360@2] fa20: ffffff80201afa30 00000000ffffffd0 0000000000000000 ffffffc0c83c3328
[    2.926333@2] fa40: ffffffc0cd367050 ffffff80201af8d0 0000000000000000 0000000000000004
[    2.934307@2] fa60: ffffff80201afac0 ffffff8009527f60 00000000fffffffe ffffffc0c8bfb810
[    2.942280@2] fa80: ffffff8001dc7038 ffffff8001dc7060 000000000000000e 0000000000000001
[    2.950253@2] faa0: ffffff8001dc76d0 ffffff800913f8c0 ffffff8008e03000 ffffff8009521eb4
[    2.958226@2] fac0: ffffff80201afaf0 ffffff8009525d0c ffffffc0c8bfb810 ffffff800aa0e000
[    2.966200@2] fae0: 0000000000000000 ffffff800aa0e000 ffffff80201afb30 ffffff8009525e74
[    2.974173@2] fb00: ffffffc0c8bfb810 ffffff8001dc7060 ffffffc0c8bfb870 0000000000000000
[    2.982146@2] fb20: ffffff800a7f8000 ffffff8009523a08 ffffff80201afb60 ffffff80095239fc
[    2.990120@2] fb40: 0000000000000000 ffffff8001dc7060 ffffff8009525db8 00000000ffffffff
[    2.998093@2] fb60: ffffff80201afba0 ffffff8009525418 ffffff8001dc7060 ffffffc0c7552e40
[    3.006066@2] fb80: ffffff800a7f8a58 0000000000000000 ffffffc0c8b04ca8 ffffffc0c8bbcf68
[    3.008334@3] usb 1-1.2: new full-speed USB device number 4 using xhci-hcd
[    3.020886@2] fba0: ffffff80201afbc0 ffffff8009524f10 ffffff8001dc7060 ffffffc0c7552e40
[    3.028860@2] fbc0: ffffff80201afc00 ffffff80095269e0 ffffff8001dc7060 ffffff8001dc7680
[    3.036833@2] fbe0: 0000000000000000 ffffffc0093aa400 ffffffc0c7550bc8 ffffff8001dc7680
[    3.044807@2] fc00: ffffff80201afc20 ffffff8009527e84 ffffff8001dc7038 ffffff8001dc7680
[    3.052780@2] fc20: ffffff80201afc40 ffffff8001de6018 ffffff8001de6000 ffffffc0c7cd8000
[    3.060754@2] fc40: ffffff80201afc50 ffffff8009083ac4 ffffff80201afcc0 ffffff80091b3b38
[    3.068726@2] fc60: ffffff8001dc7680 ffffff800a7a9000 ffffffc0c7550b80 ffffffc0093aa400
[    3.076700@2] fc80: ffffffc0c7550b80 ffffff8001dc7680 ffffffc0c7550bc8 0000000000000001
[    3.084673@2] fca0: ffffff8001dc76d0 ffffff800913f8c0 ffffff8008e03000 0000000000000124
[    3.092647@2] fcc0: ffffff80201afcf0 ffffff8009143500 ffffff80201afe58 0000000000000001
[    3.100620@2] fce0: ffffffc0c7550b80 ffffff8001dc7680 ffffff80201afe10 ffffff8009143f10
[    3.108593@2] fd00: 0000000000000000 0000000000000003 0000007ff4ecf119 0000007f948d6240
[    3.116566@2] fd20: 0000000040000000 0000000000000015 0000000000000123 0000000000000111
[    3.124540@2] fd40: ffffff8009d62000 ffffffc0c7cd8000 00000000fffffffb ffffff800a0935b8
[    3.132513@2] fd60: ffffff800a0935a8 ffffff8008ee4a40 0000000000000064 ffffff800000006e
[    3.140487@2] fd80: ffffff800000003f ffffff800000feff ffffff800a7aa388 ffffffc0c7fa3d88
[    3.146490@1] ueventd: Coldboot took 0.633 seconds
[    3.153226@2] fda0: ffffff8009d6b5f0 ffffff80024000c0 ffffff8001dc5f02 0000000000000001
[    3.161200@2] fdc0: 0000000000000123 ffffff80090b12e4 ffffff80201afe10 ffffff8001d9a028
[    3.169173@2] fde0: 000000000000000f 0000000000000000 0000000000000000 0000000000000000
[    3.177147@2] fe00: 0000000000000000 0000000000000000 0000000000000000 ffffff80090838c0
[    3.185120@2] fe20: fffffffffffffeee 00000040c3003000 ffffffffffffffff ffffffc0c7cd8a60
[    3.191608@3] input: BYZHYYZHY By ZH851 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:16B4:0703.0002/input/input5
[    3.192225@3] hid-multitouch 0003:16B4:0703.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-xhci-hcd.0.auto-1.2/input0
[    3.219527@2] fe40: ffffffc0c7cd8000 00000000000e1ac0 ffffff8008e03000 ffffff8008e03000
[    3.227500@2] fe60: 00000000000e1ac0 ffffff8008ee3e00 ffffff8008ee3c18 ffffff8008e8b4d0
[    3.235473@2] fe80: 0000000000068000 000000000007af90 0000000000000000 0000000000000000
[    3.243446@2] fea0: 000000000001f1a0 0000003200000031 0000001f00000023 000000000000001c
[    3.251420@2] fec0: 0000000000000003 0000007ff4ecf119 0000000000000000 0000000000000000
[    3.259393@2] fee0: 0000000000000000 635e5e444b48455e 635e5e444b48455e 7f7f7f7f7f7f7f7f
[    3.267367@2] ff00: 0000000000000111 0000000000000000 0000007ff4ecf119 0000000000000001
[    3.275340@2] ff20: 73656c75646f6d2f 6f6b2e696c616d2f fffffffffc000000 ffffffffffffffe2
[    3.283313@2] ff40: 0000005564b32a10 0000007f948d6220 0000007f96132000 0000007ff4ecf630
[    3.291286@2] ff60: 0000000000000000 0000000000000003 0000007f9445a330 0000000000000002
[    3.299260@2] ff80: 00000000ffffffff 0000007ff4ecf131 0000007f95ab1020 0000000000000000
[    3.307233@2] ffa0: 0000007ff4ecf640 0000007ff4ecf2f0 0000005564aac3b4 0000007ff4ecf0f0
[    3.315206@2] ffc0: 0000007f948d6240 0000000040000000 0000000000000003 0000000000000111
[    3.323179@2] ffe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[    3.331153@2] Call trace:
[    3.333753@2] Exception stack(0xffffff80201af890 to 0xffffff80201af9c0)
[    3.340340@2] f880:                                   0000000000000000 0000007fffffffff
[    3.348313@2] f8a0: ffffffc0cd371a90 ffffff8001d7ecb0 0000000000020002 ffffff800a0dd188
[    3.356286@2] f8c0: ffffff800a0dd178 0000000000000000 ffffff80201afa10 ffffff80201af6f0
[    3.364259@2] f8e0: 0000000000000000 0000000000000000 0000000000000001 0000000000000463
[    3.372233@2] f900: 0000000000000006 0000000000000463 0000000000000004 0000000000000000
[    3.380206@2] f920: 6c6f72746e6f6320 ffffffffffffffff 0000000000002000 0000000000000000
[    3.388180@2] f940: 0000000000000001 0000000000000000 0000000000020002 00000000ffffffed
[    3.396153@2] f960: ffffffc0c8bfb800 ffffffc0c8bfb810 ffffff8001db1bf8 ffffff8001db1c00
[    3.404126@2] f980: ffffff8001db1c08 ffffffbefe9d5224 0000000000000124 ffffff80201af9e0
[    3.412100@2] f9a0: ffffff8001d7ecb0 ffffff80201af9e0 ffffff80094e40e8 0000000080400149
[    3.420079@2] [ffffff80201af9e0+ 128][<ffffff80094e40e8>] of_clk_get+0x40/0x98
[    3.427330@2] [ffffff80201afa60+  96][<ffffff8001d7ecb0>] kbase_platform_device_probe+0x180/0xd90 [mali_kbase]
[    3.437238@2] [ffffff80201afac0+  48][<ffffff8009527f60>] platform_drv_probe+0x60/0xc8
[    3.445122@2] [ffffff80201afaf0+  64][<ffffff8009525d0c>] driver_probe_device+0x204/0x2b0
[    3.453267@2] [ffffff80201afb30+  48][<ffffff8009525e74>] __driver_attach+0xbc/0xc0
[    3.460894@2] [ffffff80201afb60+  64][<ffffff80095239fc>] bus_for_each_dev+0x74/0xb0
[    3.468607@2] [ffffff80201afba0+  32][<ffffff8009525418>] driver_attach+0x30/0x40
[    3.476060@2] [ffffff80201afbc0+  64][<ffffff8009524f10>] bus_add_driver+0x110/0x230
[    3.483774@2] [ffffff80201afc00+  32][<ffffff80095269e0>] driver_register+0x68/0x100
[    3.491487@2] [ffffff80201afc20+  32][<ffffff8009527e84>] __platform_driver_register+0x54/0x60
[    3.500125@2] [ffffff80201afc40+  16][<ffffff8001de6018>] kbase_platform_driver_init+0x18/0x1000 [mali_kbase]
[    3.509949@2] [ffffff80201afc50+ 112][<ffffff8009083ac4>] do_one_initcall+0x44/0x138
[    3.517663@2] [ffffff80201afcc0+  48][<ffffff80091b3b38>] do_init_module+0x64/0x1cc
[    3.525289@2] [ffffff80201afcf0+ 288][<ffffff8009143500>] load_module+0x1ca0/0x23f8
[    3.532914@2] [ffffff80201afe10+   0][<ffffff8009143f10>] SyS_finit_module+0xc8/0xd8
[    3.540627@2] [0000000000000000+   0][<ffffff80090838c0>] el0_svc_naked+0x34/0x38
[    3.548081@2] Code: 2a1303e3 9105e042 91062021 aa1403e0 (f9400e95) 
[    3.554417@2] ---[ end trace 05d0ac1fce7e23e2 ]---
[    3.565682@0] init: Restarting subcontext 'u:r:vendor_init:s0'
[    3.603449@1] audit: type=1400 audit(1420070409.636:8): avc:  denied  { sys_nice } for  pid=2670 comm="init" capability=23  scontext=u:r:vendor_init:s0 tcontext=u:r:vendor_init:s0 tclass=capability permissive=1
[    3.623308@3] spidev: disagrees about version of symbol module_layout
[    3.624304@3] spidev: disagrees about version of symbol __class_create
[    3.630646@3] spidev: disagrees about version of symbol class_destroy
[    3.637087@3] spidev: disagrees about version of symbol get_device
[    3.643191@3] spidev: disagrees about version of symbol kmem_cache_alloc_trace
[    3.650394@3] spidev: disagrees about version of symbol put_device
[    3.656541@3] spidev: disagrees about version of symbol spi_sync
[    3.662510@3] spidev: disagrees about version of symbol of_match_device
[    3.669104@3] spidev: disagrees about version of symbol device_create
[    3.675516@3] spidev: disagrees about version of symbol driver_unregister
[    3.682285@3] spidev: disagrees about version of symbol dev_err
[    3.688171@3] spidev: disagrees about version of symbol nonseekable_open
[    3.694837@3] spidev: disagrees about version of symbol spi_setup
[    3.700916@3] spidev: disagrees about version of symbol __spi_register_driver
[    3.708016@3] spidev: disagrees about version of symbol __register_chrdev
[    3.714771@3] spidev: disagrees about version of symbol device_destroy
[    3.721279@3] spidev: disagrees about version of symbol no_llseek
[    3.727341@3] spidev: disagrees about version of symbol dev_printk
[    3.733494@3] spidev: disagrees about version of symbol kmalloc_caches
[    3.744090@3] spi_meson_spicc: disagrees about version of symbol module_layout
[    3.747415@3] spi_meson_spicc: disagrees about version of symbol devm_request_threaded_irq
[    3.755430@3] spi_meson_spicc: disagrees about version of symbol devm_kmalloc
[    3.762536@3] spi_meson_spicc: disagrees about version of symbol platform_driver_unregister
[    3.770864@3] spi_meson_spicc: disagrees about version of symbol platform_get_irq
[    3.778328@3] spi_meson_spicc: disagrees about version of symbol devm_pinctrl_put
[    3.785771@3] spi_meson_spicc: disagrees about version of symbol spi_finalize_current_transfer
[    3.794340@3] spi_meson_spicc: disagrees about version of symbol dummy_dma_ops
[    3.801559@3] spi_meson_spicc: disagrees about version of symbol devm_clk_get
[    3.808655@3] spi_meson_spicc: disagrees about version of symbol spi_alloc_device
[    3.816088@3] spi_meson_spicc: disagrees about version of symbol put_device
[    3.823025@3] spi_meson_spicc: disagrees about version of symbol device_reset
[    3.830131@3] spi_meson_spicc: disagrees about version of symbol _dev_info
[    3.836977@3] spi_meson_spicc: disagrees about version of symbol spi_sync
[    3.843730@3] spi_meson_spicc: disagrees about version of symbol __class_register
[    3.851194@3] spi_meson_spicc: disagrees about version of symbol gpiod_direction_output_raw
[    3.859510@3] spi_meson_spicc: disagrees about version of symbol platform_get_resource
[    3.867417@3] spi_meson_spicc: disagrees about version of symbol spi_alloc_master
[    3.874891@3] spi_meson_spicc: disagrees about version of symbol class_unregister
[    3.882321@3] spi_meson_spicc: disagrees about version of symbol dev_err
[    3.888981@3] spi_meson_spicc: disagrees about version of symbol devm_spi_register_master
[    3.897131@3] spi_meson_spicc: disagrees about version of symbol devm_clk_register
[    3.904666@3] spi_meson_spicc: disagrees about version of symbol __platform_driver_register
[    3.912995@3] spi_meson_spicc: disagrees about version of symbol pinctrl_lookup_state
[    3.920788@3] spi_meson_spicc: disagrees about version of symbol spi_setup
[    3.927637@3] spi_meson_spicc: disagrees about version of symbol devm_ioremap_resource
[    3.935514@3] spi_meson_spicc: disagrees about version of symbol gpio_to_desc
[    3.942625@3] spi_meson_spicc: disagrees about version of symbol devm_pinctrl_get
[    3.950082@3] spi_meson_spicc: disagrees about version of symbol pinctrl_select_state
[    3.957881@3] spi_meson_spicc: disagrees about version of symbol of_device_get_match_data
[    4.022505@3] audit: type=1400 audit(1420070410.056:11): avc:  denied  { read } for  pid=2679 comm="hwservicemanage" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:hwservicemanager:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.022507@2] audit: audit_lost=2 audit_rate_limit=0 audit_backlog_limit=64
[    4.069340@1] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/data
[    4.071124@1] init: [libfs_mgr]Filesystem on /dev/block/data was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x46
[    4.085789@1] EXT4-fs (mmcblk0p16): Ignoring removed nomblk_io_submit option
[    4.103356@3] EXT4-fs (mmcblk0p16): recovery complete
[    4.103396@3] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[    4.104407@1] logd.auditd: start
[    4.104421@1] logd.klogd: 4048145001
[    4.120503@3] init: [libfs_mgr]check_fs(): mount(/dev/block/data,/data,ext4)=0: Success
[    4.161427@1] init: [libfs_mgr]check_fs(): unmount(/data) succeeded
[    4.162396@1] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/data
[    4.175159@3] type=1400 audit(1420070410.208:18): avc: denied { read } for comm="e2fsck" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.189163@3] type=1400 audit(1420070410.208:18): avc: denied { read } for comm="e2fsck" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.208144@3] type=1400 audit(1420070410.208:19): avc: denied { getattr } for comm="e2fsck" path="/vendor/lib/libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    5.007817@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.007817@2] 
[    5.008586@2] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[    5.008586@2] 
[    5.016409@2] e2fsck: Pass 2: Checking directory structure
[    5.016409@2] 
[    5.023290@2] e2fsck: Pass 3: Checking directory connectivity
[    5.023290@2] 
[    5.030649@2] e2fsck: Pass 4: Checking reference counts
[    5.030649@2] 
[    5.037532@2] e2fsck: Pass 5: Checking group summary information
[    5.037532@2] 
[    5.045128@2] e2fsck: /dev/block/data: 21100/256000 files (17.0% non-contiguous), 622689/1023198 blocks
[    5.045128@2] 
[    5.056891@2] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/data
[    5.063961@2] EXT4-fs (mmcblk0p16): Ignoring removed nomblk_io_submit option
[    5.072464@2] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.081852@2] init: [libfs_mgr]__mount(source=/dev/block/data,target=/data,type=ext4)=0: Success
[    5.091138@0] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/cache
[    5.098511@0] EXT4-fs (mmcblk0p9): Ignoring removed nomblk_io_submit option
[    5.106393@0] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[    5.115579@0] init: [libfs_mgr]check_fs(): mount(/dev/block/cache,/cache,ext4)=0: Success
[    5.143473@3] init: [libfs_mgr]check_fs(): unmount(/cache) succeeded
[    5.144365@3] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/cache
[    5.171220@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.171220@2] 
[    5.171994@2] e2fsck: cache: clean, 28/65536 files, 12746/262144 blocks
[    5.171994@2] 
[    5.180990@0] EXT4-fs (mmcblk0p9): Ignoring removed nomblk_io_submit option
[    5.188715@0] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.198533@0] init: [libfs_mgr]__mount(source=/dev/block/cache,target=/cache,type=ext4)=0: Success
[    5.207935@0] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/param
[    5.214960@0] init: [libfs_mgr]Filesystem on /dev/block/param was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x46
[    5.226948@0] init: [libfs_mgr]check_fs(): mount(/dev/block/param,/mnt/vendor/param,ext4)=-1: No such file or directory
[    5.237495@0] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/param
[    5.275744@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.275744@2] 
[    5.276540@2] e2fsck: /dev/block/param: recovering journal
[    5.276540@2] 
[    5.283603@2] e2fsck: Superblock last mount time (Thu Nov 12 19:40:08 2020,
[    5.283603@2] 
[    5.292161@2] e2fsck: 	now = Thu Jan  1 00:00:11 2015) is in the future.
[    5.292161@2] 
[    5.300489@2] e2fsck: Fix? yes
[    5.300489@2] 
[    5.305184@2] e2fsck: 
[    5.305184@2] 
[    5.309156@2] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[    5.309156@2] 
[    5.316772@2] e2fsck: Pass 2: Checking directory structure
[    5.316772@2] 
[    5.323889@2] e2fsck: Pass 3: Checking directory connectivity
[    5.323889@2] 
[    5.331247@2] e2fsck: Pass 4: Checking reference counts
[    5.331247@2] 
[    5.338103@2] e2fsck: Pass 5: Checking group summary information
[    5.338103@2] 
[    5.345721@2] e2fsck: /dev/block/param: 15/4096 files (13.3% non-contiguous), 1388/4096 blocks
[    5.345721@2] 
[    5.357119@2] EXT4-fs (mmcblk0p14): Ignoring removed nomblk_io_submit option
[    5.365467@2] EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.374684@2] init: [libfs_mgr]__mount(source=/dev/block/param,target=/mnt/vendor/param,type=ext4)=0: Success
[    5.401519@0] media_clock: disagrees about version of symbol module_layout
[    5.403131@0] media_clock: disagrees about version of symbol of_find_device_by_node
[    5.410483@0] media_clock: disagrees about version of symbol kmem_cache_alloc_trace
[    5.418025@0] media_clock: disagrees about version of symbol devm_clk_get
[    5.424791@0] media_clock: disagrees about version of symbol of_match_device
[    5.431856@0] media_clock: disagrees about version of symbol kmalloc_caches
[    5.439524@0] register clk_set_setting cpu[43]
[    5.447565@0] firmware: disagrees about version of symbol module_layout
[    5.450035@0] firmware: disagrees about version of symbol release_firmware
[    5.456631@0] firmware: disagrees about version of symbol request_firmware
[    5.463499@0] firmware: disagrees about version of symbol kmem_cache_alloc_trace
[    5.470817@0] firmware: disagrees about version of symbol kmem_cache_alloc
[    5.477665@0] firmware: disagrees about version of symbol cdev_add
[    5.483811@0] firmware: disagrees about version of symbol __class_register
[    5.490646@0] firmware: disagrees about version of symbol device_create
[    5.497256@0] firmware: disagrees about version of symbol kmem_cache_free
[    5.503998@0] firmware: disagrees about version of symbol class_unregister
[    5.510875@0] firmware: disagrees about version of symbol device_destroy
[    5.517516@0] firmware: disagrees about version of symbol cdev_init
[    5.523756@0] firmware: disagrees about version of symbol kmalloc_caches
[    5.530436@0] firmware: disagrees about version of symbol cdev_del
[    5.537305@3] Registered firmware driver success.
[    5.542225@3] Try to load video/h264_enc.bin  ...
[    5.547144@0] load firmware size : 76288, Name : video/h264_enc.bin.
[    5.552858@0] Try to load video/video_ucode.bin  ...
[    5.568356@0] load firmware size : 1816576, Name : video/video_ucode.bin.
[    5.593878@0] decoder_common: disagrees about version of symbol module_layout
[    5.598048@0] decoder_common: disagrees about version of symbol filp_open
[    5.602192@0] decoder_common: disagrees about version of symbol vfs_write
[    5.608980@0] decoder_common: disagrees about version of symbol devm_kmalloc
[    5.616008@0] decoder_common: disagrees about version of symbol platform_driver_unregister
[    5.624172@0] decoder_common: disagrees about version of symbol platform_get_irq
[    5.631586@0] decoder_common: disagrees about version of symbol fget
[    5.637870@0] decoder_common: disagrees about version of symbol fd_install
[    5.644752@0] decoder_common: disagrees about version of symbol sched_setscheduler
[    5.652253@0] decoder_common: disagrees about version of symbol dummy_dma_ops
[    5.659345@0] decoder_common: disagrees about version of symbol kmem_cache_alloc_trace
[    5.667261@0] decoder_common: disagrees about version of symbol wake_up_process
[    5.674556@0] decoder_common: disagrees about version of symbol __free_pages
[    5.681556@0] decoder_common: disagrees about version of symbol kmem_cache_alloc
[    5.688928@0] decoder_common: disagrees about version of symbol __class_register
[    5.696327@0] decoder_common: disagrees about version of symbol platform_device_unregister
[    5.704503@0] decoder_common: disagrees about version of symbol vf_reg_provider
[    5.711816@0] decoder_common: disagrees about version of symbol kmem_cache_free
[    5.719082@0] decoder_common: disagrees about version of symbol class_unregister
[    5.726460@0] decoder_common: disagrees about version of symbol vf_unreg_provider
[    5.733910@0] decoder_common: disagrees about version of symbol vfs_read
[    5.740577@0] decoder_common: disagrees about version of symbol of_reserved_mem_device_init_by_idx
[    5.749516@0] decoder_common: disagrees about version of symbol __platform_driver_register
[    5.757722@0] decoder_common: disagrees about version of symbol __alloc_pages_nodemask
[    5.765628@0] decoder_common: disagrees about version of symbol platform_device_register_full
[    5.774102@0] decoder_common: disagrees about version of symbol vfs_fsync
[    5.780881@0] decoder_common: disagrees about version of symbol filp_close
[    5.787747@0] decoder_common: disagrees about version of symbol kmalloc_caches
[   11.540301@0] vout: aml_tvout_mode_work: monitor_timeout

User avatar
voodik
Posts: 1976
Joined: Sat Dec 07, 2013 2:36 am
languages_spoken: armenian, english, russian
Location: Armenia
Has thanked: 48 times
Been thanked: 311 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by voodik »

joerg wrote:
Sat Dec 19, 2020 1:17 am
Again I am struggling with flashing custom kernel.
I use your kernel source, @voodik:

Code: Select all

Ihr Branch ist auf demselben Stand wie 'origin/lineage-16.0_odroidg12_64'
git pull
Bereits aktuell.
I change this for enabling DS1307 driver:

Code: Select all

diff --git a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts b/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
index 44211817af1d..974c806a5457 100644
--- a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
+++ b/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts
@@ -962,6 +962,11 @@
                compatible = "nxp,pcf8563";
                reg = <0x51>;
        };
+       ds3231: rtc@68 {
+               status = "okay";
+               compatible = "maxim,ds3231";
+               reg = <0x68>;
+       };
 };
 
 &i2c3 {
diff --git a/arch/arm64/configs/odroidc4_android_defconfig b/arch/arm64/configs/odroidc4_android_defconfig
index 706f89f1205d..435333200c42 100644
--- a/arch/arm64/configs/odroidc4_android_defconfig
+++ b/arch/arm64/configs/odroidc4_android_defconfig
@@ -3902,7 +3902,7 @@ CONFIG_RTC_INTF_DEV=y
 #
 # CONFIG_RTC_DRV_ABB5ZES3 is not set
 # CONFIG_RTC_DRV_ABX80X is not set
-# CONFIG_RTC_DRV_DS1307 is not set
+CONFIG_RTC_DRV_DS1307=y
 # CONFIG_RTC_DRV_DS1374 is not set
 # CONFIG_RTC_DRV_DS1672 is not set
 # CONFIG_RTC_DRV_HYM8563 is not set
I get the boot.img with dd and unpack it:

Code: Select all

abootimg -x boot.img
I replace the zImage with Image.gz and repack it (before rename it to zImage of course):

Code: Select all

abootimg --create newboot.img -f bootimg.cfg -k zImage -r initrd.img
I flash it with fastboot:

Code: Select all

sudo fastboot flash boot newboot.img
target reported max download size of 134217728 bytes
sending 'boot' (16384 KB)...
OKAY [  0.693s]
writing 'boot'...
^[[A^[[AOKAY [  1.872s]
finished. total time: 2.565s
I get last log message:

Code: Select all

[   12.243950@0] vout: aml_tvout_mode_work: monitor_timeout
I check if abootimg packing command is right. Packing boot.img with formerly saved original zImage and flash it with fastboot -> YES, it boots up.
Self compiled kernel has 9.8MB, original kernel has 10.0MB.
My kernel version:

Code: Select all

make kernelrelease
4.9.113-g7e2e405e027d
While I am writing this, comes the idea to change the version. Create an empty .scmversion file in the root directory of kernel, version is now:

Code: Select all

4.9.113
Same as the original kernel.
But it does not come up.
Full log:

Code: Select all

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 141191

BL2 Built : 22:54:32, Apr 28 2020. g12a ga659aac-dirty - changqing.gao@droid11

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
DDR driver_vesion: LPDDR4_PHY_V_0_1_15 build time: Apr 28 2020 22:54:28
board id: 1
Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from eMMC, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
00000000
emmc switch 1 ok
00000000
emmc switch 2 ok
fastboot data verify
verify result: 255
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
ddr clk to 1320MHz
Load ddrfw from eMMC, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0
00000000
emmc switch 0 ok

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from eMMC, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

R0_RxClkDly_Margin==94 ps 8
R0_TxDqDly_Margi==118 ps 10


R1_RxClkDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0

 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 

soc_vref_reg_value 0x 0000004e 0000004e 00000050 00000050 0000004f 0000004e 0000004f 0000004b 0000004d 0000004f 0000004c 0000004e 0000004d 0000004e 0000004c 00000052 0000004f 0000004e 00000050 00000050 00000050 00000050 0000004e 0000004f 00000050 0000004f 00000050 0000004f 0000004e 0000004e 0000004e 0000004f dram_vref_reg_value 0x 0000001f
2D training succeed
aml_ddr_fw_vesion: LPDDR4_PHY_V_0_1_15 build time: Jun 18 2019 20:29:43
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00700024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass

non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 440
result report
boot times 1Enable ddr reg access
00000000
emmc switch 3 ok
Authentication key not yet programmed
get rpmb counter error 0x00000007
00000000
emmc switch 0 ok
Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from eMMC, src: 0x0003c200, des: 0x0172c000, size: 0x0009c000, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0


MVN_1=0x00000000


MVN_2=0x00000000


[Image: g12a_v1.1.3386-3b31431 2019-05-21 10:41:54 luan.yuan@droid15-sz]


OPS=0x10


ring efuse init


2b 0c 10 00 01 13 18 00 00 04 34 39 32 47 38 50 


[0.939967 Inits done]


secure task start!
high task start!
low task start!
run into bl31
NOTICE:  BL31: v1.3(release):4fc40b1
NOTICE:  BL31: Built : 15:57:33, May 22 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01-00003-g2d114aa643-dirty (Nov 13 2020 - 03:27:23)

DRAM:  3.5 GiB
Relocation Offset is: d6eef000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f83668
MMC:   aml_priv->desc_buf = 0x00000000d3edf7c0
aml_priv->desc_buf = 0x00000000d3ee1b00
SDIO Port C: 0, SDIO Port B: 1
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x172000
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 12
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x2b
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
reading boot-logo.bmp.gz
27178 bytes read in 4 ms (6.5 MiB/s)
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=3840, height=1440
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
[OSD]osd_hw.free_dst_data: 0,1919,0,1079
USB3.0 XHCI init start
Net:   dwmac.ff3f0000
Hit Enter or space or Ctrl+C key to stop autoboot -- :  1  0 
## Attempting fetch boot.ini in mmc:0...
reading boot.ini
3287 bytes read in 3 ms (1 MiB/s)
## Executing script at 04000000
reading env.ini
5089 bytes read in 2 ms (2.4 MiB/s)
ini: Imported hdmimode as 1024x600p60hz
ini: Imported modeline as 2560,1440,241500,88800,60,2560,2608,2640,2720,1440,1442,1447,1481,1,1,1
ini: Imported customwidth as 2560
ini: Imported customheight as 1440
ini: Imported voutmode as dvi
ini: Imported display_autodetect as false
ini: Imported autoFramerate as true
ini: Imported backlight_pwm as no
ini: Imported adjustScreenWay as alignment
ini: Imported zoom_rate as 99
ini: Imported screenAlignment as 0 2 6 0
ini: Imported colorattribute as 444,8bit
ini: Imported osd_reverse as 0
ini: Imported video_reverse as 0
ini: Imported suspend_hdmiphy as 1
ini: Imported disablehpd as false
ini: Imported disable_vu7 as true
ini: Imported touch_invert_x as false
ini: Imported touch_invert_y as false
ini: Imported test_mt_vid as 0000
ini: Imported test_mt_pid as 0000
ini: Imported prevent_sleep as 1
ini: Imported max_freq_little as 2016
ini: Imported governor_little as performance
ini: Imported enable_wol as 0
ini: Imported heartbeat as 1
ini: Imported sg_tablesize as 2
ini: Imported overlays as i2c0 i2c1 uart0 pwm_ab
ini: Imported overlays_resize as 16384
ini: Imported gpuScaleMode as 2
movi: the partiton 'dtbs' is reading...
### CRAMFS load complete: 69364 bytes loaded to 0x10000000
### CRAMFS load complete: 223 bytes loaded to 0x1080000
### CRAMFS load complete: 223 bytes loaded to 0x1080000
### CRAMFS load complete: 380 bytes loaded to 0x1080000
### CRAMFS load complete: 412 bytes loaded to 0x1080000
movi: the partiton 'boot' is reading...
libfdt fdt_path_offset() returned FDT_ERR_BADPATH
Bad Linux ARM64 Image magic!
ee_gate_off ...
## Booting Android Image at 0x01080000 ...
reloc_addr =d3f0be50
copy done
Kernel command line: otg_device=1 buildvariant=userdebug
No androidboot.dtbo_idx configuredactive_slot is <NULL>
Unknown command 'store' - try 'help'
No dtbo patitions found
load dtb from 0x10000000 ......
No valid dtbo image found
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x02930a00
   reserving fdt memory region: addr=10000000 size=28000
   Loading Ramdisk to 3d6f8000, end 3d7ffb85 ... OK
   Loading Device Tree to 000000001ffd5000, end 000000001fffffff ... OK

Starting kernel ...

uboot time: 5905945 us
pwr_key=ffffffff
[    0.000000@0] 	07400000 - 07500000,     1024 KB, ramoops@0x07400000
[    0.000000@0] 	05000000 - 05400000,     4096 KB, linux,secmon
[    0.000000@0] 	ed800000 - ed800000,        0 KB, linux,ppmgr
[    0.000000@0] 	7f800000 - 80000000,     8192 KB, linux,meson-fb
[    0.000000@0] 	e5800000 - ed800000,   131072 KB, linux,ion-dev
[    0.000000@0] 	e3000000 - e5800000,    40960 KB, linux,di_cma
[    0.000000@0] 	cfc00000 - e3000000,   315392 KB, linux,codec_mm_cma
[    0.000000@0] 	cfc00000 - cfc00000,        0 KB, linux,codec_mm_reserved
[    0.000000@0] 	cdc00000 - cfc00000,    32768 KB, linux,vm0_cma
[    0.000000@0] sm1 clk probe ok
[    0.266907@0] codec_mm_module_init
[    0.297915@0] cvbs_out: error: failed to get vdac_config
[    0.298092@0] cvbs_out: chrdev devno 264241152 for disp
[    0.555374@0] dmi: Firmware registration failed.
[    0.826229@3] meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
[    0.854452@2] mtdoops: mtd device (mtddev=name/number) must be supplied
[    0.879761@1] meson_cpufreq_init:don't find the node <dynamic_gp1_clk>
[    0.885317@1] ff803000.serial: clock gate not found
[    0.993540@2] gpio-keypad ff800000.gpio_keypad: failed to get gpio index from dts
[    1.006300@3] fb: failed to init reserved memory
[    1.016015@3] di_get_vpu_clkb: get clk vpu error.
[    1.021811@3] Reserved memory: failed to init DMA memory pool at 0x00000000ed800000, size 0 MiB
[    1.032976@2] meson-mmc: >>>>>>>>hostbase ffffff8008825000, dmode 
[    1.083315@1] meson-mmc: >>>>>>>>hostbase ffffff800882e000, dmode 
[    1.124887@1] cectx ff80023c.aocec: cec driver date:2019/12/09:sm1 bus check reg define err
[    1.124887@1] 
[    1.129745@2] cectx ff80023c.aocec: compatible:amlogic, aocec-sm1
[    1.135567@2] cectx ff80023c.aocec: cecb_ver:0x2
[    1.140059@2] cectx ff80023c.aocec: line_reg:0x1
[    1.144604@2] cectx ff80023c.aocec: line_bit:0x3
[    1.149167@2] cectx ff80023c.aocec: ee_to_ao:0x1
[    1.154638@1] cectx ff80023c.aocec: not find 'port_num'
[    1.159026@1] cectx ff80023c.aocec: using cec:1
[    1.163691@1] cectx ff80023c.aocec: no hdmirx regs
[    1.168294@1] cectx ff80023c.aocec: no hhi regs
[    1.175256@1] cectx ff80023c.aocec: wakeup_reason:0x0
[    1.177902@1] cectx ff80023c.aocec: cev val1: 0x0;val2: 0x0
[    1.183307@1] cectx ff80023c.aocec: aml_cec_probe success end
[    1.202177@3] page_trace_module_init, create sysfs failed
[    1.208402@3] defendkey ff630218.defendkey: Reserved memory is not enough!
[    1.218660@3] Error: Driver 'spdif-dit' is already registered, aborting...
[    1.577347@3] thermal: read gpupp failed
[    1.577593@3] thermal: read gpupp failed
[    1.579712@3] thermal: read gpupp failed
[[    1.716657@0] init: Could not get mount point for '/' in /proc/mounts, /system will not be available for overlayfs
[    2.383752@1] init: /system/etc/init/lineage-system.rc: 14: ignored duplicate definition of service 'bugreport'
[    2.413546@0] libprocessgroup: Failed to mount blkio cgroup: No such file or directory
[    2.417378@0] libprocessgroup: Failed to mount memory cgroup: No such file or directory
[    2.507820@2] ueventd: /ueventd.odroidc4.rc: 102: /sys/ lines must have 5 entries
[    2.556689@2] Unable to handle kernel paging request at virtual address 0002001a
[    2.558488@2] pgd = ffffffc0092bf000
[    2.562112@2] [0002001a] *pgd=0000000000000000, *pud=0000000000000000
[    2.568413@2] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[    2.574123@2] Modules linked in: mali_kbase(O+)
[    2.578628@2] CPU: 2 PID: 2250 Comm: init Tainted: G           O    4.9.113 #2
[    2.585819@2] Hardware name: Hardkernel ODROID-C4 (DT)
[    2.590933@2] task: ffffffc0c7cd8000 task.stack: ffffff80201ac000
[    2.597005@2] PC is at of_clk_get+0x40/0x98
[    2.601223@2] LR is at kbase_platform_device_probe+0x180/0xd90 [mali_kbase]
[    2.608095@2] R4  : ffffff80201afa10, PFN:a2804
[    2.612599@2] R5  : ffffff80201af6f0, PFN:a2804
[    2.617106@2] pc : [<ffffff80094e40e8>] lr : [<ffffff8001d7ecb0>] pstate: 80400149
[    2.624645@2] sp : ffffff80201af9e0
[    2.628113@2] x29: ffffff80201af9e0 x28: 0000000000000124 
[    2.633572@2] x27: ffffffbefe9d5224 x26: ffffff8001db1c08 
[    2.639032@2] x25: ffffff8001db1c00 x24: ffffff8001db1bf8 
[    2.644491@2] x23: ffffffc0c8bfb810 x22: ffffffc0c8bfb800 
[    2.649951@2] x21: 00000000ffffffed x20: 0000000000020002 
[    2.655411@2] x19: 0000000000000000 x18: 0000000000000001 
[    2.660872@2] x17: 0000000000000000 x16: 0000000000002000 
[    2.666331@2] x15: ffffffffffffffff x14: 6c6f72746e6f6320 
[    2.671791@2] x13: 0000000000000000 x12: 0000000000000004 
[    2.677251@2] x11: 0000000000000463 x10: 0000000000000006 
[    2.682712@2] x9 : 0000000000000463 x8 : 0000000000000001 
[    2.688172@2] x7 : 0000000000000000 x6 : 0000000000000000 [    2.692342@3] usb 1-1.1: new low-speed USB device number 3 using xhci-hcd
[    2.700219@3] x5 : ffffff80201af6f0 x4 : ffffff80201afa10 
[    2.705678@3] x3 : 0000000000000000 x2 : ffffff800a0dd178 
[    2.711138@3] x1 : ffffff800a0dd188 x0 : 0000000000020002 
[    2.716604@2] 
[    2.716604@2] X22: 0xffffffc0c8bfb780:
[    2.721972@2] b780  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.730291@2] b7a0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.738611@2] b7c0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.746931@2] b7e0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.755251@2] b800  c8bc2940 ffffffc0 ffffffff 00000000 0a7f8790 ffffff80 c8bbcf00 ffffffc0
[    2.763571@2] b820  c8bc2940 ffffffc0 c8a87f80 ffffffc0 c7fc8c28 ffffffc0 0a7f87a0 ffffff80
[    2.771891@2] b840  c8a87f80 ffffffc0 0a7f84c0 ffffff80 c807bd98 ffffffc0 00000003 00000007
[    2.780211@2] b860  00000000 00000000 00000000 00000000 00000000 00000000 c8bfb878 ffffffc0
[    2.788533@2] 
[    2.788533@2] X23: 0xffffffc0c8bfb790:
[    2.793905@2] b790  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.802224@2] b7b0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.810545@2] b7d0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.818864@2] b7f0  00000000 00000000 00000000 00000000 c8bc2940 ffffffc0 ffffffff 00000000
[    2.827184@2] b810  0a7f8790 ffffff80 c8bbcf00 ffffffc0 c8bc2940 ffffffc0 c8a87f80 ffffffc0
[    2.835505@2] b830  c7fc8c28 ffffffc0 0a7f87a0 ffffff80 c8a87f80 ffffffc0 0a7f84c0 ffffff80
[    2.843825@2] b850  c807bd98 ffffffc0 00000003 00000007 00000000 00000000 00000000 00000000
[    2.852145@2] b870  00000000 00000000 c8bfb878 ffffffc0 c8bfb878 ffffffc0 c7cd8000 ffffffc0
[    2.860466@2] 
[    2.862114@2] Process init (pid: 2250, stack limit = 0xffffff80201ac000)
[    2.868786@2] Stack: (0xffffff80201af9e0 to 0xffffff80201b0000)
[    2.873149@3] input: Logitech USB-PS/2 Optical Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C00E.0001/input/input4
[    2.873633@3] hid-generic 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-xhci-hcd.0.auto-1.1/input0
[    2.902414@2] f9e0: ffffff80201afa60 ffffff8001d7ecb0 ffffffc0c7608000 ffffffc0c7608000
[    2.910388@2] fa00: 00000000ffffffed ffffff80201afa10 ffffff80201afa60 ffffff80201afa60
[    2.918360@2] fa20: ffffff80201afa30 00000000ffffffd0 0000000000000000 ffffffc0c83c3328
[    2.926333@2] fa40: ffffffc0cd367050 ffffff80201af8d0 0000000000000000 0000000000000004
[    2.934307@2] fa60: ffffff80201afac0 ffffff8009527f60 00000000fffffffe ffffffc0c8bfb810
[    2.942280@2] fa80: ffffff8001dc7038 ffffff8001dc7060 000000000000000e 0000000000000001
[    2.950253@2] faa0: ffffff8001dc76d0 ffffff800913f8c0 ffffff8008e03000 ffffff8009521eb4
[    2.958226@2] fac0: ffffff80201afaf0 ffffff8009525d0c ffffffc0c8bfb810 ffffff800aa0e000
[    2.966200@2] fae0: 0000000000000000 ffffff800aa0e000 ffffff80201afb30 ffffff8009525e74
[    2.974173@2] fb00: ffffffc0c8bfb810 ffffff8001dc7060 ffffffc0c8bfb870 0000000000000000
[    2.982146@2] fb20: ffffff800a7f8000 ffffff8009523a08 ffffff80201afb60 ffffff80095239fc
[    2.990120@2] fb40: 0000000000000000 ffffff8001dc7060 ffffff8009525db8 00000000ffffffff
[    2.998093@2] fb60: ffffff80201afba0 ffffff8009525418 ffffff8001dc7060 ffffffc0c7552e40
[    3.006066@2] fb80: ffffff800a7f8a58 0000000000000000 ffffffc0c8b04ca8 ffffffc0c8bbcf68
[    3.008334@3] usb 1-1.2: new full-speed USB device number 4 using xhci-hcd
[    3.020886@2] fba0: ffffff80201afbc0 ffffff8009524f10 ffffff8001dc7060 ffffffc0c7552e40
[    3.028860@2] fbc0: ffffff80201afc00 ffffff80095269e0 ffffff8001dc7060 ffffff8001dc7680
[    3.036833@2] fbe0: 0000000000000000 ffffffc0093aa400 ffffffc0c7550bc8 ffffff8001dc7680
[    3.044807@2] fc00: ffffff80201afc20 ffffff8009527e84 ffffff8001dc7038 ffffff8001dc7680
[    3.052780@2] fc20: ffffff80201afc40 ffffff8001de6018 ffffff8001de6000 ffffffc0c7cd8000
[    3.060754@2] fc40: ffffff80201afc50 ffffff8009083ac4 ffffff80201afcc0 ffffff80091b3b38
[    3.068726@2] fc60: ffffff8001dc7680 ffffff800a7a9000 ffffffc0c7550b80 ffffffc0093aa400
[    3.076700@2] fc80: ffffffc0c7550b80 ffffff8001dc7680 ffffffc0c7550bc8 0000000000000001
[    3.084673@2] fca0: ffffff8001dc76d0 ffffff800913f8c0 ffffff8008e03000 0000000000000124
[    3.092647@2] fcc0: ffffff80201afcf0 ffffff8009143500 ffffff80201afe58 0000000000000001
[    3.100620@2] fce0: ffffffc0c7550b80 ffffff8001dc7680 ffffff80201afe10 ffffff8009143f10
[    3.108593@2] fd00: 0000000000000000 0000000000000003 0000007ff4ecf119 0000007f948d6240
[    3.116566@2] fd20: 0000000040000000 0000000000000015 0000000000000123 0000000000000111
[    3.124540@2] fd40: ffffff8009d62000 ffffffc0c7cd8000 00000000fffffffb ffffff800a0935b8
[    3.132513@2] fd60: ffffff800a0935a8 ffffff8008ee4a40 0000000000000064 ffffff800000006e
[    3.140487@2] fd80: ffffff800000003f ffffff800000feff ffffff800a7aa388 ffffffc0c7fa3d88
[    3.146490@1] ueventd: Coldboot took 0.633 seconds
[    3.153226@2] fda0: ffffff8009d6b5f0 ffffff80024000c0 ffffff8001dc5f02 0000000000000001
[    3.161200@2] fdc0: 0000000000000123 ffffff80090b12e4 ffffff80201afe10 ffffff8001d9a028
[    3.169173@2] fde0: 000000000000000f 0000000000000000 0000000000000000 0000000000000000
[    3.177147@2] fe00: 0000000000000000 0000000000000000 0000000000000000 ffffff80090838c0
[    3.185120@2] fe20: fffffffffffffeee 00000040c3003000 ffffffffffffffff ffffffc0c7cd8a60
[    3.191608@3] input: BYZHYYZHY By ZH851 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:16B4:0703.0002/input/input5
[    3.192225@3] hid-multitouch 0003:16B4:0703.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-xhci-hcd.0.auto-1.2/input0
[    3.219527@2] fe40: ffffffc0c7cd8000 00000000000e1ac0 ffffff8008e03000 ffffff8008e03000
[    3.227500@2] fe60: 00000000000e1ac0 ffffff8008ee3e00 ffffff8008ee3c18 ffffff8008e8b4d0
[    3.235473@2] fe80: 0000000000068000 000000000007af90 0000000000000000 0000000000000000
[    3.243446@2] fea0: 000000000001f1a0 0000003200000031 0000001f00000023 000000000000001c
[    3.251420@2] fec0: 0000000000000003 0000007ff4ecf119 0000000000000000 0000000000000000
[    3.259393@2] fee0: 0000000000000000 635e5e444b48455e 635e5e444b48455e 7f7f7f7f7f7f7f7f
[    3.267367@2] ff00: 0000000000000111 0000000000000000 0000007ff4ecf119 0000000000000001
[    3.275340@2] ff20: 73656c75646f6d2f 6f6b2e696c616d2f fffffffffc000000 ffffffffffffffe2
[    3.283313@2] ff40: 0000005564b32a10 0000007f948d6220 0000007f96132000 0000007ff4ecf630
[    3.291286@2] ff60: 0000000000000000 0000000000000003 0000007f9445a330 0000000000000002
[    3.299260@2] ff80: 00000000ffffffff 0000007ff4ecf131 0000007f95ab1020 0000000000000000
[    3.307233@2] ffa0: 0000007ff4ecf640 0000007ff4ecf2f0 0000005564aac3b4 0000007ff4ecf0f0
[    3.315206@2] ffc0: 0000007f948d6240 0000000040000000 0000000000000003 0000000000000111
[    3.323179@2] ffe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[    3.331153@2] Call trace:
[    3.333753@2] Exception stack(0xffffff80201af890 to 0xffffff80201af9c0)
[    3.340340@2] f880:                                   0000000000000000 0000007fffffffff
[    3.348313@2] f8a0: ffffffc0cd371a90 ffffff8001d7ecb0 0000000000020002 ffffff800a0dd188
[    3.356286@2] f8c0: ffffff800a0dd178 0000000000000000 ffffff80201afa10 ffffff80201af6f0
[    3.364259@2] f8e0: 0000000000000000 0000000000000000 0000000000000001 0000000000000463
[    3.372233@2] f900: 0000000000000006 0000000000000463 0000000000000004 0000000000000000
[    3.380206@2] f920: 6c6f72746e6f6320 ffffffffffffffff 0000000000002000 0000000000000000
[    3.388180@2] f940: 0000000000000001 0000000000000000 0000000000020002 00000000ffffffed
[    3.396153@2] f960: ffffffc0c8bfb800 ffffffc0c8bfb810 ffffff8001db1bf8 ffffff8001db1c00
[    3.404126@2] f980: ffffff8001db1c08 ffffffbefe9d5224 0000000000000124 ffffff80201af9e0
[    3.412100@2] f9a0: ffffff8001d7ecb0 ffffff80201af9e0 ffffff80094e40e8 0000000080400149
[    3.420079@2] [ffffff80201af9e0+ 128][<ffffff80094e40e8>] of_clk_get+0x40/0x98
[    3.427330@2] [ffffff80201afa60+  96][<ffffff8001d7ecb0>] kbase_platform_device_probe+0x180/0xd90 [mali_kbase]
[    3.437238@2] [ffffff80201afac0+  48][<ffffff8009527f60>] platform_drv_probe+0x60/0xc8
[    3.445122@2] [ffffff80201afaf0+  64][<ffffff8009525d0c>] driver_probe_device+0x204/0x2b0
[    3.453267@2] [ffffff80201afb30+  48][<ffffff8009525e74>] __driver_attach+0xbc/0xc0
[    3.460894@2] [ffffff80201afb60+  64][<ffffff80095239fc>] bus_for_each_dev+0x74/0xb0
[    3.468607@2] [ffffff80201afba0+  32][<ffffff8009525418>] driver_attach+0x30/0x40
[    3.476060@2] [ffffff80201afbc0+  64][<ffffff8009524f10>] bus_add_driver+0x110/0x230
[    3.483774@2] [ffffff80201afc00+  32][<ffffff80095269e0>] driver_register+0x68/0x100
[    3.491487@2] [ffffff80201afc20+  32][<ffffff8009527e84>] __platform_driver_register+0x54/0x60
[    3.500125@2] [ffffff80201afc40+  16][<ffffff8001de6018>] kbase_platform_driver_init+0x18/0x1000 [mali_kbase]
[    3.509949@2] [ffffff80201afc50+ 112][<ffffff8009083ac4>] do_one_initcall+0x44/0x138
[    3.517663@2] [ffffff80201afcc0+  48][<ffffff80091b3b38>] do_init_module+0x64/0x1cc
[    3.525289@2] [ffffff80201afcf0+ 288][<ffffff8009143500>] load_module+0x1ca0/0x23f8
[    3.532914@2] [ffffff80201afe10+   0][<ffffff8009143f10>] SyS_finit_module+0xc8/0xd8
[    3.540627@2] [0000000000000000+   0][<ffffff80090838c0>] el0_svc_naked+0x34/0x38
[    3.548081@2] Code: 2a1303e3 9105e042 91062021 aa1403e0 (f9400e95) 
[    3.554417@2] ---[ end trace 05d0ac1fce7e23e2 ]---
[    3.565682@0] init: Restarting subcontext 'u:r:vendor_init:s0'
[    3.603449@1] audit: type=1400 audit(1420070409.636:8): avc:  denied  { sys_nice } for  pid=2670 comm="init" capability=23  scontext=u:r:vendor_init:s0 tcontext=u:r:vendor_init:s0 tclass=capability permissive=1
[    3.623308@3] spidev: disagrees about version of symbol module_layout
[    3.624304@3] spidev: disagrees about version of symbol __class_create
[    3.630646@3] spidev: disagrees about version of symbol class_destroy
[    3.637087@3] spidev: disagrees about version of symbol get_device
[    3.643191@3] spidev: disagrees about version of symbol kmem_cache_alloc_trace
[    3.650394@3] spidev: disagrees about version of symbol put_device
[    3.656541@3] spidev: disagrees about version of symbol spi_sync
[    3.662510@3] spidev: disagrees about version of symbol of_match_device
[    3.669104@3] spidev: disagrees about version of symbol device_create
[    3.675516@3] spidev: disagrees about version of symbol driver_unregister
[    3.682285@3] spidev: disagrees about version of symbol dev_err
[    3.688171@3] spidev: disagrees about version of symbol nonseekable_open
[    3.694837@3] spidev: disagrees about version of symbol spi_setup
[    3.700916@3] spidev: disagrees about version of symbol __spi_register_driver
[    3.708016@3] spidev: disagrees about version of symbol __register_chrdev
[    3.714771@3] spidev: disagrees about version of symbol device_destroy
[    3.721279@3] spidev: disagrees about version of symbol no_llseek
[    3.727341@3] spidev: disagrees about version of symbol dev_printk
[    3.733494@3] spidev: disagrees about version of symbol kmalloc_caches
[    3.744090@3] spi_meson_spicc: disagrees about version of symbol module_layout
[    3.747415@3] spi_meson_spicc: disagrees about version of symbol devm_request_threaded_irq
[    3.755430@3] spi_meson_spicc: disagrees about version of symbol devm_kmalloc
[    3.762536@3] spi_meson_spicc: disagrees about version of symbol platform_driver_unregister
[    3.770864@3] spi_meson_spicc: disagrees about version of symbol platform_get_irq
[    3.778328@3] spi_meson_spicc: disagrees about version of symbol devm_pinctrl_put
[    3.785771@3] spi_meson_spicc: disagrees about version of symbol spi_finalize_current_transfer
[    3.794340@3] spi_meson_spicc: disagrees about version of symbol dummy_dma_ops
[    3.801559@3] spi_meson_spicc: disagrees about version of symbol devm_clk_get
[    3.808655@3] spi_meson_spicc: disagrees about version of symbol spi_alloc_device
[    3.816088@3] spi_meson_spicc: disagrees about version of symbol put_device
[    3.823025@3] spi_meson_spicc: disagrees about version of symbol device_reset
[    3.830131@3] spi_meson_spicc: disagrees about version of symbol _dev_info
[    3.836977@3] spi_meson_spicc: disagrees about version of symbol spi_sync
[    3.843730@3] spi_meson_spicc: disagrees about version of symbol __class_register
[    3.851194@3] spi_meson_spicc: disagrees about version of symbol gpiod_direction_output_raw
[    3.859510@3] spi_meson_spicc: disagrees about version of symbol platform_get_resource
[    3.867417@3] spi_meson_spicc: disagrees about version of symbol spi_alloc_master
[    3.874891@3] spi_meson_spicc: disagrees about version of symbol class_unregister
[    3.882321@3] spi_meson_spicc: disagrees about version of symbol dev_err
[    3.888981@3] spi_meson_spicc: disagrees about version of symbol devm_spi_register_master
[    3.897131@3] spi_meson_spicc: disagrees about version of symbol devm_clk_register
[    3.904666@3] spi_meson_spicc: disagrees about version of symbol __platform_driver_register
[    3.912995@3] spi_meson_spicc: disagrees about version of symbol pinctrl_lookup_state
[    3.920788@3] spi_meson_spicc: disagrees about version of symbol spi_setup
[    3.927637@3] spi_meson_spicc: disagrees about version of symbol devm_ioremap_resource
[    3.935514@3] spi_meson_spicc: disagrees about version of symbol gpio_to_desc
[    3.942625@3] spi_meson_spicc: disagrees about version of symbol devm_pinctrl_get
[    3.950082@3] spi_meson_spicc: disagrees about version of symbol pinctrl_select_state
[    3.957881@3] spi_meson_spicc: disagrees about version of symbol of_device_get_match_data
[    4.022505@3] audit: type=1400 audit(1420070410.056:11): avc:  denied  { read } for  pid=2679 comm="hwservicemanage" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:hwservicemanager:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.022507@2] audit: audit_lost=2 audit_rate_limit=0 audit_backlog_limit=64
[    4.069340@1] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/data
[    4.071124@1] init: [libfs_mgr]Filesystem on /dev/block/data was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x46
[    4.085789@1] EXT4-fs (mmcblk0p16): Ignoring removed nomblk_io_submit option
[    4.103356@3] EXT4-fs (mmcblk0p16): recovery complete
[    4.103396@3] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[    4.104407@1] logd.auditd: start
[    4.104421@1] logd.klogd: 4048145001
[    4.120503@3] init: [libfs_mgr]check_fs(): mount(/dev/block/data,/data,ext4)=0: Success
[    4.161427@1] init: [libfs_mgr]check_fs(): unmount(/data) succeeded
[    4.162396@1] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/data
[    4.175159@3] type=1400 audit(1420070410.208:18): avc: denied { read } for comm="e2fsck" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.189163@3] type=1400 audit(1420070410.208:18): avc: denied { read } for comm="e2fsck" name="libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    4.208144@3] type=1400 audit(1420070410.208:19): avc: denied { getattr } for comm="e2fsck" path="/vendor/lib/libOmxCoreSw.so" dev="mmcblk0p12" ino=503 scontext=u:r:fsck:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
[    5.007817@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.007817@2] 
[    5.008586@2] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[    5.008586@2] 
[    5.016409@2] e2fsck: Pass 2: Checking directory structure
[    5.016409@2] 
[    5.023290@2] e2fsck: Pass 3: Checking directory connectivity
[    5.023290@2] 
[    5.030649@2] e2fsck: Pass 4: Checking reference counts
[    5.030649@2] 
[    5.037532@2] e2fsck: Pass 5: Checking group summary information
[    5.037532@2] 
[    5.045128@2] e2fsck: /dev/block/data: 21100/256000 files (17.0% non-contiguous), 622689/1023198 blocks
[    5.045128@2] 
[    5.056891@2] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/data
[    5.063961@2] EXT4-fs (mmcblk0p16): Ignoring removed nomblk_io_submit option
[    5.072464@2] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.081852@2] init: [libfs_mgr]__mount(source=/dev/block/data,target=/data,type=ext4)=0: Success
[    5.091138@0] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/cache
[    5.098511@0] EXT4-fs (mmcblk0p9): Ignoring removed nomblk_io_submit option
[    5.106393@0] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[    5.115579@0] init: [libfs_mgr]check_fs(): mount(/dev/block/cache,/cache,ext4)=0: Success
[    5.143473@3] init: [libfs_mgr]check_fs(): unmount(/cache) succeeded
[    5.144365@3] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/cache
[    5.171220@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.171220@2] 
[    5.171994@2] e2fsck: cache: clean, 28/65536 files, 12746/262144 blocks
[    5.171994@2] 
[    5.180990@0] EXT4-fs (mmcblk0p9): Ignoring removed nomblk_io_submit option
[    5.188715@0] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.198533@0] init: [libfs_mgr]__mount(source=/dev/block/cache,target=/cache,type=ext4)=0: Success
[    5.207935@0] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/param
[    5.214960@0] init: [libfs_mgr]Filesystem on /dev/block/param was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x46
[    5.226948@0] init: [libfs_mgr]check_fs(): mount(/dev/block/param,/mnt/vendor/param,ext4)=-1: No such file or directory
[    5.237495@0] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/param
[    5.275744@2] e2fsck: e2fsck 1.44.4 (18-Aug-2018)
[    5.275744@2] 
[    5.276540@2] e2fsck: /dev/block/param: recovering journal
[    5.276540@2] 
[    5.283603@2] e2fsck: Superblock last mount time (Thu Nov 12 19:40:08 2020,
[    5.283603@2] 
[    5.292161@2] e2fsck: 	now = Thu Jan  1 00:00:11 2015) is in the future.
[    5.292161@2] 
[    5.300489@2] e2fsck: Fix? yes
[    5.300489@2] 
[    5.305184@2] e2fsck: 
[    5.305184@2] 
[    5.309156@2] e2fsck: Pass 1: Checking inodes, blocks, and sizes
[    5.309156@2] 
[    5.316772@2] e2fsck: Pass 2: Checking directory structure
[    5.316772@2] 
[    5.323889@2] e2fsck: Pass 3: Checking directory connectivity
[    5.323889@2] 
[    5.331247@2] e2fsck: Pass 4: Checking reference counts
[    5.331247@2] 
[    5.338103@2] e2fsck: Pass 5: Checking group summary information
[    5.338103@2] 
[    5.345721@2] e2fsck: /dev/block/param: 15/4096 files (13.3% non-contiguous), 1388/4096 blocks
[    5.345721@2] 
[    5.357119@2] EXT4-fs (mmcblk0p14): Ignoring removed nomblk_io_submit option
[    5.365467@2] EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: nodelalloc,nomblk_io_submit,errors=panic
[    5.374684@2] init: [libfs_mgr]__mount(source=/dev/block/param,target=/mnt/vendor/param,type=ext4)=0: Success
[    5.401519@0] media_clock: disagrees about version of symbol module_layout
[    5.403131@0] media_clock: disagrees about version of symbol of_find_device_by_node
[    5.410483@0] media_clock: disagrees about version of symbol kmem_cache_alloc_trace
[    5.418025@0] media_clock: disagrees about version of symbol devm_clk_get
[    5.424791@0] media_clock: disagrees about version of symbol of_match_device
[    5.431856@0] media_clock: disagrees about version of symbol kmalloc_caches
[    5.439524@0] register clk_set_setting cpu[43]
[    5.447565@0] firmware: disagrees about version of symbol module_layout
[    5.450035@0] firmware: disagrees about version of symbol release_firmware
[    5.456631@0] firmware: disagrees about version of symbol request_firmware
[    5.463499@0] firmware: disagrees about version of symbol kmem_cache_alloc_trace
[    5.470817@0] firmware: disagrees about version of symbol kmem_cache_alloc
[    5.477665@0] firmware: disagrees about version of symbol cdev_add
[    5.483811@0] firmware: disagrees about version of symbol __class_register
[    5.490646@0] firmware: disagrees about version of symbol device_create
[    5.497256@0] firmware: disagrees about version of symbol kmem_cache_free
[    5.503998@0] firmware: disagrees about version of symbol class_unregister
[    5.510875@0] firmware: disagrees about version of symbol device_destroy
[    5.517516@0] firmware: disagrees about version of symbol cdev_init
[    5.523756@0] firmware: disagrees about version of symbol kmalloc_caches
[    5.530436@0] firmware: disagrees about version of symbol cdev_del
[    5.537305@3] Registered firmware driver success.
[    5.542225@3] Try to load video/h264_enc.bin  ...
[    5.547144@0] load firmware size : 76288, Name : video/h264_enc.bin.
[    5.552858@0] Try to load video/video_ucode.bin  ...
[    5.568356@0] load firmware size : 1816576, Name : video/video_ucode.bin.
[    5.593878@0] decoder_common: disagrees about version of symbol module_layout
[    5.598048@0] decoder_common: disagrees about version of symbol filp_open
[    5.602192@0] decoder_common: disagrees about version of symbol vfs_write
[    5.608980@0] decoder_common: disagrees about version of symbol devm_kmalloc
[    5.616008@0] decoder_common: disagrees about version of symbol platform_driver_unregister
[    5.624172@0] decoder_common: disagrees about version of symbol platform_get_irq
[    5.631586@0] decoder_common: disagrees about version of symbol fget
[    5.637870@0] decoder_common: disagrees about version of symbol fd_install
[    5.644752@0] decoder_common: disagrees about version of symbol sched_setscheduler
[    5.652253@0] decoder_common: disagrees about version of symbol dummy_dma_ops
[    5.659345@0] decoder_common: disagrees about version of symbol kmem_cache_alloc_trace
[    5.667261@0] decoder_common: disagrees about version of symbol wake_up_process
[    5.674556@0] decoder_common: disagrees about version of symbol __free_pages
[    5.681556@0] decoder_common: disagrees about version of symbol kmem_cache_alloc
[    5.688928@0] decoder_common: disagrees about version of symbol __class_register
[    5.696327@0] decoder_common: disagrees about version of symbol platform_device_unregister
[    5.704503@0] decoder_common: disagrees about version of symbol vf_reg_provider
[    5.711816@0] decoder_common: disagrees about version of symbol kmem_cache_free
[    5.719082@0] decoder_common: disagrees about version of symbol class_unregister
[    5.726460@0] decoder_common: disagrees about version of symbol vf_unreg_provider
[    5.733910@0] decoder_common: disagrees about version of symbol vfs_read
[    5.740577@0] decoder_common: disagrees about version of symbol of_reserved_mem_device_init_by_idx
[    5.749516@0] decoder_common: disagrees about version of symbol __platform_driver_register
[    5.757722@0] decoder_common: disagrees about version of symbol __alloc_pages_nodemask
[    5.765628@0] decoder_common: disagrees about version of symbol platform_device_register_full
[    5.774102@0] decoder_common: disagrees about version of symbol vfs_fsync
[    5.780881@0] decoder_common: disagrees about version of symbol filp_close
[    5.787747@0] decoder_common: disagrees about version of symbol kmalloc_caches
[   11.540301@0] vout: aml_tvout_mode_work: monitor_timeout
------>branch lineage-16.0_odroidg12_64_test5
Always check and use branch with latest commit
These users thanked the author voodik for the post:
joerg (Sat Dec 19, 2020 3:43 am)
Buy me a beer ;)
https://www.paypal.me/voodikjan
BTC: 377wXjEr3QsDDzRqfMco3a41wicrsv3Sfs
--------------------------------------------------------
dump logs
(dmesg; logcat -d; lsusb) | curl -F 'f:1=<-' ix.io
--------------------------------------------------------
ADB enhanced PuTTY :!:
https://github.com/voodik/puttyadb/releases

User avatar
joerg
Posts: 1257
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2, N1, N2, C4
Location: Germany
Has thanked: 80 times
Been thanked: 164 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by joerg »

I get the same result. UI does not come up. I see that my kernel now also has 10.0MB as the original one.
Do I need a special toolchain?

Code: Select all

gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu/bin/
Or do I need to copy all the kernel modules to emmc?

Code: Select all

  LD [M]  drivers/input/touchscreen/sx8650.ko
  LD [M]  drivers/media/usb/gspca/gspca_main.ko
  LD [M]  drivers/net/usb/huawei_cdc_ncm.ko
  LD [M]  drivers/net/usb/qmi_wwan.ko
  LD [M]  drivers/net/wireless/ath/ath.ko
  LD [M]  drivers/net/wireless/ath/ath10k/ath10k_core.ko
  LD [M]  drivers/net/wireless/ralink/rt2x00/rt2800lib.ko
  LD [M]  drivers/net/wireless/ralink/rt2x00/rt2800usb.ko
  LD [M]  drivers/net/wireless/ralink/rt2x00/rt2x00lib.ko
  LD [M]  drivers/net/wireless/ralink/rt2x00/rt2x00usb.ko
  LD [M]  drivers/spi/spi-meson-spicc.ko
  LD [M]  drivers/spi/spidev.ko
  LD [M]  drivers/staging/fbtft/fb_agm1264k-fl.ko
  LD [M]  drivers/staging/fbtft/fb_bd663474.ko
  LD [M]  drivers/staging/fbtft/fb_hx8340bn.ko
  LD [M]  drivers/staging/fbtft/fb_hx8347d.ko
  LD [M]  drivers/staging/fbtft/fb_hx8353d.ko
  LD [M]  drivers/staging/fbtft/fb_hx8357d.ko
  LD [M]  drivers/staging/fbtft/fb_ili9163.ko
  LD [M]  drivers/staging/fbtft/fb_ili9320.ko
  LD [M]  drivers/staging/fbtft/fb_ili9325.ko
  LD [M]  drivers/staging/fbtft/fb_ili9340.ko
  LD [M]  drivers/staging/fbtft/fb_ili9341.ko
  LD [M]  drivers/staging/fbtft/fb_ili9481.ko
  LD [M]  drivers/staging/fbtft/fb_ili9486.ko
  LD [M]  drivers/staging/fbtft/fb_pcd8544.ko
  LD [M]  drivers/staging/fbtft/fb_ra8875.ko
  LD [M]  drivers/staging/fbtft/fb_s6d1121.ko
  LD [M]  drivers/staging/fbtft/fb_s6d02a1.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1289.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1305.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1306.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1325.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1331.ko
  LD [M]  drivers/staging/fbtft/fb_ssd1351.ko
  LD [M]  drivers/staging/fbtft/fb_st7735r.ko
  LD [M]  drivers/staging/fbtft/fb_st7789v.ko
  LD [M]  drivers/staging/fbtft/fb_tinylcd.ko
  LD [M]  drivers/staging/fbtft/fb_tls8204.ko
  LD [M]  drivers/staging/fbtft/fb_uc1611.ko
  LD [M]  drivers/staging/fbtft/fb_uc1701.ko
  LD [M]  drivers/staging/fbtft/fb_upd161704.ko
  LD [M]  drivers/staging/fbtft/fb_watterott.ko
  LD [M]  drivers/staging/fbtft/fbtft.ko
  LD [M]  drivers/staging/fbtft/fbtft_device.ko
  LD [M]  drivers/staging/fbtft/flexfb.ko
  LD [M]  drivers/usb/serial/ch341.ko
  LD [M]  drivers/usb/serial/cp210x.ko
  LD [M]  drivers/usb/serial/ftdi_sio.ko
  LD [M]  drivers/usb/serial/option.ko
  LD [M]  drivers/usb/serial/pl2303.ko
  LD [M]  drivers/usb/serial/usb_wwan.ko
  LD [M]  drivers/video/backlight/lcd.ko
  LD [M]  drivers/video/fbdev/core/fb_sys_fops.ko
  LD [M]  drivers/video/fbdev/core/syscopyarea.ko
  LD [M]  drivers/video/fbdev/core/sysimgblt.ko
  LD [M]  drivers/video/fbdev/core/sysfillrect.ko
  LD [M]  fs/efivarfs/efivarfs.ko
  LD [M]  net/bridge/br_netfilter.ko

mad_ady
Posts: 9090
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, C4, N1, N2, H2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 597 times
Been thanked: 584 times
Contact:

Re: [ROM][LineageOS 17.1][Android 10.0][voodik] for the ODROID-C4

Post by mad_ady »

Did you build it from voodik's defconfig? I didn't need to change the modules when recompiling the kernel.
If you're flashing dybs too, take care that the format has changed. dtbs partition is not the same as the dtbs file and is a cpio archive with several dtbs/dtbo files. Flashing the dtb to dtbs instead of the cpio will cause a boot loop.
These users thanked the author mad_ady for the post:
joerg (Sat Dec 19, 2020 7:30 pm)

Post Reply

Return to “Android”

Who is online

Users browsing this forum: No registered users and 0 guests