<Speedsaver>
Speedsaver/ArduiPi_OLED: sc6502 assigned issue #1 "Speedsaver/ArduiPi_OLED@37230d8 may be too aggressive" by peterbmckinley to peterbmckinley (https://github.com/Speedsaver/ArduiPi_OLED/issues/1)
peterm6881 has joined #Speedsaver
<peterm6881>
hey Xogium
<Xogium>
heya
<peterm6881>
dude released a new sd card image literally today
<peterm6881>
whats your plans for Sunday by the way?
<Xogium>
no idea
<Xogium>
its just another day, far as I'm concerned
<peterm6881>
Starting kernel ...
<peterm6881>
sigh....
<peterm6881>
yeah, thats how it was with me, yesterday
<Xogium>
I never understood why people celebrate getting older
<Xogium>
that doesn't make sense
<peterm6881>
I think its for other people to celebrate the fact they exist.
<Xogium>
happy birthday… really ? How's it happy, I'm getting closer to my death
<Xogium>
hah
<peterm6881>
so its nice for somebody to wish you happy birthday, they have noted that you exist
<Xogium>
but they have noted you exist the second they talked to you
<peterm6881>
but the flip side is the fuckers who deliberately sideline you, out of malice
<Xogium>
if by that you mean me, I'm sorry; my strange way of connecting to facebook doesn't signal birthdays
<peterm6881>
anyway, any idea why an image would fails at Starting kernel?
<peterm6881>
no i didnt mean you, at all, I knew you just forgot
<peterm6881>
i meant my family
<peterm6881>
i meant my old family
<Xogium>
hmm could be plenty of reasons… Misconfigured boot parameters, misconfigured environment for u-boot… hard to know precisely why
<Xogium>
it could also not hang there but they could have forgotten to setup the serial console in kernel, so effectively the last thing you would see is that message
<peterm6881>
lol you're a glass half empty person, definitely
<Xogium>
what do you mean ?
<peterm6881>
happy birthday… really ? How's it happy, I'm getting closer to my death
<Xogium>
oh that, yeah. I mean… it always weirded me out
<peterm6881>
I would say, "Yay, I survived another year"
<peterm6881>
go me
<Xogium>
things like getting gifts too… I still haven't gotten what's the deal
<peterm6881>
that Johan guy must literally not test his images, thats pretty fucking sloppy
<Speedsaver>
Title: All SD card images (at sd-card-images.johang.se)
<Xogium>
or he does but he's got the full kit with a lcd display and everything, and doesn't rely on uart
<peterm6881>
i really admire what he set out to do, the scope of its ambition
<peterm6881>
pity its fucking useless
<peterm6881>
yeah i get what you're saying
<Xogium>
I'm only shooting in the dark here, given I can't try and debug the images
<peterm6881>
yeah he doesnt keep his gh repo up to date with his website
<peterm6881>
so no point looking there
<peterm6881>
interesting....in lsusb it shows up as this:
<peterm6881>
Bus 006 Device 005: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode
<Xogium>
lol
<Xogium>
are there blinking leds on there ?
<Xogium>
if linux runs you should see a blinking led someplace, at least its common to do this, like the blinking blue led on odyssey, the so-called heartbeat led
<peterm6881>
Onda V972 is a tablet based on the Allwinner A31
<peterm6881>
no no led
<Xogium>
hmm
<Xogium>
and on the image you did manage to boot
<Xogium>
the buildroot made one, were there any ?
<peterm6881>
yeah the multi colour led lights green
<Xogium>
so it would appear to definitely be a hang, and not just a misconfigured serial port or some shit
<Xogium>
I stopped maintaining that one a long time ago, too hard to keep up with github and this other repo at the same time not to mention all the other repos we now have on github
<peterm6881>
I thought you set it up to mirror automatically
<Xogium>
nop, github doesn't let you do that now
<peterm6881>
we should definitely do that, as a backup to Github fucking up
<peterm6881>
hmm...
<peterm6881>
would it be possible for you to bring your repo up to date?
<peterm6881>
to bypass this problem for now, if you cant fix it
<Xogium>
I never had navit on my git
<Xogium>
navit is the problem, not our speedsaver repo
<peterm6881>
understood
<Xogium>
I'll have to ask the buildroot folks if they know what the hell changed yet again
<peterm6881>
ok
<peterm6881>
make it so
<peterm6881>
sigh, looks like the kernel has issues too
<peterm6881>
no ignore that last comment
<peterm6881>
I tried grabbing the new kernel into 2022.2, but the 404 error , unsurprisingly, got me
<Speedsaver>
Title: github - The unauthenticated git protocol on port 9418 is no longer supported - Stack Overflow (at stackoverflow.com)
<peterm6881>
since we have these errors
<peterm6881>
Improving Git protocol security on GitHub
<peterm6881>
We’re changing which keys are supported in SSH and removing unencrypted Git protocol. Only users connecting via SSH or git:// will be affected. If your Git remotes start with https://, nothing in this post will affect you
<Xogium>
no we have a 404 error, because it can't find the tarball to download
<Xogium>
besides, if it had been this, we would have hit this much, much sooner
<peterm6881>
they only disabled it permanently on March 15th, i havent run a build since then
<Xogium>
this has to do with the git protocol
<Xogium>
not https
<Xogium>
and buildroot downloads navit over https
<peterm6881>
ok
<peterm6881>
i thought it might be significant that the first error was
<peterm6881>
xzcat /home/peter/buildroot-2022.02-orange/dl/acl/acl-2.3.1.tar.xz | tar --strip-components=1 -C /home/peter/buildroot-2022.02-orange/output/speedsaver/build/host-acl-2.3.1 -xf -
<peterm6881>
fatal: remote error:
<peterm6881>
The unauthenticated git protocol on port 9418 is no longer supported.
<peterm6881>
The unauthenticated git protocol on port 9418 is no longer supported occurs because GitHub has stopped accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol from March 15, 2022.
<peterm6881>
The issue can be resolved by changing the protocol from Git to HTTPS in the .gitconfig. The same approach needs to be implemented in package.json, GitHub Actions too if you are fetching the repository using the git protocol.
<peterm6881>
ive noticed in /home/peter/Speedsaver/packages/navit the Config. is config BR2_PACKAGE_NAVIT
<Xogium>
github for not warning users in advance of this except possibly on their blog that surely noone follows
<Xogium>
and pierre for using the git protocol instead of the nice buildroot macro designed for it
<peterm6881>
the part i dont understand is github was supposedly in a brown out period for 3 months since January, we've definitely done a build sine then, I'm sure
<peterm6881>
since *
<peterm6881>
good work Xogium
<peterm6881>
building now, fresh directory
<peterm6881>
do we need to fix that elsewhere in the organisation?
<Xogium>
not currently since mangopi is useless
<peterm6881>
it would probably have been ok with an sd card
<peterm6881>
that makes no sense, because it used to be 100% but we dropped it when we went to a 2.5 Watt amplifer
<Xogium>
like, as in… I only unmute it. I never set its volume
<peterm6881>
because it blew up the 1 Watt speaker
<peterm6881>
you did before, ages ago
<peterm6881>
we set it to 100%
<peterm6881>
no question
<Xogium>
Revert "board/speedsaver: lower volume of DAC in amixer to 41%."
<Xogium>
Date: Wed Mar 2 11:39:05 2022 +0100
<peterm6881>
line out and DAC should be at maximum
<Xogium>
so either this is a default setting now, which I'd find very strange, or your micro sd card bugged yet again
<peterm6881>
i think its a default setting
<Xogium>
the last time something like this happened, you burned your micro sd again and this time it was back to full volume
<peterm6881>
all right, let me repeat that
<peterm6881>
wait
<Xogium>
see ? Exactly why I don't like micro sd
<Xogium>
especially unbranded micro sd
<peterm6881>
how do i format an sd card in linux?
<Xogium>
now, if its truly doing that again it could definitely have changed
<Xogium>
or, it was always at 41% and we just never even noticed it
<peterm6881>
I was pretty sure the default setting was something, and we had to bump it up to max, but it was a long time ago
<peterm6881>
something less
<peterm6881>
how do i format this sd card?
<Xogium>
if you use dd to write an image again, then you pretty much format it
<Xogium>
unless its getting to be worn out and failing to write, and you always end up with a bogus 41%
<peterm6881>
can you try it at your end
<peterm6881>
im burning it again
<Xogium>
but like I said, I never once touched the DAC volume before, except when you asked me to reduce it after we blew up the speaker, then few days later I reverted this very change
<peterm6881>
I think you'll find at the very start, we set it to 100%. Perhaps you could create a Buildroot image without any speedsaver stuff and see what the default is
<Xogium>
there's no default since there's no audio on this board out of the box
<peterm6881>
its 41
<Xogium>
this is every commit I've ever done for this file
<Xogium>
board/speedsaver: added amixer.service.
<Xogium>
Date: Mon Nov 23 16:20:37 2020 -0500
<Xogium>
board/speedsaver: added mono differential to amixer service.
<Xogium>
Date: Mon Nov 9 16:25:20 2020 -0500
<Xogium>
board/speedsaver: set line out volume to 100% in amixer.service.
<Xogium>
Date: Wed Feb 24 02:53:42 2021 -0500
<Xogium>
board/speedsaver: lower volume of DAC in amixer to 41%.
<Xogium>
Date: Mon Feb 7 23:00:25 2022 +0100
<Xogium>
Revert "board/speedsaver: lower volume of DAC in amixer to 41%."
<Xogium>
Date: Wed Mar 2 11:39:05 2022 +0100
<peterm6881>
its currently 41
<peterm6881>
so, like I said, can you set that to 100% and make that a release :)
<Xogium>
well then, it looks none of us ever noticed it was 41% before
<Xogium>
and it always has been
<peterm6881>
and lest not worry what happened. It's my fault for fucking with different audio amplifiers. The Mangopi-R3c was hoped to get us away from all that shit
<peterm6881>
let's *, even
<Xogium>
you've got the history of that service file I just pasted, so it looks like none of us ever bothered raising up the volume
<peterm6881>
yes the default was never 100%, we set it to that
<Xogium>
no we never did
<Xogium>
we did for line out. Not for DAC
<peterm6881>
can I ask a question, can you actually set it to 100%, or is that not possible? Becuase im very sick of this stupid argument about what got changed and when, and what the default is or isnt. Its currently 41%. It needs to be 100%. Is that deliverable?
<Xogium>
fine, I'll shut up
<peterm6881>
Because im getting the impression im asking for something that must be really really hard
<peterm6881>
Sorry its just got a bit ridiculous, thats all
<peterm6881>
when all I need is for it to be 100%. I promise we will never change it, ever again
<peterm6881>
I will match the amplifier to the speaker. We will never touch volume again
<peterm6881>
yes if you follow that link, it converts it to https, as I said
<peterm6881>
if it didnt, we wouldn't be having this discussion
<peterm6881>
since thats the crux of my position, thats it wrong
<Xogium>
ah yep they do, http turned into https here. Alright then… I'll fix it, but for the next release, when we got at least something more substencial to try
<peterm6881>
that it's wrong
<peterm6881>
sigh...
<Xogium>
like a kernel upgrade or something
<peterm6881>
as you wish
<Xogium>
I mean I could do it now, but then you would get a commit that is after 2022-4-15 release
<Xogium>
and you don't seem to care for that much
<peterm6881>
lol stop trying to wind me up you witch ;)
<peterm6881>
hehe
<Xogium>
I'm not trying to, only stating
<peterm6881>
im building, nothing is gonna stop me
<peterm6881>
how are you feeling now by the way, you seem to be very much your normal self
<Xogium>
meh, only going through the motion, pretty much
<peterm6881>
going through the motions, like a virologist