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 feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
hbbs has joined #armbian
<DC-IRC>
[Discord] <therealmarcone> (if you wanted to be extra fancy, you could use /sys/block/${diskdev}/device/preferred_erase_size instead of hardcoding the alignment to 16 MiB)
<DC-IRC>
[Discord] <igorpec> oh. make a PR. I am unable to follow / worked whole day, spent 2h on meetings ... after week of lying sick in the bed.
<DC-IRC>
[Discord] <therealmarcone> My sympathies. I've been sick for 3 weeks. Finally starting to get better now.
hbbs has quit [Quit: bye]
hbbs has joined #armbian
shoragan has quit [Read error: Connection reset by peer]
shoragan has joined #armbian
shoragan has quit [Client Quit]
shoragan has joined #armbian
zeemate has quit [Ping timeout: 246 seconds]
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
jantones_ has joined #armbian
jantones has quit [Ping timeout: 255 seconds]
jantones_ has quit [Ping timeout: 268 seconds]
jantones has joined #armbian
jantones_ has joined #armbian
jantones has quit [Ping timeout: 252 seconds]
jantones_ has quit [Ping timeout: 256 seconds]
jantones has joined #armbian
buzzmarshall has quit [Quit: Konversation terminated!]
lyri has quit [Ping timeout: 260 seconds]
lyri has joined #armbian
archetech has quit [Quit: Konversation terminated!]
metta has quit []
upekkha has joined #armbian
junaid_ has joined #armbian
KREYREN_ has joined #armbian
KREYREN has quit [Ping timeout: 255 seconds]
alekksander has joined #armbian
bantu has quit []
bantu has joined #armbian
<DC-IRC>
[Discord] <igorpec> Oh, its likewise 😦 This time of the year I guess.
<DC-IRC>
[Discord] <igorpec> vim3 jammy?
jantones_ has joined #armbian
jantones has quit [Ping timeout: 276 seconds]
jclsn has joined #armbian
zeemate has joined #armbian
<DC-IRC>
[Discord] <nicod_sbc> Yes. Will look more into it and test n2+
jclsn has quit [Quit: WeeChat 4.1.2]
<DC-IRC>
[Discord] <igorpec> we might switch desktops to nooble
<DC-IRC>
[Discord] <igorpec> mesa is very old on jammy
<DC-IRC>
[Discord] <nicod_sbc> I"ll test noble too then. First sport, then testing.
<DC-IRC>
[Discord] <igorpec> you can build nooble and see how it behaves. should be better in this concern
zeemate has quit [Ping timeout: 264 seconds]
<DC-IRC>
[Discord] <nicod_sbc> N2+ has it too on Jammy. Here some error messages from dmesg. This I see in server :
<DC-IRC>
[Discord] <nicod_sbc> Building Noble now.
<DC-IRC>
[Discord] <nicod_sbc> I for now can't make the N2+ crash as the VIM3 does. Error messages are the same. Weird.
<DC-IRC>
[Discord] <igorpec> this is expected, yes
<DC-IRC>
[Discord] <nicod_sbc> Not sure. I'll try my VIM3 with another PSU and cable, I don't suspect that to be an issue but you never know.
<DC-IRC>
[Discord] <igorpec> i am 99% sure its mesa drivers. they are too old on jammy
<DC-IRC>
[Discord] <igorpec> and all those SoCs uses the same
<DC-IRC>
[Discord] <nicod_sbc> Me too, but then I'd expect the N2+ to crash at the same issue as VIM3, but N2+ seems "stable" for my tests with tons of errors.
<DC-IRC>
[Discord] <igorpec> for final builds i think to rather provide one gnome jammy desktop for legacy purposes, the rest goes to nobble.
<DC-IRC>
[Discord] <igorpec> as patching mesa drivers to make this work on different SoCs exceeds every sane R&D
<DC-IRC>
[Discord] <nicod_sbc> Yeah, no Jammy gnome better if it's not stable enough to get through login.
<DC-IRC>
[Discord] <nicod_sbc> I'm manually installing ubuntu-desktop, will build a armbian-gnome desktop to see if it's the same.
<DC-IRC>
[Discord] <igorpec> works well on rk3399 .so
<DC-IRC>
[Discord] <igorpec> that comes without mesa, so it will be ok
<DC-IRC>
[Discord] <igorpec> solution is not simple in any case.
<DC-IRC>
[Discord] <nicod_sbc> Now can't recreate the crashes with power bank and my best USB-C cable. So might have been a power issue. I saw tons of errors in dmesg and thought that must be the cause...
<DC-IRC>
[Discord] <igorpec> i have many panfrost ffe40000.gpu: l2 power transition timeout on sm1 / s905x3
<DC-IRC>
[Discord] <igorpec> but it works normally
<DC-IRC>
[Discord] <igorpec> on latest mesa
<DC-IRC>
[Discord] <nicod_sbc> Ok, then it might not be critical. I was about sure it was since I could always recreate with the same actions. Running armbianmonitor -u would crash it every time. Now it all works, can run everything. So false alert. Sorry. I trusted my PSU and cable. And VIM3 never had power issue's.
<DC-IRC>
[Discord] <igorpec> ok
<DC-IRC>
[Discord] <nicod_sbc> Then VIM3 and N2(+) are ok beside the many panfrost errors. I don't have the display going out anymore either. Can't remember if the errors were there before.
lyri has quit [Remote host closed the connection]
lyri has joined #armbian
marco44 has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
marco44 has joined #armbian
buzzmarshall has joined #armbian
jantones has joined #armbian
jantones_ has quit [Ping timeout: 264 seconds]
jantones_ has joined #armbian
jantones has quit [Ping timeout: 268 seconds]
Miyu is now known as hackkitten
lyri has quit [Remote host closed the connection]
lyri has joined #armbian
KREYREN__ has joined #armbian
KREYREN_ has quit [Remote host closed the connection]
lyri has quit [Read error: Connection reset by peer]
lyri has joined #armbian
archetech has joined #armbian
lyri has quit [Remote host closed the connection]
lyri has joined #armbian
flyback has quit [Quit: Leaving]
flyback has joined #armbian
Mangix has quit [Read error: Connection reset by peer]
<DC-IRC>
[Discord] <Tonymac32> right, but if you have stuff you want on that NVMe you'll erase it with that option. either 5 or 7 to get the bootloader into SPI or eMMC
<yang>
yeah I noticed two things... sd card /boot partition contains 5.10.x kernel, and nvme /boot partition contains 6.1.x kernel, I guess it somehow got duplicated
<DC-IRC>
[Discord] <Tonymac32> if it's a fresh install I'd go option 4, personal preference
<yang>
It's not a fresh install, I need to preserve the content on nvme :/
<DC-IRC>
[Discord] <Tonymac32> but the RK3588 is still very "special", so I can't promise that's a great plan
<yang>
so do I try no. 5 install update the bootloader on SD/EMMC
<yang>
?
<DC-IRC>
[Discord] <Tonymac32> you could, but I'm not sure why we're not seeing more than one block device if you have bootloader on SD right now
<yang>
yeah , I dunno either
<yang>
ahhh
<DC-IRC>
[Discord] <Tonymac32> which kernel
<yang>
maybe it's without the eMMC module...
<DC-IRC>
[Discord] <Tonymac32> ahhh
<yang>
physical module I mean
<DC-IRC>
[Discord] <Tonymac32> right right
<yang>
damn, how will it work then?
<DC-IRC>
[Discord] <Tonymac32> if anyone can verify the MTD boot is acceptable, you could run #7
<DC-IRC>
[Discord] <Tonymac32> on rk3399 it's perfection, but.. well.. RK3399 is a WIP-pocalypse so
<DC-IRC>
[Discord] <Tonymac32> on rk3399 it's perfection, but.. well.. RK3588 is a WIP-pocalypse so
<DC-IRC>
[Discord] <Tonymac32> RK3588*
<DC-IRC>
[Discord] <Tonymac32> lol
<yang>
well I can try MTD boot, what do I loose? there are no other options
<yang>
if it will fail I can keep using it with the SD card boot
<DC-IRC>
[Discord] <Tonymac32> well, SPI is always first boot priority
<DC-IRC>
[Discord] <Tonymac32> so it could go VERY wrong if something is borked
<yang>
oh
<DC-IRC>
[Discord] <Tonymac32> you'd have to RKDEVTOOL the thing
<yang>
then it would be better that I obtain the emmc module
<yang>
like order one
<yang>
and proceed afterwards?
<yang>
what would be other options?
<yang>
I won't be able to put it back in the chasis , though
<yang>
the sd card sticks out of the chasis on the wrong side heh
<yang>
ok, so I have chosen no. 7 and flashed the device...
<yang>
now...what happened
<yang>
the device got an IP from the 10.0.40.X
<yang>
and suppossedly the ssh belongs to the Ubuntu distribution
<yang>
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
lyri has quit [Remote host closed the connection]
zeemate has quit [Ping timeout: 256 seconds]
<yang>
ok, so I figured out i
<yang>
the MTD got flashed to Jammy 22.08 , and it is booting up into that, when the SD-card is not inserted. If I insert the SD-card it boots to Debian (previous install)