ArmbianHelper 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 | Logs: -> irc.armbian.com
<stipa> if it's not USB3 related it should work
<stipa> USB3 and video acceleration sux
<stipa> and choose a board that has a maintainer
<stipa> then try to get the zwave system working
<stipa> mostly ppl bodge NASes and various internet servers
<stipa> there's not much home automation
<stipa> yet
norwich_ has joined #armbian
norwich has quit [Ping timeout: 260 seconds]
norwich_ is now known as norwich
<philarmbian89> Yeah I might just have to use this OrangePiPcPlus for something else
<philarmbian89> can't seem to get hassio / openhab working with Docker
<philarmbian89> I can manually pull images for hassio but it doesn't recognize zwave from the same host on 3000
<stipa> does it work without docker?
<philarmbian89> No support for Armbian with either of those projects
<philarmbian89> like without docker
<stipa> i don't get it, those projects works exclusively in docker?
<philarmbian89> In the context of Armbian yeah :(
<stipa> so, you can't just download the source and compile?
<stipa> o narmbian
<stipa> on*
<stipa> you could try running it inside of a VM on armbian
philarmbian89 has quit [Remote host closed the connection]
<stipa> if the tools you want work like images you boot and the machine runs just that
<stipa> newer OPIs should have silicon for VMs
philarmbian89 has joined #armbian
<philarmbian89> sry got kicked
<stipa> 02:37:34 stipa | if the tools you want work like images you boot and the machine runs just that
<stipa> 02:38:28 stipa | newer OPIs should have silicon for VMs
<philarmbian89> Yeah they have an .ova I think
<stipa> if you don't have it enabled you can build an armbian image with the VM ability enabled
<stipa> baked into the kernel and try it out
<stipa> if you get USB passthrough you're golden
<philarmbian89> actually .vdi
<ArmbianHelper> ^ Linux - Home Assistant
<philarmbian89> That's what I'm after I believe
<stipa> yeah, i guess you load one of those into a VM
<stipa> KVM i guess
<stipa> that's Allwinner H3
minist3r has joined #armbian
<Armbian-Discord> <T​onymac32> Philarmbian89 I have run HassIO on their own distro, the z-wave add-ons are good
<minist3r> I have a rockpro64 chip and I upgraded to kernel 5.15.48 on accident and its unstable and lost video and network drivers. I'm trying to downgrade to 5.15.35 the previous version that was stable but with armbian-config it seems to need an internet connection to do this. Does anyone know how I can do this?
<Armbian-Discord> <T​onymac32> I use z-wave thernostats
<stipa> minist3r: install the old image to another sdcard and transfer configs from the borked card
<stipa> T​onymac32 on what do you run that distro
<philarmbian89> Nothing right now
<philarmbian89> I have an OrangePiPcPlus I'm trying to use for hassIO
<minist3r> stipa I have boot partition on sd card but booting OS from ssd can I still do what you recommend with this config?
<stipa> minist3r: if the configs are on the SSD then put it in a computer and take what you need before the reinstall of armbian over it
<Armbian-Discord> <T​onymac32> Stipa on an N2. But it destroyed itself so maybe I roll a custom T4 image for it instead
<minist3r> so your saying to backup then wipe SSD and reinstall then restore backup?
<stipa> minist3r: yea
<minist3r> I was hoping to do it without reinstall
<minist3r> I dont mind reinstalling boot drive on sd card but dont really want to wipe my OS on ssd
<stipa> minist3r: then get the internet somehow and try something else
<stipa> in armbian-config maybe you could get back
<Armbian-Discord> <T​onymac32> The roots started getting corrupted coincidentally at the same time I decided to plug in a USB device. 🤣🤣🤣
<stipa> ghosts
<stipa> minist3r even if you get the internet and try to fix it maybe it's smart to do the backup anyway
minist3r has quit [Ping timeout: 268 seconds]
minist3r has joined #armbian
<minist3r> stipa I have a backup but when I restore it, it does not restore the old kernel
<stipa> then install everything and get just the configs
<stipa> from the backup
<minist3r> ya only reason i did not want to go that route is because I have xmpp and webserver setup that took alot of work and dont really want to do that over
<minist3r> theres no way i can just revert to old kernel?
<stipa> everything you need keep on the backup NAS or some kind of a backup
<stipa> when shit hits the fan you have the configs
<minist3r> I have everything backed up with redshift
<minist3r> I mean timeshift
<philarmbian89> Okay I changed approach and I'm going to start a docker container version of hassio on top of Armbian on the OrangePiPcPlus since hassio cannot natively install to this board like a RaspberryPi, that seems to be launching just fine
<minist3r> what tells the OS to boot what kernel
<minist3r> is it in the boot partition?
<minist3r> or what tells the bios to boot what kernel
<stipa> minist3r: i guess it's on the sdcard
<minist3r> I see in ArmbianEnv.txt its pointing toward sd card but dont see where it specifies what kernel to boot
<stipa> PhilArmbian89: kewl
<stipa> minist3r: i have no idea, i don't have such a setup
<minist3r> well on any armbian config where does it look for what kernel to boot? is there a config in the boot partition?
<ArmbianHelper> ^ Recovery - Armbian Documentation
<ArmbianHelper> ^ The boot process and various devices - Advanced users - Development - Armbian Community Forums
<ArmbianHelper> ^ [SOLVED] Apologies, dumb question on changing Armbian Kernel Image - Beginners - Armbian Community Forums
<minist3r> thank u
<stipa> yw, fell free and scrub the forum for more
philarmbian89 has quit [Remote host closed the connection]
archetech has quit [Quit: Konversation terminated!]
<Armbian-Discord> <T​onymac32> stipa I'm tired of the N2 proving to me it's unfit for literally every job, I have to cut it loose
<Armbian-Discord> <T​onymac32> can't anyone else put this chip ona board? or can Hardkernel maybe, just maybe, fix it? They can make good stuff I've seen it
<stipa> T​onymac32 idk if the money can fix it either
<stipa> it's hard to look in the chip architecture when it's baked and encapsulated
<stipa> and it's to expensive to make another one
<stipa> also take into the account that they don't even know what to fix in the first place in the silicon so making another one makes no sense
<Armbian-Discord> <T​onymac32> well it seems clear they messed up the power
<stipa> the PMU chip?
<stipa> what's wrong with it?
<stipa> it's doesn't give correct voltage?
<stipa> it doesn't rise up the voltage when the frequency increases?
<Armbian-Discord> <T​onymac32> the USB ports starve the devices and seem to cause issues with the rest of the board
<stipa> can the PSU provide?
<stipa> some PSUs think it's the short if the load is high and they turn off
<stipa> and probably give half of what they're rated for
<stipa> so that trip out at half of what they're rated for
<stipa> they*
<Armbian-Discord> <T​onymac32> rofl 12V 4A
<stipa> yeah, try to short it and see at how much Amps it turns of
<stipa> if it's a modern PSU it should turn off, i guess the law is like that
<Armbian-Discord> <T​onymac32> ... While I'm sure this would be a super enlightening exercise, this is the second supply I've used with this board, it had a 12V 2A
<Armbian-Discord> <T​onymac32> I could rig this up on my bench with the scope I guess
<Armbian-Discord> <T​onymac32> or just use a board that doesn't seem to care using the same brand/series supply
<stipa> yeah, the first step would be to rule out the PSU
<Armbian-Discord> <T​onymac32> Of course
<stipa> and actually make sure that it can provide the power
<stipa> despite what is written on it
<stipa> despite of*
<Armbian-Discord> <T​onymac32> stipa I've documented this sort of thing repeatedly for others
<Armbian-Discord> <T​onymac32> I'm also an electrical engineer
<Armbian-Discord> <T​onymac32> this is in my wheelhouse, it isn't the supply
<stipa> then fuck idk, desolder the usb ports and put them in series with a fast fancy AMp meter
<stipa> that has logging
<stipa> and log when the PMU trips out
<Armbian-Discord> <T​onymac32> lol I'm swimming in SBC's, I'm not wasting my time on this one, seriously
<stipa> well, you'll have to waste it on eventually
<stipa> on one*
<Armbian-Discord> <T​onymac32> nah, I just won't buy another N2
<stipa> what about the N2+ ?
<Armbian-Discord> <T​onymac32> I don't see any topology differences, just the SoC binning
<stipa> T​onymac32 if you can lower the frequency, try that, i guess it should waste less power
<stipa> it could give some headroom to the USB
<Armbian-Discord> <T​onymac32> see, I have this problem
<Armbian-Discord> <T​onymac32> I was sold a device with advertised capabilities
<Armbian-Discord> <T​onymac32> if it can't do that
<Armbian-Discord> <T​onymac32> Then it is goign into the waste bin and I'm going to bitch about it
<stipa> well, the easiest thing to do is to give up
<stipa> but, there's no fun in that
<Armbian-Discord> <T​onymac32> I'm past having fun with faulty designs, I'm too burnt out to work on the good ones at this point
minist3r has quit [Quit: Leaving.]
<Armbian-Discord> <T​onymac32> The only thing going to make any difference to the silly ARM SBC situation is some people telling the vendors to F off with their trash
minist3r has joined #armbian
minist3r has quit [Client Quit]
minist3r has joined #armbian
<stipa> well, you can't say no to a cheap deal
<Armbian-Discord> <T​onymac32> those aren't cheap
<stipa> oh dang
<stipa> that's bad
<stipa> but you're right, sometimes it just doesn't pay off going further and giving up is a smart thing to do
<stipa> you have like a ton of failed businesses and they all started with i can do it because i'm special
<stipa> yeah, special to the banks
<Armbian-Discord> <T​onymac32> lol I'm disappointed with this one because they can/have made good boards
<stipa> yeah, nothing is perfect
<stipa> in mostly everything i thought is perfect i found flaws
<stipa> i guess one has simply accept it and roll with what he has
<stipa> bodge something together and make the job done
crabbedhaloablut has quit [*.net *.split]
califax has quit [*.net *.split]
crabbedhaloablut has joined #armbian
califax has joined #armbian
Bag_Gnome is now known as WindBag
oida has quit [Ping timeout: 260 seconds]
<stipa> i have one RTL8153 chip overheating in 1000Mbs mode, got to look on the PCB of it to see if i can get some clues
<stipa> it works on like ove 60 C
<stipa> idling
<stipa> it works stable on the software side
oida has joined #armbian
<Armbian-Discord> <T​onymac32> AHA
<Armbian-Discord> <T​onymac32> mine is literally the sample revision 0.3
<Armbian-Discord> <T​onymac32> https://wiki.odroid.com/odroid-n2/hardware
<ArmbianHelper> ^ odroid-n2:hardware [ODROID Wiki]
xoan72545123521 has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123521 is now known as xoan7254512352
xoan72545123526 has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123526 is now known as xoan7254512352
aasami_ has joined #armbian
lemonzest has quit [Quit: WeeChat 3.5]
minist3r has quit [Quit: Leaving.]
lemonzest has joined #armbian
indy has quit [Ping timeout: 260 seconds]
indy has joined #armbian
cornelius has quit [Ping timeout: 255 seconds]
xoan72545123521 has joined #armbian
samythemany has joined #armbian
xoan7254512352 has quit [Ping timeout: 255 seconds]
xoan72545123521 is now known as xoan7254512352
xoan72545123529 has joined #armbian
xoan7254512352 has quit [Ping timeout: 255 seconds]
xoan72545123529 is now known as xoan7254512352
c0rnelius has joined #armbian
montjoie has quit [Ping timeout: 268 seconds]
montjoie has joined #armbian
xoan72545123523 has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123523 is now known as xoan7254512352
abws has joined #armbian
maknho_ has quit [Quit: WeeChat 2.3]
binarym_ is now known as binarym
abws has quit [Quit: abws]
mintelodiaz has joined #armbian
archetech has joined #armbian
samythemany has quit [Remote host closed the connection]
samythemany has joined #armbian
alekksander has joined #armbian
<stipa> T​onymac32 yeah, could be that sample has some chips that got replaced later
<stipa> some fixes can be done at home
<stipa> like changing a cap or resistor
<stipa> this could be tricky if it's not a drop i nreplacement "Due to the semiconductor shortage, the maximum DC input voltage was lowered from 18V to 16V to use to FirstSilicon's FC6800 from FC3470. "
mintelodiaz has quit [Ping timeout: 252 seconds]
<stipa> but that one doesn't seem like a problem when there were those chips avilable i guess
<stipa> this could be your fix > To lower the electrical stress to the GL3523 hub controller, the GL3523 power source has changed to 5V from 3.3V by using internal regulator. Mount a zero ohm resistor between the source and drain of Q1 instead of the FET
<stipa> As a negative side effect, the PWR red LED does dimly turn on even when the system turns off. This issue appears with the production batch of EL2102 only.
mintelodiaz_ has joined #armbian
mintelodiaz_ has quit [Remote host closed the connection]
quantum_ has joined #armbian
<quantum_> # dd if=Armbian_22.02.2_Odroidn2_jammy_current_5.10.103_xfce_desktop.img of=/dev/sda bs=4M status=progress
<quantum_> ... yet I only get the boot part as good, which I can mount.
<quantum_> Second part has a bad codepage and no PARTUUID.
<Armbian-Discord> <M​anoftheSea> Is that true in the image as well?
<Armbian-Discord> <M​anoftheSea> you can point gdisk directly at the image
<quantum_> Don't have gdisk. (KDE)
<quantum_> I pointed gparted at the image and indeed only one 6.12GB part.
<quantum_> I don't understand why this is. This image worked when I flashed it to another SD.
<Armbian-Discord> <M​anoftheSea> can you not install gdisk? From what little I remember about gparted, it makes assumptions and changes that are unwelcome
<Armbian-Discord> <T​enkawa> where did you get the image? I'll pull it and take a look (unless you built it yourself)
<ArmbianHelper> ^ armbian storage
<Armbian-Discord> <T​enkawa> ok just a few to dload it
<quantum_> I do seem to have gdisk, but have already deleted the image to DL another.
<Armbian-Discord> <T​enkawa> ok its downloading now
<Armbian-Discord> <T​enkawa> this dload mirror speed is very bouncy today
<quantum_> gdisk finds only one partition in the freshly-downloaded image.
<quantum_> Flashing to SD, same results as with prior image.
<Armbian-Discord> <T​enkawa> ok extracting it now
<Armbian-Discord> <T​enkawa> it should only have 1 partition
<quantum_> Flashing it I get two parts, the first is mountable, the second is not and has no PARTUUID, which it should.
<Armbian-Discord> <T​enkawa> hmm
<Armbian-Discord> <T​enkawa> its only got one i the image
<Armbian-Discord> <T​enkawa> Device Boot Start End Sectors Size Id Type Armbian_22.02.2_Odroidn2_jammy_current_5.10.103_xfce_desktop.img1 8192 12861439 12853248 6.1G 83 Linux
<Armbian-Discord> <T​enkawa> they must be extracting u-boot as part of a process
<Armbian-Discord> <T​enkawa> notice the offset
<quantum_> The first part has files I haven't seen before, and it does not seem to be useable.
<Armbian-Discord> <T​enkawa> whats your offsets once its flashed
<quantum_> How do I find out?
<Armbian-Discord> <T​enkawa> yeah you have an .itb and another file right?
<quantum_> compat check, filesync.version, md5sum.all, navengine, tm, version.
<quantum_> gdisk: Number Start (sector) End (sector) Size Code Name
<quantum_> 1 8192 12861439 6.1 GiB 8300 Linux filesystem
<Armbian-Discord> <T​enkawa> thats only one filesystem. wheres the second?
<quantum_> That's the only part it sees, whereas I end up with two on SD. One or both must have a PARTUUID so I can make mods to boot my Odroid N2+.
<Armbian-Discord> <T​enkawa> thats all thats on that image
<Armbian-Discord> <T​enkawa> I need the output of what your sd shows
<quantum_> That's it, above.
<quantum_> But lsblk sees two parts.
<c0rnelius> looks normal for an armbian img, unless for some reason they are using a boot partition on odriods?
<quantum_> Warning! Secondary partition table overlaps the last partition by
<quantum_> You will need to delete this partition or resize it in another utility.
<quantum_> 33 blocks!
<quantum_> (gdisk)
<quantum_> But see I need a PARTUUID to set up an /extlinux file on SD so my N2+ will boot.
<quantum_> I have to use a Fedora kernel.
<Armbian-Discord> <T​enkawa> Never seen anyone need to myself (we don't on our builder)
<Armbian-Discord> <T​enkawa> our extlinux boots just fine
<Armbian-Discord> <T​enkawa> with one fs
<Armbian-Discord> <M​anoftheSea> You should wipe your SD and start over
<quantum_> My proceure is the only way my N2+ will boot, and it comes from 'some user' on the forum. It's a Debian kernel problem.
<Armbian-Discord> <T​enkawa> I don't know Armbian's internals to their build process unfortunately but I know on the N2 it definitely works
<Armbian-Discord> <T​enkawa> N2+ as well
<Armbian-Discord> <M​anoftheSea> Remember there's a secondary GPT at the end of the SD card, which won't be touched by writing an image from the start to the end of the compression
<Armbian-Discord> <T​enkawa> exactly.. gotta wipe it
<Armbian-Discord> <T​enkawa> gotta zero the header
<quantum_> How?
<Armbian-Discord> <M​anoftheSea> At the very least, point gdisk at the SD card, expert mode: z - for zap partition table
<Armbian-Discord> <T​enkawa> or dd the first 8192 bytes of the disk
<Armbian-Discord> <M​anoftheSea> and be careful, you are intentionally wiping a disk, make sure it's the right disk
<Armbian-Discord> <T​enkawa> indeed
<Armbian-Discord> <M​anoftheSea> but that doesn't get the secondary
<Armbian-Discord> <T​enkawa> yes it does
<Armbian-Discord> <M​anoftheSea> the secondary is at the last sectors of the block device.
<Armbian-Discord> <T​enkawa> I use a 1M bs
<Armbian-Discord> <M​anoftheSea> -1 through -32, right?
<Armbian-Discord> <T​enkawa> always has worked in the past
<quantum_> Can't find an expert mode in gdisk, and there is no 'z' in commands.
<Armbian-Discord> <M​anoftheSea> "x" for expert
<Armbian-Discord> <T​enkawa> never has not worked in 5000+ builds
<c0rnelius> not sure how one could be using gpt with amlogic, but to wipe gpt one would: `dd if=/dev/zero of=/dev/sdx# bs=8M count=1`
<quantum_> Ok used xpert mode and 'z', dd'ed the image, but same result.
<Armbian-Discord> <M​anoftheSea> 8 megs? Geez. That's not just GPT, you're hitting MBR, GPT primary, and much of the AMLogic bootloader. Still missing the Secondary
<Armbian-Discord> <M​anoftheSea> But also, as a reminder with amlogic, the amlogic bootloader is right on top of the gpt table.
<Armbian-Discord> <M​anoftheSea> I believe it's possible to offset the GPT's table of entries, but I don't know of anyone that does so.
<archetech> n2 img doesnt use gpt
<Armbian-Discord> <M​anoftheSea> so we should stop talking about it
<quantum_> Idk what this means.
<Armbian-Discord> <M​anoftheSea> MBR doesn't have PARTUUID's
<[TheBug]> quantum_: get a different image and try it, that one likely is just corrupt
<quantum_> My god I guess I'm dead again. Got to go to work.
quantum_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
samythemany has quit [Remote host closed the connection]
samythemany has joined #armbian
<archetech> my n2 jammie uses uuid in fstab
<Armbian-Discord> <M​anoftheSea> uuid is a filesystem attribute
<[TheBug]> it's probably a corrupt image there are some floating around
<Armbian-Discord> <M​anoftheSea> In GPT, a partition can have a GUID for parttype, a GUID for partuuid, a label, and a filesystem uuid
<archetech> so does my armbianEnv.txt its mbr
<Armbian-Discord> <M​anoftheSea> /dev/disk/by-uuid is the filesystem's uuid - ext4 uses guid, while fat uses something shorter
<ArmbianHelper> ^ [image/png] (55.4KiB)
<Armbian-Discord> <M​anoftheSea> so, that identifies MBR, not GPT. Also, NTFS?
<archetech> mbr uses uuid's because whoever built it enabled it in initramfs
<archetech> Linux odroidn2 5.17.5-meson64 id like to upgrade this kernel though dont see any option for 5.18+ in armbian-config ;/
<Armbian-Discord> <M​anoftheSea> what?
<Armbian-Discord> <M​anoftheSea> I don't understand "enabled it in initramfs"? Enabled what? The kernel does the probing of the partitions, identifying the filesystems, and recording their uuids, right? But that information isn't in the MBR.
hgpgbb has joined #armbian
<c0rnelius> there is a reason why u-boot has fstype / uuid support.
<Armbian-Discord> <M​anoftheSea> in that case, the u-boot firmware does the fs recognition and reading of uuid
<Armbian-Discord> <M​anoftheSea> And it does so based on knowing where partitions are, based on mbr table or gpt
<Armbian-Discord> <M​anoftheSea> But the N2 uses MBR. For some reason, the image is identifying the fs as ntfs - which we're understanding as corruption
The_Loko has joined #armbian
samythemany has quit [Ping timeout: 258 seconds]
hgpgbb has quit [Remote host closed the connection]
Masterphi has quit [Quit: Masterphi]
samythemany has joined #armbian
<Armbian-Discord> <T​heBug> Actually, two thing... I grabbed wrong image and also I used partprobe wrong in my example -- when using it correctly the image is mountable as a loop device. Not sure what issue the other guy was having.
<ArmbianHelper> ^ [image/png] (165.8KiB)
<[TheBug]> pretty sure that is the correct image now and it is mountable
The_Loko has quit [Ping timeout: 248 seconds]
oida has quit [Ping timeout: 260 seconds]
ajfriesen69 has joined #armbian
Smedles has quit [Remote host closed the connection]
ajfriesen6 has quit [Ping timeout: 260 seconds]
ajfriesen69 is now known as ajfriesen6
Smedles has joined #armbian
The_Loko has joined #armbian
xoan72545123523 has joined #armbian
oida has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123523 is now known as xoan7254512352
The_Loko has quit [Quit: Leaving]
The_Loko has joined #armbian
alekksander has quit [Ping timeout: 268 seconds]
samythemany1 has joined #armbian
samythemany has quit [Ping timeout: 258 seconds]
maknho has joined #armbian
alekksander has joined #armbian
archetech has quit [Quit: Konversation terminated!]
lemonzest has quit [Quit: WeeChat 3.5]
archetech has joined #armbian
schwar3kat has joined #armbian
schwar3kat has quit [Quit: Leaving]
alekksander has quit [Quit: Konversation terminated!]
Herc has quit [Quit: Leaving]
califax has quit [Remote host closed the connection]
califax has joined #armbian
aasami_ has quit [Quit: Lost terminal]
Herc has joined #armbian
The_Loko has quit [Quit: Leaving]
xoan72545123523 has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123523 is now known as xoan7254512352
archetech has quit [Ping timeout: 252 seconds]
xoan72545123521 has joined #armbian
<ArmbianHelper> ^ New understanding of electromagnetism could e | EurekAlert!
<nekomancer[m]> old news
xoan7254512352 has quit [Ping timeout: 260 seconds]
xoan72545123521 is now known as xoan7254512352
xoan72545123526 has joined #armbian
xoan7254512352 has quit [Ping timeout: 252 seconds]
xoan72545123526 is now known as xoan7254512352
xoan7254512352 has quit [Remote host closed the connection]
xoan72545123526 has joined #armbian
archetech has joined #armbian