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
mangix has quit [Remote host closed the connection]
mangix has joined #armbian
johnnynitwits has joined #armbian
legogris1 has joined #armbian
legogris1 is now known as threenp
ikmaak has quit [Ping timeout: 246 seconds]
threenp has quit [Quit: authenticating]
threenp has joined #armbian
threenodeproblem has joined #armbian
ikmaak has joined #armbian
chewitt has joined #armbian
threenp has quit [Quit: Bridge terminating on SIGTERM]
johnnynitwits has quit [Quit: Bridge terminating on SIGTERM]
johnnynitwits has joined #armbian
threenp has joined #armbian
threenp has quit [Client Quit]
johnnynitwits has quit [Client Quit]
threenp has joined #armbian
johnnynitwits has joined #armbian
threenodeproblem has left #armbian [#armbian]
threenodeproblem has joined #armbian
<threenp>
Has anyone here been able got odoidhc4 working with cryptroot? Been doing dozens of rebuilds over the past week (from 4.x, current, dev, 5.11, with and without patches) and no matter what I try the eth0 just won't go up once unlocked when doing cryptroot. It gets DHCP fine in initramfs but the interface won't even go up with a static IP, nevermind dhcp, once booted into the full system.
<threenp>
Building without cryptroot also works
<threenp>
Wouldn't be as much of a problem if it weren't for that the USB interface is only USB 2.0 and has reported stability issues ;(
threenp has quit [Quit: Bridge terminating on SIGTERM]
johnnynitwits has quit [Quit: Bridge terminating on SIGTERM]
johnnynitwits has joined #armbian
threenp has joined #armbian
<stipa>
threenp: seems like you're from east
<threenp>
stipa [chat.freenode.net]: haha indeed! you as well? :)
<stipa>
not really, but today i am
<stipa>
:D
<stipa>
stick around
<stipa>
both europeans an US are sleeping now
<c0rnelius>
not all
<stipa>
ok, Aegentina is not sleeping
<stipa>
i saw that ODROID-HC4 is supported
<c0rnelius>
Anyone have any thoughts on how to remove un-allocated space from a shrunk partition using scripting?
<c0rnelius>
The shrinking part is simples... But the space left behind still remains. I needs to figure out how to trim this off.
<threenp>
<stipa "ok, Aegentina is not sleeping"> haha wow, other side!
<threenp>
oh yeah, and cryptroot also works fine on odroidc4, which is otherwise super similar :S
<threenp>
<c0rnelius "The shrinking part is simples..."> you want to shrink the partition?
<threenp>
> <@c0rnelius_chat.freenode.net:remerge.net> The shrinking part is simples... But the space left behind still remains. I needs to figure out how to trim this off.
<threenp>
* you want to shrink the partition? ext4?
<[TheBug]>
resize2fs?
<c0rnelius>
yes i can I shrink the partition. But what is left over is un-allocated space. So therefore the partition remains the same size, because the un-allocated space still remains.
<c0rnelius>
resize2fs -M
<c0rnelius>
leaves un-allocated space
<[TheBug]>
huh?
<[TheBug]>
sounds like you are doing it in reverse
<[TheBug]>
but
<c0rnelius>
how so?
<[TheBug]>
what I will say is the easiest way is to use gparted in x-windows since it automates all the tasks for you
<threenp>
Uhm, isn't that exactly the point? Your physical device has the space it has
<threenp>
i don't think it sounds like reverse. But the unallocated space is part of the physical device
<c0rnelius>
[TheBug]: exactly. I'm trying to resolve this through scripting.
<c0rnelius>
not manual labor
<[TheBug]>
you have a 32GB volume, you are using 5GB on it, you want to change the 32GB partition to a 10GB partition. Okay... so fsck the volume to make sure it is contigous, modify the partition size to be smaller
<[TheBug]>
resize2fs
<[TheBug]>
fsck.ext4 the finished volume
<c0rnelius>
that doesn't work
<c0rnelius>
tried it
<[TheBug]>
sure does
<threenp>
c0rnelius [chat.freenode.net]: What you refer to as "unallocated space" is exactly that. Unallocated. Why would you want to remove that?
<[TheBug]>
what you described is changing the size of the file system, not the partition
<c0rnelius>
if you have a scripting example please share
<threenp>
what is it you're trying to achieve here?
<c0rnelius>
threenp: I want to remove that space to trim the partition
<threenp>
but you said you already shrunk the partition..?
<[TheBug]>
so did you fdisk the volume, remove partion, recreate partiton of new size, save?
<[TheBug]>
what you described above was shrinking the filesystem but not the partition. If you shirnk the partition, then you can use resize2fs to resize t he filesystem to match the size of the partition
<c0rnelius>
[TheBug]: if I did all that wouldn't that kill the existing partition and the FS within?
<[TheBug]>
Make sure you sacrafice 3 goats.
<threenp>
assuming you're not using lvm or similar (which could make this easier for you, but adds another layer):
<threenp>
filesystem < partition < device
<threenp>
so if you srunk the filesystem and partition, all you have left is empty space by the drive. I mean you could overprovision through firmware depending on the drive, is that what you're referring to? That depends on manufacturer and doesn't sound like what you're really after here
<threenp>
and, well, ALWAYS make backups when operating on data you don't want to lose
<threenp>
ah, sounds like you only shrunk the filesystem, not the partition!
<[TheBug]>
c0rnelius: you have too linear a thought process of it, it doesn't work like that. Yes, you can lose data, why I mentioned you have to make sure you are using a reasonable amount less than what you plan to drop the size to and you need to fsck the partition before you proceed. Even under best case there is always 'some risk' that some of the data got allocated towards the end of the partition
<[TheBug]>
if you were extremly active in using the volume, but generally you should be fine.
<c0rnelius>
No no... I want to create an image. Say partition one is p1 and partition 2 is p2 and p2 has 8GBs of space. After all is said and done I want to now trim P2 to the minimal needed size (which is the rootfs).
<[TheBug]>
actually if you want the best understanding, load up xwindows, run gparter and use it but actually review the logs of each step, it will tell you every command it uses, you will see it does roughly the same.;
<c0rnelius>
So after running resize2fs -M is trims it down, but it leaves the un-allocated space there, hece its still 8GBs.
<[TheBug]>
s/gparter/gparted
<ArmbianHelper>
[TheBug] meant to say: actually if you want the best understanding, load up xwindows, run gparted and use it but actually review the logs of each step, it will tell you every command it uses, you will see it does roughly the same.;
<threenp>
yeah, so resize2fs resizes the filesystem, it doesnt touch the partition
<[TheBug]>
c0rnelius: if thats what you want, what you really want is LVM
<[TheBug]>
you don't want paritions
<threenp>
this ^
<[TheBug]>
partitions are not meant to be resized like that
<threenp>
well nothing wrong with it per se
<[TheBug]>
only way to effiecntly do that is with gparted cause it has to do a bunch of math on how to align things. So it's possibl it just isn'
<threenp>
in case it's a one-time thing and you don't expect to resize it as it grows
<[TheBug]>
isn't practical*
<c0rnelius>
Well I this can be manually using gparted for example
<[TheBug]>
this is why LVM exists
<[TheBug]>
read what I said, it has to do calculations and is not practical
<c0rnelius>
so I figured there must be a way to script this... which is why I was asking.
<[TheBug]>
yes ity can be done but what youa re wanting to do, you really want LVM
<[TheBug]>
you can dynamicly rezies your partitions
<[TheBug]>
resize*
<threenp>
anyway c0rnelius [chat.freenode.net] you can absolutely script fdisk, i think armbian scripts do it this way IIRC
<threenp>
but the advise you got was good, run a gui app with verbose logging that shows you the lower-level commands it runs and see what it does
<[TheBug]>
c0rnelius: um, read my earlier comment - run gparted, actually read what it does, it tells you in the logs step by step, replicate the process
<[TheBug]>
as long as you are okay calculationg the patition sizes, it can be done
<c0rnelius>
[TheBug]: I tried that already
<threenp>
and?
<c0rnelius>
It doesn't show any specific content I could see
<threenp>
it = what?
<[TheBug]>
it tells you the exact command it runs if you check down in log
<c0rnelius>
I know
<c0rnelius>
try it
<c0rnelius>
I saw nothing specific
<threenp>
but either way you have a working example in the redhat link above ^
<c0rnelius>
I wouldn't be asking if I saw it
<c0rnelius>
I thought maybe creating a stage3 script that calculates the p2 partition size and re-runs fdisk and does a rsync transfer and at the end creates the img... But? Thats like a ton of extra effort.
<c0rnelius>
Must be a way to remove the un-allocated space.
<[TheBug]>
c0rnelius: if you want to do what you are suggesting manually by hand, get it to how you want, fsck both volumes, enter fdisk, remove both partitions, recreate them the new sizes, run resiz2fs on each partition, fsck each partition. Thats pretty much it.
<[TheBug]>
yes you remove both partitions, recreate them the size you want them
<archetech>
use a bootable tool like gparted
<c0rnelius>
Trying to figure it out on a scripting level
<[TheBug]>
resize2fs each parition, fsck
<threenp>
if you really don't want LVM would prob be a lot easier to just determine the size and rebuild creating the image with a root partition with the intended size straight away
<archetech>
gparted=scripts already made and built in
<[TheBug]>
'man fdisk' ?
<threenp>
build once -> measure size -> rebuild with intended size
<c0rnelius>
threenp: yeah i think thats the only way
<threenp>
it's not, but it's prob the asiest ;)
<c0rnelius>
real dick punch :D
<threenp>
and, well, you could also create new partition -> rsync over
<[TheBug]>
or check out sfdisk....
<c0rnelius>
[TheBug]: I did
<c0rnelius>
thats why I'm asking for ideas
<c0rnelius>
which I appreciate very much. thanx
threenodeproblem has quit [Ping timeout: 264 seconds]
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
Guest66215 is now known as comrade
s_frit has quit [Remote host closed the connection]
Guest64086 has joined #armbian
bbt has joined #armbian
archetech has quit [Quit: Leaving]
mangix has quit [Remote host closed the connection]
mangix has joined #armbian
<mrjpaxton[m]>
I wish there was rsync for dd, so you could, I guess, dd your changes over to another drive.... That sounds like a terrible idea, never mind.
azend has joined #armbian
<[TheBug]>
um there is, it's called dd over ssh or nc
<[TheBug]>
but I guess your saying where you could do like an active update of some kind?
<[TheBug]>
I mean functionally if the disk image was small enough you could rsync the device
<[TheBug]>
but you would be better off just rsyncing the data on the filesystem level
<[TheBug]>
or otherwise using something like an lvm snapshot
<threenp>
you can replicate the partition table between devices of same geometry too: `sfdisk -d /dev/sda | sfdisk -f /dev/sdd`
<threenp>
you prob need to change fs uuids since youy don't want duplicates: `tune2fs -U random /dev/sdd` or `cryptsetup luksUUID /dev/sdd --uuid NEWUUID`
<threenp>
* you prob need to change fs uuids since you don't want duplicates: `tune2fs -U random /dev/sdd` or `cryptsetup luksUUID /dev/sdd --uuid NEWUUID`
<threenp>
* you prob need to change fs uuids since you don't want duplicates: `tune2fs -U random /dev/sdd2` or `cryptsetup luksUUID /dev/sdd2 --uuid NEWUUID`
stipa_ has joined #armbian
stipa has quit [Ping timeout: 268 seconds]
stipa_ is now known as stipa
azend has quit [Quit: No Ping reply in 180 seconds.]
<c0rnelius>
mrjpaxton[m]: That can be done. I actually have two scripts for it. One for sd over to sda and another from sd to mmc. They are both very specific in what they do, but could be modified easily depending on the use case.
Naka has joined #armbian
Nakaori has quit [Ping timeout: 256 seconds]
<HerculeP>
c0rnelius: IIRC I could use PiShrink even for my armbian backups, not 100% sure tho (it was years ago)
<c0rnelius>
alrighty.
<HerculeP>
lemme check, I have to move an odroidc2 armbian 32GB SD to a 8GB emmc anyhow ..
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #armbian
stipa_ has joined #armbian
<kprasadvnsi[m]>
My LCD driver works with BSP but failed to work on mainline. It turned out mipi DSI controller driver is completely different from bsp one
stipa has quit [Ping timeout: 268 seconds]
stipa_ is now known as stipa
<lanefu>
kprasadvnsi[m]: bummer
<kprasadvnsi[m]>
Yah, it suck
archetech has joined #armbian
BenG83 has joined #armbian
macc24_ has quit [Ping timeout: 272 seconds]
macc24 has joined #armbian
archetech has quit [Quit: Leaving]
Elpaulo has quit [Quit: Elpaulo]
sunshavi has quit [Ping timeout: 265 seconds]
archetech has joined #armbian
arti has quit [Quit: arti]
Algyz has quit [Read error: Connection reset by peer]
arti has joined #armbian
BenG83 has quit [Quit: Leaving]
sunshavi has joined #armbian
cstroie has joined #armbian
cstroie has quit [Remote host closed the connection]
BenG83 has joined #armbian
archetech has quit [Quit: Leaving]
archetech has joined #armbian
archetech has quit [Quit: Leaving]
archetech has joined #armbian
whoiswho has joined #armbian
<whoiswho>
Hi all, anyone here to answer some (probably very basic) questions about building the kernel? I've tried following the guide on the Armbian docs (among others sources) but I'm suspecting the resulting images are just using the default config
<whoiswho>
Is the config file in output/config directory the one used making the image? If so, it must ignore the settings I set (using the TUI configuration tool), for instance 1000 Hz timer etc.
<Werner>
Yes and no. Let me explain. If you use the build script and choose to modify the default kernel config a copy of this config will be put into the output folder. It is also used for the kernel in this run.
<Werner>
If you plan to use this custom config for future builds without additional adjustments you have to provide it to the build script via userpatches folder. Check docs for this: https://docs.armbian.com/Developer-Guide_User-Configurations/
rrman_ has joined #armbian
rrman has quit [Ping timeout: 272 seconds]
BenG83 has quit [Quit: Leaving]
<whoiswho>
Ok. Just to clarify, are you saying that the default config is put in the output/config folder or my modified version? Building using the Ubuntu distro from the Armbian build guide in a virtual environment.
<Werner>
The modified one of course :)
<whoiswho>
The issue I'm having is that it doesn't seem to apply any of my modifications -- again, all done via the configuration script -- so I'm assuming it's just using the default config
<Werner>
Add a custom version string to your custom kernel and compile it. Then check if it is there
<whoiswho>
Yes, that's what I would've assumed also! :-) But checking that config, it's just the default config
<Werner>
Um
<Werner>
So you say it exports the default config? you did save the config before exiting, yes?
<whoiswho>
Precisely, I've added a custom string (LOCALVERSION) and changed a few other parameters, for instance 1000 Hz timer, but the config in output/config does not contain any of it
<Werner>
Were the changes present in the compiled kernel image?
<whoiswho>
I saved it yes. I'm assuming the "Save" in the menu is just for exporting it for future runs though? It should apply whatever I've modified regardless of if I "Save" it in the menu?
<whoiswho>
Neither of the changes appear to be present in the compiled kernel.
<whoiswho>
To apply the modified kernel settings in the menu you should just exit via the "Exit" button or double-tap the Esc button right?
<Werner>
Saving in menuconfig is for the current run and exporting the modified config to output
<Werner>
Let me test kernel customization real quick
<whoiswho>
Ok, it seems that the config file gets exported to a folder under /cache/
<Werner>
The cache folder holds the kernel sources under which root folder the config is usually stored with the name .config. The build script takes it from there and puts a copy to output
<whoiswho>
(but not to output/config which one would've thought)
<whoiswho>
Alright, I see.. Yeah, then it doesn't make sense why the config in output is not changed
<Werner>
export of custom config works for me
<whoiswho>
The .config file in the cache dir should then have my settings? Let me check that
<whoiswho>
Nope, it's just the default settings.. So that's the issue I guess.
<whoiswho>
Hmm..
<whoiswho>
I chose to save/export the settings (via the menu) to the file .config_1000hz which it done properly.. it's in the cache folder along with the .config (with default settings)
<whoiswho>
I don't really know what to try and what could cause it to ignore my settings.. appreciate all the response though ;-)
<whoiswho>
Can you supply the config file via the compile.sh script btw?
<Werner>
compiled kernel also contains my changes. build script works as intended
<Werner>
Not sure why you are having issues
<whoiswho>
good to know, then it must be something on my side
<whoiswho>
Just a thought, if I were to overwrite the .config file that is currently in the cache dir (build/cache/sources/linux-mainline/linux-5.10.y) would the script recognise my settings then? Or is it rewritten every time the script is run?
<Werner>
I guess it will be overwritten by automatic checkout of the sources
<Werner>
To provide a custom config check the documentation link I mentioned earlier regarding user configuration
<whoiswho>
Alright, yep
<whoiswho>
Altering the configuration as outlined in "Providing build configuration" just changes the first part of the build where you choose if you want to build kernel only, board type etc., AND if you want to recompile the kernel
archetech has quit [Quit: Leaving]
<whoiswho>
.. but not which config should be used in kernel config?
<Werner>
Naming depends on board and selected branch. like linux-sunxi-current.config
<whoiswho>
yep, going to try to run it once to see if I can get the proper name..
<whoiswho>
It's for an Odroid N2+ and I want the current branch so I'd guess it would be linux-odroidn2-current.config
<Werner>
n2 is meson64 I think
<whoiswho>
yeah you're probably right.. it the board name that's "odroidn2"
<Werner>
Its not about the board name, its about the family the board belongs to ;)
<whoiswho>
yep
<whoiswho>
I'll try to put my config as "linux-meson64-current.config" in there as see if it recognises it (and skipping the KERNEL_CONFIGURE option to .compile.sh). Appreciate the help Werner.. I'll log out as the build usually take a couple of hours
<Werner>
Pay attention to the output of the script and make sure it mentions this " Adding user provided meson64 overrides"
<whoiswho>
(Still very weird that it doesn't seem to apply the settings I make in the TUI though, but as long as it works some way I'm good..)
<c0rnelius>
Last time I checked the n2/+ just share the same dtsi file and the dts is nothing but includes. Of course I could be wrong as I don't actually own the board.
grae has joined #armbian
<grae>
evening all
grae has quit [Ping timeout: 240 seconds]
archetech has joined #armbian
Guest64086 has quit [Remote host closed the connection]