ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | | Github: | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: ->
Myron has quit [Ping timeout: 260 seconds]
awb99_ has quit [Quit: Connection closed for inactivity]
flyback has quit [Quit: Leaving]
flyback has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
Guest66 has joined #armbian
<keesj> Hi
<keesj> During setup (Bullseye) on a NEO PLUS2 I am asked to create a user account and I have to enter a password. If my password contain a shell escape char (\) the script is telling me that the passwords do not match
<keesj> I am also a bit confused about the message that I need to reboot as soon as possible for the resize to happen but after a reboot the messages remains
<keesj> still ( Usage of /: 84% of 1.8G ) roughtly does match my sd card size (2g)
Myron has joined #armbian
archetech has quit [Quit: Leaving]
<[TheBug]> well first, maybe it makes sense not to make the initial password with an escape character in it and maybe just reset it again later...
<[TheBug]> and the systemd unit for resize will still exist after it has done resize
<[TheBug]> so maybe that is what you are seeing?
<keesj> I checked the code and it looks for a file in /var/run/resize2fs-reboot (and this file does exist) my guess is that the resize fails (my card is a bit small e.g. 2Gig)
<keesj> I am running out of space but all my other sd cards are dead :(
<keesj> (log of resize running )
Myron has quit [Ping timeout: 250 seconds]
Guest66 has quit [Ping timeout: 256 seconds]
Myron has joined #armbian
alekksander has joined #armbian
qwr has joined #armbian
<qwr> sharing some experiences with Odroid-N2+ (not asking for any help)
<qwr> background - installed armbian buster image and did sata install to SSD connected with VL817 SATA Adaptor 2109:0715
<qwr> then upgraded it to bullseye and installed mesa 21.2.0 from experimental
<qwr> and installed arm64 firefox and armhf chromium via multiarch to have widevine (local web broadcasts some programs with widewine encryption)
<qwr> it mostly worked (i started at end of august), but had 3 weird problems that i think solved now having some free time
<qwr> first the usb boot hanged up about half of times after kernel detected the sata drive
<qwr> turns out that UAS is culprit, disabling UAS with usb-storage.quirks=2109:0715:u made it now boot every time without problems
<qwr> second, about 2-3 minutes after boot the compositor froze (no matter with - used Xorg compton and wayland weston and wayfire (self compiled)
<qwr> turns out armbian has /etc/udev/rules.d/hdmi.rules with runs /usr/local/bin/hdmi-hotplug
<qwr> for some reason the hdmi-hotplug script stalls on my odroid installation and when systemd finally killed something went wrong and the compositors froze - diverting the hdmi.rules fixed it
<qwr> finally third issue was/is weirdest - when TV connected via HDMI was off and turned on, then sometimes the board shutdown
<qwr> found from auth log "auth.log.1:Dec 25 19:04:59 piix systemd-logind[1641]: Power key pressed."
<qwr> like wtf, i don't have any "power key" and why it gets invoked when TV is turned on?
<qwr> but set the *Key=ignore in /etc/systemd/logind.conf and it seems fine now, no idea what went wrong there
<qwr> the kernel even don't have CEC enabled (CONFIG_CEC_MESON_AO and CONFIG_CEC_MESON_G12A_AO are not set for some reason in the armbian kernels)
<qwr> but for now it seems to work fine, currently 5.15.8-meson64 and mesa/panfrost 21.2.1-2 (from
<qwr> as widewine upgraded to version needing patched widevine, i also took patched armhf libc6 package from
<qwr> s/patched widevine/patched glibc/
yunus has joined #armbian
<qwr> long rant, hope it didn't disturb you, the armbian is great (couldn't have the board working so well without armbian) and merry holidays for you :)
<IgorPec> merry holidays! it would be better to paste this experience to forum
<IgorPec> some of problems are known but since those boards are packed with bugs its impossible to address them
<IgorPec> vendor, on the other hand, lives in their own bubble ;)
<qwr> ok, i'll try to create forum account and put it there
<IgorPec> great!
<IgorPec> but if you want to fix problems ... git clone :)
<qwr> probably getting faster PC soon, might try then to build armbian by myself, which is probably needed to fix things in the source :)
yunus has quit [Remote host closed the connection]
hook has quit [Quit: ZNC 1.7.2+deb3 -]
willmore has quit [Remote host closed the connection]
hook has joined #armbian
<IgorPec> qwr we have quite sufisticated CI so kernels are rebuild at merge request
<IgorPec> and in case you want to tackle troubles, we can also provide some hw for development
lanefu has quit [Quit: WeeChat 3.2-dev]
lanefu has joined #armbian
BeachyHead has quit [Read error: Connection reset by peer]
BeachyHead has joined #armbian
<sunshavi> Merry Xmas guys
<IgorPec> likewise! thanks
<sunshavi> At this time. I am trying fo find virtual courses for the children on the summer. They are on vacation from the school here in the South Hemisphere
Toasty has joined #armbian
Redentor has joined #armbian
luca__ has joined #armbian
<luca__> .
luca__ has quit [Client Quit]
luca__ has joined #armbian
luca__ has quit [Client Quit]
Redentor has quit [Quit: Leaving]
BeachyHead has quit [Read error: Connection reset by peer]
BeachyHead has joined #armbian
<Armbian-Discord> <l​anefu> Lol nand-sata-install is in my phone's keyboard dictionary
<Armbian-Discord> <I​gorPec> rm -rf / too ?: )
Toasty has quit [Quit: Toasty]
<lanefu> Not net
<lanefu> Yet
<IgorPec> hehe
a__pi has quit [Remote host closed the connection]
<sinned6915> lo-
<sinned6915> i am trying to get my head around using an OrangePi with Octoprint
<sinned6915> specifically PSU control
<sinned6915> I am trying to understand what GPIO control is native with Armbian, specifically bullesye
<sinned6915> i am finding that there is not much standardization with gpio
<IgorPec> what standards do you expect?
archetech has joined #armbian
<sinned6915> when i serch i keep reading about different gpio libraries
<sinned6915> i am trying to figure out if python-periphery will work on armbian
<sinned6915> at least something that dinifitvely says yes or no
<Armbian-Discord> <T​onymac32> Sinned6915 I would say just give it a try. It looks to me like it simply opens the devices and manipulates them the way you could from the command line, so I see no reason it won't work
<sinned6915> i think i have confused myself into oblivion
<sinned6915> easier to get help here or on discord?
<sinned6915> i am trying to use an LED and manually turn it off and on
<[TheBug]> not sure what you are expecting but we are not gonna hand hold you through setting stuff up whether it be on Discord or irc, thats your job. We will do out best to help point you in the right directiojn though, and since its so easy to write another armbian SDcard you have very little to lose by testing installing it and seeing if it works how you want
<Armbian-Discord> <s​inned6915> i am not expecting handholding
<Armbian-Discord> <s​inned6915> i am trying to understand how to control simple gpio on-off on armbian
<Armbian-Discord> <s​inned6915> trying to to do baby step, like a simple LED blink scriot
<Armbian-Discord> <s​inned6915> trying to use python-periphery now
<[TheBug]> well I would suggest you do read the links IgorPec gave to you, and then more specifically go look at
<Armbian-Discord> <s​inned6915> somehow i mised that. i will read that nect
<Armbian-Discord> <s​inned6915> i am struggling to find reliable resource to translate pinnumbers to gpio. board is orangepi zero
<Armbian-Discord> <s​inned6915> i am reading this page-
<Armbian-Discord> <s​inned6915>
<Armbian-Discord> <s​inned6915> bit it makes no sense.
<Armbian-Discord> <s​inned6915> its the only explanaion i have found that explains the pin translation
<Armbian-Discord> <s​inned6915> when i connect an LED plus current resistor to board pins 5 & 6, which I believe are PA06/GPIO11 and GND the LED glows faintly and the board resets.
<Armbian-Discord> <s​inned6915> i expected the LED to be completely off
BeachyHead has quit [Read error: Connection reset by peer]
BeachyHead has joined #armbian
BeachyHead has quit [Read error: Connection reset by peer]
BeachyHead has joined #armbian
<Armbian-Discord> <T​onymac32> pin numbers to GPIO is everyone's issue getting into this stuff. So you need to know which pin is which on your specific board hardware wise, then see what Linux decided to call it
<Armbian-Discord> <T​onymac32> some vendors give you a decent reference, some don't
<Armbian-Discord> <T​onymac32> often the mainline and vendor kernels will assign them different numbers too
<Armbian-Discord> <T​onymac32> It really is a "choose your own adventure" story, but the issue is at least 2 choices are made long before the average user knows they're playing: The Vendor and the board
<Armbian-Discord> <s​inned6915> do i have to enable any of the gpio options in armbian-config? I am pretty sure I have the right pin number/assignemnt fromORangePi docs. I am confused why the pin that i believe is GPIO11 is floating and as soon as I to connect an L:ED to it the board resets.
<Armbian-Discord> <T​onymac32> no, the GPIO is there by default
<Armbian-Discord> <s​inned6915> am i wrong to to connect the LED+resistor to the board withough the script running?
<Armbian-Discord> <T​onymac32> no, that should be fine. make sure you're counting the pins right
<Armbian-Discord> <T​onymac32> also remember PA11 is the I2C, so perhaps you will need to do something special if you're wanting to use it like "just another GPIO"
lanefu has quit [Read error: Connection reset by peer]
<Armbian-Discord> <s​inned6915> ah, ok, i didnot think about the I2C
<Armbian-Discord> <s​inned6915> will PA06 work like generic gpio?
<Armbian-Discord> <T​onymac32> maybe, assuming it hasn't been enabled as PWM. That needs you to check in Linux for what is where in GPIO
<Armbian-Discord> <s​inned6915> ok, that may have been my problem. at least the board is not resetting when LED connected
<Armbian-Discord> <s​inned6915> i am trying to learn what the diffrerences in the hardware options are in armbian-config
<Armbian-Discord> <s​inned6915> should i even worry about them ?
<Armbian-Discord> <s​inned6915> when would someone enable any of these?
<Armbian-Discord> <T​onymac32> if you want to use a specific peripheral. So if you want SPI, I2C, one wire, etc
<Armbian-Discord> <T​onymac32> so that article you linked is almost 5 years old
<Armbian-Discord> <T​onymac32> and is using the Legacy Armbian kernel
<Armbian-Discord> <T​onymac32> so kernel 3.x
<Armbian-Discord> <s​inned6915> periferals: unless i am doing something specific, i can leave along?
<Armbian-Discord> <T​onymac32> I think so but it depends on what the dev/maintainer who brought that board in thought was good/bad to have enabled
<Armbian-Discord> <s​inned6915> article: yes, that is why i was questioning it and its recomenndatoins.
<Armbian-Discord> <T​onymac32> Yeah I'm not an Allwinner guy, but the port numbers are likely not the same in mainline, at least that has been my experience with the others
<Armbian-Discord> <s​inned6915> is there a morereliable source for info for those new to armbian?
<Armbian-Discord> <T​onymac32> well, anything using a mainline kernel will have the same GPIO numbers
<Armbian-Discord> <s​inned6915> the site are good, but i am findign them a more higher level that i am looking for
<Armbian-Discord> <T​onymac32> that's kernel dependant, not distro
<Armbian-Discord> <s​inned6915> one of the things i miss from wiringpi was the satus table
<Armbian-Discord> <s​inned6915> that way i could 'see' what i was doing
<Armbian-Discord> <s​inned6915> can i install wiringpi?
<Armbian-Discord> <T​onymac32>
<Armbian-Discord> <T​onymac32> super old, no idea
<Armbian-Discord> <T​onymac32>
<Armbian-Discord> <T​onymac32> that might be better
<Armbian-Discord> <s​inned6915> i should be able to apt install and apt remove it without any collataral damage?
<Armbian-Discord> <T​onymac32> or maybe worse, OPi docs are horrific sometimes
<Armbian-Discord> <T​onymac32> I honestly don't know, I've never used wiringpi
<Armbian-Discord> <s​inned6915> i am currently on bullseye. can you recommend a 'cutoff date' on stuff i find so as to not get my hopes up or be especially cautious?
<Armbian-Discord> <s​inned6915> i mean obviously if its for kernel 5.x i thnk i can be pretty confident
<Armbian-Discord> <I​gorPec>
<Armbian-Discord> <I​gorPec> this is all you need to know
<Armbian-Discord> <I​gorPec> you need to do something like this ?
<Armbian-Discord> <I​gorPec> stock armbian, nothing extra
<Armbian-Discord> <s​inned6915> i cam to the understanding that the /class method was outdated
<Armbian-Discord> <I​gorPec> this is the code to drive:
<Armbian-Discord> <I​gorPec> #!/bin/bash task(){ gp=$1 [[ ! -d /sys/class/gpio/gpio${gp} ]] && echo ${gp} > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio${gp}/direction echo "0" > /sys/class/gpio/gpio${gp}/value sleep 5 echo "1" > /sys/class/gpio/gpio${gp}/value } task "$1"
<Armbian-Discord> <I​gorPec> kernel 5.10.43-sunxi
<Armbian-Discord> <I​gorPec> but it works on all others too
<Armbian-Discord> <s​inned6915> i am trying your example. its complaining about syntax errors
<Armbian-Discord> <s​inned6915> pi@orangepizero:~/dpexampls$ python3 File "/home/pi/dpexampls/", line 2 task(){ ^ SyntaxError: invalid syntax pi@orangepizero:~/dpexampls$
<Armbian-Discord> <s​inned6915> i am really confused.
<[TheBug]> did you provide $1?
<Armbian-Discord> <I​gorPec> that's not pythong
<Armbian-Discord> <I​gorPec> its pure bash
<Armbian-Discord> <s​inned6915> uh, duh!
<[TheBug]> ohh that too
<Armbian-Discord> <s​inned6915> ok, so i am stuck with the gpiochip number now.
<Armbian-Discord> <s​inned6915> i need to read the docs a bit more.
awb99_ has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
lanefu has joined #armbian
alekksander has joined #armbian
Myron has quit [Ping timeout: 260 seconds]
<Armbian-Discord> <s​inned6915> i have some success but now i am confused about other things-
<Armbian-Discord> <s​inned6915> and did a "chmod a+rx" to it but I can only get it to work correctly as running it as root, not as the user
<Armbian-Discord> <T​onymac32> might need to chmod the gpio
<Armbian-Discord> <s​inned6915> now i am really confused