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/Twitter feed: #armbian-rss | Logs: -> irc.armbian.com
califax has quit [Remote host closed the connection]
califax has joined #armbian
mdx0 has joined #armbian
<mdx0>
hi I'm having issues with odroidn2+ and petiboot
<mdx0>
I packed the latest petiboot.img on a sdcard rename it and turned the switch from the n2+ to SPI and powered on...I came into petiboot menu but wont update automaticly.
<mdx0>
2 years ago I update petiboot with cable
<mdx0>
but that isnt available at the moment
schwar3kat has left #armbian [Offline]
<mdx0>
and had removed the emmc
<mdx0>
I trying recovery mode
<cornelius>
last I checked it needed a boot partition for petitboot to pull the *.img and run the update.
norwich_ has joined #armbian
norwich has quit [Ping timeout: 272 seconds]
norwich_ is now known as norwich
chewitt_ has joined #armbian
chewitt has quit [Ping timeout: 246 seconds]
xoan0 has joined #armbian
xoan has quit [Ping timeout: 255 seconds]
xoan0 is now known as xoan
<mdx0>
recovery was successful...trying to the latest updae...but how I can shutdown the system in petiboot menu?
<mdx0>
can I just pull the power cord or how i can halt the system?
alekksander has quit [Quit: Konversation terminated!]
pablocastellanos has quit [Read error: Connection reset by peer]
<mdx0>
cornelius, wasnt necessary
pablocastellanos has joined #armbian
<mdx0>
I formated fat32 and spiboot.img powered on and it updating...
<mdx0>
but how the hell I can shutdown petiboot menu? I pull the powercord just...
<cornelius>
Well that's good. Control alt delete? And pull the plug.
<cornelius>
Last time I updated mine I had a ext2 boot partition on the img.
<mdx0>
okay, thank you for chat
pablocastellanos has quit [Read error: Connection reset by peer]
<mdx0>
bye
mdx0 has quit [Quit: Leaving]
pablocastellanos has joined #armbian
Mangix has quit [Read error: Connection reset by peer]
<clever>
i can set the clock before i turn on the arm, but cant get cpufreq to change it at runtime
<lanefu>
on what device?
<lanefu>
using armbian?
<clever>
lanefu: rpi2, currently using custom firmware + nixos or debian, unrelated to armbian
<clever>
the registers for arm clock are the same across the entire pi0 to pi3 range
<clever>
first is the PLLB registers, to set the multiplier from 19.2mhz to something in the ghz range
<clever>
then there is the PLLB_ARM divider, to divide it back down
<clever>
the PLL has a range it works best in, so slower speeds are outside of that range, and need the divider
<Armbian-Discord>
<lanefu> ahh
<clever>
there is also a floor to the PLL, and if you request too low of a clock, it just bottoms out, and never locks, running at whatever that floor is
<clever>
i suspect the floor is temp and device dependant, so your freq becomes unpredictable
<clever>
behind the scenes, the PLL is just doing VCO / foo, and then phase-comparing that to the 19.2mhz crystal
alekksander has quit [Ping timeout: 256 seconds]
<clever>
and using a feedback look to adjust the VCO
<clever>
lanefu: but there is also a bit of a secret trick, the /foo divider, cant run above a certain freq, so if the PLL is too fast, it cant acculately count cycles to divide
<clever>
but, there is a dedicated /2 divider you can turn on, which can run faster
<clever>
so you can switch between OUT/foo == 19.2mhz and OUT/2/foo == 19.2mhz
<clever>
depending on what range OUT is in
<clever>
and the final arm freq, is then either (19.2mhz * foo)/bar, or (19.2mhz * 2 * foo)/bar, where you can choose which, and pick foo/bar
chewitt_ is now known as chewitt
<clever>
the root problem i have, is that even with the dts i linked above, cpufreq doesnt even activate
<clever>
so i have no freq's to pick from
<clever>
so there is no way to even attempt to change freq
califax has quit [Remote host closed the connection]
califax has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
stipa_ has joined #armbian
stipa has quit [Ping timeout: 272 seconds]
stipa_ is now known as stipa
lemonzest has quit [Quit: WeeChat 3.5]
<Armbian-Discord>
<lanefu> Honestly didnt you expect it to be a bad article
<Armbian-Discord>
<bret> They're not that impossible to get hold of, you just have to be quick!
<Armbian-Discord>
<bret> I've had a few in my basket after following rpilocator but then realised I'm being dumb. I can instead spend that ££ on other random boards that I can hope to arrive some point this year
<Armbian-Discord>
<bret> Need to track down why my Banana Pi M2 Zero only sees 1 wireless network at a time randomly, though it's an archive image and unsupported so I don't think I'll waste too much time on that, USB ethernet is working at least
chewitt has quit [Quit: Zzz..]
<stipa>
bret just buy a chip
<stipa>
lanefu: i expected it to be a change of my life
inspectorSands has joined #armbian
<Armbian-Discord>
<bret> Can I have salt and vinegar on that chip? Bit of ketchup too?
<inspectorSands>
Hello, I've noticed that the HDMI port on my Orange Pi Zero 2 doesn't seem to work with any of the Armbian releases. Is that expected?
<Armbian-Discord>
<lanefu> It's more fair to say that it's not unexpected
<stipa>
inspectorSands: maybe your monitor sux
<stipa>
it sends wrong EDID or smthn like that
<Armbian-Discord>
<lanefu> a lot of SBCs can be very picky about monitors that don't follow proper hang shake protocols.... and the H616 SoC on teh zero2 still isn't very mature from a kernel support perspective
<inspectorSands>
interesting, it has "Status is unknown/to be completed" in the HDMI Video column for H616
<inspectorSands>
I kind of expected this board to "just work"... oops
<stipa>
yeah, that's a trap
<stipa>
it's a hackboard
<stipa>
you could join the sunxi project and help out
<stipa>
it's a new chip as lanefu said, give it few years
alekksander has joined #armbian
<inspectorSands>
I haven't tried any of the images available from orangepi.org because the Armbian project seems more trustworthy but think I might cave in
<stipa>
try, yeah, maybe it works better, but you'll be stuck at that kernel
<stipa>
maybe come later when things get better if the image from OPI works better
<stipa>
i tried some for my board too but i haven't had luck with those, i didn't even have a boot as i remember
<stipa>
in the end it's mostly manufacturers fault that some boards don't work
<stipa>
since they never got the linux working on it
<stipa>
then, there are sunxi and armbian to fix that
<inspectorSands>
I just flashed this image from orangepi.org and HDMI works perfectly: Orangepizero2_2.2.0_ubuntu_bionic_desktop_linux4.9.170.7z
<stipa>
inspectorSands: do you have audio over HDMI?
<inspectorSands>
my display doesn't have a speaker so I don't know
<stipa>
try the TV
<nekomancer[m]>
the tv? at 2022?
<stipa>
nekomancer[m]: yeah, the TV
<inspectorSands>
I use 32" Sony scavenged from the rubbish dump as a second monitor for my standing desk :-)
<nekomancer[m]>
tv is something from 90th
<stipa>
nekomancer[m]: i like to watch movies on a TV
<stipa>
it hs inbuilt speakers too
<stipa>
and is big
<nekomancer[m]>
projector for big. laptop or tablet for individual. no niche for tv.
<nekomancer[m]>
* for big familia. laptop
<stipa>
projector is washed out
<stipa>
no contrast
<stipa>
and you need to have a wall for it
<nekomancer[m]>
I need a wall, and 3 more walls to protect from wind, and roof (from the rain or snow), and electricity, and a lot of things.
<inspectorSands>
hii
<stipa>
nekomancer[m]: i need just a TV
<stipa>
if it rains i use it for roof
<inspectorSands>
just tried connecting the OPZ2 to my TV, no picture at all
<stipa>
upsie
<inspectorSands>
closest I got was the TV saying "out of range" after turning on the Pi while everything was plugged in (no signs of life whatsoever at this point) then changing to another HDMI port and back to the original
<inspectorSands>
so why does HDMI work on the orangepi.org Bionic image work but not on Armbian? Is it differences in the kernel as opposed to userland?
<inspectorSands>
(dammit, I'm too used to being able to edit my crappy writing in Slack...)
<stipa>
manyn reasons, upping in kernel usually requires intervention
<stipa>
and code change in some places
<stipa>
with new krenel come new features and stuff
<inspectorSands>
oldest kernel I tried was from this image Armbian_22.05.3_Orangepizero2_bullseye_legacy_4.9.255.img.xz
<stipa>
what's your budget to get that board going?
<inspectorSands>
time or $$$?
<stipa>
if you're a coder you can contribute time, sure
<inspectorSands>
I'd be happy to sink a few hours into it, for the sake of learning if nothing else
<inspectorSands>
quite laughably I've been told I have enough knowledge of Linux to get an SRE job at FAANG, but I feel absolutely clueless about how the kernel handles displays/HDMI
<stipa>
yeah, it's mostly hacking
<stipa>
low level
<stipa>
bodging badly fucked up silicon together
<nekomancer[m]>
<inspectorSands> "(dammit, I'm too used to being..." <- matrix support edition
aasami_ has quit [Quit: Lost terminal]
alekksander has quit [Quit: Konversation terminated!]
<inspectorSands>
it doesn't work with my crappy old DVI monitor and a micro HDMI to DVI cable, though
<nekomancer[m]>
look for fresher hdmi device on jukyards
xoan4 has joined #armbian
xoan has quit [Ping timeout: 256 seconds]
xoan4 is now known as xoan
xoan has quit [Remote host closed the connection]
xoan has joined #armbian
xoan8 has joined #armbian
xoan has quit [Ping timeout: 246 seconds]
xoan8 is now known as xoan
<Armbian-Discord>
<lanefu> #SRELife
Malditron has joined #armbian
<steev>
inspectorSands: most people don't know how the kernel handles displays/HDMI, and HDMI is a pita in the first place, since monitor manufacturers aren't against lying in their EDID