Werner 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 | Type 'help' for help | Logs: -> irc.armbian.com
CrashTestDummy has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
standardrat has quit [Read error: Connection reset by peer]
standardrat has joined #armbian
califax- has joined #armbian
califax has quit [Ping timeout: 276 seconds]
califax- is now known as califax
Malditron has joined #armbian
Redent0r has joined #armbian
Redentor has quit [Ping timeout: 260 seconds]
Redentron has joined #armbian
Redent0r has quit [Ping timeout: 260 seconds]
CrashTestDummy2 has joined #armbian
<steev> i mostly idle, but i do chat in the debian-arm channel
CrashTestDummy has quit [Ping timeout: 245 seconds]
<c0rnelius> I had to bail when the guy in charge of uboot suggested we could install rockchip, amlogic and allwinner uboot, all on one partition and boot all boards using one massive kernel. I don't believe he was successful in this venture, but said he was making progress. Considering the flash points and the differences between them in some cases when it comes to sd vs mmc, I just didn't see it.
<c0rnelius> But more power to them.
Redentron has quit [Ping timeout: 260 seconds]
Redentor has joined #armbian
<c0rnelius> I got pointed to some video from 2019. So I was like you've been working on this stupid idea for 2 years? Why not just make things just work `right` instead of recreating the wheel? As grand as an idea that it is, its kind of pointless.
<c0rnelius> Of course just my opinion.
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 245 seconds]
Redentor has quit [Remote host closed the connection]
<Armbian-Discord> <X​en> That's going about it the wrong way IMHO. They should just get all the SBC vendors together and make a standard.
archetech has quit [Quit: Leaving]
<steev> another standard that they implement incorrectly and/or ignore
<steev> and c0rnelius that was me :P well, and vagrant
<steev> vagrant was the one making pinebook and pinebook-pro boot from the same sdcard
<Armbian-Discord> <X​en> better than no standard. Like the SATA standard, etc. Some devices end up being incompatible, but it's much better than not having a standard.
<steev> well there's uefi, and some devices use it, but even then... they fuck it up
<Armbian-Discord> <X​en> Sure. That's the case for all standards.
<steev> what i mean is, the standards exist already, but vendors ignore them anyway. and users continue to buy the hardware because cheap > standard following
<steev> which, as a poor person, i get
<Armbian-Discord> <X​en> There's no standard that I know for SBCs. Closest you get is ARM SystemReady.
<steev> SRIR would be... EBBR which... is UEFI
<c0rnelius> Unless they created some standard uboot, with current flash points as they are its just not going to work. And I thought that was you :)
<steev> it definitely requires trickery. i'd love to reach a point where an image could be synonymous with an iso. i get so tired of answer what image users should use
<c0rnelius> Plus I don't understand how UEFI would be able to know which dtb to use?
<steev> you could run a uefi app to figure it out
<c0rnelius> Yeah I've never looked into it honestly.
<c0rnelius> Interesting. But what if I'm headless and this fails?
<steev> then fix it?
<c0rnelius> I wouldn't need to too if the boot setup already knew what to look for, is what I'm saying. This seems like a good thought for arm in a gui type situation.
<c0rnelius> I believe Libre Computer played around with grub on the imgs they made. Had a nice little uboot logo and grub loaded, but the keyboard part of it didn't actually work. So it just created a delay in the boot process. Maybe they fixed that at some point I don't know, but the whole thing seemed like creating extra steps for no reason. That was of course a few years ago. I suppose things have gotten
<c0rnelius> better?
<steev> that still requires an image per machine
<c0rnelius> this is true
<steev> i mean, realistically, if vendors just threw an spi chip on most boards, the bootloader could *mostly* be ignored, but again, vendors fuck that up
<steev> spinor
<c0rnelius> Plus mainline doesn't play well with spi last time I checked.
<steev> who knows if it's broke again, i'm not at a device manufacturer anymore, i don't have to care really :D
<c0rnelius> Isn't most of that spinor vendor specific?
<c0rnelius> Also requires a fat partition for boot i thinks?
<steev> it's just a chip that you can write whatever you want in it, most vendors would do u-boot, and u-boot having distroboot enabled gives the extlinux stuff, or you can do grub with the efi
<steev> nope
<Armbian-Discord> <X​en> SPI NOR is pretty standard.
<steev> if it suddenly requires it, that's news to me, because we had it on the efikamx smartbook and mine is running behind me with 2 linux partitions, no vfat
<Armbian-Discord> <X​en> Some chips have vendor specific commands, but mostly read/write/erase is standard.
<c0rnelius> I thought fat was required for it to work correctly using vendor uboot on say, amlogic devices?
<steev> The Efika MX Smartbook (small laptop computer) was announced in August 2010.
<steev> 11 years later and vendors are still screwing up, imagine that :P
<Armbian-Discord> <X​en> Also EBBR seems like a spec. more than a standard. And it's way too complicated.
<steev> i do still have my efikappc here too, i should get it working again sometime
<c0rnelius> I think the only board I have with SPI is the N2+ and yeah it doesn't work with mainline uboot.
<c0rnelius> And if I'm right, the HC4 if you wanna use mainline uboot you need to actually erase the SPI bit, before you can even use mainline.
<c0rnelius> Its a big fucking mess
<steev> sounds like an amlogic issue, not an spinor/u-boot issue
<Armbian-Discord> <T​onymac32> yeah, their (Amlogic) bootloader is a fking dinosaur full of garbage and hacks
<c0rnelius> Probably is. I have no doubt.
<Armbian-Discord> <X​en> That's weird because SD is pretty much SPI.
<Armbian-Discord> <T​onymac32> thank you 2015.1
<Armbian-Discord> <T​onymac32> spi flash chips use a different access method entirely if you look past the bus itself
<Armbian-Discord> <X​en> How big is their mask ROM?
<Armbian-Discord> <X​en> I don't have the board myself and I'm reading their docs. and it seems pretty effing complicated. Lol.
<Armbian-Discord> <R​ichNeese> grumble
<Armbian-Discord> <T​onymac32> I don't have those ones either
<Armbian-Discord> <R​ichNeese> Tony your up late
<Armbian-Discord> <R​ichNeese> I just woke up fell asleep ay 8pm
<Armbian-Discord> <R​ichNeese> 4 jpur nap
<Armbian-Discord> <T​onymac32> lol
<Armbian-Discord> <R​ichNeese> so explain the issue in the m4 vs m4v2 ?
<Armbian-Discord> <R​ichNeese> what is the issue in the device tree
<c0rnelius> Yeah I wanna know too. Because I was interested in getting one but now everyone is saying its garbage.
<c0rnelius> Isn't the m4v2 clocked higher?
<Armbian-Discord> <R​ichNeese> 2g vs 4g ram
<Armbian-Discord> <R​ichNeese> and the direction on the emmc when plugged in should be the only major diff
<Armbian-Discord> <R​ichNeese> I knw the v2b the screwed things up
<Armbian-Discord> <R​ichNeese> ddr3 vs lpddr4
<Armbian-Discord> <R​ichNeese> and 2 buttons on the v2 power and reset
<Armbian-Discord> <R​ichNeese> M4B they went backwords
<Armbian-Discord> <R​ichNeese> swap 2 USB3 for 2 USB2 and drop ram by 2 gig
<Armbian-Discord> <R​ichNeese> I pulled the spec sheets
<Armbian-Discord> <R​ichNeese> M4B sucks
<Armbian-Discord> <R​ichNeese> m4v2 is on hold as they ran out of parts
<c0rnelius> Funny... COVID. Not only do we all know how we are going to die now, but it also screwed with manufacturing.
<c0rnelius> I wonder if Polio or Small poxs had the same impact back in the day?
<c0rnelius> At least everyone can thank the Spanish Flue for helping the better countries of the world to win WWI. COVID... Not so much.
Malditron has quit [Quit: Konversation terminated!]
<Armbian-Discord> <R​ichNeese> shower bbiab
<c0rnelius> Here is a good one no one talks about: Vitiligo
<c0rnelius> Guess what? No cure.
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
fizikz has quit [Remote host closed the connection]
Heisath has joined #armbian
stipa has quit [Quit: WeeChat 3.3-dev]
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 245 seconds]
attah has quit [Read error: Connection reset by peer]
attah has joined #armbian
califax has quit [Remote host closed the connection]
[TheBug] has quit [Quit: ZNC - http://znc.sourceforge.net]
CrashTestDummy has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
attah has quit [Read error: Connection reset by peer]
attah has joined #armbian
Proxysna has joined #armbian
archetyp has joined #armbian
Heisath has quit [Quit: Client closed]
standardrat has quit [Read error: Connection reset by peer]
standardrat has joined #armbian
archetyp has quit [Quit: Leaving]
bzyx has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
bzyx has joined #armbian
attah has quit [Read error: Connection reset by peer]
attah has joined #armbian
Fleck has quit [Quit: GOSUB w/o RETURN]
Fleck has joined #armbian
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 260 seconds]
pablocastellanos has quit [Ping timeout: 265 seconds]
lanefu-er is now known as lanefu
standardrat has quit [Remote host closed the connection]
standardrat has joined #armbian
archetech has joined #armbian
pablocastellanos has joined #armbian
archetech has quit [Quit: archetech]
[TheBug] has joined #armbian
[TheBug] has quit [Changing host]
[TheBug] has joined #armbian
archetech has joined #armbian
aandrew has joined #armbian
<aandrew> good morning, everyone - I'm trying to modify the dtb for a bpi m2 zero to disable otg and force host mode since hte attached usb hub isn't being detected (the hardware works on an rpi zero)
<aandrew> I can see the dtb files for all supported architectures in /usr/lib/linux-image-current-sunxi, and can use dtc to decompile, change dr_mode and recompile
<aandrew> but I don't think this file is actually used. All of the documentation I'm seeing so far talks about a /boot directory but the bpi m2 zero image has no separate /boot partition (like rpi), and the /boot *file* is very small and a binary image
<aandrew> I have tried for both focal and bullseye images for bpi m2 zero
<aandrew> pretty sure I'm missing something very basic here
<Armbian-Discord> <R​ichNeese> the dtb to decompile and reecompile on active builds is /boot/dtb
<Armbian-Discord> <R​ichNeese> as its already go everything compiled into it
<aandrew> both the focal and bullseye images create a single partition (ext2), no separate /boot partition like what I see with rpi images
<aandrew> I'm finding these images here: https://www.armbian.com/bananapi-m2-zero/
<Armbian-Discord> <R​ichNeese> ext4 not 2
<Armbian-Discord> <R​ichNeese> and thats default on most the imgs
<Armbian-Discord> <R​ichNeese> we dont do the /boot /root split anymore
<Armbian-Discord> <R​ichNeese> unless you install on emmc/nvme/sata
<Armbian-Discord> <R​ichNeese> and usb
<aandrew> ok, and is /usr/lib/linux-image-current-sunxi the correct place to edit the appropriate dtb file?
<aandrew> (it's the only place I can find dtb files in the image so I'm assuming yes)
<Armbian-Discord> <R​ichNeese> no
<Armbian-Discord> <R​ichNeese> as I said you have to get the dtb from /boot
<aandrew> hm
<Armbian-Discord> <R​ichNeese> and decompile it and recompile it
<aandrew> /boot is a file, not a directory
<Armbian-Discord> <R​ichNeese> with the changes
<Armbian-Discord> <R​ichNeese> dood look on /boot is a dir
<aandrew> -rw------- 1 andrew staff 36 4 Oct 10:41 boot
<Armbian-Discord> <R​ichNeese> /boot should have files in it
<aandrew> I"m not running on the bpi right now, I'm mounted on an x86 lnux box (since I can't get usb working yet I can't type or even ssh in)
<aandrew> /etc/fstab doesn't seem to indicate a loopback file or /boot either
<aandrew> *for
<Armbian-Discord> <R​ichNeese> your not understanding
<Armbian-Discord> <R​ichNeese> its not its a dir with files for booting
<Armbian-Discord> <R​ichNeese> its not a partition
<Armbian-Discord> <R​ichNeese> you burned the img to sd right
<aandrew> ok, how does this directory get created? the image I download creates a small (36 byte) file for /boot
<aandrew> yes I did
<Armbian-Discord> <R​ichNeese> then mounted it on a x86
<aandrew> I can erase that and create a /boot dir and put a dtb in there but this doesn't seem like something I should be doing on a fresh install that is otherwise booting
<Armbian-Discord> <R​ichNeese> no
<Armbian-Discord> <R​ichNeese> you meessed it up
<Armbian-Discord> <R​ichNeese> /boot has the kernel and other files in it
<aandrew> it's kind of hard to mess up... download .xz, use balenaetcher to select .xz and it decompresses and writes to sd just like a dozen other sd card installs I"ve done
<aandrew> I'll do it again, but this is the third time I'm trying it
<[TheBug]> huh
<[TheBug]> sure you write an image but the image has a file system
<aandrew> Armbian_21.08.1_Bananapim2zero_bullseye_current_5.10.60.img.xz - that's what I'm burning to the 16G SD card
<[TheBug]> mount the sdcard and go in /boot
<aandrew> I understand that
<[TheBug]> there are files, like bios config files located in here
<Armbian-Discord> <R​ichNeese> and there is a dtb dir
<[TheBug]> aka dtb file
<[TheBug]> etc
<aandrew> believe me I got it, I'm not new to linux or rpi or bbb or any of the others, but this is the first time I'm using armbian and bpi
<aandrew> when balenaetcher is done, I have a single ext4 filesystem on the sd card. I go there and there's a tiny (34 byte) file named "boot" in the root dir
<[TheBug]> cd /boot
<[TheBug]> not /root/boot
<aandrew> I know
<aandrew> I'm not in /root/boot
<[TheBug]> what you are saying is not lining up with what you then say you know
<[TheBug]> so if you know it, say it correctly
<aandrew> the root dir is the root of the filesystem
<[TheBug]> the dtb file will be in /boot on the sdcard
<aandrew> not /root
<[TheBug]> you will decompile the dtb to a dts
<[TheBug]> you will update the dts then recompile to dtb
<aandrew> $ cd /mnt/boot
<aandrew> cd: boot: not a directory
<aandrew> $ ls /mnt/boot
<aandrew> -rw------- 1 andrew staff 36 4 Oct 10:41 boot
<[TheBug]> whats the device name for your sdcard? mmcblk0? sda?
<[TheBug]> fdsik -l /dev/device
<aandrew> mmcblk0p0
<Armbian-Discord> <R​ichNeese> depends on how you mount it
<[TheBug]> fdsik -l /dev/mmcblk0
<Armbian-Discord> <R​ichNeese> if its in a sd socket its mmcblk
<aandrew> [TheBug]: it's ext4
<aandrew> it's mounted correctly, I see the entire armbian system there, all hte standard directories
<Armbian-Discord> <R​ichNeese> if in a usb to sd adapter its sd
<aandrew> not gonna flood, but standard stuff, like this:
<aandrew> $ ls -l
<aandrew> total 152
<aandrew> lrwxrwxrwx 1 andrew staff 0 21 Aug 08:54 bin -> usr/bin
<aandrew> -rw------- 1 andrew staff 36 4 Oct 10:41 boot
<aandrew> drwxr-xr-x 0 andrew staff 4096 26 Aug 04:28 dev
<aandrew> drwxr-xr-x 0 andrew staff 4096 26 Aug 04:29 etc
<aandrew> drwxr-xr-x 0 andrew staff 4096 10 Apr 16:15 home
<[TheBug]> I didn't ask you if it was mounted I asked the output of fdisk is there more than one partition?
<aandrew> there is a single partition
<Armbian-Discord> <I​gorPec> howdy
<aandrew> pulled this sd card into a mac too, same idea: ext4 (I have a fuse plugin to access ext2/3/4), one partition, boot is a file, not a directory
<Armbian-Discord> <I​gorPec> aha, unsupported board. we don't know if this build work
<[TheBug]> aandrew: I just downloaded the image and mounted it in a loop device
<[TheBug]> I CD to /boot and it looks like
<[TheBug]> root@orangepiplus2e:/storage/boot# ls
<[TheBug]> armbianEnv.txt armbian_first_run.txt.template boot.bmp boot.cmd boot.scr config-5.10.60-sunxi dtb dtb-5.10.60-sunxi initrd.img-5.10.60-sunxi overlay-user System.map-5.10.60-sunxi uInitrd uInitrd-5.10.60-sunxi vmlinuz-5.10.60-sunxi zImage
<aandrew> yeah it is unsupported, and it boots, just trying to modify the dtb to change the usb port from otg to host, not rocket science
<[TheBug]> so not sure whats going on there
<[TheBug]> seems just fine for me
<aandrew> [TheBug]: ok, so there is something very weird going on with my system
<[TheBug]> you should be able to mount the sdcard and fine the same in /boot
<Armbian-Discord> <I​gorPec> that is probably supported via overlays?
<Armbian-Discord> <I​gorPec> armbin-config
<aandrew> [TheBug]: that's the confirmation I needed to dig a little deeper elsewhere, definitely not an armbian issue
<Armbian-Discord> <I​gorPec> yeah. borked sd card lookslike
<[TheBug]> aandrew:
<[TheBug]> root@orangepiplus2e:/mnt2/temp# xz -d Armbian_21.08.1_Bananapim2zero_focal_current_5.10.60.img.xz
<[TheBug]> root@orangepiplus2e:/mnt2/temp# losetup /dev/loop0 Armbian_21.08.1_Bananapim2zero_focal_current_5.10.60.img
<[TheBug]> root@orangepiplus2e:/mnt2/temp# partprobe /dev/loop0
<[TheBug]> root@orangepiplus2e:/mnt2/temp# mount /dev/loop0p1 /storage
<aandrew> *nods* I was going to try a loopback mount next
<[TheBug]> so you can see the image before you write it
<[TheBug]> can even change it there
<[TheBug]> then losetup -d /dev/loop0 to destroy the loop device before you burn image
<aandrew> yep, thank you
<[TheBug]> (after unmounting of course)
<aandrew> although I usually just use mount -o loop /path/to/whatever /mnt/point -o ro
<[TheBug]> problem is it won't perform partprobe and the partition isn't on the main device
<[TheBug]> as you noted I did a partprobe on the loop device
<aandrew> oh, good point
<[TheBug]> as in the image contains partitions, it won't find this when trying to mount using mount -o loop
kprasadvnsi has quit [Ping timeout: 250 seconds]
kprasadvnsi has joined #armbian
bzyx has quit [Ping timeout: 252 seconds]
bzyx has joined #armbian
sndb has joined #armbian
attah has quit [Read error: Connection reset by peer]
attah has joined #armbian
minnix[m] has quit [Ping timeout: 250 seconds]
minnix[m] has joined #armbian
<aandrew> got that issue solved
<aandrew> apparently ext4 isn't 100% compatible with old linux distros and definitely not with paragon extfs fuse plugin
<aandrew> newer linux machine saw it just fine
<aandrew> dtb modified and I'm where I wanted to be like 5h ago :-)
<aandrew> thanks for the help guys, I do appreciate it :-)
archetyp has joined #armbian
<[TheBug]> ;)
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
qqqhhh2 has joined #armbian
qqqhhh has quit [Ping timeout: 246 seconds]
qqqhhh2 is now known as qqqhhh
archetyp has quit [Ping timeout: 268 seconds]
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
archetyp has joined #armbian
archetech_ has joined #armbian
archetech_ has quit [Quit: Konversation terminated!]
flyback has quit [Ping timeout: 245 seconds]
flyback has joined #armbian
archetyp has quit [Quit: Leaving]
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian