nihilista

Ok, thx for info. armbianmonitor -u gives an error but i remember bsp package was successfully installed, so it should be ok to apt autoremove...

After latest upgrade 21.05.01 apt says linux-buster-root-current-odroidxu4 is obsolete now and could be removed with autoremove. But even this version was installed with same upgrade, so i wonder why it should be removed now? Should i really remove that package? Thx

Just to inform, newest 5.4.28-odroidxu4 kernel seems to work fine too. Hopefully past problems with every new update are gone ;-)

Allright....now all seems to work fine, good work And with with 5.x kernel now my dual dvb-c stick has 2 working adapters (mostly the reason why i waited for working mainline kernel on this device)....

OK, thx. So i will test latest 5.4 kernel...maybe that works with latest. Before it won't boot at all ;-)

Anyone tested new kernel 5.4.19 ? Changelog says "Odroid XU4 current with kernel 5.4.y seems unstable", but what does than mean? Till now it wasn't unstable, it didn't work at all ;-) And why did same changelog say "Odroid XU4 legacy kernel images instability" ? Is 5.4.x now more stable (because it "seems") than 4.14.x? I'm bit confused... Btw, its no problem to make an image/backup and test and i know, developers couldnt test all....but little information will be fine :-)

Ah, will be fine if that get fixed. No really need for using 5.x kernel, but as it fully supports my dual dvb tuner (4.14 did not) it would be fine to have a working 5.x kernel. Many thx for all the good work !

I can confirm, no boot with latest 5.4.7 kernel....

Mmm...maybe i just wait a bit...but normally i have a backup before testing ;-)

Thx, good to know...and yes, its just a small bug ;-)

Hey, just a little question: On my other boards i can update u-boot within armbian-config, but not on odroid HC1 (system on ssd). Is that normal behavior or did i miss something? Not a big thing as i can do that with dd...btw. Maybe i have to test with 5.4.y kernel, don't know i need newer u-boot...

After upgrade to latest kernel (4.19.38) my device only boots into maintenance mode. System is on emmc and no problems before. I started armbian-config and switched back to previous kernel, but it doesn't boot system. Even with all USB devices disconnected it didn't start (as i see there are some usb errors in log), file system seems to be clean, just didn't start system in normal mode.... Any advice? Thx Update: OK, solved, after installing latest updates within maintenance mode its ok again....

With 4.14.5 kernel/debian next image booting fine (system on emmc), but i had debian legacy kernel and after upgrading no boot.

I should have known better..... today i did an apt update and saw thet there was an update to 5.38. Installed it and like with nearly every last update the device (OrangePi +) didn't boot. Did you even test updates in the stable repo before ? Don't know whats going wrong, so i will test it, but thats annoying.....

Confirmed, works without problems till now...

OK, thx, will try that..

Ah, good, which packages should be installed? linux-image-next-odroidxu4_5.34.171020, 5.34 u-boot, jessie-root, dtb ....?

Thats bad, cause now i've setup my device and just waiting for update, complete new install is not an option as i took some hours in configuring..... Are the packages in beta repo fixed too? So that maybe i can set beta source temporarily and install new packages from there?

Ah, great, thx Waiting for getting fixed packages from the repo ;-)

Yes, i know, but my thought was if solution is known and just some days away i wait and did a setup from scratch with benefits of fast ssd....

Good to see thats a real bug, but it stops me from setting up the device If i could i would help fixing this fast, but i have no idea how...but i hope you will find a solution

I used Armbian_5.33_Odroidxu4_Debian_jessie_next_4.9.51 image, tested with ext4 and btrfs, on GPT and dos partition. I dont have logs (flashed image again and again several times for next try), but after next try i could try to get some, need to mount sdcard on another linux device.

No, not without sdcard. Only with root filesystem on ssd. As i said, i did that with included armbian-config tool(nand-sata-install, boot from sd, rootfilefs on sata), but after reboot i have no access to the device. Don't know whats wrong, files are copied, boot.ini was changed to correct UUID, fstab (on ssd) includes new root, boot binding.... Maybe i have to manually change fstab on sdcard too? Or copy /boot to ssd too? I couldn't see whats wrong here...

Just a little question: I'm new with this device, but not with armbian. Tested the Image for HC1 and it works fine, but if i try to boot root filesystem from sata device (using armbian-config, sata install) it didn't boot. Anyone tested that with success? Thx

Now with 5.31 i upgraded all my 3 devices (bananapro,orange pi pro, nanopi), all running fine...so big thx to devs.