Ukhellfire

Let me re-upload and I'll let you know Img re-uploaded... https://drive.google.com/file/d/1HUbTWB0GABIVviS3349FN11S0_Wy2jDN/view?usp=drivesdk Fingers crossed! Any chance of logs of you get to it @Kamileon

Is that the latest I've just uploaded? I've just edited the post with a new link? Can anyone get me a full u-boot log and dmesg from a non-booting build please? I'm finding it hard Debugging it, whilst mines booting...

Woops! I do apologise! Didn't even think about that!

Let me take more logs. I believe the eth is working now... I'm home now. Let me take some more.logs and upload them! So guys... There's another new build! This time I'm a bit more hopeful, but obviously I can be proved wrong like before! Haha! I've added some stock files from orangepis repos, and this seems to have sorted a few issues this end! Obviously I've been booting for a while, which is the most confusing thing ever, as noone else can. But I now have working ethernet, wifi and Bluetooth. This has all started working since this last build. Fingers crossed everyone else is more successful too! I really hope so! Please let me know how you get on! @Kamileon @orangepifan @Rockford the Roe @amaethon SCRAP THAT!! I missed something on that last one... Try this one: https://drive.google.com/drive/folders/1B7A_pc3W6GLBjt9vAkShh5scp4pQwFrc And here's a dmesg from this build booting: https://drive.google.com/file/d/1LQ5qgTZBLdhauLeqD3OArM8ci2uzLdnb/view?usp=drivesdk

I've got a full set of logs here from my board. Problem is, I seem to be able to boot, but noone else can? https://drive.google.com/drive/folders/1VSl0DS_GFbRpt1rp8PBDnV6QKI8KPOjY I'm not at home at the moment. Will be I I couple of hours. I can pull new, more recent logs then...

U-Boot SPL 2021.10-armbian (Mar 14 2022 - 08:18:53 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):a04808c1-dirty NOTICE: BL31: Built : 08:18:34, Mar 14 2022 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc07c170, model: OrangePi 3 LTS INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2021.10-armbian (Mar 14 2022 - 08:18:53 +0000) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 LTS DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3202 bytes read in 4 ms (781.3 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 154 bytes read in 3 ms (49.8 KiB/s) 35780 bytes read in 9 ms (3.8 MiB/s) 4191 bytes read in 6 ms (681.6 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 45000000 12462020 bytes read in 619 ms (19.2 MiB/s) 21735432 bytes read in 1077 ms (19.2 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=41710000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 12461956 Bytes = 11.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 4941d000, end 49fff784 ... OK Loading Device Tree to 00000000493ab000, end 000000004941cfff ... OK Starting kernel ... This was posted a couple of pages back from a non booting os

It's from the 5.16 kernel orangepi have just uploaded. It won't load. Getting errors. Also the boot errors... https://nextcloud.lodz.webredirect.org/s/T8dMn3gk2YHe64p

Sorry mate, image didn't load. Can you upload again? No we have boot problems too. Vcc-pc and vcc-pd bank regulator problems I believe. Can't figure it out! OK thanks!

Hmm OK. Are you able to grab a dmesg?

In that case I shall adjust my dtsi! Haha! Cheers! *** NEW BUILD COMING SOON *** This includes an extremely high probability of it booting! HAHA! And not only that, but wireless too! Aswell as other things... Keep your eyes open for it! So the new build is officially up. It's based on a load of new files and changes. So please please please test it and get back to me! Unfortunately wifi isn't working 😞 ethernet is though. Dmesg is clean for me. But would like to know if it is for you guys too. Please fire away with the logs! It can be found here: https://drive.google.com/file/d/1ge-aoMk0RTODJaViUNcdXgTbnJyzZCAu/view?usp=drivesdk @Kamileon @Rockford the Roe @orangepifan

Ah OK brilliant! Thank you I'll take a look! 👍 So it seems that my dtsi file already has this line. But the sunxi-mmc.c doesn't have this. I think I shall have a play and see what's happening!

On android though?

Didn't know whether you'd seen anything was all... ti's all good! Well I think I may have cracked it. It's all about vcc-pc and vcc-pd. Going by the nin booting dmesg. I believe this is different, because of the fact we have an emmc chip, which means vcc-pc is supplied by a different regulator! Eldo1! https://github.com/orangepi-xunlong/openwrt/blob/openwrt-21.02/target/linux/sunxi/patches-5.4/410-v5.6-arm64-dts-allwinner-a64-olinuxino-Add-bank-supply-re.patch#L13 This doesn't exist on either the OPi3 dts, or the dts that I'm using (I don't think, need to do some testing and reading), which would explain why your all getting the same errors over the OPi3 and the OPi3-LTS. I'll keep people posted!

Probably the defconfigs and dts files... you should compare uboot to kernel. Also, pull the defconfigs and dts files from your working android. Also, see this, and read the pdf. It will take some work. http://www.orangepi.org/downloadresources/Orange Pi 3 LTS/2021-12-27/OrangePi3LTS3f8a530c448a3ef4fc1fa323.html @igor on another note, I don't suppose you have any ideas on what might be happening with the booting and not booting issue I'm having building for the OPi3 Lts? I want to bring it up and possibly maintain it, but can't seem to figure out why people aren't able to boot my build? But I can?

@jernej The correct axp regulator settings? What we discussed above? Obviously I've got the settings 8n the dts and dtsi files. If these are the ones, they all seem correct! There's 2 extra lines in my dts This line: https://github.com/afaulkner420/Linux-Mainline-5.15y/blob/20254c2cf8c14d52162dc5cb93ac0b73965f8e2a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3-lts.dts#L203 And https://github.com/afaulkner420/Linux-Mainline-5.15y/blob/20254c2cf8c14d52162dc5cb93ac0b73965f8e2a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3-lts.dts#L204 And it seems that it's mmc2 that it's complaining about. 4022000.mmc which I believe is mmc2

At the moment I'm stumped. Not th sure where to find it all. Thought I did, but everything looked the same, OK. So maybe I didn't find it?

Ah OK. I was reading it wrong then. From what I understood it was the way it dished out addresses or whatever it is. I shall look into those settings. Otherwise, I haven't got a clue why it wouldn't be booting on others devices, unless it is power supply related like suggested? But Durley that would be down to the regulator settings too? So this can be sorted too? Either that or I'm u derstanding things wrong? Guess im kinda learning tidbits on the fly here! But I love it, its all good! I get a buzz out of getting things going! Haha!

Well I was thinking along those lines. As the builds aren't that different at all. Mine and orange pis. @Kamileon @orangepifan @Rockford the Roe This is the power supply I'm using... https://www.amazon.co.uk/dp/B09CPGFT3H/ref=cm_sw_r_apan_glt_i_F969Q5FGJYJHWW0QMBDP?_encoding=UTF8&psc=1 I'm booting very reliably now using this. this being said, I am going to try that one last ditch attempt to get it running on your boards with code change. The difference being, orangepi use I2C to manage the pmic, whereas armbian is using RSB. I'm going g to switch to I2C as a test and let you guys test that out. May not work, but may. They regulate things differently so maybe!

They are the exact same errors that I got rid of, that allowed me to boot. Somethings different in out setups I think. Maybe power supply rating? I don't know. Let me do another build..

Ah brilliant! I'll have a read through! Did anything stand out to you?

I did enable it in uboot? Have you tried all ports? Think mine worked in the top one of the 2. The USB3 port? Also, I've uploaded a new image. In the ethernet folder. Ethernet works perfectly, and I've removed the WiFi driver for now (it wasn't loading properly). The image now boots without any errors. Maybe this will help you to boot it? I've also got one more thing I want to try in regards to u reliable booting... I'll keep you posted in that one! @Kamileon

Ok this is strange. I really don't get why I can boot. But you can't? Are you able to grab a dmesg?

I've started digging into it a bit. It seems (from what I can see) that it's not every module. Just some. This could purely be down to the fact I haven't gone through and check absolutely everything. Just the booting sides of things... Yeah I'll build an OPi3 img and boot that. See what happens. I know the ethernet worked last time I tried that? Just had to plug it in from boot, as it wouldn't connect if I plugged in once booted.... Still, it's all a step closer! Tha k you for what you've done so far! Never know, I may get to the point of attempting to debug your WiFi driver too! Haha! @jernej So. I've built and booted the OPi3 image. And everything seems to be good at a slight glance. No red errors as it's booting saying about failing to load kernel modules etc... Will dig deeper shortly to double check! Although, digging a bit deeper with the OPi3-LTS build, I've found a few modules are are failing to load. I tried starting systemd-modules-load.service manually, and then run journalctl -xe as suggested by the prompt. The output is as follows: https://drive.google.com/file/d/1rdit5SVwaYIggGXfRa4NXQQxIwlnashm/view?usp=drivesdk There's 3 main modules. That's the 3 from the WiFi driver. So I've disabled them from the build for now. And am building again without them. Hopefully this allows systemd-modules-load.service to start properly...

I just reverted the commit that changed it in the first place. Both places are back to @745 now 😀 @jernej So it seems that it's booted! Straight away! No messing about! Obviously there a fair bit that isn't working. Ethernet, wifi, aswell as probably a few other things! Haha! I've managed to grab a load of logs. I'm still getting the modules error too? Link to logs... https://drive.google.com/drive/folders/1VSl0DS_GFbRpt1rp8PBDnV6QKI8KPOjY On another note, the img is up on google drive: https://drive.google.com/drive/folders/16UHmZsGD4qv7HqY5pPtZcQZ1WeEBDFA8 If anyone else is up for testing it for me? @Kamileon @Rockford the Roe @orangepifan If possible, if things don't boot etc, any chance of some logs back too? Pretty please? Haha! And bow I sit here and anxiously read through the plethora of logs, and await some testing!

I'm just impatient! Haha! If I can do something without buying something to, I'm all for it. Well I read the rx is 3.3v but the tx is 5v, so thought maybe! But I guess I'm outta luck! Haha! Oh well! I started off a build before I went to bed last night, with the regulator set back to @745 in kernel dts. Will be testing very shortly. So fingers crossed! I'll report back! I'm also going to tidy my repos up in github, so they make a bit more sense, and aren't just me messing with settings haha!