ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | Armbian 20.11 Tamandua released | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
cisco87 has quit [Remote host closed the connection]
<mangix> anyone know what the deal is with mvebu and not supporting higher speed SD cards?
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
cisco87 has joined #armbian
cisco87 has quit [Remote host closed the connection]
macc24 has joined #armbian
sunshavi has quit [Ping timeout: 268 seconds]
sunshavi has joined #armbian
sunshavi has quit [Read error: Connection reset by peer]
cstroie has joined #armbian
archetech has quit [Quit: Leaving]
cstroie has quit [Ping timeout: 246 seconds]
cstroie has joined #armbian
cstroie has quit [Ping timeout: 268 seconds]
caiortp has joined #armbian
cstroie has joined #armbian
cstroie has quit [Ping timeout: 246 seconds]
oida has quit [Ping timeout: 240 seconds]
oida has joined #armbian
prefixcactus has quit [Ping timeout: 240 seconds]
prefixcactus has joined #armbian
cstroie has joined #armbian
qCactus has joined #armbian
prefixcactus has quit [Ping timeout: 268 seconds]
cstroie has quit [Remote host closed the connection]
LRN has joined #armbian
<LRN> What's the default keyboard layout switching combo in Armbian?
<LRN> (when running only the terminal, no X11)
chewitt has quit [Read error: Connection reset by peer]
<binarym> LRN: you mean a special key combination to switch between different keyboard layout ?
<binarym> setxkbmap is supposed to change keyboard map at runtime
<f476> .13
lanefu has left #armbian ["beatdown mode for a few days"]
eltoozero has quit [Quit: ZNC 1.7.5 - https://znc.in]
eltoozero has joined #armbian
chewitt has joined #armbian
sunshavi has joined #armbian
eicloud has joined #armbian
<eicloud> is there any sbc which can do sr-iov i.e. create multiple virtual nics from a single nic?
<eicloud> alternatively an sbc with pcie slot, iirc there are a couple of those, but i'm not sure if there still needs to be hardware support from the sbc itself
<binarym> eicloud: what is your purpose
<binarym> cause multiple virtual nics from a single nic can't be easily achieved with
<binarym> 1/ VLANs
<binarym> 2/ address aliases on NIC
<binarym> it's not depending on hardware imho, pure software
<[TheBug]> I think you meant can?
<binarym> yeah, sorry :)
<binarym> eicloud: ip addr add 1.2.3.4 dev bla0 => add the address 1.2.3.4 to device bla0
<[TheBug]> but past that, there are only a few devices that will have working mini-pcie which you can convert, you the two that come quickest to mind are rk3399 (RockPi 4c, NanoPi M4v2, RockPro64) or ESPRESSOBin which also already has a 3 x 1Gbit topaz switch, so if you just want some networking switch or something, it may be able to do what you need out of box.
<[TheBug]> You would have to really give more information though if you want a more specific recommendation.
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
<binarym> damn ... i just looked up to "sr-iov" that eicloud mentionned ...
<binarym> and i still can't figure out his needs :)
<LRN> binarym, yes, i meant that
<LRN> um...i have no idea what setxkbmap is. And even if i knew, i would not have been able to use it, since my keyboard layout is not en_US
<[TheBug]> huh? it prompts you on first boot to choose your keymap.. so not even sure what your discussing per se, but unless you don't have a screen plugged in it will both prompt to change passwords as well as set keyboard map on first boot
<LRN> i can't even log in after rebooting, because keyboard layout sticks, and because my login only uses ascii
<LRN> yes
<[TheBug]> if your not paying attention and just hitting enter all the way through, thats on you
<LRN> on first boot it figured out from my timezone that i need extra keyboard layouts. I said "yes". It added an extra layout, and immediately switched to that layout, without ever telling me how to switch back.
<eicloud> sr-iov is not the same as some virtual address for a nic: https://en.wikipedia.org/wiki/Single-root_input/output_virtualization
<eicloud> it is usually used for virtualization and offers better separation between networks
<eicloud> or better isolation of virtual machines
<LRN> So right now i have 2 viable option that i was able to find: 1) use alt+KEYNUM to input needed ascii chars one by one to log in and change something. 2) re-flash Armbian on the sd-card, and re-do the whole installation again, this time not opting in for another layout
<LRN> s/option/options/
<ArmbianHelper> LRN meant to say: So right now i have 2 viable options that i was able to find: 1) use alt+KEYNUM to input needed ascii chars one by one to log in and change something. 2) re-flash Armbian on the sd-card, and re-do the whole installation again, this time not opting in for another layout
<LRN> if you don't have any useful advice, i'd just do one or the other, so it's no big deal. Still, it'd be nice to learn how to switch between keyboard layouts in the console.
<LRN> dixi
<LRN> h-m-m...or is it "dixit"? I forgot.
<[TheBug]> LRN: I am not understanding the issue there, it is working as it's supposed to, you should set it on first boot and you really shouldn't have to change it
<[TheBug]> if you need to, then maybe on first boot setup ssh and ssh into it
<[TheBug]> and then change it on command line as you need
<[TheBug]> or ssh in before it changes it
<[TheBug]> I dunno
<LRN> how do i change it on command line
prefixcactus has joined #armbian
<LRN> (as i need)
qCactus has quit [Ping timeout: 260 seconds]
<LRN> i.e. which keys do i need to press to change the layout.
<[TheBug]> keys?
<LRN> yes. Keyboard keys.
<[TheBug]> sounds like Google is your friend and you need to spend some time talking to them
<LRN> I did talk to Google about it. Google told me a lot of things, like Alt+Shift, or Ctrl+Winkey+Space, but none of them worked for me.
<[TheBug]> then you searched for somethign weird cause there are no "magic keys"
<[TheBug]> you would have to login and run a program
<[TheBug]> which someone in here already mentioned to you
<LRN> how do i log in and run a program, when my login is in ascii and all program names are in ascii, and my layout is not capable of producing ascii characters normally (other than the aforementioned alt+NUMBER)?
<[TheBug]> please re-read what I said about half a page up ^
<LRN> i see. Any other advice other than "use ssh"?
<[TheBug]> You want some magic that doesn't exist
<LRN> Thanks. That's what i needed to hear.
<LRN> I really thought that i had missed something basic there. Glad to know that i didn't.
<[TheBug]> I don't even understand the use case for what you describe, on first boot you set the keyboard layout you are going to us, you then shouldn't need to change it
<[TheBug]> use*
<[TheBug]> if you do then you have some abnormal use case
attah has joined #armbian
<LRN> i'm struggling to imagine a use-case where you use the terminal with a layout that is not en_US
<LRN> like, how do you "sudo" when you can't type "sudo" on your keyboard? Boggles the mind. That's why i thought that i'm missing something.
<[TheBug]> huh
<[TheBug]> I really don't understand your problem
<[TheBug]> the default layout is english
<[TheBug]> otherwise, when it prompts choose the one you need
<[TheBug]> not connecting where there is some problem?
<LRN> The default layout is en_US. I set up everything (login, password, root password) in ascii characters. Then Armbian helpfully offered me a different layout that matches my geolocation. I agreed, and now i can't type any ascii characters. I can't log in. I can't run commands.
<LRN> That is the problem.
<[TheBug]> so... don't do that
<[TheBug]> :)
<LRN> I agreed to a non-en_US layout on the assumption that it's going to be installed *in addition* to en_US. Because you can't use the terminal without en_US.
<LRN> Obviously, that wasn't the case.
<[TheBug]> key word... assumption
<Werner> Recently somebody reported a bug with the geo detection where I think AR was mislabeled as Argentina or something
<Werner> Probably
<[TheBug]> LRN btw per debain in general the proper way to fix it would be to use SSH
<[TheBug]> since..
<[TheBug]> The system’s keyboard configuration has no impact on the mappings used over SSH: SSH doesn’t transmit keystrokes, it transmits characters, there is no keyboard-style mapping involved.
<LRN> uh-huh
<[TheBug]> past that you will need to write a new image and choose correctly during setup
<[TheBug]> once logged in via SSH, you can run dpkg-reconfigure keyboard-configuration
LRN has left #armbian ["Leaving"]
prefixcactus has quit [Ping timeout: 240 seconds]
prefixcactus has joined #armbian
caiortp has quit [Ping timeout: 246 seconds]
<ArmbianTwitter> @ChiefGyk3D ((((Moshe)))): @kraftingg @thepine64 @Raspberry_Pi @system76 @brave stock htop for Armbian for @thepine64 Rock Pro 64 on @armbian https://tinyurl.com/yglzc8oh (30s ago)
<IgorPec> we need another adjustement of 1st login script?
<IgorPec> aha
<IgorPec> Detected timezone: America/Buenos_Aires
<IgorPec> Adding console keyboard layout: AR
<IgorPec> this is what i get from his ip
<IgorPec> but what should be correct?
<IgorPec> found the problem
Elpaulo has quit [Quit: Elpaulo]
Elpaulo has joined #armbian
<IgorPec> werner: i think final solution is to not deal with the keyboard
stipa has quit [Remote host closed the connection]
stipa has joined #armbian
loredin has quit [Quit: Boom bye bye]
<martinayotte> IgorPec: I've finally built OPi3-XFCE-Desktop, I got LightDM login, but as soon as I log, there HDMI output goes blank and desktop never comes...
<martinayotte> I will try another desktop flavor ...
attah has quit [Remote host closed the connection]
sunshavi has quit [Ping timeout: 260 seconds]
loredin has joined #armbian
<IgorPec> martinayotte: that's strange
<IgorPec> did you enable 3D support?
loredin has quit [Ping timeout: 240 seconds]
eicloud has quit [Quit: Connection closed]
loredin has joined #armbian
marco44 has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
marco44 has joined #armbian
loredin has quit [Read error: Connection reset by peer]
loredin0 has joined #armbian
bzyx has quit [Quit: No Ping reply in 180 seconds.]
bzyx has joined #armbian
loredin0 has quit [Quit: Ping timeout (120 seconds)]
loredin has joined #armbian
loredin has quit [Quit: Ping timeout (120 seconds)]
loredin has joined #armbian
tparys has joined #armbian
<tparys> evening all
<IgorPec> hi
<tparys> MicroZed is booting, but after some manual steps outside of build system
<IgorPec> that was fast :)
<IgorPec> what left outside?
<tparys> Xilinx bootgen, and Zynq FSBL are both manual adjustments
<tparys> helps that I've done my own MicroZed builds in the past. just seems silly to do my own build system, ya know?
<tparys> it's also missing /boot/armbianEnv.txt, which I'm not sure where that gets populated
<IgorPec> maintainig build system is pain.
<IgorPec> armbianEnb.txt is created from https://github.com/armbian/build/tree/master/config/bootenv
<tparys> gracias
<tparys> https://github.com/tparys/build/ on branch microzed if you have any interest
<tparys> I'm sure there's lots I've missed so far
<IgorPec> you are welcome to push it to the main branch once you are happy with it
<tparys> suspect it'd fall under WIP or CSC?
<IgorPec> CSC
<tparys> I might also run sbc bench, just for fun
<tparys> just curious, if bootgen is a specific application for building boot file, should it go in uboot debian, or separate package?
<IgorPec> u-boot package is just fine
<tparys> unfortunately, the FSBL has FPGA configuration in it, so will have to rebuild on-board if someone loads their design :(
<tparys> or at least part of it, the Zynq is an interesting design
<IgorPec> indeed
<IgorPec> but this tool for manipulating bootloader, you have sources or binary only?
<IgorPec> this=
<tparys> it used to be closed source as of Vivado 2018.2, which is when I did last spin of this for myself, but now open source Apache
<IgorPec> ahaa
<tparys> and is why the second tool exists, because it was closed source x86 only, and no way to update it on the board
<tparys> but all things considered, Xilinx sources are in good state. Their "legacy" kernel is Linux 5.4
<tparys> and their development branches look like 5.12