<KotCzarny>
did you miss the part of setting 'bootargs' ?
<yekka>
there is no boot.cmd on my boot partition. only boot.scr and changing any bit of it will result in a failed boot.
<KotCzarny>
boot.scr is just boot.cmd with uboot header on top
<KotCzarny>
as in checksum etc
<KotCzarny>
so just copy boot.scr to boot.cmd, remove few binary chars at start, edit, then add header with mkimage
<KotCzarny>
mkimage -C none -A arm -T script -d boot.cmd boot.scr
<KotCzarny>
is the command
<yekka>
Thank you KotCzarny.
<KotCzarny>
i've added that info to the page just now
jelly has quit [Read error: Connection reset by peer]
<KotCzarny>
also, this information is further down the page in 'installing uboot' section. which i admit isnt the right place
hpagseddy[m] has joined #linux-sunxi
<KotCzarny>
unless it was, before addition of other booting methods
Danct12 has joined #linux-sunxi
jelly-home has joined #linux-sunxi
<yekka>
Thats great KotCzarny. Thanks for updating wiki
dddddd has joined #linux-sunxi
<libv>
as i said several times before
<libv>
the changelog and list of supported devices should not live there, the first should be a separate page, the other should be collapsible
<libv>
it makes people unable to see the real info on that page
<fALSO>
Yo good morning
<libv>
but this is what happens when people use the wiki as a glorified changelog.
<KotCzarny>
k
<fALSO>
Just got a non sunxi board
<KotCzarny>
im gonna butcher uboot's page now
<fALSO>
rockpro64
<fALSO>
gonna play with it today
<libv>
KotCzarny: thanks, but...
<libv>
look at what happened to the mainline page
<KotCzarny>
yeah, mainline uboot's page
<KotCzarny>
that is
<libv>
err, mainline kernel page... the changelog was moved over, and then it was continued on the main page regardless
<KotCzarny>
we will prevail!
<KotCzarny>
just watch me
xqdzn has quit [Remote host closed the connection]
craigo has joined #linux-sunxi
<KotCzarny>
done.
<KotCzarny>
how do you like it?
<libv>
KotCzarny: where did the devices list go? someone will complain, sadly
<KotCzarny>
see 'see also'
<libv>
ah, right
<KotCzarny>
its also more readable that way
<KotCzarny>
more concise
<libv>
yeah, but it might help to mention that as a link in the initial blurp
<libv>
indeed
<libv>
but as a user errs into that page (having missed his device page), he will wonder whether his device is at all supported
<libv>
not showing the full list is good
<libv>
but it might help to link to it
<KotCzarny>
feel free to add some descriptive text
<libv>
right
<libv>
willco
yekka has quit [Ping timeout: 258 seconds]
megi has joined #linux-sunxi
yekka has joined #linux-sunxi
jelly-home is now known as jelly
<yekka>
@KotCzarny I did as you told and problem is fixed thanks.
<KotCzarny>
good
antoine89 has joined #linux-sunxi
<yekka>
can add a hint to wiki about initial boot.cmd too? some, like me may not know that they are essentially the same (except the first line) and since there is no boot.cmd example file around.
<KotCzarny>
it's very distro dependant
<KotCzarny>
some might not even use boot.* and just set uboot env directly
<yekka>
ok. thanks for the fast support! now those damn led's can lit up ;D
<antoine89>
KotCzarny what is the best way to modify my SID? is it possible to burn the SID fuses, and will they all then show 1, meaning that the information is modified? or is it possible to supply 2.5V to the GND pin to enable writing?
<KotCzarny>
um
<KotCzarny>
first of all, i hope you have plenty of boards to test things
<KotCzarny>
:)
<antoine89>
, i'll get more only if it works
<KotCzarny>
how would you know if you have to experiment?
<antoine89>
i have 1 that i am willing to spare
<KotCzarny>
only few people (1?) experimented with writing sid
<antoine89>
could you point me to that person?
<KotCzarny>
hmm, cant remember the nick
nexgen has quit [Quit: Leaving]
<KotCzarny>
you might try searching channel logs
<antoine89>
ok, thanks very much
<KotCzarny>
also, sid is already burned
<KotCzarny>
so you cant modify it
<KotCzarny>
although no one experimented in overwriting remaining 0s
<antoine89>
not exactly i think. because if you supply proper voltage, the efuses can be modified because the current will jump the burned gap of the fuses
<KotCzarny>
anyway, that's uncharted territory, feel free to report any success/failure
<antoine89>
sure. it will take a while though
<antoine89>
if anyone's interested i'll supply 2 boards and pay 200 usd in case of success
tuxillo has quit [Ping timeout: 246 seconds]
gaston_ has joined #linux-sunxi
yekka has quit [Quit: Leaving]
powerpan has joined #linux-sunxi
powerpan has quit [Remote host closed the connection]
ninolein has joined #linux-sunxi
msevo has quit [Quit: Leaving]
xqdzn has joined #linux-sunxi
antoine89 has quit [Ping timeout: 248 seconds]
selfbg has quit [Quit: selfbg]
tuxillo has joined #linux-sunxi
forkbomb has quit [Quit: In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.]
<KotCzarny>
did you leave 'early console' in the kernel?
<xqdzn>
idgi xD
<KotCzarny>
anyway, kernel didnt boot, for whatever reason
<KotCzarny>
:)
SopaXorzTaker has quit [Quit: Leaving]
<KotCzarny>
check if you have early console enabled in kernel
<xqdzn>
what i did: download linux from source, patch with 5.2.9 diff, patch with 5.2.8 diff, patch sun4i-gpadc-iio-add-H3-support.patch, config, then compile zImage
<KotCzarny>
you might also start with working .config from the other kernel
<xqdzn>
wait, lemme google about early console first
<xqdzn>
I just need to do the right patch to get thermal sensor working
<xqdzn>
i saw someone build ubuntu image and thermal sensor is working. I tried to build the dtb file, close enough but it seems like I have to make modification on the kernel as well.
<xqdzn>
that's why i want to rebuild kernel in the first place.
<KotCzarny>
i have thermal sensor + ths working on my boards since 4.16-rc1
<xqdzn>
H3 ?
<KotCzarny>
yes, and a20
<xqdzn>
what did you patched?
<KotCzarny>
already pasted you, that armbian thread patch
<xqdzn>
Hi anarsoul, thank you so much for joining! I read that yesterday, and still wondering why i can't see it on source yet (maybe mainline guy didn't approve it yet), then i tried to google up those filenames. That's why i ended up in armbian and ballena repo.
<anarsoul>
it hasn't landed yet
<anarsoul>
so you'll have to apply it to your tree
<xqdzn>
which one?
<xqdzn>
all of 18 series of diff ?
<anarsoul>
whole series
<anarsoul>
and you'll have to modify your dts since Yangtao didn't provide dts changes
<xqdzn>
dont worry about dts, i modified mine
<xqdzn>
that's when i know i should recompile my kernel because i think i already did best for dtb
<xqdzn>
because compiling in arm taking forevurrrr
<xqdzn>
and since thermal sensor is not working yet, I almost fry my board
<anarsoul>
don't enable dvfs without thermal
<xqdzn>
idt i did it yet
<xqdzn>
i barely get my sensor working xD
<xqdzn>
anarsoul I'm doing native builds << with distccd? or chroot one?
<anarsoul>
xqdzn: chroot on armv8 board
<xqdzn>
so, do you think something like prepare(){ # ALARM patches git apply ../0001-ARM-atags-add-support-for-Marvell-s-u-boot.patch } will be enough in PKGBUILD?
<anarsoul>
I don't remember pkgbuild syntax, try it?