Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Forums Feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
<Guest36921> lanefu, seems works, previusly at this time he already stops.
<Guest36921> that parameter EXTRAWIFI=no seme solved the probem... there is a list oo those usefull parameters?
<Guest36921> i will like to strip down the size of kernel to speed up boot time :-)
<lanefu> i've heard good things about docs.armbian.com
<Guest36921> thanks.
<lanefu> glad to help
<Guest36921> armbian is a deep sea... need time to explore all :-)
archetech_ has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 260 seconds]
ChriChri_ is now known as ChriChri
martinl has joined #armbian
martinl has quit [Ping timeout: 260 seconds]
archetech_ has quit [Quit: Konversation terminated!]
archetech has joined #armbian
<Guest36921> lanefu, i discovered that EXTRAWIFI=no make not usable the internal wireless chip of nanopiduo. that with my actual version of kernel works perfectly.
<buZz> yay perfection
<buZz> :)
<Guest36921> it seems im play with atoo short blanket: i pull to cover feet and belly is naked, i pull to cover head, and arms are naked. time to give up and go to sleep.
Guest36921 has quit [Quit: Leaving]
_whitelogger has joined #armbian
xecuter has quit [Ping timeout: 272 seconds]
xecuter has joined #armbian
redentor has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
pinkieval has quit [Ping timeout: 256 seconds]
sunshavi has quit [Remote host closed the connection]
pinkieval has joined #armbian
sunshavi has joined #armbian
sunshavi has quit [Read error: Connection reset by peer]
archetech has quit [Quit: Leaving]
archetech has joined #armbian
sunshavi has joined #armbian
archetech has quit [Quit: Leaving]
<ArmbianTwitter> @Chainsman (💩💩Chainsman💩💩): @A13_technology @armbian Can you talk to it using Hayes AT commands like other mobile modems? (6s ago)
martinl has joined #armbian
martinl has quit [Ping timeout: 240 seconds]
archetech has joined #armbian
RzR has quit [Ping timeout: 260 seconds]
RzR has joined #armbian
martinl has joined #armbian
martinl has quit [Ping timeout: 256 seconds]
martinl has joined #armbian
martinl has quit [Ping timeout: 240 seconds]
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #armbian
thefinn93 has joined #armbian
martinl has joined #armbian
sassinak-work has quit [Ping timeout: 260 seconds]
sassinak-work has joined #armbian
sunshavi has quit [Ping timeout: 260 seconds]
sunshavi has joined #armbian
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #armbian
Strykar has quit [Quit: /quit]
Strykar has joined #armbian
ScrumpyJack has quit [Quit: Eat more sushi]
msev- has quit [Quit: Leaving]
<DaRock> hey guys
<DaRock> I'm hoping someone can provide an answer on this, I've tried a few places with no response
<DaRock> I need to find out what the "part uuid" command would do in uboot boot.scr?
<DaRock> I can't find anything anywhere
rneese has joined #armbian
sassinak-work has quit [Ping timeout: 240 seconds]
sassinak-work has joined #armbian
<ArmbianTwitter> @armbian (armbian): Updated kernel and images for Odroid XU4 / HC1 / HC2 / MC1. Stable kernel 4.14.195 + 5.4.61 and test 5.8.5. #wireguard #docker #debian #ubuntu #aufs #minimal #iot #infosec https://t.co/WlVrobbBZQ https://t.co/BAIpE4EkLJ (8s ago)
<ArmbianTwitter> @guidol70 (Guido Lehwalder): #stockfish v12 with neural network (#NNUE) chess engine on #aarch64 #64bit #armbian https://t.co/zrELacayTN https://t.co/Ax3L8DOtAX (7s ago)
rneese has quit [Quit: Leaving]
cart has joined #armbian
<ArmbianTwitter> @armbian (armbian): RT @guidol70: #stockfish v12 with neural network (#NNUE) chess engine on #aarch64 #64bit #armbian https://t.co/zrELacayTN https://t.co/Ax3L… (2s ago)
<IgorPec> darock: par uuid is ID of your drive / partition. its unique
<DaRock> +IgorPec: no its an actuall command in uboot
<DaRock> I found it in a boot.scr file: part uuid ${devtype} ${devnum}:2 uuid
<DaRock> but apart from other lines like that in forum posts etc that seem to be removed due to lack explanation of its operation, I can find bugger all on what it actually does and how it works
<DaRock> what I _want_ to do is tweak this script to boot archlinux and run its root from a usb hdd rather than the forced continued use of the sd card, but I need to understand what is happening to do that, and how important this command actually is
<DaRock> I get the PARTUUID - I've used it before
<DaRock> from the little I could find the "part" command is that there are other verbs that can be used as well, like "part list"; but no other explanations although there is sample output of that particular use
<IgorPec> i don't know if uboot can read that. but probably it does
<DaRock> I tried trawling the source code, but that was impossible task to narrow down
<IgorPec> yeah, u-boot is a mess
<DaRock> its not reading it - its an actual command
<IgorPec> part to do what ?
<IgorPec> we don't use it IIRC
<DaRock> EXACTLY!!! :-)
<DaRock> actually I found lots of uses of it in armbian as well :-)
<DaRock> always in the boot.scr though
<DaRock> well boot.{cmd,txt,scr}
<IgorPec> aha, I see
<IgorPec> it reads partition id from this and that device
<IgorPec> we obviously read from which UUID u-boot was started
<DaRock> and then what? What is the usage of the command?
<IgorPec> i don't recall why we need tht
<IgorPec> perhaps to know where to store u-boot environment
<DaRock> on arch the next command sets up bootargs with root=PARTUID=${UUID}
<DaRock> on arch the next command sets up bootargs with root=PARTUID=${uuid}
<IgorPec> i am not familiar with arch
<DaRock> I know, but thats still linux bootargs
<IgorPec> we use this differently
<IgorPec> we don't rely on u-boot to tell us where rootfs is
<DaRock> so I'm guessing the last argument uuid stores the found uuid for the partition in that variable?
<IgorPec> we store that elsewhere
<DaRock> I'd have thought so too
<IgorPec> yes, thats't the partition where u-boot was booted from
<DaRock> which is what is driving me absolutely nuts trying to figure out what is going on here
<IgorPec> while we are not tied to that
<IgorPec> our solution is more universal and bullet proof.
<DaRock> isn't there a way to detect a rootfs through checking devices?
<IgorPec> we boot devices sometimes from old legacy u-boot's. you can't trust them
<IgorPec> from linux?
<DaRock> uboot
<IgorPec> from u-boot probably only with recent versions. not sure
<DaRock> in the autoboot sequences I've setup I usually have it loop through devices/types
<IgorPec> yeah but you don't know which partition contains boot fs
<DaRock> I'e never used boot.scr before though
<IgorPec> i mean you can code something to detect that
<DaRock> usually use common sense - I use usb a lot so thats first, then sata if available, then mmc last, etc
<DaRock> I use env variables to hold the lists in
<DaRock> incidentally, the next line is this:
<IgorPec> if you deal with one hardware, things are easy ... when you have more, things start to get complicated
<DaRock> setenv bootargs console=ttyS1,115200 console=tty0 root=PARTUUID=${uuid} rw rootwait smsc95xx.macaddr="${usbethaddr}"
<DaRock> true
<DaRock> I've got rpis and a marvell espressobin only so far
<IgorPec> worse :)
<DaRock> but with the variables I figure user can set what they want for ordering - similar to typical bios
<IgorPec> are among the worse. there are worse then this.
<IgorPec> yes, but those scripts are not actually on a user level
<IgorPec> its still a bit too low
<DaRock> I use uenv myself
<DaRock> not boot.scr
<DaRock> yeah
<IgorPec> from linux?
<IgorPec> you can manipulate setting from there too
<IgorPec> if its supported by u-boot
<DaRock> really? How?
<DaRock> I'm usually slogging over serial....
<IgorPec> well, you can save something into evnironment and reboot into new relaity
<DaRock> how does that work?
<IgorPec> print some variable etc. i think its print_env and save_env ... you need to install some tools to linux and that0s it
<IgorPec> but i was only playing with this some time ago, not really using it
<DaRock> I use both printenv and saveenv already, btu I had no idea that cold be done from linux
<IgorPec> i know its possible to access u-boot env from linux
<IgorPec> do some googling
<DaRock> think I might... :-)
<IgorPec> but this is again hardware specifis. not sure if all hw supports this oob
<IgorPec> some might support env stored only on this and that device etc
<DaRock> hmmm... interesting. I can see how it isn't for all users - getting an unbootable device might be problematic for some :-)
<DaRock> so is there any way to find docs or info on obscure commands? any tricks?
<IgorPec> not sure about the docs. we have none and what you can find with google or by peeking into the code
<DaRock> damn...
<IgorPec> most of such software is ... looking into the sources
<DaRock> actually, if its not good practice to rely on uboot to provide rootfs info, then what can be used?
<DaRock> try "grep -R part doc/" in uboot sources :-D
<IgorPec> yeah, you wish :)
<DaRock> apparently LABEL isn't necessarily a working solution
<IgorPec> i can't tell for sure.
<IgorPec> but in case this breaks down in u-boot, we will not notice ;)
<IgorPec> on the other hand, user must change u-boot manually
<IgorPec> he is not using UUID
<DaRock> looks like I'm gonna keep tearing hair out until I reach an acceptable solution...
<IgorPec> and also the problem there is bad script
<DaRock> if test "${devtype}" = "mmc"; then part uuid mmc ${devnum}:1 partuuid; fi
<IgorPec> devnum is variable passed by uboot
<DaRock> uh huh
<DaRock> "then part uuid ..."
<IgorPec> aha, you mean first partition?
<DaRock> which gets removed and lost because I don't think anyone really gets how it works or what it does
<IgorPec> that's hard coded, obviously
<DaRock> no I mean it uses the "part uuid" command to fill the partuuid variable
<IgorPec> boot.scr is not exactly user configurable ... uEnv.txt (armbianEnv.txt) is
<DaRock> no - thats exactly the point
<IgorPec> well, if you will start to look into our boot scripts ... there will certainly be some anomalies
<DaRock> although boot.txt says at the top: "# After modifying, run ./mkscr"
<DaRock> but thats what I'm dealing with
<DaRock> is there a different set of command references?
<IgorPec> for boot scripting?
<DaRock> yeah
<IgorPec> there is um ...
<IgorPec> yeas, wait
<DaRock> see if I fiddle with uenv then that is just going to be overidden by the devs at archlinux, so that is of no use unless I resolve the boot.scr
<IgorPec> i can't find ref now, but its some kind of script language
<IgorPec> from somewhere
<DaRock> it looks basically the same as uenv, except uenv runs variable contents instead
<IgorPec> sorry, i know nothing about archlinux philosophjy
<DaRock> and this obscure "part" command
<DaRock> neither do I - thats the problem :-)
<IgorPec> why using it then?
<DaRock> what other choice do I have?
<IgorPec> armbian ?:)
<DaRock> they don't distribute a generic only platform specific, and then lock you in to whatever they want to do - jst like most others out there
<IgorPec> because that is not possible
<IgorPec> arm is way way too diverse
<DaRock> I dunno about armbian, and I've jst chased a goose down alpinelinux way (which I would have preferred) only to find that they don't flip the right switches for the packages I need
<IgorPec> whhen no linux is good, you create your own.
<DaRock> I find that hard to believe given with aarch64 now and uefi boot
<IgorPec> count devices that supports uefi
<DaRock> if I had the resources and time to do that then I would have probably been able to fix the issues with alpine
<DaRock> I already run archlinux on x86_64 so far, so I figured I might as well stick to what I know for the time being after all that messing around
<DaRock> but of course everything is painful isn't it? :-)
<IgorPec> but userland is pretty generic on all
<IgorPec> we use debian userland just for the sake of normal people
<IgorPec> and because maintaining is expensive
<DaRock> in theory - and alpine offers this - one can boot a generic kernel and install a more specific one to optimise the specific hardware
<IgorPec> we have specific kernel for each kernel family and we don't provide generic. yet. arm only
<IgorPec> optimised experience only
<DaRock> arm64 though?
<IgorPec> arm64 and arm32, both
<DaRock> I think with the migration to arm64 that wil change over time
<IgorPec> in the mainstream, yes
<IgorPec> that is already very different than the rest
<DaRock> arm32 was a bit of a hodgepodge, but arm64 seems to have reined in the wild west feel of arm
<IgorPec> no, i don't think there is any difference but marketing
<IgorPec> for IOT 32bit is plenty
<DaRock> yes but arm64 is aimed for the pc users, so need better standardisation
<IgorPec> but sadly there is just one overpriced workstation and they just killed marvel arm64 server line
<DaRock> I noticed more distros offering a generic option once arm64 came round and uefi was on the table
<IgorPec> it become cheap enough
<DaRock> when did the server get killed?
<IgorPec> maintaining armbian is 10x more expensive then let's say manjaro
<DaRock> I'll bet
<IgorPec> they onyl provide arm64 and build what gets to mainline
<IgorPec> i just read the news about a week ago
<IgorPec> didn't really checked if its real or fake but possible
<DaRock> figured - I hadn't heard yet
<IgorPec> but on the other hand, there are big business using arm64 ... which on the other hand means little
<DaRock> I think there are a few still banging around - I'm pretty sure AMD wouldn't give up easily on their investment yet
<IgorPec> since arm = custom design
<IgorPec> and if you want that, and if you have enough money to afford (Amazon, Apple) this is what you want to do
<IgorPec> to kill intel/amd dependancy
<DaRock> I reckon arm64 changes that quite a bit as opposed to the arm32 line and multiple command sets
<IgorPec> yeah, sure there are changes. aynway, you can't run one kernel on both and support will eventually fade out
<DaRock> only one set of command and ftbs help with the peripherals
<DaRock> fun and games :-)
<IgorPec> yeah, defenetly not boring
<DaRock> I think I'm gonna call it a day - I'll have to go hunting for that boot scripting reference and try tackle this thing tomorrow
<DaRock> thx for the guidance +IgorPec
<IgorPec> ok, cu
macc24 has quit [Quit: ZNC 1.7.5 - https://znc.in]
drobo_00 has joined #armbian
sassinak-work has quit [Ping timeout: 240 seconds]
sassinak-work has joined #armbian
drobo_01 has joined #armbian
drobo_00 has quit [Ping timeout: 264 seconds]
drobo_01 is now known as drobo_00
drobo_00 has quit [Quit: drobo_00]
DaRock has quit [Ping timeout: 256 seconds]
willmore has quit [Ping timeout: 256 seconds]
macc24 has joined #armbian
willmore has joined #armbian
redentor has quit [Quit: Leaving]
martinl has quit [Ping timeout: 260 seconds]
archetech has quit [Quit: Leaving]
martinl has joined #armbian
phipli has joined #armbian
phipli_ has quit [Ping timeout: 256 seconds]
archetech has joined #armbian
archetech has quit [Client Quit]
archetech has joined #armbian
Mony_ has joined #armbian
Mony has quit [Ping timeout: 265 seconds]
RzR has joined #armbian
RzR has quit [Changing host]
Mony_ has quit [Ping timeout: 240 seconds]
Mony has joined #armbian
<ArmbianTwitter> @ComputingNl7 (NL7 Computing): The new video is already on the way ;) https://t.co/KuyCY10XPn #Linux #LinuxTips #Ubuntu #Armbian #orangepipc #technology #electric #electronics #Computing #computers #MachineLearning #HowTo #tutorial #aliexpress #Gearbest https://t.co/oUBDQnhSpB (21s ago)
martinl has quit [Ping timeout: 258 seconds]
Ntemis has joined #armbian
archetech has quit [Read error: Connection reset by peer]
Ntemis has quit [Read error: Connection reset by peer]
archetech has joined #armbian
archetech has quit [Ping timeout: 258 seconds]
archetech has joined #armbian
cyberbanjo has joined #armbian
cyberbanjo has left #armbian ["The Lounge - https://thelounge.chat"]
martinl has joined #armbian
martinl has quit [Ping timeout: 258 seconds]
DaRock has joined #armbian
archetech has quit [Ping timeout: 258 seconds]