ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
chewitt has quit [Quit: Zzz..]
chewitt has joined #armbian
chewitt has quit [Client Quit]
alekksander has quit [Quit: Konversation terminated!]
<DC-IRC>
<rpardini> Md: yes. those are applied after the drivers. `6.2.0-rc3-meson64` is an old build, though.
<Md>
it's what I have found in the latest sid build available for the Banana Pi M5
<Md>
which, BTW, works fine with Armbian
lyri has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
arch3r has quit [Quit: bye]
alekksander has quit [Ping timeout: 240 seconds]
<nekomancer[m]>
rpardini: how to build `tools/perf` — `linux-tools-6.2.7-meson64.deb`?
alekksander has joined #armbian
lyri has quit [Ping timeout: 246 seconds]
lyri has joined #armbian
arch3r has joined #armbian
MrFixIt has quit [Remote host closed the connection]
MrFixIt has joined #armbian
alekksander has quit [Read error: Connection reset by peer]
alekksander has joined #armbian
lyri has quit [Ping timeout: 255 seconds]
lyri has joined #armbian
<DC-IRC>
<rpardini> great question, I asked that the other day. we gotta start building kernel tools, but it's userspace, really, and we've no provisions for it yet
<DC-IRC>
<rpardini> I needed `usbip`, ended up building it device side myself
<DC-IRC>
<rpardini> having a linux-source pkg would have helped, but it has not yet been resurrected.
<DC-IRC>
<rpardini> anyway, answer is: PRs accepted 😉
alekksander has quit [Quit: Konversation terminated!]
<nekomancer[m]>
curent system are very complicated :( I digging around more than week but still have no ideas
<nekomancer[m]>
my head too small to grok it
<nekomancer[m]>
<DC-IRC> "<rpardini> I needed `usbip..." <- how you do that? it looks like a start point for perf
<DC-IRC>
<IgorPec> good afternoon
<DC-IRC>
<IgorPec> that usbip used to work with a workaround ... its on a forum, but we haven't got to the state of building this withing tools
<DC-IRC>
<IgorPec> not those, not master
<DC-IRC>
<IgorPec> @rpardini what is the state of other artifacts caching? are there any hardcore problems behind?
KronosDm has joined #armbian
KronosD[m] has left #armbian [#armbian]
<DC-IRC>
<rpardini> shouldn't be. next up is armbian-config, then the bsp's
<DC-IRC>
<rpardini> it just work, no surprises or problems expected
<DC-IRC>
<rpardini> its just work, no surprises or problems expected
<DC-IRC>
<rpardini> but yeah, there are always some
junaid_ has quit [Remote host closed the connection]
<TRS-80>
I am pretty sure the new batch of PBP came with nothing on SPI flash, however I would like to confirm that before writing tow-boot (or similar) to it.
<TRS-80>
The instructions I found at https://wiki.pine64.org/wiki/Pinebook_Pro_SPI seem to require accessing the SPI via maskrom mode from a second machine, which seems ridiculous to me. Is there no easier way to do so directly from the PBP itself?
lyri has quit [Remote host closed the connection]
<p0g0>
TRS-80, if you boot the PBP from an SD card or USB, doesn't the SPI Flash detect as a block device?
<nekomancer[m]>
seems ok to device where you have to dismount tenh screws to access to switch to change boot order, to switch to enables serial console in audio socket, and to do serial console switcheable with audio socket.
<nekomancer[m]>
they completely mad.
<p0g0>
I've left Manjaro on both my PBPs, booting from SD instead, so I haven't tried to flash them.
<TRS-80>
I can't boot from SD card. RK3399 boot order is SPI, eMMC, SD card. Yes it's stupid. Apparently they did not put any bootloader on SPI on new batch. And switch does not work for me to turn off eMMC. But in case where I thought I had switch off, it is also possible that my Armbian image did not work.
<TRS-80>
nekomancer[m]: You will get no arguments from me. I am just trying to get this thing I paid for working. For like the Nth time in the year or whatever since I bought it. :(
<p0g0>
So you cannot boot the thing at all? That's harsh.
<nekomancer[m]>
good luck with it
<archetech>
so you want to erase the spi + write zeros to it
<archetech>
so you want to erase the spi = write zeros to it
<p0g0>
well, how to write anything to it...
<archetech>
I did it on my rock5
<nekomancer[m]>
my pbp lays in box for some years. unbootable on unknown reason.
<p0g0>
iirc there is a serial console but I think that took some nifty cable
zeemate has joined #armbian
<TRS-80>
nekomancer[m]: I am telling you the reasons my friend! :)
<TRS-80>
p0g0: Yes let's not get into that, lol.
<p0g0>
the OP5, that was easy to set up...
<archetech>
nekomancer[m]: dig it out and clear the spi
<nekomancer[m]>
I did.
<p0g0>
hmm, the serial console should let you revise the boot sequence, tho that's more a guess than anything.
<TRS-80>
OK, so some helpful person in #pinebook just told me that /dev/mtd0 is the device I am looking for. That does appear in Manjaro that came on it. So I will dd that somewhere and see what's in there. I suspect nothing on my recent batch.
<p0g0>
wait, you can boot Manjaro?
<archetech>
ya cant its machine code in mtd0
<TRS-80>
nekomancer[m]: In your case I think installing tow-boot (or similar) to SPI should do it. I just want to see what's there ex factory, before I write over it. Just out of curiosity.
<TRS-80>
p0g0: Yes, sorry if that wasn't clear. To me that's equally as unusable as not being able to boot (apologies to archetech <3 lol).
<TRS-80>
archetech: OK but wouldn't it just be all 00s if so? I could view in a hex veiwer of some kind I am guessing.
<archetech>
you either clear it or reflash it to stock
<p0g0>
Yeah, I don't use or like Manjaro, but I did not have any trouble booting from an SD so, I've not had your troubles...
<TRS-80>
p0g0: Is your PBP original batch? Those came with some bootloader on SPI, I am pretty sure.
<p0g0>
They are a couple of years old.
<TRS-80>
Yep, original batch.
<p0g0>
maybe a bit more
<TRS-80>
Mine I got with newer batch.
<p0g0>
well, I might be able to dd off the data from mine if that's any virtue (but not right now).
<TRS-80>
I am about to try on mine right now
<p0g0>
I'm afk for a while, gl
<TRS-80>
cheers
<TRS-80>
appears to be all <FF>
<TRS-80>
up to hex 01000018 which is 16777240 decimal, pretty close to 16 MiB it's supposed to be I guess?
Flecks has quit [Ping timeout: 246 seconds]
TRS-80 has quit [Quit: Later, taters!]
TRS-80 has joined #armbian
<DC-IRC>
<Jason123> TRS-80 you can flash spi right from linux
<DC-IRC>
<Jason123> what pinebook pro you have? the ones from 2021?
<DC-IRC>
<Jason123> right after they had to raise the price
<TRS-80>
I bought mine mid 2022, second batch. Yes I am trying to flash tow-boot, but instructions seem to want to do so indirectly by putting some 'installer' on an sd card first. Is there no way to flash directly to the SPI (/dev/mtd0) device?
<DC-IRC>
<Jason123> make sure the spi is cleared first mine was all ready
<DC-IRC>
<Jason123> but you can flash directly to the spi
<TRS-80>
On second batch I am pretty sure they came empty. I even double checked.
<TRS-80>
I guess I did not find those instructions yet, I'll keep looking, thanks.