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
califax has quit [Remote host closed the connection]
califax has joined #armbian
califax has quit [Ping timeout: 268 seconds]
califax has joined #armbian
pablocastellanos has joined #armbian
juri_ has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
lemonzest has quit [Quit: WeeChat 3.5]
<stipa> dang, i've fried my opi, it's dead short over 5V rail...
<stipa> RIP OPI
<c0rnelius> good work
<stipa> tanks
<stipa> to bad i don't have bench psu
<stipa> i can't heat it up
archetech has quit [Ping timeout: 252 seconds]
<stipa> i guess it's the PMU
<c0rnelius> i made one out of an old x86 PSU
<c0rnelius> comes in handy
<stipa> yeah, i guess that would be too much, i would need something that can control current output and show how much is drained
<stipa> but, you may be right
<stipa> i have few of those around
<c0rnelius> well yeah its not exact like that. it can do 3.5, 5, 12 and 24
<stipa> i think there also some negative voltages
<c0rnelius> probably. I have a bunch of wires set aside as I only needed the following.
<stipa> but yeah, a computer psu could heat it up but some do shut down if they sense a short
<stipa> i have two old AT ones
<stipa> those that have a switch
<stipa> yeah, that could work
<c0rnelius> its can work. https://i.imgur.com/Z9dyqmc.jpg
<ArmbianHelper> ^ [image/jpeg] (196.9KiB)
<ArmbianHelper> ^ [image/jpeg] (227.5KiB)
<c0rnelius> just make sure its been unplugged for awhile so you don't kill ur self if you touch the wrong thing.
<stipa> right right
norwich has quit [Ping timeout: 240 seconds]
archetech has joined #armbian
xoan726 has joined #armbian
xoan72 has quit [Ping timeout: 268 seconds]
xoan726 is now known as xoan72
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #armbian
xoan721 has joined #armbian
xoan72 has quit [Ping timeout: 268 seconds]
xoan721 is now known as xoan72
norwich has joined #armbian
xoan725 has joined #armbian
xoan72 has quit [Ping timeout: 252 seconds]
xoan725 is now known as xoan72
samythemany has joined #armbian
xoan729 has joined #armbian
xoan72 has quit [Ping timeout: 268 seconds]
xoan729 is now known as xoan72
samythemany has quit [Quit: Bridge terminating on SIGTERM]
samythemany has joined #armbian
archetech has quit [Quit: Konversation terminated!]
xoan729 has joined #armbian
xoan72 has quit [Ping timeout: 252 seconds]
xoan729 is now known as xoan72
alekksander has joined #armbian
maknho has quit [Ping timeout: 252 seconds]
oida has quit [Ping timeout: 268 seconds]
mpmc is now known as Windbag
oida has joined #armbian
oida has quit [Ping timeout: 244 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 252 seconds]
Windbag is now known as mpmc
oida has joined #armbian
oida has quit [Ping timeout: 252 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 244 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 268 seconds]
Toasty has joined #armbian
califax has quit [Ping timeout: 268 seconds]
califax has joined #armbian
oida has joined #armbian
oida has quit [Ping timeout: 252 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 244 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 245 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 245 seconds]
haritz has quit [Remote host closed the connection]
oida has joined #armbian
lemonzest has joined #armbian
oida has quit [Ping timeout: 240 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 244 seconds]
oida has joined #armbian
oida has quit [Ping timeout: 252 seconds]
samythemany has quit [Ping timeout: 268 seconds]
stipa_ has joined #armbian
stipa has quit [Ping timeout: 252 seconds]
stipa_ is now known as stipa
samythemany has joined #armbian
oida has joined #armbian
oida has quit [Ping timeout: 276 seconds]
samythemany1 has joined #armbian
samythemany has quit [Ping timeout: 268 seconds]
oida has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
oida has quit [Ping timeout: 252 seconds]
xoan728 has joined #armbian
xoan72 has quit [Ping timeout: 252 seconds]
xoan728 is now known as xoan72
oida has joined #armbian
oida has quit [Ping timeout: 240 seconds]
samythemany1 has quit [Remote host closed the connection]
samythemany1 has joined #armbian
oida has joined #armbian
oida has quit [Ping timeout: 245 seconds]
oida has joined #armbian
cyph84 has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
SallyAhaj has joined #armbian
oida has quit [Ping timeout: 245 seconds]
haritz has joined #armbian
haritz has quit [Remote host closed the connection]
ajfriesen has quit [Quit: The Lounge - https://thelounge.chat]
califax has quit [Ping timeout: 268 seconds]
califax has joined #armbian
oida has joined #armbian
ajfriesen has joined #armbian
xoan720 has joined #armbian
xoan72 has quit [Ping timeout: 240 seconds]
xoan720 is now known as xoan72
<ArmbianHelper> ^ Error retrieving title. Check the log for more details.
califax_ has joined #armbian
califax has quit [Ping timeout: 268 seconds]
califax_ is now known as califax
haritz has joined #armbian
cyph84 has quit [Ping timeout: 252 seconds]
samythemany1 has quit [Ping timeout: 268 seconds]
archetech has joined #armbian
mrueg has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
lemonzest has quit [Quit: WeeChat 3.5]
quantum_ has joined #armbian
<quantum_> Well I feel pretty foolish. Trie trying respectively dd and Etcher. But nothing will boot to the quality SD card.d in an Odroid N2+ both Jammy KDE Plasma, and Bullseye...
<archetech> tried the switch in both spots?
<quantum_> yep.
<archetech> try the plain jammy img
<quantum_> SHA sum doesn't match, but then they don't say whether they use shasum, sha1sum, sha224sum, sha256sum, sha384sum, or sha512sum
<quantum_> I'm dling now.
<quantum_> The SD card mounts fine.
<quantum_> Ok 3 hours 56 min for the standard image...
<archetech> thats nuts
<archetech> its 360 MB
<Armbian-Discord> <M​anoftheSea> Shouldn't the number of bits indicate which sha algo?
<quantum_> I've gone to a diff mirror, faster now.
<quantum_> sha256sum matches the .xz file.
<quantum_> # dd if=Armbian_22.05.4_Odroidn2_bullseye_current_5.10.123.img of=/dev/sda bs=4M status=progress; sync
<quantum_> no boo. Solid red and double flashing blue, repeated.
<Armbian-Discord> <I​gorPec> solid red and flashing boot is o.k., screen might start a bit later
<quantum_> Ok now I have text. Ends with "Gave up waiting for filesystem device. (initramfs)
<c0rnelius> unless the blue blinking is super rapid. in that case something has gone wrong.
<quantum_> flash flash......flash flash... etc.
<Armbian-Discord> <I​gorPec> that is probably bad flash ... which is why we highly don't recommend dd
<c0rnelius> nothing surprises when it comes to the N2. When it works, it works great. When it doesn't is just a nightmare.
<quantum_> "ALERT! /dev/mmcblk1p1 does not exist!"
<Armbian-Discord> <I​gorPec> amplog devices are picky for sd cards
<quantum_> This very card wirked in this n2+ a year ago. It's a high-grade Transcend "High Endurance".
<quantum_> 128GB
<quantum_> Still downloading the XFCE and Plasma versions...
<Armbian-Discord> <I​gorPec> all those images have identical hw layer
<Armbian-Discord> <I​gorPec> in fact there are two kernels , 5.10 and 5.17
<quantum_> Well that doesn't portend well.
<Armbian-Discord> <I​gorPec> which could have diff, also in this
<quantum_> It seems to require a block device which isn't there.
<Armbian-Discord> <I​gorPec> yes, that means sd card was not initialized properly or similar
<Armbian-Discord> <I​gorPec> like i said, amlogic hw still have issues, for me, it always works, try different sd card perhaps, and check 5.10 and 5.17 kernel images
<Armbian-Discord> <I​gorPec> it must work
<quantum_> I only have Transcend. I'll check the bullseye images for where it's requiring /dev/mmcblk1p1. I did a dd. Maybe Etcher would work.
<Armbian-Discord> <I​gorPec> bullseye or jammy makes no dif
<Armbian-Discord> <I​gorPec> those images are made in automated manner. we provide them with two different kernels, only that matters
<Armbian-Discord> <I​gorPec> did you check forum if anyone run into similar problems?
<quantum_> Ok bullseye has 5.10. Maybe the xfce or Plasma flavors will have a newer kernel.
<quantum_> Haven't checked there. With such early and crucial failures it's discouraging. But I'll keep trying until it's Fail.
<Armbian-Discord> <I​gorPec> you have kernel version listed right from download button
<Armbian-Discord> <I​gorPec> Variant EU USA Asia Torrent User space Kernel Integrity Size Last modified Bullseye stable 5.10.y SHA ASC 399M Jul 1, 2022 Jammy Budgie stable 5.10.y SHA ASC 1194M Jul 1, 2022 Jammy Cinnamon stable 5.10.y SHA ASC 1227M Jul 1, 2022 Jammy Gnome stable 5.10.y
<Armbian-Discord> SHA ASC 1255M Jul 1, 2022 Jammy KDE Plasma stable 5.10.y SHA ASC 1227M Jul 1, 2022 Sid rolling 5.17.y SHA ASC 447M Jul 1, 2022 Sid Budgie rolling 5.17.y SHA ASC 1128M Jul 1, 2022 Sid Cinnamon rolling 5.17.y SHA ASC 1171M Jul 1, 2022 Sid Gnome rolling 5.17.y
<Armbian-Discord> SHA ASC 1134M Jul 1, 2022 Sid KDE Plasma rolling 5.17.y SHA ASC 1237M Jul 1, 2022 Sid XFCE rolling 5.17.y SHA ASC 1001M Jul 1, 2022
<quantum_> Hm, have to use Sid for 5.17. This needs to be stable.
<Armbian-Discord> <I​gorPec> stable should be 5.10.y
<Armbian-Discord> <I​gorPec> but you can try 5.17.y
<quantum_> True. Just finished dling xfce stable.
<Armbian-Discord> <I​gorPec> also use some proven tool for writing image - which verifies
<Armbian-Discord> <I​gorPec> maybe your sd card is broken and you will waste several hours before you realize
<Armbian-Discord> <I​gorPec> if you verify, you know
<quantum_> sha256sum checks. Using Etcher...
<Armbian-Discord> <I​gorPec> ok
stipa_ has joined #armbian
stipa has quit [Ping timeout: 245 seconds]
stipa_ is now known as stipa
<quantum_> I​gorPec: Identical symptom, as you'd predicted. "ALERT! /dev/mmcblk1p1 does not exist!"
<quantum_> (initramfs)
<quantum_> grep can't find mmcblk1p1 anywhere in /etc.
<quantum_> I'll try kernel 5.17.
alekksander has quit [Quit: Konversation terminated!]
crabbedhaloablut has quit [Remote host closed the connection]
califax has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
califax has joined #armbian
califax has quit [Write error: Connection reset by peer]
crabbedhaloablut has quit [Write error: Connection reset by peer]
califax has joined #armbian
crabbedhaloablut has joined #armbian
<quantum_> Blank screen on HDMI with kernel 5.17. Tried switch both positions.
<quantum_> Tried two different n2+'s. Looks like Armbian is not compatible with Odroid N2+.
<archetech> Host: odroidn2 Kernel: 5.17.5-meson64 aarch64 bits: 64 Console: pty pts/0
<archetech> Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
<archetech> Welcome to Armbian 22.05.3 Jammy with bleeding edge Linux 5.17.5-meson64
<archetech> solid red 2 blues using sdcard switch set to sdcard
<archetech> so seems its an image issue I dont have which img I used handy
<archetech> Armbian_22.05.2_Odroidn2_jammy_edge_5.17.5.img
<archetech> that will work if your sdc is good
archetech has quit [Quit: Konversation terminated!]
Toasty has quit [Ping timeout: 268 seconds]
haritz has quit [Ping timeout: 240 seconds]
<quantum_> Even Armbian_22.05.4_Odroidn2_bullseye_current_5.10.123 doesn't work. It can't find the UUID device it needs to boot.
<quantum_> I've tried six images from here: https://mirrors.jevincanders.net/armbian/dl/odroidn2/archive/
<ArmbianHelper> ^ Index of /armbian/dl/odroidn2/archive
<quantum_> They all confirm sha256sum, but none is able to boot. Rotating circle for an hour and a half.
<quantum_> Why am I wasting my time with this?
califax has quit [Remote host closed the connection]
califax has joined #armbian
archetech has joined #armbian
<Armbian-Discord> <M​anoftheSea> Can you type at the initramfs?
<Armbian-Discord> <M​anoftheSea> Maybe check if you instead have an mmcblk0?
<archetech> armbianenv.txt check the root setting
califax has quit [Remote host closed the connection]
califax has joined #armbian
haritz has joined #armbian
quantum_ has quit [Remote host closed the connection]
haritz has quit [Remote host closed the connection]
quantum_ has joined #armbian
<quantum_> Can not type at (initramfs)
<quantum_> fstab calls for a certain UUID but boot fails to find that very UUID. Mounting the SD card on a diff system confirms that sda1 is indeed that UUID. Something is screwed.
<clever> quantum_: during boot, the kernel should print every partition it can find
<clever> [ 1.717790] ata3.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 32), AA
<clever> [ 1.731094] sda: sda1 sda2 sda3 sda4
<clever> like this
<quantum_> CLI images fail that way. GUI images go to the Armbian logo and rotate the circle for an hour and a half. No idea what it's doing.
<quantum_> On CLI it may, but then it goes into a loop looking for disk and finally times out with the UUID problem.
<archetech> armbianenv.txt check the root setting
<quantum_> I'm writing to SD Armbian_22.05.4_Odroidn2_bullseye_current_5.10.123.img
<quantum_> All Sid images boot with no HDMI output.
<quantum_> Don't know where armbianenv.txt is.
<archetech> /boot
<quantum_> It has 5 lines. Checking the UUID.
<quantum_> Confirmed, /dev/sda1 in fact has UUID="7f6e2bfc-5c36-4b15-b638-a5ba7f9f9a90", as represented in armbianenv.txt.
<quantum_> ... but on boot can't find it.
<quantum_> (rootdev=)
<quantum_> rootfstype= is in fact ext4 as represented since I have it mounted on another system.
<archetech> now check boot.cmd
<archetech> rootdev=
SallyAhaj has quit [Remote host closed the connection]
<quantum_> setenv rootdev "/dev/mmcblk1p1"
<quantum_> setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 coherent_pool=2M loglevel=${verbosity} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 elevator=noop hdmimode=${hdmimo>
<quantum_> setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 coherent_pool=2M loglevel=${verbosity} ubootpart=${partuuid} libata.force=noncq usb-storage.quirks=${usbstoragequirks} ${usbhidqui>
<archetech> mmcblk0p1 is usually root
<quantum_> No idea what the SD card looks like to the Odroid.
<steev> quantum_ when it's sitting there doing the logo, you can hit esc i believe
<quantum_> I can change it. But the failure is by UUID not block device.
<archetech> steev: I think it gets stuck on expanding the rootfs
<steev> archetech: possibly; though quantum_ does seem to have rootdev set to /dev/mmcblk1p1 so it shouldn't be trying to touch /dev/sda partitions?
<archetech> reson im having him look at env and uboot setup pretty sure I had to monkey with it to bot too
<steev> for testing purposes... what happens if you unplug sda?
<quantum_> If you mean from the Odroid I haven't tried that, as it's the boot device.
<archetech> quantum_: you could use odroid ubu ya know
SallyAhaj has joined #armbian
<quantum_> Well it's /dev/sda on my laptop. That's where I examine it. The only place I can examine it.
<steev> it won't show up as sdX on the odroid though
<steev> it's showing up as sda on your laptop because usb scsi device
<quantum_> Understand.
<quantum_> odroid ubu does the same things, in CLI and GUI.
<archetech> then its def the sdcard
<quantum_> Well it's a high-grade Transcend Hig Endurance. I have another I can try.
<quantum_> Is it not possible that the Odroid can't handle 128GB?
<steev> sd cards can, sadly, fail at any (and usually the most inopportune) time
<archetech> dont care what it is ya should have tried another sdcard in the first hour of troubleshooting
<quantum_> No because this exact card worked before with Ubu Mate 20.
<steev> yes, but testing a different card can then tell if it's an issue with the card, or with the image(s)
<archetech> look they are finicky things get real or wste ur time
<quantum_> Doing it...
<steev> saying "this card worked before, so it should continue to work" isn't how sdcards work - and i'm not saying that it's the card at fault
<steev> if you have serial output from the droid, getting the boot log would be nice
crabbedhaloablut has quit [Remote host closed the connection]
<quantum_> Don't have serial. Flashing...
<quantum_> (Etcher)
crabbedhaloablut has joined #armbian
<quantum_> Diff SD, same prob. About 25 of these: Begin: Running /scripts/local-block ... done.
<quantum_> Then "Gave up waiting for root file system device. Common problems:
haritz has joined #armbian
<quantum_> - Root args (cat /proc/cmdline) as if I could so a cat
<archetech> got a spare hdd and usb3 caddy use that instead of sdcard
<archetech> much nicer perf too
<quantum_> -- Check rootdelay. (did the system wait long enough)
* archetech rarely uses sdcards
<archetech> ya rootdelay should be =10
<quantum_> - Missing modules (cat /proc/modules: ls /dev)
<archetech> if ya use usb3
<quantum_> ALERT! UUID="7f6e2bfc-5c36-4b15-b638-a5ba7f9f9a90" does not exist. Droping to a shell!
<quantum_> (initramfs)
<quantum_> Without exception this happens with all CLI images.
<quantum_> I can try to dd the image to a usb flashdrive, but how do I direct the boot there?
<quantum_> UUID 9a90 -does- exist. This is the nexus of the problem. Probably with all the N2 images.
<archetech> odroid has netboot installer for usb3 drives
<archetech> uses spi