ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | | Github: | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: ->
CrashTestDummy2 has quit [Quit: Leaving]
chewitt has joined #armbian
indy has quit [Quit: ZNC 1.8.2 -]
CrashTestDummy has joined #armbian
chewitt has quit [Quit: Zzz..]
steev has quit [Ping timeout: 268 seconds]
steev has joined #armbian
NishanthMenon has quit [Ping timeout: 268 seconds]
NishanthMenon has joined #armbian
indy has joined #armbian
indy has quit [Ping timeout: 268 seconds]
Manouchehri has quit [Ping timeout: 245 seconds]
NishanthMenon has quit [Ping timeout: 260 seconds]
steev has quit [Ping timeout: 256 seconds]
lvrp16 has quit [Ping timeout: 268 seconds]
NishanthMenon has joined #armbian
steev has joined #armbian
lvrp16 has joined #armbian
Manouchehri has joined #armbian
sunshavi has joined #armbian
indy has joined #armbian
indy has quit [Ping timeout: 244 seconds]
poxifide has quit [*.net *.split]
archetech has quit [Quit: Konversation terminated!]
poxifide has joined #armbian
ddurst has quit [*.net *.split]
nekomancer[m] has quit [*.net *.split]
marshall[m] has quit [*.net *.split]
solderfumes has quit [*.net *.split]
mcfrdy has quit [*.net *.split]
PPAChao has quit [*.net *.split]
mwfc has quit [*.net *.split]
mwfc has joined #armbian
PPA has joined #armbian
ddurst has joined #armbian
mcfrdy has joined #armbian
solderfumes has joined #armbian
marshall[m] has joined #armbian
nekomancer[m] has joined #armbian
ikmaak has quit [Ping timeout: 268 seconds]
archetech has joined #armbian
ikmaak has joined #armbian
indy has joined #armbian
indy_ has joined #armbian
indy has quit [Ping timeout: 244 seconds]
payano has joined #armbian
indy_ is now known as indy
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
threenp has quit [Remote host closed the connection]
samythemany has quit [Remote host closed the connection]
samythemany has joined #armbian
threenp has joined #armbian
Guest24 has joined #armbian
Guest24 has quit [Client Quit]
RoBo_V25 has joined #armbian
RoBo_V25 has quit [Client Quit]
payano has quit [Quit: leaving]
archetyp has joined #armbian
stipa has quit [Ping timeout: 244 seconds]
archetech has quit [Quit: Leaving]
archetech has joined #armbian
sunshavi has quit [Ping timeout: 256 seconds]
stipa has joined #armbian
TRS-80 has joined #armbian
yangmobi1e has quit [Changing host]
yangmobi1e has joined #armbian
archetech has quit [Quit: Konversation terminated!]
Redentor has joined #armbian
<TRS-80> So I guess maskrom is basically just a lookup table pointing to some address where to find the next software to load in boot process?
Redentor has quit [Quit: Leaving]
lanefu has quit [Read error: Connection reset by peer]
sunshavi has joined #armbian
The_Loko has joined #armbian
<Armbian-Discord> <T​onymac32> Well it's an extremely minimalistic first stage loader
threenp has quit [Remote host closed the connection]
samythemany has quit [Remote host closed the connection]
samythemany has joined #armbian
threenp has joined #armbian
alekksander has joined #armbian
<nekomancer[m]> IgorPec: I fix my `focal` builder, now it can build rootfs for `hirsute` again. Fix was a reset of qemu-user-static with text `docker run --rm --privileged multiarch/qemu-user-static --reset -p yes`
alekksander has quit [Quit: Konversation terminated!]
<c0rnelius> Thats a common problem with focal
<c0rnelius> they completely fucked qemu some how.
<c0rnelius> If you use hirsute doesn't break.
flyback has quit [Remote host closed the connection]
flyback has joined #armbian
<c0rnelius> and I mean hirsute as the host via docker or actually building native or cross.
<c0rnelius> I haven't noticed any major issues yet with impish or jammy. But... Its Ubuntu so we shall see.
chilly has joined #armbian
<nekomancer[m]> I am just afraid to upgrade focal armbian on my N2
<c0rnelius> Well would be no point going to Hirsute its almost EOL.
<c0rnelius> Problem is everytime there is an update, ur gonna need to run that command again.
<c0rnelius> If it involves qemu
chilly has quit [Quit: Leaving]
<c0rnelius> One reason I'm currently working on moving to Jammy. Which is still like 7 months off from being a stable release? Or something like this.
<c0rnelius> And my lord. Clang-13 is not any faster than Clang-12 when it comes to compiling a kernel :\
Guest7 has joined #armbian
<Guest7> Hi, can someone help me with HDMI issue on rk3288 v3?
<Guest7> IgorPec I've saw your comments on the forum about HDMI -> DVI issues, maybe I can learn something from you?
<nekomancer[m]> c0rnelius: you tink clang into armbian build script?
<c0rnelius> nekomancer[m]: No its a experiment of my own making.
<c0rnelius> Would be interesting though to insert into Armbian. Make things take longer though, thats for sure.
The_Loko has quit [Remote host closed the connection]
<[TheBug]> Guest7: I am not certain on your issue, but it would not suprise me to find that there is some type of flag or change to the dtb needed to correct that as it sounds like you are most likely not using an active DVI adapter so it maye require some config change to bring up
<[TheBug]> unfortunately I do not know what it would be off top of my head
<[TheBug]> has some suggestions to try there at least
<[TheBug]> I think disp_dvi_compat=1 is the main thing your needing
<Guest7> [TheBug] thank you! Accidentally I've just landed there!
<Guest7> after I change armbianEnv should I just reboot or something else is needed?
<[TheBug]> yes you will need to reboot
<Guest7> looks like the guys in that thread didn't have any luck with that
<Guest7> I'm trying to use it with a simple 1024x768 res
<Guest7> should I set monitor=hdmi or monitor=dvi in this case?
<[TheBug]> did you have this working previously on another image?
<[TheBug]> or is this the first time you are trying to make it work?
<Guest7> I had this working with ayufan-rockchip but this one had problems with RTC, so I've moved to armbian
<[TheBug]> yeah so on legacy kernel
<[TheBug]> are you using legacy kernel on Armbian to test
<[TheBug]> it may work better out of box than mainline
<[TheBug]> also it may be that you still have to patch dtb in some way to bring it up
<[TheBug]> may have to do with whether or not display is providing EDID and actually communicating
<[TheBug]> you should also be able to get some info on this in the dmesg on boot
<[TheBug]> so if you have a USB TTL serial adapter I would hook it to see what its outputting on console there
<Guest7> that sounds pretty hard
<[TheBug]> also I haev read that some of the drivers don't like to put out DVI resolution under 1920x1080 at least that is what I read on one thread
<[TheBug]> so could be related there
<[TheBug]> but I would start off by
<[TheBug]> first getting Armbian Legacy kernel version
<[TheBug]> and see if that works out of the box
<[TheBug]> then I would suggest if you want mainline, also checking some of the older archived images to see if this is something that has broken in recent version
<Guest7> can I switch that dynamically without breaking other stuff like python?
<Guest7> (kernel)
<[TheBug]> I mean you will need to write whole new image I would think
<[TheBug]> and test with it
<Guest7> wouldn't Buster be a better alternative?
<[TheBug]> BTW here are where you can find archived images for Rock64 -
<[TheBug]> one of our archives
<TRS-80> And btw Guest7 please don't ping Igor for private support, we don't want the poor over workedd man to come in here and yell at you and then it gets on Reddit that Armbian is some horrible project full of mean people, ya dig? :)
<Guest7> @+TRSE-80 got it!
<[TheBug]> wb TRS-80
<TRS-80> o/
<[TheBug]> what rock you been hiding under
<[TheBug]> it must be a comfortable rock
<[TheBug]> ;p
<TRS-80> been working man, it's a grind when I do it but then I can take some time off (which I just started today) and do what I want for a little while
<[TheBug]> yeah I took today off as well
<[TheBug]> or would be distracted working currently
<TRS-80> I mean I will be taking the next months off ;)
<[TheBug]> ohh well fun
<[TheBug]> I don't get 'months' off
<[TheBug]> lol
<[TheBug]> lucky to get 'weeks'
<[TheBug]> so what you saying is you are gonna be hard at work here helping out with Armbian ;p
<[TheBug]> ?
<[TheBug]> hehehe
<Armbian-Discord> <T​onymac32> I been working 12's for the man for weeks, it's a mess over here
<Guest7> [TheBug] alright, I can try other versions, but can you recommend one which is known to work with RTC and HDMI->DVI cables?
<Armbian-Discord> <T​onymac32> I did take some days off though
<[TheBug]> Guest7: well seeing as the current doesn't and I would assume that it shoud... it could easily be a regression that hasn't been reported so.. can't really tell you where to start
<[TheBug]> other than I would assume based on what I read
<[TheBug]> this shouldn't be an issue in Legacy
<[TheBug]> but its also a whole different driver
<TRS-80> as I said, trade off is they own almost all my time when I am working, hence disappearing for all that time
<[TheBug]> mainline you may have to try a few and see
<Guest7> I see, thank you
<[TheBug]> Tonymac32: you ever used DVI on Rock64?
<Armbian-Discord> <T​onymac32> no, only hdmi. The signal paths are the same though, HDMI is just a fancy plug with extra stuff like audio
<TRS-80> I plan on helping some at Armbian, yes, but also have bunch of personal projects to work on as well. Currently trying to get the word out about upcoming changes to Supported status on many devices.
<[TheBug]> yeah but I have seen weird issues with some DVI adapter that don't pass EDID through correctly
<nekomancer[m]> does rock64 have dvi?!
<[TheBug]> my guess is that is part of the issue
<[TheBug]> as I see weird patches that supposedly try to get around devices that don't advertise edid correctly
<Armbian-Discord> <T​onymac32> well right, if the cable isn't I2C'ing correctly, no bueno, manual settings time
<[TheBug]> nekomancer[m]: adapter from HDMI -> DVI is no so uncommon
<[TheBug]> though usually I would suggest an active adapter so you don't end up with issues but what Tonymac32 said is also very much true, it should ' just work ' in most cases as it's just pins being remapped
<Guest7> I mean, I have no problem with that setting being manually set and fixed
<Guest7> I just don't know what to try
<[TheBug]> well first would be to try legacy image as noted and see if it works
<[TheBug]> this at least gives you a starting point
<[TheBug]> cause if it isn't working in Legacy I would say it may be something with the adapter or display and not passing EDID or the communications needed for the display to negotiate with the output
<[TheBug]> You mentioned it worked in Ayufan's images so it likely will work in our Legacy image
<[TheBug]> next I would start with an older mainline image and test it
<[TheBug]> Guest7: another thing you need to be aware of is there is a reason Rock64 is CSC (community support) in Armbian and it is because those boards are not great quality to start in general and have lots of weird hardware bugs, so it is very possible in mainline we have just been pushing images and not really fully testing them as we don't currently have a maintainer there
<[TheBug]> most of us if we have a Rock64 have v1 or v2 generally
<[TheBug]> not saying v3 is bad but after issues with v1 and v2 we kinda stopped having active support because of all the weird issues
<Guest7> As for me you're doing a great job, because RTC worked straight out of the box
<Guest7> it's just a matter of getting this weird HDMI -> DVI cable to be interpreted correctly
<[TheBug]> yeah
<[TheBug]> best is if you can see the output in dmesg when it does fail
<[TheBug]> it will make it more obvious
<[TheBug]> but for that you need a USB to Serial adapter to plug to the board
<[TheBug]> so you can see the console when it comes up without video
<[TheBug]> this would at least get you closer to the 'why' of it not working
<[TheBug]> my guess is you would see it fails to negotiate or something similar
<Guest7> thanks, unfortunately the board is not near me
<Guest7> all I have is an ssh connection to it currently
<TRS-80> What's the word I am looking for like 28nm, is that node size or ... ?
<TRS-80> There is some other word, it is on the tip of my tongue.
<Armbian-Discord> <l​anefu> Never stop negotiating
<Guest7> @+TRS-80 ... process?
<nekomancer[m]> resolution? techprocess? stopgap?
<nekomancer[m]> lithography?
<stipa> process size
<TRS-80> process was the word I was thinking, thanks
<stipa> yw
<stipa> TRS-80: but nekomancer[m] can go deeper into it if you have the balls