Ukhellfire

Oh ive got some heatsinks im going to wack on them. not quite that big, but still! haha! Well the only reason im mention it, is because of the lock up, and the fact that when it was running the orangepi3 armbian, and the orangepi os, it was nowhere near as hot... Well today has been a lot of error solving, chasing my tail etc... but it has taught me one thing. Start with the simpler things! Haha! Today has been spent trying to get the WiFi module to build properly. With no success. So for now, I'm going to concentrate on bringing the board up properly first. Make sure everything else is working etc... Then I'll battle the WiFi. I think it's going to be the hardest part to this to be honest. Just going to leave this here 😉 Running very smoothly too! I guess I'll be battling the WiFi sooner than I thought! Do need to swap the leds over in the config so the green led is on when it's booted though! It's the little things!

I have just read through that aswell! Wow! Very observant me! Good News! It boots! i can log in. desktop shows. feels like the cpu is overheating somewhat, and then eveything locks up. No Wifi, but im pretty certain thats due to the fact its not enabled in the dts file. This is the least of my worries though at the moment.

I've gone through that documentation so many times! I must of scanned over that and missed it! Thank you! It's worked! Is there any way to pass this without having to set it as a flag every time I build? Now to test it! Fire it up!

Ah OK. It does seem to be when compiling wifi drivers. rtl88x2bu I believe... So I shall give this a go! Is there anywhere I can find extra build flags like this? Is there a list anywhere?

Oh OK! Yeah that's probably a bit different I guess? Haven't looked at it. I dont see see why that wouldn't work. Except my kernel isn't 100% complete yet. The driver needs editing and little bits etc... Have just discovered that my patches wernt being applied properly on armbian build though. Well now I'm stuck here...

Are you bringing the board up through patches? Are you putting the patches in the patches folder? Or the userpatches folders? I shall bare this in mind thank you!

What gets me, is it boots with the orange pi 3 image. So I'm trying the orange pi 3 uboot! Then I'll start adding things over slowly, see what breaks it. Trial and error. The long way, instead of a uart debug adaptor. If not I'll buy one! Haha!

If I submitted a pull request with the config file with a .csc extension, and then offered myself as a maintainer, would armbian change the extension for me? Or would I need to submit another pr? I may just start from scratch on a clean build repo and do a wip config file 😉 think I may have to offer my services. At the moment, I'm building up the commits to submit a pull request. Making sure I'm not forgetting things etc. Making things as tidy as possible. As soon as I know it boots etc, you'll be more than welcome to try the build! I can either upload the img somewhere, or you can build it from my forked repo. Obviously I'll let you know when it's all fully complete. At the moment there's thing sitting locally that I haven't pushed as a commit. So the build would fail. As for the WiFi and ethernet, I'll keep that in mind. I'm hoping using the boards actual dts files etc may help with this. Not sure yet. Plus I discovered the WiFi driver was looking in the wrong place for the WiFi firmware! So I've corrected that to. Haha if only they would send me presents! That would be cool. I'll have another of the same boards! Or maybe an opi 4? Haha! If only! May have to ping them a little message let them know I've done it though! What a lot of work for a couple of day! So I've tested the first of the orange pi 3 lts builds... It doesn't boot. Intact the board doesn't actually turn on, or seem to turn on, with the sdcard plugged in... very strange. Thinking it may be something with uboot. Not sure yet.

So... I've been bringing up the board properly. Using the correct dts files for the 3 lts and not the 3. Both for kernel and uboot. I've created a whole patch set for the Orange Pi 3 LTS now. Ready and waiting for a pull request once I've done a test build. If it boots. And runs, I'll submit the pull request. One thing I'm not sure off though, is, would it be a wip or a csc? We shall see! Haha!

Check the other thread above I linked...

Haha thank you! It started purely selfish! I want armbian for my board! Haha! But then noone seems to be doing it, so figured I would. I have plenty of experience in this department. I used to reverse engineer drivers etc for mediatek soc phones. This is exactly the same. And this is all open source, and I feel strongly about open source, so will glady do it all publicly! At the moment it's booting, it runs quite well. Ethernet only works when booting with the cable connected. If you connect the cable once already booted, it doesn't kick in. Not worried about that one at the moment. It's probably just a persistent permission thing. As for the WIFI: Kernel modules build. The whole image builds and boots now. But the WiFi still doesn't work. The modules are found in /vendor/modules but are not loaded on boot. I can see this with the output of "lsmod" OK. I'll load the modules myself. "Insmod uwe5622_bsp_sdio.ko" I get an error. "insmod error could not insert module uwe5622_bsp_sdio.ko invalid module format" Now I'm think I need to delve into my kmsg and see what's going on when I run this command. If anyone with any experience is willing to give me a heads up if they've encountered this before? Feel free!

Haha that's OK then! Don't wana start off on the wrong foot! Haha! Well I'm going to need people to test once I got things working if you or anyone is interested?

Update. So, I seem to be getting compilation errors. And thankfully armbian logs everything during a build. Haven't had time to sit and go through it properly, but it seems to be (as I expected) the tty side of my ported drivers. Not to sure if it's a conflict, or whether it's just due to the fact the driver is from an older kernel than what armbian builds. This I'll look I to over the next couple of days. At the moment I have a few hours every evening (except today, typical! Just when I need spare time!) Going to leave the errors here, incase anyone has a spare few minutes before I do! The highlights are purely the word "error" haha! After more digging. I beleive its down to a deprecated function: alloc_tty_driver Which was deprecated by: tty_alloc_driver Conclusion, I was kinda right. It's because it's a driver from an old kernel! Now to change over the function, and try get this working! Wish me luck! Well... I'm on a roll. Some errors have been sorted. Some errors have been suppressed through makefile. These errors are only warnings though being thrown up, so everything should be OK. Fingers crossed! Running a build now, and will be testing tonight. So far the build hasn't errored out! Let's give this a go! I hope people don't mind me recording my progress here BTW. I've kind of hijacked the thread! Sorry!

https://github.com/afaulkner420/Linux-Mainline-5.15y/commit/59cc9191b9acc88a2f6a318d7bce5c2fc7fa2476 Commit here for the drivers if anyone wants to take a look...

And so the fun begins...!

Drivers ported. Patches created. Patches added to build/userpatches/kernel/sunxi-current. Bit of a hacky approach to adding lines to config files, for modules etc. But want to see if it works first. Then to create patches for them! Now building a test build 😉 So it turns out that the firmware files are already automatically imported into the build! One step forward! Now after putting the modules in the right config file (doh!) I'm running another build. Unfortunately I won't be able to test until a lot later 😞 I'll keep everyone posted! Then I guess I'll create the patches, test, and probably bring up the board properly!

Still playing with creating patches at the moment. Can't you compile against this kernel and uboot? Failing that, maybe your own repo, commit whats needed, and send pull request? Just a thought?

@Igor question for you if you don't mind answering or pointing me in the direction of I fo with the answer? When building armbian, the patches. All the patches in the patch folder, do they all get applied? Or are the patches called by the specific board in a config somewhere? the link you posted above for the r1+. He adds patches for certain things, but nothing calls them. Is it just a case of adding a patch if something never before seen in armbian is needed?

Been looking into this a bit. https://forum.armbian.com/topic/19846-orange-pi3-lts/?do=findComment&comment=136479 due to the fact it's already working for other boards, surely this is an easy fix? I will be having a build and play shortly

Ah brilliant! I shall take a look! I've run out of time recently. Have booted orange pis official ubuntu for it. And it works. WiFi and ethernet. So if this update doesn't work, the drivers can be ported. I've had a fair bit of experience with this, when I was reverse engineering drivers for the lcm on mediatek soc phones. Does the orange pi 3 boot on the lts? Have you tried this? Well apparently wifi drivers are available. Maybe we just have to enable it? https://linux-sunxi.org/Wifi#AW859A Off to find the dts now! I'm looking at this line in particular... https://github.com/armbian/build/blob/master/config/boards/orangepizero2.conf#L5 As it also appears here... https://github.com/orangepi-xunlong/orangepi-build/blob/main/external/config/boards/orangepi3-lts.conf#L6 I feel a build coming on!!! Definitely think I'm onto something... https://github.com/orangepi-xunlong/linux-orangepi/commits/orange-pi-5.10/drivers/net/wireless/uwe5622 I think a long evening porting the driver over, figuring out if I need to pull in firmware too, and where from. And then building/testing... And possibly some patches coming our way!

Hi all! I'm new to this community, and am about to dive into the world of the orange pi 3 lts! It's due for delivery today, and I already have built every variant from orange pis build script. I plan to port over the support for the pi 3 lts from their own github, as I believe other things have slightly changed to. I believe this to be a great board with a lot of potential! My plan is to 1) port, and then 2) submit patches for approval over here. Fingers crossed! Good luck to everyone else involved!