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>
<.richn> you building cli
<DC-IRC>
<.richn> edge/current
<DC-IRC>
<.richn> out line more of the issue
<DC-IRC>
<.richn> just saying it does not work does not explain anything
<DC-IRC>
<patrickdk> hmm, didn't even know you where talking to me, as most of what you said doesn't apply
<DC-IRC>
<patrickdk> not sure what building cli means
<DC-IRC>
<patrickdk> booted the bookworm image off the armbian website
<DC-IRC>
<patrickdk> keyboard doesn't work, it's missing 10 out of 12 keypresses
<DC-IRC>
<patrickdk> something keeps running randomly starting/stopping a much of services
<DC-IRC>
<patrickdk> if I run sh instead of bash the keyboard almost works fine, but then programs just dont run
<DC-IRC>
<patrickdk> installed bullseye and it's all good
<DC-IRC>
<.richn> the issue is armbian rolled back alot of rk3399 kernels because the media kernel was not being updated/maintained
<DC-IRC>
<.richn> I knwo thereis work on it to bring it back to par
<DC-IRC>
<patrickdk> what does rk3399 have to do with the rk3588?
<DC-IRC>
<.richn> looking if i can find a diff img
<DC-IRC>
<.richn> I missed that board
<DC-IRC>
<.richn> ok ... hmm
<DC-IRC>
<.richn> the device tree has to be worked on like the new T6 we are working on . its using provider kernel src
<DC-IRC>
<.richn> let me look
<DC-IRC>
<patrickdk> was there some reason not to use the 5.10.110 kernel from bullseye? it works fine
<DC-IRC>
<.richn> becuase most new imgs they build a new kernel for that platform bullseye/bookworm/sid
<DC-IRC>
<.richn> but I am reviewing
<DC-IRC>
<.richn> it has to do with their build system
<DC-IRC>
<patrickdk> but every release has 5.10.y hmm
<DC-IRC>
<.richn> its a linux/android kernel mess
<DC-IRC>
<.richn> but yse it was out
<DC-IRC>
<.richn> but the src they are using if from friendlyelec
<DC-IRC>
<.richn> I am digging the code
<DC-IRC>
<.richn> it seems they have a cpy of the provider kkernel src and they have patched it and it moght not be 100 bookworm compatable it seems
<DC-IRC>
<.richn> going to have to look further in to it once the T^ is finished and the new code is into the kernel src.
<DC-IRC>
<.richn> rk-3588 is still being added to the MLK
<DC-IRC>
<.richn> so there is not alot of support that is there yet
<DC-IRC>
<patrickdk> hmm
<DC-IRC>
<patrickdk> was attempting to get this setup to ship out 😦 oh well
<DC-IRC>
<patrickdk> somehow my other one works much nicer
<DC-IRC>
<.richn> 5.10 is a old kernel base
<DC-IRC>
<.richn> adn other then what the provider sent otu there is not much
<DC-IRC>
<.richn> if it used bullseye and worke well get the bullseye img and use it
<DC-IRC>
<.richn> it will remain support for a few more years
<DC-IRC>
<.richn> but once the kernel is fixed and updated they can change over
<DC-IRC>
<patrickdk> ya, I was attempting to get hdmi working
<DC-IRC>
<patrickdk> just works on bullseye
<DC-IRC>
<patrickdk> but I have to recompile and make new dtb to get it working on bullseye, possible, annoying
<DC-IRC>
<.richn> well there is work going on to get things into 6.4 but its taking time
<DC-IRC>
<.richn> rk3588 is a new and fast growing chip
<DC-IRC>
<patrickdk> ya, my opi5 has been fine, just alittle limited in ability
<DC-IRC>
<patrickdk> why I got the r6s also
<DC-IRC>
<patrickdk> didn't expect them to be that different
<DC-IRC>
<.richn> they are different makers diff functions
<DC-IRC>
<.richn> which have to go into a dtb
<DC-IRC>
<patrickdk> yes, but I mean the kernel on the same cpu
<DC-IRC>
<.richn> and the old dtb and the new dtb dont mesh
<DC-IRC>
<minervarhatesthepi> I posted on pine64 discord.. how this isn't resolved after several months of pinebooks not working from emmc? Ridiculous
<DC-IRC>
<minervarhatesthepi> Quite frustrating
<DC-IRC>
<minervarhatesthepi> If replacing the emmc were that easy, like 10 super tiny and annoying screws.
<DC-IRC>
<tenkawa42> @minervarhatesthepi 6.x kernels are "not" an everyday thing for a company that basicly just builds the hardware and releases it to the public
<DC-IRC>
<tenkawa42> Pine doesn't really support software
<DC-IRC>
<minervarhatesthepi> What? Manjaro is the official OS, it runs on mainline
<DC-IRC>
<tenkawa42> Manjaro isn't Pine
<DC-IRC>
<tenkawa42> its 3rd party
<DC-IRC>
<minervarhatesthepi> But manjaro is the official OS of the PBP
<DC-IRC>
<minervarhatesthepi> They ship manjaro on their pbps
<DC-IRC>
<tenkawa42> Only out of convenience
<DC-IRC>
<tenkawa42> Those machines have always been presented to me as "once its yours... be prepared to support ot yourself"
<DC-IRC>
<tenkawa42> Those machines have always been presented to me as "once its yours... be prepared to support it yourself"
<DC-IRC>
<minervarhatesthepi> I don't see your point. They ship the pbps with manjaro, not a forked linux like radxa.
<DC-IRC>
<minervarhatesthepi> Ohh no, that wasn't the idea. If so, then it's a horrible product
<DC-IRC>
<tenkawa42> umm...
<DC-IRC>
<tenkawa42> have you looked at other products.. rockpro64... for example...
<DC-IRC>
<tenkawa42> they don't offer any updates for it
<DC-IRC>
<minervarhatesthepi> I am not talking about support in the way that adding features, lkke we should have perfect vpu at this stage
<DC-IRC>
<minervarhatesthepi> I am asking it to work at least
<DC-IRC>
<tenkawa42> It did... when it was "released"
<DC-IRC>
<tenkawa42> not their fault the kernel changed
<DC-IRC>
<minervarhatesthepi> Ohh, but they keep selling them, pine64 isnt out of bussiness
<DC-IRC>
<minervarhatesthepi> And again, they dont ship the with a foked linux
<DC-IRC>
<minervarhatesthepi> They use mainline and rolling releases
<DC-IRC>
<minervarhatesthepi> Old armbian boots just fine from this emmc.
<DC-IRC>
<minervarhatesthepi> Someday vpu will actually work on common software (browsers,obs,mpv,etc), currently, that's not there. I've seen improvements like gamma control on 6.1, but not much and lot of regressions.
<DC-IRC>
<.richn> its going to take time to get the kernel back uptodate as the media kernel is no longer being updated. and maintained by the guy who did it
<DC-IRC>
<.richn> so its going to take time chillout man
<DC-IRC>
<.richn> limited staff anad limited people putting in time to help out makes it hard
<DC-IRC>
<.richn> we have 2 people working on rk chips and they are working on newer boards
<DC-IRC>
<.richn> if you have a issue go use Manjaro for the board
<DC-IRC>
<.richn> manjaro has a img for the PBP
<DC-IRC>
<.richn> I dont know what kernel they are using
<DC-IRC>
<.richn> your acting like this is a huge company its not
<DC-IRC>
<.richn> and its opensource
<DC-IRC>
<.richn> meaning you can work and submit patches
<DC-IRC>
<.richn> !000% wrong on this as newer kernel fix bugs and performance as device tree files get updated and kenel builds. with bug fixes .
<DC-IRC>
<.richn> I have the 6.1.30 and. i am booting mine up on serial console now
<DC-IRC>
<.richn> and testing
<DC-IRC>
<.richn> test the ubuntu vs the debian also
<DC-IRC>
<minervarhatesthepi> Sure, that's why I can't boot it properly. You can't deny that regression also tend to happen, not even rebooting works properly with modern kernel (from sd). I don't deny that modern kernel may fix some stuff and eventually add more features, but rk3399 development it's mostly dead by now. There is no enough interest. That's why I don't have much hopes of actually receiving new <clipped message>
<DC-IRC>
<minervarhatesthepi> features. I've been hearing the "vpu is coming to mainline" since 2018...
<DC-IRC>
<.richn> its a hardware isu not a os issue
<DC-IRC>
<.richn> stop blaiming if there is notice that some emmc dont work as expected thats not the os fault
<DC-IRC>
<.richn> I have 6.1.30 and I wiped the emmc and I am installing via armbian-config now
<DC-IRC>
<minervarhatesthepi> It's, older kernel works Rich. It's the software
<DC-IRC>
<.richn> well I am installing 6.1.30 right now no issue
<DC-IRC>
<.richn> other then I have to use serial console as I dont have a monitor on it
<DC-IRC>
<minervarhatesthepi> Sure, on your emmc may just work!
<DC-IRC>
<minervarhatesthepi> Not mine and many others.
<DC-IRC>
<minervarhatesthepi> It's nothing obscure, many reports of this, and that's why armbian site warns about it.
<DC-IRC>
<minervarhatesthepi> Armbian pbp site.
<DC-IRC>
<.richn> i have the orignal emmc I have 3 diff emmc all from pinebooks
<DC-IRC>
<minervarhatesthepi> You were lucky then
<DC-IRC>
<.richn> and I am going to test all 3
<DC-IRC>
<.richn> I have 2 pinebookpro boards with out monitors
<DC-IRC>
<.richn> and they are both on uarts right now
<DC-IRC>
<.richn> 1 have 64 and 1 has 128
<DC-IRC>
<.richn> have you tried the manjaro img
<DC-IRC>
<.richn> and see what it does
<DC-IRC>
<.richn> they dont say what kernel they are using in their imgs
<DC-IRC>
<.richn> the kernelsrc for the bullseye and the bookworm are coming from 1 place so its not a diff kernel src
<DC-IRC>
<.richn> the config file is the same
<DC-IRC>
<.richn> I am going over the config fiels
<DC-IRC>
<.richn> have you tried the 6.3 rdge img
<DC-IRC>
<.richn> looks 6.3 is sid only
<DC-IRC>
<.richn> ok both the boards I have loaded fine.
<DC-IRC>
<.richn> so I can confirm the current imgs work on the pbp as they stand.
<DC-IRC>
<.richn> I am telling oyu if you test like a say I want to know if you boot and wipe the emmc and put a balnk partiton on it does it install ok
<DC-IRC>
<.richn> with the 6.1.30 kernel
<DC-IRC>
<.richn> thats what I just did I wipe the chip before loading
<DC-IRC>
<.richn> I can build you a 6.3.x and let you test
<DC-IRC>
<rpardini> Hmm. That `LINUXFAMILY=rk35xx` change had escaped me
<DC-IRC>
<rpardini> Well I dunno. Sincerely for me it's ok this way. Boards were .wip anyway
<DC-IRC>
<efectn> I think it's a bit weird to have different families for legacy and edge kernel. Why don't we merge both completely?
<DC-IRC>
<rpardini> I agree...
<DC-IRC>
<amazingfate> Rk356x edge has already get merged into rockchip64.
<DC-IRC>
<Tonymac32> Yeah, I just need somewhere quiet to work for a bit before the "omfg add <feature> pls" and "Let me shit out 200 patches unchecked from another project on top of your work" people show up 😆
<DC-IRC>
<tenkawa42> sorry.. can't have that.... merge failed