lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC>
<Keurig> Orange pi 5 and wifi dongle question.
<DC-IRC>
<Keurig> I have a usb wifi. It never works after armbian boot up. I need to unplug it and reseat it then it works.
<DC-IRC>
<Keurig> Is there a way to make the wifi persistant on boot up?
<DC-IRC>
<Keurig> I have tried the 3.0 and the 2 - 2.0 ports
<DC-IRC>
<TheJtornero> Hello, want to use Rockpi 4C+ with LTSP (Linux Terminal Server Project). I need to be able to make a PXE boot, so far I am able to but I have to enter into uboot menu at every startup. Has anyone made that with the compile.sh script?
<DC-IRC>
<IgorPec> no, this is something you will need to develop
<DC-IRC>
<IgorPec> its not supported
<DC-IRC>
<IgorPec> those wireless drivers are sometimes in a terrible state and there is little Armbian ca do about. Keeping them in build-able state on always changing kernels is already hard and the problem you are mentioning is probably related to this old and buggy kernel. Already that represent serious commitment. You can try hacks like unloading, loading module ...
<DC-IRC>
<rpardini> I'd say, "awesome", as always!.... I'd only ask for you to add a branch that is a copy of the previous/current state, so we can revert to it if needs be... (release is coming very soon)
<DC-IRC>
<rpardini> Rebase looks good. If I export the patches from old, and export patches from new, and compare them, they look _sane_
<DC-IRC>
<rpardini> So I'd say _go for it_
<DC-IRC>
<amazingfate> You can checkout a new branch from tag with command like `git checkout linux-5.10-gen-rkr4 -b rockchip-linux-rkr4`
<DC-IRC>
<rpardini> yep exactly, just push a branch or tag there so we've a reference to the old branch and it is not gc collected by git 👍
<DC-IRC>
<amazingfate> I intend to update to rkr4 after the release.
<DC-IRC>
<rpardini> oh, ok. I thought we'd push last-minute. It is, technically, a "bugfix" so would be valid as well 😉
<DC-IRC>
<rpardini> either way you're the boss....
<DC-IRC>
<amazingfate> I may change my mind to toggle branch at last minute🤣 I've been using rkr4 kernel for days.
<DC-IRC>
<rpardini> Yeah, let me go and cherry pick your armbian branch (for rk4 / the correct rock-5a) and I'll make some images for the guys to test.
<DC-IRC>
<rpardini> Release is looking good. Just built 421 images tonight successfully
<DC-IRC>
<rpardini> hopefully @IgorPec is also having success?
<DC-IRC>
<IgorPec> morning
<DC-IRC>
<IgorPec> i will leave you guys to decide if we merge this
<DC-IRC>
<IgorPec> i am too far away from this
<DC-IRC>
<rpardini> yeah, I'd say is 100% @amazingfate's call -- I'm also just jockeying stuff back and forth, my 3588 is actually doing apt repo work 😉
<DC-IRC>
<rpardini> the kedge2 conversion is completed, tested, and working.... inclusive bluetooth
<DC-IRC>
<IgorPec> yes, will it survive rkr4 tag ?:)
<DC-IRC>
<rpardini> I'll test later. Given AF's track record: _yes_
<DC-IRC>
<rpardini> will be nice to review OPI5 (and variants) too
<DC-IRC>
<IgorPec> i can test once its merged, its more verifying ...
<DC-IRC>
<IgorPec> current test process -> artefacts -> repo -> test
<DC-IRC>
<rpardini> I am only a bit/slightly disappointed in Indiedroid folks, they've done well with their (separate) build, but the proper kernel PR is hanging there (mostly due to adding a frakked up wifi driver)
<DC-IRC>
<rpardini> for months now
<DC-IRC>
<rpardini> so 23.05 will be the most complete 3588 build ever, and only Indiedroid will miss the bus
<DC-IRC>
<rpardini> (and for sure people will use their custom build and come here for support. hold your horses)
<DC-IRC>
<IgorPec> ah, leave it. its their job to fix it
<DC-IRC>
<rpardini> if you think, 3-5 months of poor users coming here to get support for unnoficial build, vs investing some time this week and getting it official...
<DC-IRC>
<rpardini> looks like to me they're selling a _metric ton_ of those boards.
<DC-IRC>
<IgorPec> but the way how they are dealing with this is ... pushing all problems and costs to us
<DC-IRC>
<rpardini> yeah, they should partner up is what I say. it is _not_ too late.
<DC-IRC>
<rpardini> let's call them or something. a few hours this week will save us a lot of trouble down the next few months.
<DC-IRC>
<IgorPec> i am not saying its too late, just its low priority
<DC-IRC>
<IgorPec> btw. are you perhaps seeing this? "I noticed a couple months ago that setup of minimal images were complaining about missing utilites.
<DC-IRC>
<IgorPec> On the Rock-pi-s, the minimal image seemed to put the terminal into a bad state during the initial setup where:
<DC-IRC>
<IgorPec> many keystrokes were being dropped (unless one took care to type v e r y s l o w l y)
<DC-IRC>
<IgorPec> the netui utility simply failed
<DC-IRC>
<IgorPec> At the time, I thought the errors so obvious that I assumed they would be fixed by whoever submitted the breaking patch.
<DC-IRC>
<IgorPec> Unfortunately, the problem is still present.
<DC-IRC>
<IgorPec> It's difficult for me to believe this is impacting only the RockPI-S ?
<DC-IRC>
<IgorPec> Are you testing minimal images?"
<DC-IRC>
<balbes150> this is the conclusion from my image
<DC-IRC>
<NicoD> Was there anything special you needed to do to enable it on your images? I think other builds also had the same issue.
<DC-IRC>
<balbes150> Apart from the correct assembly of the u-boot and the kernel, I'm not doing anything special.
<DC-IRC>
<Tenkawa> Note he is using a very old u-boot
<DC-IRC>
<Tenkawa> U-Boot 2017.09. I don't think that's what current images usde
<DC-IRC>
<Tenkawa> U-Boot 2017.09. I don't think that's what current images use
<DC-IRC>
<Tenkawa> (I'm checking now)
<DC-IRC>
<balbes150> funny, trying to get a UART console on edg2, but doesn't know which u-boot is used there.... there are only two options for edg2 - u-boot-2017 and EDK2, the main u-boot-2023 is only for Rock 5, but it is experimental and not yet intended for mass use.
<DC-IRC>
<Tenkawa> What are you talking about?
<DC-IRC>
<Tenkawa> Khadas has been updating u-boot that "branch" as of a few weeks ago... its not had a "name" change however so its a very badly named version
<DC-IRC>
<rpardini> Thanks. See there how `U-Boot SPL 2017.08 (Aug 30 2022 - 16:31:59) ` while your u-boot is only loaded later (`U-Boot 2017.09-armbian (May 24 2023 - 14:47:41 +0300)`) from MMC. Current images ship no u-boot at all, and work directly from the u-boot in SPI. That's how Khadas images in oowow work too AFAIK. Good thing, since we'll be targeting oowow soon. Unfortunately their u-boot in SPI can't boot bootscripts boot.scr, so I had to sti
<DC-IRC>
<rpardini> I do agree that investing time in EDK2 is best for those boards, so as much as we can avoid hacking uboot the better.
<DC-IRC>
<Tenkawa> @rpardini why would we ignore Khadas's updates directly they have been making for it?
<DC-IRC>
<rpardini> Well, feel free to chase the vendor's uboot, or use Oleg's, both work.
<DC-IRC>
<rpardini> Oleg's ready to go.
<DC-IRC>
<rpardini> The vendors' is a bit targeted at oowow, and not general OS use, last I looked.
<DC-IRC>
<c0rnelius> It's vendor u-boot, they aren't going to bother changing the version and rev in the makefile.
<DC-IRC>
<rpardini> (my thinking is: leave uboot alone, use factory SPI one, invest time in edk2.)
<DC-IRC>
<rpardini> Oleg also has a good edk2 blob.
Tenkawa has joined #armbian-rockchip
Tenkawa has quit [Client Quit]
<DC-IRC>
<Tenkawa> @amazingfate commpiled and booted right up... now to see if the uart runs any better
<DC-IRC>
<Tenkawa> Linux kedge 5.10.160-kedge #1 SMP Wed May 24 14:29:07 EDT 2023 aarch64 GNU/Linux
<DC-IRC>
<Tenkawa> @amazingfate one thing I did notice is an initial test of the usb3 port with a thumb drive shows much higher io speeds