ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | Armbian 20.11 Tamandua released | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
Glock24 has joined #armbian
Glock24 has quit [Ping timeout: 256 seconds]
<locki>
now i cand fing graphics in dmesg:( so i dont have fb1 device
<locki>
is time to go to bed ...
Glock24 has joined #armbian
locki has quit [Quit: Connection closed]
sunshavi has joined #armbian
Toast has quit [Ping timeout: 240 seconds]
R0b0t1 has quit [Ping timeout: 256 seconds]
R0b0t1 has joined #armbian
ChriChri has quit [Ping timeout: 256 seconds]
ChriChri has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 256 seconds]
ChriChri_ is now known as ChriChri
ChriChri_ has joined #armbian
ChriChri- has joined #armbian
ChriChri has quit [Ping timeout: 265 seconds]
ChriChri has joined #armbian
ChriChri_ has quit [Ping timeout: 264 seconds]
ChriChri- has quit [Ping timeout: 264 seconds]
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 240 seconds]
ChriChri_ is now known as ChriChri
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 272 seconds]
ChriChri_ is now known as ChriChri
R0b0t1 has quit [Ping timeout: 272 seconds]
R0b0t1 has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 240 seconds]
ChriChri_ is now known as ChriChri
Glock24 has quit [Read error: Connection reset by peer]
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 265 seconds]
ChriChri_ is now known as ChriChri
R0b0t1 has quit [Ping timeout: 265 seconds]
R0b0t1 has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 265 seconds]
ChriChri_ is now known as ChriChri
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 240 seconds]
ChriChri_ is now known as ChriChri
steev has quit [Read error: Connection reset by peer]
steev has joined #armbian
archetech has joined #armbian
archetech has left #armbian [#armbian]
s_frit has joined #armbian
chewitt has quit [Quit: Adios!]
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 240 seconds]
ChriChri_ is now known as ChriChri
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 264 seconds]
ChriChri_ has quit [Ping timeout: 240 seconds]
ChriChri has joined #armbian
ChriChri has quit [Ping timeout: 256 seconds]
ChriChri has joined #armbian
ChriChri has quit [Ping timeout: 240 seconds]
flyback has quit [Ping timeout: 260 seconds]
flyback has joined #armbian
<mangix>
how do you edit kernel cmdline again?
qCactus has joined #armbian
<IgorPec>
mangix: add extraargs= to the /boot/armbianEnv.txt
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
archetech has joined #armbian
archetech has left #armbian [#armbian]
<ArmbianTwitter>
@haerwu (Marcin Juszkiewicz): I got an idea for blog post during weekend. But need some help. Need to create a list of Linux distribution claiming to support aarch64. CentOS, Debian, Fedora, OpenSuse, Ubuntu are known to everyone. Arch, Armbian, Alpine are already of my list. Any other suggestions? https://tinyurl.com/y5dy7ng3 (11s ago)
<tlwoerner>
specifically i downloaded the armbian buster image
<tlwoerner>
i'd really like to be able to find the kernel sources for that build, but i keep getting lost in the build script
<tlwoerner>
and i keep ending up at a 4.4 kernel, instead of a 5.10 :-)
<tlwoerner>
when i build a 5.10.12 kernel from upstream, my boot doesn't work (it gets stuck while booting the kernel)
<tlwoerner>
but the 5.10.12 kernel in the armbian image works great
<tlwoerner>
i'd like to know if your kernel is patched in any way
f476 has joined #armbian
f476 has quit [Ping timeout: 240 seconds]
<qCactus>
I've fixed mainline u-boot to work on my devboard and want to now build armbian with it. How do I make the build script use my own repo instead of fetching from upstream every time?
<IgorPec>
tlwoerner: this hw is not officially supported since we have no hw or no maintiner. can't tell why its not working
<IgorPec>
kernel is heavily patched, yes
<IgorPec>
qCactus: i assume you have read build documentation and you are still lost?
<qCactus>
IgorPec: Yes. I've discovered the .ignore_changes magic file that way, but it seems to have no effect on the repo
<IgorPec>
you want temporal or permanent change?
<qCactus>
well, I guess permanent in the sense of "until these changes get merged into mainline"
Herc_ has joined #armbian
<qCactus>
lib
<IgorPec>
we mainly use patches for that
<IgorPec>
but you can also point to your branch
<IgorPec>
by adding overrites to userpatches/lib.config
<IgorPec>
any variable can be overrired this way ... but this will make a change for all variants, if you will build other board it will still use this override
<qCactus>
The lines you linked seem to involve the kernel, though... did I understand correctly that I need to just add definitions concerning u-boot to the same place?
<IgorPec>
u-boot is treated the same way
grae has joined #armbian
<tlwoerner>
IgorPec: sorry i wasn't clear, your image for this board works great!
The-going has quit [Quit: Konversation terminated!]
<IgorPec>
martinayotte: is your farm at most recent u-boot / kernel ?
<grae>
just curious, anyone have any tips for hunting down rockchip I2S clock issues?
<grae>
I'm digging through differences between the FriendlyElec 4.4 image and the current Armbian DTB's (21.02.2), and am a little stumped at what's missing
<[TheBug]>
other than it is likely that FriendlyElec is using BSP vs Armbian compiling it's own legacy kernel with patches? I am not sure.
<[TheBug]>
also, what board?
<[TheBug]>
'rockchip' is pretty general
<grae>
NanoPi M4V2
<[TheBug]>
so rk3399, okay
<[TheBug]>
so your best person to wait on an answer from will likely be Tonymac_32 but he is working and won't be around to later in the night EST
<[TheBug]>
I am sure if he sees your question he will comment, but again I think its mostly, if anything like Raxda's image
<[TheBug]>
that FriendlyArm built BSP kernel which is different than Armbians
<grae>
yeah, there's code differences as well
<[TheBug]>
as in kernel provided directly by rockchip vs Armbian kernel w/ patches
<IgorPec>
not sure if we were doing anything around i2s on this board
<IgorPec>
that part is probaly just copy past
<IgorPec>
so its possibly wrong
<grae>
that's fair, but dmesg fills with "rockchip-i2s ff890000.i2s: Fail to set mclk -22", and the best I've done so far is disable the device
<IgorPec>
i2s is used also for hdmi / dp
<[TheBug]>
grae: which kernel on the Armbian side?
<IgorPec>
perhpas thats related
<IgorPec>
or driver doesn't pic it up right or wrong pin
<grae>
theres two messages, one for &i2s1 (audio jack) and &i2s2 (hdmi). Both complain
<IgorPec>
ahaa
<[TheBug]>
I also see [ 2059.548699] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22 in my dmesg , assuming thats what your checking
<grae>
yep
<[TheBug]>
I was led to believe that has something to do with GPU / Graphics
<[TheBug]>
lead*
<IgorPec>
well, dunno , didn't dag in this areas
<[TheBug]>
I think lanefu and I were BSing back and forth about it at one point and that is what we decided, but I can't fully remember
<grae>
I figured I'd check if there was any known problems, before I went digging through device tree binding documentation
<[TheBug]>
ohh no, wait
<[TheBug]>
isn't it related to audio
<[TheBug]>
[ 2059.548710] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
<grae>
yes, ff8a0000 is the HDMI audio, ff890000 is the headphone jack
<IgorPec>
yes
<[TheBug]>
I was lead to believe those errors don't actually cause any major problems / letting devices be enabled don't seem to cause any major issue for me
<[TheBug]>
Also ASoC should indicate it's ALSA having issues
<[TheBug]>
using puleaudio instead may also resolve that
<grae>
yep, "ASoC: error at snd_soc_dai_set_s"
<martinayotte>
IgorPec: I'm using any farm, only some desktop computer...
locki has quit [Quit: Connection closed]
<IgorPec>
martinayotte: sunxi :)
<IgorPec>
did you play with recent u-boot?
<martinayotte>
recently, I've done a build for OPiOnePlus, it was using default 20.10 without issue